Database Develop

[Q] Stuck in recovery mode

Right, so I've been following http://forum.xda-developers.com/xperia-z/orig-development/root-xperia-z-c660x-unlocked-t2154310 to root my xperia z. I followed the instructions but when I wrote the second image it refused to boot properly, looping constantly through the sony logo IIRC.
To fix this I used the recovery image. I can get into it just fine but when I try to install SuperSU-1.25-Busybox-1.20.2-UPDATE.zip it goes through the motions, but rebooting the phone just brings me back into recovery mode. Any ideas on what's wrong?

Rare Devil said:
Right, so I've been following http://forum.xda-developers.com/xperia-z/orig-development/root-xperia-z-c660x-unlocked-t2154310 to root my xperia z. I followed the instructions but when I wrote the second image it refused to boot properly, looping constantly through the sony logo IIRC.
To fix this I used the recovery image. I can get into it just fine but when I try to install SuperSU-1.25-Busybox-1.20.2-UPDATE.zip it goes through the motions, but rebooting the phone just brings me back into recovery mode. Any ideas on what's wrong?
Click to expand...
Click to collapse
there is only one image that you need to flash that is boot.img
after that flash advance stock kernel in recovery followed by super su make sure your bootloader is unlocked if you plan to flash custom kernel
what firmware you are on?
Unlocking bootloader invalidates warranty

androidtweaker1 said:
there is only one image that you need to flash that is boot.img
after that flash advance stock kernel in recovery followed by super su make sure your bootloader is unlocked if you plan to flash custom kernel
what firmware you are on?
Unlocking bootloader invalidates warranty
Click to expand...
Click to collapse
I'm not sure what firmware I'm on but I did update it just before I tried all this. I did unlock my bootloader and used boot.img to get into recovery mode. Super su is done through recovery mode right? Because every time I try to install it it just returns to recovery mode with no changes

Rare Devil said:
I'm not sure what firmware I'm on but I did update it just before I tried all this. I did unlock my bootloader and used boot.img to get into recovery mode. Super su is done through recovery mode right? Because every time I try to install it it just returns to recovery mode with no changes
Click to expand...
Click to collapse
Try twrp recovery you can download the .img from here
after flashing recovery try flashing SU from twrp.
post the results

androidtweaker1 said:
Try twrp recovery you can download the .img from
after flashing recovery try flashing SU from twrp.
post the results
Click to expand...
Click to collapse
Flashing that img gives me an error "writing: 'recovery' FAILED (remote: Command not allowed)

If you want to try TWRP, try Dual Boot recovery with Philz Touch CWM Advanced Edition and TWRP by shoey63.
Sent from my C6603 using Tapatalk

What do I specifcally type for that? From what I've seen different img files use different commands

Rare Devil said:
What do I specifcally type for that? From what I've seen different img files use different commands
Click to expand...
Click to collapse
fastboot flash boot boot.img
By the way, the guide you were following is outdated and has an old version of the kernel, that's why you went into a bootloop.
Sent from my C6603 using Tapatalk

kingvortex said:
fastboot flash boot boot.img
By the way, the guide you were following is outdated and has an old version of the kernel, that's why you went into a bootloop.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
It booted properly. Thanks. So from there it's just installing zip? Or are there any other steps?

Flash a SuperSu zip and you're rooted. Simple as that.
I suggest this one - SuperSU zip.
Sent from my C6603 using Tapatalk

kingvortex said:
Flash a SuperSu zip and you're rooted. Simple as that.
I suggest this one -
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
It still gives me a black screen when I reboot and go past the sony startup screen. How long does it usually take?

Rare Devil said:
It still gives me a black screen when I reboot and go past the sony startup screen. How long does it usually take?
Click to expand...
Click to collapse
http://d-h.st/UP0
this help me, but back me to KK 4.4.4, but i have my sony back

Bootloader flashfail

I made a mistake and did not turn on the debug mode. So when trying to unlock the bootloader using the tool here:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
it dint work. Now I keep getting "UTAG "flashfail" configured as fastboot" error. I have searched the forums and it seems I need to reflash the motorola boot img to get it to work.
Someone please help me out with it. I am on the latest 5.0.2 update for XT1068 - Indian version.

vicky_ag said:
I made a mistake and did not turn on the debug mode. So when trying to unlock the bootloader using the tool here:
http://forum.xda-developers.com/moto-g-2014/development/ultimate-moto-g-2014-toolkit-t2979862
it dint work. Now I keep getting "UTAG "flashfail" configured as fastboot" error. I have searched the forums and it seems I need to reflash the motorola boot img to get it to work.
Someone please help me out with it. I am on the latest 5.0.2 update for XT1068 - Indian version.
Click to expand...
Click to collapse
ok download the boot.img and use mfastboot to flash

reefuge said:
ok download the boot.img and use mfastboot to flash
Click to expand...
Click to collapse
Links to the boot image please

vicky_ag said:
Links to the boot image please
Click to expand...
Click to collapse
heres a flashable zip if you have custom recovery, or just use the boot.img (5.0.2) from unzipped file
Code:
mfastboot.exe flash boot boot.img

That worked. But now having another issue
I have rooted a lot of phones but this is the first I am stumbling my way through it. I unlocked the bootloader by going to Motorola's site and then went ahead and tried to root the phone using the tool mentioned in original post.
So the tool pushes the boot.img and reboots the phone. Then even when the phones boots in TWRP, the computer keeps saying waiting for device.
Now when I try to do a normal boot, I get the warning from Motorola but then phone wont bootup. No matter how much I wait or even try to re-flash the above image.

vicky_ag said:
That worked. But now having another issue
I have rooted a lot of phones but this is the first I am stumbling my way through it. I unlocked the bootloader by going to Motorola's site and then went ahead and tried to root the phone using the tool mentioned in original post.
So the tool pushes the boot.img and reboots the phone. Then even when the phones boots in TWRP, the computer keeps saying waiting for device.
Now when I try to do a normal boot, I get the warning from Motorola but then phone wont bootup. No matter how much I wait or even try to re-flash the above image.
Click to expand...
Click to collapse
Please don't use mfastboot. It is known for having problems with latest Android versions. You can use Minimal adb and fastboot or the the latest Android SDK.
Next make sure you have flashed the latest TWRP 2.8.4.0.
Wipe everything in twrp. Cache, dalvik and data.
MTP is a bit messed up (not just on our devices). Go to mount, disable mtp, unmount everything, connect usb and enable MTP. Now your device should appear on your computers file manager.
One last thing. Unless you flash the latest SuperSU 2.4.5, stock Lollipop will automatically remove twrp and reinstall stock recovery on the next boot (Actually there is another way. But why would you want to install TWRP without rooting the phone).

doppelhelix said:
Please don't use mfastboot. It is known for having problems with latest Android versions. You can use Minimal adb and fastboot or the the latest Android SDK.
Next make sure you have flashed the latest TWRP 2.8.4.0.
Wipe everything in twrp. Cache, dalvik and data.
MTP is a bit messed up (not just on our devices). Go to mount, disable mtp, unmount everything, connect usb and enable MTP. Now your device should appear on your computers file manager.
One last thing. Unless you flash the latest SuperSU 2.4.5, stock Lollipop will automatically remove twrp and reinstall stock recovery on the next boot.
Click to expand...
Click to collapse
Oh. After many tries now I am stuck in a bootloop. The phones goes to the "warning" then reboots for 5-6 times before it actually starts up. So I am wondering what will be the correct way to go about rooting and clearing this mess. And I see only SuperSu 2.4.0 in play store. has there been a latest version?

vicky_ag said:
The phones goes to the "warning" then reboots for 5-6 times
Click to expand...
Click to collapse
That's because off the outdated SuperSU. Get the latest .zip here http://forum.xda-developers.com/showthread.php?p=23427715

doppelhelix said:
That's because off the outdated SuperSU. Get the latest .zip here http://forum.xda-developers.com/showthread.php?p=23427715
Click to expand...
Click to collapse
So I went this way. I installed the recovery using the tool mentioned in the op. Installed SuperSU latest. Still when I go to bootloader and try recovery, nothing happens. I booted up the phone to see if SuperSU is installed and it appears fine in the apps. But the recovery wont load no matter what.
Another strange thing even when I am connected on 3G, I am not getting the icon.

vicky_ag said:
So I went this way. I installed the recovery using the tool mentioned in the op. Installed SuperSU latest. Still when I go to bootloader and try recovery, nothing happens. I re-tried installing recovery, still no go.
Click to expand...
Click to collapse
Then how did you install SuperSU if you can't get into recovery?

doppelhelix said:
Then how did you install SuperSU if you can't get into recovery?
Click to expand...
Click to collapse
I got in the first time using the tool mentioned in the op. I checked and it uses the command:
fastboot.exe boot twrp.img
This causes the phone to boot into twrp and I can copy the SuperSU to install. But the recovery still doesn't work.

vicky_ag said:
I got in the first time using the tool mentioned in the op. I checked and it uses the command:
fastboot.exe boot twrp.img
This causes the phone to boot into twrp and I can copy the SuperSU to install. But the recovery still doesn't work.
Click to expand...
Click to collapse
What are you talking about. TWRP is the recovery.
---------- Post added at 10:08 ---------- Previous post was at 10:06 ----------
Oh sorry. Now I understand. Please use this commands:
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img

doppelhelix said:
What are you talking about. TWRP is the recovery.
Click to expand...
Click to collapse
Ok so this is what has happened:
1. I use the tool mentioned which uses the command:
fastboot.exe boot twrp.img
2. This causes the phone to boot into TWRP recovery. Then I installed SuperSU.
3. Rebooted the phone completely and checked the version of SuperSU.
4. Again went to the bootloader menu, selected TWRP. Nothing happens at this setup. phone doesn't boot at all. on clicking the power button it goes into normal boot
5. I tried going to the bootloader menu and running.
fastboot.exe flash recovery twrp.img
still no luck. Again trying to go from the bootloader menu to recoery yields no boot up.

vicky_ag said:
Ok so this is what has happened:
1. I use the tool mentioned which uses the command:
fastboot.exe boot twrp.img
2. This causes the phone to boot into TWRP recovery. Then I installed SuperSU.
3. Rebooted the phone completely and checked the version of SuperSU.
4. Again went to the bootloader menu, selected TWRP. Nothing happens at this setup. phone doesn't boot at all. on clicking the power button it goes into normal boot
5. I tried going to the bootloader menu and running.
fastboot.exe flash recovery twrp.img
still no luck. Again trying to go from the bootloader menu to recoery yields no boot up.
Click to expand...
Click to collapse
You are overriding the boot image with the recovery. The correct commands are
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img

doppelhelix said:
You are overriding the boot image with the recovery. The correct commands are
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Just tried that:
C:\fastboot>fastboot.exe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 0.496s]
writing 'boot'...
OKAY [ 0.438s]
finished. total time: 0.944s
C:\fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (9696 KB)...
OKAY [ 0.463s]
writing 'recovery'...
OKAY [ 0.433s]
finished. total time: 0.903s
Click to expand...
Click to collapse
Still when I go to the bootloader and select recovery, phone doesn't boot up at all.

vicky_ag said:
Just tried that:
Still when I go to the bootloader and select recovery, phone doesn't boot up at all.
Click to expand...
Click to collapse
Ok. Let's try this.
Can you boot normally into android? If so, please look if SuperSU is installed. If so, go to play store and install Android Terminal Emulator.
Open it and type
Code:
su
Supersu should pop up. Allow root.
Next type
Code:
reboot recovery
The device should boot into recovery. ( some people have this problem)

doppelhelix said:
Ok. Let's try this.
Can you boot normally into android? If so, please look if SuperSU is installed. If so, go to play store and install Android Terminal Emulator.
Open it and type
Code:
su
Supersu should pop up. Allow root.
Next type
Code:
reboot recovery
The device should boot into recovery. ( some people have this problem)
Click to expand...
Click to collapse
Thanks that works

vicky_ag said:
Thanks that works
Click to expand...
Click to collapse
Nice. Until you can go directly to the recovery, be very carefull not to leave the recovery without having flashed a rom and SuperSU. Also make sure that you grant adb access by accepting the RSA key when connecting the device with your computer. Just in case.

doppelhelix said:
Nice. Until you can go directly to the recovery, be very carefull not to leave the recovery without having flashed a rom and SuperSU. Also make sure that you grant adb access by accepting the RSA key when connecting the device with your computer. Just in case.
Click to expand...
Click to collapse
I am actually fine with a stock ROM on Motorola for now. They have lesser fluff than samsung et al. The major reason for trying to root the phone was to get TitanBackup working, I have been preserving some apps at a particular version in my last phone. The only way I found to restore the app and data was to use TitanBackup. The whole unlock the bootloader was because of Motorola adding a step to do this.
Adding recovery was an addition just in case Motorola forgets about us 1 year down the line. Then might flash to CM or something

Recoveries gone

Hi,
Well, I do have one recovery - cyanogen recovery, all others are gone.
With cyanogen I can't flash gapps or tangerine kernel,so I need my old ones back.
How it happened? Flashed FlexOS,after reboot they were gone, replaced by cyanogen recovery.
Any help would be appreciated.
Thanks

jaretti said:
Hi,
Well, I do have one recovery - cyanogen recovery, all others are gone.
With cyanogen I can't flash gapps or tangerine kernel,so I need my old ones back.
How it happened? Flashed FlexOS,after reboot they were gone, replaced by cyanogen recovery.
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Use Rashr app from playstore to flash twrp or philZ

don't have app store, in fact don't have any gapps as cannot install them in cyogen recovery. when download apk. file get "Cant open" message.

jaretti said:
don't have app store, in fact don't have any gapps as cannot install them in cyogen recovery. when download apk. file get "Cant open" message.
Click to expand...
Click to collapse
you have to install tangerine if you use lollipop ....go into fastboot mode flash the kernel via fastboot ..reboot and you have twrp or philz

Is it possible that I've lost root? Cause that what root checker says.
P.s. managed to install gapps,will try flashing kernel like suggested tomorrow. Any links on how to do it?
Thanks guys

jaretti said:
Is it possible that I've lost root? Cause that what root checker says.
P.s. managed to install gapps,will try flashing kernel like suggested tomorrow. Any links on how to do it?
Thanks guys
Click to expand...
Click to collapse
i have did this from a long time so forgive if it didn't work for you>>> form pc download this zip that i uploaded it for you(https://mega.co.nz/#!y51TmaJR!gSWCWbF_6d3JKbkyjgNzhdfBoKakFvNCCFFvBfRl-cY) extract to C:\fastboot then move the kernel.elf if is it tangerine it will be like this (tangerine.elf)>>>press ctrl+shift on the keyboard and then press open command window here then type: fastboot flash boot (the kernel name.elf) when it's done type fastboot reboot
example: fastboot flash boot tangerine.elf
p.s you have to install the drivers for you phone google it or maybe(Connect your Xperia SP via USB. (Don't forget to enable USB Debugging)
Then run the Software (http://adbdriver.com/downloads/) and choose ur phone, which should be listed in the list.
i hope i helped with this if it didn't work so i'm sorry my friend for wasting your time
good luck :good:

Hi, it's all sorted now.
if someone have same problem this is what I've done:
installed gapps aroma as other packages wouldn't install from cyanogen recovery, then flashed super su also from recovery. after that I was able to install phillz recovery using rashr app from Google store. then from phillz installed tangerine kernel. all good now,
thanks everyone!

P9 bricked please help

Hi Guys,
My friend bricked his phone. Im trying to recover it. Its a VNS-L21.
I tried putting the stock rom on it using dload method from
https://boycracked.com/2016/09/13/official-huawei-p9-lite-vns-l21-stock-rom/amp/
and
http://huafirmware.com/8-firmware/16-huawei-p9-lite-vns-l21
but the upgrade fails everytime saying incompatible.
any help is appreciated :fingers-crossed:

My fix for the issue
malikusmanrasheed said:
Hi Guys,
My friend bricked his phone. Im trying to recover it. Its a VNS-L21.
I tried putting the stock rom on it using dload method from
https://boycracked.com/2016/09/13/official-huawei-p9-lite-vns-l21-stock-rom/amp/
and
http://huafirmware.com/8-firmware/16-huawei-p9-lite-vns-l21
but the upgrade fails everytime saying incompatible.
any help is appreciated :fingers-crossed:
Click to expand...
Click to collapse
Hey man, I got a problem just like you and this is the way I fixed it.
Download the Huawei update extractor:
https://forum.xda-developers.com/showthread.php?t=2433454
And use this to open your Update.app you already downloaded.
Extract the 'boot.img' and the 'system.img'.
Now you need fastboot, follow this tutorial:
https://www.xda-developers.com/xda-...tall-adb-and-fastboot-system-wide-in-windows/
Now open terminal/cmd/powershell and open the folder the boot.img and system.img you extracted are in.
Connect your phone in fastboot and run the following commands:
fastboot flash system [Extracted_System.Img]
fastboot flash boot [Extracted_Boot.img]
fastboot reboot
This resolved the issue for me, I hope also for you!

JatanX said:
Hey man, I got a problem just like you and this is the way I fixed it.
Download the Huawei update extractor:
https://forum.xda-developers.com/showthread.php?t=2433454
And use this to open your Update.app you already downloaded.
Extract the 'boot.img' and the 'system.img'.
Now you need fastboot, follow this tutorial:
https://www.xda-developers.com/xda-...tall-adb-and-fastboot-system-wide-in-windows/
Now open terminal/cmd/powershell and open the folder the boot.img and system.img you extracted are in.
Connect your phone in fastboot and run the following commands:
fastboot flash system [Extracted_System.Img]
fastboot flash boot [Extracted_Boot.img]
fastboot reboot
This resolved the issue for me, I hope also for you!
Click to expand...
Click to collapse
Hi Jatan,
Thanks for the reply. I tried that as well with a couple of stock images but all i got was a blank screen. Can you share the stock image that you used?
:good:

for most Stock images when i try to "Fastboot flash system d:\System.img" ( system.img is in D: in my case), i get this error
FAILED (remote: sparse flash write failure)

malikusmanrasheed said:
for most Stock images when i try to "Fastboot flash system d:\System.img" ( system.img is in D: in my case), i get this error
FAILED (remote: sparse flash write failure)
Click to expand...
Click to collapse
How did he brick it? What was he specifically doing (nougat update etc.)? Do you get the same error when you try and flash a boot image, stock recovery or other partitions?
Can you install twrp? If so, try wiping the system & boot partitions in twrp, then try flashing boot & system again in fastboot. If he'd updated to nougat, then you'll need to try and flash the rollback package first then dload a Marshmallow rom and go from there

I would suggest using this tool:
https://forum.xda-developers.com/p9/development/huawei-p9-eva-l09-eva-l19-eva-l29-tool-t3591358
to install this tool to unlock bootloader and install twrp.
After unlocking your bootloader everything on your phone is gone though.
Then in twrp you can try to repair your your partitians by going to wipe->advanced wipe->repair or change...
And thereafter continue with the steps is provided earlier or install a new rom, this is up to you.
I hope it fixes it for you.

colthekid said:
How did he brick it? What was he specifically doing (nougat update etc.)? Do you get the same error when you try and flash a boot image, stock recovery or other partitions?
Can you install twrp? If so, try wiping the system & boot partitions in twrp, then try flashing boot & system again in fastboot. If he'd updated to nougat, then you'll need to try and flash the rollback package first then dload a Marshmallow rom and go from there
Click to expand...
Click to collapse
Hi colthekid,
He just went nuts and wiped everything he could see in the twrp.
After that I have tried to write this via the method jatan suggested:
VNS-L21C185B360
from http://www.stechguide.com/download-huawei-p9-lite-b360-nougat-update/
still no boot.

JatanX said:
I would suggest using this tool:
https://forum.xda-developers.com/p9/development/huawei-p9-eva-l09-eva-l19-eva-l29-tool-t3591358
to install this tool to unlock bootloader and install twrp.
After unlocking your bootloader everything on your phone is gone though.
Then in twrp you can try to repair your your partitians by going to wipe->advanced wipe->repair or change...
And thereafter continue with the steps is provided earlier or install a new rom, this is up to you.
I hope it fixes it for you.
Click to expand...
Click to collapse
I'l try that and update.

i have twrp. repaired the partitions. did the flast via fast boot using the above method
"Now open terminal/cmd/powershell and open the folder the boot.img and system.img you extracted are in.
Connect your phone in fastboot and run the following commands:
fastboot flash system [Extracted_System.Img]
fastboot flash boot [Extracted_Boot.img]
fastboot reboot"
and still the same. It flashes the files fine. but at boot i get a black screen.
I think im using the wrong files. Can anyone please share the link for a full stock rom nougat , or a roll back from nougat to mm (i flashed this VNS-L21C185B360 latest)

or maybe i need to do write the oeminfo or something. Read it somewhere. not clear on what it is

malikusmanrasheed said:
I think im using the wrong files. Can anyone please share the link for a full stock rom nougat , or a roll back from nougat to mm (i flashed this VNS-L21C185B360 latest)
Click to expand...
Click to collapse
Maybe you need to continue this in the P9 Lite forum?
However, in the meantime, this should help you along!!
Firmware... https://forum.xda-developers.com/hu...huawei-p9-lite-firmware-compilations-t3517124 (pick a full MM rom)
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)

colthekid said:
Maybe you need to continue this in the P9 Lite forum?
However, in the meantime, this should help you along!!
Firmware... https://forum.xda-developers.com/hu...huawei-p9-lite-firmware-compilations-t3517124 (pick a full MM rom)
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)
Click to expand...
Click to collapse
This:
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)
solved my problem.
Putting the puzzle back again:
I think the genius removed the oeminfo along with everything else he could see in the twrp wipe menu.
I tried to put multiple firmwares on the device nougat ( as he updated) but the boot still showed blank.
As soon as i flashed the oeminfo --> then MM firmware, the device booted up.
Thank you so much everyone for your help. Really appreciate it :good::good::good::good::good::good:

Excellent! :good::good:
And I'm sure your friend is glad to have a working phone again!
Explains why dload wouldn't work as well. As far as I'm aware the update.app checks oeminfo to make sure the firmware is compatible. Hence if you want to debrand a phone to C432, you have to flash a C432 oeminfo before the C432 update.app will flash successfully. No oeminfo=no compatibility for anything!!!

hi,
please help unbrick my P9
I can't get into fastboot, the only one thing it boots is the eRecovery, (system partition damaged)
---------- Post added at 04:26 AM ---------- Previous post was at 04:11 AM ----------
konstwww said:
hi,
please help unbrick my P9
I can't get into fastboot, the only one thing it boots is the eRecovery, (system partition damaged)
Click to expand...
Click to collapse
somehow i managed to get to fastboot but trying to flash system get error
sending sparse 'system' (449861 KB)...
OKAY [ 14.749s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.142s
Update: To get into fastboot is very important that smartphone is connected via USB to PC, then Power-button and VolumeDown together till Phone gets into fastboot.
from there flash TWRP, and reboot to recovery, after that install full Update (Files and guideline is here in first post part 3 and 4 https://forum.xda-developers.com/p9/development/rom-huawei-p9-magic-rainbow-t3601064).

malikusmanrasheed said:
This:
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)
solved my problem.
Putting the puzzle back again:
I think the genius removed the oeminfo along with everything else he could see in the twrp wipe menu.
I tried to put multiple firmwares on the device nougat ( as he updated) but the boot still showed blank.
As soon as i flashed the oeminfo --> then MM firmware, the device booted up.
Thank you so much everyone for your help. Really appreciate it :good::good::good::good::good::good:
Click to expand...
Click to collapse
Can you please send me your full steps. I really need it

[GUIDE] Fix TWRP Recovery Script Loop & Unable to boot

Hello!
This is actually a common "thing" across many devices so just because this thread is on the Oneplus 5 forum doesn't mean it won't work for your device!
So I know exactly what you're going through....
THE PROBLEM
You've flashed a Zip file, everything seemed to work fine, you pressed the reboot button.... But then... Black screen, blue LED (or something like that)....
You then try to reboot to recovery and then you see "Running Open Recovery Script" and you manage to decipher "Wiping Data", either you clean flashed your ZIP file and this is not a problem or you dirty flashed it and so you're screaming at your phone because it just wiped everything without you asking (I mean, this never happened to me or anything I'm just trying to imagine what it would look like :crying
You then try a few things but you're phone won't even get close to the Bootanimation and keeps trying to boot up into recovery and keeps on Wiping your data which is now non-existent.
THE FIX :fingers-crossed:
Method 1/
This is the most convenient and easiest method but it might not work for you, I'm not even entirely sure how I made it work for me... Anyway:
Once the phone has booted up into recovery and is flashing the ZIP, try the following:
WILL UPDATE AS SOON AS I FIND THE EXACT METHOD
-Taking a screenshot (Power+volume)
-Pressing the back, home and récents button as many times as you can
-Pressing the power button
Basically, for now until I'm certain on what gets you out of this script thing, press every button on the phone a few times (that's what I did)
Click to expand...
Click to collapse
Method 2 [FAILSAFE]/
This method will work no matter what (if your problem is the one this thread covers that is), but it's quite teedious!
Step1/ Boot into the Bootloader (Power+Volume up)
Step2/ Install ADB & Fastboot on your PC (Google)
Step3/Download Stock recovery & TWRP
Step 4/Move both files to the ADB folder for ease of access
Step5/Type in
Code:
fastboot flash recovery STOCK_RECOVERY.img
(change file name)
Step 6/Boot into this new recovery
Step 7/ Ponder for a minute at how useless it is
Step 8/Boot into Bootloader again
Step 9/Type into terminal
Code:
fastboot flash recovery TWRP_RECOVERY.img
(change file name)
Step 10/Boot into recovery and wipe everything except Internal storage
Step 11/Flash ROM again!
VOILA! :fingers-crossed:
Hope it helped, if you have any questions, feel free to ask me!
Cheers, Matt

I had this issue when I was flashing various roms, in my case it ended up being that some of the roms were incompatible with data being formatted as ext4 (mainly oos based ones, but a few others as well) since I went full f2fs, haven't seen this issue. That might be something to consider adding, it's pretty destructive, though, as going with f2fs on /data formats /sdcard, too

I had this issue when I was flashing various roms (xXx NoLimits, ExperienceOS) on the encrypted data partition. Only FreedomOS flashing and booting ok

dragynbane222 said:
I had this issue when I was flashing various roms, in my case it ended up being that some of the roms were incompatible with data being formatted as ext4 (mainly oos based ones, but a few others as well) since I went full f2fs, haven't seen this issue. That might be something to consider adding, it's pretty destructive, though, as going with f2fs on /data formats /sdcard, too
Click to expand...
Click to collapse
Ahh, that's interesting

R0iZ said:
I had this issue when I was flashing various roms (xXx NoLimits, ExperienceOS) on the encrypted data partition. Only FreedomOS flashing and booting ok
Click to expand...
Click to collapse
I had it on my old phone once (Oneplus X) so it's not rom/device specific... And I don't think it's a bug, more a compatibility issue...

first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5

Fyzik753 said:
first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5
Click to expand...
Click to collapse
You can't boot into bootloader? Are you sure? Long less power + Volume up

Fyzik753 said:
first method doesnt work for me (and i have not expecting it to work)
second method should work but i have a little problem, i cant boot into bootloader
can someone help me with this
phone: Doogee X5
Click to expand...
Click to collapse
Are you trying to install/fix TWRP designed for OnePlus 5 into a different phone? Good luck!

i have a problem with instaling twrp ...
example:
phone have bootloader unlocked
flashing original 4.5.14 firmware .... all good ... boot phone ... settings ... done
reboot to bootloader ... flash twrp (or blu_spark twrp) ... done ... reboot to twrp .. all good
reboot to system ... done. poweroff (or restart)...
boot to recovery ... surprise ... original recovery ... not twrp
flash again twrp ... done ... boot to system ... reboot to recovery ... original recovery ....
saw .. what is going on ?
thanks

aoprea said:
i have a problem with instaling twrp ...
example:
phone have bootloader unlocked
flashing original 4.5.14 firmware .... all good ... boot phone ... settings ... done
reboot to bootloader ... flash twrp (or blu_spark twrp) ... done ... reboot to twrp .. all good
reboot to system ... done. poweroff (or restart)...
boot to recovery ... surprise ... original recovery ... not twrp
flash again twrp ... done ... boot to system ... reboot to recovery ... original recovery ....
saw .. what is going on ?
thanks
Click to expand...
Click to collapse
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..

iamelton said:
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..
Click to expand...
Click to collapse
thanks ... solved with install magisk
ps. I was accustomed with samsung phones where this does not happen...

Hi, I hope there's somebody who can help me with this.
I think, method could help me, but when I try to flash the recovery, I get this message:
Code:
target reported max download size of 535822336 bytes
sending 'recovery' (27525 KB)...
OKAY [ 0.914s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.954s
Any Ideas to solve this?

iamelton said:
OxygenOS overwrites the recovery with stock one when you boot into the OS..
to avoid this, after flashing twrp, (without rebooting to system) flash SuperSU or Magisk immediately..
Click to expand...
Click to collapse
i have op5
i don't know what should i do - i install magisk and twrp - is it in the twrp i do that i wipe and i flash rom
but i find the some problem open and after boot i don't found the twrp and my recovery return to official recov
please help
my phone without root is worthless

Im_Mattgame said:
Hello!
This is actually a common "thing" across many devices so just because this thread is on the Oneplus 5 forum doesn't mean it won't work for your device!
So I know exactly what you're going through....
THE PROBLEM
You've flashed a Zip file, everything seemed to work fine, you pressed the reboot button.... But then... Black screen, blue LED (or something like that)....
You then try to reboot to recovery and then you see "Running Open Recovery Script" and you manage to decipher "Wiping Data", either you clean flashed your ZIP file and this is not a problem or you dirty flashed it and so you're screaming at your phone because it just wiped everything without you asking (I mean, this never happened to me or anything I'm just trying to imagine what it would look like :crying
You then try a few things but you're phone won't even get close to the Bootanimation and keeps trying to boot up into recovery and keeps on Wiping your data which is now non-existent.
THE FIX :fingers-crossed:
Method 1/
This is the most convenient and easiest method but it might not work for you, I'm not even entirely sure how I made it work for me... Anyway:
Once the phone has booted up into recovery and is flashing the ZIP, try the following:
Method 2 [FAILSAFE]/
This method will work no matter what (if your problem is the one this thread covers that is), but it's quite teedious!
Step1/ Boot into the Bootloader (Power+Volume up)
Step2/ Install ADB & Fastboot on your PC (Google)
Step3/Download Stock recovery & TWRP
Step 4/Move both files to the ADB folder for ease of access
Step5/Type in
Code:
fastboot flash recovery STOCK_RECOVERY.img
(change file name)
Step 6/Boot into this new recovery
Step 7/ Ponder for a minute at how useless it is
Step 8/Boot into Bootloader again
Step 9/Type into terminal
Code:
fastboot flash recovery TWRP_RECOVERY.img
(change file name)
Step 10/Boot into recovery and wipe everything except Internal storage
Step 11/Flash ROM again!
VOILA! :fingers-crossed:
Hope it helped, if you have any questions, feel free to ask me!
Cheers, Matt
Click to expand...
Click to collapse
You saved me bro my life is your from now thankyou love u♥