I just upgraded to t-mobile 1.60... the upgrade went well and then it drove me nuts because
I got a no service error.
So I thought it was locked and followed the xda2unlock procedure, hard-reset into
bootloader mode (power+reset+action, make sure you sync all your files first) just to
tell me that my phone was already unlocked.
then when I finally reset my phone... the upgrade finished updating my phone and now it
works well.
Related
Hi guys,
Upgraded to 1.16 radio - (Tmobile UK ROM)
This kept 'hanging' so upgraded to 1.20 - this failed
Left with NO GSM - followed steps as requested set pass etc.
Still wouldn't upgrade
Tried to put latest ROM on (South african?) this FAILED but installed boot load 1.09 - argh!
BOUGHT (£20) the imei-check to downgrade - this WONT WORK - keep failing!!
Please help - stuck now - phone boots - but has NO GSM all the time...
Please help!!
please attach a usb monitor capture of a full rom upgrade until it fails. Probably will be "cid not allow (255)", but just to make sure.
No T-MOB001 rom exists yet
Did that - thats exactly where it failed!
Is it stuffed? :-(
I don't know, never had one of those with "NO GSM" error on my hands.
Probably as radio is screwed CID is corrupted and you'll not be able to flash a ROM even with your original CID. I think for you the best would be to send it to service centre.
Yeh, thought it may be stuffed! FUnny thing is, when I do a hard reset, it doesn't have the NO GSM, it reports 1.16.0.0, it's as if the T-Mobile customs reset it all. Is there any way of stopping the customs?
Regardless, I have had the phone < a month so I'm ringing customer services to see what they can do - maybe not admit I've tried to upgrade it just yet!!!
roger said:
Is there any way of stopping the customs?
Click to expand...
Click to collapse
I guess by "customs" you mean the Extended Rom, if yes, just do a soft reset before it installs (3 seconds). But I don't think it would do any difference...
Ok- update to problem,
Managed to downgrade from 1.09 to 1.04 of bootloader usining IMEI-CHECK.
Did HARD RESET and plugged in hermes when "press screen to continue" came up (just booted) linked to ACTIVESYNC then ran the software IMEI-CHECK sent me, this connected to hermes and asked for .unl file from imei-check. This 'downgraded' to 1.04 of bootloader.
Then managed to install a 1.13 radio rom - hermes still kept hanging -but I could use phone a little (managed to make 2 calls before a lock up). I was going to re-install another full rom upgrade - I think this may have sorted it, but by this time I had rung T-Mobile support in UK and they agreed to replace unit (I pretended it had gone wrong 'all on its own' hope Karma doesn't catch up with me!)
I THINK I would have managed to sort this using the solution from IMEI-CHECK and this forum by reapplying another full ROM upgrade. So thanks to everyone for their help! Hope this is of some use to someone!
I flashed my locked g4 with faria's shelltool that installed wm6, my phone now wont make it past the ipl/spl screen. at this point i found the sd card backup method and unlocked my g4 through the website. when running through this method i find that the utility is unable to copy the extrom.. it seems to be the last hitch, my phone as of now is a brick and i am hoping for that to change. any help please?
Im not so sure its a brick, I think I read in other posts that if it makes it to the IPL/SPL screen there is still hope.. if it was a brick, I dont think it would do ANYTHING.
You might want to look into that though, I may be wrong, but I am pretty certain there is hope for u.
Hi there.
Turn off the phone, remove battery if necessary. Then press and hold camera button and then press the power button, your phone will enter in boot mode, now flash with the operator´s rom.
Cheers
sorry for the delayed response here. the phone (even in boot mode ) will not be found by active sync so i cannot get the thing to flash with the t-mo rom. since this issue i contacted customer care and am having the phone replaced under warranty.
the phone will NOT be recognized by activesync.. you just need to start the ROM update and it will go along fine. you need the original carrier ROM, and unless your device is CID unlocked, you need to use ShellTool to flash the WM6 ROM. good luck
-Nstefanelli-
I've had my 8525 now since June 2007. I'm on my third 8525 because it appears after a few monthof use either the soft keys stop working or the touch pad. Well I just received my latest new 8525 in the mail and tried to upgrade the software yesterday but none of them want to work. They get to 1% on the upgrading screen and then the phone restarts itself and the RUU says the file is corrupt, and it says that with all the different versions of Roms i have downloaded. I researched this stuff as much as I could yesterday but a lot of it seems complicated. I see that there is a crack to unlock the CID but that it voids the warranty. What am I doing wrong here, or better yet, what should I do in order to get my phone to upgrade to the Rom that I desire? Thanks and sorry for being such a newbie at this stuff but I havn't had any problems on the 2 other phones i've had before.
You should (MUST) have Hard SPL on your device before Flashing. With HardSPL it tells the device that all RUU's are OK. I guess that's what's happening.
As for breaking the warrenty, well its your choice.
I have a 8125 G4 sim unlocked w lokiwiz and a flashed WMSE5_rev4 with soft spl, well the problem that i have now is that i recentley tried to flash a new wm6 rom without hard spl ( yeah i know stupid) And now i am stuck on tri color boatloader screen no matter if i turn it off or not still goes back to the same thing. and yes the rom that i was flashing was g safe, i think were i messed up is not CID unlocking it with hard spl?when i tried to flash the new rom it went all the way to 100% and then gave error after that. NO activesync connection right now
questions
1- DID I BRICK IT
2- is there a way to recover this device
unlock it again. (CID) i had the same thing on my wiz g4. and no. is not bricked.
ok thank you and i will let u know what happens so i should use hardspl right?
ok thank you and i will let u know what happens so i should use hardspl right?
still lost
Ok this is where im at i have tried to flash other roms, NOTHING. the phone is cycling between charging(when on charger) and bootloader every few seconds then i pull it off and nothing. i cant get hard spl to recognize the phone nor will activesync. i understand that i need to CID unlock the phone but i cant even get that far?
any suggestions? please walk me through it im not stupid but HTC's are a whole new ball game for me. im used to motorolas(by the way they suck!)
thanks in advance
Get the original stock ROM for your Wizard version and flash it to get your OS back, then you can HardSPL or SoftSPL.
p.s. G4 Wizard does not have free solutions to actually "CID unlock". Either HardSPL and SoftSPL are hacks that tricks the RUU to allow flashing, you will still see your device as Locked in WST(Wizard Service Tool).
go to activesycn settings turn OFF allow usb connections and retry
I read it here in another thread after I returned My P4300 to cincinati bell in exactly the same condition you described.
Good Luck
Hey guys,
I just got a brand new Telus P4000, and love the look of this ROM - http://forum.xda-developers.com/showthread.php?t=462827.
I have been trying to figure out for hours how to put this on, and have checked all the FAQs and guides I can find, and am very frustrated, and I am really hoping one of you guys are able to help...
So i updated the firmware from HTC from 5 to 6.1 I believe. I ran nueSPL-2.47 on the phone and believe it installed successfully?
Whenever I try to install a ROM it gets stuck at 0% and then says that an error has occured.
I am probably missing something stupid and small, but and so new to phones and am having a hard time.... Anyone have any insights?
Thanks
your probably not actually unlocked, put it in bootloader (power +camera then soft reset) and read what it says, should say 2.40 olipro somewhere there. if not, re-run the unlocker and make sure you follow all its directions explicitly. alot of people leave out the disconnect and reconect step thinking it's not necesary, when in fact, windows won't load drivers without disconecting first