[HELP] Sharp Aquos S2 64GB Taiwan/International Firmware (Google Play)

KERRR on 04/07/2018 - 16:23
Last edited 04/07/2018 - 16:38

I recently bought the Sharp Aquos S2 64GB from this deal and need some help with it: https://www.ozbargain.com.au/node/385307

I received the Sharp Aquos S2 64GB today and am giving it to my mum for her birthday. I connected it to wifi to see how videos looked (hadn't changed it to Taiwan/International firmware yet). While I was out, it OTA updated to Oreo 8.0! Can I flash from OTA Oreo 8.0 to Taiwan/International 8.0 or Taiwan/International 7.1.1?

Advice would be greatly appreciated as XDA thread says: "DO NOT UPGRADE VIA OTA TO ANDROID OREO (8) (firmware 2000+) OTHERWISE YOU WILL BE NOT ABLE TO FLASH THOSE ROMS, UNLOCK OR TO DO ANYTHING NON OFFICIAL, UNLESS YOUR BOOTLOADER IS UNLOCKED".

Current Phone Version:
Oreo 8.0
Build: 00CN_2_140

Firmware on hand:
SS2-135F-0-00WW-B01-update.zip
SS2-2080-0-00WW-B02-135F-0-00WW-B01-update.zip

Renamed Firmware:
SS2-136F-0-00CN-B01-update.zip
SS2-2141-0-00CN-B02-update.zip

Tried re-flashing the above firmware. One shows up as "new update" after inputting code: * # * # 874 # * # * but when I click "install update" a message pops up saying "Problem Occurred". Anything that can help me to convert this phone to full English with google play services would be great. :)

Mobile

Comments

  • ntt on 04/07/2018 - 22:25

    it seems you're updated automatically by the phone to Oreo

  • KERRR on 09/07/2018 - 17:34

    Yeah it agressively updated to Chinese Oreo 8.0 within 20 mins of being on wifi. What I read on XDA is you can't downgrade on this version yet. Not sure how long I'll have to wait, but phone is essentially a paperweight until I can figure this out.

    Any advice is greatly appreciated. I don't know why they don't let you downgrade, what if your not a fan of Oreo 8?

    Sigh…

    • Pricebeat on 11/07/2018 - 16:55

      Where do you paste the file on the phone? I keep getting file not found. I pasted it in phone directory

  • Pricebeat on 10/07/2018 - 21:16

    I am in same situation. Do update if you find any solution

    • tpup1 on 11/07/2018 - 06:41

      Also in this situation unfortunately, please let us know if you find anything

      • mattie on 11/07/2018 - 09:33

        Me too, sucks.

      • Pricebeat on 11/07/2018 - 17:32

        May be we can unlock the bootloader as per this video
        https://youtu.be/5H1tGZ4W0Kc
        And then downgrade?

        • KERRR on 12/07/2018 - 21:58

          You can only try and see if it works. Let me know if it does.

    • illumination on 15/07/2018 - 03:35

      I've had a quick look… but this doesn't seem to be addressing the issue we're experiencing? I can't quite recognise what this is supposed to be for or what this is supposed to fix?

      Is 135E the firmware version of the TW 7.1.1 firmware we're trying to install? Based on the instructions posted by ajoesmith on Whirlpool, it seems it's 136F?

  • illumination on 14/07/2018 - 03:20

    I'm in the same position too lol

    • Pricebeat on 15/07/2018 - 17:23

      Just found this post. you will have to translate it. try unlocking bootloader first to downgrade. I don't have windows laptop to try atm.

      • illumination on 15/07/2018 - 17:25

        Thanks I'll look at this now..!

        edit: You know what, this just looks like a French (translated) version of this under "BOOTLOADER UNLOCK", "@SS2/SAT Bootloader unlock (if you have unlockcode.bin)".

        Damn this is hard. Really hard to find all the info necessary.

  • iphoneors7 on 14/07/2018 - 15:52

    In the same position.
    FFS

  • illumination on 15/07/2018 - 03:34

    Have posted a lengthy comment on Whirlpool to hopefully get some assistance!

  • nulled on 15/07/2018 - 15:48

    I am in the same problem. Can't use the phone at all - everything is in Chinese.

    • illumination on 15/07/2018 - 15:54

      Is the problem everything is in Chinese or your phone updated OTA to Android 8.0.0?

    • Pricebeat on 15/07/2018 - 17:35

      Change language by going into Settings > 4th option from bottom up > then 5th option from top. > tap on first option > tap on second option > choose English.

      • nulled on 16/07/2018 - 03:58

        Thanks. I did choose English (US), but most of the installed apps including Amap is in Chinese and not useful if I can't read.

  • illumination on 15/07/2018 - 17:24

    Another person who looks like he's in a similar position, but the difference between me and him is he says his "Build number" is 00CN_1_35C. Mine is 00CN_2_120. It also isn't clear if he's on 8.0.0.

    • Pricebeat on 15/07/2018 - 17:31

      mine is 00CN_2_140 lol. Under the android version it says 8.0.0

      • nulled on 16/07/2018 - 03:56

        My one is the 00CN_2_140
        Anyway forward?

  • illumination on 15/07/2018 - 17:56

    This guy was in the same position as me/us? (I feel we might be on different build numbers)

    His phone got updated to 8.0.0 00CN_2_120. Can't figure out what he did afterwards though and am relying on Google Translate here.

  • iphoneors7 on 17/07/2018 - 14:25

    Hey guys, has anyone worked anything out?

    • illumination on 17/07/2018 - 17:52

      I haven't… and I think I've been the most active here.

      Although I haven't tried anything in the last 24 hours.

  • illumination on 17/07/2018 - 20:15

    You know, I'm amazed no one else before this post on Ozbargain has experienced this. This phone has been pretty popular here for at least a few months now and connecting to WiFi during the initial setup phase of a new phone is very much "standard".

    Either that, or any other Ozbargainer who has previously experienced this:

    • Gave up, and accepted their phone was a paperweight
    • Figured out a solution themselves and never posted the solution
    • Also experienced the problem but did not post/ask for help
    • iphoneors7 on 17/07/2018 - 21:48

      Right now I'm just using dodgy apk downloads for all my apps.
      I need to find a solution to this shit/

      • tpup1 on 17/07/2018 - 22:21

        i found this has actually worked really well as a workaround in the meantime.

        Just a heads up to others, if you go to apkmirror you can download apps and then transfer them to the phone via usb. Unfortunately, I couldn't get any google apps to work but i got facebook, whatsapp, instagram and osmaps. Then if you go into the chinese browser app on the phone, with a bit of playing around you can get a dodgy version of chrome as well (which I use for youtube).

        It's not great and I don't know about the security but it's functional at least

    • Pricebeat on 20/07/2018 - 15:39

      Even if everyone complains there is no fix for this atm.

  • KERRR on 19/07/2018 - 08:28

    Check out this Reddit link. Guy claims you can unlock bootloader on Oreo 8 by buying unlock key from guy on XDA for $6. Rslist Reddit user has asked for more info on how to do that. Will wait for his response and report back: https://www.reddit.com/r/AndroidRoms/comments/8wm5rr/how_to_…

    • chochoy on 20/07/2018 - 11:50

      any updates? I'm also in the same boat as you guys.

  • iphoneors7 on 20/07/2018 - 19:56
    +1

    Found this on a russian forum; has been translated.

    Create a guide to rollback from 2.080 (Android 8) to 1.35E (Android 7) for a locked bootloader .
    I myself got into this unpleasant situation and there is no concrete leadership anywhere.
    In general, there is a good instruction for switching to custom 8 here .
    I will describe in my own words for the transition to 7. I rolled back two phones.
    In the process all data will be deleted, make a backup.
    We need drivers, adb / fastboot. Google (the driver for example is in the programs ntool or OST). If you have problems installing the firewood on Win10 here .

    1. The program to unlock the loader at the moment can only be obtained by a file-signature through the utility ntool. To create such a file you need 10 credits. This can be done even without a phone. But you need to know the serial (sticker on the phone, for example SS2LHMG854700578 or better through "adb devices") and IMEI1 (also on the sticker or better * # 06 #)

    - You need to buy credits. You can take a minimum of 20 credits (~ $ 6). Where to buy find yourself - Google to help.
    - Google / download ntool
    - On the Settings tab, enter the login / password (give with credits) and click New Password. Through Information, you can check how much credit is used / used.
    - In the HMD Smartphones tab in the fields, enter SERIAL and IMEI1. Click BOOT UNLOCK.
    - The IMEI_SERIAL.bin file will be created in the Backup folder. You can rename to unlockkey.bin - this is the signature file for unlocking.

    1. Unlocking the bootloader with the received file is described here . But she somehow does not quite unlock. That's why I still did point 3, although it is probably possible to do it right away as in point 3

    2. So, the phone is not completely unlocked for fastboot. Therefore, after rebooting again, you need to turn on USB debugging and reboot into fastboot and enter two commands:
      fastboot flash unlock unlockkey.bin
      fastboot oem unlock-go

    On the phone again press Unlock. Now the phone is completely broken. After unlocking, we wait a long time (about 5 minutes) until the phone reboots.

    1. Next, you need to flash TWRP and put the old BOOT out of it. Described here , item 11

    2. You can flash 1.35. The program for firmware (OST) and the firmware 1.35E in the format nb0 here . By the way, the link in the header for this firmware does not work.

    Special thanks to heineken for the provided firmware and information. Separate Fu Sharp for the release of the official firmware with a bad connection.

    source: https://translate.googleusercontent.com/translate_c?depth=1&…

    • illumination on 21/07/2018 - 01:07
      +1

      Hang on… so you tried this and it worked?

      • iphoneors7 on 21/07/2018 - 11:23

        I haven't tried this, but from all my research this is legit.

    • KERRR on 21/07/2018 - 07:29

      That's the same advice I got from rslist. $6 is a small price for a usable phone. I'm going to try it next week and report back.

      • iphoneors7 on 21/07/2018 - 11:26

        I want to try this now but I have a mac, need to find someone that can lend me their windows pc.

        • I know nothing on 21/07/2018 - 16:34

          Have a look at this link at xda

          This Heineken guy claimed he has a tool called Online Service Tool that will load the official 1.35E worldwide Rom onto the Sharp Aquos S2. But he didn't say if the boot loader must be unlocked beforehand. However, the last sentence seems to imply No because he said the boot loader can be unlocked after uploading the Rom.

          https://forum.xda-developers.com/showpost.php?p=75936562&pos…

        • mingu90 on 23/07/2018 - 16:18

          @I know nothing: Please note that it is for normal flashing "from the box", which you use for flash the WW rom into a CN rom phone.

      • iphoneors7 on 23/07/2018 - 19:50

        Did you end up trying it?
        I would of tried but i don't have windows

        • mattie on 23/07/2018 - 21:32

          I can lend one, I'm in 2217

      • linnaen on 31/07/2018 - 14:54

        Well?

  • iphoneors7 on 25/07/2018 - 19:30
    -4

    Is everyone actually too scared to try the method that I linked? puss puss pussies
    I live in a mac household and can't try it.
    Going to use a friend's PC asap

  • mattie on 26/07/2018 - 11:32
    +1

    I would love to give it a go but really can't understand much of the instructions, is this the ntool https://www.ntool.info/

  • dan o on 27/07/2018 - 19:57

    first time post - joined because in same boat as everyone… any solutions as yet?

  • shiznit on 30/07/2018 - 15:03

    From the Whirlpool forum, muffie has successfully unlocked the bootloader from locked Taiwan 8.0.
    It should work the same way for locked Chinese 8.0

    https://forums.whirlpool.net.au/forum-replies.cfm?t=2664378&…

    • iphoneors7 on 30/07/2018 - 17:17
      -1

      we all have locked china 8.0. So it is not relevant

      • pongwaters on 30/07/2018 - 23:18
        +3

        I unlocked an S2 on CN_2_140 (Oreo 8 China) just fine using ntool. Cost 20 credits, $8.54 AUD (5.99 USD + 30c + AUD Conv).

        Ntool gets flagged as a Win32/Tiggre!plock on unpack. Ver 0.036.

        Flashed it back to 7.1.1 00WW_1_35E with OST. Works great.

        Could in theory now bump it to Oreo WW stock, re-lock the bootloader so its normal without the dirty yellow boot warning, with the knowledge I can unlock it again at will with the patch from Ntool.

        • KERRR on 31/07/2018 - 02:22
          +1

          Glad to hear it worked for you pong. Can you provide a step by step tutorial on what you did, so others can follow. Much appreciated!

        • beebul on 31/07/2018 - 11:44

          I'd like to hear how you did this too.. thanks :)

        • dan o on 31/07/2018 - 19:49

          Step by step tutorial please!!!

      • pongwaters on 31/07/2018 - 22:58
        +6

        Not a lot of time to write up a guide sorry. Here is the high level stuff.

        All information is effectively found from a lot of reading of the XDA thread

        Overview:

        • Get Android fastboot/adb working on your workstation so you can talk to your phone via USB debug mode. Acquire ADB from the web such as latest_usb_driver_windows.zip from Google here Make sure fastboot works when your phone is in download mode. I had to change my driver inf file as per here to get Windows to see the phone in download mode, else fastboot failed.

        • Use fastboot to flash the unlock image you acquired from ntool. Instructions

        • Bootloader unlocked - your free to do what you want now

        After bootloader unlocked:

        • I then followed XDA link heineken78's material "Instruction how to get back from offical SAT/SS2 oreo WITH UNLOCKED BOOTLOADER"
        • Then downgraded to "Official Firmware 135E WW installation via service tool", here
          Applying SS2-135E-WW-open_bl.nb0.zip with the OST tool.
        • After this was complete I had a working stock 7.1.1 WW ROM with Google apps. You can then upgrade to stock Oreo or go with custom ROMs
  • illumination on 31/07/2018 - 03:08
    +1

    Here's my latest update

    Basically:

    • I've bought credits for US $6.29 to use ntool to unlock bootloader
    • Generated the .bin file using ntool to unlock the phone (renamed to unlockkey.bin - requires you to plug in IMEI1 and serial number of phone)
    • Installed ADB drivers using "OST Portable"
    • ADB commands are working fine and as expected when phone is on, but not working in Download Mode

    I'm stuck here. Based on my research so far, it's probably to do with updating drivers but I haven't been able to figure out how to get the right drivers.

    Seems like you also need to technically "unlock bootloader" twice, for some reason.

    The google translated stuff from 4pda can be a little hard to understand but I've been trying to make sense of it as much as I can. I get the feeling someone on the Russian forum might've experienced what I've experienced but googling for the keywords (understandably) doesn't give me any search results from 4pda!

    Anyway, at least things are looking a bit better now, given that it seems 1 or 2 people seem to have been able to get it working from the current state of our phones lol

    • pongwaters on 31/07/2018 - 23:13

      Try this.

      You need to tell the driver about your USB device ID. Worked for me anyway. Windows will then link your device to the ADB driver not some other less useful driver.

  • mattie on 02/08/2018 - 17:35

    Clear as mud

  • impulsebuy on 02/08/2018 - 17:49

    I'm in the same situation, just ordered credits,,, Who want half of my 20 credits for $5?
    I was having issue with drivers in windows too, however after I install windows driver came with phone it seem to fixed it,,,fastboot can see the device now.

    • KERRR on 03/08/2018 - 18:23

      I'll do that impulse, can you transfer credits? PM me

      • impulsebuy on 03/08/2018 - 18:37

        I can't see why not. You require to download the Ntool here.
        I'll provide the account login still have 10 credits loaded. Check PM for my pay-pal payment.

  • mattie on 03/08/2018 - 18:05
    +1

    I'll give you $20 if you fix my phone.

  • illumination on 05/08/2018 - 03:58

    Still going through this…

    Latest issue:
    When using OST to install TWRP, I'm getting the following error:
    Error = Download fails, Error = SE_ERR_SUT_PHONE_KEY_ACCESS_FAIL (0x60E), but it seemed like it worked? Because phone restarts into TWRP. Haven't tested the next part of actually trying to install 135E WW Firmware though because it's still downloading. Also haven't flashed "SS2-Bootloader_old_service.zip" yet because I can't get it on the device.

    Also - I think I may have semi bricked it? Because right now if I restart (i.e. leave TWRP Recovery), the phone doesn't turn on. It tries to boot but it just sits on the "Android" boot text.

    Anyone who's been through this already able to advise?

    • misterpotatomato on 06/08/2018 - 06:45
      +1

      If you can get into TWRP you may be able to sideload a new rom onto it, maybe. I have no experience with this particular phone, I just know that I have successfully sideloaded a rom onto one of my China Mobile phones.

      I wouldn't stress too much about your semi-brick, if your flash of your rom has failed then the phone won't boot. You are only really screwed if you can't get into TWRP/download mode.

      Google "adb sideload" for more information. It boils down to this:

      1. boot into TWRP
      2. get your rom .zip
      3. in TWRP, advanced, there should be an ADB sideload option
      4. tap that (go hippy go!, uh, the ADB sideload option i mean)
      5. phone is now in adb sideload mode
      6. on your pc, in command prompt, use "adb sideload rom.zip" (if your adb is too old you will not have the sideload option. get the android sdk for the newest/shiniest adb.exe)
      7. wait for flash to complete, reboot phone when done

      like i said i dont have this phone and i have written the above from memory so if you do that and it asplodes its not my fault. hope it goes well!

      • shiznit on 06/08/2018 - 07:39

        What's an asplosion? Sounds like something that happens after eating too much Mexican/Indian.

      • illumination on 06/08/2018 - 20:11

        Thanks so much for the advice.

        I'll try it when I get a chance.

        I wouldn't stress too much about your semi-brick, if your flash of your rom has failed then the phone won't boot. You are only really screwed if you can't get into TWRP/download mode.

        Yea that's what I'm thinking too. Being able to get into TWRP/dowload mode normally means it's recoverable.

        On a side note - tried switching it on yesterday and it was stuck on "Sharp" screen (different issue to above). Couldn't get into Download mode. Didn't try entering Recovery mode/TWRP - pretty sure Recovery/TWRP needs a computer.

        • illumination on 07/08/2018 - 03:40

          FYI misterpotatomato - I didn't end up following your steps because I managed to fix it another way.

          So my phone (at the time of the comment you replied to), as I said, didn't seem to be able to be loaded into Download Mode or Recovery mode but I didn't have it connected to USB.

          I tried it tonight and was able to load it into download mode. Flashed TWRP from download mode and went from there.

          My phone is working now.

    • pongwaters on 06/08/2018 - 22:04

      I installed TWRP via download mode not via OST initially.

      Ref

      -Download twrp from here https://forum.xda-developers.com/sho...&postcount=288
      -Flash twrp from fastboot: "fastboot flash boot filename.img"

      e.g. "fastboot flash boot SS2-boot_twrp.img"

      Side note:
      This version of TWRP broke my wifi on android 7 but later it corrected when I flashed the 135 rom back on. Some Transient panicing. Its fine on Oreo.

      Then:

      -Get Bootloader_oldservice.zip for you model from here https://forum.xda-developers.com/sho...&postcount=287
      -flash zip from TWRP.

      I recall perhaps getting the Error = SE_ERR_SUT_PHONE_KEY_ACCESS_FAIL when I did not set the right OST options:

      Ref

      1. for NORMAL flashing of firmware you choose Options: 1,3,4 ( clear logs send to factory), 5 (300WW).Untick option 8!
        for UNBRICK (9008 mode) flashing of firmware you choose Options: 2,3,4 ( clear logs send to factory), 5 (300WW).Untick option 8!

      a

      • illumination on 07/08/2018 - 03:39

        Thanks so much pongwaters.

        I've fixed it now. I had to use fastboot to install TWRP for it to work for me. Then flashed Bootloader_oldservice.zip from TWRP.. the treble… then done!

  • ubor on 06/08/2018 - 19:42

    Is NTool something you run on Windows PC or on your Sharp S2?

  • illumination on 07/08/2018 - 03:35
    +4

    Ok I did it! Phone is working with Google Play Store! So satisfying..

    This is definitely one of the more difficult Androids I've tinkered with. The instructions are not too clear and are sorta all over the place. This is no one's fault - no one gets paid to do this but it just makes it hard for those that are less familiar.

    It's late, but I just wanted to let you all know that I've done it and I've got a Word document typed up pretty much with a "log" of what I did and roughly in what order, including the errors and problems I've encountered.

    I'll share the link below, but let me make 2 things clear:

    • This is extremely rough right now. I've literally done it quickly just so if any of you want to see what I roughly did in what order you can see what I did, but do not follow it exactly in order because you might just encounter some of the issues I had. I will get around to fixing it up when I can, and am open to others amending/touching it up if necessary
    • I did not install TW Firmware. Instead, I installed the custom ROM "Unified treble rom v3".
    • If you want to install TW Firmware and use it relatively "cleanly", I think you just flash the TW firmware instead of the custom ROM zip firmware.

    My eventual goal is to:

    • Have GCam/Google Camera
    • Have Magisk so I can hide root and continue using Android Pay

    But I have setup the phone in v3 treble and confirmed that it does now indeed have Google Play Store.

    Also - happy to sell my remaining 10 credits to someone to use ntool for half the price I paid ($8.90ish).

    Here's the link to my "scrap log"

    • dan o on 07/08/2018 - 09:31

      you are an absolute legend!! i've just downloaded a copy from your google docs. thanks HEAPS for writing it all down! i'm also keen to buy your 10 credits off ya if still available!

      • illumination on 07/08/2018 - 14:23

        No prob.

        Yep still available. Message me. I can't message you - I think your PMs are turned off.

        • dan o on 08/08/2018 - 06:35

          oops sorry. default settings when i signed up. message you now

    • illumination on 07/08/2018 - 14:22
      +1

      At work at the moment and don't have the phone with me, but wanted to add something about battery life.

      I deliberately left the phone on overnight on flight mode. It dropped 7% (~6 hours).

      That's not very good for standby battery life..!

      We'll see how it goes going forward - apparently some phones need to "warm up" to a new custom ROM and need time to "settle".

      Further to my comment above:

      • Feel free to ask me questions about bits of the guide and I'll try and help out
      • Feel free to edit the document and make things clearer/better
      • I recommend you read ahead a few steps just so you can get an idea of the problems I encountered and what I ended up doing to address the problems.
      • illumination on 09/08/2018 - 00:25

        I deliberately left the phone on overnight on flight mode. It dropped 7% (~6 hours).

        Second night, it dropped 6%, also over about 6 hours.

  • willhaben79 on 09/08/2018 - 23:28

    Does anybody know if the the Sharp Aquos S2 and Sharp Aquos C10 (which started to sell in Germany in July) are really identical, like stated on some websites? If it would be the same phone, one could use the firmware of the C10, which should contain all European languages for the S2.

  • illumination on 10/08/2018 - 13:53

    Small gripes with the phone so far (but nothing major - probably more so that I'm spoilt by Redmi Note 4)

    • Can't name SIM cards. This was extremely handy on the Redmi Note 4 with LineageOS but I don't think it's a common feature on other phones. Particularly important for SIM sluts like myself
    • Lack of 3.5mm headphone jack - an inconvenience, but not a huge one I guess, but the more people (like me) say this and feel this way, the more manufacturers will feel it's ok to keep omitting it. I guess I'm kinda undecided on how crucial I think it is.
    • Auto brightness (known issue, as pointed out on Whirlpool) on the Treble V3 ROM does not work very well. The highest brightness is dimmer than the highest brightness that you can manually set, and the lowest brightness is brighter than the dimmest brightness you can manually set.
    • Battery life is inferior to Redmi Note 4. I can't quite tell yet how bad it is, because I've been using as a wireless modem which obviously eats into the battery a lot quicker, but from its standby time I can tell it's not as good as the Redmi Note 4!
    • The (relatively) smaller modding community makes the instructions to do any sort of modding a little muddier (as can be seen from our/my experience above)

    I'll post up positives later, which I'm sure will outweigh the negatives!

  • ubor on 10/08/2018 - 19:26

    Hi illumination, how do you run NTool. I open the zip file on my PC. It contains 2 folders (Drivers and Tools) and 3 files (ntool.exe, NTool.ini, ntoolLib.dll). When I extracted the files to a new folder, only the two folders and ntoolLib.dll are extracted. the ntool.exe is not there. Do you know what I should do? Should it disable anti-virus to install NTool. Thanks.

    • illumination on 11/08/2018 - 12:23

      Hey, not sure what's happening there. It does sound like it could be related to the anti-virus tool.

      Basically after you extract, you literally double-click ntool.exe to open it which is the file you're missing.

      See if disabling anti-virus helps.

      • ubor on 12/08/2018 - 12:26
        +1

        After disabling the anti-virus program, I was able to run ntool.exe.

  • illumination on 12/08/2018 - 20:57
    +1

    Has anyone else successfully been able to recover from 8.0 CN Firmware? I'm hoping my guide has helped?

    I've added the following to the guide (below the main content):

    • How to obtain root access (by installing Magisk) - this allows you to keep using Google Pay + other apps that don't like rooted phones
    • How to install Google Camera
    • How to install AdAway - this allows your phone to block all ads in all apps

    Further comments I have:

    • I wish I could configure the fingerprint sensor to also double up as a home button/have other features/functions
    • Battery life is definitely not as good as Xiaomi Redmi Note 4, but don't forget 3000mAh battery vs 4000mAh. Example of inferior battery life - 11% standby drop from 8 hours overnight. So there's probably something going on there - but keep in mind it could be an app that I've installed
    • I'm not great with cameras but I think the Sharp has a better camera than the Xiaomi Redmi Note 4, and I think it's better than the stock camera?
    • Evie Launcher is pretty cool - potential alternative to Nova Launcher (read about it on Reddit) - just wish I could configure apps on the home screen to be able to have alternative gesture shortcuts like is possible on Nova Launcher, e.g. swipe on WhatsApp to open SMSes
    • Using Magisk as a way to "hide" root is amazing
    • WhatsApp messages still cause my phone to vibrate, despite having turned off "Vibrate" under "Message notifications" and "Group notifications". I had this same issue on my Xiaomi Redmi Note 4 running LineageOS, and I "force" turned it off by using Privacy Guard to prevent WhatsApp from being allowed to make my phone vibrate. The downside? It doesn't vibrate for anything - including WhatsApp calls, which I wanted it to vibrate for… I never figured out a fix for this on the Redmi Note 4. Hoping to find one for this phone. This doesn't have PrivacyGuard so there isn't even a way for me to turn off vibrate for WhatsApp.
    • Stock alarm app has very little parameters that you can play with - i.e. can't adjust snooze time from 10 mins to 5 mins or other.
    • The "intuitive gestures" mode of navigating the phone is quite cool, but I don't think there's a way to configure it a bit differently which is a shame. For example, the "swipe up and hold to access task viewer" - you have to hold position in the middle of your screen for a bit longer than I'd like to…
    • The phone has its own implementation of Face ID, which I don't think I noticed anyone else mention, and I find it pretty accurate/good!
    • I miss the headphone jack
    • Screen looks great. I don't dislike notches so the "notch" doesn't bother me. Alternative is you have no notch (no "wings") and you lose the space next to the camera and have no screen there instead
    • It's so nice, small, light, portable, yet it's still a 5.5" phone
    • %#!&ing amazing phone for $200
    • shiznit on 12/08/2018 - 23:34

      Thanks for the guide, it helped me fix a friend's stuck phone. One thing I noticed is if you install the trebled rom through ost, it includes twrp. So you can skip the steps for installing twrp. Just unlock the bootloader then install trebled.

    • shiznit on 13/08/2018 - 08:48

      Regarding fingerprint sensor gestures, there are many apps on the Play store that let you customise them. You need to be on Oreo. I'm still on Nougat so I haven't tried any.

      • illumination on 15/08/2018 - 18:54

        Haha I can't believe I didn't think of that! True. I will look into it.

    • ubor on 13/08/2018 - 19:16

      Hi illumination, I have question about running NTool. After I entered IMEI and S/N of the phone, what is the next step. There are so many options: IDENTIFY, FLASH, FRP UNLOCK, BOOT UNLOCK etc. I tried to IDENTIFY but nothing happens. It kept saying "Waiting for phone".
      Any idea? Your help is appreciated.

      • shiznit on 13/08/2018 - 21:54
        +1

        BOOT UNLOCK

        Fill in your login details in the other tab first.

      • illumination on 13/08/2018 - 21:56
        +1

        What shiznit said.

        Sorry didn't realise the guide didn't state that.

        A reminder though (to all) - feel free to update the document!

        • ubor on 14/08/2018 - 19:46

          I got the bin file in the backup folder now. How can I unlock the bootloader on my Sharp S2? Do I use NTool to do it or use OST Portable to do it. I ran OST Portable and it asked me to connect the phone and select software image file. Is it the place to enter the bin file created by Ntool?

          Sorry being a noob.

        • illumination on 15/08/2018 - 14:06

          @ubor:

          Hey, you use OST Portable.

          In OST Portable, there's a folder called "SUT" which is where your fastboot/ADB commands should work in CMD.

          You put the bin file into the SUT folder.

          Sorry being a noob.

          Haha it's fine. I know this is not super simple especially if you haven't played much with rooting/tinkering Androids before.

        • ubor on 15/08/2018 - 22:11

          @illumination: Thanks illumination. I finally got my phone's bootloader unlocked. According to your scrap log, the next step is TWRP install. The XDA web page says it is for 135 ROM. However, my phone is already upgraded to TW Oreo 8.0. Does it mean I cannot install TWRP?

        • illumination on 16/08/2018 - 04:31

          @ubor:

          The XDA web page says it is for 135 ROM. However, my phone is already upgraded to TW Oreo 8.0.

          Does that mean you were always on TW 8.0 and you are simply following this guide to try to unlock your bootloader?

          According to your scrap log, the next step is TWRP install.

          Yep, that's after doing a combination of fastboot unlock type of commands in CMD not once, but twice. Did you do that? I'm still not sure why it requires it twice, but all the guides said to do it twice, with slightly differing commands, so I did it twice.

          Also - notice my scraplog shows me trying to use OST to install TWRP using "SS2-twrp.2.nb0". This didn't work for me and I then did it from fastboot (CMD) - refer to what's currently at step #39.

          I also notice for steps #41-42 is me getting the phone ready (by flashing "SS2-Bootloader_old_service.zip" via TWRP) to flash the Custom ROM from file "SS2-SIUI_v3_1_trebled_by_heineken.nb0". Might not be necessary if you're not planning to get to Custom ROM.

          Does it mean I cannot install TWRP?

          I think you still can because you've obviously unlocked your bootloader using CMD and the fastboot commands right? As above, I used CMD/Fastboot commands to "install" TWRP, so I think you can too. I don't think it's related to what firmware you're on.

        • ubor on 16/08/2018 - 18:25

          @illumination:
          Yes, I flashed to TW 7 135 ROM when I first got my phone but it auto-upgraded to TW 8.0 without notification. Since then, the phone became unresponsive with System UI not responding. I factory reset it almost every week and I became sick of it. I will try loading a custom rom now I have the bootloader unlocked. Thanks for your help.

        • illumination on 16/08/2018 - 18:29

          @ubor: Oh that's interesting.. so you actually already have Play Store - you're just trying to change it up because it's not working well for you.

          Let me know if you have any more questions!

        • ubor on 16/08/2018 - 18:37

          @illumination:
          Yes, I had everything and it did work well for the first week it was on TW 8.0.
          I have another question. What is the fastboot command to extract TWRP SS2 downloaded from here: https://forum.xda-developers.com/showpost.php?p=76412381&pos… in step 39?

        • illumination on 16/08/2018 - 18:40

          @ubor: oh LOL

          I remember struggling here too. I was like wtf.. where the hell is the link, it's not there.

          I've included a screenshot for #39 now and boxed where the link is. It's easy to miss. It kinda camouflages into the post somehow…

Login or Join to leave a comment
Login Join