I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?
BoredDude said:
I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?
Click to expand...
Click to collapse
You can try to boot directly into twrp with "fastboot boot TWRP.img"
zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s
zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
BoredDude said:
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s
Click to expand...
Click to collapse
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!
ChazzMatt said:
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!
Click to expand...
Click to collapse
I fixed it erasing the TWRP folder in my internal storage
Related
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
I decided to reflash TWRP using Fastboot (Yes, it did show up in Fastboot), and I was able to flash it using:
fastboot flash recovery twrp.img
But when I tried to boot from it using: fastboot boot twrp.img
I get the following error:
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (14698 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.274s]
finished. total time: 0.790s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.529s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.578s
plzzzhelp
Hmmmm...i don't think you can't reboot into recovery using fastboot command...you need to use power button + volume down to reboot into recovery manually....
iPusak Gaoq™ said:
Hmmmm...i don't think you can't reboot into recovery using fastboot command...you need to use power button + volume down to reboot into recovery manually....
Click to expand...
Click to collapse
i tried all things..none of them worked..still stucked at oneplus logo..
and i don't have any rom installed..i can only boot into fastboot
battery low!!!!! said:
i tried all things..none of them worked..still stucked at oneplus logo..
and i don't have any rom installed..i can only boot into fastboot
Click to expand...
Click to collapse
re-flash the recovery and don't forget to use this command after flashing recovery....
Code:
fastboot format cache
then reboot to recovery manually....
I have exactly the same problem except I still have a working OS.
After I couldn't boot into recovery I tried to flash a new recovery by using the TWRP app ("flashed successfully"), reboot to the recovery... same thing, it's stuck at the logo. I tried the flashify app as well (flashed successfully)... reboot... same thing.
I also tried to format the cache in fastboot after flashing the recovery which didn't help.
So either I am stuck with this ROM for the rest of my OPOs live or someone can help me.
I am by no means new to flashing. I flash new ROMs since my HTC Desire, I flashed my SGS3 on a weekly basis and I own my OPO since it came out and I never had any problems.
battery low!!!!! said:
i tried all things..none of them worked..still stucked at oneplus logo..
and i don't have any rom installed..i can only boot into fastboot
Click to expand...
Click to collapse
if you don't have ROM installed you can manually flash a a rom from fastboot.
Return your OPO to Stock via fastboot
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
and reinitialize the rooting process, flash Twrp and supersu
Hello,
Edit: Don't know how or why, but after a couple of more tries I was able to boot the recovery directly and flash the rom. So everything is working fine right now. Admin/mod, would you like to close this thread? Thank you
For some reason I wanted to flash a new rom on my XT1039. In the process I screwed up and got it softbricked. I already had a look at the thread started by alfread56 and although the situation seems quite similar, the offered solutions didn't work out for me.
Right now my phone doens't have any rom installed. Flashing twrp with fastboot suggest everything works allright (using a linux system by the way):
fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (8314 KB)...
OKAY [ 0.295s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.598s
After the reboot and holding the buttons for recovery mode I still get the stock recovery screen. When I select recovery in this menu, the phone shuts down. Because I know holding the recovery buttons on reboot takes some timing, I have redone the procedure of flashing twrp and holding the buttons numerous times. But it never went to the twrp recovery.
Then I tried to boot the twrp image directly with
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.290s]
booting...
OKAY [ 0.230s]
finished. total time: 0.520s
Here I made a mistake: I have also flashed the boot partition with the twrp image with fastboot flash boot recovery.img (don't know how much of problem this is).
Booting up the TWRP image works fine. Then I've wiped dalvik, cache, data, internal storage and after several runs also deleted system by accident, and factory reset. When trying to flash the lineage zip everything works out fine for about 1 second, then the screen flashes en the phone is back in the TWRP screen. Too quick for me to see what the output is, but I do see there are not red marked lines (no errors)
I have tried it with several different ROMS (al checked), with several versions of TWRP and with fastboot and mfastboot. Does anybody know a solution on how to get twrp recovery working on my phone, or why I can't flash a rom when I boot twrp directly? Any help is appreciated!
Thank you in advance.
Regards,
weisa4564
I'm trying to obtain root on a Shield K1 that has the latest ota update (5.4).
I've unlocked the bootloader, but the latest TWRP just won't flash, says OK and writes to recovery, but same stock recovery stays there.
Do I need to use an older developer image, one that was released prior to the latest TWRP?
This is what the terminal is giving me:
Code:
[[email protected] tablet ]$ sudo fastboot flash recovery twrp-3.2.1-0-shieldtablet.img
target reported max download size of 100663296 bytes
sending 'recovery' (12426 KB)...
OKAY [ 0.487s]
writing 'recovery'...
OKAY [ 0.506s]
finished. total time: 0.993s
Then, when I reboot to recovery, I get a dead robot with a little ? & "No command"
EDIT: OK, I fixed it, by using "fastboot boot twrp.img" and then installing lineage and then installing twrp
I didn't know that you could boot an image without installing it that's really good to know.
So that's a workaround.
I could just compile a new TWRP but that would take effort
scres said:
I could just compile a new TWRP but that would take effort
Click to expand...
Click to collapse
You definitely don't need to do that. I have a K1 on 5.4, and TWRP works fine. Although I did already have TWRP installed before flashing 5.4. So not sure if that makes a difference.
Try fastboot erase cache, and flash a different TWRP build (like a build or 2 older such as 3.1.1-0).
I fixed this already
So I have been trying to flash the Pixel Factory Image, I have used the most recent SDK Platform Tools and I still can't get past the boot loop. I also have tried to flash the TWRP recovery but I am getting this:
Code:
C:\Users\MyName\Documents\Pixel\minimal_adb_fastboot_1.4.3_portable>fastboot flash recovery twrp-3.3.0-0-sailfish.img
target reported max download size of 536870912 bytes
sending 'recovery' (31000 KB)...
OKAY [ 0.828s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 0.938s
I have even tried but the bootloop is still there:
Code:
PS C:\Users\MyName\Documents\Pixel\minimal_adb_fastboot_1.4.3_portable> ./fastboot boot twrp-3.3.0-0-sailfish.img
downloading 'boot.img'...
OKAY [ 0.727s]
booting...
OKAY [ 1.010s]
finished. total time: 1.740s
There are a couple things wrong here:
Pixels don't have a recovery partition, everything happens in the boot one (root, twrp, custom kernel)
The first command in the first code block you wrote is wrong because the recovery partition is not there. In case you wanna flash a stock boot image, maybe for recover your device faulty kernel/twrp etc, without have to reflash the whole rom, the command should be "fastboot flash boot boot.img"
The command you sent in the second code block (./fastboot boot twrp-3.3.0-0-sailfish.img) in fact is correct because you just boot the twrp image (= no errors).
But when you wanna flash the recovery, you have to boot the twrp img and when it booted you have to flash the twrp.zip that you can download from the official site from the twrp screen, not the .img
Hope this helps
I'll add that you should also use the official platform-tools downloaded from Google. The minimal (and other alternatives) can give you problems when trying to flash.
The latest platform-tools is here. Note that Google hasn't updated the changelog, and the latest version is actually 28.0.3, not 28.0.2.
For TWRP, you need both the latest .img and .zip files from here, and transfer the .zip file to the Pixel. Use the boot command to boot from the .img, then from within the temporarily-booted TWRP install the .zip file.