hi, ive just flashed TWRP onto my lollipop. seemed to be succesful, however when i boot into recovery all i get is the wee android dude lying on his back looking a bit dead! any ideas how to get this working. i just installed lollipop today
If you did 'fastboot flash recovery twrp.img' and not 'fastboot boot twrp.img':
Browse around, I'm pretty sure this has been answered before.
Search topics: install-recovery.sh, recovery-from-boot.p
Boot to Android, then flash again.
Aerowinder said:
Boot to Android, then flash again.
Click to expand...
Click to collapse
Ugh... What are you talking about?
What's happening is that every boot, his install is checking for stock recovery, and every time it doesn't find it, it will reflash it.
well I was using the flash method and it didnt work so i tried yor boot method and i could see teh twrp logo for about 5 seconds then the rebooted. i still get the android dude on his back with red triangle
5.0 will check recovery and overwrite twrp if your not rooted. Download latest SuperSU and place on sd. Boot to boot loader/fastboot. Fastboot flash recovery recovery.IMG. then fastboot boot recovery.IMG. then when twrp boots, flash SuperSU. Reboot
Sent from my Nexus 5 using Tapatalk
MG386 said:
5.0 will check recovery and overwrite twrp if your not rooted. Download latest SuperSU and place on sd. Boot to boot loader/fastboot. Fastboot flash recovery recovery.IMG. then fastboot boot recovery.IMG. then when twrp boots, flash SuperSU. Reboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
that worked a treat. is it necessary to flash the MODIFIED BOOT IMAGE?
Related
Im kinda outta the know, but i see a few Rogers guys that cant root since the 1.94( i think) update but can unlock thru htcdev. Some of you guys are having trouble getting a flashed recovery to stick, so you cant get a rooted rom flashed. Well, there is a VERY simple solution for you guys.
You have your recovery.img in your adb/fastboot folder and your in your device bootloader.
fastboot flash recovery nameofrecovery.img
Ya ya, you tried that, But Wait!
Now
fastboot boot nameofrecovery.img
That WILL boot you into your custom recovery. Now u can nandroid and flash your rooted rom. Once booted up, go download goomanager and install recovery from there. That one WILL stick.
If you ever temporarily need to use the stock recovery, simply put the stockrecovery.img into your adb/fastboot folder and just do
fastboot boot stockrecovery.img
do whatever, after you reboot you will still have your custom recovery, since all you did was boot the stock recovery, not flash it. Also works vice versa
Added:
if you boot a cwm recovery at first steps, after installing recovery thru goomanager go make a new nandroid because twrp wont restore a cwm backup.
Hope this helps out a little:beer:
Could have used this info a few days ago
Bookmarking this.
Sent from my HTC One XL using xda premium
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
also it says invalid "boot image header!" in red letters
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
P.Kosunen said:
http://forum.xda-developers.com/showthread.php?t=2542219
Install full factory image with fastboot.
Click to expand...
Click to collapse
Alright thankyou!
I got everything to work again but I still can't flash roms. They just bootloop :S
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
You do know flashing stock again removes root, so it has to be rerooted again ?
aradalien said:
You do know flashing stock again removes root, so it has to be rerooted again ?
Click to expand...
Click to collapse
Yes I am very aware and followed through with root with that outcome.
kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview this cwm worked for me
Click to expand...
Click to collapse
CWM doesn't work it. It boots up (Im used cyanogenmod) the cyanogenmod boot animation but just stays there.
P.Kosunen said:
It could be too big recovery install with fastboot causes problem, every recovery cwm/twrp i tried to install with fastboot fails.
http://forum.xda-developers.com/showpost.php?p=49559872&postcount=234
Twrp_MotoG_signed_010814_163615.zip
Download vocoderisms TWRP build, extract "recovery.img" from it.
After you have kitkat installed and working:
Option 1, use TWRP without install:
Boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img) and install rom from there.
Option 2, install TWRP (have not tested):
Upload twrp zip to phone (adb push Twrp_MotoG_signed_010814_163615.zip /sdcard/), boot to bootloader (adb reboot bootloader), boot twrp (fastboot boot recovery.img), install Twrp_MotoG_signed_010814_163615.zip.
Click to expand...
Click to collapse
I've flashed twrp too and came out with the same outcome.
stuck in fastboot
Misterowl said:
Okay so I tried to flash cyanogenmod 11 for the first time on this moto G (US). It bootlooped and I tired to reflash it again and it did the same. There was no way of returning to stock because I had not made a backup. So I tried to flash stock in the bootloader and that didn't work. I went into the recovery and it said 'cant mount /sdcard. So go back into the bootloader and format the sdcard and that doesn't work (which I returned to the recovery to see it not working). I go back and flash twrp thinking that recovery would have something to help me flash a new rom and now I don't even have a working recovery. It takes me straight back to the bootloader and every time I flash a recovery it says Mismatched partition size (recovery) and I am unable to boot into it.
I have no clue on what to do at this point and I need help.
Click to expand...
Click to collapse
Exactly i am also facing same problem....
mobile unable to instal firmware...
still i am searching for solution ...
guys plz help me
I thought I am the only one with this problem..After mailing the phone to SC and got it back after 2 months, the phone still looks the same, just like they did nothing to fix it.
Updated to the 5.0 factory image using the flash-all.sh script. fastboot flashed the latest twrp. go to reboot recovery and it boot loops on the teamwin logo. How can I get twrp to actualy boot after upgrading to 5.0
Guitarboarder28 said:
Updated to the 5.0 factory image using the flash-all.sh script. fastboot flashed the latest twrp. go to reboot recovery and it boot loops on the teamwin logo. How can I get twrp to actualy boot after upgrading to 5.0
Click to expand...
Click to collapse
Root, wipe twrp folder, reflash recovery
Guitarboarder28 said:
Updated to the 5.0 factory image using the flash-all.sh script. fastboot flashed the latest twrp. go to reboot recovery and it boot loops on the teamwin logo. How can I get twrp to actualy boot after upgrading to 5.0
Click to expand...
Click to collapse
I'm having a similar issue, I flash the newest twrp using fastboot. When I go into recovery it shows teamwin logo and after a pause it just reboots into the system. This is only one of a handful of issues twrp has given me while using 5.0.
It seems everybody except me has this issue. It's apparently because of MTP in 2.8.2.0.
ANDROIDRAZRM said:
Root, wipe twrp folder, reflash recovery
Click to expand...
Click to collapse
thanks. did the cf autoroot and then flashed recovery and everything seems to be working
Ok here's what happened. I am rooted running Slim Kat with CWM recovery installed. I decide to install TWRP using their app. When I booted into recovery, I got the TWRP splash screen, but the phone immediately rebooted. No recovery. I flashed CWM back using ADB. I was able to get into recovery from fastboot, but once I rebooted into the ROM, I couldn't get back into recovery again! Well, I said screw this! I had been thinking about flashing the factory stock lollipop ROM image, so I guessed this was as good a time as any. That process went well. Flashed lollipop images with ADB . Booted up. Everything fine. Set everything up. Tried to go into recovery. I have no recovery. Pressing Vol up & power buttons just reboots phone. Tried flashing CWM again. It flashed fine and phone will go into recovery from fastboot, but if I boot into ROM, and then try to go back into recovery — no recovery! I extracted the stock recovery from the image and flashed that. Same thing! I am out of ideas! Help!
Sent from my Nexus 7 using Tapatalk
With Lollipop it will install stock recovery after every boot. You can just boot twrp/cwm and flash SuperSU, that should fix your problem. If it doesn't delete /system/etc/recovery-from-boot.bak and you should be fine
Sent from my Nexus 5 using XDA Free mobile app
bm19981217 said:
If it doesn't, delete /system/etc/recovery-from-boot.p and you should be fine
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Correction.
Thanks! Looks like I was making 2 mistakes!
1. Had the button sequence backwards for stock recovery. It's hold power button down, then Vol up, release. I was holding power and Vol up simultaneously.
2. Didn't know that about lollipop. That explains why recovery kept "disappearing“.
Sometimes, trying to figure this stuff out at 3 am is not a good idea.
Still don't know why I had the problems with TWRP on Kitkat.
Sent from my Nexus 7 using Tapatalk
GadgetLady said:
Still don't know why I had the problems with TWRP on Kitkat.
Click to expand...
Click to collapse
Probably because you will have flashed 2.8.2.0 which doesn't work for most people. Try 2.8.1.0 and you'll be fine
Sent from my Nexus 10 using Tapatalk
As a matter of fact , it was 2.8.2.0.
Sent from my Nexus 7 using Tapatalk
GrenW said:
Probably because you will have flashed 2.8.2.0 which doesn't work for most people. Try 2.8.1.0 and you'll be fine
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I think this above post need to be emphasized. TWRP 2.8.1.0 solved all my problems.
With TWRP 2.8.2.0, I spent hours trying to figure out how to make recovery stick, even after rooting with CF Auto root, and the SuperSU BETA from Android L, AND after deleting the recovery-from-boot.p files and the install_recovery.sh files. It just would not load TWRP 2.8.2.0, using either "fastboot flash recovery twrp.img" OR "fastboot boot twrp.img". Either - it would reflash stock recovery (if I didn't properly delete the recovery script files), or, it would show the TWRP boot screen for a second or two, and then boot android normally! Every time!
As soon as I used 2.8.1.0 and retried "fastboot boot twrp2810.img" from a stock reflash, it worked without a hitch. Here are the steps I used to upgrade using fastboot from 4.4.4 to Android L (Euphoria ROM)
reboot into tWRP recovery in 4.4.4
Factory reset
Format system
Format userdata
Format cache
Reboot into bootloader.
fastboot flash bootloader with Android lollipop version. Reboot the bootloader
fastboot flash radio with Android Lollipop version. Reboot the bootloader
fastboot flash boot (stock lollipop). Reboot the bootloader
fastboot flash recovery (TWRP 2.8.1.0). Reboot the bootloader
fastboot flash system (stock lollipop)
fastboot flash userdata (stock lollipop)
fastboot flash cache (stock lollipop)
***Now, here it's really important not to boot into android!!!!
instead of trying to boot recovery from the fastboot menu, and just to be extra careful I did
fastboot boot TWRP2810.img (to boot directly from the img in my platform-tools folder)
Then when I was in TWRP I used the sideload option and did:
ADB sideload BETA-SuperSu-v2.39.img to load root onto my phone.
Then I restarted into Android for the first time and as soon as I got there,
I downloaded root explorer (or ES file explorer - and enable root options in the ES file explorer menu)
deleted /system/recovery-from-boot.p
delete /system/bin/install_recovery.sh and the other file in the folder which is a shortcut with the same name (probably overkill but I wasn't taking any chances).
Then reboot into bootloader - and pick recovery - and hopefully, if all went well - voila, TWRP will properly boot.
Here you can easily sideload Euphoria OS (or other) and the Bpear Gapps (or other) and away you go.
You can also flash franco kernel or whatever.
Now, your root should stick, and TWRP should stick.
Thank you GrenW for pointing out the importance of using 2.8.1.0 instead of 2.8.2.0!!!
Guys i faced a wierd problem . I flashed twrp image and then twrp zip and then magisk ..i rebooted and when i tried to boot in recovery . The recovery was gone but magisk is still . What should i doo nowwww ?
What you do now is you
fastboot boot blu_sparktwrp.img
And then in twrp you flash blu_sparktwrp.zip
Reboot to twrp
Flash magisk 17.2.Zip
Done..rebot.
whizeguy said:
What you do now is you
fastboot boot blu_sparktwrp.img
And then in twrp you flash blu_sparktwrp.zip
Reboot to twrp
Flash magisk 17.2.Zip
Done..rebot.
Click to expand...
Click to collapse
It didnt work ....it goes away after a reboot
sanu26661 said:
It didnt work ....it goes away after a reboot
Click to expand...
Click to collapse
It must work. You're basically flashing TWRP temporarily, so when you are in TWRP for the first time, you have to flash the zip file so that it stays installed. Try that again, maybe you did something wrong, but it has to work, you just need the .img that you flash with your PC, and the .zip that you flash using TWRP when you boot into it the first time.
Kluxe Nobody said:
It must work. You're basically flashing TWRP temporarily, so when you are in TWRP for the first time, you have to flash the zip file so that it stays installed. Try that again, maybe you did something wrong, but it has to work, you just need the .img that you flash with your PC, and the .zip that you flash using TWRP when you boot into it the first time.
Click to expand...
Click to collapse
I booted img first then installed zip but when i reboot to recovery thers only stock recovery present ...did like 10 times results are same
the blu_spark twrp? v2?
If twrp isn't sticking, from my experience is to lock bootloader, flash stock OS and start from scratch.....
Do not flash stock with unlocked bootloader