I've tried to upgrade my magician to 1.13 but the unit fails. My first attempt done the 1 and 2 stage but failed in stage 3. I reset the phone and tried it again for several times but it fails. The worst is it cannot complete the first stage then error. Any help you could advice me buddies out there... thanks
what do you mean by stage one, stage 2, stage 3?
iirc, there's a list of stufff you have to do to prepare for a 1.13 flash... did you do them? it's in a sticky at the top of the board
Related
This is the problem:
When i try to upgrade to a new rom by the usb procedure, after the first step (radio) i'm getting this error: (img)
If i try with the SD procedure, it will stop at 68% with "download fail"
Any ideas?
thanks
I'm afraid your chip has some damage, last time I heard something simular it had to be repaired by a professional. Stll got warranty? Use it!
regards, M
Are you sure? This is not the first upgrade and the other one had gone.
You can try the previous upgrade again & see what happens. What worries me in your story is that both methods fail. Only thing I can think of to do is using an upgrade which was previously successful. If that fails now, you're device is malfunctioning I'm afraid :-(.
M
Hi!
Can anybody help me?
I was upgrading with faria's roms.
It all went ok until it reached 99%. after waiting for around 5 minute at that point, it sad that there was a communication error with the phone, and i need to do some recovery actions(remove from the usb, remove the batteries) It said that if i can see 3 bars, then everything is ok.I could see it, so i restarted the upgrade utility. But it did not want to do anything. It said to get a newer version of the upgrade utility. and my phone remained in that 3 color state, having 3 messages on it: IPL 2.16 then on the other corner saying RUU, then in a next row SPL 2.16
Can anybody help me to fix this phone?
Thank you in advance
ghola_2 said:
Hi!
Can anybody help me?
I was upgrading with faria's roms.
It all went ok until it reached 99%. after waiting for around 5 minute at that point, it sad that there was a communication error with the phone, and i need to do some recovery actions(remove from the usb, remove the batteries) It said that if i can see 3 bars, then everything is ok.I could see it, so i restarted the upgrade utility. But it did not want to do anything. It said to get a newer version of the upgrade utility. and my phone remained in that 3 color state, having 3 messages on it: IPL 2.16 then on the other corner saying RUU, then in a next row SPL 2.16
Can anybody help me to fix this phone?
Thank you in advance
Click to expand...
Click to collapse
Mine did something similar - PC Blue-screened about half way through the upgrade and left the Wizard at the Bootloader screen. I tried to re-run the upgrade and it said I needed a different version of the upgrade utility. I just re-installed the WM6 MB version and this worked fine, once it was back up and working I re-ran the Faria upgrade and it worked fine.
I think if you just copy the 'nk.nbf' file from Faria's ROM and use the upgrade utility from the MB version it will work.
HTH
Andy
ok.. here are the steps.. its very easy.. i had the samething..
your phone is probably CID locked.. so what you need to do is just download the original tmobile ROM.. and connect the phone and install the original ROM.. You didnt birck the phone because you get the bootloader screen.. which means, you can still save the phone..
anyway.. connect the phone via usb and install after you install the original wm5, download the shelltool from here and follow the instructions.. and install the ROM via shelltool.. Then you should be good to go with the new
wm6.
http://forum.xda-developers.com/showthread.php?t=271043&highlight=CID+unlock
DR.P'S UNLOCKING THREAD worked wonders for me.
BTW, after following Dr. P's instructions and loading Faria's ROM, my MDA took approx. 13-15 minutes at 99% before I hit the glorious 100%. Like a wise person before me said, patience is a virtue. I waited until the 5 minute mark, got up, used the restroom, grabbed an ice cold Pepsi and then waited some more.
Yup, first time disaster. I followed the guide here, installed the necessary Cert_SPCS.cab/EnableRapi.cab files, rebooted, and then started the Shelltool update...only to belatedly notice a notification screen on my 8125 asking if I wanted to run one of the programs.
I said yes, but even though the update completed, my 8125 is stuck at the boot screen.
Worse, I reset the 8125 into boot loader mode and tried to flash back, only to get a 300 error. I tried to use an updated RUU and ROM set, only to get 264 or 274 errors.
Any hope here, or did I just manage to brick my 8125?
Are you trying to flash an offical rom while in bootloader mode?
Yup. Tried to flash the official 8125 ROM from HTC. Tried to flash a number of different ROMs, actually - I always get a 264 or 274 "Communication" error, except for the official ROMs, which gave me a 300 error.
Not looking good here...
this has helped me with bad flashes
http://forum.xda-developers.com/showthread.php?t=298613
Been there, done that. In fact, that was the thread I first read. I've tried to flash to Wizard_love, but I get a 264 error.
From what I've read in the RUU Docs, a 264/274 error is rare, and fatal in this case. It's not looking good...
(On the bright side, the iPhone release has created a flood of used 8125's on eBay )
I did a little searching for you,
http://www.google.com/advanced_search?q=+site:http://forum.xda-developers.com&hl=en&lr=&as_qdr=all
I read some were how to flash a phone that has errors, I couldn't find that post. Maybe someone else here knows of that post You didn't mention is your phone G3 or G4 I did find this post, doesn't look good. I hope someone has a better answer for you, good luck.
http://forum.xda-developers.com/showthread.php?t=304456
Another post I found for you.
http://forum.xda-developers.com/showthread.php?t=294107
Thanks for the links, unfortunately it's still a no-joy situation here.
This is a G4 Cingular 8125 - sorry I forgot to mention that earlier.
ActiveSync was set to allow USB connections, and I've tried using the official RUU update utility from HTC for the Cingular 8125 with the 8125 in Bootloader (3 color) mode - I get an error 274.
I then tried the Wizard_Love version - error 264.
Next, the MB WM6 ROM - error 300.
Finally, in desperation I try the Shelltool app method again, even though I can't copy over the necessary bootloaders. It hangs up mid-flash, as expected.
Can't go forward, can't go back. Looks like I've got myself a brick...sigh...
upd: ahh, it is g4.....
so ignore whats below
it IS NOT brick ,trust me i had exactly same prob while testing cooked ROM - all yyou need is to download chinese rescue ROM, THEN flash it by its RUU, then RUU wLOVE, then flash ..anythin(g3)...and then flash IPLSPL, as it will be unequal, usually.
its unclear, why RUU cant do flash sometimes, but i believe, that you do not have brick( i had same situation 3 times = 14 flashes..;/ but machine is alive !)
of course, you may have same errors with chinese..if connecting, reconnecting etc is not working, then...use any rescue ROM closest to original, old hogs. check your firewall, and remember - SR device before EACH try - oterwise you surely will have 300 error - 1 try for each reset, no more.
chinese rescue ROM(you MUST flash wlove after that 1), or shelltool will lead you to...3bars.;/
http://pda.oleyek.com/ROM/Others/RUU_Prodigy_1070302_103_10703102_CMCC_CHS_Ship.exe
if its not working...maybe that 1..
http://rapidshare.com/files/29657481/RUU_TMobile_US_226102_22610105_022511_WWE_Ship_tmob_rom.exe
maybe other...
wizard love rescue ROM:
http://rapidshare.com/files/8651097/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar
Just a "happy ending" update:
Was just about to buy a new 8125 on eBay, when I gave it another try - hard reset the device twice in a row, then tried again to flash back to the original Cingular 8125 ROM -- it worked!
Then, in a fit of flashing madness, I went ahead and flashed one of Faria's latest WM6 sets -- and it worked as well!
So, not only don't I have brick, I actually got it upgraded. Whew...
pls help for flashing rom
pr0naLd said:
this has helped me with bad flashes
http://forum.xda-developers.com/showthread.php?t=298613
Click to expand...
Click to collapse
I have spent 24 hrs flashing my qtek 9100 sim free - i think it is the g4 as IPL IS 2.17 / SPL 2.17 NO ZEROES THOUGH . IT DOES SYNC BEYOND 99% AND THE HELP WINDOWS COMES OUT - IT GOES BACK TO THE BOOTLOADER SCREEN ( 3 - 4 LINES OF RED BLUE GREEN ). PLS HELP AS I AM DYING TO GET THE WM 6.0 ONTO MY WIZARD. thanks and appreciate.
[email protected]
BOWERS said:
I have spent 24 hrs flashing my qtek 9100 sim free - i think it is the g4 as IPL IS 2.17 / SPL 2.17 NO ZEROES THOUGH . IT DOES SYNC BEYOND 99% AND THE HELP WINDOWS COMES OUT - IT GOES BACK TO THE BOOTLOADER SCREEN ( 3 - 4 LINES OF RED BLUE GREEN ). PLS HELP AS I AM DYING TO GET THE WM 6.0 ONTO MY WIZARD. thanks and appreciate.
[email protected]
Click to expand...
Click to collapse
Kindly confirm its a G3 or G4 before flashing. This will help you out. http://forum.xda-developers.com/showthread.php?t=298613
wizard G4 boot ok but jump to B/L screen
its aliveeee its aliveeeeeeeeee
i've had 2 android phones before, i must've flashed roms 50+ times in the past nevertheless im paranoid enough to always follow procedure by confirming on written step by step instructions. just now with this new evo i bought a couple weeks ago im having problems flashing roms, im positive to be unrevokedly rooted forever with full nand acces. tried cm6.1 got message "cant symlink" "error line 31" process aborted. retried unsuccesfully, redownloaded rom, retried failed again, tried other roms like virus and bakedsnack every attempt unsuccesful with SAME error. of course i performed a nandroid backup which i've been trying to restore since the first failed attempt but though it completes seemingly without problem phone gets stuck on "htc evo 4g" screen. i use amon ra recovery 1.8.0, always careful to have enough juice. have hboot 2.0.2 S-off. help me, pretty please.
ow! I feel good! ta-nana-nana- nana!
hooray! for me and all who are helped by this short thread in the future! our solution is right here, search this within xda:
"[ROOT][GUIDE] HBoot 2.02 S-OFF - Fresh Like Pine Cones Edition"
Im new here so i cant post links, we're concerned only with the :
"PC36IMG_Recovery.zip" that's in the thread.
got this after 6 hours researching all internet. it seems many of our new EVO'S require this custom RA recovery to flash roms or restore nandroids; just rename it to PC36IMG.zip, place it in sdcard, power off, start fastboot, wait a few seconds it will prompt you for installation, press up volume for yes, when its done choose reboot. after that its flashing as usual yipay!
Hi,
I just bought a HTC One S ville - great phone, but wanted to try MIUI.
I got S-OFF, had rooted it using the standard guide and had
clockwork-touch-5.8.3.1 for recovery.
I flashed MIUI but during load, it would hang - the same with Cyanogenmod 10, even though
I followed guides.
I had a nandroid and could revert, but HBOOT i tried "clear storage", and then must trouble started.
Now I couldn't mount SD card in recovery, and I couldn't boot into MIUI.
I followed this thread to gain access to the SD Card:
http://forum.xda-developers.com/showthread.php?t=1630459
But that didn't work since I can't reflash clockwork-touch-5.8.3.1 since I get remote: signature verify fail - maybe because
it's RELOCKED (?) - otherwise I might have been able to mount, butno luck.
As a last resort, I tried RUU, but gets connection error 170 on two PCs running Windows 7 - tried 5-6 times.
So, after 4 hours I'm fairly sad, I have no idea as what to do a part from retrying RUU. I had a Legend once, and it took me 20-30
tries to get RUU working on Windows 7.
Any help would be greatly appreciated since I'm about to give up for now ;(
I quick follow up - I resolved the problem by installing HTC Sync which I didn't have installed...
Hope this can help others.
Regards,
Fred
What hboot and carrier are you on, if not unlocked. Probably running the wrong ruu, or missing the drivers.