Current Setup :
HardSPL (latest, 3.56 I believe)
Radio: 1.65.29.22 (from Niki or Neon, almost positive it was Niki)
Solace v3.1
Decided I wanted to go back to newest radio, attempted to flash to it; hit a snag at about 78%. Progress didn't update for a while, then to 100%. Update app said there was a flash error, and it did not complete correctly. Device restarted, stuck at bootloader. Re-attempted the flash, same result.
Next, I tried flashing AT&T's latest ROM. Stalled at about 76%, message about having a communication error, walked through the apps troubleshooting steps; it tried (and failed) again.
Tried the latest HTC direct ROM, same result.
Tried to flash the latest HTC via MicroSD card, got 20(ish) percent through, the Radio line then went red and said "RSA Failure". Then that whole process died on me as well.
The only way I can get my device back up to run MTTY to remove the RUU flag. When issuing the "task 8" command to format, it instead reboots the phone. The phone will come up normally after that.
Since I got it back up, I have tried flashing once again, and am getting the same result. Am I just stuck here now?
It's not that I don't like this ROM, I'm just wanting to update the radio. Any ideas what else I might be able to try?
Try using the search function next time before you create a new thread.
If you would tryed you could find this post
Yes, thank you...except that I started my thread saying that the proposed solution was exactly what CAUSED the problem to begin with. I tried to flash to the 1.70.x radio, which is where I got the flash write error.
Anyone else?
Now that you can get it up normally, have you tried going to a stock HTC ROM first, then the new ROM, then the radio? Or HTC, radio, new ROM? I'd probably do it the second way. You said you tried flashing stock before getting it up again, and that you tried flashing after getting it back up, but you didn't state what you've tried flashing after getting it back up.
Since I've gotten it back up, I've tried both OEM and radio only. Both have the same result.
Really at a loss now as to what to try next.
Did you try the 3.29Hard2 SPL? I haven't encountered your issue and wish I could be mroe help here. My only thoughts would be to try a different SPL, or perhaps looking into the ForceUSB issue. Best of luck.
Related
Ok, I really have read existing threads related to similar problems, but I am completely stuck on the boot screen (not bootloader screen) with my Tilt.
I flashed Dutty's 6.1 ROM last week and all had been working fine until last night. The phone was stuck with screen lock (screen nor buttons would respond). So, I performed soft reset and it just stopped at 'smart mobility' boot screen. I then performed hard reset, and again it just stopped and hung at 'smart mobility' screen.
This morning I got into the bootloader screen (power + camera + reset) and flashed original ROM (well, new officiall AT&T ROM released last month). Original ROM flashed successfully, but it now hangs on AT&T boot screen. I have tried hardspl, and flashing multiple ROMs, which all complete successfully, but it always hangs at the boot screen.
Thoughts?
what radio are u using?
Well, with Dutty's I was using 1.64.08.21 that came with the ROM... When I flashed to the stock AT&T ROM, I used the radio included with it as well (1.27.14.09).
tmac said:
Well, with Dutty's I was using 1.64.08.21 that came with the ROM... When I flashed to the stock AT&T ROM, I used the radio included with it as well (1.27.14.09).
Click to expand...
Click to collapse
Dutty's didn't come with a radio.
Well, I was using 1.64.08.21.. Right now, I have the stock ROM flashed with 1.27.14.09
I have a similar problem. I flashed alex rom yesturday then I flashed back to OEM to test something then today I flashed back to alex cube rom and it said flash was successful but when I did a hard reset during the "Tap screen to begin" my phone go stuck in the AT&T inital logo. I tried connecting to USB to reflash but USB won't detect the phone. I have hard reset, removed battery, and no avail. Does this mean I bricked my phone?
To clarify, I have been doing these for some time and also had and 8125 previously, so I understand the flashing process. I also understand that there are only certain radios that work with WM 6.1 and 6.0. This doesn't appear to be a radio incompatibility issue. As I mentioned, I was using Dutty's 6.1 ROM just fine for several days before this happened. I had been using Sleuth's 6.1 prior to that.
Tim
You always should re-flash the radio AFTER flashing the ROM. Pt yuor device into boot loader (hold camera, power & reset button). Reflash the Radio. If that doesn't work PM me & I'll walk you thru looking for bad memory blocks.
hchavarria said:
I have a similar problem. I flashed alex rom yesturday then I flashed back to OEM to test something then today I flashed back to alex cube rom and it said flash was successful but when I did a hard reset during the "Tap screen to begin" my phone go stuck in the AT&T inital logo. I tried connecting to USB to reflash but USB won't detect the phone. I have hard reset, removed battery, and no avail. Does this mean I bricked my phone?
Click to expand...
Click to collapse
NO, it does not mean brick. It means you may want to try another USB port, check the activesync connection settings, & possibly reflash using the SD card.
Edit: After looking at your MTTY feedback, & confering with a few of the Gods, I have to unfortunately tell you that your NAND chip appears to be damaged beyond flushing. The blocks can't even be erased, & that's the problem. When you reflash the blocks have previous ROM data still stored & because of the NAND damage they cannot be overwritten. Return under MFG warranty is all you can do. (Believe me, I really hate saying this & even got confirmation from Pof & Jocky) Sorry Guy.
My 30-day return policy date is tomorrow so I went to the AT&T store today and they swapped it out with a new device. They mentioned next time I have to ship it.
Could this have happened because of to much flashing? Or was this possibly an already existing defect?
I got a new one shipped to my overnight. There was obviously something wrong with it, as I tried everything under the sun. Flashed new ROM, then flashed new radio, flashed original ROM, etc. Everything gets stuck on the boot screen. At one point yesterday, I left it at the boot screen for a couple hours and it finally booted up, but then locked up again once it did. Then next time I reset, it got stuck on the boot screen again.
Please tell me you installed hardspl first?
Soft Reset Looping - Dead Kaiser
Hi all,
I have been flashing/testing many roms for a number of years now. I particularly enjoyed Jasjamming in my Tytn I days. Now...
Great work seen by many developers.
When I first got my Kaiser, i tried HardSPL, and had "white screen" issue, I then followed instructions on "white screen" thread....copied cab to kaiser....ran cab from kaiser..........eventually was able to flash to a new/ different ROM
However, I recently flashed my Kaiser and after using it for 6-7 hours after flash, it soft reset itself. It continued to keep soft reseting itself without geting to boot screen. It kept reading "smart mobility" and it would reset, vibrate, reset, vibrate, reset.......
I tried EVERYTHING - remove battery, flash back to original ROM, change radio (bootloader worked in safe mode - holding down camera button), but to no avail.
I then tried MTTY, and no go with this too. I eventually had to give my phone back in to HTC.
The question I ask is what is the cause of this? Is it excessive flashing? Is is HardSPL? Any comments/ suggestions would be welcomed...
Many thanks
P1Tater said:
Please tell me you installed hardspl first?
Click to expand...
Click to collapse
If you are asking me that question, the answer is yes I did run hardspl. As I mentioned, I have been doing this for long enough that I know what I am doing. I also mentioned that I was successfully running Sleuth's 6.1 for a month or two before switching to Dutty's new 6.1. I was only running Dutty's for a few days before all of this happened.
There is definitely something wrong.. if I let it sit long enough, it will eventually boot. It will work for a few minutes, and then lock up again. Once I reset, it sits on the boot screen for a couple hours again. I have flashed several different ROMs and Radios to get different results, but the results are always the same.. It hangs at the boot screen.
I guess you have also tried going to the tri-color screen and re-flashing as well as a HR or MTTY command
tmac said:
If you are asking me that question, the answer is yes I did run hardspl. As I mentioned, I have been doing this for long enough that I know what I am doing. I also mentioned that I was successfully running Sleuth's 6.1 for a month or two before switching to Dutty's new 6.1. I was only running Dutty's for a few days before all of this happened.
There is definitely something wrong.. if I let it sit long enough, it will eventually boot. It will work for a few minutes, and then lock up again. Once I reset, it sits on the boot screen for a couple hours again. I have flashed several different ROMs and Radios to get different results, but the results are always the same.. It hangs at the boot screen.
Click to expand...
Click to collapse
Please don't take offence to my probing, as my questions weren't directly directed to you. All I am saying is that we need to understand what is the actual cause of this problem, or we all will be "flashing in the dark", and fearing that this problem could be imminent every time we flash in the future.
Many thanks.
P1Tater said:
I guess you have also tried going to the tri-color screen and re-flashing as well as a HR or MTTY command
Click to expand...
Click to collapse
P1 - Since I can't get the phone to boot completely (well, except for waiting several hours), the only way that I have been flashing different ROMs is from the tri-color screen. Regardless of what ROM or Radio I try, it still just hangs at the boot screen. The only thing I haven't tried was MTTY.
AvinashDhaniraj said:
Please don't take offence to my probing, as my questions weren't directly directed to you. All I am saying is that we need to understand what is the actual cause of this problem, or we all will be "flashing in the dark", and fearing that this problem could be imminent every time we flash in the future.
Many thanks.
Click to expand...
Click to collapse
I was actually replying to P1, hence the reason I quoted him. So, I don't take offense to anything you said.
Well, I hope your not getting offended to my questions? I am just trying to cover all of the simple fixes first since those have been the majority of the things that fix "Most" people's issues. I suggest getting in touch with GSLeon3. He has a pretty good handle on what goes on in flashing and all of the fixes.
P1Tater said:
Well, I hope your not getting offended to my questions? I am just trying to cover all of the simple fixes first since those have been the majority of the things that fix "Most" people's issues. I suggest getting in touch with GSLeon3. He has a pretty good handle on what goes on in flashing and all of the fixes.
Click to expand...
Click to collapse
Not offended at all... I am appreciative of the suggestions.
Hi,
I followed this guide for rooting and JF'ing my G1: http://www.androidandme.com/2009/05...r-rooting-your-android-g1-to-install-cupcake/
Everything worked fine but I cannot for the life of me get the radio to update.
It's stuck on Baseband: 62.33.20.08H_1.22.12.29
I downloaded the HTC radio update, renamed it to update.zip and followed to install procedure (home+power, alt-s).
I have tried wiping the phone beforehand etc. as well, but doesn't seem to make a difference.
It does not show any errors or anything, and seems to complete successfully, but the baseband never gets updated.
Is there something else I can try?
Thanks
If I were you, my next step would be to reflash jf.
Also, did you install the new radio update before jf 1.5? I heard that was the right way to do it.
I've tried reflashing to 1.0, reflashing radio back to original, then updating radio, updating OS - radio version still stuck on the same :/
is the official radio update signed with testkeys or "official" key?
i got my update package from haykuro's site and it worked fine.
you could also try reflashing the recovery image as suggested in the steps to get root, then update the radio image again. also remember to press home+back and wait till the phone reboots itself.
What's the radio package you're using? (Link/filename)
If it's not http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip, then it's the wrong one.
>>If it's not http://sapphire-port-dream.googlecod..._22_19_26I.zip, then it's the wrong one.
This is the radio package I'm using.
>>you could also try reflashing the recovery image as suggested in the steps >>to get root, then update the radio image again. also remember to press >>home+back and wait till the phone reboots itself.
Have reflashed back to original firmware (removing root and hardspl), then tried RC7->RC8 upgrade (radio is not updated) and then OTA update to Android 1.5.. again the radio isn't updated.
I have also tried keeping the phone rooted, and manually updating to stock android 1.5.. again radio isn't updated..
I'm all out of ideas?!
It's starting to sound like you've got a bad EEPROM to me. Does it go through all the normal steps? It should unpack the update, prompt you for a reboot, show a pic of a chip with an arrow pointing to it, and finally reboot again. No errors reported?
Hi,
Thanks for your response.
You're right - it goes through the entire procedure 'successfully,' i.e. it reports no errors and prompts for reboot, then does another reboot cycle after the 'unpacking' logo.
Just for everyones benefit:
Got the handset replaced - must have been a bad EEPROM as mikedmayer suggested.
I'm glad you were able to do that. What did you tell T-mobile? I can just imagine the blank look on the cust-serv's face when you try to tell them you think it's got a bad EEPROM because when you try to flash the radio it wouldn't take. Either that or them asking you why you're trying to flash your own radio.
Hey Guys,
First off this is a re-post, me old thread was closed, I am sorry for reopening but I am still having this issue. DaveShaw and smokestack76 had posted. Dave thank you for your reply but I have been through the noob flash guide and many many many other threads and it does not resolve my issue.
I'm not new to flashing and roms, I have flashed at least 100 times and have done some cooking. Had the random stuck in bootloader that wouldn't resolve itself today (using 3.29) Loaded kaisdiagsd.nbh and flashed stock att rom. (probably should have gone right for the spl patch but I was frustrated and needed my phone) Boot loader is now v3.65
Flashed fine, reboot, same issue. Phone will now only load the stock 6.1 att rom from the micro sd. kaisdiagsd.nbh is stuck on loading as for all other roms. I can occassionally get the os to load using mtty. From there tried jumpspl and it would not connect via usb at all.
I have tried flashing spl from the sd and yes spl image was KAISIMG.nbh and KAISDIAG.nbh was on there as well. Card is formatted fat32. HardSPL would start, read the file and get stuck on loading.
When in the stock 6.1 os I get the old unrecognized usb device in both xp and vista.
Is there anything else I can do to reflash spl? All i can think of is trying the task 2a, wiping everything and trying to flash from diag but I don't even want to try that route without something solid in place.
The phone is 2 years old, upgrading when the touch pro 2 hits att in aug sept or whenever it is released, but I need my phone.
I have gone through many many many posts. I'm stuck. Any help would be appreciated.
I have the stock 6.1 att rom up right now but I would like to resolve the issue.
__________________
finally finally got the patched version of 3.29 flashed. I will let you guys know how it goes from here. I am on a different computer at work.
Success!
I started from complete scratch and a fresh brain and was able to get everything going.
After I got the os back up i was able to start jumpspl and get it to connect via usb. Then only the force usb on 3.29 patch would work. After that repaired active sync and I was ready to go. Thanks smokestack79 for the late night help last night. I was out of it and frustrated. Seems like she's got a little more life in her after all.
I have an Qtek S100 and according to the imei check its an o2 rom.
After a long time i decided to use my qtek again just for fun and see what i can do with it.
In windows 2003se it keeps giving low battery although its connected to usb, anyway i decided to give it a go and installed wwe05 but totally forgot about the radio rom that needed to be 1.12. (it was 1.13).
So it gave "bad radio" during startup.
I tried to flash it with multiple radio roms, including the original o2 one, but some dont start at all and some keep getting stuck at 45%.
and eventually give error 114, i can flash it back to original rom, but as soon as i want to update the radio, same thing happens.
now it gives "no radio" in wwe05, and after flashing back to 2003se it says "no gsm".
the radio wasn't giving any error/problem before i decided to update the os, so i doubt it's an hardware issue. i checked mutiple threads about 114 radio, but haven't found a sollution yet.
maybe somebody here can help me get my radio back.
You should read this Thread first http://forum.xda-developers.com/showthread.php?t=705702. Maybe there is the Solution.
i tried them all with normal usb flash, they all stop at 45% and give error 114.
Next Idea is here : http://forum.xda-developers.com/showthread.php?t=494635&page=2
Dont use a USB HUb !
k, i charged battery as long as possible, (althought i think its nearly dead) it now shows 100%.
I'm also using a different system now with windows 7,, when trying to flash it doesn't give an error, but after a few seconds its shows "congratulations", but it hasn't done a thing....
i can only try a windows xp in vmware, will try next first.
nvm, tried multiple roms, guess one of them changed my bl, cause its showed version 1.5.0 when its needs to be 1.00 or 1.02, so i tried to update my bootloader with pnewbootloader and version 1.02.nb0 and it resulted in an error ITFlashRom and never came back to the living. no boot no bootloader. paperweight is going in the bin. topic can be closed.
Hi,
Alright, im totally new to this; I'm trying to run Android on my HD2...
So, All guides I found kind of talked about the same things:
1, Flash phone with HSPL3
2. Flash phone with Radio 2.15.50.40
3. Flash magldr v.1.13
4. Download a NAND ROM -- I was first trying with Cope's Cyanogen Rom, kept getting stuck on GO GO GO! (in magldr) after a while I actually got it to work, but couldn't get data to work, the first time I restarted the phone it got stuck again....
Then I flashed official tmobile wm, got rid of magldr, and started all over, but this time I tried flashing MDJ's Cyanogen Rom, however after resolving several previous issues i got stuck on GO GO GO! again...
also, I have tried with both magldr v 1.11 and 1.13
-------------------
Is there something wrong with the previous steps I took? Any suggestions?
There is another thing that was always wrong with my phone which might be causing this problem; ever since I got it it would sometimes get stuck on the first purple "stay together" screen and not want to move... Even after I restart the screen would persist, and the only solution was to let it 'chill' for a while before attempting to turn on again...[It got stuck even when I flashed the wm to get rid of mangldr]
So any suggestions on how could I get Android running ???
Thanks
Never mind....
It seems to have fixed itself!!! THIS IS GREAT!!! Skyfire, one bus away!!!!
Thanks to all for this awsome forum and for the great roms!!!!
xzpx said:
Hi,
Alright, im totally new to this; I'm trying to run Android on my HD2...
So, All guides I found kind of talked about the same things:
1, Flash phone with HSPL3
2. Flash phone with Radio 2.15.50.40
3. Flash magldr v.1.13
4. Download a NAND ROM -- I was first trying with Cope's Cyanogen Rom, kept getting stuck on GO GO GO! (in magldr) after a while I actually got it to work, but couldn't get data to work, the first time I restarted the phone it got stuck again....
Then I flashed official tmobile wm, got rid of magldr, and started all over, but this time I tried flashing MDJ's Cyanogen Rom, however after resolving several previous issues i got stuck on GO GO GO! again...
also, I have tried with both magldr v 1.11 and 1.13
-------------------
Is there something wrong with the previous steps I took? Any suggestions?
There is another thing that was always wrong with my phone which might be causing this problem; ever since I got it it would sometimes get stuck on the first purple "stay together" screen and not want to move... Even after I restart the screen would persist, and the only solution was to let it 'chill' for a while before attempting to turn on again...[It got stuck even when I flashed the wm to get rid of mangldr]
So any suggestions on how could I get Android running ???
Thanks
Click to expand...
Click to collapse
Hi, Can you please tell me how do you fix your data to work? On my HD2 everthing iworks fine except data using phone connection ( Data works fine on wifi). Please let me know how to fix this or send me a link for your android ROM. I am using Flash phone with HSPL2.08
2. Flash magldr v.1.13. Anroid version 2.2. I dont know the radio version i am using.
Thanks in advance. Mathew