Related
Hey Experts,
I cant 4 the life of me understand how to flash Amon Ra 2.2.1.
I have followed the wiki/Xda to run "fastboot flash recovery recovery image from Adb
It says its successful on Cmd n stuff, but i still think i m on stock reCovery
I have tried to put the recovery.img on sd card, and tried i just get a screen witha Exclamation sign with a lil android guy.
I m trying to do an nandroid backup and wipe data/dalvik b4 flashing Cm7.
Thats y i m trying to get onto Recovry:
Specs:stock 2.3.4, Bootloader unlockd (not roooted still!!)
Can som1 help? thx
Flash it from fastboot. Which I think you did anyways but that is not adb.
Then you must boot directly into recovery. If you boot up the phone it will overnight it with stock. You flash from a computer. Not from SD......
Sent from my Nexus S using XDA App
fastboot flash recovery recovery.img
Why do people have such a hard time with literally one command?
GldRush98 said:
fastboot flash recovery recovery.img
Why do people have such a hard time with literally one command?
Click to expand...
Click to collapse
Dude, unfortuantely i have already run both "fastboot flas recovery" and also somting like "fastboot reboot recovery". on bootloader-fastboot
Ok, screw Amon-Ra!! if i get into recovery(to Actually do an Nandorid and wipe), i still get the android with exclamation
Just help me do an nandroid and wipe cache/dalvik
I ll take it on from there
thx sir!
Again. Put the recovery image in the same directory as fastboot on your computer. Issue the correct exact command. Fastboot flash recovery "put the exact file name here"
Now on your phone which is still in fastboot mode.... pick the recovery option. It is that simple.....
albundy2010 said:
Again. Put the recovery image in the same directory as fastboot on your computer. Issue the correct exact command. Fastboot flash recovery "put the exact file name here"
Now on your phone which is still in fastboot mode.... pick the recovery option. It is that simple.....
Click to expand...
Click to collapse
"Put the recovery image in the same directory as fastboot on your computer"
yeah, thats the one dude ! i had that Amon Ra 2.2.1 in the tool directory. Moved it to Fastboot and flashed su.zip from recovery.Silly me i had it in Tools instd of Fastboot
Im all set with a rooted 2.3.4 with Amon Ra! thx dude
i have mrkd ur post as thx n stuff so that this thread is resolved
If you are on a stock ROM, any custom recovery (like Amon_RA) will be overwritten on every boot with the stock recovery.
To make the custom recovery stick while using a stock ROM, you need to delete (or rename) the following two files:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
... as mentioned in the first post of the Amon_RA recovery thread...
efrant said:
If you are on a stock ROM, any custom recovery (like Amon_RA) will be overwritten on every boot with the stock recovery.
To make the custom recovery stick while using a stock ROM, you need to delete (or rename) the following two files:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
... as mentioned in the first post of the Amon_RA recovery thread...
Click to expand...
Click to collapse
/system/recovery-from-boot.p and /system/etc/install-recovery.sh!!
Where do i find these files?
Do u wnt me to dwnload some market app like root explorer/astroid file mgr etc to delete them?
Is there a way faster/better way of findin em and Deleting me?
thx ~
Read the guide in Wiki. The file to flash from recovery that does just that, is there.
Jack_R1 said:
Read the guide in Wiki. The file to flash from recovery that does just that, is there.
Click to expand...
Click to collapse
Yeah. Sad thing is, had he actually read the wiki and done what it said, he would have never had to make this thread. Sigh... people will never learn.
All,
I'm coming from a nexus environment where I've been able to do fastboot boot twrp-2.6.3.1-ghost-4.4.img rather than fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img since I'm hoping to keep the stock recovery while installing supersu. It complains about "(bootloader) Command restricted" with the MotoX even though my bootloader is unlocked. Is this typical of Moto devices? Do I actually need to flash twrp, then supersu and then the stock recovery if that's the final result I want? FWIW, I want SU on it but I'd like to also receive future OTA updates w/o too much dorking around of at all possible.
thanks peterb
Are you using mfastboot or just regular fastboot?
I fastboot twrp no problem. I did however mfastboot the system.img . But to answer your question twrp will ask you if you want to root when you go to reboot.
Fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img is the command, when you flash do not reboot the device to the system but boot into recovery instead, you should be good to go and twrp should ask if you wish to root, if not just download the flashable supersu zip
Sent on my Moto X
I understand that you should flash if you want to have TWRP installed on your phone but that's not what I want. I'd like to just boot into TWRP, install the SuperSU.zip and then boot back up as normal leaving the stock recovery in place so that I will continue to get OTA updates. I get that this is likely not the norm but it's what I did with my N4 to get SuperSu so that I could update boot.prop for flashing a hybrid radio. Doing this made it easier to get the phone back to OTA ready w/o having to flash the stock recovery back.
I found a couple of posts in the N4 where the fastboot command failed and you needed to start using the "-c" command. I was wondering if this was the problem I was running into. The argument for -c is a bit cryptic so I worry that the one I found is likely N4 specific:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Basically what I'm wondering is if anyone has been able to just boot into TWRP w/o actually flashing it to the recovery partition.
If this is not possible then I'll flash TWRP, root and then flash the stock recovery back on since I did get the stock 4.4 image from Motorola.
thanks peterb
flashallthetime said:
Fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img is the command, when you flash do not reboot the device to the system but boot into recovery instead, you should be good to go and twrp should ask if you wish to root, if not just download the flashable supersu zip
Sent on my Moto X
Click to expand...
Click to collapse
Interested in this as well, for booting kernels. Device support has been hit-or-miss for me in the past.
And folks, he's asking about fastboot's ability to launch an image _without_ flashing. This is a somewhat esoteric/advanced use.
I'm interested in this too even though I have a locked Moto X.
I didn't know this was possible, huh. As for our device, it'll probably help if we can figure out what that -c command means.
Sent from my Moto-X (GSM DE) using the xda-developers app
thehockeydude44 said:
I didn't know this was possible, huh. As for our device, it'll probably help if we can figure out what that -c command means.
Sent from my Moto-X (GSM DE) using the xda-developers app
Click to expand...
Click to collapse
If I'm remembering right, google took the ability to boot a recovery without loading one away in 4.2. We tried to do this on the HTC 1 Google edition when we pulled its partitions to make a system dump. It failed.
OTA fails when the device is rooted, even if you have the stock recovery.
The OTA zip checks the system partition. If there is any single modification, it fails.
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Yea, this is the other way to do it. It's just a bummer if one can't use the flexibility to just boot into recovery. Note that I still seem to be able to boot into custom recovery on my Nexus 4 that's running KitKat. I'm curious about the comment about not getting an OTA with su installed. I know that with a modified build.prop and radio, the N4 wouldn't update but I could adb sideload successfully once I put build.prop back and the stock radio on. I figured the OTA would just unroot and then I'd have to do the process again.
Anyway, this was my plan B, just would have preferred to boot recovery.
peterb
waiflih said:
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Click to expand...
Click to collapse
if u want to "unroot" to take otas, u can just flash stock system
waiflih said:
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Click to expand...
Click to collapse
I am interested in this as well. How do we get a copy of the stock recovery to reflash?
Also, I have had rooted stock and custom recoveries and have received OTA's before (but they were on Nexus devices).
droiddog said:
I am interested in this as well. How do we get a copy of the stock recovery to reflash?
Also, I have had rooted stock and custom recoveries and have received OTA's before (but they were on Nexus devices).
Click to expand...
Click to collapse
you can take it from the the file used in rsdlite, according to you fw version
The only reason I want the stock recovery is because I think you can't remotely lock or erase your device on a custom recovery. Does anyone know anything to the contrary? Thanks.
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
ReproOne said:
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
Click to expand...
Click to collapse
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
Thank you for the reply. I thought about taking that approach, but I was really hoping someone would have an answer on why the procedure wasn't working now. My bootloader is still unlocked.
I found this as an approach someone did on the Nexus 4 for a similar issue:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Thoughts?
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
ReproOne said:
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
Click to expand...
Click to collapse
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Thank you for those steps. I do not have an external SD card installed, so I modified it to store the recovery.img on sdcard instead.
Now I can always fastboot flash twrp and then back to stock recovery.
Thank you again!
nfinitefx45 said:
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Click to expand...
Click to collapse
You would need root to do this. Not being able to use "fastboot boot" you would just be backing up the flashed recovery. Possibly towel root temp root, but I would assume it has been patched in newest update.
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
xPhantom said:
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
Click to expand...
Click to collapse
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
neudof said:
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
Click to expand...
Click to collapse
Yes, after the OTA, just flash TWRP back through fastboot and then re-flash SuperSU to get root back.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
I just applied the update released today, and I tried to save the recovery.img file before flashing TWRP. However, it kept giving me permission denied. Do you have the recovery.img file from the update released today so I can use it for the next update?
fastboot not working
please any help on how to access fastboot on HTC one m8.
its showing black screen n fastboot mode...
wot can I do 2 annul d problem
rooting problem
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
jinal shah said:
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
Click to expand...
Click to collapse
What's the output in the terminal when you fastboot flash recovery?
rooting problem
It doesn't show any error as such.
In the command window it shows successful.
But when I click on recovery it reboots back to fast boot.
Like for a second it shows the screen which reads 'this build is only for developers'
But then instead of opening Twrp it reboots back to fast boot.
So im running CM12.1 and im trying to flash the CWM recovery i used for installing CM and i can get into fastboot mode and flash it, but then every tutorial says then go into recovery through the UI on the screen, but my bootloader screen is just black and obviously cause im in fastboot mode i cant boot directly into recovery without rebooting the device which will reflash the stock recovery
What can i do?
Cheers
Reboot and press the volume keys up and down simultaneously to boot into recovery.
I have cm12.1 but the problem is, the recovery is showing black screen. I tried flashing from fastboot twrp image file and xzdualrecovery only to cause boot loops.
Is there any method to install recover on cm12.1 without causing bootloops?
Sent from my Nexus 7 WiFi using Tapatalk
Try this.
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Sent from my Nexus 7 WiFi using Tapatalk
Not really sure what I'm doing wrong. Last rooted phone was a Nexus 5, and that was of course painless to root and flash ROMs to...
I'm using a Verizon XT1096 with 5.1 on T-Mobile.
So I was able to get the bootloader unlocked via Motorola's website, now that Verizon is allowing them to do so. No problems there. My problem now is that I can flash a recovery, but if it reboots, the recovery is gone. And I can't get any recoveries to flash anything. I can't push an apk, root zip, or even a ROM. Says Installation Aborted, with no other error codes. Even tried CWM and disabling Signature Checking, which gives me more info, saying that the footer is mismatched. Phone does say the bootloader is unlocked though so that shouldn't be it...
Honestly, I'd just like to get it on CM12 until I can get a Nexus 6P.. Can anyone tell me if I'm doing something wrong? Or is there just no way to root yet? I figured even the XT1095 CF-Auto-Root method would work for 5.1, but no dice..
Not sure what to do here. Please move my thread if need be. Don't post here much...
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
RepeatUntilTheEnd said:
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
I thought I tried that but maybe not. I've read that some stock ROMs can and will overwrite the recovery upon booting, but I could be wrong. I'll look at that when I get home tonight.
oraixearl said:
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
Click to expand...
Click to collapse
Thank you, I'll try this tonight when I get home. This may solve it. I think I remember the bootloader spitting something out about a partition mismatch.. Will report back as soon as I try it.
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
TsarProdigy said:
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
Click to expand...
Click to collapse
Strange as it worked for me. I'm glad you got it sorted out tho. Cheers.