Related
Strange little story– A tale of (apparent) success snatched from the jaws of chronic stupidity and without any idea why it all worked.
I was given an unwanted X10 Mini Pro for my daughter – which was locked to 3 UK. So I unlocked it using a server unlock bought through eBay. That all worked perfectly but then I wanted to unlock the bootloader and install CM9.
I’d installed CM7 on another X10MP for a friend last year and so I had S1tool etc but of course it reported “RA0405” (locked bootloader) and “non recognised certificate” . (Awww, sh1t !)
Well then I read that flashtool can now unlock the bootloader so I thought I’d give it a try. Running Flashtool 8.10 I tried it but couldn’t get beyond the pop-up window where it asks you to connect the phone in flash mode. (Aww, Double sh1t!!)
Then clicking around the options on flashtool I came across “Root” and thought I’d give it a go in case the BL unlock needed root access. Well it threw up a few lines of text and reported that I was rooted. I re-ran the BL unlock again but no joy. (Awwww, double bugg3ry sh1t!!!).
Call me pig-headed but I then tried S1tool one last time. Again, it don’t work but it did throw up one line that told me specifically that while I still had the dreaded “Capital R” locked bootloader that it was “already rooted”.
On the basis that the phone had cost me nothing and that “root” normally indicates “take me any way you like , big boy” I then went back into flashtool and flashed the NaA ICS kernel. It worked!
I tried to restart into CWM – It worked too!! I wiped and flashed CM9 – It worked!!!!
I rebooted praying to all the saints that it wouldn’t bootloop and eventually a lockscreen appeared and it let me in to the start of the usual setup wizard.
Now, the BL unlocking guides all said that forcing a BL unlock with a non-SEMC/SETools or Optimus unlocked phone ccould either break your Sim-unlock or bork your radio functions completely so I still wasn’t optimistic but I shut the phone down slapped in my daughter’s Voda SIM, restarted and – “By the sacred balls of St Bartholemew!!” everything works just perfectly.
Now my question is simple. In true “idiot savant” mode have I got to the right end-point by a totally illogical and a “that should never have worked” series of blunders? Or could someone intelligent tell me why it worked and (if so) why it isn’t already written-up somewhere as another way to get past your BL and do a custom ROM install?
I’m not touching the damn thing again – in case my luck has now run out - that much I do know……
Could you post the output of S1Tool?
Unlocking the bootloader on an unrecognised simlock-certificate MAY work, but more often than not it destroys the radio-capability.
I'm fairly sure your bootloader is unlocked, can't imagine the nAa-kernel working otherwise, but without the output of S1Tool there's no way of telling
I'm getting an error when trying to unlock my phone's bootloader :
FAILED remote: Command not allowed.
I am copy/pasting "fastboot -i 0x0fce oem unlock 0xBEA3575C8951F712"
When I type "fastboot devices" it recognizes my device, and I installed all the drives from flashtool so I don't think its a driver issue.
I've tried using flashtool, the sdk, and minimal adb and falshboot. For flashtool I've tried adding the ulcode.txt to registerd devices folder.
I've tried different PC's and different cables. I've also tried it on androids 5, 6, 7, all of which I've flashed from the flashtool download tool (Custom UK versions).
I have USB Debuggin on, OEM unlock on, and Unkonwn Sources on. When I type *#*#7378423*#*# the phone says "Bootloader unlock allowed : yes".
A final thing to note is when I flashed android 7 the OEM unlock butto was grayed out - "Bootloader already unlocked", even though the *#*#.... code still said "Bootloader unlock allowed : yes".
I've searched all the forums and none of the fixes seem to work. Any help would be greatly appreciated - thanks!
Edit : I tried this on my old z1 compact and it worked, so its nothing wrong with my computer. I guess my z5 is just broken.
Nope, I am having the exact same issue you are. I have model E5823.
Got the unlock code off sony.
Trying everthing I can.. Can't get past that damn FAILED (remote: Command not allowed). error.
Installed 5 different fastboot/adb programs, sony drivers are latest. fastboot and adb do work, they see the device OK, it just won't accept any unlocking.
Unlockable is yes, in service settings view.
I am currently in the middle of trying to get the sony emma flashtool program to actually access my phone - it just gives me a "phone is locked" message..
going to try flashing a stock ROM with flashtool next.. but you're not giving me hope.
It is possible, because sony itself says it is, and there are other people out there who have done it. There must be a way.
Hey guys,
same here.
After fastboot fails to unlock the bootloader with
fastboot -i 0x0fce oem unlock 0xKEY
Click to expand...
Click to collapse
I tried it with flashtool and this post https://forum.xda-developers.com/showpost.php?p=58070067&postcount=34 and it worked!
But now I want to flash the modified kernel with TWRP and SuperSU with
fastboot flash boot kernel.img
Click to expand...
Click to collapse
but without success
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Same in Flashtool using option >>>>lightning icon"/Fastboot mode/Select kernel to Flash/path to boot.img.
Now bootloader is unlocked but DRM Keys still activ - if i can trust the system information.
Backup the TA-Partition was successful with iovyroot.
Whats wrong with this piece of plastic? I'm rooted all my Galaxy's before, but without any problems - this Z5c is annoying. And only because I want to change my MAC address, because my wife has same phone and same MAC Both in the same network isn't good.
Anybody who can help?
Thanks!
lfjriazr6kp6w95 said:
Hey guys,
same here.
After fastboot fails to unlock the bootloader with
I tried it with flashtool and this post https://forum.xda-developers.com/showpost.php?p=58070067&postcount=34 and it worked!
But now I want to flash the modified kernel with TWRP and SuperSU with
but without success
Same in Flashtool using option >>>>lightning icon"/Fastboot mode/Select kernel to Flash/path to boot.img.
Now bootloader is unlocked but DRM Keys still activ - if i can trust the system information.
Backup the TA-Partition was successful with iovyroot.
Whats wrong with this piece of plastic? I'm rooted all my Galaxy's before, but without any problems - this Z5c is annoying. And only because I want to change my MAC address, because my wife has same phone and same MAC Both in the same network isn't good.
Anybody who can help?
Thanks!
Click to expand...
Click to collapse
You helped me fix it! Turns out I had named my ulcode file ulcode.txt so it was actually ulcode.txt.txt
I still don't get why adb didn't work but flashtool does, though.
For your other point, I used this guide to flash a kernel.sin:
https://twigstechtips.blogspot.ca/2016/04/sony-z5-compact-root-without-losing-ta.html
Hope it helps, and thanks again!!!!!
lfjriazr6kp6w95 said:
>> I tried it with flashtool and this post ***pasted*** and it worked!
1.: Go to the folder where Flashtool was installed
2.: Open the folder named "custom"
3.: Open the folder named "mydevices" (if it exists, in my case Flashtool version 0.9.18.4)
4.: Right button, New, Folder. Name the folder with your device code.
5.: Open the folder created previously
6.: Right button, New, Text Document. Name the text document as ulcode
7.: Open the text document created previously
8.: Paste your unlock code and save
9.: Open Flashtools and try the BLU option again.
obs 1: the step #3 I think it depends on your Flashtool version, because it wasn't mentioned at the solution
obs 2: at the step #4 is mentioned your device code. your device code is showed in the log when you click the button BLU, at the "Current device", after your device model.
Search a line like:
09/045/2015 23:45:08 - INFO - Current device : C2104 - AB100C2DE3 - 1272-4136_R5B - 1269-5420_15.3.A.1.17 - WORLD-a_15.3.A.1.17
in this case, the device code is AB100C2DE3 and this should be the new folder name (step 4)
Click to expand...
Click to collapse
I tried that method, it does not work. It SEEMS to work from face value, yes, but it is faulty I think.
Also, the location of the folder is wrong - it should go in /users/USERNAME/.flashtool/registeredDevices/
It 'unlocks' it during the flash stage of BLU in flashtool, yes, but it's supposed to do it in the fastboot stage according to other instructions I've read! It also freezes up and does not complete the operation unless I 'cancel' it - but it's supposed to go through a wipe process. It never does.
The system info has no status on whether or not it's unlocked or unlockable after flashtool 'unlocks' it using that method. Also, no other flashing can be done, because it returns the same Command not allowed error every time.
I believe fastboot is set up correctly as it returns getversion 0.5 and the device shows up in fastboot devices. I checked the IMEI was a correct one by going to imei.info. Don't know what else to do.
Why the heck are our devices refusing to unlock when others are doing it fine, and it's claiming to be unlockable?!?
I returned my Z5C and got a new one from the manufacturer and it's again refusing to unlock.
Hi,
I am late on this thread, but just buy a Z5C and face exactly that situation : no way to unlock the device ! Using flashtool and BLU results as a Rooting Status unknown, so I have to unlock the device using flashtool again...
The only thing I succeed is to flash the latest firmware with the help of XperiFirm. Still have "Bootloader unlock allowed : yes" but impossible to unlock it.
Has anyone found a solution for that problem ? Could it be related to a specific firmware to install ?
I am totally lost after two days of reading and unsuccessful attempts ; I would really like to install LineageOS on my new Z5C.
Any help would be greatly appreciated. Thanks.
Hi,
After some hours fighting with windows, drivers, signature (all in a VM), I switched back to Linux/Ubuntu. At least flashtool seems to work better (out of the box), and it asks me to reconnect the device in fastboot mode... But still the same error at the end. It adds "Maybe the OEM is not enabled", but it is of course (double checked).
But what means "Bootloader status : ROOTABLE" ? Did I miss something ?
Can somebody help please ? I contacted Sony support, but they don't support such operation...
Here is the log from flashtool :
====================
05/032/2018 17:32:18 - INFO - Please connect your device into flashmode.
05/032/2018 17:32:35 - INFO - Opening device for R/W
05/032/2018 17:32:35 - INFO - Device ready for R/W.
05/032/2018 17:32:35 - INFO - Reading device information
05/032/2018 17:32:36 - INFO - Phone ready for flashmode operations.
05/032/2018 17:32:36 - INFO - Opening TA partition 2
05/032/2018 17:32:37 - INFO - Current device : E5823 - CB5A274154 - 1299-1743_R12C - 1295-6639_32.2.A.5.11 - GENERIC_32.2.A.5.11
05/032/2018 17:32:37 - INFO - Closing TA partition
05/032/2018 17:32:37 - INFO - No loader in the bundle. Searching for one
05/032/2018 17:32:37 - INFO - Processing loader.sin
05/032/2018 17:32:37 - INFO - Checking header
05/032/2018 17:32:37 - INFO - Flashing data
05/032/2018 17:32:37 - INFO - Loader : S1_Root_f936 - Version : MSM8994_41 / Boot version : S1_Boot_MSM8994_LA1.2.2_42B / Bootloader status : ROOTABLE
05/032/2018 17:32:37 - INFO - Max packet size set to 4M
05/032/2018 17:32:37 - INFO - Opening TA partition 2
05/032/2018 17:32:37 - INFO - Start Reading unit 00 00 08 B2
05/032/2018 17:32:37 - WARN - ERR_SEVERITY="MINOR";ERR_CODE="0025";ERR_DYNAMIC="00000000";
05/032/2018 17:32:37 - INFO - Closing TA partition
05/032/2018 17:32:37 - INFO - Ending flash session
05/032/2018 17:32:37 - INFO - Now unplug your device and restart it into fastbootmode
05/033/2018 17:33:51 - INFO - Unlocking phone using key AF668B4FXXXXXXXX
05/033/2018 17:33:51 - INFO - ...
05/033/2018 17:33:51 - INFO - FAILED (remote: Command did not succeed)
05/033/2018 17:33:51 - INFO - finished. total time: 0.032s
05/033/2018 17:33:51 - WARN - Maybe the OEM is not enabled
05/033/2018 17:33:58 - INFO - Device disconnected
05/033/2018 17:33:58 - INFO - Device connected in fastboot mode
05/034/2018 17:34:07 - INFO - Device disconnected
I give up ! Tried almost everything (Win7x32, Win8.1x64, Flashtool v0.9.25 & 0.9.23 with ulcode.txt file created in user profile, Ubuntu, adb/fastboot command, from simple package, or Android studio), without any success. Some feedback though about Flashtool :
> Much easier to use the Linux version. On Ubuntu 18.10, it just works out of the box. I can easily flash the latest firmware ("Customized FR" in my case) though I downloaded it with Xperifirm on windows, as I did want to install mono on my Ubuntu desktop. At least I am now running Android 6.0.1.
> With version 0.9.25, I can use UBL button, Flashtool asks first for connect device in Flashboot mode (green light), then asks to disconnect and reconnect in Fastboot mode (blue But same error at the end : FAILED (remote: Command did not succeed). After a reboot, I can see "Rooting status : Unknown" in the service page.
> If I reflash, unknown rooting status is still there. I have to use Flashtool 0.9.23.2 (found link on another xda thread, only for windows) to "relock" the device and get back the "Bootloader unlock allowed : yes".
I don't understand what happens, what is the reason for that... Total mystery to me. There are so many posts about this issue, no one gives a real solution, Sony support does not care.
I am sad to be unable to install LineageOS on my device... Now will look how to "clean" Xperia Android as much as possible. Don't know if this is even possible. Don't know if I can root my phone, etc...
Last, why did I buy a Sony Z5C ? was looking for small (4.6") & afordable phone with good camera... Never thought I would be unable to install LineageOS.
That does sound frustrating. Have you checked the settings in the developer options? There's one there about "allow oem unlocking". If it's not set, you can't do it from fastboot, so maybe that's your problem? It's worth a try, at the very least.
tonsofquestions said:
That does sound frustrating. Have you checked the settings in the developer options? There's one there about "allow oem unlocking". If it's not set, you can't do it from fastboot, so maybe that's your problem? It's worth a try, at the very least.
Click to expand...
Click to collapse
Yes, I checked that for sure... Same for "Enable USB debug" and "Allow Unknown sources" in Security options.
Yesterday, as a last try, I follow that thread : I flashed old Lollipop firmware (E5823_32.0.A.6.200), backup TA partition, and tried unlock booloader again : same error FAILED (remote: Command did not succeed).
Probably something changed on Sony side that makes unlocking bootloader impossible ? That's what I think now.
Hmm, and in the service menu it says bootloader locking is allowed?
I'd be very surprised if Sony changed anything recently (if they even could, on a released phone), and I was able to do it successfully a few weeks back.
What's the error if you use an invalid unlock key? Maybe there's a typo (or request it from Sony again)? I know I'm grasping at straws, but I'm otherwise not sure. I had no difficulties at all...
tonsofquestions said:
Hmm, and in the service menu it says bootloader locking is allowed?
I'd be very surprised if Sony changed anything recently (if they even could, on a released phone), and I was able to do it successfully a few weeks back.
What's the error if you use an invalid unlock key? Maybe there's a typo (or request it from Sony again)? I know I'm grasping at straws, but I'm otherwise not sure. I had no difficulties at all...
Click to expand...
Click to collapse
Yes, Bootloader is OK, and providing a invalid unlock results in the same error : FAILED (remote: Command did not succeed).
From Sony website, you always get the same number when providing your EMEI.
Note there tones of threads about this issue, and really no clear solution, at least none from what I tried...
hi man!. Have you figure out how to unlock the bootloader? Same situation over here. This is my 3th xperia but first time facing this issue. Tomorrow I will install win 7 and will see if works
minos_cr said:
hi man!. Have you figure out how to unlock the bootloader? Same situation over here. This is my 3th xperia but first time facing this issue. Tomorrow I will install win 7 and will see if works
Click to expand...
Click to collapse
Unfortunately no. It is still the same, and I gave up for now, as I tried everything I could.
But I have a last plan : my Z5C is now running Android 6.0.1, which I installed myself using Flashtool & Xperifirm. Actually I got that phone with Android 5.1.1, and no upgrade was available when looking at system parameters, or even the Sony website). So I did it myself, using last package for French in Xperifirm.
And now, when looking at http://www.sonymobile.com/update, providing my EMIE code, it says my phone is up to date and running Android 7.1, which is wrong.
So I contacted Sony support for that, and they asked me to run a System -> Factory settings -> ReInit -> Clear everything. (or something simmilar).
I did not do it, because I am pretty sure this will not work, and I will probably go back to Android 5.1.1.
But I may contact the repair service (http://support.sonymobile.com/fr/repair/) and send my phone back to them asking for Android 7.1. I can complain for that, because my warranty is still valid !
My last hope is that when I will get back the phone from them, totally reinitialized, unlocking may work !!
I cannot do it for now, because I am going to move the next 2 months, but will try this when I am back. As I said, this is my last hope, unless someone find a solution to that problem.
Good luck to you, and keep us informed... By the way, which Android version are you running, and what says the Sony update site ?
man, yesterday I was frustrated too. Today, I installed windows 7 (it was a pain in the a**) and flashtool did the job like a champ.
pled said:
Unfortunately no. It is still the same, and I gave up for now, as I tried everything I could.
But I have a last plan : my Z5C is now running Android 6.0.1, which I installed myself using Flashtool & Xperifirm. Actually I got that phone with Android 5.1.1, and no upgrade was available when looking at system parameters, or even the Sony website). So I did it myself, using last package for French in Xperifirm.
And now, when looking at http://www.sonymobile.com/update, providing my EMIE code, it says my phone is up to date and running Android 7.1, which is wrong.
So I contacted Sony support for that, and they asked me to run a System -> Factory settings -> ReInit -> Clear everything. (or something simmilar).
I did not do it, because I am pretty sure this will not work, and I will probably go back to Android 5.1.1.
But I may contact the repair service (http://support.sonymobile.com/fr/repair/) and send my phone back to them asking for Android 7.1. I can complain for that, because my warranty is still valid !
My last hope is that when I will get back the phone from them, totally reinitialized, unlocking may work !!
I cannot do it for now, because I am going to move the next 2 months, but will try this when I am back. As I said, this is my last hope, unless someone find a solution to that problem.
Good luck to you, and keep us informed... By the way, which Android version are you running, and what says the Sony update site ?
Click to expand...
Click to collapse
I imagine (but can't say for certain) that whatever check Sony is using to display that info is either the last version that "called home" (maybe it needs the Xperia Companion software?), or the latest version that the phone was ever updated to. If you flash an old one with Flashtool (or worse: never connect to the internet with it), how on earth would you expect them to know the right version? Why would it even matter? The OS version is (largely) unrelated to the fastboot version, and shouldn't affect unlocking, other than the "allow oem unlocking" option in the developer settings.
I agree that the factory reset will leave it on the same OS; there's no reason it would upgrade.. I'm not sure why the OS wouldn't show updates available, maybe that customization version never had more releases. But is there any reason not to just download it and flash with Flashtool?
I couldn't find any other threads with people reporting problems - the majority of reports I saw were of successes. Not that I don't believe what you're seeing, mind you, just that I know there have been a lot of people getting things to work without a lot of issues.
minos_cr said:
man, yesterday I was frustrated too. Today, I installed windows 7 (it was a pain in the a**) and flashtool did the job like a champ.
Click to expand...
Click to collapse
Would be happy to know which Win7 (x32 or x64) and which flashtool version you used. Also if you setup the ulcode.txt file ?
---------- Post added at 09:59 AM ---------- Previous post was at 09:40 AM ----------
tonsofquestions said:
I imagine (but can't say for certain) that whatever check Sony is using to display that info is either the last version that "called home" (maybe it needs the Xperia Companion software?), or the latest version that the phone was ever updated to. If you flash an old one with Flashtool (or worse: never connect to the internet with it), how on earth would you expect them to know the right version? Why would it even matter? The OS version is (largely) unrelated to the fastboot version, and shouldn't affect unlocking, other than the "allow oem unlocking" option in the developer settings.
I agree that the factory reset will leave it on the same OS; there's no reason it would upgrade.. I'm not sure why the OS wouldn't show updates available, maybe that customization version never had more releases. But is there any reason not to just download it and flash with Flashtool?
I couldn't find any other threads with people reporting problems - the majority of reports I saw were of successes. Not that I don't believe what you're seeing, mind you, just that I know there have been a lot of people getting things to work without a lot of issues.
Click to expand...
Click to collapse
Well, this is a mystery to me. What I can say is that Sony website displays now :
Votre Xperia Z5 Compact est à jour !
Sortie : 32.2.A.5.11
Informations sur mon Android™
Android™ 7.1 Nougat est publié pour Xperia Z5 Compact.
Initially, I got the phone with Version 32.0.A.6.200. So they know somewhere I did an upgrade.
I would be happy to download the 7.1 version, but using Xperifirm, the only one I can find for the French country is the one I got, resulting in Android 6.0.1.
And because I have no knowledge at all on Sony specific things, I did try another firmware : I don't want to brick my phone.
Honestly, I have tried everything I could (Linux, Win, adb, flshtool, x32, x64, ulcode.txt, etc...) will always the same error, despite I agree most of people appears to success at one time. But most of the time without any clear explanation of what happen ! (except ulcode file story).
I read somewhere my problem could be related to the "Customization Version" (1299-1743_R12C in my case). Don't even understand what it could be related to, and how to change it.
What I expect is that Sony repair service will wipe everything on my phone, so that I could unlock it after it that.
Would be happy to know which Win7 (x32 or x64) and which flashtool version you used. Also if you setup the ulcode.txt file ?
Click to expand...
Click to collapse
I've personally used both Windows 10 (x64) and Linux. I used the latest version of Flashtool (0.9.25.0) and 0.9.24.4, though I couldn't tell you which combination I used on which OS.
[OS woes]
Let's start from the beginning. What OS are you trying to get to. Why?
Also note that there are multiple download versions in XperiFirm for your 1299-1743, make sure you're taking the right one.
I see 32.2.A.5.11, which it looks like you have (according to the earlier screenshot), which should be Marshmallow.
I also see 32.4.A.1.54, which should be Nougat.
Either should be straightforward to install with FlashTool (it sounds like you installed 5.11 with it?).
In the end, the customization option is mostly some regional differences - language, built-in apps, some VoLTE/fingerprint options for some regions, etc. Nothing significant ... or important if all you want to do is unlock it. That should be completely independent of the OS version.
Downgraing your OS and unlocking the bootloader should both end up resetting your phone/wipe the data.
So you should back up anything you want, and then mess around from there. I also fear the Sony Repair will wipe data, but it s also called "repair" so maybe it will backup/restore some of it. I'm not sure.
It's also possible that something is wonky with the OEM unlock setting, so wiping data will kick it back into working. It can't hurt to try, and is certainly easier than sending in a phone...
tonsofquestions said:
So you should back up anything you want, and then mess around from there. I also fear the Sony Repair will wipe data, but it s also called "repair" so maybe it will backup/restore some of it. I'm not sure.
It's also possible that something is wonky with the OEM unlock setting, so wiping data will kick it back into working. It can't hurt to try, and is certainly easier than sending in a phone...
Click to expand...
Click to collapse
Thank you for your advice. Will try again from scratch when I am back from travelling : 2 months in Asia ! At least, I will benefit of the "panorama" feature from the Sony camera that I may lose with LineageOS !
Hi all,
Wishing you all a happy New Year in arrears and the very best for the next 12 months.
I've got a problem with my device, its a STF-AL10 model with international rom bought during the November Sales.
It came with STF-L09C432B150 installed, I got the bootloader unlocked, TWRP installed and rooted with Magisk and was working fine except the capacitive buttons.
I thought I could live without capacitive buttons but I didn't work out and I had the urge to find a solution. After some intensive reseach (48hrs on a weekend in my 'lab') it seems the B120 firmware had no issues with the capacitive buttons, so I tried to downgrade to that and thats when the problems started.
Coming from an ancient Sony Z2, I never had issues flashing ROMS, Kernels and the sort as it was almost always easily done in TWRP or CWM (I had a Multi boot thing going, so I chose which recovery I fancied!). Anyway this are my issues now:
- Obviously, my phone was rebranded at origin as I know for sure AL-10 is not for EU market
- I tried restoring the same STF-L09C432B150 (rollback package found on XDA) with DC-Unlocker (wasted 19 Euro) but did not work. Always stops at 5% near end of flashing.
- Tried B130. same error.
- Tried Chinese STF-AL10C00B110. Same error.
- Tried full board flash for STF-AL10 with all DC Phoenix files. Same error.
- Tried forced method with files on a Sandisk SDcard (64GB) formatted to exFAT. Fails, wrong files.
- I noticed that in ADB, it said my bootloader was unlocked but FRP locked.
- After board flash, ADB said Bootloader unlocked (nothing about FRP) but in Muli-tool it says LOCKED.
- Now all ADB commands the write to the phone give errors.
DC-unlocker support keep on saying I should use the correct firmware for my phone, ok but the phone was rebranded at source...do use a Chinese firmware first then update ?
in desperation I did another full board flash but this time I think I wiped oeminfo and Vendor partions. ( I think this is what caused the HARD-BRICK!). Now no Honor logo, no Recovery, No eRecovery, nothing but a blank black screen. ADB still works but no status about bootloader or FRP.
IMEI has changed to 0123456789ABCDEF
You can all laugh and shake your heads which I will take as my punishment but is there a solution to all this, I'm willing to pay another 19 EUR for DC-Phoenix if it helps to fix my phone and if possible get it rooted with all buttons and functions working. That was my intension all along (I'm not really interested in custom Roms, just root access!).
HCU tool for some reason does not install on my computer, and besides, the phone does not boot into an OS to be able to change OEM and VENDOR data.
I even tried the HOTA.zip in the ReBRAND HONOR 9 thread but the file is missing (link down).
And to top it all there is no UK service center.
Please advise...
I think DC unlock is not supported for thì this model. Did Did you try Huawei Funky???
Apparently all versions of Honor 9 are supported by DC-unlocker and DC-Pheonix....
ums1405 said:
Hi all,
Wishing you all a happy New Year in arrears and the very best for the next 12 months.
I've got a problem with my device, its a STF-AL10 model with international rom bought during the November Sales.
It came with STF-L09C432B150 installed, I got the bootloader unlocked, TWRP installed and rooted with Magisk and was working fine except the capacitive buttons.
I thought I could live without capacitive buttons but I didn't work out and I had the urge to find a solution. After some intensive reseach (48hrs on a weekend in my 'lab') it seems the B120 firmware had no issues with the capacitive buttons, so I tried to downgrade to that and thats when the problems started.
Coming from an ancient Sony Z2, I never had issues flashing ROMS, Kernels and the sort as it was almost always easily done in TWRP or CWM (I had a Multi boot thing going, so I chose which recovery I fancied!). Anyway this are my issues now:
- Obviously, my phone was rebranded at origin as I know for sure AL-10 is not for EU market
- I tried restoring the same STF-L09C432B150 (rollback package found on XDA) with DC-Unlocker (wasted 19 Euro) but did not work. Always stops at 5% near end of flashing.
- Tried B130. same error.
- Tried Chinese STF-AL10C00B110. Same error.
- Tried full board flash for STF-AL10 with all DC Phoenix files. Same error.
- Tried forced method with files on a Sandisk SDcard (64GB) formatted to exFAT. Fails, wrong files.
- I noticed that in ADB, it said my bootloader was unlocked but FRP locked.
- After board flash, ADB said Bootloader unlocked (nothing about FRP) but in Muli-tool it says LOCKED.
- Now all ADB commands the write to the phone give errors.
DC-unlocker support keep on saying I should use the correct firmware for my phone, ok but the phone was rebranded at source...do use a Chinese firmware first then update ?
in desperation I did another full board flash but this time I think I wiped oeminfo and Vendor partions. ( I think this is what caused the HARD-BRICK!). Now no Honor logo, no Recovery, No eRecovery, nothing but a blank black screen. ADB still works but no status about bootloader or FRP.
IMEI has changed to 0123456789ABCDEF
You can all laugh and shake your heads which I will take as my punishment but is there a solution to all this, I'm willing to pay another 19 EUR for DC-Phoenix if it helps to fix my phone and if possible get it rooted with all buttons and functions working. That was my intension all along (I'm not really interested in custom Roms, just root access!).
HCU tool for some reason does not install on my computer, and besides, the phone does not boot into an OS to be able to change OEM and VENDOR data.
I even tried the HOTA.zip in the ReBRAND HONOR 9 thread but the file is missing (link down).
And to top it all there is no UK service center.
Please advise...
Click to expand...
Click to collapse
Try stock service B130 firmware:
https://forum.xda-developers.com/honor-9/how-to/stf-l09c432b130-capacitive-buttons-100-t3729106
Instead of step 4 do forced upload: VOLUME UP + VOLUME DOWN + POWER
Hi,
I've managed to re flash b150. In doing so I got back recovery and erecovery but when you reach that final stage of the process the phone stops at 5%. When I reboot to recovery, factory reset stops at 35%
Any ideas
?
Sent from my [device_name] using XDA-Developers Legacy app
ADB now showing BOOTLOAD UNLOCKED but there is no FRP status.
Sent from my [device_name] using XDA-Developers Legacy app
ums1405 said:
ADB now showing BOOTLOAD UNLOCKED but there is no FRP status.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
FRP status is not only on Chinese phones
you need to sew firmware for al10
The phone was rebounded by the shop I bought it from.
It said STF-L09B150 indexical info when the phone was working.
So if I'm going to repair this brick what update files should I use?
Original Chinese or the b150 used when rebranded?
Sent from my [device_name] using XDA-Developers Legacy app
Hi all,
FYI, I've sent the phone back to the shop I bought it from.
I'll take my chances, better than paying money for something that may not work.
Thanks everyone for showing interest in my situation, I let you all know how I get along with this issue.
Ps.: As a community, lets push Huawei/Honor to release Kernel Sources for this model and others like the P10 Plus.
Ps: Huawei/Honor have to realise that a strong developer community adds value and desirability to a product. That's how a product becomes 'Cool' translating into more revenue/customers/profit - eg OnePlus.
.
Hi all, a quick update .....
Sent the phone back and from what I gather the phone actually had an issue with the main board.
Now enjoying a brand new MATE 10 (Non-pro with 6/128gb) in beautiful Obsidian black.
Wonderful.
Back in december/january some users reported a glitch while rebranding STF-AL10 to STF-L09 with the old nougat hwota (at oem bin flashing step).
After editing hwota script, then rebranded : they ended with a FRP locked status.
Their only way to unlock frp was with dcunlocker or funkyhuawei I don't remember.
After frp unlocked, their bootloader wasn't seen through fastboot.
I think this could be solved by regedit a value in registry.
To my knowledge the only public firmware files working with the dload way (3 buttons + usb connected) are the one titled "service repair", the others one won't work dload as they are. They are for hwota or forcing "official" ota.
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
Motorola G4 XT1625
Minor Problem: Phone will not start normally, only boots into Fastboot mode.
Minor Problem: Phone is oem Locked
Major Problem: I never went into "settings" on the phone and ENABLED OEM UNLOCKING.
Question: Is it possible to get this phone flashed with stock ROM?
A little background. Not a developer, phone started acting up a few days ago, shutting down or rebooting on its own, do not remember anything such as an update or my clearing of the cache occurring in that time frame, but I was still hoping it was a software issue that would work itself out. Now the phone fails during start up and reports this
STARTUP FAILED
ERROR: Failed to pass validation , backup to fastboot.
It does mention I should use Software Repair Assistant to recover the phone, which correct me if I'm wrong , only works with Verizon phones. I did try the SRA, it connected to the phone, but would stall about halfway through.
I have found much info on this forum regarding unlocking the bootloader of this phone, I have installed on Moto tools on my PC, requested and received an unlock code, connected to the phone and can send commands via command line. Unfortunately when I send the oem unlock the phone responds that I need to enable development mode in settings, which I cannot get to because the phone wont boot to the OS. Is there an easy way around this that I'm just not seeing?
In the end the problem may be hardware related, I just hate to give up on it so easily. Contacted Motorola about the device, as it turns out the unit was 6 days out of warranty ( that's if you use the Amazon ship date, it was only actually 2 days out if you use the activation date). Their response was as expected, sorry can't help you, thanks for being a Motorola customer, have wonderful day, next........
MSC 1/24/18