Related
Hopefully, someone can help me fix my f*ckup...
I attempted to flash the qtek "test" rom to my I-mate K-jam branded wizard. The flash worked, and the customisation from the extnded rom completed.
then the fun began...
the device booted, and hung at the splash screen. I soft reset, and it hung at the same point. I then tried a hard reset, and it still hung...
At this point, I thought "oh well" and tried to flash back the old os.. which wouldn't work, as I couldn't get an activesync connection. so I put the device in bootloader, and flashed the rom. but.. it's now stuck in bootloader. no combination of soft or hard reset will allow it to boot, but I can flash roms.
anyone got any ideas?
thanks!
<edit>
Just a quick update.. flashing button's custom rom image got me out of bootloader, and booting as far as the splash screen again, but showin the old i-mate, not his pint..
I'll keep tinkering, and hoping that someone has a clue what i've screwed up.
</edit>
2 others with same problem
You're not alone...
http://forum.xda-developers.com/viewtopic.php?t=40871
Yeah, I saw
Sadly mine came from ebay, so returning it's going to be hard!
Hopefully, it's fixable.
It looks bad!! I'm afraid
I've given up and hopefully will get a replacement from T-mobile?? Somebody suggested I try running the battery down. I did this and now it won't start at all or even charge - so it's now well and truly dead!!!
I think whatever we have all down is terminal - as you say you can't even run activesync. Hope you didn't pay too much for your ebay wizard?!
I've been trying to get my old extended rom and new Qtek OS on my Wizard (Vario).
But now it gets stuck in the spash screen (ie the one giving the ROM numbers).
I've tried putting the wizard into bootloader mode and I can flash RUU's but when it resets it still gets stuck on the spash screen and won't go any further !!!????
What can I do ??
Please Help
Cheers
John
I should say that I had flashed using button's ROM RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
and this worked fine!
I then copied across my T-mobile Extended ROM and again everything seemed OK.
BUT then I tried to restore my new saved OS ROM using aWizard and this caused a freeze on my Wizard. It was after a hard reset that the wizard stopped at the splash screen.
Now of course I'm limited in my options because Activesync won't work until the Wizard has fully booted up.
I have tried setting the Wizard into bootloader mode and tried several ROM's (RUU Installer ones) but every time the correct splash screen comes up with the new ROM numbers but that is as far as it gets.
I also noticed on hard reset that you get the following message
Format FAT partition
Format failed
it then goes to the splash screen as before.
Are there any other things I can try Or will I have to send it back to T-mobile for a replacement??
(It's only 2 months old and I have re-flashed it with the orginal T-mobile ROM - but still won't go past the splash screen!!)
I live in hope
John
I have this EXACT same problem!
I can reflash any ROM but it will not go past the splash screen. Only difference was I wasn't playing with my extended ROM. I flashed the AKU2 QTEK ROM yesterday and have been fine through several soft resets, etc. This last time I was uninstalling phonealarm and after a soft reset I got a "could not find smswakeup.exe" (or something similar) and it's been stuck ever since! I also get the "Format Failed" message. Can anyone help!?
I think I'm going to have to send it back to T-mobile and hope they give me a replacement. Something is wrong, it doesn't seem to make any difference what ROM I used.
I think I'll reload the T-mobile shipped ROM grom the FTP site and send it back - and claim ignorance that it it suddenlt freezed and now won't boot up! - Bummer!!!
Right I've logged a fault and it will be sent back - let's hope T-mobile can't detect it's been unlocked and had several ROM updates - I suspect they will try a ROM update themselves then give up ???
The worrying thing though is that it IS possible to kill your phone with updates - maybe it was when I used aWizard to try and restore a ROM that did it??? I'll be more carefull next time!!
this has just happened to one of the devices im flashing at the moment.... absolulty f**king raging :evil: :evil:
i wish teher was a solution!!? anyone got any ideas?
activesync wont find it, so aWizard wont work.
i can flash between 3 roms without any problems (1.5.x 1.6.x 2.x) but always hangs on the splash screen. i have flashed back to the default rom that it came installed with it so i could just send it back to o2 (only 2 days old!)
i would rather just get it sorted by myself thoough so if anyone has ANY ideas then please let me know.
thank you!
Good luck! after about 3 days of trying different types of firmware, I gave up and sent it to expansys, for repair. And it looks like they've lost the bloody thing now. :evil:
tonym001 said:
Good luck! after about 3 days of trying different types of firmware, I gave up and sent it to expansys, for repair. And it looks like they've lost the bloody thing now. :evil:
Click to expand...
Click to collapse
yup looks like i might have to give up... ohwell, no worries i will just return it back to O2...
looks like one of our sales guys wont be getting a new phone on tuesday :lol:
same problem here.
tryed to write os with awizzard after changing extended_rom.
kills phone.
format failed..
Tryed different os's from win util - failed
upgraded with sd card methode worked.
in short :
you need a working wizzard to make a os dump on sd card.
Connect to wizzard with usbterm or romupdate.exe or simular.
do a rs2all command to dump os to sd card.
stick this card in broken phone.
hold voice comm button while resetting.
On ask press voice comm button again.
it bow restores the sd backup to phone.
saved mine.....
btw sd card backup can be read ad write by pc with util ntrw.exe .
so if you don't have a working dump i can upload one.
just mail me.
grtx , arnold
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
There is hope
Last week after trying to downgrade to the original Cingular ROM on my 8125 using aWizard I ended up with a device that was close to being a paperweight. At least I thought so until I read and read and finally was able to get it to the bootloader and then plugged in the USB cable and ran the RUU for the new Qtek ROM (2.17). Guess what happened, yeah it worked. To my surprise I had a perfect device after 15 minutes.
For about 3 hours I thought I was a toast. Never will I do that again.
THIS is truly heaven for me !!
I have my O2 XDA MINI S locked on the splash screen .. and i updated some ROMS to it ....BUT IT DOESNT GET THROUGH IT .... please tell me what to do in a little detailed manner .. please so that i can get my phone to work.. there is no warranty on the phone and i stay IN INDIA . SO YOU'LL ARE MY ONLY HOPE .
my email id is - [email protected]
If you have a dump of the O2 XDA MINI S ..please mail it to me
Plese tell me what to do next ? WILL TRULY APPRECIATE HELP
PLEASE SOME ONE ATLEAST MAIL ME the dump of the os SO THAT I CAN TRY THE SD CARD UPGRADING ,.,,, O2 XDA MINI S
Re: There is hope
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.
Thank you so much
my mail : [email protected]
Thanks friend
hellomoto_25 said:
Last week after trying to downgrade to the original Cingular ROM on my 8125 using aWizard I ended up with a device that was close to being a paperweight. At least I thought so until I read and read and finally was able to get it to the bootloader and then plugged in the USB cable and ran the RUU for the new Qtek ROM (2.17). Guess what happened, yeah it worked. To my surprise I had a perfect device after 15 minutes.
For about 3 hours I thought I was a toast. Never will I do that again.
Click to expand...
Click to collapse
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.
Thank you so much
my mail : [email protected]
Thanks friend
odyseus said:
I've been trying to get my old extended rom and new Qtek OS on my Wizard (Vario).
But now it gets stuck in the spash screen (ie the one giving the ROM numbers).
I've tried putting the wizard into bootloader mode and I can flash RUU's but when it resets it still gets stuck on the spash screen and won't go any further !!!????
What can I do ??
Please Help
Cheers
John
Click to expand...
Click to collapse
stuck on o2 screen helppp
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.I see alot of post, so complicated
Thank you so much
my mail : [email protected]
Thanks friend
flexchen said:
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
Click to expand...
Click to collapse
how to use bootloader
could you tell me how to use mentioned bootloader for restoring the images? where can I get the software?
Please help
Hendrick
flexchen said:
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
Click to expand...
Click to collapse
Hi Arnold
My O2 cda mini s get stuck at splash scree, I read your post, still not so understand how to solve it, could you be so kind to write me step by step, and send me some software to solve it. Your help will be so much appreciated.
Hendrick
Email: [email protected]
arnoldl said:
same problem here.
tryed to write os with awizzard after changing extended_rom.
kills phone.
format failed..
Tryed different os's from win util - failed
upgraded with sd card methode worked.
in short :
you need a working wizzard to make a os dump on sd card.
Connect to wizzard with usbterm or romupdate.exe or simular.
do a rs2all command to dump os to sd card.
stick this card in broken phone.
hold voice comm button while resetting.
On ask press voice comm button again.
it bow restores the sd backup to phone.
saved mine.....
btw sd card backup can be read ad write by pc with util ntrw.exe .
so if you don't have a working dump i can upload one.
just mail me.
grtx , arnold
Click to expand...
Click to collapse
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
I need help ppl. I flashed my Touch HD with RUU_Dutty_s_HD_WM6.5_R6_5.2.23007.5.3.0_1.59.709.0_Radio_52.62.25.34_1.14.25.24_Turbo rom . i've been using it for the last one week and yesterday i hard reset my phone and when i tried switching it on again, it got stuck at the 'smart mobility' screen and has been the same ever since. Please help me out with this problem guys. Any help will be much appreciated.
Thanks
If you have already done a hard reset, you will have lost yor info so I would try and do another if that does not work reflash again.Good luck
If you can't get past smart mobility screen and you have tried a couple hard resets, turn off phone by removing battery, go into bootloader and then reflash rom
well i followed instructions..went to bootloader screen and reflashed the rom..its working now..thanks for your help..i think it was a problem with the dutty rom. One thing i must say that most of the ppl who flash the dutty rom face this problem...something to think about eh...anyways i've lost all my data..but my phone is up and running again..thanks guys....
simon_manurulz said:
well i followed instructions..went to bootloader screen and reflashed the rom..its working now..thanks for your help..i think it was a problem with the dutty rom. One thing i must say that most of the ppl who flash the dutty rom face this problem...something to think about eh...anyways i've lost all my data..but my phone is up and running again..thanks guys....
Click to expand...
Click to collapse
IMHO I would have to disagree with you on that. Most people using Duttys roms would not get this issue. I've used all his roms and never experienced this.
Anyway, your problem solved. Thread Closed
Right. I bought this phone (second hand, flashed with shifu 4.2 ROM {I have no clue what this means}) and it worked perfectly. It didn't come with a sim, so I went out and bought two. An O2 and an Orange one. The O2 one had problem's activating, so I placed in the Orange one. The phone somehow screwed up, saying iLockV2.exe is corrupt/could not be found. So, I contacted the seller, he told me to do a hard reset, which I done. The phone worked fine from there.
This afternoon, the phone froze, so I took out the battery and put it back in. The same problem occurred with the iLockV2.exe thing above; so I tried to do another hard reset, it didn't work. After that, I was stuck at the HTC screen where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
.
I then took out the battery again, and the same thing happened. So I took out the battery once more, and when I pushed the power button it wouldn't turn on. So, I took the battery out and left it for about 4 hours, and put it back in, but now, I'm still stuck at the HTC boot screen (same code as above).
What do I do to make my phone work again?
koglaa said:
Right. I bought this phone (second hand, flashed with shifu 4.2 ROM {I have no clue what this means}) and it worked perfectly. It didn't come with a sim, so I went out and bought two. An O2 and an Orange one. The O2 one had problem's activating, so I placed in the Orange one. The phone somehow screwed up, saying iLockV2.exe is corrupt/could not be found. So, I contacted the seller, he told me to do a hard reset, which I done. The phone worked fine from there.
This afternoon, the phone froze, so I took out the battery and put it back in. The same problem occurred with the iLockV2.exe thing above; so I tried to do another hard reset, it didn't work. After that, I was stuck at the HTC screen where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
.
I then took out the battery again, and the same thing happened. So I took out the battery once more, and when I pushed the power button it wouldn't turn on. So, I took the battery out and left it for about 4 hours, and put it back in, but now, I'm still stuck at the HTC boot screen (same code as above).
What do I do to make my phone work again?
Click to expand...
Click to collapse
First of all, stop taking out the battery when the phone is on because that really screws up the files. You are doing more harm than good there.
Try a series of soft resets to try and fix it. If that doesn't work, try a series of hard resets to solve the problem.
If no luck there, go into bootloader ( tri color screen ), hold in power and camera button at same time while doing a soft reset. The try flashing a stock Orange rom ( found in the wiki ) Then re-flash with shifu rom.
Not letting me hard reset, so I'm just going to reflash (Y). I hope I do this right :\
EDIT:
My computer can't read my phone when connected via usb D:
koglaa said:
Not letting me hard reset, so I'm just going to reflash (Y). I hope I do this right :\
EDIT:
My computer can't read my phone when connected via usb D:
Click to expand...
Click to collapse
What does the phone do when you try to hard reset ?
When you put your phone into bootloader what does the screen say . When in bootloader, does the bottom of the screen change from serial to usb when you plug it in to your pc ?
denco7 said:
What does the phone do when you try to hard reset ?
When you put your phone into bootloader what does the screen say . When in bootloader, does the bottom of the screen change from serial to usb when you plug it in to your pc ?
Click to expand...
Click to collapse
The phone just soft reset's when I try to hard reset.
And yes, it does change from serial to usb when I plug it into my computer
Seem's like I was doing the hard reset wrong. Same thing is still happeneing, not getting past the part where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
EDIT:
After 20 or so hard resets, I've moved onto the boot-loader, then it took about 5 minute's to load to the main OS. I think everything is sorted out now. Thanks
omg, this is getting really annoying now. The phone keeps on crashing at random interval's and can only be recovered by hard resetting :\
Well if it keeps happening try a different ROM just make sure you follow F.A.Q for ROM your flashing.
The thing that it's saying is corrupted is S2U2 and to me sounds like it just can't find the .lnk in Windows StartUp.
Flash OEM Rom before the new one and if you have 2GB or smaller SD Card flash using the SD Card method.
stylez said:
Well if it keeps happening try a different ROM just make sure you follow F.A.Q for ROM your flashing.
The thing that it's saying is corrupted is S2U2 and to me sounds like it just can't find the .lnk in Windows StartUp.
Click to expand...
Click to collapse
It happen's when the phone freeze's and I soft reset it :\
koglaa said:
It happen's when the phone freeze's and I soft reset it :\
Click to expand...
Click to collapse
I'd go with what Philux-X says "to which is why i said F.A.Q" try and flash a stock ROM prior to flashing custom so as to clear nand.
The corruption due to stalling sounds pretty normal as the phone does not get to shut down via the usual method.
stylez said:
I'd go with what Philux-X says "to which is why i said F.A.Q" try and flash a stock ROM prior to flashing custom so as to clear nand.
The corruption due to stalling sounds pretty normal as the phone does not get to shut down via the usual method.
Click to expand...
Click to collapse
I'll do that next time it crashes .
Thanks for all your help guys