Ahhhh...sorry, had to get that out.
Okay, I am trying to upgrade to farias WM6 rom but it has been frozen at 89% for like 15 mins. The phone says 89% but the computer says 90%. Am i screwed?
BTW. Cingular 8125, cid unlocked and everything, have successfully upgraded before
Hi!
I have the same problem before. Try it again for a couple time.
If not, I can fix for you.
Thx, I got it fixed. It was as simple as resetting the device and reflashing the tmobile rom. IDN WTF happened, but it appears to have re-CID-locked my phone. Wacky stuff, I tell ya, wacky stuff, .
Related
Hi guys!
Tried to flash the phone with WM6 rom via RUU - didnt work, so i took a ShellTool and tried with this one - and now its the best part:
its teeling it can take more than 15mins but i took more than 1 hour - nothing happened, so i disconnected the phone a hard reset it.
OMG its telling OS 4.0.0.0 and wont boot so i took MrClean 2.24 rom pout the phone in bootloader mode with camera+reset and succesfully flashed it to MrClean.(now i think Im a god)
but after succesfull booting it satrted customizing and reset itself... from now on its copletely dead, no response
do you guys have had something like this or maybe some of you know what happened
My device is G4
thx in advace, cheers
gutaker said:
Hi guys!
Tried to flash the phone with WM6 rom via RUU - didnt work, so i took a ShellTool and tried with this one - and now its the best part:
its teeling it can take more than 15mins but i took more than 1 hour - nothing happened, so i disconnected the phone a hard reset it.
OMG its telling OS 4.0.0.0 and wont boot so i took MrClean 2.24 rom pout the phone in bootloader mode with camera+reset and succesfully flashed it to MrClean.(now i think Im a god)
but after succesfull booting it satrted customizing and reset itself... from now on its copletely dead, no response
do you guys have had something like this or maybe some of you know what happened
My device is G4
thx in advace, cheers
Click to expand...
Click to collapse
Is the phone CID unlocked?
Did you use an RUU from same provider?
If none of these answers is affirmative then you better forget that phone. Only recovering via JTAG (requires tools, knowledge (which you can't find here) and skills) or by getting a new board.
Last chance may be a flat battery; try a new one or charge that in another phone.
cheers
Suprising that a RUU didn't brick your phone (or probably it did).
Try charging the battery?
thx for replies guys
no my phone is not cid unlocked and as far as i know none get cid unlocked g4
i used ruu 2.5.2 from xda ftp, so as you said probably my phone is bricked...
thank god (or someone else) there are friends of mine owning same phone so i can try with other batteries
the strange thing is that not ruu bricked it, i think the post flash customization is faullty...
will keep you up to date
just to inform you:
after few days (weeks) of laying inactively on my desk i managed to try once again to resurrect my brick...
assuming the battery is empty i connected my WIZ to a charger and surprise! it lighted the red led for about a second... now i'll wait a few hours and see whats gonna happen
btw: anyone of you guys had something like that in the past?
First off, anyone on this forum who has contributed anything, I am have the deepest respect for, and my favorites will get donations as soon as I have money. Ok enough a$$ kissing.
So here is my problem:
I flashed it's right's TNT 6.1 19919 after hardspling. After many problems, like pseudo-hard resetting (turning off, losing all but 6% battery, and changing the date back to what it was originally i.e. 1/27/06) while in a phone call and doing the same while using the wifi, i hard reset and still the same problems occurred. so I undid the hardspl, so now i am back to 2.25.001 in the bootloader but when i connect it to the computer (winxp) to flash the original rom (cingular 2.25) it freezes at 91%. If anyone has had this problem occur or knows the solution as to get ANY rom back on it, IT would be greatly appreciated.
Also after doing some reading I tried to flash wizard love 2.26 to it and that freezes at about 50-60%. so I am stuck and it is really annoying.
Full 8 hour charge, restart computer, different usb port. Same happens: Error 302 Update Error
Hum... maybe when you reCID locked it, you put a CID that's not for that official ROM you're trying to flash. The misbehavior of the phone is due to the ROM you had, not the CID Unlock. If I'm not mistaken, you can hardSPL it again, from bootloader. Then you can try and flash any other ROM you wish. Give my ROM (WM5SE rev5 - if your phone can handle 240MHz - or rev4) a go, after you have CID Unlocked your phone.
My phone can take up to 273 but, all the roms i flashed were g4 safe.... because the ipl spl never changed and i checked them in shell tool . it gives me a update error 302 which wizard love documentation says that the "phone needs a new rom code" which implies that it needs to be taken to cingular, and i dont think i can lie that well. how would one "accidentally" put their phone into bootloader?
theblackhandx said:
First off, anyone on this forum who has contributed anything, I am have the deepest respect for, and my favorites will get donations as soon as I have money. Ok enough a$$ kissing.
So here is my problem:
I flashed it's right's TNT 6.1 19919 after hardspling. After many problems, like pseudo-hard resetting (turning off, losing all but 6% battery, and changing the date back to what it was originally i.e. 1/27/06) while in a phone call and doing the same while using the wifi, i hard reset and still the same problems occurred. so I undid the hardspl, so now i am back to 2.25.001 in the bootloader but when i connect it to the computer (winxp) to flash the original rom (cingular 2.25) it freezes at 91%. If anyone has had this problem occur or knows the solution as to get ANY rom back on it, IT would be greatly appreciated.
Also after doing some reading I tried to flash wizard love 2.26 to it and that freezes at about 50-60%. so I am stuck and it is really annoying.
Full 8 hour charge, restart computer, different usb port. Same happens: Error 302 Update Error
Click to expand...
Click to collapse
You have posted present IPL/SPL 2.25.001,is it 2.25.001 or .0001 ?
As you removed 'HardSPL',did you reflash the appropriate IPL/SPL regarding your phones official bootloader IPL/SPL...?
You shud do the 'HardSPL' again and either do the removal of HardSPL again correctly as instructed in the sticky ' How to remove HardSPL' or Flash any other Rom to recover.
Cheers!
no it was 2.25.001 just a typo. i think i will try these suggestions when i get home and i will post my findings.
I've got a weird one. Yesterday, my phone was running fine (I've had Dutty's rom on it for about 4months), I lost sound and needed a reboot. I rebooted and immediately got the RGBW bootloader screen. Successive reboots gave me this. I removed my flash card and tried again - was able to get in the O.S. but I still had no sound, so I rebooted again. Now I can't seem to get past the bootloader.
I'm probably going to try a reflash of the ROM, but I'm curious if there is another option since I'd rather not lose my data.
Any thoughts?
--Edit--
Bootloader screen says:
"KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8"
Bottom says: "Serial"
dude i am sorry to inform you but without an os back up is impossible
*just a thought - try removing SC Card and Sim Card and Remove Battery for some time then put everything back and try.. but most likely.. dont put lots of hope on this..
KyleK29 said:
I've got a weird one. Yesterday, my phone was running fine (I've had Dutty's rom on it for about 4months), I lost sound and needed a reboot. I rebooted and immediately got the RGBW bootloader screen. Successive reboots gave me this. I removed my flash card and tried again - was able to get in the O.S. but I still had no sound, so I rebooted again. Now I can't seem to get past the bootloader.
I'm probably going to try a reflash of the ROM, but I'm curious if there is another option since I'd rather not lose my data.
Any thoughts?
--Edit--
Bootloader screen says:
"KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8"
Bottom says: "Serial"
Click to expand...
Click to collapse
jahrami said:
dude i am sorry to inform you but without an os back up is impossible
*just a thought - try removing SC Card and Sim Card and Remove Battery for some time then put everything back and try.. but most likely.. dont put lots of hope on this..
Click to expand...
Click to collapse
Well, it's not a total loss. I have a backup of my settings from about 3 months ago and all my PIM data from 2 nights ago. I was just hoping to be able to recover most of it.
Thanks for the idea though, no luck. Here's hoping the new flash will work!
So I added the newest version of Dutty's - phone took it fine. I installed some apps, rebooted multiple times, worked for like 30minutes. Rebooted after installing one of the apps asked me to, and BLAM .. bootloader.
Would it be reasonable to assume that the ROM in this thing might be hosed?
Interesting I had the EXACT same issue yesterday with a the Default ATT ROM.. I was going to try Duttys since Its already wiped
Ransom342 said:
Interesting I had the EXACT same issue yesterday with a the Default ATT ROM.. I was going to try Duttys since Its already wiped
Click to expand...
Click to collapse
Yeah, mine seems to be fubar'd. I tried flashing Dutty's ROM again, it took the flash, rebooted, and immediately gave me the bootloader again with a blank image.
*edit*
Tried again with a different ROM. It got to the loading screen for the OS, as soon as I rebooted it went back to the bootloader with a blank OS.
Looks like my ROM is fubared. I think my warranty is up, or coming up very soon. Does HardSPL void it? Because I'd assume that is the only thing they can tell was done.
of course hard spl will void ur warranty but if u can revert to orgininal spl
http://forum.xda-developers.com/showthread.php?t=335568
KyleK29 said:
Does HardSPL void it? Because I'd assume that is the only thing they can tell was done.
Click to expand...
Click to collapse
Same issue - Semi Fix
Hi Kyle,
I started having the same exact problem three weeks ago (it is now Sep.18.2008). I've got no sound coming from my phone, and when I reboot I get the bootloader screen.
my FIX: Plug the phone into it's usb cable, and have it plugged into a source (computer, power jack, etc).
When I reset my phone with it plugged into the usb cable, it finds the rom and loads up perfectly. But when I reset without it, I get the bootloader. I still have not figured out why it is doing this. CAVEAT: this only works with my usb cable plugged into the power outlet of MY CAR. I know...it's weird...but that's what's working for me. When plugged into the computer I still only get the bootloader - it works in the car only. But I suggest you try your car, computer, and a wall outlet if you have one for usb and see what works for you. I find that I rarely reset my phone anyway, but it's just annoying when I do.
I hope this message hasn't found you too late :S Cheers
May anyone can help me ?
Kaiser 100 (TILT 8925) during Flashing, the battery was discharged. Now it does not join, the green light diode only burns at power ON attempt.
The computer defines it on USB as Flash device, but the driver from ActiveSynch do not approach.
How to restore it ?
What buttons for input in Flash mode (tricolor) ?
BR !
I tried to upgrade my 8125 using Shelltool earlier this week. I used the tool successfully before and so I was assuming that things would just go well.
Unfortunately, I ended up being stuck on the bootscreen. I can also still go into Bootloader mode and so I figured all I need to do is to download the Wizard Love ROM, go into Bootloader mode and apply the ROM to restore an older version. Well, for some reason the RUU utility keeps telling me about a communication issue even though I already disabled USB in Active Sync and I also killed the program using Task Manager...
What am I missing here? I am hoping that someone can enlighten me...
Thanks,
Jens
For some reason I was finally able to flash my 8125 with the Wizard Love ROM this morning. Flash completed and I was back to an old working ROM.
Unfortunately, when I flashed it with the latest CR86 it flashed fine, but then I am stuck on the Bootloader screen. Already tried it twice and just running it a third time, but I am puzzled...
Any help?
Thanks,
Jens
jstraten said:
For some reason I was finally able to flash my 8125 with the Wizard Love ROM this morning. Flash completed and I was back to an old working ROM.
Unfortunately, when I flashed it with the latest CR86 it flashed fine, but then I am stuck on the Bootloader screen. Already tried it twice and just running it a third time, but I am puzzled...
Any help?
Thanks,
Jens
Click to expand...
Click to collapse
its on its last flashes my friend(or maybe just tire of custom roms)
but just before mine died, it would do that, until i was stuck on the bootloader and the screen would just die, i would have to leave it off then turn on but the same, after that i just left it alone
i could not flash anything on it and i could not see it suffer anymore
i still have it but dont have time to bring it back to life, at least it blinks at me
That's what I was worried about...
Strange thing is I probably only flashed it about 10 times... Very frustrating!
Thanks for your reply!
Hmmm, I just tried the old Wizard Love ROM again and it worked right away.
What am I missing here? I am trying to get to the new CR85 6.5 ROM, but I always end up being stuck on the bootscreen loader. I mean it shows me the HTC screen, but then it goes straight to the bootscreen...
Any suggestions?
I am back in business!
It turned out that flashing back to an older ROM disabled my HardSPL. I guess a case of user error on my end...
Anyhow, I also experienced the fading display mentioned above and I think that's just a sign of a weakening battery. It seems that the phone doesn't charge fast enough over USB in Bootloader mode.
So, if you run into the same problems like me:
- Charge your phone using the charger when you are stuck in Bootloader mode for extended amount of times!!!
- Flash an old provider ROM or Wizard Love ROM
- Re-apply HardSPL if needed
- Upgrade to a newer ROM
Cheers,
Jens
Hello,
I don't know what happened but the other day something really bad happened.
After unlocking my HTC HD7 really well (see here), my girlfriend also got he same phone that came with the same SPL and everything,
Went throught RSPL and HSPL fine, but when attempting to write a custom rom (latest from ansar, like I did to mine), at 5-6% throwed a write to flash error [226], and the only way to get out was getting out the battery
I tried a few more times without any luck, always stuck at 6% on the laptop and 5% on the phone, until once when I took the battery out, the phone didn't start again, no response on anything, battery, power plugin, button combination ...
What could go so wrong? I thougth that when having done RSPL and HSPL, installing ROMS couldn't brick the phone
I can change the phone once, but now I'm really scared even updating mine in the future
What does make the [226] errors? I searched a lot but found nothing, some people says the radio is to high? some the drivers
And what does going the phone from working in bootloader to brick? Maybe u have to wait some time before taking off battery after the write error [226] to make sure?
if you freshly dld the rom i suggest you to reload it from internet, then do a defrag to have your files cleaner than possible...hope you didn't do wrong with H/RSPL it could be harmful