Database Info

revert to stock g1 from modded

i have a g1 that i installed Jesusfreaks 1.31 to and also flashed hardspl to it.. im having serious battery issues so i am going to return my phone for another one.. im trying to find a how-to on reversing everything i have done along with the stock rc30 image... can someone please point me at a tutorial or in the right direction...
i have googled it for the past 30 mins and have found nothing..
thanks

Download the G1Orig SPL here, flash that. Then download one of the revert update packages here and flash that. Remember to Alt+W to wipe the user and cache partitions too.
Edit: By the way are you having recurring serious battery charge loss or was it just one event?

You could flash the original bootloader (image is in the SPL thread) and then load the stock t-mobile rc29 onto your phone. Then take your phone to T-Mobile for warranty.
This way it just seems as though your phone never got the OTA rc30 update
I brought my phone in to ask a question about a clicking noise my phone had (the arm that the display moves on feels loose) when open. The guy behind the counter asked to see my phone and I was not thinking...he took it and noticed the clicking but said it was normal; he showed me his phone and a few display phones that did the same. Then he fired up "About phone" and suddenly became quite...he turned quite confused and told me that this was not a Dev phone. I played dumb and told him "I don't know, this is how it came from the store when I got it last month..." He then rebooted my phone to see both custom spash screens and the engineering boot loader...I wish I had a camera for the look on his face.
Oddly enough, both he and his manager were reluctant to give me my phone back.
So yeah, I recommend putting a stock rc29 on your phone before taking it in

i downloaded the origSPL and when i go to flash it with alt s it says verifying update package
no signature
verification faield
installation aborted
its renamed to update.zip and im assuming because i have done this before that i am doing it correctly .. any advice?

Did you already revert back to official Android? The SPL updaters are signed with test keys, so if you have already reverted to official Android then anything signed with test keys will fail to flash.

this is my build and kernel version..
would this be the updated rc30? i thought that i updated it correctly and i assume that i could not have flashed hard spl if i hadnt
Kernel version
2.6.25-01843-gfae26b0
[email protected] #19
build numberer kila-user 1.0 tc4-rc30 116143 ota-rel-keys,release-keys

When you enter recovery mode do you see JF's custom background or is it the standard recovery?

its JF's recovery screen.. im thinking to flash the test key recovery.img and then downgrade.. flash the new orig spl then the orig rc30.. witll that work?

If you're seeing JF's recovery screen then you already are running on test keys; there is no need to flash a different recovery.img

i have reformatted the sd card a bunch of times... only thing i can thnk of is that when i download the files from here to my mac it comes as a folder and then i zip them and rename them.. can this be the problem?

Comes as a folder? Sorry, I have no idea how macs work (or don't). You should not need to be zipping anything. If it worked before in the past i'm sure you got it working somehow. The MD5 of the file as it appears on the sdcard should be the identical to what I posted in the SPL sticky.

honestabe said:
i downloaded the origSPL and when i go to flash it with alt s it says verifying update package
no signature
verification faield
installation aborted
its renamed to update.zip and im assuming because i have done this before that i am doing it correctly .. any advice?
Click to expand...
Click to collapse
just use the RC29 NBH file and flash it from SD card. this will make it like it was out of the box.

but the spl will be the hardspl not the orig spl correct?

NBH file doesn't overwrite the SPL though, does it?

honestabe said:
i have a g1 that i installed Jesusfreaks 1.31 to and also flashed hardspl to it.. im having serious battery issues so i am going to return my phone for another one.. im trying to find a how-to on reversing everything i have done along with the stock rc30 image... can someone please point me at a tutorial or in the right direction...
i have googled it for the past 30 mins and have found nothing..
thanks
Click to expand...
Click to collapse
Just flash the Dream file here : http://forum.xda-developers.com/showthread.php?t=463779
It will go back to RC29 and back to that tri-color boot screen, then get the OTA RC30 here : http://forum.xda-developers.com/showthread.php?t=451090

ok.. i figured it out.. here was the problem.. on my mac when using safari in the preferences it has an option to auto open trusted files ..ex. pdf zips etc..
so it was unzipping the zips into folders.. then when i was re-zipping them it was messing it up.. i now have it working..
hope this helps others with this problem
and thanks to you guys for trying to help me trouble shoot it

honestabe said:
my mac when using safari
Click to expand...
Click to collapse
There's your problem

that brings up the question...
to make thing simple for people.
Does anyone have the orignal G1 recovery.img image so for those who want to revert back to orignal firmware with ORIGNAL keys it would be nice.
for some people its better for them to know that thye are reversing their steps them.
what I know from all the threads above is just loading loading firmwares with test keys....
now how about the original recovery.img. Provding a reverse would be nice.
=)

Getting the original recovery.img is easy. Just download the original RC30/RC8 file from any mirror and open it up with your favorite archiving program. However in order to revert the SPL you would still need to be using test keys.

recovery I can do
the reverting of SPL..hell I dont know how to do that....

Help! please

I did a wipe with JF 1.41, and now im stuck on the flashing android, it just keeps looping can someone please help me with how to get this fixed.

Joeriginal said:
I did a wipe with JF 1.41, and now im stuck on the flashing android, it just keeps looping can someone please help me with how to get this fixed.
Click to expand...
Click to collapse
!!!
Buddy, u may have gotten a corrupted update.zip, jus bring your phone back with the original rc29 nbh file, and follow the jf 41 update instructions again... you should be fine. With that file safely on your cpu or sdcard you should be able to unbrick your phone at any time. Good luck pal

Joeriginal said:
I did a wipe with JF 1.41, and now im stuck on the flashing android, it just keeps looping can someone please help me with how to get this fixed.
Click to expand...
Click to collapse
!!!
Buddy, u may have gotten a corrupted update.zip, jus bring your phone back with the original rc29 nbh file, and follow the jf 41 update instructions again... you should be fine. With that file safely on your cpu or sdcard you should be able to unbrick your phone at any time. Good luck pal

I have jf 1.41 on my phone, and when I try to enter bootlooader it goes to the same alt s, alt w option screen, what do I do from there, how do I get my phone to get past the flashing android, Im kinda stressin here.

If you can get to that screen try flashing with another update.zip off the SDCard

You will have to find another way to access your sd card, such as througha media reader, even a digital camera if that is what it takes. You need to put that DREAMIMG.nbh file back on your sdcard and flash it, and go threw the rooting process again. So find something you can use to access that microsd card with.

***{Solved!!!!}*** Bootloader locked to RC30 and above?

I decided to try and root my stock G1 this morning. The bootloader does not allow me to flash down to RC29. It gives the "Update Terminate" after it fully flashes it, but before it checks the flash. Then it only loads into the bootloader and stops.
However i just successfully flashed to RC30. None of the guides on here specify that I had to load another spl or bootloader first.... Am I missing something?? Thanks for your help.
Bootloader:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
SEP 2 2008
Solved!!!: Apparently I was on the right track. My US T-Mobile G1 was locked somehow to only accept only RC30 and above. I made a goldcard for my SD card and the image no longer failed (same sd, same image file) at the flashing the .nbh. If anyone has been having issues flashing a US G1... try a goldcard... It instantly fixed the problem! I guess its not only for German and UK?!
BTW.. thanks to pk at codeandroid.org for his guide to make the goldcard without a WM device or linux... http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2 (in broken english... lol)
Thanks to Viper and revskills.de for their work on goldcard images
Thanks to JesusFreke for this bada$$ ROM (1.5)
Thanks to Haykuro for his android 101 guide.
Great work everyone really...

you need to make sure that your sd card is formatted fat32 and checksum on the DREAIMG.NBH
then try again. should work.

thanks for replying did that. The md5 checksum matched perfectly I have 3 different sd cards all formatted in fat32 only. still no go. I have tried 3 different links to the dreaimg.nbh. made sure it was in all caps and everything. nothing.
It will find the file.
It will flash the file to 100%.
When it would normally check the integrity of each portion it says...
"dreaimg.nbh - FAIL"
"Update Terminate"
"Update FAIL".
The odd part is it will flash the RC30 nbh just fine... same sdcard, same instructions.

try a different sd card- my stock one didnt flash either, same error over and over.
use this nbh -
http://www.mediafire.com/?sharekey=78b87e4b3d9bce857f7ec40ada4772a691de501fd3b9a6eb5be6ba49b5870170

tried all 3 cards with your file. same thing. Why will it so willingly let me flash rc30 the exact same way?

you got me.....

this was the confusing part. so im sitting on rc 30 right now for the 5th time. i have had 30 or so unsuccessful flashes of RC29 and EVERY flash of RC30 was successsful... this is my barrier to Haykuros and/or JF roms...

The file names are case sensitive. It must be DREAIMG.nbh . All caps for the prefix, no caps in the suffix.

thanks for your response... i tried both ways. most of my 30 attempts was changing caps... no caps... on file name and extension. reformatting... downloading from new sources... clearing my temp folder so windows wasn't transferring the same file every time since they are names the same (trust me windows does that with same named and same sized files...)
The only thing I can come up with is a modded bootloader. My G1 is not the one i had from launch date... so this phone never had any lower than RC33 (got the phone 5 weeks ago, came pre-loaded with RC33). This maybe one of T-Mo's tactics in the "War on Root".

That may not be the issye... I had RC30 when I bought the phone. I was able to get to RC29 with no issues... I don't think tmobile did anything to the phone.

i wish it wasnt but how can this phone reject rc29 but accept rc30. does anyone have a rc28, rc19, or below .nbh?

Can you try flashing the engineering Bootloader or HARDSPL first, then fastboot?
I'm not sure if you can use those without having root first though.

ICBM said:
Can you try flashing the engineering Bootloader or HARDSPL first, then fastboot?
I'm not sure if you can use those without having root first though.
Click to expand...
Click to collapse
no i cant. from what i've seen the first step to installing any bootloader is accessing SU... which is root... which means i'm shot down again... getting depressed.
Has anyone tried loading HardSPL without root?

crushsuitandtie said:
no i cant. from what i've seen the first step to installing any bootloader is accessing SU... which is root... which means i'm shot down again... getting depressed.
Has anyone tried loading HardSPL without root?
Click to expand...
Click to collapse
You are right, you need root to be able to load a different boot loader. I got a replacement sent to me from T-Mobile with RC33 on it maybe 3 weeks ago and i had no problems with obtaining root. If i were you i would call up T-Mobile and tell them the Menu button is not working every time on your replacement. They may send you an express replacement...

makes me wish i had kept my launch phone... I got it with RC17 or 18... but i remember getting rc19 ota... this sucks. The only reason i traded it in is because GPS wouldnt ssync anymore unless i did a wipe... so i knew it was a software problem... if i had just rooted it I bet i wouldnt be in this crap. i couldbe on haykuros... right now...

Sounds like a hardware issue to me. The data from the SD card isn't being written to flash properly so the SPL can't verify it. I would try calling T-Mobile to see if they can send you another unit. Obviously don't tell them you tried to flash an unsupported ROM, just make up a story and they will likely believe it.

Just to exclude the obvious. Shouldn't the file be called DREAMIMG.nbh not DREAIMG.nbh as you've written.. Or is that just a typo in your posts?

crushsuitandtie said:
thanks for your response... i tried both ways. most of my 30 attempts was changing caps... no caps... on file name and extension. reformatting... downloading from new sources... clearing my temp folder so windows wasn't transferring the same file every time since they are names the same (trust me windows does that with same named and same sized files...)
The only thing I can come up with is a modded bootloader. My G1 is not the one i had from launch date... so this phone never had any lower than RC33 (got the phone 5 weeks ago, came pre-loaded with RC33). This maybe one of T-Mo's tactics in the "War on Root".
Click to expand...
Click to collapse
ok i received my phone like a month ago an it came with Rc33 install and my phone when try to flash Recovery, i get a error EveryTime, look at all My Topic you see
I just keep on trying and i get it on my 7th try lol I'm not lien

bp8575 said:
Just to exclude the obvious. Shouldn't the file be called DREAMIMG.nbh not DREAIMG.nbh as you've written.. Or is that just a typo in your posts?
Click to expand...
Click to collapse
The correct image name is DREAIMG.nbh. looks wrong but its right... I think it IS a hardware issue. The is writing but not verifying certain images... and its now giving me checksum errors on rc30 after 8 successful loads, but when i retried without doing anything to the file it completed. I would say its my card but I have 3 different cards...

bump for anyone else having trouble...

Something Went Wrong - HardSPL

First of all, thank you to all the modders out there. Next, thanks to everyone who gave a little time to help me with my problem.
A little background: I have an ATT Tilt, it is about 18 months old and for the most part has been functioning great. I have had several different ROMs on here - I probably have had 12 or so ranging from 6.1 to 6.5 and back. I have been using HardSPL for as long as I can remember. The most current ROM I had was a clean 6.5 Build 23003. It was working really well, except for sometimes I couldn't get the phone to come out of sleep mode and I would have to soft reset. It started happening more and more frequently, so I decided to reflash to Ultimate-X2.V6 -23004. As I was reading through the thread, he recommended HardSPL 3.34 and Radio 1.71.xxx. No problem I said, so I went off to flash 3.34 to replace my 3.56 SPL. I was using a 1.65 radio, but I never got the chance to upgrade.
So thats where the problem starts. When I try to flash the 3.34 SPL (following the instructions and using JumpSPL) it flashes, but then the phone doesn't reboot. I figure the SPL wiped out something, so following the recommendations in the Ultimate X2 thread, I attempt to flash the ATT Stock ROM. I start the phone up in bootloader mode (the bootloader still says 3.56 - interesting eh) and then flash the ATT Stock ROM. The ROM installs but the phone never reboots...
I have tried flashing Radios and other ROMs and redoing the SPL, but the phone just doesn't boot. I can reliably get to the bootloader screen, but it still says 3.56. I tried following the Wiki for "Kaiser Stuck in Bootloader" and flashing ROMs or SPL that way, but it still doesn't work.
I would also love to give you guys that diagnostic information (I should have done this last night) because I was able to view it, but now when I try to boot KAISDIAG.nbh from the memory card it just sits at "Loading...".
I have tried just about every step of different ways of flashing, different SPLs, etc. If there is anything anyone can recommend or try I am more than willing.
Let me know if you need more information or I need to clear anything up.
Again, I appreciate everyone taking time to read this and offer up their expertise.
Thanks,
OutrightLie

Only thing i can suggest is flashing 3.56 again with th SD card. Then 3.34 with the SD card. Or have you tried that already?

Just wondering... do you removed SIM card before flashing your new HardSPL?

I *think* I have tried that.
Does JumpSPL do anything other than put the phone in Bootloader mode? Or is all I have to do, just copy the *.nbh to the memory card, rename it to KAISIMG.nbh and then let it go. If JumpSPL does something more, I may be in trouble because I can't get to an OS.

daigoro64 said:
Just wondering... do you removed SIM card before flashing your new HardSPL?
Click to expand...
Click to collapse
I never have. Not with roms radios or SPL. I know its recomended but i have never had a issue with that.

daigoro64 said:
Just wondering... do you removed SIM card before flashing your new HardSPL?
Click to expand...
Click to collapse
I did remove it the first time, and a few times after that while trying stuff. The first time - for sure. Other times, it was in or out while I was just playing around with stuff. Hopefully something I did subsequently didn't make the problem worse.
Are there any steps I can take to if I did leave the SIM card in during a troubleshooting flash that screwed it up?

OutrightLie said:
I *think* I have tried that.
Does JumpSPL do anything other than put the phone in Bootloader mode? Or is all I have to do, just copy the *.nbh to the memory card, rename it to KAISIMG.nbh and then let it go. If JumpSPL does something more, I may be in trouble because I can't get to an OS.
Click to expand...
Click to collapse
From SD. You will need kaisdiag.nbh and then rename Spl to kaisimg.nbh. Have those both on root of card.

smokestack76 said:
From SD. You will need kaisdiag.nbh and then rename Spl to kaisimg.nbh. Have those both on root of card.
Click to expand...
Click to collapse
I will try that. I need a memory card reader here at work, so this may have to wait until I get home. The only roadblock I see, is right now I have just KAISDIAG on the memory card and it gets stuck at "Loading..." when I attempt to boot. It didn't do this last night, but this morning it seems get stuck there.

OutrightLie said:
I will try that. I need a memory card reader here at work, so this may have to wait until I get home. The only roadblock I see, is right now I have just KAISDIAG on the memory card and it gets stuck at "Loading..." when I attempt to boot. It didn't do this last night, but this morning it seems get stuck there.
Click to expand...
Click to collapse
I have one in my share folder. Might wanna get it and format the card..remember it has to be fat32 and replace the kaisdiag and SPL just to be safe.

I will give it a shot when I get home tonight - unless I can find a memory card reader before then.
Thanks!

Follow exactely this thread
http://forum.xda-developers.com/showthread.php?t=498320
Note your sdcard should be formated FAT32

I just got home. I copied the KAISDIAG.nbh and the 3.56 bootloader (called it KAISIMG.nbh) to the memory card after formatting it to FAT32. It attempts to load the KAISDIAG, but stops at "Loading...". I tried both a 2GB SD Card and an 8GB card, still no luck.
Any other things I can try?

[Q]Fuze undetected on any PC, just charges

I am in deep trouble here and could really use some help please. My ATT Fuze is not being detected by any PC and i have tried everything from different wires to changing everything on the fuze it self. Now my only option is to exchange it but i don't have the original OS because i am using NRGs Rom and hard SPL it about 4 months ago. Now to my question, is there anyway i can revert it to stock ROM and SPL with micro sdhc card? I need some steps please because i cant find a way to do it. Would i have to change the OS and the SPL to return if there is anyway please let me know.

darkreborn said:
I am in deep trouble here and could really use some help please. My ATT Fuze is not being detected by any PC and i have tried everything from different wires to changing everything on the fuze it self. Now my only option is to exchange it but i don't have the original OS because i am using NRGs Rom and hard SPL it about 4 months ago. Now to my question, is there anyway i can revert it to stock ROM and SPL with micro sdhc card? I need some steps please because i cant find a way to do it. Would i have to change the OS and the SPL to return if there is anyway please let me know.
Click to expand...
Click to collapse
First, what OS are you running on your PC.
Second, have you disabled/Enabled "enable faster data" in Settings/Connections/USB to PC?
Third, Have you deleted the partnership and tried to reestablish it?
Doesn't seem to be a warranty issue.

Fuze Reply
First of all thanks for your reply.
I have tried it on 4 different computer but unfortunately same result on vista and XP, on my phone i am using NRG july version rom.
I have disabled and enabled faster data in but doesn't seem to matter.
I tried everything, i reinstalled windows mobile device but doesn't seem to matter. When i ended the partnership it wasnt being detected after it or before it.
Cant i exchange it because its a faulty phone? Also can u please tell me if i can revert it to att stock rom and spl with a micro sdcard because i am going to buy a card reader. I really don't want to toss this phone and waste all that money please help!

darkreborn said:
First of all thanks for your reply.
I have tried it on 4 different computer but unfortunately same result on vista and XP, on my phone i am using NRG july version rom.
I have disabled and enabled faster data in but doesn't seem to matter.
I tried everything, i reinstalled windows mobile device but doesn't seem to matter. When i ended the partnership it wasnt being detected after it or before it.
Cant i exchange it because its a faulty phone? Also can u please tell me if i can revert it to att stock rom and spl with a micro sdcard because i am going to buy a card reader. I really don't want to toss this phone and waste all that money please help!
Click to expand...
Click to collapse
Yes, you can revert via SD card.
Do Radio and ROM first, then do stock SPL last.
Rename each RAPHIMG.NBH (one at a time) on a FAT32 formated card 2gb or smaller.
Go into bootloader mode and it should flash from there.
I would test your USB connection after you flash back to stock ROM before you flash the stock SPL to see if it may have fixed your issue.

Huh
Thanks a lot man!
Now the hard part , why do u say a card 2gb or smaller?
So i can revort the SPL with a micro sdhc card also? can u tell me where i can find this stuff, i am really sorry for the trouble and would really appreciate it if you can tell me step by step because i am a noob
Hopefully ATT exchange it for the usb issues , gotta check with them after this. Thanks

darkreborn said:
Thanks a lot man!
Now the hard part , why do u say a card 2gb or smaller?
So i can revort the SPL with a micro sdhc card also? can u tell me where i can find this stuff, i am really sorry for the trouble and would really appreciate it if you can tell me step by step because i am a noob
Hopefully ATT exchange it for the usb issues , gotta check with them after this. Thanks
Click to expand...
Click to collapse
I've heard that anything over 2 gb will cause an issue but I have done it from an 8gb card.
Start here for issues encountered.
Basically once you find your ROM Radio and SPL, extract the files so you can see the .NBH files for each.
1. Take the ROM file and rename it "RAPHIMG.nbh " without quotes.
2. Place it in the root of your storage card and enter bootloader mode (Volume Down + Reset), the phone will read the image file and begin to load it.
Do this for each file but wait until the first file has loaded.
Radio.nbh will be renamed to RAPHIMG.nbh
SPL.nbh will be renamed RAPHIMG.nbh
As one is done loading, remove it from starage card and put the next one on and repeat step 2.
Another thread regarding SPL.
I hope this helps you and sorry I don't have the time to walk you through it.
Just read first then you'll know what to expect.

Bruce Inman said:
I've heard that anything over 2 gb will cause an issue but I have done it from an 8gb card.
Click to expand...
Click to collapse
my best guess is just in case the bootloader doesn't have drivers for SDHC cards... my x51v has drivers for SDHC in WM, but flashing requires SD cards because the bootloader doesn't read SDHC

revert SPL or no?
Hey thanks bruce!
One more question, should i revert the SPL even tho i changed the radio and os. When i go to ROM version it says 1.95 but is that the SPL? Also you think ATT will take the phone back with the phone not syncing reason or do i have to make up some other stuff up? O btw the 8gb kingston card worked fine for reverting it and it still doesnt detect the phone

darkreborn said:
Hey thanks bruce!
One more question, should i revert the SPL even tho i changed the radio and os. When i go to ROM version it says 1.95 but is that the SPL? Also you think ATT will take the phone back with the phone not syncing reason or do i have to make up some other stuff up? O btw the 8gb kingston card worked fine for reverting it and it still doesnt detect the phone
Click to expand...
Click to collapse
To be safe I would revert the SPL as well.
The 1.95 is the ROM build base.
You want to revert back to stock SPL 1.90.
I can't second guess what AT&T will cover or not but you may want to "further your cause"....
Best of luck!!!

in my experience (my UK t-mob vario is back at repair right now) - DONT revert the SPL if you cant do it from the USB.
Obvisously you have a different setup to me, but when i tried to revert my phone to stock for exactly the same fault (no usb sync, regardless of pc or cable / phone rom, state etc etc) i managed to get the phone to refuse to boot due to a spl / rom difference. As i couldnt load from usb - i couldnt flash anything new, and as i had managed to overwrite hard spl - i couldnt flash what i wanted from the SD card! (if i could get the usb to work, i could fix it all - but as that was the problem i had to send it off fubar)
For some reason (god knows why!) it appears that t-mob are repairing my phone under warrenty despite the spl error but i wouldnt advise getting yourself in the same situation, as i was 100% expecting it to come straight back to me!
My personal advice is send it off with the correct rom, radio & splash screens (and remove security unlock if required) so the phone looks stock - the only difference will be the spl version. They probably wont notice!

1.90 or 1.95
Thx for the info guys, my new phone is coming and it took me about 2 to finally on its way. About the SPL, mine says 1.90 and that was when i first did the hard spl to change roms. What is the stock SPL 1.90 or 1.95? at loading it hows me 1.90 olinex i think...also i can change it if needed with my 8gb sdhc card or no?

I had a problem with my PC not detecting my fuze a few weeks ago. I found out it was my new firewall blocking the connection. I disabled the firewall and it worked like normal.

If it were me i would try to connect again after you flash the stock rom. If there was something wrong with the usb it still wont work. If it connects to activesync the maybe it was your ROM, or something else.
Just a suggestion