I am very new at the whole root and rom process so i took the time to read through to forums to see if i could walk through it to get a rom.
When i tried to root my phone everything was okay, but when it was finished it said press the action key, instead of rebooting. when i pressed the action key it went back to the original screen and said serial0.
I went through all that because when i tried to install the rom, it said no signature and verification failed.
can some one help me fix this?
thanks in advance.
shockaj said:
I am very new at the whole root and rom process so i took the time to read through to forums to see if i could walk through it to get a rom.
When i tried to root my phone everything was okay, but when it was finished it said press the action key, instead of rebooting. when i pressed the action key it went back to the original screen and said serial0.
I went through all that because when i tried to install the rom, it said no signature and verification failed.
can some one help me fix this?
thanks in advance.
Click to expand...
Click to collapse
What ROM are you trying to install? It's a problem with the ROM most likely, not your phone.
shockaj said:
I am very new at the whole root and rom process so i took the time to read through to forums to see if i could walk through it to get a rom.
When i tried to root my phone everything was okay, but when it was finished it said press the action key, instead of rebooting. when i pressed the action key it went back to the original screen and said serial0.
I went through all that because when i tried to install the rom, it said no signature and verification failed.
can some one help me fix this?
thanks in advance.
Click to expand...
Click to collapse
It's hard to tell how far you got in the root process.. When you reboot into recovery (Home+Power) what does the screen look like?
Like the other poster said, it could be a problem with the ROM. But it could also be that you have the stock recovery image (which won't flash a modded ROM, since it is signed with the wrong keys).
i am trying to install the newest Cyanogen rom and i probably have the stock recovery img... how do i get a new one, i believe i downloaded my from http://forum.xda-developers.com/showthread.php?t=442480 but there is a possibility i didnt..
Not knowing where you are in the process of getting root, it's probably best to assume you don't have it, and go ahead and make sure your phone is fully rooted first. I read a few guides when I was starting - the first one that really made a lot of sense was Gizmodo's:
http://gizmodo.com/5146797/how-to-hack-android-for-multitouch-web-browsing-on-the-t+mobile-g1
Follow that, step by step. If any step doesn't react the way they say it will, you may need to start over. Once you finish that guide, you should be able to flash nearly any other ROM (other than Hero ROMs that need the "Danger" SPL - avoid until you study more).
After you've completed the guide for rooting, you can upgrade to the Cyanogen recovery (awesome because it lets you backup & restore your phone on the go, no PC needed) and CyanogenMod 3.6.5
Download this:
http://n0rp.chemlab.org/android/cm-recovery-1.3.1-signed.zip
Rename it to update.zip
Put it on the root of your SD card
Reboot into recovery (Home+Power)
Alt-S to flash it
Home+Back to reboot
Then download this:
http://n0rp.chemlab.org/android/update-cm-3.6.5-signed.zip
Rename it to update.zip
Put it on the root of your SD card (replace the last file we put there)
Reboot into recovery (home+power)
Alt-W to wipe
Alt-S to flash
Home+Back to reboot
Then you're all set. If you get lost at any point, just come back and tell us what's going on.
thanks Saiboogu. i got to the telnet, but when trying to connect to local host is says error while connecting to server error while receiving from server: null
shockaj said:
thanks Saiboogu. i got to the telnet, but when trying to connect to local host is says error while connecting to server error while receiving from server: null
Click to expand...
Click to collapse
OK - So you flashed DREAIMG.NBH, right? Go to Settings > About phone and scroll down to Build number - make sure it says RC29 somewhere in that string.
If that's right, just make sure you are launching telnetd correctly..
Press Home
Press Enter
Press Enter
type telnetd
Press Enter
You should wind up in your contacts searching for "telnetd" - if that's what you see, you probably did it right.
Then try the telnet client again. If that doesn't do it.. Sorry, I'm stumped. Hopefully someone else will chime in.
When i typed in [enter] [enter] telnetd [enter] nothing happens. it just remains as being searched...
also it is RC29
shockaj said:
When i typed in [enter] [enter] telnetd [enter] nothing happens. it just remains as being searched...
Click to expand...
Click to collapse
That sounds right -- All you'll see is the phone searching your contacts for telnetd, but if you did that exactly right, it should have run in the background. Then, run the telnet app on the phone and connect to localhost... Work this time?
Thanks that was the porblem.. i was able to get into the root and install the Cyanogen fine, but now that it is booting up the android screen tries to load then flickers, and it is stuck in this rotation....
That's a boot loop. Did that happen as soon as you installed CM3.6.5? Sounds like you need to flash again, maybe download and then flash again - sometimes the download can get corrupted. Also, make sure you wipe *first,* then flash. If you do it the other way, things can break.
nevermind i just wiped it again then reinstalled it and it worked, thanks so much for your help, i would have never finished this without yuo!
No problem at all, glad you got it. Now that you're all set, make sure you boot into recovery and perform a Nandroid backup - gives you lots of freedom to try things, knowing you can come back to a good working copy.
thanks thats great advice knowing me its only a matter of time!
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
Hello all, I have a friend with a G1 that is currently running Cyanogen 4.0.4. He is interested in updating to the latest stable release, but has had trouble booting after he does. Since I have no experience with the G1 or Android in general, I was hoping someone might be able to walk us through the process.
I know his phone is rooted, but I'm not sure what he used to do so. I also think he could probably use a radio update.
Thanks for your time!
xiton said:
Hello all, I have a friend with a G1 that is currently running Cyanogen 4.0.4. He is interested in updating to the latest stable release, but has had trouble booting after he does. Since I have no experience with the G1 or Android in general, I was hoping someone might be able to walk us through the process.
I know his phone is rooted, but I'm not sure what he used to do so. I also think he could probably use a radio update.
Thanks for your time!
Click to expand...
Click to collapse
This link provides all the steps needed to upgrade from 4.0.4 to the current release
http://wiki.cyanogenmod.com/index.p...version_less_than_4.1.99_or_other_rooted_ROMs
Download the Android 1.6 Recovery Image (it has "-ota-" in the filename):
http://www.4shared.com/file/164243978/15081498/signed-dream_devphone_userdebu.html
Download the latest CyanogenMod ROM for your device:
http://n0rp.chemlab.org/android/upda...7.1-signed.zip
1) Hold power and turn the phone off
2) Start up in recovery mode by holding home and pressing power.
3) You are now in recovery mode.
4) Press Alt-W to wipe all data
5) Press Alt-A to apply any zip from sd
6) Choose signed-dream_devphone_userdebug-ota-14721.zip (You won't see the entire filename)
7) When it is done it will ask you to reboot to complete the installation. Press Home+Back
8) You will be returned to the recovery screen in a few minutes, be patient.
9) Press Alt-A to apply any zip from sd
10) Choose update-cm-4.2.7.1-signed.zip
11) After the update is complete, hold Home and press Back to restart. (May take up to 15 minutes to boot)
12) Complete the setup process
i have looked everywhere (i think) for signed-dream_devphone_userdebug-ota-14721.zip Where did it go... i'm also on 4.0.4 and want all the googly goodness if you have- or- can find a link?? thanks so much. i've learned alot from u guys, sorry for not posting
Found a mirror using the Google (real complicated stuff, not recommended for beginners)
http://pomac.netswarm.net/mirror.html/mirror/android/adp1/android-1.6
It has both
signed-dream_devphone_userdebug-img-14721.zip
&
signed-dream_devphone_userdebug-ota-14721.zip
yozpalang said:
Download the Android 1.6 Recovery Image (it has "-ota-" in the filename):
http://www.4shared.com/file/164243978/15081498/signed-dream_devphone_userdebu.html
Download the latest CyanogenMod ROM for your device:
http://n0rp.chemlab.org/android/upda...7.1-signed.zip
1) Hold power and turn the phone off
2) Start up in recovery mode by holding home and pressing power.
3) You are now in recovery mode.
4) Press Alt-W to wipe all data
5) Press Alt-A to apply any zip from sd
6) Choose signed-dream_devphone_userdebug-ota-14721.zip (You won't see the entire filename)
7) When it is done it will ask you to reboot to complete the installation. Press Home+Back
8) You will be returned to the recovery screen in a few minutes, be patient.
9) Press Alt-A to apply any zip from sd
10) Choose update-cm-4.2.7.1-signed.zip
11) After the update is complete, hold Home and press Back to restart. (May take up to 15 minutes to boot)
12) Complete the setup process
Click to expand...
Click to collapse
iirc, his loader only lets you upgrade if you rename the files to update.zip. whats the one you are using that lets you preserve filenames?
xiton said:
iirc, his loader only lets you upgrade if you rename the files to update.zip. whats the one you are using that lets you preserve filenames?
Click to expand...
Click to collapse
If you can only apply "update.zip" you probably want to upgrade the recovery image
What recovery are you on?
Are you sure the phone is rooted and you're not at the stock recovery?
Either way give Cyanogen's Wiki a read, there's a lot more info there
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
jackslim said:
If you can only apply "update.zip" you probably want to upgrade the recovery image
What recovery are you on?
Are you sure the phone is rooted and you're not at the stock recovery?
Either way give Cyanogen's Wiki a read, there's a lot more info there
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
Click to expand...
Click to collapse
Thanks for all the info. I'm going to forward the info to him, since I'm not sure what he's running atm.
xiton said:
iirc, his loader only lets you upgrade if you rename the files to update.zip. whats the one you are using that lets you preserve filenames?
Click to expand...
Click to collapse
get the CM recovery here the update to this one here then you can apply any zip
yozpalang said:
please don't comment if you don't know what you are talking about
Click to expand...
Click to collapse
That's the OP asking for clarification because he's still lost
jackslim said:
That's the OP asking for clarification because he's still lost
Click to expand...
Click to collapse
sorry ,my bad
Needing some assistance as well.
The steps outlined on Cyanogen's wiki are dead simple. I followed them to the letter (save for installing the Hard SPL).
The problem is when my phone gets to the above listed step 11, it reboots and sits at the T-Mobile G1 logo. This is my second attempt to make the rooting/new mod changes and I let it sit at the logo for over an hour with zero change on the boot screen.
I have already installed the dreaimg.nbh, and I have DL's (3 times fro 2 different sources) the "signed-dream_devphone_userdebug-ota-14721.zip" and the "update-cm-4.2.7.1-signed.zip" and can use the 'apply any zip' option from the recovery menu.
The process itself seems to go fine (i.e. installing/formatting, blah blah blah) but the final reboot does nothing.
So, I am at a loss why apparently installed OS simply will not boot. Odd thing, is that I left my blue tooth headset on by accident and upon the last reboot, I hear it connect! It's almost as if it does boot up but will not change the screen.
I setup a second machine(Karmic Ubuntu) strictly for ADB but haven't the best clue on how to get it to work. While in the recovery menu I can issue "adb shell reboot" and the phone reboots but I cannot get the status. Even when trying "adb usb". Either I get 'device not found' or "connection closed" with either of those commands.(Not recalling which at the moment).
After this 'stuck on G1 logo', I can reboot and 'restore latest backup'(as noted in Cyanogen's steps) and the OS loads (although it is buggy as hell when trying to use any browsing, signal cuts in and out, drops carrier and gets it back.....severely annoying)
So....could use some real guidance.
As it stands:
OS: kila-user 1.0 TC4-RC29 115247 ota-rel-keys, release-keys
Recovery menu shows "Build: CyanogenMod v1.4 + JF" at the bottom.
Where to go from here?
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.
Hello
i have a problem with my nexus one,
i tried to install some theme's and it whent horribly wrong.
when ever i boot my nexus one it tells me prosesses have stopped unexpectedly, and it shuts down again. and it stays in this loop.
now ive tried to recover my phone a few times with
"fastboot devices"
"fastboot flash recovery "image file""
how ever the command promt doesnt go beyond "waiting for device"
i think the problem is that USB debugging is turned off, is there any way of turning this on without haveing to go to settings ? (couse yeh i cant get there)
please help me on this one
hope im not totaly f-ed
//Duvel
sorry if there are typo's im dutch
did you put the phone into fastboot mode, before you tried the fastboot command? and second, why are you flashing the recovery image? that won't fix you phone
i think you should try a factory reset, either by flashing your rom again or by selecting some option. what rom do you have installed? stock? if not, which and which recovery image do you have installed? there is an option in amon_ra's image do factory reset. i never used the stock recovery, but there should be an option to wipe there as well. anybody?
ps: please stop using fastboot and adb commands, if you are don't know what you are doing, before you brick your phone.
i used the following guide to root
forum.xda-developers.com/showthread.php?t=636795
i just stoped at the part where the sence ui was installed,
yes i put my phone into fastboot mode but again i think the problem is that i cant enable USB Debugging
ok i just recovered my phone with the following image
"CyanogenMOD version : recovery-RA-nexus-v1.7.0-cyan.img"
how ever im still getting unexpected application stops,
com.android.setupwizard
com.android.bluetooth
com.android.callender
com.android.mms
any idea on how to restore them ?
maybe its usefull to know i tried to use the morph "BlackMatteMorph"
from the following thread "forum.xda-developers.com/showthread.php?t=654858"
//Duvel
got it fixed now
thanks alot FloOGB some of your pointers realy helped me out,
i fixed it by installing the drivers provided by th3fallen
"forum.xda-developers.com/showthread.php?t=613217"
after that i followed the following steps got from from a post of Jeremy Sikora
"forum.androidcentral.com/google-nexus-one-roms-hacks/7366-how-install-custom-roms-your-nexus-one.html"
im sure the same topic is on XDA somewhere, this was just the first website i got directed to by google
1.) With your device powered off hold down on the volume down rocker while pressing the power button. From there select "recovery".
2.) Once in recovery select backup/restore and choose Nand backup.
When that is completed you now have a backup image saved on your SD card in case you ever need to go back to the normal ROM.
3.) Now from the recovery menu select Wipe and then Wipe data/factory reset.
4.) Once the wipe is completed select Flash zip from sdcard to select the ROM you wish to install.
5.) Once the flashing process is completed simply reboot and enjoy your freshly flashed Nexus One!
i installed the rom: Cyanogenmod For Nexus One V5.0.6
"forum.cyanogenmod.com/index.php?/topic/150-cyanogenmod-for-nexus-one-v506-04152010/?"
sorry that you arent able to click the links im providing, im new to the forum and im not allowed to make direct links yet.
so thanks again FloOGB.
//Duvel
you're welcom, no problem
even if i didn't say anything that useful i think i would have never thought about drivers since i'm using only linux and it's sort of plug and flash here.
Hi
I have been using Clockwork recovery for months and tonight was flashing ROM/zips as usual, and all of a sudden when I try to get into recovery my Nexus just sits on the colored X. When I pull the battery it reboots fine with the ROM I currently have installed. Then I go back into ROM manager, re-flash clockwork recovery: it says flash was successful, so then I choose to boot into recovery, and again it just sits at the blue, red, green and yellow X.
So then I tried a round-about way by going into ROM manager and choosing to restore a backup. Again, when I choose to restore backup it just boots to the colored X again and freezes there.
I've also tried the regular method of holding power button and trackball and get the same results.
Does anyone know why this might be happening? Right now I'm stuck with a ROM I was just playing with and didn't necessarily want to use permanently....I'm afraid I might be stuck with it forever now
Thanks for any help!!!
I've been searching and I should add that my bootloader is not unlocked
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Jack_R1 said:
Try to flash your recovery manually, using the guide from my signature. Try Amon_RA's.
Click to expand...
Click to collapse
Well I ended up wiping all user data in fastboot and now I get nothing but an X nomatter what I do, won't boot at all.
All I can do is hold down the power button and trackball and get the page that says
bootloader
reboot
reboot bootloader
power down
the only way I'm going to get this fixed is to use my computer and I've never done it that way...I've always used ROM manager
I'll read the links but I think I'm screwed because a lot of this is over my head
Thanks for the links !
1) Try to follow "Unroot/restore" guide first, see if you can restore functionality using PASSIMG method. Once you have functional FRG33 with recovery, you can root it, replace the recovery and install custom ROM of your choice / update to FRG83G.
2) If nothing helps - consider a) replacing your phone, b) unlocking the bootloader and flashing recovery through fastboot.
Getting in over your head is sometimes a good way to expand your horizons
Hi Jack
Thanks for the help
I'll do some reading and see what I can do....got two feet of snow here so I guess I have the time
worst comes to worst I'm still under warranty.
Well I tried the instructions but nothing happens..it just sits on the screen with the androids skateboarding. I renamed the zip and moved it to my SD card but it doesn't seem to even search for it, let alone find it. Really wish I had not deleted storage. At least I had a working ROM at that point.
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Jack_R1 said:
Which instructions did you try? Did you download FRG33, rename it to PASSIMG.ZIP (and not PASSIMG.ZIP.ZIP !), put it on the root of SD card and reboot to bootloader?
Click to expand...
Click to collapse
Hey Jack...
Sorry for taking so long to respond...I finally had to crash for awhile, my brain was frying.
Yes I did what you describe: downloaded FRG33, renamed it PASSIMG.ZIP(not ZIP.ZIP) moved it to SD card just like any ROM and held down volume and power button and came to the screen with the three androids. Then it just stayed there, nothing happened.
The only thing is I had to use my backup Nexus One(EDGE only on ATT model) to move it to the SD card as I don't know how to access the SD card with the device acting like this. If I connect the device to my computer while the three androids are on the screen, I hear it connect to the computer, but nothing pops up allowing me to access the SD card....
Like I said I'm a noob at this I appreciate you trying to help me here
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Rusty! said:
About 3 seconds after the 3 androids skating appears, you should see some text flash up?
It does say you're in HBOOT and not FASTBOOT right? If in fastboot, pick the bootloader option and then it should find the file.
Click to expand...
Click to collapse
Hi Rusty
Sorry I somehow missed your post here. Yes I see some text flash up...takes a little longer than 3 seconds...maybe 8 seconds...
At first it says I'm in Fastboot, but then I press the power button and then it says HBOOT at the top.....that's when the text flashes on the screen. It flashes too fast for me to read it though....but nothing happens after the text flashes on the screen.
I'll be damned guys....I got it working! After responding to Rusty's post above, I decided to give the whole thing another try. Well I went thru the whole process of putting the file on the SD card and realized I had in fact renamed it zip.zip....it LOOKED like it was only ZIP, but when I clicked on the file while it was still on my PC, it said it was zip.zip...that's when I knew what the problem was.
My problem now is getting it re-rooted. Originally I used the Universal Androot application..the true one-click method...I just tried it again and it didn't work.
Is there a way to downgrade to a version where this app will work again?
Thanks guys you really helped me out here!!
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Jack_R1 said:
Please read the guide in Wiki, and follow one of the zillion SuperOneClick threads that are around. It's really as simple as it gets - and if you happen to have Windows 7, it's even more simple - you won't need to install the drivers.
Click to expand...
Click to collapse
Yup I'm already rooted!!! Thanks man!!!! Took 12 minutes!!
Okay I'm having another issue: SuperOneClick said I was rooted,I have the superuser icon in my app drawer, but ROM manager will not flash Clockwork mod recovery and Titanium Backup says I do not have root rights??
well I rebooted and now have root rights but am still getting an error when I try and flash clockwork mod: it says: "an error occurred while flashing your recovery"
Do you have Busybox installed?
Jack_R1 said:
Do you have Busybox installed?
Click to expand...
Click to collapse
You're going to think I'm a dip**** but I don't even know what busybox is?
Let's just say it's an app that the system needs Go to Market, download and install it, try again. If it doesn't work - you can try to install custom recovery manually, using another guide from Wiki. Look in "Installing Recovery" for "For locked bootloader - flash_image using Terminal" guide. If you don't know what Terminal is - download "Android Terminal" by Jack Palevich from the Market.
Use the fix problems button in Titanium Backup to install it, long story short is it lets you use a bunch of native Linux commands that as missing from Android.