Related
Hi,
I unlocked my bootloader, flashed boot.image and CM snapshot 12 and then after setting up my phone I tried installing TWRP 2.8 with that stupid TWRP Play Store app.
NOW i cannot get into bootloader OR recovery with neither the bootmenu nor adb commandline nor the Volume+- on reboot...
PLEASE HELP me get TWRP 2.8 on my device... OR get me back into Recovery... I'm going crazy here
Turning off the phone and using the volume buttons after turning it on, gives me a black screen with an orange LED for recovery. How do I fix this.
PLEASE, there must be someone out there that can help me get recovery back???
Puffin617 said:
Hi,
I unlocked my bootloader, flashed boot.image and CM snapshot 12 and then after setting up my phone I tried installing TWRP 2.8 with that stupid TWRP Play Store app.
NOW i cannot get into bootloader OR recovery with neither the bootmenu nor adb commandline nor the Volume+- on reboot...
PLEASE HELP me get TWRP 2.8 on my device... OR get me back into Recovery... I'm going crazy here
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53220435&postcount=4
here is a recovery guide
i suggest sticking with CM11 or Using the TWRP build by Championswimmer, his ones support CM11 but i have no idea how to use it or install it ( i think recovery partition)
Envious_Data said:
http://forum.xda-developers.com/showpost.php?p=53220435&postcount=4
here is a recovery guide
i suggest sticking with CM11 or Using the TWRP build by Championswimmer, his ones support CM11 but i have no idea how to use it or install it ( i think recovery partition)
Click to expand...
Click to collapse
I have tried flashing an FTF (that I have used in the past) but it fails....
UPDATE: Got the FTF to Flash...
Puffin617 said:
I have tried flashing an FTF (that I have used in the past) but it fails....
Click to expand...
Click to collapse
1. install drivers
2. Download FTF for your device
3. Flash FTF
(flashmode=Volume down)
Envious_Data said:
1. install drivers
2. Download FTF for your device
3. Flash FTF
(flashmode=Volume down)
Click to expand...
Click to collapse
Do I need to UNLOCK again after FTF?
Puffin617 said:
Do I need to UNLOCK again after FTF?
Click to expand...
Click to collapse
No. Flashing a FTF restores the entire device to a factory state.
Bootloader isnt affected at all
Envious_Data said:
No. Flashing a FTF restores the entire device to a factory state.
Bootloader isnt affected at all
Click to expand...
Click to collapse
Thankx for the help
I'm back on CM with everything flashed correctly. Now I just want to get rid of this CWM and get TWRP back on...
Puffin617 said:
Thankx for the help
I'm back on CM with everything flashed correctly. Now I just want to get rid of this CWM and get TWRP back on...
Click to expand...
Click to collapse
As said there is only CWP and Philz
No twrp for xperias and cm11
Envious_Data said:
As said there is only CWP and Philz
No twrp for xperias and cm11
Click to expand...
Click to collapse
Flashing the latest monxDIFIED gives you TWRP 2.8...
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
@KaiserSnorezay
XZDR is still not compatible with MM, that's why you got a bootloop...
Also you can't install the "regular" TWRP with twrp manager on a LB as there is no recovery partition... it won't work and probably will mess your phone in the process.
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770
Just did it exactly this way yesterday on my friends d6503 (minus the d6502 patch obviously) had 0 troubles MM, root and recovery working perfectly.
Thanks, will try this today. Is wiping data required or can i get by by just flashing the older one?
ptmaniac said:
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
Click to expand...
Click to collapse
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
KaiserSnorezay said:
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
Click to expand...
Click to collapse
Weird, after you have your phone rooted it should be simple to install xzdr... just enable usb debugging in the phone and make sure you have the adb drivers correctly installed in your pc.
Download the latest xzdr from nut's thread ( http://forum.xda-developers.com/showthread.php?t=2261606 ) unzip it and run install.bat . After a successful install the phone should reboot to twrp automatically and it's done.
Okay, I fixed it..using Flashfire! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
KaiserSnorezay said:
Okay, I fixed it..using ! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
Click to expand...
Click to collapse
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
dodge911 said:
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
Click to expand...
Click to collapse
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
KaiserSnorezay said:
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
Click to expand...
Click to collapse
okay. you mean flashing any old firmware ( which i did and still in bootloop ) & root it. Then installing recovery for the same firmware ?
with "recovery" will i be able to get back my whole data ?
KaiserSnorezay said:
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
Click to expand...
Click to collapse
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
DedSec_35 said:
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
Click to expand...
Click to collapse
Sorry, I ditched my Z2 for a Oneplus 3 in August 2016. Learnt my lesson, only going to use phones with easily unlockable bootloaders.
Hi I had Xpower5 Rom. I wanted to try new Nougat. I had many issues with flash (error of processing system.sin and loader.sin). I dont know how now it work. After that I flashed AndroPlus 43 kernel and TWRP 3.0.2. Kernel works but No white led on startup and no recovery there (also adb reboot recovery not work) . I tried another img of twrp and nothing changed. Any idea how install recovery? Anybody has the same problem with flashing? Thanks
As this phone doesn't support universal recovery and only sports a ota partition that can be used for recovery but then requires a kernel that supports booting recovery from ota partition, it's a hustle to use non standard recovery systems.
Is there even a nougat compatible kernel with included TWRP ota boot support for this phone?
This should work
https://forum.xda-developers.com/showpost.php?p=70807294&postcount=132
Also patching the stock kernel with the rootkernel tool integrates working twrp.
Gewiz said:
This should work
https://forum.xda-developers.com/showpost.php?p=70807294&postcount=132
Also patching the stock kernel with the rootkernel tool integrates working twrp.
Click to expand...
Click to collapse
It works! Thanks. Problem was: no white LED flash there. I have to press vol down and power on.
But I have still have a problem with flashing. Error of processing file loader.sin or system.sin. I cant flash again anything
Make sure you use latest ver of flashtool 0.9.23.2
Gewiz said:
Make sure you use latest ver of flashtool 0.9.23.2
Click to expand...
Click to collapse
Yes I have latest version. I tried older version as well but nothing changed
hromanse said:
Yes I have latest version. I tried older version as well but nothing changed
Click to expand...
Click to collapse
Flash firmware 5.11 first and flash nougat firmware afterwards.
This should work
Not work as well
the 3.1 3.0.2 TWRP bundled in rootkernel 5.23 messess up the internal permissions, so it will appear to work until you try and recover, or - TWRP runs a wipe with mkext4fs
i was talking a bit about it in https://forum.xda-developers.com/showthread.php?t=3560135
---------- Post added at 18:16 ---------- Previous post was at 18:13 ----------
Gewiz said:
Flash firmware 5.11 first and flash nougat firmware afterwards.
This should work
Click to expand...
Click to collapse
Yeah, going back to Lollipop and going all the way up to Nougat works, this is what happened to me. I thought I had a psuedo-recovery-dual system boot .... where i could switch between Marshmallow and Nougat
But then I decided to factory reset, and that started all the problems.
NeoBeum said:
Yeah, going back to Lollipop and going all the way up to Nougat works, this is what happened to me...
Click to expand...
Click to collapse
Thanks! It works
hromanse said:
Thanks! It works
Click to expand...
Click to collapse
Just make sure Restore works, so you don't get burned thinking everything is ok and end up with 12GB of partition mismatched data backup after a month, like I did
Hi, i have new honor 9, as i open the phone , it is upgrade to B183 Version.
i need to automatic call recorder and i have found a zip.file to flash whit twrp. So i want install twrp and root...
The first time i download TWRP 3.1.1-1 and Supersu 2,82, i install all whit my zip file per automatic call recorder...
all is ok, twrp, i have root and call recorder working,,, but...
I lose navigation buttons and Camera Flash.
for navigation buttons isnt a problem... i can use only Home button ( i had a Meizu phone before but...
I need camera flash ! it have to work.
so....
for have again all working , i used the Rebrand Guide of HWOTA, whit B120 all work again.
cannot have more OTA upgraded but i think because i just had download them whit my imei.... ok i will wait new update for verifyng it.
I can use Finder Firmware Huawey for have manual upgrade.
Now i'm again in b183.
how can I do now for have a valid twrp or valid method for root phone? Because i read that same people have them..... but i think have reroll to b120 almost 50 time whithout always same results....
oh oh, i see now that i have wrong section. moderator can you move?
SOLVED!
After many time i can have all working now:
Starting to B183 firmware whit button and flash not working:
Step 1) Rollback on B120, downgrading by flashing with hwota scripts, this post . option are 2 (directory upgrade) and 1 (same brand). with this you will have working buttons
Step 2) Update to B183 (FF full-ota files timestamped 2017.12.28)
Step 3) Unlock the bootloader.
Step 4) Install the TWRP-3.1.1.1_120_130_170.img from this thread.
Step 5) Install Supersu SR5
WARNING: you have to be carefull when go in TWRP recovery: do not modify system data at twrp's boot, then rebooted choosing not to install twrp at twrp's exit prompt. ( dont'know if it is important... but so it work
so you will have a b183 firmware whit all working: root, button and flash.
please, reply if this work for you.
Add more infos about FF .
In updater system , no update available after roolback to B120.
Need to use Firmware Finder Huawei on Playstore.
1-Choose the desired full version
2-Check Firmware access for be sure not make mistakes.
3-Get an update throught DNs , register update and change Dns .
4- Come back to updater and check update .
angelobiz said:
Step 2) Update to B183 (FF full-ota files timestamped 2017.12.28)
Click to expand...
Click to collapse
In this step, did you do it with the HWOTA tool or with fully stock B120 inside the system?
Zuzler said:
In this step, did you do it with the HWOTA tool or with fully stock B120 inside the system?
Click to expand...
Click to collapse
While on stock B120 use the android application Huawei Firmware Finder to upgrade:
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/
But you could try to test to use HWOTA to upgrade from b120 to b183 and then report here?
I already tried upgrading to B182/183 with HWOTA. I was on B120 and did a B182 and B183 upgrade. I was left with no capacitive keys and no flash. Camera was working however.
Just right now downloading B183 on top of a new locked B120 with the Firmware Finder, will report back.
However, it's very inconvenient to update the system this way if you have an unlocked bootloader and are rooted. I mean, downgrade to B120, twice within HWOTA, upgrade within the system and then AGAIN re-unlock the bootloader which results in a factory reset - come on...
Does it also work with Magisk or only with SuperSu?
SuperSu already is nice, but the additional benefits like would be nice to have, especially passing SafetyNet.
Anyone still with missing navigation buttons? I might have a solution that does not require flashing firmware or doing factory reset
zxz0O0 said:
Anyone still with missing navigation buttons? I might have a solution that does not require flashing firmware or doing factory reset
Click to expand...
Click to collapse
Mind telling us?
For me everything worked fine by downgrading to B120 and then updating B183 through the OS.
Zuzler said:
Mind telling us?
For me everything worked fine by downgrading to B120 and then updating B183 through the OS.
Click to expand...
Click to collapse
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Good. This might be a breakthrough. Could you please share a step by step guide what to do? Thanks.
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
good, can you share your modified TWRP recovery???
the solution not work if you do different. you have to downgrade to B120 to HWOTA whit file of its post. After have to upgrade to B183 whit FFH whit locked bootloader
ang stock recovery, after install twrp and supersu.
i dont know why, but so it work.
angelobiz said:
good, can you share your modified TWRP recovery???
the solution not work if you do different. you have to downgrade to B120 to HWOTA whit file of its post. After have to upgrade to B183 whit FFH whit locked bootloader
ang stock recovery, after install twrp and supersu.
i dont know why, but so it work.
Click to expand...
Click to collapse
It would be a good thing.
Edit : As we are all trying to make your device 100% functional with root.
Here is a link for a Su Emui , not testes yet. Work on the mosty Huawei devices
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
http://www.mediafire.com/file/pn2pv1rqih1ug81/SuperSU-v2.82-EMUI5-SELPermissive[1].zip
https://androidfilehost.com/?fid=673956719939815322
I had used this version and it work
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Can you provide details?
I wonder if we can pull the touch_key firmware from a working B120 firmware and flash over a later version?
angelobiz said:
I had used this version and it work
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Now i'm ok .
I used the good twrp and sideloaded Supersu.sr3 .
All buttons and flashlight work nice
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
So did your twrp fix touch_key once broken?
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Can you please share your modified TWRP recovery, so we can test on our phones?
This issue is driving me crazy.
Thanks :good:
Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
I'm using more current Twrp and magisk 16 I do not know which is preventing the biometric reader
rinampa said:
I'm using more current Twrp and magisk 16 I do not know which is preventing the biometric reader
Click to expand...
Click to collapse
At the time, I do not know either what is causing this. Because the Oreo rom is rather bugged a bit. (Lower audio, wifi not turning on once it's off and now this)
What twrp should i use for nougat version?
HnsAlczr said:
What twrp should i use for nougat version?
Click to expand...
Click to collapse
Since it's nougat, preferably use 20180304. Once on Oreo, you can flash the latest.
+)KEV1N(+ said:
Since it's nougat, preferably use 20180304. Once on Oreo, you can flash the latest.
Click to expand...
Click to collapse
After i flash twrp thru adb reboot it on twrp works properly but when i reboot to system im stuck at Asus Logo, did i do something wrong on the process?
HnsAlczr said:
After i flash twrp thru adb reboot it on twrp works properly but when i reboot to system im stuck at Asus Logo, did i do something wrong on the process?
Click to expand...
Click to collapse
Did you upgrade your system to Oreo? If so, did you have substratum themes on?
I wonder when he opens the twrp he asks for the PIN number , password or something?
How do I unlock the ZenFone 3 Zoom bootloader on Android Oreo ?
ZueiraBR said:
How do I unlock the ZenFone 3 Zoom bootloader on Android Oreo ?
Click to expand...
Click to collapse
https://www.asus.com/br/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_Download/,Select the android operating system, Versão UnlockTool_2018_0629(android O)
2018/06/29740.7 KBytes.
Read the instructions carefully.
+)KEV1N(+ said:
Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Hi all, does not work with WW-80.30.76.10 . Help me please
personal I flashed the twrp by adb fastboot soon then I entered i REBOOTED-SYSTEM by own twrp! but when I turned it off and put it in recouvery mode (twrp) it goes into the original factory recovery! Does anyone know the solution ??
Delaias1995 said:
personal I flashed the twrp by adb fastboot soon then I entered i REBOOTED-SYSTEM by own twrp! but when I turned it off and put it in recouvery mode (twrp) it goes into the original factory recovery! Does anyone know the solution ??
Click to expand...
Click to collapse
Installed twrp by fastboot goes into recovery in twrp restart the always by twrp.
After updating to twrp new version I can not update more firmware, I have to download recovery stock
I am having problems in twrp I can not install rom always error 7 in this last update how to solve?
Please, I appreciate your help.
+)KEV1N(+ said:
Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Is there any UN-OFFICIAL unlock method ? tks
Can someone help me? I can't find the correct version (or doesn't even exist) of twrp for my zenfone zoom s.
(UL-Z01H-WW-80.30.76.74)