Related
Edit: ****, ok so my phone isn't booting up now..the phone just freezes at the g1 splash logo.
I can still get into recovery console/bootloader, can I save my phone? Help!
I do have other theme's in /sdcard/themes/
I don't know if I can delete the current update.zip in my root and move one of them to the root and rename it, then flash that on? Someone please help!
-Ok so, I have the sdk...
-I'm in fastboot mode
-I have the correct driver for the phone, windows picks it up
but when adb doesn't pick up the devices, is there something I need to do to "get started" so to say? I'm trying to install some themes and push the browser.apk into the phone but, im stumped
tehseano said:
Edit: ****, ok so my phone isn't booting up now..the phone just freezes at the g1 splash logo.
I can still get into recovery console/bootloader, can I save my phone? Help!
I do have other theme's in /sdcard/themes/
I don't know if I can delete the current update.zip in my root and move one of them to the root and rename it, then flash that on? Someone please help!
-Ok so, I have the sdk...
-I'm in fastboot mode
-I have the correct driver for the phone, windows picks it up
but when adb doesn't pick up the devices, is there something I need to do to "get started" so to say? I'm trying to install some themes and push the browser.apk into the phone but, im stumped
Click to expand...
Click to collapse
First, you are at the wrong screen. You should not be in fastboot mode in the bootloader for updating themes, you should be in recovery mode.
I suggest you perform a wipe to possibly bring your phone back to normal at least. It can be done by turning off the phone, then pressing and holding the back and home button until you enter recovery mode.
From there press alt + w to wipe the phone.
Then restart by pressing back + home.
Next, before installing the theme, make sure its the correct one for your phone. Check with the author if it was made for RC30 or RC8, and if it is a non-wipe theme, because if it is not, you will be stuck at the Tmobile G1 splash screen (aka be in an indefinite loop) like your current situation.
If you are trying to install browser.apk (im assuming the multitouch browser - please correct me if im wrong) you will need to install JF 1.41 first. By default it will include the multitouch version of browser.apk
Please provide more information about your situation, and keep us posted.
andonnguyen said:
First, you are at the wrong screen. You should not be in fastboot mode in the bootloader for updating themes, you should be in recovery mode.
I suggest you perform a wipe to possibly bring your phone back to normal at least. It can be done by turning off the phone, then pressing and holding the back and home button until you enter recovery mode.
From there press alt + w to wipe the phone.
Then restart by pressing back + home.
Next, before installing the theme, make sure its the correct one for your phone. Check with the author if it was made for RC30 or RC8, and if it is a non-wipe theme, because if it is not, you will be stuck at the Tmobile G1 splash screen (aka be in an indefinite loop) like your current situation.
If you are trying to install browser.apk (im assuming the multitouch browser - please correct me if im wrong) you will need to install JF 1.41 first. By default it will include the multitouch version of browser.apk
Please provide more information about your situation, and keep us posted.
Click to expand...
Click to collapse
Sorry, I should have provided more information, and explained that the 2nd half of this post was my original post, which was just me asking how to correctly use ADB. I do already have JF 1.41, I upgraded yesterday. It wasn't my first theme I installed either. I was using Vintage War (for the Dream), but it hadn't been updated for 1.41, so I was trying the standalone apk adb push method found in this forum, which is where this post first oriented.
I was in recovery mode for installing themes, I'm using JF 1.41 RC30, with the HardSPL bootloader. Initially after installing the theme it would go blank after the g1 splash, so I had tried to install it again hoping it would fix it, unfortunately my thumb is a bit to fat and I hit alt W instead of S, anyways that is what put me into this infinite loop.
But like I said this wasn't my first time trying to mod the phone, I've had it rooted for a month or so now, and have been keeping up-to-date.
Any more information I can provide, please let me know. My phone is my livelyhood, I need it. So if anyone can help, the sooner would be better. Either way I am entirely greatful for any help anyone can provide. Thanks in advance!
tehseano said:
I was in recovery mode for installing themes, I'm using JF 1.41 RC30, with the HardSPL bootloader. Initially after installing the theme it would go blank after the g1 splash, so I had tried to install it again hoping it would fix it, unfortunately my thumb is a bit to fat and I hit alt W instead of S, anyways that is what put me into this infinite loop.
Click to expand...
Click to collapse
It is weird how a wipe caused you to go into an infinite loop. Which apk's did you try to push to your phone?
I would suggest to go without using the theme for now. JesusFreke had pointed out that some themes were causing problems for the new 1.41. update. You should check with the author of the theme to see if its compatible with the new 1.41 (which it should be since RC30 1.3, RC30 1.31, and RC30 1.41 are all compatible)
andonnguyen said:
It is weird how a wipe caused you to go into an infinite loop. Which apk's did you try to push to your phone?
I would suggest to go without using the theme for now. JesusFreke had pointed out that some themes were causing problems for the new 1.41. update. You should check with the author of the theme to see if its compatible with the new 1.41 (which it should be since RC30 1.3, RC30 1.31, and RC30 1.41 are all compatible)
Click to expand...
Click to collapse
....How do I get out of the loop. My phone doesn't get passed it. There has to be something I can do in console or recovery or something. I'm really sorry if I'm coming off as rude or demanding but I really need a phone, and I need it right now. I don't know what more I can tell you before someone can finally give me a solution (sorry)
1. Download RC29
2. Copy it onto your sdcard
3. Reboot your phone into the SPL with Power+Camera
4. When prompted, press the end key to start the reflash.
Note: this will completely wipe the flash chip on your phone and revert everything back to factory. You will need to re-root your phone and update to JF1.41
Next time, use nandroid to backup before installing themes, etc.
Datruesurfer said:
1. Download RC29
2. Copy it onto your sdcard
3. Reboot your phone into the SPL with Power+Camera
4. When prompted, press the end key to start the reflash.
Note: this will completely wipe the flash chip on your phone and revert everything back to factory. You will need to re-root your phone and update to JF1.41
Next time, use nandroid to backup before installing themes, etc.
Click to expand...
Click to collapse
Alright, I'm doing it now. And I did use nandroid and make a backup, no one said anything about how to restore it. Regardless thank you so very much, you are my Savior right now!
tehseano said:
Alright, I'm doing it now. And I did use nandroid and make a backup, no one said anything about how to restore it.
Click to expand...
Click to collapse
That's easy. Just grab a copy of the fastboot utility and the images off your sdcard in the 'nandroid' directory and boot your phone into the SPL. Plug your phone in via usb and press the back button once and you should see "Serial0" change to "FASTBOOT" Then open up a windows command prompt in the location of the exe you downloaded and run:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
fastboot reboot
Your phone will come back up with all of your applications, settings etc from when you did the backup. Keep in mind you need the HardSPL to do this though(look for three androids on skateboards in SPL). The G1 factory bootloader does not support fastboot, only NBH images that come from the factory.
Hi, my situation is a bit worse:
I have a Dev Phone, upgraded to JFv1.41.
Today, I got the pop up message telling me to do a "system holiday update 2 of 2". I press "Update now" and the phone got reboot. Since then... I could not get through the first screen that has the word "Android" at all, not even to the screen where Android icon is flashing. It just freezes right there.
The only way to turn off is to take out battery. I could not enter recovery mode through pressing Home+Power. One time, the screen actually turned into weird color patterns. Is there anything I can do? consider that I don't have any nandroid back up image at all?
I tried to download the DREAIMG-RC29.zip, unzip and copy to the sdcard, then reboot into the SPL with Power+Camera but nothing happens, just a 4 color screen said "serial0".
Thanks in advance.
Isn't the 4 color screen the standard bootloader that ships with retail G1's (not a dev phone bootloader)?
lugiamx said:
Hi, my situation is a bit worse:
I have a Dev Phone, upgraded to JFv1.41.
Today, I got the pop up message telling me to do a "system holiday update 2 of 2". I press "Update now" and the phone got reboot. Since then... I could not get through the first screen that has the word "Android" at all, not even to the screen where Android icon is flashing. It just freezes right there.
The only way to turn off is to take out battery. I could not enter recovery mode through pressing Home+Power. One time, the screen actually turned into weird color patterns. Is there anything I can do? consider that I don't have any nandroid back up image at all?
I tried to download the DREAIMG-RC29.zip, unzip and copy to the sdcard, then reboot into the SPL with Power+Camera but nothing happens, just a 4 color screen said "serial0".
Thanks in advance.
Click to expand...
Click to collapse
I had the same problem, almost verbatim. ADP1.1, JFv1.41, ran the Holiday update 1 of 2, no problems, did the 2 of 2 update, got stuck at the flashing Android boot screen. Pulled the battery, rebooted, same thing, waited 2-3 minutes at the flashing screen and was just about to pull the battery again and then all of a sudden the damn thing came to life, the OS loaded up and now everything's working fine. Gave me quite a scare.
ummm actually the fastboot utility wont work for my computer soo what shoud i do.... if anything i need a really good reply something long cause im new to this and my fone wont get off the android sign.
chinoman said:
ummm actually the fastboot utility wont work for my computer soo what shoud i do.... if anything i need a really good reply something long cause im new to this and my fone wont get off the android sign.
Click to expand...
Click to collapse
Why have you just hijacked a 5 month old thread? You haven't given use any details either. Fastboot is available for all OS's, it will work on your computer, you just probably don't know how to use it. Please make a new thread in the Q&A section where we can help you out there.
This should be closed or moved to Q&A.
hey man just unroot ur phone and root it again u soft bricked ur phone its ok
hey just try to unroot k
hey if u want me to fix it for u just email me at [email protected] and ill help u
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.
Okay so im sure the answers for this are here in this forum, but this forum is huge and Ive been working on this for 2 days now. Just got a G1. Want to put ANY rom on it at this point. Ive tried following the "[GUIDE] STOCK-2-CYANOGEN" sticky in the development forum several times, to a T, and cant seem to even get past the 3rd step.
Ive started this over and over again - here's my process. Put DREAMIMG.nbh on my newly formatted FAT32 2GB SDcard. Reboot, get into bootloader, flash the phone with the update. Phone restarts, I enter my google info in, Im on the phone. I place cm-recovery-1.4.img on the sdcard root (ive tried two others and they have the same outcome) Now I root, which took awhile to work in the first place.. enter enter, telnetd, enter, go to market and download telnet. connect localhost. I type this:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery cm-recovery-1.4.img
cat cm-recovery-1.4.img > /system/recovery.img
....everythings gravy, no errors thrown, etc. I put the Hard SPL update.zip on the root of the sdcard, i shut phone off. Attempt to go to bootloader, it stalls on the G1 splash screen, and Ive waited up to 30 mins, before i ultimately have to remove the battery. I cannot load into, or add a new recovery console so I can even continue attempting to flash ANY rom. SO, I start from scratch...over, and over again. Unroot the phone, reload original bootloader, and they work. 2 days in circles!
Now I normally can figure these types of things out, especially with research that this forum has plenty of, but im at my wits end. WTH am i doing wrong I cant follow these guides any better than word for word! Man Ill PAY someone to just get a rom loaded for me at this point heh
wow that guide is old use this one
http://wiki.cyanogenmod.com/index.php/Main_Page#Upgrading_from_Vanilla:_Installing_your_first_mod
okay this is where Im getting hung up on. I did all of that, and once I turn off my phone to install the actual OS, this part "Flash Android1.6 & CyanogenMod latest", i hold home and press power, then the Tmobile G1 splash appears and just hangs... Never proceeds to the recovery option or anything for that matter, without taking out the battery. It doesnt do this when I have it stock, just after i flash cm-recovery-1.4.img
I've no idea if you'll get different results, but you could try flashing Amon_RA's recovery instead of cyanogen's. Just change cm-recovery-1.4.img to recovery-RA-dream-v1.6.2.img (or whichever version you choose).
http://forum.xda-developers.com/showthread.php?t=566669
Okay so I just used Amon_Ra's, followed the instructions and flashed it via terminal, with no errors, just the same as cm_recovery reacts. Shut off fone, and tried home+power. Its frozen on the G1 splash............... How is it if I actually just revert it back to unrooted stock, the recovery console works fine..but any of the updated ones I need to use to get a ROM just will NOT work..?? Please help, im seriously going on like 17 hours with this thing...I genuinly will pay someone if we get this figured out! So very desperate!
hmm strange.
in terminal type
su <enter>
reboot recovery <enter>
Or from command prompt if you have adb setup
adb reboot recovery <enter>
see if that gets you into recovery correctly.
I apologize, I forgot to mention I had done that also, shortly after my last post.. Its not like im not doin the research here hehe. I did the $su, then reboot recovery. it rebooted, and froze at the same splash. I dont have adb, nor know what it is. This shouldnt be this complicated i wouldnt think. Do u think its something wrong with my phone that I cant simply load an alterate recovery image? I mean, it DID work before I had to continually set this thing back to stock..
just fyi, bc ive seen other ppl have this problem..i resolved the issue by reloading dmd64 firmware, then starting over again. I also used recovery-RA-dream-v1.5.2 instead of recovery-RA-dream-v1.6.2 or cm_recovery. Not sure if this made a difference in addition to updating to dmd64, but i was finally able to boot in to recovery and flash the images
I've got the exact same problem !!!
I've installed and used custom ROMs for over a year now, and last week I tried to upgrade to CM5 and since then, I haven't been able to use any other custom ROM, only the official HTC ADP1.6 stock ROM (which sucks...).
Each time I install one, it freezes on the G1 screen and nothing happens (even restoring my pre-CM5 nand backup does the same, it freezes on G1 screen )
Haven't had time to try yet (and honestly, I'm a bit tired of reflashing my phone, I need it sometimes and those things take a lot of time...), but I'm going to try switching back from Amon Ra's latest to Cyan's 1.4 recovery, reflash adp1.6 and a superD right after it, without rebooting to see if it works.
I'll let you know if it works (and then wait for official Froyo, if it ever comes out for the G1, with its official Apps2SD...)
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-
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.