Related
Made a huge error.....didnt go through forums and read instructions before trying to Flash a German T-Mobile MDA Compact to a English ROM....
The device is completely dead....
Followed all the steps required to get it back up...It is refusing to do so though....
Used this thread:
http://forum.xda-developers.com/viewtopic.php?t=19500
One thing to note is that I am not using the AC charger, am using the USB cable to charge the phone.
Can someone please helpme...
Haven't got past the bootloader mode...
If you followed the instructions from the other thread, it should have started flashing.
Some things to check on:
1) Did you do a full d2s before you attempted the upgrade? It's always good to have something to fall back on.
2) If you can get to a bootloader screen, all is definitely not lost.
3) Sometimes, it takes 4 or 5 minutes for the "Press to flash" comes up on the screen so be patient with that.
4) Make sure you did exactly a 416 byte copy from the original rom file in to the new flash file.
5) You can only write an nb1 file from the pc AFTER it has been created from the pocket pc. If the SD card has been pc formatted, the nb1 file will write to it but the pocket pc won't recognize it and will just sit there at the bootloader screen.
HTH
I think I fired the MDA
Well I did not create the nbf file from the ppc, downloaded it from the the forum FTP. I do not have the backup of the nbf file. As I mentioned I did not read the forums before trying the update.
I just downloaded the T-Mobile ROM update and tried installing it. Obivousioly it didn't work, Game the dreaded the 112 error in the 3rd step.
Am not even getting the bootlader screen now..
Any ideas on how I can get this device up and running.?...
ok, need some clarification here. "What" are you trying to load (nbf files or nb1 files) and how are you trying to load them (SD flash or the standard USB based upgrade)?
Easy enough to check to see if your device can still get to bootload mode....hold the camera and power switches in at the same time and hit soft reset with your stylus. After letting go of those and you see either "Serial" or "USB" at the top of the screen, you should still be able to recover from this.
Tried with the nb1 files not nbf (sorry abt teh error)..
The bootloader screen was showing up ...unitll I tried the T-Mobile MDAcompact_vers11201
After the 112 error while updating...the device now refusing to get to the bootloader mode.
Have I fried the device and made it unusable....?
hey just got back the bootloader screen...
Take the SD card out, disconnect the USB and tell me what happens when you hold the power and camera buttons in at the same time, then hit the soft reset.
Also, has the unit been charged recently?
Its showing Serial v1.00...after the reset.
Its been on the USB chatge all along.....
Great. If you get Serial at the top, this can be recovered.
If you want a good T-Mobile 1.12 rom file, go here and use this one:
ftp://ftp.xda-developers.com/Uploads/Magician/tmobile-uk_wwe_ROM_1.12.00(thereapermanl).rar
Unpack it and follow all the procedures about copying the 416 bytes, rewriting the file, etc. from the other thread. I have tested this rom file and it installs ok.
Thanks for the encouraging words...
Will it work even if I do not have a backup of the original ROM on my machine?....I only have the tmobile.nb1 file which I got from the XDA forums.
Lemme try using that and editing it.
Thanks a ton for your help.
You might be a little stuck for an nb1 flash if you don't have an original flash back up but don't fear. You can go here and get this WWE1.12 file and just do a USB type upgrade:
ftp://ftp.xda-developers.com/Magician/Shipped_ROMS/WWE_11200_128_11210_ship.exe
I know this one works too. It's ROM 1.12, Radio 1.12 and Ext_ROM 1.12. When you try to run the upgrade program though, it might give you a Country ID error. If so, use the attached upgrade program instead. If this one gives you a Country ID error again, close the program and just run it again. I've been down all these roads already.
Lemme get this right this time: I will be doing the following
1. Install the ROM as you have mentioned. With the country id hack if necessary
2. Hopefully by now the device would be alive. If so will take a backup of the ROM on the SD card
3. From then on follow the instruction given in the doc.
Hope I get it righ this time else Its going to be a long night for me.
Lemme know if I have to do anything else.
Either ROM will work fine for you. It just depends on whether or not you want I-Mate stuff on it or T-Mobile stuff on it.
Doing the USB upgrade will put the I-Mate ROM on but after that, it should be working and you can then do an SD backup, follow the SD flashing procedures and get the T-Mobile ROM on.
Good Luck!
The masupgrateut is throwing up a ruu.dll error?...you seen that one before?
What sort of error? Not found?
yup...
I extracted the ROM exe and found teh file...copied it to the windows folder..and ran the no id program...no error this time round but the update is still giving a COuntry ID error...
Been looking at various posts...specially this one...
http://forum.xda-developers.com/viewtopic.php?t=14973
Thinks thats gonna help?
ok...two things.....just run it again. The no ID program sometimes does that on the first time 'round so just run it again.
Second, stick this at the end of the RUU.conf file:
[CHECKCEID_TYPE]=1
ran the program multiple times...still getting the COuntry ID error...
Are you running this program? MaUpgradeUt_noID.exe
...with the change in the RUU.conf file?
I just noticed something....did you extract all the files to a single directory and just run it from there or did you just pull a few out?
ALL the files have to be in the same directory. This is also where you need to execute the installer program.
How to get back to RC29? by modifying the update script?
I' chose to update to RC30 while didn't know that update fixed up the permission problem.
I wanted to roll back to RC29 then I tried to do update to the RC29 package.
Failed at the first line of update script:
assert getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,test-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,test-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,test-keys"
Click to expand...
Click to collapse
I'm gonna try to append one condition to this line: "|| 1"
But is there any side effect by doing this?
And, I don't know if this will work, since I don't quite know the update package's format.
I think is kind of sun's jar file, and plus a update script in META-INF folder, two cert files(one of this also keeps the sha1 of the manifest file's sha1sum).
Can someone give me some advice?
fluke.l said:
I' chose to update to RC30 while didn't know that update fixed up the permission problem.
I wanted to roll back to RC29 then I tried to do update to the RC29 package.
Failed at the first line of update script:
I'm gonna try to append one condition to this line: "|| 1"
But is there any side effect by doing this?
And, I don't know if this will work, since I don't quite know the update package's format.
I think is kind of sun's jar file, and plus a update script in META-INF folder, two cert files(one of this also keeps the sha1 of the manifest file's sha1sum).
Can someone give me some advice?
Click to expand...
Click to collapse
As soon as you change one byte in the update.zip folder, the update won't verify against the signature, and will fail.
I've tried.
How did you modify the update.zip?
Did you package it in jar way -- which will count the sha1sum of each file and put into MANIFEST.MF?
How do the phone verify the update.zip? by cert files or just check the sha1sum?
Question: what happens, if I try to apply rc29 from SD card (i.e. signed-kila-ota-115247-prereq.TC4-RC19_RC28) after getting RC30 OTA on my G1?
1. update fails
2. update bricks the phone
3. I can have my root back
Does the name _really_ mean that TC4-RC19 is the only thing it will install over?
What checks are actually made before it bootstraps a SD card update.zip?
Can someone comment on the likely result before I get impatient and discover it is #2, please
Doesn't work but doesn't brick
I just tried it. The update will fail, but you won't brick the phone.
this may be a dumb question but why can't the modded RC30 update just be signed with the OTA keys and then used as an update.zip from the SD card?
dagentooboy said:
this may be a dumb question but why can't the modded RC30 update just be signed with the OTA keys and then used as an update.zip from the SD card?
Click to expand...
Click to collapse
Because only {Google,T- Mobile,HTC} have the OTA private keys needed for creating an OTA signed file.
I guess the only hope is google/t-mobile releasing a full update
Downgrade from RC30 to RC29
I have been reading up on the modded RC30 and haven't seen anyone mention this, so here it goes:
My phone had been taking forever to get OTA updates - I didn't get any notifications until the 11th. I wanted to keep root access so I never applied it, but downloaded the RC29 update and installed that manually. I was planning on updating to the modded RC30 once I had some free time. This morning I accidentally allowed the OTA update - damn thing popped up as I was clicking something else. I figured I was stuck with the official RC30 update.
At the end of the first part of the update it gives you the normal recovery prompt - reboot, install update from sdcard, or show/hide text, so I figured I'd try to install RC29 over RC30 (even though I'd heard it's impossible). It worked! I guess until the phone has fully installed the update, you can re-flash whatever update you have on the card. This probably won't help too many people, but if you accidentally allow the OTA update like I did and still have an update on the card this could save you!
Nice to know. Thanks
so if i let it reboot after it installed the update than im pretty much screwed for now?
ChrisAshton84 said:
I have been reading up on the modded RC30 and haven't seen anyone mention this, so here it goes:
My phone had been taking forever to get OTA updates - I didn't get any notifications until the 11th. I wanted to keep root access so I never applied it, but downloaded the RC29 update and installed that manually. I was planning on updating to the modded RC30 once I had some free time. This morning I accidentally allowed the OTA update - damn thing popped up as I was clicking something else. I figured I was stuck with the official RC30 update.
At the end of the first part of the update it gives you the normal recovery prompt - reboot, install update from sdcard, or show/hide text, so I figured I'd try to install RC29 over RC30 (even though I'd heard it's impossible). It worked! I guess until the phone has fully installed the update, you can re-flash whatever update you have on the card. This probably won't help too many people, but if you accidentally allow the OTA update like I did and still have an update on the card this could save you!
Click to expand...
Click to collapse
U Said your Phone taking foreever to get Update
This means you must be on RC19 and phone was trying to get Full RC30 from google.
Becuase of Full update it paused some where and ask you to reboot, Becuase Patch RC30 Update dont ask for it.
Please Explain you Full Situation !!
yup i got stuck with the RC30 update about an hour ago. was dialing a number and it popped up and i accidentally pressed update now! it bites, oh well
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
I'm mad that I didn't decline the update to rc30!!!!!!!
ChrisAshton84 said:
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
Click to expand...
Click to collapse
Thanks for your reply
hmm, possible reasons
it seems to me (very close to a complete moron) that the updates get copied to a "ramdisk"(4 lack of a better term) then when you see that arrow going into the chip after reboot is when its written from this "ramdisc" to the flash?
maybe its just the hash talkin take it for what it is an educated guess... AKA a theory.
bhang
ChrisAshton84 said:
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
Click to expand...
Click to collapse
great tip this is bound to help many others, anybody by any chance know when the next update is coming out?
I tried to Simulate Same thing
1. I already had Updated the phone to Stock RC30 and
2. I Copied RC30 on to SDCard as update.zip
3. Started into Recovery Modem and Pressed ALT+S
4. The Phone Started Verifying the File
5. Then i have Format Boot, System Partition
6. Copied some thing to Phone and asked me to Press Home+Back
7. I pressed it and its flahed Radio Image and reboot in recovery ode twice and did something.
In your Case the Phone might have Extracted the Images into Ramdisk but it might didnt flashed it to phone really and between that u got that Reboot Option and Reflashed the Full RC29 again.
We can reflash the same Version as many time we like but we can not flash lower version as the Recovery command dont allow.
If we keep RC30 as Update and remove the SDCard in between and put a new Card with Update.zip of RC29 the phone unmount the SDCard and then it dont detects the new SDCard is inserted and flashes error so Simulating your Process by Swapping 2 SDcard with RC30 and later on RC29 dont work for me.
If i could place RC30 into Phone and then Try to Simulate that it got the RC30 update frmo Internet and in between flash it with RC29 from SDcard might help me. But i am still not sure.
Downgrade from official RC30 to RC29 ?
My try to change some file on my system then my font was brick . But I use recovery mode, update to official RC30 then I phone worked again. But I want to acess my phone again. Please tell me how to downgrade to RC29 from official RC30 ?
This was posted in another thread here, but it needs its own. (if someone beat me to it, please delete).
A .nbh image file has been released that will allow you to downgrade your rc30 phone to rc29 which will re-introduce the root bug. Once there you can follow the steps to get root access, install the modified recovery image and flash JF's rc30 and keep root! The steps can be found in various threads on this forum, and also in my wiki.
To downgrade using this NBH file: http://android-dls.com/wiki/index.php?title=Root_For_RC30
To gain root access: http://android-dls.com/wiki/index.php?title=Rooting_Android
To flash the recovery and install modified rc30: http://android-dls.com/wiki/index.php?title=Keeping_Root
Please remember this wiki is made and edited by users, not just me. Some information might not be written as well as it can, and if you find a problem, please feel free to login and correct it.
Good luck to everyone stuck on RC30 who wanted root, its finally here!
By the way, I got this info from disconnects site (gotontheinter.net) and I believe (might be wrong) he got it from here somewhere.
Hehe. I knew someone out there still had a copy of the RC29 NBH. This is great news!
MD5 checksums:
53840b90a0fe1bfab19fab8ef8fb9724 *DREAIMG_TC4-RC29.NBH
4f0efb2037524a06bda26f286bba474d *HappyNewYear.zip
Eng Bootloader sticky information updated.
Darkrift said:
This was posted in another thread here, but it needs its own. (if someone beat me to it, please delete).
A .nbh image file has been released that will allow you to downgrade your rc30 phone to rc29 which will re-introduce the root bug. Once there you can follow the steps to get root access, install the modified recovery image and flash JF's rc30 and keep root! The steps can be found in various threads on this forum, and also in my wiki.
To downgrade using this NBH file: http://android-dls.com/wiki/index.php?title=Root_For_RC30
To gain root access: http://android-dls.com/wiki/index.php?title=Rooting_Android
To flash the recovery and install modified rc30: http://android-dls.com/wiki/index.php?title=Keeping_Root
Please remember this wiki is made and edited by users, not just me. Some information might not be written as well as it can, and if you find a problem, please feel free to login and correct it.
Good luck to everyone stuck on RC30 who wanted root, its finally here!
By the way, I got this info from disconnects site (gotontheinter.net) and I believe (might be wrong) he got it from here somewhere.
Click to expand...
Click to collapse
I'll update my stickied post and host the NBH as well.
Nice, spread this fast!! all those users who have wanted root and its here. We need them all to get it before tmo or google find a way to block this!! Someone slashdot it!!! (just please dont slashdot my site directly lol, im on shared hosting)
Yehaaa, best christmas present, however a bit late
Anyone already tried it out?
To avoid creating two stickies with overlapping information, I suggest putting a prominent link in the first post to Koush's main sticky on rooting.
will this work on tc5-rc8 uk
Nope, we'll need a different .nbh file for that. With luck someone'll find it soon
works on stock RC30 just fine..
For TC5-RC8 users:
http://forum.xda-developers.com/showpost.php?p=3109773&postcount=97
http://www.megaupload.com/?d=QIDKOHPW
MD5:
2f02dd9a3b7c7f2fe058047b9c7a0245 *DREAIMG_TC5-RC7.NBH
b253b71fad2ed0352bcb58c4966b9a25 *HappyNewYearUK.zip
For those in the UK...
Here's your RC7 NBH... http://forum.xda-developers.com/showpost.php?p=3109773&postcount=97
Man. chavonbravo is everyone's hero today.
I am trying this now - once flashed with root on RC7, can i do the bootloader flash to Engineering to keep root forever?
for the tc5 rc8 i keep getting
no signature (1 files)
verification failed
any ideas
Epic Fail
Runs through the update, then:
DREAIMG.nbh - FAIL
Update Terminate
UPDATE FAIL
UPDATE:
I had to download the DREAIMG.nbh that was in the zip file, and put that on the sd card. De-bricked, and now my phone is root-enabled.
Thank u so much, I have been waiting this for a long time. Happy new year to everybody
OMG it worked!!!!!
I wiped out my SD card with it connected to my comp through USB. Then reformatted it to FAT32 (it was FAT), and copied the dream file to my phone. Rebooted with the camera key held, pressed power when it told me to. Then it took less than 10 mins to do its thing and now I am setting up the phone again after its reset.
Woot!
kila-user 1.0 TC4-RC29 115247
ota-rel-keys,release-keys
am i missing something, i got the phone to flash back to RC29, did the reset and typed telnetd, but its not doing anything, it just says telnetd on the screen. did i miss a step?
After that go to market and download the telnet app and keep going. And using those walkthroughs I did what they said but I used JK v1.3 instead of 1.2 and now I am a very happy panda, just look at my sig!
thanks to all for the NBH file, I downgraded from RC30 to RC29, rooted upgraded to modified JF1.3 changed to Engineering bootloader, the best new year gift for G1 user.. am planning to upgrade to modifed RC8 but not now..
-Pramod
[HOW-TO] Hey Noobs ... Here's help when you think you "bricked" your phone (U.S.)
Since we have apps now that seemed to have inspired G1 noobs to root and flash their phones without the prequisite of reading the instructions, I hope they might read this to help them get out of the "bricked" situation they often find themselves in. It's simple to do, it's saved my ass a number of times, and it will quickly get you back to a pristine T-Mobile status.
NOTE: This is for U.S. T-Mobile users. Your mileage my vary and it may need to be adapted with different files relative to your country and carrier.
You are not bricked if you can get into the recovery or bootloader just jammed up!
How to quickly UN-"brick" your phone:
All you need are two files.
DREAIMG.nbh
update.zip
THESE TWO FILES ARE FOR THE CONVENIENCE OF PEOPLE IN THE U.S.These can be downloaded at:
- http://www.brentcctx.com/android/DREAIMG.nbh
- http://www.brentcctx.com/android/update.zip
DREAIMG.nbh is the original T-Mobile U.S. Rom.
update.zip is the original T-Mobile U.S. "cupcake" update (signed-kila-ota-148830.de6a94ca)
Download these two (2) files and put them on the root of your sdcard and restore the original T-Mobile rom. You will do this by
remove the sdcard from your phone
put the sdcard into your card reader
put the card reader into your computer
make sure your computer recognizes the sdcard with a drive letter (Windows) or is mounted (Linux)
look in the root directory of your sdcard for any file named "update.zip". If one is there, delete it.
copy DREAIMG.nbh to the root of your sdcard
copy update.zip to the root of your sdcard.
double check that DREAIMG.nbh is spelled just like that (with DREAIMG in all caps and nbh in lowercase)
double check that update.zip is spelled correct and the whole thing is lowercase
safely remove the card reader from your computer (unmount in linux or eject properly in Windows)
remove the sdcard from the card reader
make sure your phone is off
put the sdcard back into your phone
press and hold the CAMERA button
while still holding the CAMERA button, press the POWER BUTTON (red button on the bottom right of phone)
at this point, you should see the phone checking your sdcard, looking for DREAIMG.nbh and checking it for errors
wait until you see "OK" beside all the different items and instructions at the bottom of your screen.
now, press the POWER button (red button on the bottom right of phone) which will restore DREAIMG.nbh
wait until everything has completed.
reboot your phone
your phone will also write the old, original radio back to your phone too and reboot itself
your phone will now boot into the recovery screen (if it didn't, start over with #1)
you should see the triangle with a yellow exclamation point ! (again, if you don't, start over with #1)
Now that you are in the recovery screen, that means your phone has been restored to the original G1 factory condition. Note: you have also lost root at this point, your radio is back to the original and, if you had a different SPL, that's been replaced as well.
While still in the recovery screen, it's now time to update your phone to "Cupcake". This is the OTA version from T-Mobile. It is not rooted or modified. It is strictly the OTA update.
Open up your keyboard and press ALT + L to go from the triangle/! to a menu
For safety sake, press ALT + W to wipe your phone (it should have already occured, but we're being safe)
Now we want to apply the sdcard:update.zip by pressing ALT +S
Wait until the update completes and you see instructions at the bottom of the screen.
Follow the instructions to reboot your phone.
At this point, your phone will update the radio. Be patient and wait for the phone to reboot itself.
Your phone will reboot into recovery again. All you need to do at this point is reboot your phone by pressing HOME+BACK.
You will have to be patient again while your phone boots for the 1st time with "Cupcake". If, after 5-7 minutes your phone hasn't fully booted, that means you have done something wrong. Start completely over.
If at any point during the process you get a warning that DREAIMG.nbh or update.zip cannot be found, that means you didn't copy the files properly. Start over! Put your sdcard back into your computer, check the root of your sdcard for DREAIMG.nbh (that filename is case sensitive) and update.zip (case sensitive as well). Make sure that update.zip isn't named update.zip.zip (that often happens with Windows).
Once your phone has rebooted, you will have to log in again. Your should have your phone back.
I now recommend flashing Cyan's latest recovery image. Search XDA Developer's Forum for the latest. Download and install.
If you still want to try and flash a modified rom, hopefully you have learned from the experience and will be more careful. My suggestion is to the following items, in the following order. Search XDA for the proper thread.
-- DOWNLOAD ANY ADDITIONAL FILES YOU WILL NEED (rom, SPL?, radio)
Now is a good time to re-format & re-partition your sdcard.
In most instances, you will want 3 partitions in this order: Fat32/Ext3/Swap
If you don't have anything to partition your card, get a trial version of Paragon Partition Manager.
Once your card is partition, copy all of your needed files to the Fat32 partition.
Install Cyan's latest improved recovery image next.
Install the most up-to-date radio
If, and only if, the rom you want to install requires a different SPL, then install that.
Now install the modified rom of your choice.
It's a good idea to re-flash the latest radio once again.
Now create an emergency kit !
For future problems, take those two files you originally download from the top of this thread and put them on your sdcard right now ... in the root of your directory. ALWAYS KEEP THEM THERE ! Do NOT rename them (keep them DREAIMG.nbh and update.zip). That way, should your phone ever hit the crapper again, you are fully prepared to get your phone working again anywhere you are without the need for a computer.
NOTE: if you do keep DREAIMG.nbh and update.zip in the root of your sdcard, be careful not to overwrite the update.zip file with a modified rom update. When you want to install a modified rom, just copy the modified rom's .zip file to your sdcard (do not rename it, keep it named whatever the developer named it). If you are using Cyan's latest recovery image, you will be able to apply any update using any .zip file in the root of your sdcard. Update to a modified rom by choosing that rom's .zip file name.
Can we get a sticky please at the very top of the page since this is the #1 asked question everso we don't keep getting this new thread daily, I always kept dreaimg on my phone as a just in case emergency get out of jail free card. Can the op also edit his post to mention that you are not bricked if you can get into the recovery or bootloader just jammed up at the very top of his post
Great. Will these two files also work on EU G1 with RC7 original ROM?
If they flashed the newest SPL shouldn't they flash the Original SPL before the DREAIMG.nbh since I think it downgrades the radio or am I wrong?
That's pretty much the purpose of doing it the way I described. It's less risky to just flash the DREAIMG.nbh and let it take it back to factory condition. It does the SPL & the old radio. There is no need to do the original SPL first doing it this way. It's also the safest for anyone that's inexperienced.
gridlock32404 said:
Can we get a sticky please at the very top of the page since this is the #1 asked question everso we don't keep getting this new thread daily, I always kept dreaimg on my phone as a just in case emergency get out of jail free card. Can the op also edit his post to mention that you are not bricked if you can get into the recovery or bootloader just jammed up at the very top of his post
Click to expand...
Click to collapse
agreed... can this be a sticky! it will help cut down on senseless new threads saying help or ummm i need advice.
this is a great write-up btw!
Can you post both links to the us rc29 and also eu version rc7 plus the cupcake upgrade since they are differant and flashing roms not meant for your locale could also cause problems
gridlock32404 said:
Can you post both links to the us rc29 and also eu version rc7 plus the cupcake upgrade since they are differant and flashing roms not meant for your locale could also cause problems
Click to expand...
Click to collapse
I will, and that's a very good point.
I'll do that when I get home in the morning.
Thanks for the suggestion.
blueheeler said:
That's pretty much the purpose of doing it the way I described. It's less risky to just flash the DREAIMG.nbh and let it take it back to factory condition. It does the SPL & the old radio. There is no need to do the original SPL first doing it this way. It's also the safest for anyone that's inexperienced.
Click to expand...
Click to collapse
Really? Wow all this time since RC33 I thought you had to flash the original SPL and DREAIMG.nbh to unroot lol
Hey,
First, I searched, but couldn't come up with anything directly matching or related to this.
So I rooted my friends phone, I'm not a newbie at this, did mine and my roommates as well, gave him the 1.33.2005 Haykuru SPL, the newest radio 2.22.23.02, loaded Super E's 1.0.3 rom, and it loaded up fine, he was able to sign into google and it started to sync his phone, contacts, etc, I was even able to install an app from the market, but then his connection just stopped.
I'm going to go over it tomorrow with a fine toothed comb to make sure I didn't miss anything, but one of the things I did was AFTER loading 1.33.2005 I THEN loaded the 2.22.23.02 radio (he already had the 26i radio). This didn't change anything.
So I'm going to check all of his settings, and he can connect to the web/market through wi-fi, but is there any particular reason why he wouldn't be able to connect via the network? This is a MT3G 1.0.
Thanks
You should of flashed the new radio first then the Danger SPL
sleepy3194 said:
You should of flashed the new radio first then the Danger SPL
Click to expand...
Click to collapse
This is not true. I updated the same exact way that he described. 26I to Death SPL and then to the newer radio.
Missing the 3g connection is some unknown anomilly of rooting our phones...I have lost my 3g connection a number of times and it would always come back eventually (24 hours to 48 hours) on its own. No amount of wiping and flashing will bring it back (in my experience).
Hope this helps.
G1ForFun said:
This is not true. I updated the same exact way that he described. 26I to Death SPL and then to the newer radio.
Missing the 3g connection is some unknown anomilly of rooting our phones...I have lost my 3g connection a number of times and it would always come back eventually (24 hours to 48 hours) on its own. No amount of wiping and flashing will bring it back (in my experience).
Hope this helps.
Click to expand...
Click to collapse
Thanks G1, that's kind of what I was hoping for. I knew it wasn't bricked, since the rom loaded and everything works via wi-fi.
I'll see how he's doing today.
G1ForFun said:
This is not true. I updated the same exact way that he described. 26I to Death SPL and then to the newer radio.
Missing the 3g connection is some unknown anomilly of rooting our phones...I have lost my 3g connection a number of times and it would always come back eventually (24 hours to 48 hours) on its own. No amount of wiping and flashing will bring it back (in my experience).
Hope this helps.
Click to expand...
Click to collapse
Read this #11
Alternate Rooting Method
This method is based on the guide available at theunlockr.com. It takes a bit longer than the telnet method described above, but removes some of the risk if you plan on flashing Danger SPL, which is required for CyanogenMod 5.x, since you will already have a compatible radio at the end of the process.
For this method you will need the following:
1. Cupcake update.zip
2. flashrec
3. Amon_RA Recovery 1.7.0
(note. there are several versions of Amon_RA Recovery available in the thread above. Read through the original post and decide which one is best suited for you. For simplicity reasons, it is recommended you rename this file "recovery.img" and it will be referred to as such in this guide.)
1. After downgrading to RC29/RC7 as described above, move the Cupcake update.zip file to your SD card and rename it "update.zip". Be sure to move it to the root of the card and not into any folders.
2. Turn off your phone and boot into recovery mode by holding down the Home and End (power) buttons until the recovery screen appears (the /!\ screen).
3. Slide out the keyboard and hit Alt+S to apply the Cupcake update. This will take a little while. Let the phone reboot on its own.
4. Once the phone has rebooted, go through the setup process and sign in to your Google account.
5. Go to Settings ->SD Card and Phone Storage and select Unmount SD Card
Then select Format SD Card. The card should remount after this (this WILL erase everything from your SD card, so make sure you back up anything important first)
6. Connect your phone to your computer with your USB cable and pull down the status bar/windowshade.
Select USB Connected and hit the button labeled Mount. You should see your SD card become available on your computer.
Move the files "flashrec.apk" and "recovery.img" to your SD card.
unmount/eject/"safely remove" your SD card from your computer through your OS.
On your phone, pull down the status bar/windowshade again, select Turn Off USB Storage, and hit the button labeled Turn Off.
7. Go to Settings ->Applications and enable Unknown Sources.
8. Go to the Market and download a file manager, such as Astro or Linda.
9. Open the file manager you just downloaded, select "flashrec.apk", and install it.
10. Open your newly installed flashrec app and hit the button labeled "Backup Recovery".
Once that is complete, type in the full path to the recovery image file on your sd card, which most likely will be "/sdcard/recovery.img" and hit Flash Custom Recovery Image.
Once that is complete, exit the app and turn off your phone.
11. Boot into recovery by holding the Home and End (power) buttons until the new recovery screen appears. This time, instead of /!\, you should see a menu with several options appear. Stay on this screen. Do not reboot or turn off your phone. If you do, you may lose your custom recovery image. At this point you should already have radio version 2.22.19.26I, so you will not be at risk of bricking your phone while flashing Danger SPL due to an incompatible radio. However, it is recommended that you flash radio version 2.22.23.02 before flashing Danger SPL so you will have the most up-to-date radio and make double-sure that you have a radio compatible with Danger SPL.
sleepy3194 said:
Read this #11
Alternate Rooting Method
This method is based on the guide available at theunlockr.com. It takes a bit longer than the telnet method described above, but removes some of the risk if you plan on flashing Danger SPL, which is required for CyanogenMod 5.x, since you will already have a compatible radio at the end of the process.
For this method you will need the following:
1. Cupcake update.zip
2. flashrec
3. Amon_RA Recovery 1.7.0
(note. there are several versions of Amon_RA Recovery available in the thread above. Read through the original post and decide which one is best suited for you. For simplicity reasons, it is recommended you rename this file "recovery.img" and it will be referred to as such in this guide.)
1. After downgrading to RC29/RC7 as described above, move the Cupcake update.zip file to your SD card and rename it "update.zip". Be sure to move it to the root of the card and not into any folders.
2. Turn off your phone and boot into recovery mode by holding down the Home and End (power) buttons until the recovery screen appears (the /!\ screen).
3. Slide out the keyboard and hit Alt+S to apply the Cupcake update. This will take a little while. Let the phone reboot on its own.
4. Once the phone has rebooted, go through the setup process and sign in to your Google account.
5. Go to Settings ->SD Card and Phone Storage and select Unmount SD Card
Then select Format SD Card. The card should remount after this (this WILL erase everything from your SD card, so make sure you back up anything important first)
6. Connect your phone to your computer with your USB cable and pull down the status bar/windowshade.
Select USB Connected and hit the button labeled Mount. You should see your SD card become available on your computer.
Move the files "flashrec.apk" and "recovery.img" to your SD card.
unmount/eject/"safely remove" your SD card from your computer through your OS.
On your phone, pull down the status bar/windowshade again, select Turn Off USB Storage, and hit the button labeled Turn Off.
7. Go to Settings ->Applications and enable Unknown Sources.
8. Go to the Market and download a file manager, such as Astro or Linda.
9. Open the file manager you just downloaded, select "flashrec.apk", and install it.
10. Open your newly installed flashrec app and hit the button labeled "Backup Recovery".
Once that is complete, type in the full path to the recovery image file on your sd card, which most likely will be "/sdcard/recovery.img" and hit Flash Custom Recovery Image.
Once that is complete, exit the app and turn off your phone.
11. Boot into recovery by holding the Home and End (power) buttons until the new recovery screen appears. This time, instead of /!\, you should see a menu with several options appear. Stay on this screen. Do not reboot or turn off your phone. If you do, you may lose your custom recovery image. At this point you should already have radio version 2.22.19.26I, so you will not be at risk of bricking your phone while flashing Danger SPL due to an incompatible radio. However, it is recommended that you flash radio version 2.22.23.02 before flashing Danger SPL so you will have the most up-to-date radio and make double-sure that you have a radio compatible with Danger SPL.
Click to expand...
Click to collapse
I suppose whoever wrote that isn't aware that its perfectly safe to flash the latest radio after the Death SPL. Its how most of us who were already on the 26I radio and Danger SPL ended up on the latest radio...
19.26I ---Death SPL---- 23.02
you could just fast boot erase system and then re flash the Rom
Haha, well, thanks for all the responses guys, it actually turns out the tower near his house wasn't giving out data connections, because as soon as we met up for me to look at it, it worked fine.
G1ForFun said:
This is not true. I updated the same exact way that he described. 26I to Death SPL and then to the newer radio.
Missing the 3g connection is some unknown anomilly of rooting our phones...I have lost my 3g connection a number of times and it would always come back eventually (24 hours to 48 hours) on its own. No amount of wiping and flashing will bring it back (in my experience).
Hope this helps.
Click to expand...
Click to collapse
Do you know if this would apply to an HTC Incredible (CDMA)?