No recovery found on my device (Xperia z3 dual) - Xperia Z3 Q&A, Help & Troubleshooting

I have a Z3 dual, and I seem to have no recovery (or even a partition). The phone has no data saved so it is safe to reinstall firmware and start over. But I am trying to get the phone going for use. I currently have 5.0.2 (rooted)installed, and want to boot to recovery to flash a zip file. I have tried a million times to do this in kitkat as well as the current upgrade. In all cases there is no recovery. TWRP cannot create a custom one and there is no recovery to boot into. I installed goomanager and tried to create a custom recovery and got the message "No recovery can be found on your device". Now, I have read that some xperia models actually did not come with any stock recovery (but I cannot verify this). I believe this might the problem from the very start. So, how do I create a custom recovery, where there seems to never have been a stock recovery to begin with. It seems like an endless loop of trying to create a custom recovery, only to be told by TWRP or goomanager that you cannot boot into recovery because there isn't any. I hope this makes sense what I am describing. I have tried many times to create a custom recovery, did re-installs of the firmware (downgraded, upgraded -- ALWAYS ROOTED), tried with bootloader locked and unlocked -- no luck in all permutations and combinations. In the end I cannot boot into the TWRP recovery screen (or any recovery screen for that matter). It simply just hangs for a bit then simply boots normally. Sometimes it gives a message telling me there is no recovery to be found. I know I am missing something, so any help is greatly appreciated.

Related

NS4G CWM/Recovery Flash Issues

So. I'm sorry to say, but this phone has given the biggest headache. Here's the background:
I really only use this phone for entertainment and stuff. BUT I decided to root and unlock the bootloader, somehow or another the phone apparently lost root a few times (According to some users here) but never lost SuperUser or anything. I've never been able to flash a rom on this thing. Then a few weeks ago the phone just encountered an error of some sort and would only get to the ICS boot animation and loop over and over. I just gave up on it. Then one day I decided to play with it. I got it into fastboot and then into recovery, (Not CWM Recovery) and was able to get it all set up again. So I figured I'd give it one more shot. I downloaded CWM and downloaded recovery, and a custom rom. tried to flash through fastboot>recovery but it's still the stock recovery, not CWM recovery. So I factory resetted it etc and started from scratch. Now if I download CWM it WILL NOT download recovery. It gets about 99% of the way and tells me: "An error occurred while attempting to run privileged commands!" If I download it from a link I can't open the file....... Someone help I just want a good JellyBean Rom. :crying:
Edit: I've Googled as much as I could stand and still haven't come across anything entirely helpful. Please explain so I could understand. Pictures help if needed lol
Anyone?
You can't use clockworkmod app to flash recovery without root.
Get the fastboot image of cwm recovery ( not the app). Or twrp. Flash it with fastboot.
Boot directly into it and flash what you want. If you boot up a stock os it overwrites the custom recovery on boot.
clockworkmod app sucks IMHO and should never be used for anything period. Not fond of the recovery itself either.

Problem installing custom recovery, please help!

I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
retfeg said:
I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
Click to expand...
Click to collapse
same problem here! brand new phone, 4.4.2 o2 UK.
the mismatched partition size error is not important i know that.
have tried Philz (got it to work once, but after rebooting, had gone again. ever after letting it fix the rom rewrite on exit!). also tried stock CWM 6046 and 6047.
have tried entering recover immediately after flashing.
have tried flashing multiple times.
have tried different usb ports.
ideas please?
i've never had this much trouble with any phone (have experience over 3 years with Blade, G300, Xperia range etc.)
edit: tried using fastboot -S 0 parameter also, seems to make no difference. phone won't boot into recovery. this is slightly different to the problem i had with old phone, that one would boot Philz but not boot any ROMs. this one is booting stock ROM. if i can get Philz to "take" again i could try flashing CM, but i wanted to stay on stock, and just root it..
edit2: just started working! bizarre.. hope this doesn't jinx it. i wrote two recovery images with -S 0 and it works, not sure if because of that or something else. btw Philz won't backup the stock rom, odd - it just errors out, CWM standard works though.
hurrah! i rebooted normally, went back to fastboot and recovery still there. this is with recovery-clockwork-6.0.4.7-falcon.img
now i can hopefully root it..
wonder if my 3rd moto g will get any easier! this is a huge PITA of random non-workiness so far.

XZP Wont Boot after Flashing Standard Rom

Hi All,
I've been trying to install TWRP, Root etc on my XZP since yesterday. I've done something wrong at some point, and now my phone will not boot at all.
I had no troubles unlocking bootloader, installing TWRP etc initially. I then tried to install a custom rom from these forums and that's where things spiraled downwards for me.
As part of that procedure, I needed to flash the latest sony firmware first. That went fine.
However, now TWRP is not able to decrypt storage, so I'm not able to flash anything else. Perhaps this is because I booted into the new sony firmware and forgot change the pattern/fingerprint to pin/fingerprint.
So I'm not able to unlock the storage via TWRP by entering a password.
I tried to reflash the same firmware again using newflasher. But the phone won't boot at all. It turns off immediately after the Unlocked bootloader warning. It's not going into a boot loop. Just turns off.
I then tried to flash the TWRP recovery image using adb fastboot command, and the flash seemed to execute properly, but I still can not boot into recovery.
Is it possible the main storage is still encrypted, so nothing can flash to it? Bricked? If so, how do I proceed?
I read something about reformatting partitions? But I'm not able to get into TWRP recovery menu to do this.
*EDIT: I reflashed trwp recovery image, and am not able to boot into recovery. I still can not unlock (unencrypt) the main storage though.
*2nd EDIT: I followed the instructions here:https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
I was then able to flash the stock ROM back onto my device, and I'm able to boot my phone up. I'll look at installing a custom ROM at a later date.
Thread closed at OP request

Cannot boot after flashing TWRP

I was finally able to unlock my bootloader today after the 72-hour waiting period, but am having a problem getting TWRP flashed. I can flash the stock ROM (perseus_images_8.12.13_20181213.0000.00_9.0_cn_21f4637335.tgz) no problem, get through setup, enabling ADB, etc, but as soon as I flash TWRP, the device stops booting. It flashes successfully, but then attempting a reboot always ends up with the device back at the bootloader. Key combos for other modes doesn't make a difference. I'm working on trying the Global ROM too, just to see how that runs, but I have not been able to get TWRP at all or get the device booted to anything other than fastboot after a TWRP flash (tried official & unofficial versions).
I've seen other posts with a similar issue, but that usually seemed to be about users accidentally ended up in Fastboot & not knowing how to get out of it. That's not the case here.
I've been using Android & custom ROM's for years, so I know my way around ADB, Fastboot, & everything rooting & custom ROM's entail, I just seem to be missing something here.
Thanks for any help you can provide.
EDIT:
Not sure why flashing the Global Dev ROM (perseus_global_images_9.5.17_20190517.0000.00_9.0_global_134d3070e5.tgz) made any difference, but after that, ran through the first run wizard, I was able to flash TWRP from the bootloader & actually boot into it so I could flash a custom ROM.

[HELP] Remove boot loop without root & USB debugging?

Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Hørk said:
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Click to expand...
Click to collapse
Ever fix it?

Categories

Resources