Database Info

[Q] Flashed the LPX13D image and now my recovery is gone.

Hi Guys,
Hoping you can help me with this.
I was originally running Slimkat 4.4.4 and had the latest TWRP installed.
I downloaded the file for LPX13D and extracted all of the files right down to the Flash-all.bat and the images for bootloader, radio, and the system.
I ran the Flash-all.bat, and it installed everything successfully. The device booted, and voila, I am on 5.0 now.
The problem now, is that when I reboot into recovery, I am instead met with the little android guy laying on his back, with a red triange/exclamation point in his chest.
No problem, I say to myself. I'll just flash TWRP manually.
So I go to the bootloader, and try the command fastboot flash recovery recovery.img (renamed to make it faster to type.)
It goes through the motions, and says it was successful.
But when I go to recovery, it's the same red triange guy still.
I tried pressing volume up, power+volume up, etc. No dice. After about 30 seconds, it reboots on it's own back to system.
When I connect it to the Nexus Root Toolkit, and click on Flash recovery, and then choose TWRP latest, I get a window that pops up that tells me :
______
File Dependency Download
Status: Stock Kernel: Not Present - Need to download (this is in red)
Then a button that says "Download + Update All File Dependencies"
So what's my best option here? Should I let the NRT update the dependencies?

Try to flash cwm and tell me what happens

Isus <3 said:
Try to flash cwm and tell me what happens
Click to expand...
Click to collapse
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.

deleted

Stupendousman2012 said:
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
Click to expand...
Click to collapse
Twrp is not optimized yet well like cwm is for andorid l

Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Lethargy said:
I flashed the new developer preview for 5 minutes or so then went to revert. Recovery wouldn't boot not matter what I flashed, until I flashed a KK userdata.img. So it seems like the new developer preview changes the internal storage/data partition more then the old one.
Click to expand...
Click to collapse
Don't try getting around it. Nothing to do with anything else.
Isus <3 said:
Twrp is not optimized yet well like cwm is for andorid l
Click to expand...
Click to collapse
What? CWM is outdated.

Lethargy said:
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Don't try getting around it. Nothing to do with anything else.
What? CWM is outdated.
Click to expand...
Click to collapse
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
I also flashed the boot.img and the supersu update to get root working, and it seems to be going well now.
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.

Stupendousman2012 said:
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
Click to expand...
Click to collapse
Flash userdata.img and your TWRP will work properly.
Stupendousman2012 said:
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
Click to expand...
Click to collapse
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
Stupendousman2012 said:
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Click to expand...
Click to collapse
It says that because CWM is outdated.

Lethargy said:
Flash userdata.img and your TWRP will work properly.
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
It says that because CWM is outdated.
Click to expand...
Click to collapse
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?

Stupendousman2012 said:
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Click to expand...
Click to collapse
Yeah. Don't need to boot into recovery and wipe data since flashing a .img with fastboot while in bootloader erases it first then flashes. Just make sure you backup your stuff, including internal storage, off to a PC first if you have anything important.

Until L is officially released, we're using the below thread
http://forum.xda-developers.com/show....php?t=2796217
Android "L" Developer Preview Help, Troubleshooting, Q&A
Sent from my Nexus 5 using Tapatalk

HELP! Nvidia Shield OEM 6.0 NO RECOVERY! NO ROOT!

Hi, everybody, I am having problems with my nvidia shield tablet, it seems that after I had updated to android 6.0 I lost my custom recovery, and the original recovery is not there. Therefore I cannot update to 6.0.1, i cannot root, and my computer does not recognize the tablet when i go into the bootloader. Please help!

Are you able to turn off the tablet and use the volume keys to get into bootloader/fastboot mode? You can fastboot flash recovery from there.
Sent from my Nexus 6 using XDA-Developers mobile app

Are you able to turn off the tablet and use the volume keys to get into bootloader/fastboot mode? You can fastboot flash recovery from there.
Sorry it took so long to reply, yes, I can get into the boot loader. I can even fastboot, but my computer can't seem to communicate to my tablet once its in Fastboot/bootloader so every time I try to do as you said. My computer can't send the commands because it doesn't recognize the tablet.

Update drivers

I also lost twrp and root after the full OTA update. I tried to fastboot flash recovery back, but when I reboot into recovery it says "no command". How can I fix this? Its seems as if the recovery partition is gone? Thanks for any help.

That is stock recovery

lafester said:
That is stock recovery
Click to expand...
Click to collapse
How can I get TWRP to flash then? I am getting this:
Code:
sudo ./fastboot flash recovery recovery.img
[sudo] password:
target reported max download size of 100663296 bytes
sending 'recovery' (7228 KB)...
OKAY [ 0.353s]
writing 'recovery'...
OKAY [ 0.334s]
finished. total time: 0.687s
It finishes too fast to actually do anything. I have tried both 3.0.0 and 3.0.2 twrp for MM. I would appreciate any suggestions on how to fix this. Thanks.

You renamed twrp to recovery? If so you did flash it. Do you reboot directly into recovery?
Sent from my SHIELD Tablet using Tapatalk

Yes I renamed it to recovery.img and rebooted. When I reboot to recovery, it still just says no command.

Are you unlocked?

Yes boot loader shows unlocked

Latest twrp?

Problem with oopof1 phone

Problem with oopof1 phone
I have made Rom for the wrong phone oppof1f and the phone has stopped on this logo
I do not move I have stood on this and I can not enter the recovery permanently, what is the solution?
And sorry if the subject is not in place​

Picture of the problem
store6.up-00.com/2017-05/149603505807811.png

So it looks like its trying to install the rom.
if you cant enter recovery.
extract the recovery.img for the stock rom in the link below
boot into fastboot (power and volume up) then,
fastboot flash recovery recovery.img
if you can enter recovery do this.
Turn off the phone and put this rom for the f1f on the micro sd card.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=46153
then hold the power button and volume down and it should come up with a langauge to pick.
then press install from sd card.
select the rom.
if it fails keep trying. u can also try wiping data and cache

Jamie_oppo said:
So it looks like its trying to install the rom.
if you cant enter recovery.
extract the recovery.img for the stock rom in the link below
boot into fastboot (power and volume up) then,
fastboot flash recovery recovery.img
if you can enter recovery do this.
Turn off the phone and put this rom for the f1f on the micro sd card.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=46153
then hold the power button and volume down and it should come up with a langauge to pick.
then press install from sd card.
select the rom.
if it fails keep trying. u can also try wiping data and cache
Click to expand...
Click to collapse
When you press the power button and the volume down, this message appears
Store6.up-00.com/2017-05/149603505807811.png
And unable to enter into recovery
Unable to access your phone

up up up up

If fastboot mode is working, you can try to boot another recovery (twrp, with fastboot boot twrp.img) and wipe the cache partition (that might have update information on it).
If it's not enough, I'd try to wipe data. But before that, try to backup things while TWRP is working.

tarek.eid said:
up up up up
Click to expand...
Click to collapse
Can you boot unto fast boot using power and volume up?

kdd998 said:
If fastboot mode is working, you can try to boot another recovery (twrp, with fastboot boot twrp.img) and wipe the cache partition (that might have update information on it).
If it's not enough, I'd try to wipe data. But before that, try to backup things while TWRP is working.
Click to expand...
Click to collapse
Yes FastBoot mode works
And when working twrp.img recovery
Of this site
Https://twrp.me/devices/oppof1.html
But there is a problem with the message
Target reported max download size of 268435456 bytes
Sending 'recovery' (25858 KB) ...
OKAY [1.142s]
Writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
Finished. Total time: 1.157s
Can you explain
Clear the cache section

Jamie_oppo said:
Can you boot unto fast boot using power and volume up?
Click to expand...
Click to collapse
Yes I know how to login to FastBoot mode
But this message appears after the steps are executed
Target reported max download size of 268435456 bytes
Sending 'recovery' (25858 KB) ...
OKAY [1.142s]
Writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
Finished. Total time: 1.157s

tarek.eid said:
Yes I know how to login to FastBoot mode
But this message appears after the steps are executed
Target reported max download size of 268435456 bytes
Sending 'recovery' (25858 KB) ...
OKAY [1.142s]
Writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
Finished. Total time: 1.157s
Click to expand...
Click to collapse
Type fastboot oem unlock then repeat

Jamie_oppo said:
Type fastboot oem unlock then repeat
Click to expand...
Click to collapse
This message has not been opened
FAILED (remote: oem unlock is not allowed)
Finished. Total time: 0.009s

tarek.eid said:
This message has not been opened
FAILED (remote: oem unlock is not allowed)
Finished. Total time: 0.009s
Click to expand...
Click to collapse
Looks like you have a locked bootloader with unlocking disabled via developer options. With bootloader locked,no recovery and cant boot to rom to enable bootloader unlocking you only real option is to follow instuctions in this post to flash back to original stock firmware using low level QDloader to flash entire phone in factory mode.
PS This is only for f1f not f1s. You do have a f1f, right?

MiniBlu said:
Looks like you have a locked bootloader with unlocking disabled via developer options. With bootloader locked,no recovery and cant boot to rom to enable bootloader unlocking you only real option is to follow instuctions in this post to flash back to original stock firmware using low level QDloader to flash entire phone in factory mode.
PS This is only for f1f not f1s. You do have a f1f, right?
Click to expand...
Click to collapse
Yes my phone is f1f
I will carry
Https://drive.google.com/file/d/0B3vGskcdFbBcVThPS3FIb2dkdGs/view?usp=drivesdk
I will try
Take you

There is a problem with these definitions
Qualcomm HS-USB QDLoader 9008 (COM5
A triangle sign appears that needs to be defined
Does this affect
Even if it has a possible impact on its definition

tarek.eid said:
There is a problem with these definitions
Qualcomm HS-USB QDLoader 9008 (COM5
A triangle sign appears that needs to be defined
Does this affect
Even if it has a possible impact on its definition
Click to expand...
Click to collapse
You need to follow the instruction in the post I linked and "Install the QDLoader driver found in the DRIVER directory of the extracted archive". If its using the correct drivers the triangle should not be there. (you mean in contol panel?)
If you have problems PM the quy who posted the link. He said he would help.

OPO A001 Cannot Boot in TWRP

Hello All,
I tried many ROMs but somehow now I am not able to boot in TWRP after flashing it.
Not able to add image here.
Command used is fastboot flash recovery twrp-2.8.6.0-bacon.img
target reported max download size of 536870912 bytes
sending recovery (10180 KB)
OKAY [ 0.368s]
writing recovery
OKAY [ 0.186s]
finished total time 0.554s
I can boot in fastboot mode. Any help would be appreciates. Thanks

Sanjay13 said:
Hello All,
I tried many ROMs but somehow now I am not able to boot in TWRP after flashing it.
Not able to add image here.
Command used is fastboot flash recovery twrp-2.8.6.0-bacon.img
target reported max download size of 536870912 bytes
sending recovery (10180 KB)
OKAY [ 0.368s]
writing recovery
OKAY [ 0.186s]
finished total time 0.554s
I can boot in fastboot mode. Any help would be appreciates. Thanks
Click to expand...
Click to collapse
Boot into twrp just after you flash it.And flash latest twrp this time.
I recommend @kutep0v 's twrp.

Mr.Ak said:
Boot into twrp just after you flash it.And flash latest twrp this time.
I recommend @kutep0v 's twrp.
Click to expand...
Click to collapse
hello,
I am getting a error
booting
Failed ( remote:dtb not found)

Sanjay13 said:
hello,
I am getting a error
booting
Failed ( remote:dtb not found)
Click to expand...
Click to collapse
You mean a error while flashing recovery?

Just after flashing, long press volume down plus power button to restart & get into recovery.
In case problem persists, memory could be corrupted.
You might need to start afresh installing cm13 snapshot. That'll wipe your phone internal memory as well.

kapil_dheer said:
Just after flashing, long press volume down plus power button to restart & get into recovery.
In case problem persists, memory could be corrupted.
You might need to start afresh installing cm13 snapshot. That'll wipe your phone internal memory as well.
Click to expand...
Click to collapse
Thanks Kapil. I could resolve the problem myself. I did a instaal cm13 using the below link.
http://tweakguy.com/return-your-oneplus-one-to-full-stock/
Then flashed TWRP and then had the ROM installed. Guess now I can flash anything for OPO.
Well my due credit to TweakGuy and also to DeadlyIndian for the ROM below having the latest Oxygen and Marshmellow
https://forum.xda-developers.com/oneplus-one/development/rom-oxygenos-3-1-2-t3470907
Thanks once again to all who read this.

Twrp touchscreen not working.

First time trying to root, in order to install magisk and to get the full functionality of Edge sense +.
I was following this guide:
www-DOT-theandroidsoul-DOT-com/htc-u11-root-twrp-recovery-and-bootloader-unlock/
1. I have successfully unlocked bootloader
2. I have installed twrp
After some research, i think i made a mistake here, by installing twrp-3.1.1-0-ocn instead of the 3.2.1.2-ocn.
When booting to recovery mode, TWRP shows up, it asks for a password or to swipe the screen, but the screen is not responsive.
So i tried to flash the newest version of TWRP on top of the old one and i get this error :
PS C:\Users\ilan\Desktop\unlock-bl> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (39676 KB)...
OKAY [ 1.137s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.145s
PS C:\Users\ilan\Desktop\unlock-bl>
How should i proceed?
I thought about going to stock recovery and then try to flash the new version of TWRP, but i didnt do a recovery. I have found that there is a way to recover to stock using something called RRU.
Help will b amazingly appreciated, tnx in advance

U may have already resolved..had same issue. Need to reboot directly to recovery and not via DL menu...then do Install Twrp Image file. Boot phone then if u can reboot directly to recovery go that route. If not try via Cmd Prompt...adb reboot recovery. Either way Twrp screen should be respnsive so u can flash Twrp img.

jelive said:
U may have already resolved..had same issue. Need to reboot directly to recovery and not via DL menu...then do Install Twrp Image file. Boot phone then if u can reboot directly to recovery go that route. If not try via Cmd Prompt...adb reboot recovery. Either way Twrp screen should be respnsive so u can flash Twrp img.
Click to expand...
Click to collapse
This is partially true. If anyone expierience touch screen not working in TWRP after following this tutorial: "theandroidsoul.com htc-u11-root-twrp-recovery-and-bootloader-unlock" - problem is, that old version of TWRP is linked there. You HAVE to download version 3.2 not 3.1 ->eu.dl.twrp.me/ocn/twrp-3.2.1-2-ocn.img.html
when touch screen is not working, use "adb reboot" and then "fastboot flash recovery twrp3.2.img"
it works for me