Before someone flames me for being a n00b and not being able to use the search function in the forum, this is not a thread where I ask about *how* to unroot my phone; that information is here, and I have been using that to attempt to unroot.
The problem is as follows:
The 'Home' button on my G1 has broken in such a way that it 'turbo-presses' home continuously. I cannot open any applications, use the phone function, text, or anything. When I reboot my phone, or it runs our of battery, I am greeted with the recovery screen. On the off-chance that it lets up long enough to let me turn my phone on, (as I already explained) all I can do is receive calls.
I plan to take the phone back to T-Mobile to get a replacement, but need to unroot it so my warranty is not void.
1. Get the original SPL for your phone, get it here
2. Rename it to update.zip and copy it to your sd card. /sdcard
3. Download the DREAIMG.nbh from here.
4. Place DREAIMG.nbh on the root of your SD card. /sdcard
5. Go into your phones recovery. [Hold the home & power button]
6. Push Alt+S on your G1 to flash it with update.zip
7. After it does its thing, gettig back to your home screen.
4. Start phone in bootloader. [Hold camera+power button]
5. Hit power to start the update DO NOT INTERRUPT!! i can not stress this enough.
6. Click on the action button(track ball) and your phone will reboot.
7. YOU NOW HAVE STOCK FIRMWARE, it will update on it's own in a little bit, or *Settings>About phone>System Updates*
The steps in italics are as far as I can get!
(I also have the cupcake update on my sdcard ready for when it works)
Please help - I do not have a usable phone currently, and it's really bugging me. I know it's a mechanical fault. Phone details are in my sig.
This is not my first port of call - I *have* tried other methods. For instance:
1. Recovery
2. Apply SPL
3. adb shell reboot bootloader
whereupon I get either a 'Serial0' message, or no message whatsoever (when plugged into PC)
It would also seem that rebooting after the SPL update and pulling out the battery at the G1 screen, as some guides suggest, doesn't work either, since when I boot (and attempt to boot into bootloader) I instead end up in recovery.
For your information, entering 'adb shell reboot' doesn't override the pressing down on the home button, as I'm sure you're aware, and I can't find an adb command that forces a normal reboot.
I can provide more information if needed, and sorry for the wall of text - I needed to explain thoroughly!
hendos43 said:
Before someone flames me for being a n00b and not being able to use the search function in the forum, this is not a thread where I ask about *how* to unroot my phone; that information is here, and I have been using that to attempt to unroot.
The problem is as follows:
The 'Home' button on my G1 has broken in such a way that it 'turbo-presses' home continuously. I cannot open any applications, use the phone function, text, or anything. When I reboot my phone, or it runs our of battery, I am greeted with the recovery screen. On the off-chance that it lets up long enough to let me turn my phone on, (as I already explained) all I can do is receive calls.
I plan to take the phone back to T-Mobile to get a replacement, but need to unroot it so my warranty is not void.
1. Get the original SPL for your phone, get it here
2. Rename it to update.zip and copy it to your sd card. /sdcard
3. Download the DREAIMG.nbh from here.
4. Place DREAIMG.nbh on the root of your SD card. /sdcard
5. Go into your phones recovery. [Hold the home & power button]
6. Push Alt+S on your G1 to flash it with update.zip
7. After it does its thing, gettig back to your home screen.
4. Start phone in bootloader. [Hold camera+power button]
5. Hit power to start the update DO NOT INTERRUPT!! i can not stress this enough.
6. Click on the action button(track ball) and your phone will reboot.
7. YOU NOW HAVE STOCK FIRMWARE, it will update on it's own in a little bit, or *Settings>About phone>System Updates*
The steps in italics are as far as I can get!
(I also have the cupcake update on my sdcard ready for when it works)
Please help - I do not have a usable phone currently, and it's really bugging me. I know it's a mechanical fault. Phone details are in my sig.
This is not my first port of call - I *have* tried other methods. For instance:
1. Recovery
2. Apply SPL
3. adb shell reboot bootloader
whereupon I get either a 'Serial0' message, or no message whatsoever (when plugged into PC)
It would also seem that rebooting after the SPL update and pulling out the battery at the G1 screen, as some guides suggest, doesn't work either, since when I boot (and attempt to boot into bootloader) I instead end up in recovery.
For your information, entering 'adb shell reboot' doesn't override the pressing down on the home button, as I'm sure you're aware, and I can't find an adb command that forces a normal reboot.
I can provide more information if needed, and sorry for the wall of text - I needed to explain thoroughly!
Click to expand...
Click to collapse
The SPL is included in the RC29 DREAING.nbh, so there's no need to worry about flashing it seperately. Just put DREAIMG.nbh on the root of your sdcard and use the adb command to get into the bootloader (adb shell reboot bootloader, as you said). [home] isnt a valid shortcut in the bootloader, so as long as your file is named correctly and on the root of the card, you should be able to hit [power] and flash.
goldenarmZ said:
The SPL is included in the RC29 DREAING.nbh, so there's no need to worry about flashing it seperately. Just put DREAIMG.nbh on the root of your sdcard and use the adb command to get into the bootloader (adb shell reboot bootloader, as you said). [home] isnt a valid shortcut in the bootloader, so as long as your file is named correctly and on the root of the card, you should be able to hit [power] and flash.
Click to expand...
Click to collapse
This is all well and good, but since I'm in the UK, do I not have to use the RC7 DREAIMG.nbh?
Does that include the related SPL?
Thank you for your prompt reply.
EDIT: I am using the .nbh file found here.
Also, after rebooting numerous times to no avail, I have just booted into the OS. Is there anything I should do whilst I have this available?
Ah, I you didn't have a flag by your name so I assumed yank.. sorry about that.
Yes, RC7 also includes the SPL. Flashing that should be the only thing you need to do before you send it back.
I get 'Serial0' error still?
hendos43 said:
I get 'Serial0' error still?
Click to expand...
Click to collapse
Serial0 isn't an error, it's the mode the bootloader is in.
When you first boot into that mode it should search for update files on the card.. it should run through a list of filenames before displaying Serial0.. is that happening?
Edit: make sure your battery is well charged or it might not attempt the update.
I don't believe so, but then there is only one file on the card, so it may be happening very quickly. Why is it that I can skip the SPL update, but some (most) guides say to flash it first if you've ever done it in the past?
EDIT: No, it's not showing anything. It pauses before showing 'Serial0', but doesn't show any files. Is the .nbh corrupt?
Also, if this is of use, this is the exact information my bootloader shows:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
(Rainbow background)
hendos43 said:
I don't believe so, but then there is only one file on the card, so it may be happening very quickly. Why is it that I can skip the SPL update, but some (most) guides say to flash it first if you've ever done it in the past?
Also, if this is of use, this is the exact information my bootloader shows:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
(Rainbow background)
Click to expand...
Click to collapse
I'm a bit hazy here cos I've not used stock in AGES and I've never tried to revert, but maybe the SPL you've flashed will only accept US signed files.. Try flashing HardSPL from recovery, then using the RC7 DREAIMG.nbh again.
goldenarmZ said:
I'm a bit hazy here cos I've not used stock in AGES and I've never tried to revert, but maybe the SPL you've flashed will only accept US signed files.. Try flashing HardSPL from recovery, then using the RC7 DREAIMG.nbh again.
Click to expand...
Click to collapse
No, I've never tried to revert either . I will try this. Will flashing the Hard SPL require me to reboot to OS?
EDIT: I used DangerSPL which allowed me to flash the DREAIMG. Rebooted, and obviously now have stock Recovery mode. Installing the update.zip I had on the sdcard (cupcake)
EDIT 2: Now in full stock, with my fault! Time to make a claim!
Thank you xda, and especially you, goldenarmZ =)
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
How do I un-root my G1 if I have Haykuro's spl?
The first thing you must to do is downgrade the SPL . (This is very important you must to do this step first, DOWNGRADE THE SPL)
download the original stock SPL - http://www.megaupload.com/?d=6JMCDJJH
Rename the Original SPL to Update.zip and place it (now named update.zip) on the SD card (not in any folder)
Turn off the phone
Turn on the phone holding Home and End key till the recovery screen pops up.
Hit Alt W to wipe the phone, then hit Alt S to load the update.zip
After the update is complete, press Home and Back to reboot.
next
you must to load the factory DREAMIMG.nbh
1. Download the Original DreaIMG.nbh file: http://www.megaupload.com/?d=XXSQ0T7W
2. If the file downloaded above downloads as a .Zip file, please unzip it first then put the DreamIMG.nbh file that is inside on the SD card (root SD card not in any folder)
3. 3. Turn the phone off if it is on.
4. Turn on the phone by holding the Camera button and the End key until the bootloader screen turns on.
5. Hit the End key to start the update. DO NOT INTERUPT THIS PROCESS.
6. Once it is done, hit the trackball to restart the phone. You now are on the stock firmware RC29. You must do the next section to get back to cupcake.
Back to cupcake
Download the cupcake update from here - http://code.google.com/p/android-ro...=signed-kila-ota-148830.de6a94ca.zip&can=2&q= , then put it on your SD card, rename it to update.zip Turn off your phone and turn it back on by holding down Home and Power to get to recovery mode. In recovery mode (the ! screen) hit Alt L to see text, then hit Alt S to Apply the update.
Or just flash the RC29 image cause it has the stock spl with it. It will downgrade everything at once.
^^^^ G1gurl have a Haykuro SPL he must to downgrade the SPL before downgrade to RC29. G1gurl if you downgrade to RC29 without downgrade the SPL you go to have a BRICK. downgrade the SPL first and the next step is downgrade to RC29
But why lose such acess? Are you returning it?
Ace42 said:
But why lose such acess? Are you returning it?
Click to expand...
Click to collapse
Yes I'm having problems with it, I hate having to do everything all over again but when I touch it touches something else. Is there a way I can fix that or try to repair it?
G1gurl said:
Yes I'm having problems with it, I hate having to do everything all over again but when I touch it touches something else. Is there a way I can fix that or try to repair it?
Click to expand...
Click to collapse
Being able to calibrate the screen is one of the thing's I've always thought the G1 lacked, especially because I got fat fingers.
Have you tried wiping your data and reflashing your rom yet, to see if it's a software bug?
jackslim said:
Being able to calibrate the screen is one of the thing's I've always thought the G1 lacked, especially because I got fat fingers.
Have you tried wiping your data and reflashing your rom yet, to see if it's a software bug?
Click to expand...
Click to collapse
Yes I've tried that too, but it goes away and then it starts again, but I''m trying out mlign hero rom and it's seems to be ok now.
hey guys, i tryed the one clik meth od here:
http://theunlockr.com/2009/08/22/how...-in-one-click/
after everything, when i get to step 12 and reboot my phone (holding home and power) my phone just freezes with the rogers logo up (i need to remove battery to get back).
What can I try next to root my phone? should i first restore my back up image that i made with the program before I do anything else?
I need some help as i really need to root this phone for 2 reasons
1)apps on sd
2)Rogers locked out the touchscreen keyboard
http://forum.xda-developers.com/showthread.php?t=563679
Follow this, if you want CM keep going all the way through, if you want someone else's ROM then flash that instead of CM's.
hey, ok so my latest update is that i got myself to SPL 1.33.2005
i was able to boot into everything that was needed (power + camera) (power + home)
I am now at this step:
http://forum.xda-developers.com/showpost.php?p=4848777&postcount=506
Look at where he posts his info he has:
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.20.17
I have:
DREAM PVT 32B SHIP S-OFF
does it matter that mine says S-OFF
Hold your horses! That isn't the link I gave you to follow... You are in dangerous territory right now... what all have you done, exactly? Flashing that SPL can and will brick your phone if not done right.
I was using the link you gave me, close to the top it says to follow the linked guide for rogers phones as they are done differently(my phone is rogers)
that link leads you to:
http://forum.xda-developers.com/showthread.php?t=558301
once done that it says to go to:
http://forum.xda-developers.com/showpost.php?p=4848777&postcount=506 (never mind i should not use this as his spl is different as well, not the spl gotten from the previous link)
OR
http://forum.xda-developers.com/showthread.php?t=544654
this first one is a relply of the second link (supposedly easyer)
LAST EDIT:
So, should i continue following
http://forum.xda-developers.com/showthread.php?t=544654
Ok, carry on! As long as your reasd twice and do once you should be ok. And don't worry about the 'on' vs 'off', the big concern is what board do you have, and you have the 32b PVT, which is the one you need. I believe that 'on' 'off' is in regards to carrier lock.
like i edited, the first link guy does not have the SPL that I now have, i will be following the final link
http://forum.xda-developers.com/showthread.php?t=544654
When it says:
"once you are at SPL 1.33.2005 (AND ONLY THEN)
download this (it is hyperlinked)
(md5: 4a58a5702fdf899547011888d9cc066f .. sha1: 99e38e4f8798e952e67421a42e7b053ea70957b7)
extract both images wherever you'd like."
does it mean extract whereever on the sd?
I would assume extract and place on the root of the SD card based off the fact you will be doing all this from fastboot, aka the phone itself.
alright so i did that stuff, now when i boot the phone hangs at the rogers logo, what should i try.
did make a nandorid back up in the recovery menu a little while ago, how an i use it to go back? or is there another option to do something?
I can still boot into the recovery menu and camera+ power menu
Can you get into recovery? First boots take a long time as well, how long has it been hung up? But it sounds like you don't have a ROM on the device currently.
I can get into recovery, It was hung for like 4-5 minutes before i reset it. I dont think i did the fastboot stuf right, I pressed send inorder to fastboot, it said fastboot and i started typing the stuff on the link (you cannot see anything i was just typing) i then rebooted to recovery and Alt+s applyed the update (cynogen).
it is hung at the rogers screen. Can you try and translate the link
http://forum.xda-developers.com/showthread.php?t=544654
a bit better and i can try the fast boot part again?
In the guide it says press back arrow to get inot fast boot but on my screen there is only one option for fastboot and it is the send button.
I tryed to use the update.zip file again but this time it said that it could not mount and that the directory does not exist.
It sounds like you did do the fastboot right, actually, since if you didn't it would boot up fully...
I would try this, dl this rom and put it on the root of your sd card, then boot into recovery mode and select "flash any .zip update" or whatever the exact wording is, then select the file named "dwang-v1.15" and follow the onscreen prompts. It is also probably a good idea to get your phone on a charger sometime soon, wouldn't be surprised if the battery is getting close to dead since when in fast boot and recovery and during boot up itself battery drain is pretty quick.
I truly think you did the fastboot stuff right, since when done you should have the SPL and radio, recovery, but no ROM and need to boot into recovery and flash the new ROM.
Forgot to give the link to the ROM, it is dwang's, my personal favorite and a good starting point to work from:
http://forum.xda-developers.com/showthread.php?t=567023
the option is apply update.zip so i should probably change the file name to that. Ill give it a go.
its still hanging on the rogers icon, weird. Perhaps i should use the nandoid backup? if you agree that that is the best option how would i do that?
another note, when i tryed to flash the rom you gave me it did not let me, game a an error about mounting and cannot find a file, I then put the recovery images back onto the sd card and the operation worked this time, it was unpackin na extracting and everything. Now it is still hung.
I would probably just nandroid at this point, yes
can ou guide me on how to do that?
Hmmmmmmm, do this for me as well, boot into boot loader (camera+power) and tell me what it says on the screen.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA21000)
CPLD-4
RADIO-3.22.20.17
Apr 20 2009, 15:30:43
HBOOT
<SEND> Fastboot Mode
Okay, so I know what everyone says, "make sure you know what you're doing before you update to Danger SPL." So I read and re-read all the forums and guides about various problems and how to avoid them and how to flash the radio and SPL, THEN after I was comfortable I decided to go for it.
So here is my issue:
I used the two sd card method. After wiping, I flashed the radio to 2.22.19.26I, then rebooted. I wiped again and flashed the SPL to 1.33.2005, took out the SD card and put the other one in. I rebooted from console (using command "reboot recovery"), wiped again, and flashed CM 4.2.10.1 and rebooted. After this final reboot it sticks at the G1 screen and doesn't do anything beyond here. I also tried reflashing everything and formatting the new SD card, then loaded the CM version with RA's USB-MS mode and flashed it. Same effect, stuck on G1 screen.
I still have access to the recovery image as well as fastboot and the screen with the androids on the scateboards (bootloader? I'm niot sure). WIth those things in mind, I don't think I have bricked anything, but of course that doesn't help the fact that I can't use the phone. Any help here would be AWESOME.
ROM: CM-4.2.10.1
recovery image: RA-dream-v1.5.0
Android screen reads:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
ALSO I hope a thread with an answer doesnt already exist, I did search for quite a while for a solution but couldn't find one. Thanks again to anyone who can help me out.
Just checking cause you didn't mention this step but before flashing Cyanogen 4.2.10.1 did you flash the HTC ADP image??
Have you tried flashing any other ROM's??
Since you still have recovery && bootloader you're not in a terrible position, you're not bricked, just gotta find out where you're going wrong
HamToast said:
Okay, so I know what everyone says, "make sure you know what you're doing before you update to Danger SPL." So I read and re-read all the forums and guides about various problems and how to avoid them and how to flash the radio and SPL, THEN after I was comfortable I decided to go for it.
So here is my issue:
I used the two sd card method. After wiping, I flashed the radio to 2.22.19.26I, then rebooted. I wiped again and flashed the SPL to 1.33.2005, took out the SD card and put the other one in. I rebooted from console (using command "reboot recovery"), wiped again, and flashed CM 4.2.10.1 and rebooted. After this final reboot it sticks at the G1 screen and doesn't do anything beyond here. I also tried reflashing everything and formatting the new SD card, then loaded the CM version with RA's USB-MS mode and flashed it. Same effect, stuck on G1 screen.
I still have access to the recovery image as well as fastboot and the screen with the androids on the scateboards (bootloader? I'm niot sure). WIth those things in mind, I don't think I have bricked anything, but of course that doesn't help the fact that I can't use the phone. Any help here would be AWESOME.
ROM: CM-4.2.10.1
recovery image: RA-dream-v1.5.0
Android screen reads:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
ALSO I hope a thread with an answer doesnt already exist, I did search for quite a while for a solution but couldn't find one. Thanks again to anyone who can help me out.
Click to expand...
Click to collapse
Snab a copy of cyanogen's rom (update.zip) and recovery image (on the forums)
Boot the phone into fastboot (power off, hold camera button and power on)
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
this should insure that you have a proper recovery image.
boot into recovery mode now (you can press the menu button to power off the device from the SPL menu, then hold the HOME button and power on the device)
Code:
adb devices
you may need to do this a couple times until it shows up, once adb reports your device is available
Code:
adb shell mount /sdcard
adb push update.zip /sdcard
then press ALT+S (or select the option from the menu using your wheel)
let the rom flash.
when it's complete, reboot your device (HOME+BACK) or just use the menu again.
it should now boot.. if it takes a bit longer than usual, check if the device is active using:
Code:
adb devices
if your device is listed, see if it's actually doing something using
Code:
adb logcat
if you see a bunch of "E/" followed by text, your phone is erroring out and you may have to report back here for further assistance, if you see a bunch of "apks" and "jars" flying by, your phone is booting it's just checking signatures most likely.
jackslim said:
Just checking cause you didn't mention this step but before flashing Cyanogen 4.2.10.1 did you flash the HTC ADP image??
Have you tried flashing any other ROM's??
Since you still have recovery && bootloader you're not in a terrible position, you're not bricked, just gotta find out where you're going wrong
Click to expand...
Click to collapse
ADP image? I did the steps exactly as I described them. Should I have flashed HTCs ADP image? I guess so, if thats what I did to get CM in the first place. Is that the image that puts all the Google Apps on the phone? Also, if I'm getting CM v4.2.10.1 from the website, and I'm coming from a new radio and SPL, should I have to treat it as though I'm not updating and am coming from a freshly rooted phone?
and @haykuro, I'll try that as soon as I get the time.
Before you flash Cyanogen for the first time you need to flash HTC's ADP image
Check out the Cyanogen's Wiki for a full guide on installing his rom
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Since you've already gotten as far as getting a custom recovery skip down to the section called "File Download" and continue on, that should get you on the right track
Yes that is the image that get's you all the Google Apps
Yes after installing the 1.33.2005 SPL you have to reinstall a fresh ROM
jackslim said:
Before you flash Cyanogen for the first time you need to flash HTC's ADP image
Check out the Cyanogen's Wiki for a full guide on installing his rom
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Since you've already gotten as far as getting a custom recovery skip down to the section called "File Download" and continue on, that should get you on the right track
Yes that is the image that get's you all the Google Apps
Yes after installing the 1.33.2005 SPL you have to reinstall a fresh ROM
Click to expand...
Click to collapse
Worked like a charm! Kinda makes me feel like an idiot though for not thinking about needing to treat it like a fresh install instead of an update, but I'm glad it worked!
Also, thanks for how quick you helped me out! I was only without my G1 for maybe 5 hours!
I LOVE THIS COMMUNITY!!!!
HamToast said:
Worked like a charm! Kinda makes me feel like an idiot though for not thinking about needing to treat it like a fresh install instead of an update, but I'm glad it worked!
Also, thanks for how quick you helped me out! I was only without my G1 for maybe 5 hours!
I LOVE THIS COMMUNITY!!!!
Click to expand...
Click to collapse
Man! 5 hours is 5 hours too long!
So usually I've read this is a matter of the wrong spl, or unsigned files, or other things that don't seem to be my problem. I've searched for days now and would LOVE some help.
I'm downgrading for a warranty return because my touchscreen doesn't work. I try to follow the directions found in several threads but I get hung up at the same spot.
When flashing the dreaimg.nbh file in the stock bootloader, bootloader starts, checks, then I get to the screen that asks you to press power to flash, or action to cancel. No buttons on this screen do anything. Not the "3 finger solute" to reboot, not power, not action, nothing. Just no response. And yes, I waited, and waited.
I think I've tried about every combination of everything I can think of, but please, your suggestions mean a lot to me.
The only thing I can think of, is that maybe the updated radio isn't compatible with RC29, and the phone knows this somehow and won't let me flash RC29 with my current radio? Does that make any sense? Do I need to flash an old radio, then the dreaimg.nbh?
Thanks!
(anybody wanna tell me how to get a screenshot from the bootloader and I'd be glad to show it, but it's just the standard screen)
I say try! ahaha
Same thing happened to me with the touchscreen lol.
I just flashed the old image didn't even bother to update or anything and just sent it in.
And I didn't get charged for voiding the warranty.
And no the new radio is compatible with RC29 I've used my friends phone when we were rooting it and he had the new radio.
Thanks for that, if I can't figure it out, I guess I'll try the warranty. I'm still going to work on it though, I can't imagine that someone hasn't had an unresponsive bootloader before though, and know how to fix it.
I've always done things the retard way, but I've spent the last week learning ALOT. I've got adb and fastboot setup, is there a way to flash the nbh file via fastboot or adb, bypassing the bootloader?
And FYI for others, with the nonworking touchscreen you can't "press the droid" after a factory reset. SDK, and androidscreencast fixed that, you can see your screen on your computer and use your mouse to click!
http://code.google.com/p/androidscreencast/
I also just got droid explorer, which lets you do lots of things with a GUI, including invoke androidscreencast, man that would've been easier a week ago! At least now I am able to use the phone as I had to disable the wipe unlock, and touch the droid to recover from a wipe!
I imagine this would be perfect for people with broken screens as well!
the .NBH includes EVERYTHING but an SPL... it rewrites Radio, splash1 system and usrdata...... if you cant press the action button, first try re-flashing the SPL, then try cleaning out your trackball
the action button is the trackball BTW...
Thanks for those tips. But I've done that and it still doesn't work. Even tried downloading the spl from a variety of sources, and doing a checksum to make sure it's not corrupted. And the trackball works in every other application. Basically, the stock bootloader just won't respond to any command (action to cancel, power to update, 3 buttons to reboot, nothing). It DOES recognize the .nbh, which is a step further than most bootloader fail threads I see.
Is it possible to flash an nbh file using fastboot or adb? I've figured out how to do update.zips this way, but not .nbh. I'd still have a custom bootloader, but everything else would be stock.
Thanks again everyone!
So if anybody can help, maybe this bit is useful too, I get no response from the hard spl either. Example, it is my understanding that the standard hard spl screen (with no .nbh file on card it dislplays phone radio info at top, serial0/10, 3 android skaters at bottom) that screen I should be able to press call+power+menu to reboot, right? I get nothing, and thought I should. This spl won't flash the nbh either, I guess because it won't register the "press power to contine".
1. Any ideas? My keys work when in standard usage and in recovery, why won't they work in any of the spls?
2. still wondering if/how I can fastboot the dreaimg.nbh file?
Make it unbootable (don't brick it - just wipe your current ROM and recovery partition) and restore to stock G1 SPL and if they say anything about "It won't boot" blame it on shipping.
Have you tried updating with a engineering SPL? I don't know if that would have any difference. Also, is your sdcard still partitioned? I think it has to be all fat32 or a goldcard (no idea where a goldcard actually come in on G1).
Brilliant! I bet it is the partitioning! I now remember that I thought about that for a minute, but tried other things. I'll try a fresh, all fat32 partitioning and give that a shot. Otherwise, good call on just deleting the partitions.
(actually excited to have something hopeful to try for a change!)
Solved!
Cheers to you R3s!
If anybody else finds themselves with an unresponsive bootloader, make sure your sdcard is not partitioned.
For the step by step folks who may be wanted to return a G1 to stock, in my case for a warranty return because the touchscreen doesn't work:
put the stock 1 G card in a card reader, popped it in the usb drive of a winxp system, my computer, right click on drive, format (not quick) fat32.
copied over stock spl renamed as update.zip
copied over DREAIMG.nbh
unmount sd card
pop into g1
home+power to get into recovery
apply update.zip
reboot
wipe
reboot + hold camera button
power button to apply
wait, this time I got the status bar immediately
action button to restart when prompted
reboots to spl
3 finger salute to reboot (call+end+menu)
BAM, back to the android to press the button to start
(and fully stuck there now since I don't have a touchscreen, my daughter called me crazy for being so happy, she asked if I fixed it and I said no I broke it!)
So there ya go, anybody else has this problem, reformatting the sdcard isn't enough, you have to remove the partitions.