lost recovery? - Xperia Z3 Compact Q&A, Help & Troubleshooting

The scenario:
4.4.4, stock, rooted, everything works as expected (xposed, titanium, etc)
The issue:
When I want to enter recovery either via the NDR util or by pressing volume up while booting the phone boots as usual and not into recovery.
The question:
What the fudge happened?
The solution?

lost root
charliebigpot said:
The scenario:
4.4.4, stock, rooted, everything works as expected (xposed, titanium, etc)
The issue:
When I want to enter recovery either via the NDR util or by pressing volume up while booting the phone boots as usual and not into recovery.
The question:
What the fudge happened?
The solution?
Click to expand...
Click to collapse
You update busybox? I had this also
Just root again with giefroot tool. And don't update busybox

Related

Getting into Recovery L Bloader?

TMobile 6006
How do I get into recovery without being able to boot into system and the hardware recovery method doesn't work?
New to this device. Had no problem rooting, installing CWM 6028 and getting into CWM either via hardware or booting recovery from the rooted stock.
I installed [ROM][LB][UB] eXistenZ v7.0.0 and it came up great with no problems. Installed Root Explorer and TiBu w/o problem. Booted into CWM recovery from system without problem. Restored some files system data with TiBu. Rebooted and went into a boot loop where the boot animation comes up and then the phone reboots. I managed to turn the phone off by holding power and vol+. But, on reboot I can no longer into CWM recovery. I want to reflash the rom, or restore a backup either to stock or the working new rom.
I can get fastboot to recognize the phone but don't know a command to boot into recovery. I'm certain that the CWM Recovery is still valid. I just need to get into CWM one time!
HELP!

TWRP not sticking

Just used NRT to flash the nougat factory image downloaded from image website. Everything worked great, phone is up and running. tried using NRT to flash just TWRP without root or anything else and it completes and I'm able to get into it once its done (sitting in fastboot, up to recovery, power button to enter). once I boot into android I power off and hold Vdown and power and get fastboot, go to recovery, press power, phone reboots and gives me android guy with red triangle... any idea what is going on?
icedclown said:
Just used NRT to flash the nougat factory image downloaded from image website. Everything worked great, phone is up and running. tried using NRT to flash just TWRP without root or anything else and it completes and I'm able to get into it once its done (sitting in fastboot, up to recovery, power button to enter). once I boot into android I power off and hold Vdown and power and get fastboot, go to recovery, press power, phone reboots and gives me android guy with red triangle... any idea what is going on?
Click to expand...
Click to collapse
I've read a lot of threads recently that say TWRP won't stick unless you root your phone. I've always rooted my phone after installing TWRP so I can't verify that this is true, but again, a lot of threads are saying that it's so.
alryder said:
I've read a lot of threads recently that say TWRP won't stick unless you root your phone. I've always rooted my phone after installing TWRP so I can't verify that this is true, but again, a lot of threads are saying that it's so.
Click to expand...
Click to collapse
you need to delete a recovery-from-boot file in system. or itll keep getting rid of twrp after a reboot.
simms22 said:
you need to delete a recovery-from-boot file in system. or itll keep getting rid of twrp after a reboot.
Click to expand...
Click to collapse
This is assuming you are running a modified boot.img (unencrypted, etc), no?
yes the recovery from boot file. If you allow TWRP to write system partition it will rename this file to .bak.
Str8gahbidge said:
yes the recovery from boot file. If you allow TWRP to write system partition it will rename this file to .bak.
Click to expand...
Click to collapse
Nice, a clear explanation that explains why so many dont have this issue. Like me. When I flash recovery I boot TWRP and delete a few keyboards... so yea I have mounted system writable.
I had the same issue. flashed TWRP several times, never could boot into recovery. rooting worked fine though. I went ahead and installed the TWRP installer/updater from the Google Play store and installed it from there. worked like a charm....

TWRP + Root Nougat Huawei P9

Is it possible to install TWRP with your device running the Nougat beta ?
The recovery is separate from the firmware. So I don't see why it wouldn't be possible. Root on the other hand I wouldn't know but I suppose the SuperSU beta zip file flashed with custom recovery would get the phone rooted.
If it was a kernel being flashed then that would matter as it affects the firmware (as it replaces the stock kernel).
Yep. You can install a custom recovery, even if you accidentally wipe your system, the custom recovery will still be there. (I have experience) I think that, if you can find the right supersu zip file for your phone, you should be able to root your phone.
FedoraMan said:
Yep. You can install a custom recovery, even if you accidentally wipe your system, the custom recovery will still be there. (I have experience) I think that, if you can find the right supersu zip file for your phone, you should be able to root your phone.
Click to expand...
Click to collapse
I tried to install the custom recovery using adb, however my phone can't be detected ?
Install the drivers for your phone. Just look up Huawei p9 bootloader drivers, and you should find it.
FedoraMan said:
Install the drivers for your phone. Just look up Huawei p9 bootloader drivers, and you should find it.
Click to expand...
Click to collapse
Already tried this, since installing the Nougat beta my PC only recognises my phone when in recovery mode. I installed TWRP but phone still boots into the original erecovery and not TWRP
Did you install with with fastboot? or from within the phone? Because you have to reboot to recovery pretty much right after flashing it. Try re-flashing twrp from inside the phone with flashify, then reboot to it immediately afterwards. (Get the 3.0.2-0 (or higher) version for your phone)
FedoraMan said:
Did you install with with fastboot? or from within the phone? Because you have to reboot to recovery pretty much right after flashing it. Try re-flashing twrp from inside the phone with flashify, then reboot to it immediately afterwards. (Get the 3.0.2-0 (or higher) version for your phone)
Click to expand...
Click to collapse
Yes installed with fastboot, I manually booted into recovery (volume up + power button) right after flashing it. I thought flashify requires root ??
Wait, you updated to 7.0 without root? Did you use the normal updater? Because if so, try finding a way to downgrade again. Maybe that will work
FedoraMan said:
Wait, you updated to 7.0 without root? Did you use the normal updater? Because if so, try finding a way to downgrade again. Maybe that will work
Click to expand...
Click to collapse
Yeah, I just flashed the update using the dload method. The main reason I want to install TWRP is so i can downgrade. I've tried using the dload method to downgrade however it doesn't work.
For the dload method, I think you have to flash stock recovery first
FedoraMan said:
For the dload method, I think you have to flash stock recovery first
Click to expand...
Click to collapse
I am currently using stock recovery and it still won't let me downgrade, the update reaches 51% then an error occurs. Would it be possible to flash downgrade firmware using fastboot ?
I believe you can, but you should check online to see if it is.
FedoraMan said:
I believe you can, but you should check online to see if it is.
Click to expand...
Click to collapse
I will check and try this method, I'll get back to you with the results
Ok. Good luck!
Same problem here, I installed a leaked Nougat beta for the Honor 8 via TWRP and when I tried to get back to TWRP it wouldn't let me. I've tried to flash it again via fastboot but I can't boot into it :/
I have this problem too after Flashing Nougat.
I have already flashed twrp recovery via fastboot, installation complete. But I cant boot into recovery mode.
I have never had this kind of problem before. If you tried a cold boot (Hold volume up + power), try typing "adb reboot recovery" instead (or the other way around, if you've done that)
Hello.
I came from z3.
For z3 to get in recovery with N u have to hold down vol button and insert cable. Charger or PC
Sent from my EVA-L19 using XDA-Developers mobile app
I don't know if this works, but I was looking around in HiSuite (huawei's phone thing app on pc) and saw a ROM flashing option. Try that.

Can't root LG-H811 20p because supersu soft bricks phone

So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
theprof7 said:
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
Click to expand...
Click to collapse
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
raptorddd said:
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
Click to expand...
Click to collapse
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
theprof7 said:
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
Click to expand...
Click to collapse
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
https://drive.google.com/file/d/0B90RfjoH13UEbDFBSG5XWVA0ME0/view?usp=sharing
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
theprof7 said:
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
try a custom kernel it has superSU installed.. i say imperium kernel.
try first the custom kernel.. if not you can only downgrade to 20o. no lower or youll hard brick phone.
Click to expand...
Click to collapse
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
can you please share what guide you used to unlock and root this phone? I'm having issues on finding it, im on the newest update
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
Please, can you share what guide you used to unlock and root this phone (20p)? Can not find any complex info anywhere.
Thank you.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
king200 said:
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
Click to expand...
Click to collapse
You can get the latest Imperium kernel (5.0 currently) from: http://forum.xda-developers.com/g4/orig-development/kernel-imperium-kernel-g4-v1-0-t3282915
Yes, fastboot boot from the twrp image was kind of a hack, but it worked. As for SuperSU, I tried v1.94 and SuperSU-v2.76-20160630161323.zip. Both soft-bricked the phone. Maybe the newest SuperSU will work, but I wouldn't count on it given that several previous versions didn't.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
I need to flash twrp and root from 20p also. One question to clarify exactly what you did,
Did you originally try flashing TWRP from TWRP? You said you flashed root from TWRP but I want to verify if you tried flashing TWRP from TWRP like:
> adb reboot bootloader
> fastboot boot twrp-3.0.2-0-h811.img
then in TWRP:
> install click on image tab.. then select twrp-3.0.2-0-h811.img recovery and flash it.
> reboot recovery (should reboot to TWRP you just flashed)
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
emailej said:
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
Click to expand...
Click to collapse
Yes, just loads TWRP temporarily. Later I installed some apps that flashed the recovery successfully, either rashr or flashify (I don't remember which)
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the file and keep in phone internal storage with names recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be)
Now you are in twrp recovery page in the phone.
Tap Install > Images (bottom right) > select recovery.img >
Now you are in next screen where options to slect recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
I have flashed more than 6 methods to install supersu. Keep trying and reply.

Can't enter TWRP recovery after using Flashfire, phone bootloops with xposed enabled

Tried flashfire to flash a zip rather than messing around in recovery (dnscrypt), now can no longer boot into twrp and get bootloops unless I disable xposed.
Volume down button activates the pink led as it should, momentarily, but phone then continues on into system boot sequence after entering password. No twrp logo/screen.
No files from the zip appear to have been flashed by flashfire.
Boot and keys still locked and untouched.
Reflashing twrp recovery via twrp manager or twrp app makes no difference and appears recovery is still there.
I have no access to a computer but still have root, titanium backup, couple of root file managers and terminal app etc.
Has flashfire messed with system boot scripts or something? How do I diagnose/fix?
Edit: guessing id need flashtool and computer again to roll back kernel with root and recovery (LB) on the chance that would work, S'pose I'm stuffed then, unless there's a way to live flash or find out what changed.
Edit#2: FIXED. at a friends and redid the process. Kernel.575 -> install recovery,flash root and xposed zips -> Kernel.291. Nothing lost. DO NOT use flashfire if on this recovery method, don't even be tempted. The zip I tried to flash earlier works so it was definately flashfire.

Categories

Resources