Its been a while since i last flashed to L26_WM6.1_PROV4_(3.51.502.0_WWE) My_Favorit
I decided to try an new ROM, but any one i try i get an error half was through the process. Error 302. after much playing around, the only ROM that i manage to flash is my old L26 ROM.
I searched for similar issues but nothing came up. does any one have an idea where i may be going wrong? I have Hard SPL 3.28 installed
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.
I've got a fully rooted, fully NAND unlocked evo4g and I've been having a lot of trouble flashing custom roms.
Right now I'm trying to flash Cyanogen 6.0.0 and i'm getting the following error (check the attachment for a pic of the error).
I've googled the problem and all I could draw from my research was that I needed to download a new PCM132.IMG.
Tried that, and I still get the same error message.
What am I doing wrong?
Any help is appreciated...
hi everyone i installed king cobra v1.3 and i had issues with phone app and people getting force closed or giving an error "co.android.htcdialer has stopped".so i thought its a rom problem and cleared everything(factory reset,clear cahe,clear dalvik-cahe,format system) and installed a new rom(clean rom).to my surprise i got the same error.so i switched to stock rom(1.85) after relocking the bootloader and this time the god damn error pops out again.wtf.and btw this only happens in sense based roms because it did not happen to me when i installed cm and aokp roms.
anyone help me sort this issue.this has been asked in so many threads but no reply
keep on getting a message flashed up on my tab2 which reads:
unfortunatly the process android.process.acore has stopped.
any idea what i can do to stop this?
i had a bit of a nightmare last week and had to restore stock firmware but installed 5113 rom onto a 5110 tab,all was running good but i decided to install the right 5110 rom onto it.
all ran well thru odin and it all passed.after rebooting the update ran thru and it started up with the unfortunate messages.
any idea on what i can do to sort this?
ROM is just unstable, switching to another ROM should solve your problems.