Related
So I installed the updated ROM and Radio to see if I could get the GPS working...
Everything went fine, I had to call Verizon to get the AKEY, but everything worked after that. Then I decided to downgrade because I thought it was running a little slow, and I didn't like all the added programs.
That was where I messed up. I did everything like I thought I was supposed to. I used the RELOCKER, and flashed the older version of the VZW rom... well atleast I attempted to. My phone is stuck at 0% flashed.
Any ideas?
ajshah said:
So I installed the updated ROM and Radio to see if I could get the GPS working...
Everything went fine, I had to call Verizon to get the AKEY, but everything worked after that. Then I decided to downgrade because I thought it was running a little slow, and I didn't like all the added programs.
That was where I messed up. I did everything like I thought I was supposed to. I used the RELOCKER, and flashed the older version of the VZW rom... well atleast I attempted to. My phone is stuck at 0% flashed.
Any ideas?
Click to expand...
Click to collapse
It is really tough to brick a phone.
Just pull the battery and wait 3s. Then replace. It should boot back up to the last ROM installed.
The only problem with that is that it doesn't... its stuck on the bootloader screen...
ajshah said:
The only problem with that is that it doesn't... its stuck on the bootloader screen...
Click to expand...
Click to collapse
1) To get the Tricolor Bootloader Screen to come up (actually this may be where you are already - if so, skip to #2). You must simultaneously: (a) hold down the power button; (b) hold down the camera button; and (c) use your stylus to press the little reset button in the hole at the bottom of your 6800. This should pop up the Tricolor Bootloader screen if you'd installed this first, as instructed.
(2) Then plug it into the computer's USB port. Make sure that USB is NOT enabled in "Windows Mobile Device Center" (should be in your start->programs menu). Click on connection settings and turn off the checkbox for USB connection.
(3) Then run the 3.17 Rom loader. This will get you back up and running.
(4) Then start again and run the 2.09 or 2.17 Rom loader. It should load without a hitch.
(5) Then you will have to re-setup your your MSID and MDN. You will need your EPT.
3.17 Rom Loader? which one is that?
I know I am asking a lot, but I have been searching all day, and I am a relative n00b...
so Thank you soo much for helping me out...
I have the same problem as you. Relocked the phone and now I can't do anything. Tried flashing to different radios, different roms and nothing. I did get 1 rom to go to 1% complete but it told me I had the wrong vender(sic) or something
ajshah said:
3.17 Rom Loader? which one is that?
I know I am asking a lot, but I have been searching all day, and I am a relative n00b...
so Thank you soo much for helping me out...
Click to expand...
Click to collapse
Hmm -- well maybe I need more info.
Which ROM did you 'upgrade' to?
I upgraded to the new one with GPS... I did everything in the steps, the way it said to do it...
Then I wanted to downgrade, and I saw how some1 else did it with relocking it and downgrading it, so now my bootloader reads:
TITA100
SPL-1.06.0000
CPLD-9
and it still says RUUNBH in the right corner...
Oh, and the SD card TITAIMG.nbh thing doesn't work either, unless I am doing it wrong...
The error I get is a 262 error, if that helps...
ajshah said:
I upgraded to the new one with GPS... I did everything in the steps, the way it said to do it...
Then I wanted to downgrade, and I saw how some1 else did it with relocking it and downgrading it, so now my bootloader reads:
TITA100
SPL-1.06.0000
CPLD-9
and it still says RUUNBH in the right corner...
Click to expand...
Click to collapse
Oh -- then just run the Official Released version of 2.17. You should be golden.
quantumforce1 said:
Oh -- then just run the Official Released version of 2.17. You should be golden.
Click to expand...
Click to collapse
Where can I find the official version?
do i need to go through all of this if i want to go back from the gps rom to the dcd kitchen/rom 2.0 or can i just flash back and you only have to relock if you want to go back to the stock rom?
friguy33 said:
do i need to go through all of this if i want to go back from the gps rom to the dcd kitchen/rom 2.0 or can i just flash back and you only have to relock if you want to go back to the stock rom?
Click to expand...
Click to collapse
I reflashed back to the 2.0 rom and I got stuck at the vzw logo screen so I tried to get the radio flashed back. I ended up trying to lock the spl and thats where i got screwed
quantumforce1 said:
Oh -- then just run the Official Released version of 2.17. You should be golden.
Click to expand...
Click to collapse
Tried that... Didn't work... I tried re-installing radio 1.40 first and then 2.17 and nothing, then i tried the other way... I still am stuck at 0% and then I get the 262 error...
friguy33 said:
do i need to go through all of this if i want to go back from the gps rom to the dcd kitchen/rom 2.0 or can i just flash back and you only have to relock if you want to go back to the stock rom?
Click to expand...
Click to collapse
Think of it this way ...
There are 'basically' three parts to the software that runs your phone.
1. There is the SPL / bootloader.
2. There is the Radio ROM.
3. There is the System ROM.
2 and 3 above will not load or work correctly if #1 above is bad or the wrong version.
Therefore, if you want to go back to 2.17 then the easiest way to do this is to:
1a. Get the ReLocker (which is SPL v1.06)
1b. *Don't worry that it stays in the boot loader mode.
2. Run your offical carriers released ROM, Sprint 2.17 (which will include both the System and Radio ROMs).
3. Reload your custom apps.
4. Sync.
5. *Remember from the previous article above, you will still need your EPST, MDN and MSID codes.
That's it.
If I reset, right before I get the tri color screen, it flashed a grey screen that says "no image file" for a second.
dagnasty said:
If I reset, right before I get the tri color screen, it flashed a grey screen that says "no image file" for a second.
Click to expand...
Click to collapse
Do you have the tri-color screen up? If so - what version?
Screen says:
TITA100
SPL-1.06.0000
CPLD-9
dagnasty said:
Screen says:
TITA100
SPL-1.06.0000
CPLD-9
Click to expand...
Click to collapse
Mine says the same ****....
Does yours flash "no image file" right before you get the tricolor screen?
First, my problem started with either updating to the new JFv1.43 recovery, or flashing the new SPL from Haykuro.
Symptoms:
1. Everytime I flash a new ROM, wipe or no wipe, I come back stuck at the T-Mobile G1 boot screen. The only way I've found to get through is to take out battery and boot into ADB (the Camera + Power screen) and "fastboot flash boot boot.img". This almost always work.
2. Nandroid stopped working. Nandroid always errors during the process of backing up, and I'd only have splash1.img and splash2.img in the nandroid folder of my SD card. Kind of want to try reflashing the JFv1.43, or even go back to 1.42 (can't find) for troubleshooting. Also not sure if this would affect the new SPL and cause a brick.
3. "Insufficient storage available" with Dude's and Cyanogen's builds. I'm not sure if this one is related to recovery or SPL. This might be caused by past attempts at doing apps2sd (I've done both symlink and unionfs).
Anyways, losing Nandroid has lost me a lot of time with trying out new ROM's, I'd really like to get it fixed. The boot stuck is a nuisance, but much less troublesome than losing Nandroid.
Its the SPL.
lbcoder said:
Its the SPL.
Click to expand...
Click to collapse
So then I'm stuck in this situation? Since the SPL can't be downgraded.
cigar3tte said:
So then I'm stuck in this situation? Since the SPL can't be downgraded.
Click to expand...
Click to collapse
I'm not positive (***so dont do this without researching***) but i think it would be possible to flash to a different one ( i mean, you flashed another SPL over the original one, right? ).
There is a "mega-thread" that has information on all the SPL's and their features/updates. If the info is anywhere, it's prob in there. Search in the Dev forum.
tr.slate said:
I'm not positive (***so dont do this without researching***) but i think it would be possible to flash to a different one ( i mean, you flashed another SPL over the original one, right? ).
There is a "mega-thread" that has information on all the SPL's and their features/updates. If the info is anywhere, it's prob in there. Search in the Dev forum.
Click to expand...
Click to collapse
As far as I can remember, that is where I read that you can't flash the older SPL over the new one.
cigar3tte said:
as far as i can remember, that is where i read that you can't flash the older spl over the new one.
Click to expand...
Click to collapse
damn the man!
cigar3tte said:
As far as I can remember, that is where I read that you can't flash the older SPL over the new one.
Click to expand...
Click to collapse
I could be wrong, but the key is not flashing an older RADIO with the newer spl.
You should still be able to go back to hardspl with no issues.
cigar3tte said:
As far as I can remember, that is where I read that you can't flash the older SPL over the new one.
Click to expand...
Click to collapse
I have flashed from the New H SPL to the HardSPL i originally had on the phone when I found out people were having trouble with the SPL. I install the NEW SPL again to run Hero, but you CAN flash it back to the older SPL I would recomend HARDSPL though.
*not responsible if this doesn't work but I was able to do this without any trouble. Was just a bit nerve racking.
i am 99% sure the above post is correct, don't flash a different radio, but you can flash another SPL right over the Haykuro SPL. i would double check that as there is a 1% chance it will totally screw your phone and i don't wanna be the guy that told you to do something that bricked your phone, but it should work. just to be safe you should make sure splash1 is the t-mo g1 screen so if it stops you can call t-mo
i flashed from the latest haykuro spl 1.33.2005 , to the original t-mobile spl HBOOT-0.95.0000. I fastbooted and it was showing the original spl installed.
Hey guys I am trying to figure out which SPL/radio I need and if I can flash it. I originally rooted the phone with the "1 click" method( Flash Rec). I am currently running Amon RA 1.3.2G recovery right now. Can I just download the correct SPL/radio and flash it through recovery?
My phone stats:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT- 1.33.0006 (SAPP30000)
CPLD -10
Radio- 2.22.19.26I
Please help
Thanks
Matt
You have the radio needed. Get the 2005 Engineer's spl from Amon_RA's thread. That's the one that he gave in his instructions to root it with the gold card method. You can just flash it through recovery. I did my first mytouch, well second, I bricked the first one the first time, with the gold card method. Then we got a third one for my mom, and I rooted using 1 click root, then I just flashed the spl. It gave me no problems whatsoever.
darkstar, did you try it out? did it work? i have the same phone as you and i would love to try this.
pepe6934 said:
darkstar, did you try it out? did it work? i have the same phone as you and i would love to try this.
Click to expand...
Click to collapse
almost everyone in these forums is using this spl or another one similar to it I wipe phone then apply the spl through recovery done it to a lot of mytouch's so no need for his confirmation lol
i have the same question.
so do i need to wipe->flash spl->wipe->flash rom?
I am on dwang 1.13 right now, do i need to flash to dwang 1.12 then flash spl, then flash 1.13?
d_bot said:
i have the same question.
so do i need to wipe->flash spl->wipe->flash rom?
I am on dwang 1.13 right now, do i need to flash to dwang 1.12 then flash spl, then flash 1.13?
Click to expand...
Click to collapse
the way I did it was, go to recovery>wipe>flash spl>pull battery>go back to recovery>flash rom>reboot
worked for me every time
ok right now my sdcard has only a fat32, in ra-v1.3.2g do i need to wipe data, cache, and dalvik-cache? then flash spl->bull battery->then back in to flash the rom? I read somewhere that you have to flash to a higher version of the rom that you are currently on, is this not true?
Thanks for your help
i havent wanted to flash an spl until eugenes new 2.0 rom....so could i throw both the spl and eugenes 2.0 on the sd card, boot into recovery->wipe->flash spl->reboot into recovery->flash eugenes 2.0->reboot and everything SHOULD work ok?
d_bot said:
i havent wanted to flash an spl until eugenes new 2.0 rom....so could i throw both the spl and eugenes 2.0 on the sd card, boot into recovery->wipe->flash spl->reboot into recovery->flash eugenes 2.0->reboot and everything SHOULD work ok?
Click to expand...
Click to collapse
thats what I did in the past when I first tried hero like 3 months ago...
awesome thanks! so do i need to wipe all 3 (data, cache, dalvik-cache)
d_bot said:
awesome thanks! so do i need to wipe all 3 (data, cache, dalvik-cache)
Click to expand...
Click to collapse
well data and cache are the both in the data wipe option and you can wipe them all if you want to I guess but I didnt have all those options when i was on cyanogen 1.4 just did the general wipe and flashed lol, only had one option back then
lol thanks man! im really tempted to try it tonight, but its late and i better not while i am tired hahahaha I don't want to end up with a $300 brick.
thanks for your help
It worked with no problems. I have the new SPL. Thanks guys.
Okay thanks for the help guys. I was actually going to try what you all said to do but I figured I would ask first. I wiped everything flashed SPL 1.33.2005, pulled battery, entered recovey again flashed a rom let it boot completely, shut phone off, booted to hboot and my SPL was changed to 1.33.2005.
Thanks for the help.
Why...?
If I can flash Hero's and 2.0's and what not without incident, why change the SPL? What advantage does it offer? I haven't had any trouble with my current SPL. I had to change my SPL on my Dream, but that was because the Hero's were too large, but that isn't a problem with the sapphire. Just curious.
Why...?
sorry. double post.
BlackElvis79 said:
If I can flash Hero's and 2.0's and what not without incident, why change the SPL? What advantage does it offer? I haven't had any trouble with my current SPL. I had to change my SPL on my Dream, but that was because the Hero's were too large, but that isn't a problem with the sapphire. Just curious.
Click to expand...
Click to collapse
with the perfect spl, you can't do fastboot, so you flash an engineer's spl to rectify that problem.
BlackElvis79 said:
If I can flash Hero's and 2.0's and what not without incident, why change the SPL? What advantage does it offer? I haven't had any trouble with my current SPL. I had to change my SPL on my Dream, but that was because the Hero's were too large, but that isn't a problem with the sapphire. Just curious.
Click to expand...
Click to collapse
wait what 2.0 rom are you using? Eugenes?
glad everyone got it figured out
d_bot said:
wait what 2.0 rom are you using? Eugenes?
Click to expand...
Click to collapse
Eugene's 2.0 Eclair
@tazz9690
Thanx.
Hey there guys...
So I ****ed up. I flashed the Danger SPL for WG's build of cyanogen's rom and then selected reboot. I wasn't aware you needed to flash a rom after adding the SPL but now I'm stuck with the "T-Mobile G1" screen and it will not boot into recovery.
I hold the Home key down when I boot, nothing. I hit Home, Menu & End keys at the same time and it won't even reboot. any tips? Sorry I'm searching through the threads now for help. Thank you!
No, rebooting is fine. You didn't have the correct radio, which you should have had since 1.5. You can either get a replacement from tmo saying an update bricked it, replace the motherboard or buy a new one.
the radio was wrong?
I had the 26I radio I believe
Its of no help, but I am curious.
why flash DangerSPL for a rom based on Cyanogens ?
I didnt think you needed DangerSPL for that rom ?
vixsandlee said:
Its of no help, but I am curious.
why flash DangerSPL for a rom based on Cyanogens ?
I didnt think you needed DangerSPL for that rom ?
Click to expand...
Click to collapse
you dont need too lol but some people do it just in case they want too flash a 2.0 or hero or 2.1/hero lol... but for the OP if you had the 26l radio then the spl was okay to flash does it boot up to the mytouch screen or does it do nothing I think its camera and power for the G1 to get into fastboot try that and see if it turns on
Take out battery for 10 seconds. Press Back button several times. Put back battery. Boot into recovery mode.
Well...
took it into t-mobile & just received by replacement phone yesterday.
How hooked up is that for xmas?
Brand new G1 running super smooth I love it
Boomer1331 said:
Well...
took it into t-mobile & just received by replacement phone yesterday.
How hooked up is that for xmas?
Brand new G1 running super smooth I love it
Click to expand...
Click to collapse
Great! What was your explanation to them?
Hi,
Already posted part of the situation in Amon_RA's recovery thread but neither of the answers there seem to solve my problems. Decided to post it here since the problem seems to involve aspects other than the recovery itself.
Here's the complete situation:
Had problems with RA recovery freezes since the start and with different versions. I could (and can) enter recovery mode (v1.6.2), scroll down the options but after 15 seconds the recovery just freezes and reboots every single time. Checked the version (H) and the MD5, they where all correct. Tried cm-recovery-1.4-32A and it seems to work fine but when I flash a ROM (1.6) I have similar problems with the ROM (freeze+reboot in "touch droid setup"). Curiously I flashed my hero 2.0.5 (1.5) and had no problems...
Tried booting the latest RA recovery trough fast-boot and it worked fine the first two times I did it (scrolled down the options for like 10 minutes and it didn't freeze). After that it did not work and got the freezes+rebooting problem back again. Tried ADB, Flash-rec and flashed the recovery but got the freeze+reboot problem once again. Re-checked the version and MD5 and they where all correct.
Why does this happen? Any clues?
Thanks for your help!
I'm kind of lost here...Could it be a radio or SPL problem? Should I re-flash/update it? I never had problems with the stock ROM so this situation is really odd...
Can anyone help?
Thanks in advance!
strange... try some random methods here lol (I don't know if they'll work though but it can't hurt)
First, try flashing an ENG SPL, see if that makes a diff
If that fails, try flashing a whole new ROM/RADIO/SPL
for example: Since you're a 32A user, I believe you can flash the 6.35.x radio and the 1.76.2007 SPL and then use the hero recovery. Test out a rom on the new radio for like a day and try out the recovery. See if that freezes! (This doesn't really accomplish much though because even if it doesn't freeze, i think you'll wanna go back to the old radio to try out other roms lol. You risk bricking your phone if you don't understand this stuff so don't do it if that's the case)
But anyways, I'm a bit confused. What rom are u using?
noroses said:
Hi,
Tried cm-recovery-1.4-32A and it seems to work fine but when I flash a ROM (1.6) I have similar problems with the ROM (freeze+reboot in "touch droid setup"). Curiously I flashed my hero 2.0.5 (1.5) and had no problems...
Click to expand...
Click to collapse
So you can use the recovery fine, until you flash a rom? So when you flash a rom, your recovery beings to freeze. But when you flash a different rom, your recovery works fine? Weird. Sounds like a problem when you're flashing a rom...
I have no idea dude but what I would do if I was in your situation:
1) Flash ENG SPL, something like 1.33.0010 (double check everything, i dont like advising people to play with their spl/radio so dont just take my word)
2) load up recovery and give it a try! if all that fails...
3) I'd backup your phone via nandroid in recovery (i pray that it doesn't freeze lol)
4) Wipe wipe wipe
5) Go into fastboot, fastboot erase system -w and then try another rom! And if the rom is good, then go back to your old one. Try to find out what the prob is.
It appears that you're able to flash roms still even with your recovery freezing (so weird) so I dunno. Just give it a try I guess lol
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Hi,
strange... try some random methods here lol (I don't know if they'll work though but it can't hurt)
First, try flashing an ENG SPL, see if that makes a diff
Click to expand...
Click to collapse
Will try this. Can I flash the SPL trough the recovery?
If that fails, try flashing a whole new ROM/RADIO/SPL
for example: Since you're a 32A user, I believe you can flash the 6.35.x radio and the 1.76.2007 SPL and then use the hero recovery. Test out a rom on the new radio for like a day and try out the recovery. See if that freezes! (This doesn't really accomplish much though because even if it doesn't freeze, i think you'll wanna go back to the old radio to try out other roms lol. You risk bricking your phone if you don't understand this stuff so don't do it if that's the case)
Click to expand...
Click to collapse
Will have to check and recheck this complex process.
But anyways, I'm a bit confused. What rom are u using?
Click to expand...
Click to collapse
Now I'm using stock 1.5. I tried cyanogen, superD and other 1.6 Roms and they all freezed at the android setup process. Used myhero for a week with no problems whatsoever. Since I have a nandroid backup done with CM's recovery I restore everything back as it was.
So you can use the recovery fine, until you flash a rom? So when you flash a rom, your recovery beings to freeze. But when you flash a different rom, your recovery works fine? Weird. Sounds like a problem when you're flashing a rom...
Click to expand...
Click to collapse
The Amon_Ra recovery freezes every time. It doesn't give me enough time to do anything...Now I'm using CM's recovery and I have no freezing problems while in recovery mode. The problem is after I flash a Rom and reboot. The ROM experiences freezing problems (just like the Amon_Ra's recovery).
Thank you for your answer and suggestions!
digitaljeff said:
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Click to expand...
Click to collapse
Hi,
Thanks for your answer.
I have never tried with the phone plugged into a socket but did it with the phone running on battery and connected via usb to the computer. Should it make a difference?
Could it be a hardware problem? I never had problems with the stock ROM or with the myhero ROM...
it could be hardware...
if you want to flash to new radio and spl please follow this guide to the T or else you will get a brick, you cannot flash radio and spl via recovery.
so...
follow this guide and all will be good... must have adb ....
http://forum.xda-developers.com/showthread.php?t=605239
digitaljeff said:
it could be hardware...
if you want to flash to new radio and spl please follow this guide to the T or else you will get a brick, you cannot flash radio and spl via recovery.
so...
follow this guide and all will be good... must have adb ....
http://forum.xda-developers.com/showthread.php?t=605239
Click to expand...
Click to collapse
Checked that guide but I'm unsure about this part:
If you do not have an Engineering SPL, download 1.33.2010 and flash through recovery before starting this procedure. Flash the SPL update.zip like any other update.zip file.
Click to expand...
Click to collapse
This part I can do within the recovery to enable flashing via fast-boot right?
yup you can flash the eng spl via recovery ... i should have been more specific and said you cant flash new radio and spl via recovery
for the new radio,spl and recovery you do through fastboot
good luck
digitaljeff said:
yup you can flash the eng spl via recovery ... i should have been more specific and said you cant flash new radio and spl via recovery
for the new radio,spl and recovery you do through fastboot
good luck
Click to expand...
Click to collapse
Will try that tomorrow.
Thanks for your help!
digitaljeff said:
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Click to expand...
Click to collapse
Hi again,
Still didn't mess with SPL and Radio. I'm still afraid I'll brick the phone..However yesterday tried a few simple things like using another sd card or entering recovery while plugged in. These two things seem to influence the behavior of the latest Amon_RA recovery but don't solve my problem completely. Example: When I enter recovery using the original SD card (2gb) the recovery would freeze within 20 secs max. Using another SD card (128mb) most of the times it would take longer to freeze (4 or 5 minutes). Sometimes it would not freeze at all. Although this seemed to influence what happened it wasn't constant and could not find a pattern. The same with the phone plugged into computer. Sometimes it helped. One thing is certain: with the original SD card and unplugged from the computer the recovery freezes within 20 secs every single time.
With the CM 1.4 recovery never had any freeze problems. It seems to work great while in recovery mode. The problem is after a flash a ROM I have freeze problems with the ROM itself (tried different ROM's, CM, SuperD, etc and got the same freeze problem). The only Rom that worked fine was myhero 2.0.5.
This is a very strange situation and I'm starting to think that this could be hardware..
Would that be a SD card problem?
try using another SD card and see if the problem still occurs
I am having exactly the same problem, did you ever find a solution?
Went from a fully updated magic 32A (1.76.0009H) now i'm at 1.76.0008
UPDATE: I just found that the hero recovery works (I would post link but xda doesn't allow new users to do that) however it may still be necessary to downgrade radio and spl
I had also same problem. My device is Magic 32A radio 6.35. Solution was to reflash recovery-RA-hero-v1.6.2.img.