Installing the new Sony Bootloader and Recovery
THIS IS FOR ALREADY UNLOCKED DEVICES!
DO NOT TRY THIS ON A GPE!Since a lot of people seem to have problems keeping their recovery when flashing Lollipop-ROMs i decided to put up this little guide...
You can also Skip this whole guide, by just flashing the newest stock-FW at least once!
First off, as already said, this is for already unlocked devices. You can use this Guide until "Install Custom ROM", except the rooting part, for rooting use this, if you haven't already!
Don't do it if you don't atleast somewhat know what you are doing.
I am not responsible for bricked devices, or whatever you might end up with.
So, lets get started.
1. Download Sonys FlashTool "EMMA" and install it: http://developer.sonymobile.com/downloads/tool/flash-tool-for-xperia-devices/
In the .zip file from the FlashTool you'll find a File "customization.ini"
Copy this file to the installation directory of EMMA, usually "C:\Program Files (x86)\Sony Mobile\Emma"
If you don't copy that file, Emma will ask you for a login, don't create an account there, you will NEVER get any activation-email!
2. Open EMMA and boot your Phone into FlashMode (Power off your device -> Press and hold volume DOWN -> while pressing volume DOWN insert USB-Cable)
3. Emma should now recognize your device, but you have to select it manually tough. Select your EXACT model number. Again, I am not responsible for any bricked devices or whatever you end up with!
Now select the "(Open Devices) TA update" and click "Apply Service"
It should take a few seconds and should then display SUCCESS.
You can now close Emma
4. If you haven't already download FastBoot and Drivers: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
(Run as Administrator!)
5. Download the newest version of twrp and put it somewhere:
New Inoffcial twrp-3.0.0 build by me: http://forum.xda-developers.com/xperia-z-ultra/development/togari-twrp-recovery-3-0-0-t3314440
Old official versions: https://twrp.me/devices/sonyxperiazultra.html
6. Finally boot up you Phone in FastBoot-mode (Power off -> press and hold volume UP -> while pressing wolume UP insert USB-Cable
Your LED should now light up blue
Shift+Rightklick in the Folder where you have put TWRP recovery, and select "Open Commandprompt here"
Now write "fastboot flash recovery FILENAME_OF_TWRP_FILE"
You can now unplug your USB-Cable and boot into recovery and continue from there.
Your recovery will be permanent, meaning you won't loose it or replace with any other recovery that might come with your ROM.
I hope this was somewhat helpfull
Any one can flash this to C6806?
jacklau2000 said:
Any one can flash this to C6806?
Click to expand...
Click to collapse
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
alia5 said:
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
Click to expand...
Click to collapse
tried, but no luck. thanks.
It's really weird, I used emma, and installed their latest ta update. Now I can get into fastboot mode, all commands execute successfully, but the recovery never takes. The vol down + Power doesn't work, nor does 'adb reboot recovery'. Am I missing a step somewhere? This isn't my first android device, but from where I sit, it seems like something is up with my xzu.
If I try and install the 14.4* update through emma, it goes through the whole process, completes "successfully", then boots into 14.5. Something is clearly not working here.
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
teddy74eva said:
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
Click to expand...
Click to collapse
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Hermann1222 said:
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Click to expand...
Click to collapse
I will try to compile one because, you know, summer holidays and no school however I don't know if I will make it.
Regards
Is there any (wish for TWRP) recovery for togari, which use the new bootoader?
FYI:
My device is a brazilian c6843.
Emma recognizes the device automatically and indicates with an exclamation point that there is no services available to the unit.
In the case someone doesn't know, it's basically the c6833 with DTV 1seg. It's totally compatible with c6833 firmware, losing TV, of course.
You sir are the real hero! Thank you!
I have a xzu running cm12.1, and I have 2 quick questions for those with more knowledge than me
Is it possible to flash the new bootloder using the open source FlashTool?
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
pbgapski said:
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
Click to expand...
Click to collapse
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
missing clues on new recovery partition
alia5 said:
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
Click to expand...
Click to collapse
I followed your advice, but it seems I am missing a few clues.
My sirius was on cm12.1. I backedup and flashed D6543_23.4.A.1.232_1281-5466_R6C.ftf with flashtool on linux. I tried to use emma (several times) afterwards to check for any TA updates, but all I got was "no services matched this device" or something like that. Google tells me I am not the only one with this issue with emma
Then I used fastboot to install twrp 3 from twrp.me to recovery partition, but I could not access twrp.
I fastbooted recovery again with twrp 2.8.7, and this time I could enter twrp and reflashed CM.
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
pbgapski said:
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
Click to expand...
Click to collapse
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
why it said my phone have no available service, i am on c6833
alia5 said:
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
Click to expand...
Click to collapse
I have the same problem but not bootloop just stuck at starting apps screen,BTW did you have a TWRP scripts for flashing TWRP 3.0 into FOTAkernel
hi .. after this update can i relock my phone and restore drm functions?! or phone go to unlocked forever?!
pls help i need answer
erfanzz said:
pls help i need answer
Click to expand...
Click to collapse
Search the forums on how to backup TA partitions. I have mine but never tried to restore them
Related
Hi, everyone, I just got my z3 tablet and I am in love with it except i don't like the interface. So i decide to root my tablet without unlocking the bolted and I did made it and i did install TWRP. I have a question, since I have TWRP is it possible for me to install cm 12 rom or I need to have a unlock boot loader in order to install it?
Sorry for my bad english and thank you for answering my questions.
kokorolove said:
Hi, everyone, I just got my z3 tablet and I am in love with it except i don't like the interface. So i decide to root my tablet without unlocking the bolted and I did made it and i did install TWRP. I have a question, since I have TWRP is it possible for me to install cm 12 rom or I need to have a unlock boot loader in order to install it?
Sorry for my bad english and thank you for answering my questions.
Click to expand...
Click to collapse
You need to unlock to flash a custom kernel which would be needed by the cm12 to run. So first.
1.Backup drm keys
2.Unlock BL
3. Flash CM kernel via fastboot
4. Flash CM Rom via recovery.
Sent from my SGP621 using XDA Free mobile app
I just bought a Z3 tablet compact, which should be here at the end of next week. I haven’t found a tutorial which includes all steps to get from the standard rom to CM12. Did I miss any steps or does the following steps include everything?
Root tablet on the original Sony rom
Backup TA partition (I guess that's where the DRM keys are?)
Unlock bootloader
Flash a recovery (any recommendations?) I found this tutorial, but I only need one recovery and I don’t want to flash that zip every time I install a new rom.
Flash CM12. Are there any kernels beside that one included in the CM12 zips?
Cyberratchet said:
I just bought a Z3 tablet compact, which should be here at the end of next week. I haven’t found a tutorial which includes all steps to get from the standard rom to CM12. Did I miss any steps or does the following steps include everything?
Root tablet on the original Sony rom
Backup TA partition (I guess that's where the DRM keys are?)
Unlock bootloader
Flash a recovery (any recommendations?) I found this tutorial, but I only need one recovery and I don’t want to flash that zip every time I install a new rom.
Flash CM12. Are there any kernels beside that one included in the CM12 zips?
Click to expand...
Click to collapse
I guess you should just flash the kernel via fastboot after unlocking the bootloader, that would eliminate the need to flash a recovery. It's hitting 2 birds and one stone and besides CM uses a different kernel than stock so later you would really need to flash kernel.
Sent from my SGP621 using XDA Free mobile app
Thanks for your reply. The whole flashing procedure is a lot more complicated than on my S3, so I have a follow-up question.
Should I just backup the TA partition, unlock the tablet, flash this kernel which should give me root and TWRP and then flash another recovery and CM12?
I found this recovery which is only semi-permanent, because you have to flash it before you upgrade/install a new CM12 version. It’s not big deal tbh, but is there a permanent recovery, which I only have to install once.
I'm also curious about this.
Right now, I'm trying to download the Flashtool program from Sony, but apparently, you need to "register" for it. Where did you guys download your Flashtool from?
Cyberratchet said:
Thanks for your reply. The whole flashing procedure is a lot more complicated than on my S3, so I have a follow-up question.
Should I just backup the TA partition, unlock the tablet, flash this kernel which should give me root and TWRP and then flash another recovery and CM12?
I found this recovery which is only semi-permanent, because you have to flash it before you upgrade/install a new CM12 version. It’s not big deal tbh, but is there a permanent recovery, which I only have to install once.
Click to expand...
Click to collapse
Correct, make sure the kernel is compatible with CM
Sent from my SGP621 using XDA Free mobile app
The whole procedure is really frustrating, maybe someone can help me here.
I did a backup of the TA partition and unlocked the bootloader. I tried flashing the boot.img from the cm.zip, but I have no idea how to flash the rom via the cm-recovery.
Flashing the advanced kernel to get TWRP wasn’t successful as well. I tried the fastboot mode of the Flashtool and flashed the kernel, but nothing changed.
Can someone post a brief guide with the next steps to get CM12 running (with cmd commands pls)?
EDIT: I just tried to use “adb sideload” in the CM recover, but “adb devices” doesn’t show the tablet .
EDIT2: EDIT: Seems like I got it to work after all. The DualRecover Installer worked, even without SuperSU installed.
Cyberratchet said:
The whole procedure is really frustrating, maybe someone can help me here.
I did a backup of the TA partition and unlocked the bootloader. I tried flashing the boot.img from the cm.zip, but I have no idea how to flash the rom via the cm-recovery.
Flashing the advanced kernel to get TWRP wasn’t successful as well. I tried the fastboot mode of the Flashtool and flashed the kernel, but nothing changed.
Can someone post a brief guide with the next steps to get CM12 running (with cmd commands pls)?
EDIT: I just tried to use “adb sideload” in the CM recover, but “adb devices” doesn’t show the tablet .
EDIT2: EDIT: Seems like I got it to work after all. The DualRecover Installer worked, even without SuperSU installed.
Click to expand...
Click to collapse
I ran into the same problem usin the cm12 nightlies from 27th march 2015:
Sideloading would not work because the tablet is not recognized by the computer. I tried with Windows 7 and gentoo Linux.
Installing from the sd-card in recovery mode was also not possible due to a error of missing "/misc".
I solved the problem by manually choosing the driver in Windows 7. I booted the tablet into recovery. Choose update using adb as detailed in this post:
http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534
Then I found the device in the windows device manager. Here I manually choose the adb driver that I installed earlier from the flashtool package. After that the device was correctly recognized by Windows and I could Sideloade the cm12 image.
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
joaomPT said:
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
Click to expand...
Click to collapse
As you are already familiar with adb and other stuff so will write a short post for you.
To download latest firmware, head to
http://forum.xda-developers.com/hon...tock-firmware-packages-honor-7-t3448747/page1
Google, download and install Huawei update extractor and open UPDATE.APP in it (obtained after extracting firmware).
You can see all the images. Just extract recovery and boot to platform-tools folder.
Meantime, do the unlocking command again, with
Fastboot OEM unlock xxxxxxxxxxxxxxxx
Followed by fastboot reboot
And press and hold the vol down button again until you reboot in bootloader.
Flash the recovery and boot you extracted using
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
(I got a habit of extracting and flashing system and Cust using
Fastboot flash system system.img
Fastboot flash Cust Cust.img
But they are not necessary)
Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again).
Please do report back if it comes to life.
To root, just flash twrp and then use SuperSU 2.62 (no other version) and update it later using play store.
Sent from my PLK-L01 using XDA Labs
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
joaomPT said:
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
Click to expand...
Click to collapse
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
muradulislam said:
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
joaomPT said:
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
Click to expand...
Click to collapse
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
muradulislam said:
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said » version 2.62 «
I cant thank you enough!! Can I pay you a coffee?
Thank you!
joaomPT said:
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said �?�» version 2.62 �?�«
I cant thank you enough!! Can I pay you a coffee?
Thank you!
Click to expand...
Click to collapse
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
You can find him somewhere in this thread
http://forum.xda-developers.com/honor-5x/help/honor-5x-kiw-ul00-boot-loop-t3449554/page1
Decision is yours
muradulislam said:
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
Whichever you like...
Click to expand...
Click to collapse
Alright man, cheers
joaomPT said:
Alright man, cheers
Click to expand...
Click to collapse
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
joaomPT said:
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
Click to expand...
Click to collapse
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
tgergo said:
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
Click to expand...
Click to collapse
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
I'll try... But seems too simple to be true...
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
Hi again,
I'm doing this OS installation now. It starts fine but stucks at 90%, (I'm trying to install the latest stock ROM which can be downloaded from Huawei site, B220 or221). Did you have the same issue? I waited more than half an hour at 90% but did not go on.
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Maybe formatting, Flash stock Android 5 recovery using Honor multitool , and then Flash a Android 5 firmware
Not sure it Will Work without rollback..
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
tgergo said:
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
Click to expand...
Click to collapse
Is this really work? i cant rollback to any version.
Yuaru said:
Is this really work? i cant rollback to any version.
Click to expand...
Click to collapse
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
tgergo said:
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
Click to expand...
Click to collapse
Thanks for the answer. Im gonna try this method. I can't reflash any region rom.
Hello,
I started on a quest last week to try and make my long forgotten Xperia tablet z LTE SGP321 more user friendly.
I stopped using it after being frustrated by the bloatware and its lack of customisation.
So I thought flashing a custom rom might help and wanted a bit of a technological challenge. Boy do I feel like I've got one.
I used kingroot, which worked fine. I tried to install SuperSu but it wont update the binaries.
I've managed to unlock the bootloader (forgot to do the backup TA woops!).
I downloaded TWRP app, flashed pollux_windy to recovery. Now there doesn't seem to be a combination of keys that I can find to boot the sony xperia tablet Z into recovery?? Power and volume up or down or jamming both keys...nothing seems to work. I've found one forum post suggesting it isnt possible and that I need to flash a kernel which is where I'm getting stuck.
SO this is where I am now and was wondering if I should use CWM instead or if there is another way to open recovery?
My main aim is to completely clear the tablet hard drive and start again with a custom rom.
Thanks!
>>>>>>
NEW info
So i've managed to use the ADB to reboot into the boatloader. All that happens is a black screen. I want to try and flash CWM or TWRM but it doesnt seem to work.
Im beginning to think there's something strange about the sony xperia tablet z in that it doesnt have a bootloader in its stock firmware. i've seen something about using a Kernel approach but the guides are unclear.
Any help on flashing a CWM or TWRM into recovery would be much appreciated!!
harpix42 said:
Hello,
I started on a quest last week to try and make my long forgotten Xperia tablet z LTE SGP321 more user friendly.
I stopped using it after being frustrated by the bloatware and its lack of customisation.
So I thought flashing a custom rom might help and wanted a bit of a technological challenge. Boy do I feel like I've got one.
I used kingroot, which worked fine. I tried to install SuperSu but it wont update the binaries.
I've managed to unlock the bootloader (forgot to do the backup TA woops!).
I downloaded TWRP app, flashed pollux_windy to recovery. Now there doesn't seem to be a combination of keys that I can find to boot the sony xperia tablet Z into recovery?? Power and volume up or down or jamming both keys...nothing seems to work. I've found one forum post suggesting it isnt possible and that I need to flash a kernel which is where I'm getting stuck.
SO this is where I am now and was wondering if I should use CWM instead or if there is another way to open recovery?
My main aim is to completely clear the tablet hard drive and start again with a custom rom.
Thanks!
>>>>>>
NEW info
So i've managed to use the ADB to reboot into the boatloader. All that happens is a black screen. I want to try and flash CWM or TWRM but it doesnt seem to work.
Im beginning to think there's something strange about the sony xperia tablet z in that it doesnt have a bootloader in its stock firmware. i've seen something about using a Kernel approach but the guides are unclear.
Any help on flashing a CWM or TWRM into recovery would be much appreciated!!
Click to expand...
Click to collapse
Flash boot.img of any latest custom ROM with TWRP integrated.
Rootk1t said:
Flash boot.img of any latest custom ROM with TWRP integrated.
Click to expand...
Click to collapse
Thanks for your help. I thought I'd start simple and just try and flash TWRP to recovery.
i downloaded the latest TWRP pollux windy img and then used the command fastboot flash recovery twrp.img
It says FAILED (remote: command not allowed)
adb fastboot devices displays my tablet
(by the way in configuration in service info it says bootloader unlocked: Yes)
>>>>>>UPDATE
so i managed to flash a cyanogenmod img using "fastboot flash boot boot.img"
The device then soft bricked and went into a boot loop. Is this because I used the wrong version of cyanogenmod?? Any other I can try that work?
I panicked a bit, mamanged to get the tablet into fastboot somehow andthen flashed a TWRM img to the boot using the same command above which now loads TWRM.
fastboot reboot now caused the device to go into TWRP but its in recovery mood
How can i undo that step i did when I flashed the boot img of the cyanogen mod. I want to put the old boot.img back!
Rootk1t said:
Flash boot.img of any latest custom ROM with TWRP integrated.
Click to expand...
Click to collapse
also can I ask another quick question of you, what do you do to boot into recovery on your xperia tablet Z device?
Thanks!
Sorry about all the updates.
I decided to see what you had installed on your signature and tried resurrection remix. Version 5.8 caused Error 7??
So i went for version 6.9 which i installed successfully.
Only way i know how to get into recovery is to use adb terminal command "adb reboot recovery"
Also before I installed resurrection remix would you recommend a complete wipe of everything or does it not really matter?
Thanks and hopefully that's me all sorted!
Use VOL+ or VOL- on boot to enter recovery.
harpix42 said:
what do you do to boot into recovery on your xperia tablet Z device?
Click to expand...
Click to collapse
2 way for me:
- usually you can set an "advanced reboot menu" under developer option or the ROM customization panel (depends on which ROM do you use)
- turn off your tablet, now push the power button until your screen just turn on, leave the power button and start pressing vol+ and vol- alternately until you boot into recovery
Updated for more serious reference. Hope this info helps you!
Procedure:
Once you have updated to Nougat, you would have to unlock your bootloader
The APK that unlock the bootloader works (Even though is marked as M version). (Remember that this will wipe your device!) For ULBL -> Version UnlockTool_2017_0803(android M) (FROM ASUS) https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_Download/
Zenfone will reboot and you will able to see a new splash screen that informs you that your device is unlocked giving you boot options Don't press anything. (You will see this everytime you reboot). The next screen will show an erase process. Phone will reboot.
Once booted enable developer options and adb via usb.
You can find TWRP builds right here: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w (Special thanks to: @shakalaca) Use the latest one.
Go to fastboot mode and install TWRP. (fastboot flash recovery (nameoffile).img)
Let fastboot do it's magic, once you finish press volume buttons till you find reboot recovery press power button to select. It will boot again to the first splash. Do not press anything, let it work. It will boot TWRP in a whistle.
Once in TWRP make a backup. You know it's necessary, and will save your ass in case of a softbrick.
Flash latest magisk (Current Ver: 13.3) Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot, check drawer for magisk manager, magisk and root should be enabled.
Voila. Safetynet test passed :good:
what version was twrp are you using and what steps did you take to get magisk to work.
smariob said:
So today finally I got my Asus Zenfone 3 Zoom. I couldn't contain myself to start playing with it.
My very first surprise was that the phone requested for an update. I've done it. I ended with a stock 7.1.1 AZ3Z.
This is my experience:
The APK that let you unlock bootloader works. (Remember that this will wipe your device)
After auto reboot I cheched safetynet. At this point test failed (Little bit obvious)
I was able to go to fastboot mode and install TWRP (The same you can find right here at the forum)
Let fastboot do it's magic, press volume buttons till you find reboot recovery. It will boot TWRP in a whistle.
Once in TWRP I made a backup. You know if necessary.
The next step was a crossfinger procedure. Just flashed latest magisk Beta (13)
Reboted checked for magisk manager on drawer.
It was there and root also. Enabled magiskhide, and voila. Safetynet test passed :good:
Hope this Info help you.
Click to expand...
Click to collapse
Do you know if this works with Android Pay?
magicmanfk said:
Do you know if this works with Android Pay?
Click to expand...
Click to collapse
It should work with it, im able to login intoy bank account with no problem with this method, I will give it a try for you though.
mr573162 said:
what version was twrp are you using and what steps did you take to get magisk to work.
Click to expand...
Click to collapse
magicmanfk said:
Do you know if this works with Android Pay?
Click to expand...
Click to collapse
It's twrp 3.1.0
It should work as it passes CTS profile and Basic Integrity I can't test it myself because I live in Mexico and Android Pay is not avialable here yet.
Will edit OP
Just a question as I'm having difficulty booting into TWRP.
My device is unlocked and when flashing TWRP using the command "fastboot flash recovery twrp.img" and trying to boot into it nothing happens other than my device going into the bootloader. I have tried flashing both the most recent TWRP 3.1.1 and 3.1.0 yet I keep on coming to the same problem. Can anyone provide help? thanks in advance.
GarGarStinks said:
Just a question as I'm having difficulty booting into TWRP.
My device is unlocked and when flashing TWRP using the command "fastboot flash recovery twrp.img" and trying to boot into it nothing happens other than my device going into the bootloader. I have tried flashing both the most recent TWRP 3.1.1 and 3.1.0 yet I keep on coming to the same problem. Can anyone provide help? thanks in advance.
Click to expand...
Click to collapse
Everytime you reboot the pone starts into boot loader. It has a countdown to boot into whatever is commanded.
Once you flashed succesfully the recovery img you just have to select option to boot recovery with vol keys and power.
Phone will reboot into bootloader agin let it boot on contdown (don't press any key)
Then it will boot into twrp.
Hello, on nougat i am trying to install the twrp, I downloaded the official bootloader release program (after installing the message "unlocked device") but trying to install the twrp via fastboot me by an error message. ... but I think the problem is the unlocking of the bootloader (if I turn the ze553kl in fastboot mode I see my device is "locked") ... there is another version of the bootloader release software? The one available on asus site would look for android M ... maybe there is one for Nougat? Thanxs
Wop. I used the M version apk on Nougat. It worked with no issues, the unlock of boot loader is successful when all the content of your smartphone is wiped.
For reference: https://www.youtube.com/watch?v=hg77b8o8Jk4 Min 1:29
Thank you! But running the software, does not run any wipe, it only displays an "unlocked" message without having to restart anything else. I also tried to make a "factory reset" and repeat lab process but the result does not change ...
TWRP tip!!
smariob said:
Go to fastboot mode and install TWRP. You can find TWRP and how to install it right here: https://forum.xda-developers.com/zenfone-3-zoom/how-to/twrp-zenfone-3-zoom-t3624551
:
Click to expand...
Click to collapse
If you follow that link and flash the recommended version, TWRP might load upside down and mirrored, impossible to use. I flashed the latest version from the MEGA link (3.1.1) and it was back to normal. Just a head's up for future reference, you might want to update your post.
---------- Post added at 09:39 PM ---------- Previous post was at 09:32 PM ----------
smariob said:
Go to fastboot mode and install TWRP. You can find TWRP and how to install it right here: https://forum.xda-developers.com/zenfone-3-zoom/how-to/twrp-zenfone-3-zoom-t3624551
:
Click to expand...
Click to collapse
If you follow that link and flash the recommended version, TWRP might load upside down and mirrored, impossible to use. I flashed the latest version from the MEGA link (3.1.1) and it was back to normal. Just a head's up for future reference, you might want to update your post.
Updated, never had mirror issues but is always better to have latest recovery.
Edit. Jimbo, I got an anwer from the source it notes: "please use 'fastboot flash recovery' instead of 'fastboot boot' to avoid up side down screen"
I've also tried installing from scratch with Asus flash tool, but I still can not unlock bootloader ... Anyone know if there is also an unofficial method for unlocking the bootloader?
@bizzino what model of Z3Z are you using?
Maybe Unlock bootloader app is intended for specific models... Let me do a little bit of research
Double posted... (Don't know for what reason this is happenning)
smariob said:
@bizzino what model of Z3Z are you using?
Maybe Unlock bootloader app is intended for specific models... Let me do a little bit of research
Click to expand...
Click to collapse
Ze553kl. WW_Z01H
bizzino said:
Ze553kl. WW_Z01H
Click to expand...
Click to collapse
Couldn't find another unlock tool than 2017_0803 ...
What info gives you fastboot mode?
smariob said:
Couldn't find another unlock tool than 2017_0803 ...
What info gives you fastboot mode?
Click to expand...
Click to collapse
Locked
Works just fine, thank you
But how would I go about setting the phone back to stock if needed in the future? (Removing Magisk, and replacing TWRP with the original recovery software).
@bizzino No news for you i wasn't able to find more info I'm sorry. Maybe change it for warranty? @subsector you should flash original recovery via fastboot and then sideload the stock rom
Back to Stock with @raystef66's Files
This guide used a method stemmed from paranoia. Now that we have decent flashable files everything is much simpler!
We'll be using raystef66's flashable TWRP files to go completely back to stock. At the end there's instructions if you want to lock your bootloader.
Be sure that you are on the latest TWRP version!
1) Files to Download:
- TWRP Flashable Bootstack/Stocksystem Image from here: Download Center. Download the latest BOOTSTACK and STOCKSYSTEM from there.
- If you want to lock the bootloader, also download the STOCK RECOVERY zip from the same stocksystem version that you downloaded. The flashable stock recovery zips are on the Factory Images Division, right above the TWRP flashable files.
- Magisk 15.2 (or latest), or SuperSU 2.79 (Latest not recommended ). If you will relock the bootloader, skip this part.
2) Installation
- Put all the files on the internal storage or SD card. Backup your important stuff from the internal storage, because you might need to format it!
- Go to TWRP. Wipe data, system and cache (don't format data though).
- Install the bootstack that you downloaded. Then install the stock system.
- If you will NOT relock the bootloader, install Magisk or SuperSU
- Reboot
If the phone asks for a password when it gets to the system, go to TWRP. It will ask for a password, just select Cancel. After you're on the main TWRP screen, select Wipe, then Format data, then type yes. After that, reboot.
3) 5 second screen removal / restore Fastboot
This is useful whether you're relocking the bootloader or not. Just go to raystef66's guide and follow it completely. After doing it your phone will have Fastboot (very good for softbricks and relocking), no 5 seconds screen (your phone will boot up faster) and it will be even closer to full stock.
4) ONLY FOR RELOCKING - Replace TWRP with Stock Recovery
Simply go to TWRP and flash the stock recovery file you downloaded. After that, enable OEM unlocking and USB debugging from the dev options, and then go to Fastboot and issue "fastboot oem lock".
@Choose an username... thanks for the credits.
you can return to stock in that way. you can reflash twrp with tool, allways checking bootloader still unlocked.
I allway update in this way, reboot to twrp, flash the recovery image, not a zip, its the same, but I make sure that the recovery correspond to the base version in my phone. after that, I reboot to system directly, update in the ota way, or the zip way, but from running android, rooted or not, and I dont have to wipe.
After update is done, the most important thing is leave the phone till it is completly booted, then you can reflash twrp with axon7tool again.
You dont need to root, you dont need anything to keep twrp. You only need to flash supersu or magisk if you use darkenfx zips. And if you do it, you have to backup wipe and restore cause you lose encryptation.
But thats all. I think stock rom its still the best, not in battery life, but in camera and bundled apps, It works perfectly, except, I have 2 bugs since allways, wake up with proximity sensor covered, and whatsapp online with app in background, I can live with that
I can re-lock bootloader after this process?
thanks for the guide.
Help Needed ! A2017g Bricked while trying to returning to stock
Hi, Please help me to get my Axon 7 in a working state. I was using Xenon HD Rom for A2017g Oreo. With twrp version as suggested in the guide.
I followed the procedure, installed the bootstack and then stock system B09
But when I tried to reboot, it said no OS Installed. Then I rebooted, and it was stuck at bootloader with no twrp and just the message as follows :
Android Recovery : ZTE/P996A04_N/ailsa_ii
7.1.1/NMF26V/20171120.101942
user/release-keys
Use volume up/down and power
and then certain other options in blue
Please help !
I also have a Problem.
I tried going back to stock from LOS 14.1. Now I am stuck on the 5 seconds screen, it won't continue.
The files I used were the Nougat B10 Files :-/
HansWursT619 said:
I also have a Problem.
I tried going back to stock from LOS 14.1. Now I am stuck on the 5 seconds screen, it won't continue.
The files I used were the Nougat B10 Files :-/
Click to expand...
Click to collapse
Enter the recovery, it should be the stock one (turn the phone off, then hold vol+ and power). Then download a stock B10 file (not the twrp flashable one) and install it from an SD card
No its not the stock one, its still TWRP.
I only flashed Bootstack and stock system (step 2). The reboot afterwards doesnt work
What do you mean by "a stock B10 file"? There are so many files types :-/
I am not quite sure what I should do now, do I have to do the EDL route? That one sounds confusing as well.
EDIT: I tried using B08 Files and now the reboot prompt in TWRP tells me there is no os installed.
Will I, like naveen09y, end up without TWRP if I reboot now?
HansWursT619 said:
No its not the stock one, its still TWRP.
I only flashed Bootstack and stock system (step 2). The reboot afterwards doesnt work
What do you mean by "a stock B10 file"? There are so many files types :-/
I am not quite sure what I should do now, do I have to do the EDL route? That one sounds confusing as well.
EDIT: I tried using B08 Files and now the reboot prompt in TWRP tells me there is no os installed.
Will I, like naveen09y, end up without TWRP if I reboot now?
Click to expand...
Click to collapse
Probably, so just don't. You should just wipe system and data, flash the bootstack, then the system. Also follow raystef's guide to "remove bootloader unlocked inscription"
I now managed to get the phone working with EDL flash of MM B10.
But I cant relock the bootloader :-/
Bascially my bootloader is gone so I cant reboot to it and do "fastboot oem lock".
Why is this such a hassle
HansWursT619 said:
I now managed to get the phone working with EDL flash of MM B10.
But I cant relock the bootloader :-/
Bascially my bootloader is gone so I cant reboot to it and do "fastboot oem lock".
Why is this such a hassle
Click to expand...
Click to collapse
You didn't follow my instructions. Follow raystef's removed unlocked bootloader inscription and you'll get fastboot back. You can do that with the phone on.
Don't relock it unless it's really necessary (i.e. warranty). If you're gonna sell it just follow that guide and don't relock, the 5 seconds screen will disappear and it'll look like it's locked
I cant follow the guide because I can't access the bootloader...
Also the TWRP files in https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 this guide (step 6) are no longer accessible.
HansWursT619 said:
I cant follow the guide because I can't access the bootloader...
Also the TWRP files in https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 this guide (step 6) are no longer accessible.
Click to expand...
Click to collapse
What? Lol
First of all - you are basically installing the bootloader with raystef's guide, so I have no idea why you want to enter it...
You have to enter TWRP and follow the guide from there.
The guide from Controllerboy is basically the same guide but it also has instructions on other things (i.e. unlock etc.). I don't know what you are trying to accomplish with it. Use EDL Tool by djkuz if you want to install TWRP (it is explained there how to do that).
Phone was rooted with Magisk 16, I was on AEX Android 8.1 ROM. I'm trying to return to stock and relock bootloader.
I wiped everything, I flashed A2017G-N-B10-bootstack and A2017G-N-B10-stocksystem from "TWRP flashable Bootstack/Stocksystem Images" section. Booted to system and now phone is stuck on the ZTE POWERED BY android boot screen. 5 minutes there. Is it normal?
Edit: Got tired of waiting and kept pressing the power button. After doing so, the phone reboots but same thing. And I can't access TWRP with VOL INCREASE + POWER BUTTON.... VOL DECREASE + POWER BUTTON takes me to Factory Test Mode.
aLexzkter said:
Phone was rooted with Magisk 16, I was on AEX Android 8.1 ROM. I'm trying to return to stock and relock bootloader.
I wiped everything, I flashed A2017G-N-B10-bootstack and A2017G-N-B10-stocksystem from "TWRP flashable Bootstack/Stocksystem Images" section. Booted to system and now phone is stuck on the ZTE POWERED BY android boot screen. 5 minutes there. Is it normal?
Edit: Got tired of waiting and kept pressing the power button. After doing so, the phone reboots but same thing. And I can't access TWRP with VOL INCREASE + POWER BUTTON.... VOL DECREASE + POWER BUTTON takes me to Factory Test Mode.
Click to expand...
Click to collapse
Try this.
Oki said:
Try this.
Click to expand...
Click to collapse
Yes, thanks. I already had seen it some minutes ago. It's so convenient that you posted this guide today lol
I want to flash stock rom from RR Nougat. I have installed latest twrp, flash bootstack and then stock system. After that I flash supersu 2.79. But when I press reboot system it say no OS installed
Willchi said:
I want to flash stock rom from RR Nougat. I have installed latest twrp, flash bootstack and then stock system. After that I flash supersu 2.79. But when I press reboot system it say no OS installed
Click to expand...
Click to collapse
The best way to return to stock is via EDL, for example MiFlash or EDL tool. If you have an U, then DrakenFX's zips can do that, it happened to me already. Usually G zips like raystef's work just fine.
Try using Magisk instead of SuperSU, just in case. Use 16.7
@Choose an username...
Thanks for posting this.
Credits to all concerned a big thumbs up.
I do however feel that there are to many versions of the Axon 7 packages and I can see why people are ending up with boot issues etc.
Syberclone said:
@Choose an username...
Thanks for posting this.
Credits to all concerned a big thumbs up.
I do however feel that there are to many versions of the Axon 7 packages and I can see why people are ending up with boot issues etc.
Click to expand...
Click to collapse
what
you do realize this guide is older than a year right?
Yeah, its all good