In my G1, I cannot boot into recovery or into Android. So, I'm trying to flash Amons recovery via fastboot, which, according to the how-to, I can't, I need Engineering SPL, which I don't have. How can I fix my problem here? I have Amons recovery image in the root of my sd. and fastboot. How can I fix my problem?
Derkek said:
In my G1, I cannot boot into recovery or into Android. So, I'm trying to flash Amons recovery via fastboot, which, according to the how-to, I can't, I need Engineering SPL, which I don't have. How can I fix my problem here? I have Amons recovery image in the root of my sd. and fastboot. How can I fix my problem?
Click to expand...
Click to collapse
Search here: http://forum.xda-developers.com/showthread.php?t=566669
Now run away cause the mean people will be here shortly.
Thankyou
Thank you muchly. I've been there before but for some reason, when I went to it again, it all clicked. I needed to do this in command prompt. *runs away before the meanies come*
Related
So I just got into this stuff last week and have learned quite a bit. I tried various types of images. Accidentally I happened to load the Android 1.6 dev image to my regular G1. Now it wont let me flash anything! It wont let me flash images or even the spl! Please help me!!! How do I get back to cupcake now?
You mean the stock ADP1v1.6 image from developer.htc.com?
First off, you do NOT want to be flashing the SPL. The first thing you should have done is to write the ENGINEERING SPL (ADP1 stock SPL), and then NEVER touch the SPL again.
Now since you managed to write the stock ADP1v1.6 image, I suspect that you already have this (or the uselessly different hack of it called HARDSPL), which means that you have a mode called FASTBOOT (which can be used to write ANY image (in image format, not in update format) to the device. I suggest flashing the RECOVERY partition with cyanogen's recovery image. You can use fastboot to do this. The fastboot binary and instructions on getting into fastboot mode is available at developer.htc.com/adp.html -- the command to use would be "fastboot flash recovery recovery.img".
Note: With a stock ADP1v1.1 or newer, root access is available (yes, stock root), but only via ADB -- this is a SECURITY precaution to prevent malicious apps from hijacking root. If you want to su to root, just need to go in via ADB. So in other words, if somehow you have a stock tmobile SPL that lacks fastboot, then you DO have root access, so you can go in and flash the recovery partition over ADB. What you would do here is copy the recovery.img onto the root of your sdcard and use the flash_image command... i.e. "flash_image recovery /sdcard/recovery.img".
Hi,
I've owned and ROM'd two Android phones, but not a G1 and wanted to help out a friend to get her stock 1.6 G1 to CM5. We ran into problems which led me to not want to continue before they are sorted out. I looked for answers to this but couldn't find any, so please don't flame me if I overlooked any. I tried to go by the instructions in the CM wiki.
This is what we did:
- We installed ClockWorkMod Recovery through the ROM Manager app
- We rebooted into that recovery and via adb flashed AmonRA recovery
- we rebooted into the AmonRA recovery which worked (I *think* just regularly holding Home while powering on)
- we flashed the appropriate radio update for her US TMo G1
- the documentation said "phone will reboot during update". I think it did, but it seemed stuck on "formatting cache" in recovery.
- when holding Home on reboot after that, it did from there on NOT reboot into the custom recovery
- instead, it rebooted into what looks like "bootloader" mode on my Moto Milestone, a screen with a phone and an exclamation point. We could get into stock recovery with Alt-L, but I don't think that is what we wanted.
At this point, it seemed to not reliably boot into custom recovery, so I didn't want to continue the process. I assume I could have gone down the same of flashing a custom recovery, but I wasn't sure what would happen with/after installation of the DangerSPL if booting into recovery wouldn't work.
So - is the "booting into bootloader instead of recovery" a known issue? Am I too much of a noob on the G1 and did totally miss something? Could or should we proceed to the DangerSPL / CM5 installation with this going on?
Any help would be much appreciated!
W0nk0
Flashing a new recovery from CM5 or CM6 is not working well. Try flashing the recovery image / radio image / ... from fastboot and you should be fine.
Edit: I did not read well the first time. Now I notice, that you are still on stock SPL, sorry. But re-reading well I've got a question: Are you sure you flashed already successfully a new recovery? For me it seems you are still on a plain stock G1.
Sent from my Htcclay's Superfly G1 using XDA App
Thanks a lot for your help!
We _were_ on a custom recovery twice, after flashing it from ROM manager (Clockworkmod then) and on the AmonRA recovery after that. As the recoveries clearly had non-stock things like nandroid I'm quite positive.
The problem seems to be that they didn't "stick" - we flashed the radio ROM upgrade from Amonra recovery, but after a reboot with Home pressed landed in the exclamation point screen again (which seems to indicate stock recovery as you can get to that with Alt-L from there).
If fastboot is indeed the way to go, where do I get the drivers for the windows/pc side of it? The noob guide I found had no help there :/.
Thanks again,
W0nk0
Sent from my Dell Streak using Tapatalk
Few things;
1) if you have the OEM system image, then, indeed, the recovery will be overwritten by the OEM recovery image upon reboot into the system.
2) You say that you've written a RADIO image.... ***WHAT*** radio image did you write? You should have written a radio with a version number that starts with a "2".
3) Have you written a new SPL? The SPL you should write is 1.33.2003. DO NOT install deathSPL, no matter how many RETARDS suggest it. There is ABSOLUTELY NO USE in it. 1.33.2003 is SAFE to install (unlike 1.33.2005), and the ONLY benefit of 1.33.2005 has been GREATLY EXCEEDED, making that "benefit" entirely pointless.
Note that with the stock SPL (0.95.0000), there IS NO FASTBOOT. 1.33.2003 has a very strong fastboot capable of writing ALL partitions, including the radio image. Fastboot is the safest way to write the radio and SPL, but prior to installing an SPL with a strong fastboot mode, obviously you can't use this feature.
Steps:
1) Reinstall custom recovery,
2) reboot into recovery and write 1.33.2003 SPL.
3) DO NOT let it boot into regular system prior to installing 1.33.2003 SPL, or it will overwrite that custom recovery.
4) After installing the good SPL, it would still overwrite the custom recovery by booting into the regular system, but by this time, you will have FASTBOOT, so it doesn't matter.
5) Now do what you want... but once you have a 2.x radio and 1.33.2003, do NOT write any other radio or SPL, and for F SAKES DO NOT RUN ANY NBH FILES EVER NO MATTER WHAT!!!
My G1 is stuck on Amon RA recovery....I tried to use firerat's method and after i flashed foroyo rom its stuck in the recovery...but it doesnt show any options...
Just
Build : RA-dream-v1.7.0
thats it i cant do anything....
i know i didnt brick my phone...please help...
[Solved]
solution : install fastboot and you can erase the system...
C:\\ .......android-sdk-windows\tools\fastboot devices
C:\\ .......android-sdk-windows\tools\fastboot -w
C:\\ .......android-sdk-windows\tools\fastboot flash recovery [recovery path with ".img"]
walla your recovery is overridden by the new one...
Most likely you did not completely follow the instructions how to install mtd, but nevertheless what SPL do you have installed? If you have 1.33.2003 I suggest to flash recovery again using fastboot and you are rescued.
Otherwise ... I don't know. Even if you are able to connect via adb I do not expect you can flash a new recovery while beeing in recovery. For sure you are able to go into bootloader install dreamimg.nbh, etc. but this would mean to do the hole rooting process again.
AndDiSa said:
Most likely you did not completely follow the instructions how to install mtd, but nevertheless what SPL do you have installed? If you have 1.33.2003 I suggest to flash recovery again using fastboot and you are rescued.
Otherwise ... I don't know. Even if you are able to connect via adb I do not expect you can flash a new recovery while beeing in recovery. For sure you are able to go into bootloader install dreamimg.nbh, etc. but this would mean to do the hole rooting process again.
Click to expand...
Click to collapse
thankx man for replying....i kinda fixed it ...i followed this step
http://forum.xda-developers.com/showthread.php?t=807183&page=13
post number 160
but afte i Flash FR-recovery-v1.5.3-CustomMTD_S.zip and reboot to recovery my amon recovery goes blank...kinda funny....
actually you can do anything with fastboot...erase system...flash recovery...i couldnt flash a rom..but was able to override the recovery....that all i needed...
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.
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.