G1 in weird limbo state - G1 General

Hi all,
I've been trying to install an OS on a G1 for about 2 hours now. I have gone through about 20 posts and followed instructions to the T. I own a pc repair company and I post regularly to some windows and general computer repair forums, so I'm pretty technical. Since I'm 100% stuck, I'm hoping one of you can help.
I don't know anything about the history of the phone, but it currently boots to the rainbow bootloader screen:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Serial0
I can drop the NBH file from DREAIMG-RC29.zip off of google's android file list into the root of the SD card and get the radio back to 1.22 no problem. I have actually tried 4 different versions of RC29 and all seem to work the same.
I have downloaded about 5 different versions of Android 1.5 (as well as 2 versions of 1.1, and a few of 1.6), changed them to update.zip, and attempted to load the OS and every single one of them fails*(see below for error) in the step "Verifying update package..." EXCEPT signed-kila-ota-148830.de6a94ca.zip. This one actually goes through all of the installation steps without erroring, tells me to hit home+back to reboot, says its updating the radio, goes to a screen with an image of a box pushing an arrow into a phone.... but then it reboots to the rainbow bootloader screen again!
*Error from above: E:Failure at line2: assert file_contains("SYSTEM:build.prop".... MORE ... Installation aborted.
When I reboot the phone now, it immediately tries to reload dreaimg.nbh. If I delete dreaimg.nbh off the SD card, the rainbow screen flashes (very quickly) to a gray screen that says "Loading.... No Image File!"
I know the phone isn't technically "bricked" because I'm able to interact with it, it reboots when I hold green+red+menu, but it sure seems like I'm in an infinite loop at this point.
My only goal is to get an OS loaded on this phone. ANY OS at this point.
Any suggestions on steps I can take? Need any other information?
Thanks alot for taking the time to read my post. I appreciate your time.

Thread moved inside G1 General.

sffan15 said:
Hi all,
I've been trying to install an OS on a G1 for about 2 hours now. I have gone through about 20 posts and followed instructions to the T. I own a pc repair company and I post regularly to some windows and general computer repair forums, so I'm pretty technical. Since I'm 100% stuck, I'm hoping one of you can help.
I don't know anything about the history of the phone, but it currently boots to the rainbow bootloader screen:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Serial0
I can drop the NBH file from DREAIMG-RC29.zip off of google's android file list into the root of the SD card and get the radio back to 1.22 no problem. I have actually tried 4 different versions of RC29 and all seem to work the same.
I have downloaded about 5 different versions of Android 1.5 (as well as 2 versions of 1.1, and a few of 1.6), changed them to update.zip, and attempted to load the OS and every single one of them fails*(see below for error) in the step "Verifying update package..." EXCEPT signed-kila-ota-148830.de6a94ca.zip. This one actually goes through all of the installation steps without erroring, tells me to hit home+back to reboot, says its updating the radio, goes to a screen with an image of a box pushing an arrow into a phone.... but then it reboots to the rainbow bootloader screen again!
*Error from above: E:Failure at line2: assert file_contains("SYSTEM:build.prop".... MORE ... Installation aborted.
When I reboot the phone now, it immediately tries to reload dreaimg.nbh. If I delete dreaimg.nbh off the SD card, the rainbow screen flashes (very quickly) to a gray screen that says "Loading.... No Image File!"
I know the phone isn't technically "bricked" because I'm able to interact with it, it reboots when I hold green+red+menu, but it sure seems like I'm in an infinite loop at this point.
My only goal is to get an OS loaded on this phone. ANY OS at this point.
Any suggestions on steps I can take? Need any other information?
Thanks alot for taking the time to read my post. I appreciate your time.
Click to expand...
Click to collapse
I don't fully understand the issue.. You can get to the stock SPL, you can get to recovery to flash an update.zip, but you can't get it to boot the main system?

Yes, I guess that is the issue.
It seems to load the 1.5 OS I mentioned in my original post just fine, but the phone wont boot into anything but the SPL.
It acts as if there isn't a main system to boot to.
I'm also wondering if there is anything else that should be on the SD card other than update.zip and DREAIMG.spl?
Thanks for your help golden

thats weird, fist time ive seen a problem like this...

I've never seen this either.. usually when dreams get stuck in an spl loop a broken button is the culprit, but since you can get into recovery normally that seems unlikely. This is going to be really hard to diagnose and fix from a stock spl and recovery as well..
Did this phone ever work or did it come to you in this state?

Right? I have really done alot of work previous to posting here, and I only found one other person with the exact same issue. Unfortunately no one had an answer for him either. I never like to bug forums if I don't absolutly have to :/
According to the eBay post, the phone worked fine but broke when the previous owner tried to root it himself.
My dad purchased the phone assuming I would be able to fix it (laughs).

I would be willing to try just about anything at this point, if anyone has any crazy suggestions on how to get the phone to boot to an OS.
Is there any way to 100% wipe everything on the phone, like EVERYTHING, and start fresh? Or is that essentially what you're doing when you boot to recovery mode, tell it to reset to factory, and then reinstall the DREAIMG file?

Related

[FIXED] HTC Magic partially bricked

Hi everyone,
Yesterday i tried to root my HTC Magic, but it kinda failed.
Now, it gets stuck at the Rogers screen (Rogers is the carrier, its the first screen you see when you boot). I can get in Fastboot mode but i have absolutely no clue what to do in order to unbrick the phone.
I don't care if i have to put a custom ROM or the original one, i just want to have a useable phone.
I'd like to have detailed instructions on how to proceed and where to download the stuff i need.
Thank you very much for your time !!!
EDIT: Problem fixed
Explain exactly what you were doing. It can be undone if you can get into fastboot. You might have to flash a different ROM or SPL (if you flashed the wrong SPL)
I tried this: http://android-dls.com/wiki/index.php?title=Magic_Rooting but the thing is, Method 1 didnt work for me, the line :fastboot boot recovery-new.img didnt work, it did what its doing now (ie booting but freezing at first screen) but by removing the battery and putting back in, it booted normally.
Then i tried method 2, but with the update.zip from method 1, this time it worked, i was able to apply the update, but when it rebooted, it froze, and now it freezes every time i boot, but i can still get in fastboot
i didnt touched the SPL.
the easiest was to fix it is to locate the file on the net called:
SAPPIMG_Sapphire_TMUS_1.88.531.1_COC10_release_signed.nbh
download it to your pc
format your sd to card to fat32
copy and paste the NBH file to memory card
put card in phone and power on while holding down the vol. button and it should automatically pick up the NBH file and just follow the steps
so i format the card, put the NBH file in, boot to fastboot, follow the instructions and thats it ?
that will put my phone back in its origial state ?
since i format the sd card, i loose everything, but i can backup without problems ?
EDIT: No, it did not work. I formated my sd card, put the NBH on the card, boot the phone in HBOOT and it didnt do anything.
Sounds like you got the wrong recovery image. Did you download h or g?
I'm pretty sure it was H
EDIT: Well first of all i tried this one: http://www.droiddeveloper.com/hrbuilds/recovery-new.img.zip
but it did no work properly: when i tried to do: fastboot boot recovery-new.img it booted to the rogers screen and froze instead of booting to the green screen
Then i tried this one: http://rapidshare.com/files/248983573/recovery-RAv1.0H.img
This time i managed to get to the green screen and apply the update.zip, but when it rebooted it froze and now it's stuck there
OK i fixed my problem, and for anyone who's having the same problem, here's what i did:
1- I downloaded Amon_RA's latest H recovery ROM (at the time it was v1.2.1) available right here
2- I downloaded the MyHero ROM v1.1.1 here
3- I renamed the Hero ROM to update.zip and copied it to my sd card
4- I booted my Magic in fastboot and typed this in fast boot: fastboot boot recovery-RAv1.2.1h.img
5- Once my phone was at the green recovery screen, i applied the update.zip
The following rebooting process of the phone took a long time (ie 10-15 minutes, be patient)
Once it booted completely, the phone was working perfectly with an Hero ROM.
At first i didnt receive any 3G connection, but after setting up the APN it was working fine.
I hope this will help someone out and thanks to everyone who replied to this post.
Retucex said:
OK i fixed my problem, and for anyone who's having the same problem, here's what i did:
1- I downloaded Amon_RA's latest H recovery ROM (at the time it was v1.2.1) available right here
2- I downloaded the MyHero ROM v1.1.1 here
3- I renamed the Hero ROM to update.zip and copied it to my sd card
4- I booted my Magic in fastboot and typed this in fast boot: fastboot boot recovery-RAv1.2.1h.img
5- Once my phone was at the green recovery screen, i applied the update.zip
The following rebooting process of the phone took a long time (ie 10-15 minutes, be patient)
Once it booted completely, the phone was working perfectly with an Hero ROM.
At first i didnt receive any 3G connection, but after setting up the APN it was working fine.
I hope this will help someone out and thanks to everyone who replied to this post.
Click to expand...
Click to collapse
Hi Retucex,
I have an HTC Magic from Rogers. I haven't done anything to it, it's pretty much out of the box.
Your process explains how to upgrade to a Hero ROM from a recovery. How do I upgrade my phone that is perfectly running?
Thanks!
i wish it could be that simple on my magic too. the only problem is that it says fastboot remote: not allowed. what should i do, then?
tibosee said:
i wish it could be that simple on my magic too. the only problem is that it says fastboot remote: not allowed. what should i do, then?
Click to expand...
Click to collapse
You have what they call a perfected SPL, that will not allow fastbooting into a recovery ROM. There is a way to solve this, but it is not as easy as rooting. This thread should help.
http://forum.xda-developers.com/showthread.php?t=535221
htc0 said:
Hi Retucex,
I have an HTC Magic from Rogers. I haven't done anything to it, it's pretty much out of the box.
Your process explains how to upgrade to a Hero ROM from a recovery. How do I upgrade my phone that is perfectly running?
Thanks!
Click to expand...
Click to collapse
There are many threads already about this, so a simple search should do the trick but for a general idea, you need to download the Android SDK. Then, fastboot into a recovery ROM, (google it, Cyanogen or AmonRa). Then, using the recovery ROM, flash a ROM of your choice, there are many on this forum, again, a simple search should do the trick. If you try fastbooting, and it says fastboot not allowed, you have a perfected SPL and should follow the guide above.

No! I bricked my phone!!

I just rooted my Mytouch a couple days ago and everything worked perfect and i did it without bricking my phone. I was trying to get the supercsdiv4 rom, but i needed to flash the lateset radio and heres where the problem started. the radio tried to flash was 2.22.23.02. I used the recovery image to flash it and then when i rebooted the phone it stayed stuck at the splash screen and i cant get into fastboot or recovery anymore. it just boot to the splash screen and stays there. I know i cant get my phone back but i want to know what i did wrong so that i dont ever do it again. maybe it was because the radio i had was a 32a radio and this radio i tried to flash might have been 32b but im not sure why that wouldn't work if my phone is 32b
here was my system
pvt 32b
Hboot 1.33.2005
radio 3.22.20.17
have you tried taking the battery out for a bit.. relax a while, then put it back in and try to get into recovery mode (home and power)
this actually happened yesterday and my phone was off the whole time so it has had plenty of time to rest. My phone is truly bricked
well im sorry to hear that, but i have no idea what you did wrong, unless you did flash a 32a over a 32b or the other way around, im sure that could really mess up the phone.
may be a useless idea but have you tried a hard reset
1. With the phone turned off, press and hold the HOME and BACK buttons.
2. Briefly press the END CALL/POWER button while continuing to press the HOME and BACK buttons.
3. When you see the screen with the 3 Android
images, release the HOME and BACK buttons, and then press the TRACKBALL.
i have no idea if it will do anything but might as well explore EVERYTHING.
Similar Problem (Partial Brick?)
Not to take anything away from clint1225 but
I have a similar problem and didn't want to start another thread.
I tried unrooting my devices using the method
described at theUnlockr.com. Everything was fine up until I tried using
their sappimg file (said it worked for all old magics).
At the hboot stage, it found the sappimg but the update failed.
However, the magic now says:
SPL-1.33.0006 (SAP50000)
Radio- 2.22.19.261
Ship S-On G.
It's a 32A version.
I had an engineering spl and 6.35xx radio before I attempted to unroot.
Oh I'm not able to access recovery but I can access
fastboot (computer can't find it though under "fastboot devices")
Other than that, it's stuck at the first splash screen.
Any advice/tips?
Sorry for the long post and thank you.
Good luck to you too, clint1225!
UPDATE *Similar Problem (Partial Brick?)*
In the adb, the serial number
of the htc magic is coming
up under "fastboot devices".
However, if I try to
flash a recovery for example, the adb
returns "remote access not allowed".
I've read about the gold card method
but my phone won't boot up properly
(stuck at splash screen) and I can't
access recovery. Only fastboot seems to be
working.
Any help is greatly appreciated.
Thanks!
Take it for what it's worth coming from a newb. But from my understanding if you can reach your phone with Fastboot your a NOT bricked. But this is what I have heard here on XDA, I haven't proven this myself.
Check around and hopefully with fastboot you can get your phone back. Good luck.
I did the exact same thing a few weeks back. I flashed a 3.22 radio over my 2.22 radio, thinking it's an upgrade but after it reboots, it wont get past the logo screen. I spent the whole day trying to find ways to recover it but cannot find any. Thank god I have warrenty on it so I went to the Tmobile store, told them I updated it and when it restart, it got stuck on the logo screen. They gave me a new phone and told me dont f-up this one. Now I'm afraid of updating my phone to the 6.something radio.
Update *Similar Problem (Partial Brick?)*...again.
MasterColdSoul and koolpre,
Thanks for the tips and luck!
I figured it wasn't a total brick so I searched
the whole day on google and xda.
What I can tell you is that I now have a functional phone.
I used the rogers "mandatory" update (2 sappimgs) to
get my phone (rogers 32a) working again (boots fully).
However, I now have the SPL 1.76.0010 which means
I've lost root functionality and it's harder to get root.
But I could use the phone to make a gold card and get root again.
Boy I'm glad this worked! I should have learned my lesson
but I will probably try to root, hehe!
Thanks to google search and xda community!
koolpre said:
I did the exact same thing a few weeks back. I flashed a 3.22 radio over my 2.22 radio, thinking it's an upgrade but after it reboots, it wont get past the logo screen. I spent the whole day trying to find ways to recover it but cannot find any. Thank god I have warrenty on it so I went to the Tmobile store, told them I updated it and when it restart, it got stuck on the logo screen. They gave me a new phone and told me dont f-up this one. Now I'm afraid of updating my phone to the 6.something radio.
Click to expand...
Click to collapse
just because the radio starts with bigger numbers doesn't make it an update. 3.22 was the old radio and 2.33.23.02 is the latest radio so you were actually downgrading your radio and thats why your phone brick. Just letting you know because you seem to be under the wrong impression. Dont make that mistake again. just do a little research to find the latest radio.

[help please] MyTouch 3G issue

I am attempting to root a mytouch 3G 2.1 (w/ the headphone jack)
I followed the directions from theunlockr
got my goldcard working (according to the link on that page that tells you how)
After flashing the sappimg file on that page, I still had touch screen. (the site said I wouldn't)
and when I got to step 7 - the step about flashing through fastboot - I got the error "(remote: not allow)"
I flashed the attached file and got the same error.
I searched some more and found a supposed fix I downloaded the first and tried it, got "model ID incorrect! Update Fail!"
At this point, my phone would not show up in adb, but it would in fastboot, and it would boot to the login to google screen (didnt bother logging in earlier)
Tried the second one, same error.
Reset the device, booted fine. Restarted into fast boot, it is recognized, but still getting error "(remote: not allow)". Still not showing in adb.
My phone currently says:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
so my phone works, but it is not rooted and I still have the stock recovery. If I could get Amon_ra on it I feel comfortable with doing the updates through recovery.
And if I understand it correctly, this root is like a droid, caused by the ROM and not actually part of the stock ROM, correct?
I've done 4 g-1 and a droid in less than 3 hours each, but I've been at this all day.
Help! What can I try?
I tried to show links, but I'm new to the board and cant.
Ok, So I will document as I go, so either someome can help me at some point or I can help someone else if they have the same problem.
Redownloaded the sapping file (through the cyan wiki)
Reformated my goldcard through phone.
used a sd card adapter and HxD to put goldcard back on sdcard.
transfered new sapping file to sd card
booted in bootloader, got "Model ID Incorrect" Update failed.
I do have the three skating androids though... is that stock?
I will try rebooting my computer, maybe windows is being stupid...
Rebooted, Windows is not seeing the phone. Neither is the HTC sync thing, and neither is adb
Changed USB ports, uninstalled unknown device, changed usb ports again,
ADB recognized it (not in bootloader mode)
ok, found another site with adb commands. forums .tmonews. com /index. php? topic= 10412 .0;wap2
did a google search for "vodaphone sappimg", came up with a forum post on here, downloaded it to my goldcard, still get model ID incorrect.
so I started over from the beginning using cyan instructions. update failed again.
No idea what is going on!

Mytouch 3g possibly bricked

so im trying to root my sisters mytouch 3g and it was originally 2.2.1 with a "perfect" spl, i used rom manager to flash clockwork mod, that failed and left me with no recovery, so i followed the guide to make a goldcard and was able to get it to the 2005 spl which showed s-off H (its a google branded phone) I was then able to flash clockworkmod recovery I then tried to flash cm6 to the phone and it just sat at the splash screen. I tried 2 other roms as well with the same results. Then i was reading more and it said the 2004 spl was s-off G so i went to flash that, it said flashing complete restart phone through menu to complete i did that and the update screen came up for a second then the screen went black.. Now i cant boot into hboot, recovery, or fastboot. Im thinking the phone is now bricked! Are there any other tricks to try and bring this thing back..I read somewhere about jtagging but could really find much about it. I need to get this thing working asap and dont even understand how this happened.. Ive hacked alot of things and this little phone as been the most confusing and time consuming thing to date. also if it helps it was radio version 3 something. When i try to boot using power and back the splash comes up and if i keep holding after about 4 seconds it reboots again, if i let go a second after the splash screen it just sits at the splash until i pull the battery after a few minutes.
franky_402 said:
so im trying to root my sisters mytouch 3g and it was originally 2.2.1 with a "perfect" spl, i used rom manager to flash clockwork mod, that failed and left me with no recovery, so i followed the guide to make a goldcard and was able to get it to the 2005 spl which showed s-off H (its a google branded phone) I was then able to flash clockworkmod recovery I then tried to flash cm6 to the phone and it just sat at the splash screen. I tried 2 other roms as well with the same results. Then i was reading more and it said the 2004 spl was s-off G so i went to flash that, it said flashing complete restart phone through menu to complete i did that and the update screen came up for a second then the screen went black.. Now i cant boot into hboot, recovery, or fastboot. Im thinking the phone is now bricked! Are there any other tricks to try and bring this thing back..I read somewhere about jtagging but could really find much about it. I need to get this thing working asap and dont even understand how this happened.. Ive hacked alot of things and this little phone as been the most confusing and time consuming thing to date. also if it helps it was radio version 3 something. When i try to boot using power and back the splash comes up and if i keep holding after about 4 seconds it reboots again, if i let go a second after the splash screen it just sits at the splash until i pull the battery after a few minutes.
Click to expand...
Click to collapse
Its a brick. I'll tell you now that you can find a step by step process on using JTAG in the Wiki, but its not an easy process. Your going to have to have some moderate electronic knowledge plus moderate knowledge of how the phone boots to get it working. Your better bet would be to have it replaced under the warranty or insurance if you have either. If not, your second best bet would be to find someone who already has a working JTAG setup and see if you can get them to help you out.
Sent from my Optimus T using Tapatalk.
dang another mt3g down noobs need to ask for help
here is a link to a jtag tutorial
best of luck

[Q] Main version older! Update fail!

Disclaimer: I have searched and searched, but found nothing that works.
Mytouch 3g, google branded.
Rooted about a year ago. Installed CM5(I think it was 5). Got greedy and messed it up. Tried to go back to stock. Failed. Bought a Vibrant. Put the mytouch in a drawer. Trying to get it to work again. Here is the problem(s):
The recovery installed was a vodafone. It booted up fine, but when on the welcome screen where it says "touch the android to begin" the phone would not recognize the fact that I was actually touching the screen. Track ball worked fine, but since it actually wanted me to touch the screen it was a no go.
Today while trying to fix the phone and trying to flash all kinds of recovery images I would get the "Main version is older! Update fail!" message. I finally found one (the 2.53.707.2_-_sappimg.zip) that would actually get past the update fail.
The phone now boots up to the main home screen. But it still does not recognize the fact that I am actually touching the screen. The only way I can navigate anything is by using the track ball.
When I click on the "dialer", "contacts", or "call log" icons I get the message:
"Sorry. The process android.process.acore has stopped...blah blah blah"
Does anyone have any ideas?
I have a gold card.
Download my fastboot commander from my signature and provide here all device info.
Just don't flash anything until i say so... you have been warned.
I have a similar problem.
Device info:
SAPPHIRE PVY 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
Jun 2 2009, 17:28:28
Initially the device wouldn't boot up at all. I managed to flash an RRU and get Android to boot the phone but now the problem is the SDCARD isn't recognized, every time the device boots up it says SD CARD is ready to be removed. I found a command to fix the sdcard bit from the cyanogen mod forums even though I am not running it (I know) remote boot is not allowed on my phone so I can't even use that. Tried to flash the Engineering SPL 2.53.707.2_-_sappimg using a gold card but it pops up stating:
Main Version is older!
Update Fail!
Please help!
[EDIT]
Also, fastboot getvar version-main gives out the following:
version-main: 2.56.494.7
I understand that my version is higher. Is there a way I could modify it? or the sappimg to think otherwise?
[EDIT]
Cheers!
[UPDATE]
I have managed to root using one click method and now have busybox and su.
I have also managed to flash amon_ra recovery without sd card (well obviously since SD card isn't working for me). Recovery doesn't see the sd card either sadly.
[/UPDATE]

Categories

Resources