Hey all, Im on Firerat's version of CyanogenMod 5 (latest), same SPL and radio in my sig. I tried to flash Amon's latest recovery, but i got an "Out of Space" error in terminal, so i tried to clear up things on /system, and flashed it through adb. I rebooted into recovery by holding power and home, and it took me to a black screen and it kept rebooting constantly into the black screen, i had to pull my battery out for it to stop. However, the ROM loads just fun with no problems...I tried reverting to my old version Amon RA 1.6.2, and i got no error on terminal, strange thing is the newer Amon Recovery is a smaller filesize...I tried redownloading and installing it but not luck...when i rebooted into recovery, same thing. Am I doomed to a recovery-less G1 or is there hope? =O
Thanks everyone!
If you already have ADB access on your computer
Flash the recovery through fastboot or Droid Explorer
thanks for the suggestion, tried that and same as before it still shows the g1 logo then a black screen, then the g1 logo and logo fades away to a black screen and it goes into a loop where its constantly vibrating and rebooting and showing a black screen the whole time. im confused..
while in adb did you try to command it to reboot to recovery or explore and see if you indeed still have a recovery or not?
Kemekill Products said:
while in adb did you try to command it to reboot to recovery or explore and see if you indeed still have a recovery or not?
Click to expand...
Click to collapse
i rebooted into recovery with adb but it was corrupt. i actually solved the problem. i searched deeper and deeper and got creative with search terms to find out that some people have had a similar experience flashing Amon 1.7, the easy solution was to download rom manager from market, flash the clockwork recovery, then from the app flash amon 1.7. all is well again, thanks for chiming in guys
Next time, to avoid any mistakes, flash it through fastboot.
It's the safest/best way to do it.
AustinAce said:
Next time, to avoid any mistakes, flash it through fastboot.
It's the safest/best way to do it.
Click to expand...
Click to collapse
yeah lbcoder was talking about that with spls i had no idea same went for recovery images. but next time ill play it safe. i heard it was actually a terminal problem with CM5
I flashed the Tayutama 1.0.3 captivated ROM, then I used the clockwork recovery to replace the glass lock screen by the Froyo stock one.
Now the phone automatically boots to the clockwork recovery screen, tried to take the battery out but no use.
I still can boot to download mode, but the point is that I left something important in the old system, and now it seems I can't take it out because of this bug.
Any idea?
Fixed it. Here's the tips for people who have the same problem as mine:
1. Use clockwork create a backup.
2. One click flash
3. Install Tayutama's ROM
4. Use clockwork again, choose "Advanced restore" and "restore DATA"
It should work.
crazyfffan said:
I flashed the Tayutama 1.0.3 captivated ROM, then I used the clockwork recovery to replace the glass lock screen by the Froyo stock one.
Now the phone automatically boots to the clockwork recovery screen, tried to take the battery out but no use.
I still can boot to download mode, but the point is that I left something important in the old system, and now it seems I can't take it out because of this bug.
Any idea?
Click to expand...
Click to collapse
Did it wipe your data? Or is it in a backup? You could ADB pull the file/information if its a picture or file .... IF you didn't wipe your SD Card.
Also you could attempt to find Tyutama 1.0.3 ROM and find the stock lock screen and try and push it back on and see if your phone reboots.
But rule of thumb:
Always put a backup of whatever your about to screw with on your SD Card. You can use root explorer/ADB/Little Green Men to do it.. doesnt matter how you get the file.. important thing is to have it on the SDCard.
When it fubars you can always (usually) copy the backup back to the location where you fubard it - and *voila* your phone should boot right up.
I have done this (countless) a few times and have always been able to restore the phone to have it boot up enough for me to either re-flash or go on my merry way.
Good luck.
First off, I'm very sorry as I know by now you are mostly sick of noobs but I tried to figure out what I'm doing wrong on my own and am just stuck.
So here it goes:
I rooted my DROID 2.2.1 with superone click. Did everything I've read to do and tried to install bugless beast ROM. Tried to boot into recovery but I got the triangle exclamation point screen on reboot. Tried to install the ROM via ROM manager and the same thing happened. I was then able to get to clockwork recovery through ROM manager somehow and installed the ROM. At this point, I got the startup screen for bugless beast and it just looped. I restored back to Froyo and cannot get back to recovery boot because that $#%% screen with the triangle exclamation is killing me.
What should I do now? Or am I just too noob at this and should go back to the Matrix lifestyle of "ignorance is bliss" by unrooting?
Thanks again.
Matt
prepare to kick yourself in the head ^^
- the "triangle exclamation" pictures is EXACTLY the point where you can enter Recovery.
here´s how: press "volumeUP" and the "camera" button at the same time.
then navigate through the recovery (if you have a custom recovery installed, you´ll need to choose "apply update.zip" to load the custom/open recovery on the first screen) using your D-Pad.
Thank you for the button combo to get where I need to go. Now does anyone know why when I load a ROM, the start up screen just loops forever? I have tried loading cyanogen6 and bugless beast now both with the same issue.
nevermind...I'm stupid. Sorry. Needed to wipe data. But how do I get all my data back? If I restore data through nandroid then I just get boot loops again.
I haven't used rom manager before.
So i would recommend you to use open recovery to do flashing or rooting.
Have u flash a vulnerable recovery sbf ??
If yes, you can go to recovery mode and select "apply update".
Then the open recovery is applied.
By using OR, you can root phone and apply any updates you want.
Sent from my A853 using XDA App
matty1098 said:
nevermind...I'm stupid. Sorry. Needed to wipe data. But how do I get all my data back? If I restore data through nandroid then I just get boot loops again.
Click to expand...
Click to collapse
Boot loops??
Do u mean your phone keep rebooting??
Sent from my A853 using XDA App
Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.
A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D
are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!
Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.
Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?
Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.
For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.
I have a rooted HTC Hero (Sprint) and during preparations for upgrading to CM7 I ran into issues with ROM Manager.
First, I backed up everything (apps and data) via two different methods. I cleared davlik cache, and then performed a CWM Flash Recovery backup. Once that completed successfully, I sought out to apply the CM7 ROM. I selected it from the GUI menu, rather than rebooting into the Flash Recovery. I selected to backup everything and then wipe the data/cache. During the process, the phone hung (white HTC screen for over 10 minutes). I could reboot successfully after this, and selecting "Recovery" didn't work either. I figured my phone was bricked. But miraculously, it managed to finally recover.
The recovered ROM was a fresh clean slate. So, I installed ROM Manager and Titanium backup again. However, when I tried to reboot to the CWM Flash Recovery, or even try entering the CWM CUI menu from power up (by holding the HOME key), the phone hangs. Something is seriously screwed up with ROM Manager. I'd like to wipe it completely clean and start over, but everything I've tried results in a phone that hangs. I'm now thinking I should use a different program for managing the ROMs... but, being familiar with ROM Manager and seeing other people use it successfully, I feel determined to make it work. Any suggestions?
I would just flash an RUU and start from scratch.
https://docs.google.com/file/d/0B9lyYjZr_O3gZnJrRVFqRmh4eVU/edit
I was able to recover.
What I didn't realize is that the first boot can take upwards of 20-30 minutes. I pulled the battery after around 15 minutes, thinking my phone had hung.
Anyway, when I selected "Recovery" again I left the phone alone and eventually I got a stock ROM again. Whew!
While ClockworkMod is fine for 2.1, when you're on 2.3 there's no question that TWRP is the way to go. I've flashed it to my phone (did "flash_image recovery [recoveryfilename.img]") from the terminal window and it's working great, far more extensive than ClockworkMod.