Hi, I did a search but couldn't find anything, so I'm starting a new thread.
I have a rooted G1 running Froyo For Trout(don't think this is the problem though..). I was in rom manager and was trying to do a backup, but it would just reboot to an endless G1 screen. I took the battery out, and reboot and the OS works completely find. I tried rebooting into recovery from Rom Manager and by pressing home and power, and both just lead me to an endless G1 screen. The OS still loads fine though. I have flashed both Clockwork and AmonRA, and tried both. (I have flashed them from Rom Manager).
So, to sum it up, I was flashing the recovery in rom manager, it says its complete, but I seem to not have a recovery. And I've rebooted into Clockwork and AmonRA before that many times, so I'm not sure what the problem is. Help!
have you tried to flash the recovery through terminal or adb? that is the best way to do it, any ways.... just get the directions from ra's 1.7 post
I'll try that, and let you know if it works!
Edit: One question(probably gonna sound really stupid..), I have DangerSPL. Is that the same as an engineering SPL?
Edit: ^Nevermind, found the answer.
michael2041 said:
I'll try that, and let you know if it works!
Edit: One question(probably gonna sound really stupid..), I have DangerSPL. Is that the same as an engineering SPL?
Edit: ^Nevermind, found the answer.
Click to expand...
Click to collapse
Didn't work. I flashed via terminal application. I typed what was required and pressed enter. Then I closed the terminal, and tried to reboot into recovery with home and power. What did i do wrong?
michael2041 said:
I'll try that, and let you know if it works!
Edit: One question(probably gonna sound really stupid..), I have DangerSPL. Is that the same as an engineering SPL?
Edit: ^Nevermind, found the answer.
Click to expand...
Click to collapse
not trying to be rude, why did you post this in development?
Oops, does this belong in Q/a?
ya Q&A but they will move it eventually... what was the message it gave you after you pressed enter...
I'm wondering if maybe you have a dodgy home button? In terminal emulator have you tried entering reboot recovery?
Try flashing through fastboot or even booting through fastboot...
fastboot boot recovery (then drag and drop recovery int cmd window)
fastboot flash recovery (do the same as boot)
shadowch31 said:
I'm wondering if maybe you have a dodgy home button? In terminal emulator have you tried entering reboot recovery?
Click to expand...
Click to collapse
that or try flashing recovery from terminal, not from clockwork`s app.
#flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img (assuming that you have the recovery-RA-dream-v1.7.0.img file in /sdcard. ) /sdcard will be the fat partition of your sdcard. at least you`ll see if there`s an error on flashing. after the flash_image command, may try to reboot as shadowch31 says. #reboot recovery (that whould reboot straight into recovery (if there is one - if not, reboot it with green+menu+red, let the battery be).
p.s. the death spl is not the same as the engineering spl. from what i know, it is like engineering spl but first of all it resize the partitions of your phone`s internal memory. it`s good that you have death spl.
p.s.2 - "#" symbol means that you run the command with su.
Thread moved to Q&A.
When I tried flashing via terminal app on the phone, it just goes to a new line when I press enter, no confirmation or anything. So should I try in fastboot?
michael2041 said:
When I tried flashing via terminal app on the phone, it just goes to a new line when I press enter, no confirmation or anything. So should I try in fastboot?
Click to expand...
Click to collapse
it`s normal to go straight to a new line. you should try to reboot into recovery
Okay, so I put the command into the terminal emulator. Went to the new line, and I waited for a little bit in case it was doing something.. then I did the reboot recovery command and nothing happened.
Now I tried turning off the phone and booting into "recovery" with home and power...endless g1 screen. What do I do next?
I did it via fastboot, and voila I have recovery! Thanks everyone for all their help. Now I can do my nandroid backup
i`m glad that you now have recovery. what did you do on fastboot ? flash_image or reboot recovery ? it`s really strange that the phone do nothing on "reboot recovery" from terminal.
I did flash_image from fastboot.
Related
ok i have run into this weird issue with my G1. it was working perfectly fine yesterday. i turned it off and charged it until it was fully charged like i usually do, but when i turned it on the boot loader screen flashed and the phone turned off! this happens whenever i try to turn the phone on. i cant get into recovery becuase the bootloader screen just flashes. when i try to get to the bootloader screen, it starts up fine but then looks for an image and turns off again. this started happening a few days after flashing haykuros spl if that helps. am i bricked or is there a way to fix this? thanks in advanced
edit: i am also usin the latest experimental build from cyanogen although i dont think this is the problem.
edit2: i managed to get my phone to start up, but im afarid to switch it off just incase it starts happening again so im still looking for a solution to this problem.
edit3: ok back to square one, my phone froze after fully booting up, restarted itself and now the problem is back! wow this is annoying.
it sounds like your camera button could be stuck. if you want to test this type reboot recovery into the recovery console and see if it boots into recovery or bootloader.
check and see if your camera button is stuck or partially stuck since you were able to boot it up once at least
Do you have fastboot working? if so, you can grab your nandroid backups from your SD card and flash them.
or go to cyanogens thread, download the recovery and flash the recovery using the fastboot command to install. i believe its
fastboot flash recovery recovery.img
but plz confirm before you do that
EDIT: david means use adb since you cant get into recovery
adb shell reboot recovery
B-man007 said:
Do you have fastboot working? if so, you can grab your nandroid backups from your SD card and flash them.
or go to cyanogens thread, download the recovery and flash the recovery using the fastboot command to install. i believe its
fastboot flash recovery recovery.img
but plz confirm before you do that
EDIT: david means use adb since you cant get into recovery
adb shell reboot recovery
Click to expand...
Click to collapse
he said he got the phone up and running i meant if he wanted to see if it was a software problem he could type reboot recovery into the terminal emulator and see if he got the bootloader screen or the recovery screen.
also i believe the fastboot commands you posted are correct.
ok thanks for the help guys. before reading your posts a left the phone for a few wins powered it on and now mt phone has booted up and it is working. i will try your solutions still though. i am not sure if i have fast boot working. when the bootloader screen flashed i do remeber it saying fastboot so does that mean i have it running?
edit: camera button seems to be fine although i havent tried the rebbot recovery yet though lol because i need my phone an im not sure if i can get it working again.
do you have adb set up
david1171 said:
do you have adb set up
Click to expand...
Click to collapse
yeah, although im using the 1.5 sdk and not the latest 1.6 does that matter?
if you have adb you will need to have the fastboot.exe (which i think is in the tools folder of the sdk) so cd to the sdk tools folder then use
fastboot flash recovery recovery.img
(also have the recovery.img in the tools folder for this)
ok thanks my phone froze so i had to turn it off and now i am back to square 1 again is there anything besides the camera button that could be casuing this?
djosiah said:
ok thanks my phone froze so i had to turn it off and now i am back to square 1 again is there anything besides the camera button that could be casuing this?
Click to expand...
Click to collapse
have you tried the fastboot flash recovery recovery.img command?
david1171 said:
have you tried the fastboot flash recovery recovery.img command?
Click to expand...
Click to collapse
i cant get into fast boot...the screen with 3 androids on skateboards flashes once really quickly and thats it :/
can anyone help me? the camera button seems to be fine and not stuck. is there another factor that could be causing this? i think i might try unrooting then going through all the steps to root it again. or flashing back to the hardspl and see what happens.
update: i managed to get the phone to boot up again so i went into terminal and typed reboot recovery and i got to the recovery screen ok, but when i pressed home + back to restart the phone the bootloader screen flashed again really quickly :/ it also seems like if i leave the phone off for a few hours it will power up fine but when it is turned off i have to wait another few hours til i can switch it back on.
djosiah said:
can anyone help me? the camera button seems to be fine and not stuck. is there another factor that could be causing this? i think i might try unrooting then going through all the steps to root it again. or flashing back to the hardspl and see what happens.
update: i managed to get the phone to boot up again so i went into terminal and typed reboot recovery and i got to the recovery screen ok, but when i pressed home + back to restart the phone the bootloader screen flashed again really quickly :/ it also seems like if i leave the phone off for a few hours it will power up fine but when it is turned off i have to wait another few hours til i can switch it back on.
Click to expand...
Click to collapse
this sounds like a hardware problem instead of a software problem since there is still a recovery screen, if your phone is still under warranty call your provider and see if there is anything they can do about it, and if they send you another one, just unroot the one you have
my phone isnt under warranty so looks like i will either have to put up with or buy myself a new one. thanks for the help.
If your sure your camera button isn't stuck, check your back button. If not, maybe some sweat or water got into it. some type of hardware dmg possibly. If your the do it yourself type of person, theres always this handy dandy notebook, I mean service manual
http://forum.xda-developers.com/showthread.php?t=468673
wilnotdie said:
If your sure your camera button isn't stuck, check your back button. If not, maybe some sweat or water got into it. some type of hardware dmg possibly. If your the do it yourself type of person, theres always this handy dandy notebook, I mean service manual
http://forum.xda-developers.com/showthread.php?t=468673
Click to expand...
Click to collapse
ahh yes that would make sense seeing as the bootloader screen says fastboot so it must be a problem with the back button. never thought of that. thanks for the help.
ok assuming that the back button is the problem, if i were to flash back to the hard spl would this problem go away seeing as fastobot mode only works with the 'special' spl?
Something very odd has happened. I reverted my phone back to stock via the .nbh file. Now when i reroot it and install cynagens recovery image it completes and when i try to boot the phone into recovery it freezes at the T-Mobile G1 screen and i have to pull out the battery to turn off the phone. anyone know the reason why my phone does this?
firstly, wrong section
secondly....can you boot normally? or in to fastboot (camera+power)?
if you can do any of these, then contrats....you bricked it
Edit: Oh ok my bad My eyes passed over the recovery and I thought he meant just rebooting.
try connecting your phone to your computer and do an adb logcat to see if its doing anything.
if you manage to get adb working while the phone is in the G1 screen then try fastbooting a new recovery image.
Moved as not Android Development.
he cant wipe and reflash if he cant get in to recovery
did you try going into terminal and flashing another recovery? maybe the file was corrupt
garok89 said:
he cant wipe and reflash if he cant get in to recovery
Click to expand...
Click to collapse
exactly.
I haven't been able to get ADB working with my phone. Yes i can boot normally and yes i can boot into fastboot. once I root the phone, I've tried to flash roms through the stock recovery, i cant seem to flash anything as i get an error. I have done this before multiple times on many of my friends phones. i followed the guide on wiki, stock g1 to cynagenmod, once I've flashed the cynagen recovery image my phone freezes at the T-Mobile G1 screen once I enter recovery.
SmokeyJBluntz said:
did you try going into terminal and flashing another recovery? maybe the file was corrupt
Click to expand...
Click to collapse
Yes I tried flashing Amon Ra Recovery with the same result.
http://cyanogenmod.com/download/recovery/cm-recovery-1.4.img
Go to terminal emulator and type:
flash_image recovery /sdcard/cm-recovery-1.4.img [enter]
Did you try using fastboot to erase the existing recovery and then install a new one?
junkdruggler said:
http://cyanogenmod.com/download/recovery/cm-recovery-1.4.img
Go to terminal emulator and type:
flash_image recovery /sdcard/cm-recovery-1.4.img [enter]
Click to expand...
Click to collapse
Yea, do that. There's no reason that should be happening. Did you use the good ol' fashioned flashrec.apk? That's how I got my first recovery and started flashing (from stock.)
whats the error you get flashing? i know when i rooted my phone i Fd up by doing the OTA update. it removed the flash command from terminal and console. i had to go at it again. start fresh. downgrade, root....
junkdruggler said:
http://cyanogenmod.com/download/recovery/cm-recovery-1.4.img
Go to terminal emulator and type:
flash_image recovery /sdcard/cm-recovery-1.4.img [enter]
Click to expand...
Click to collapse
Just did this same result.
SmokeyJBluntz said:
whats the error you get flashing? i know when i rooted my phone i Fd up by doing the OTA update. it removed the flash command from terminal and console. i had to go at it again. start fresh. downgrade, root....
Click to expand...
Click to collapse
when i run into an error i downgrade with the .nbh file that i got off the cynagen wiki and try again.
where do you get the error?(or is the "error" it not doing what you want?)
in terminal emulator? did you reboot to recovery from terminal after? or with the end button? (type: reboot recovery[enter] in terminal)
are you giving it enough time to actually flash the recovery before you pull the bat? (sometimes it takes a lil bit)
try erasing the recovery image via fastboot.
then flash the Amon_RA recover image.
junkdruggler said:
where do you get the error?(or is the "error" it not doing what you want?)
in terminal emulator? did you reboot to recovery from terminal after? or with the end button? (type: reboot recovery[enter] in terminal)
are you giving it enough time to actually flash the recovery before you pull the bat? (sometimes it takes a lil bit)
Click to expand...
Click to collapse
Well the thing is, I'm not getting an error. Here I'll explain step by step what i did. Maybe I did something wrong.
1) Placed the DREAMIMG.nbh file from wiki in the root of my sd card.
2)Pressed power and camera button to get the phone to bootloader. Followed the onscreen instructions to install the image.
3)Went through the sign in steps to get my phone to the home screen.
4)Followed the steps on wiki to root the phone pressed enter twice and typed "telnetd".
5)opened market and downloaded telnet.
6)pulled out my sdcard and put the cm-recovery-1.4.img on my sdcard.
7)opened telnet hit connect.
8)typed flash_image recovery /sdcard/cm-recovery-1.4.img and waited for the ## after that. like it says in the wiki.
9)placed the files from the wiki on the sdcard.
10)reboot the phone to recovery via power and home button. but this is where my phone freezes at the T-Mobile G1 screen.
11)pulled out the battery after waiting 10 min and just pressed the power button and the phone booted up fine. tried again via the telnet and typed "reboot recovery" same result.
12) i reformated my sdcard placed the DREAMIMG.nbh and tried steps 1-11 with same result.
i have even tried a different recovery Amon Ra's recovery as well with the same result. and worst of all ive been a few days with the 1.0 software without an ota update.
any suggestions?
This isnt the first time ive done this with a G1. ive even done this on my wifes MT3G and it worked flawlessly. Ive done it on 2 othe G1's but mine wont seem to take it. whats the deal?
I am noticing a something when under original recovery. Something that i havent seen until now. when i press alt + L it brings up the text and it says " Android system recovery utility E: Can't open /cache/recovery/command"
then it brings up usual commands like Alt + L, Alt+S, and Alt+W. but when i try to install even the official updates it says
Installing from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:No signature (5 files)...
E:Verification failed
Installation aborted.
Press Home+Back to reboot
could this mean anything or be the reason for the problems im running into?
it might just be that the ROM you were trying to flash wasnt signed correctly.
ernvillanueva90 said:
Well the thing is, I'm not getting an error. Here I'll explain step by step what i did. Maybe I did something wrong.
1) Placed the DREAMIMG.nbh file from wiki in the root of my sd card.
2)Pressed power and camera button to get the phone to bootloader. Followed the onscreen instructions to install the image.
3)Went through the sign in steps to get my phone to the home screen.
4)Followed the steps on wiki to root the phone pressed enter twice and typed "telnetd".
5)opened market and downloaded telnet.
6)pulled out my sdcard and put the cm-recovery-1.4.img on my sdcard.
7)opened telnet hit connect.
8)typed flash_image recovery /sdcard/cm-recovery-1.4.img and waited for the ## after that. like it says in the wiki.
9)placed the files from the wiki on the sdcard.
10)reboot the phone to recovery via power and home button. but this is where my phone freezes at the T-Mobile G1 screen.
11)pulled out the battery after waiting 10 min and just pressed the power button and the phone booted up fine. tried again via the telnet and typed "reboot recovery" same result.
12) i reformated my sdcard placed the DREAMIMG.nbh and tried steps 1-11 with same result.
i have even tried a different recovery Amon Ra's recovery as well with the same result. and worst of all ive been a few days with the 1.0 software without an ota update.
any suggestions?
This isnt the first time ive done this with a G1. ive even done this on my wifes MT3G and it worked flawlessly. Ive done it on 2 othe G1's but mine wont seem to take it. whats the deal?
Click to expand...
Click to collapse
http://zenthought.org/content/project/flashrec
try to downgrade and use it. thats how i originally got r00t.
I have a Mytouch 3G running test 7 on my phone, and i just installed the clockworkmod rom manger. After, installed it i wanted to flash a new rom, so flashed the clockwork mod recovery, and when i tried to install the new rom from the sd card, it keeps on getting stuck on the mytouch screen, and nothing happens. How do i get into the recovery screen? thanks
First: This belongs in Q & A !!!!111
Which ROM did you flash? Maybe you had to wipe before
right now, i'm running cyanogen test-7, but when i go into the clockworkmod rom manger app and pick the flash rom from sd card, it just says it has to go to the recovery, and then my phone will reset and it would just get stuck on the mytouch screen. So, i just pull out the battery and reset the phone again, and i realized if i press the end button, it will go the rom that is already on the phone. I'm i suppose to push some buttons or something to get to the recovery screen?
No it should flash the rom you select and reboot the phone to boot the new rom without keypress needed.
maybe the wrong device was selected when downloading the recovery image? Try reinstalling clockworkmod recovery from rom manager.
Mod edit: not dev related, moved to q&a
I have the same problem.
I downloaded and installed Rom Manager from the Market and it has completely screwed up my recovery (I can't get into it at all). I tried flashing Amon's again (through Rom Manager) and it still doesn't work.
HTC G1. CM5.07 test 7 (trying to go to stable!).
Your recovery has been corrupted, you will need to flash it through fastboot.
JAguirre1231 said:
Your recovery has been corrupted, you will need to flash it through fastboot.
Click to expand...
Click to collapse
Yes thank you. I erased recovery partition in fastboot then reflashed Amon's.
Working now.
i got into the fastboot screen, but i have 4 options. hboot mode, reset device, restart to hboot, and power down. how do i flash from here?
illmatic282 said:
i got into the fastboot screen, but i have 4 options. hboot mode, reset device, restart to hboot, and power down. how do i flash from here?
Click to expand...
Click to collapse
Connect to your PC via USB, and from the command line issue "fastboot erase recovery" and then "fastboot flash recovery filename.img"
More on common fastboot commands here can be found on these forums, i'm not allowed to post links.
i connected my phone to my computer but nothing on my computer pops up. only the new hardware wizzard pops up. what do i do from here? im i suppose to get a adb popup? how do i set up the fast boot? i'm so confused..thanks
some one, please help..i want to be able to flash new roms in the future...thanks in advance
Can I sugges that you try this sticky thread at the top of this forum board.
It contains all you need to know on who to set up fastboot and how to use it - there are a couple of tutorials on it if you read through the thread.
CM 5.0.7 for Dream/Sapphire introduced a bug in flash_image. It causes recovery flashes to fail. It has since been fixed in the latest test of 5.0.8 I believe.
Man i have the same darn bug cant get back into recovery for nothing, and i dont have a pc to fastboot i have a non intel based mac so no adb or fastbooting, i have been doing fine for forever without adb or fastboot but is there any way around this one, i need help bad, im on HTTClay Superbadv1.3 and it has all sorts of bugs but i cant nandroid or bart or flash any rom without recovery, can someone please help!!!
Also is there another way to erase the recovery partition?
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
hey guys, i hope somebody can help me...
i tried to load a new rom to my magic and rooted it. after some flashing i cant get into fastboot or recovery menue. i onle see the "htc magic" screen at my vodafone branded magic.
so is there anybody who can help? - i cant establish a connection via usb too
are you keeping hold of home+back whilst turning the phone on to enter fastboot?
I just posted this for someone on the cyanogenmod forum, hopefully it helps...
I had the same problem the night before last, I was flashing the newest ra revovery through terminal and I believe I made some typos or did not wait long enough and of course I forgot to type su the first couple times... silly me
but after trying a couple times I got it back through terminal.
You can try it through terminal, although theres issues with doing this in cyanogen mod 5.0.7, I'm not sure if the newer roms have the same issues.
but I believe the problem was a few people lost their recovery completely (which obviously wont matter to you) I've done it succsessfully from a donut rom, but havent tryed it from anything higher so I cant promise it will work.
if you want to try:
Open terminal emulator
type: su
hit enter and allow superuser permissions.
type: flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
(or the name of whatever ra recovery is on your sd card)
hit enter and wait a few minutes just to be sure.
then close terminal and try to reboot into recovery.
if it doesent work the first time check and make sure everything was typed correctly and try again.
Also you can just re-root the phone, that should fix it, its a pain though lol
I just rooted & flashed my Rogers Dream with cm 5.0.8 last weekend and it would freeze on the boot logo (Rogers) and I thought the same thing had happened. I could get to the recovery though.
I realized that you have to install the ROM and the Kernel Patch (I didn't do this) and once I applied the Brian Cook Kernel Patch, the phone booted immediately.
I don't know if this is the same problem you have but hopefully this info will help.
Cheers.
I would try re-rooting if you can. Unlockr . com has kinda an interesting method that might work.
D-