Database Develop

Recovering from a bad flash...

I was running xelencin's latest custom rom. I have used his previous versions and all was good.
This one hung at 98%. I was just letting it do its thing when out of nowhere, BSOD. So now my phone is just sitting at 98%. I thought there was a forum post here about recovering but I'm not able to find it.
Thanks.

Update: After a soft reset, I am back to the multicolor screen. When I plug it in, it says USB in the bottom left hand corner. Device manager shows a PocketPC USB Sync device as well.
When I perform a hard reset (Comm Button + Voice Dial held, then press soft reset with stylus), I am taken right back to the same multicolor screen.

You're at the bootloader.
This is a Good Thing(tm).
At this point, you should be able to rerun any (assuming you are CID unlocked) any RUU ROM upgrade. Let it do its thing and you'll be good to go.

gamescan said:
You're at the bootloader.
This is a Good Thing(tm).
At this point, you should be able to rerun any (assuming you are CID unlocked) any RUU ROM upgrade. Let it do its thing and you'll be good to go.
Click to expand...
Click to collapse
For those that get stuck here in the future:
I had to extract the installer so as I could get past the CID unlock. I then ran "ROMUpdateUtility_Wizard_NoID.exe" and all went well!

rosewood said:
For those that get stuck here in the future:
I had to extract the installer so as I could get past the CID unlock. I then ran "ROMUpdateUtility_Wizard_NoID.exe" and all went well!
Click to expand...
Click to collapse
Yep, I went thru the exact same thing yesterday when trying to upgrade to 2.24. My PC decided to shutdown (not restart, a complete instant shutdown!) at 8% flashing. I decided to grab the "Mr Clean AKU2.3 ROM" which already had the ROM flash program available separately and then just put in the .nbf file I wanted and it was good to go

if your not cid unlocked, then what? xtract what? to wherehow can i transfer any thing, it seems though the device screen says usb, the avtivesync doesnt detects my phone. n?m, ive got it

What happen when your not CID unlocked? I had removed my hardspl before I tried to again flash a rom. I am stucked with the bootloader now...
Pls help

xpxj said:
What happen when your not CID unlocked? I had removed my hardspl before I tried to again flash a rom. I am stucked with the bootloader now...
Pls help
Click to expand...
Click to collapse
Only Official stock rom or the wizard_love rom will get flashed,no other wm6 rom is possible.

Restore from Bootloader?

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

SE Updater failed to install new rom, what is the best thing to do now?

Hello,
I know you guys got some excellent walkthroughs, roms, programs and threads where you've helped a lot of people out but I could really use some personal feedback. I had hoped to fix my phone using one of the excisting threads but unfortunalty I can't get it to work with those.
My problem is one I've seen more of in here, I used the SE updater and it froze at 53%, I did what the program said, reconnected and it froze again at 12%, and again, again, etc. So I disconnected thinking it might be a bad USB port. But then the updater didn't recognise my phone at all. So I used the mtty program suggested in some of the threads and I got past the red/green/blue screen but now it's stuck at the Sony Ericson logo, as if WM6.1 is gone.
This is what the red/green/blue screen currently states:
KOV110
SPL-0.78.0000
MicroP1-787
MicroP2-707
From what I gather this means I can't flash roms, right? I tried making it a hard-spl but when I use the tool it says it can't connect.
So is there anyway to get a rom on it and bring it back to life?
Thanks inadvance!

Get an original rom from here : http://forum.xda-developers.com/showthread.php?t=475482
copy .nbh file from the package onto your sd card and rename it to : Kovsimg.nbh then bring phone into boot loader via : vol down + power.
It should flash the rom now. i the problem is still present after that you
have to deal with mTTy but first try the flash...
i think you could also bring phone into bootloader without sd card inserted then connect usb cable, display should now print 'USB',and after that start rom update utility.
regards

meska said:
Get an original rom from here : http://forum.xda-developers.com/showthread.php?t=475482
copy .nbh file from the package onto your sd card and rename it to : Kovsimg.nbh then bring phone into boot loader via : vol down + power.
It should flash the rom now. i the problem is still present after that you
have to deal with mTTy but first try the flash...
i think you could also bring phone into bootloader without sd card inserted then connect usb cable, display should now print 'USB',and after that start rom update utility.
regards
Click to expand...
Click to collapse
Thank you for your reply, I will do as you said although I've already tried something similiar to this. I believe the problem was that I couldn't flash roms from my SD since I don't have the hard SLD. But I will try it anyway as soon as I get home.
In the mean time I would love to hear more ideas about how to fix my phone.

Ronnet said:
Thank you for your reply, I will do as you said although I've already tried something similiar to this. I believe the problem was that I couldn't flash roms from my SD since I don't have the hard SLD. But I will try it anyway as soon as I get home.
In the mean time I would love to hear more ideas about how to fix my phone.
Click to expand...
Click to collapse
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.

original roms will still work with original spl... but nevermind =P

laurence0609 said:
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.
Click to expand...
Click to collapse
My phone can still power on in the sense that it shows the Sony Ericson logo or that I can access the three collor screen. But it won't launch WM6.1. I also have a problem with updating to hard DSL. It does recognise my phone because without it connected the program finds nothing and with the phone connected it wants to start updating. It says ''updating from image version: (emply) to image version: 1.00.X1 Ipress next and it opens a progress bar on both my X1 and the PC. But it never goes beyond 0% and then gives me an connection error. I think it has something to do with not being able to get passed the Sony Ericson logo. I mean the hard-DSL program does recognise my mobile but activeSync is never active because my PC doesn't recognise a WinMobile phone (since it wont go past the Sony Ericson screen)

meska said:
original roms will still work with original spl... but nevermind =P
Click to expand...
Click to collapse
Really? That might fix my device then. Could you suggest a rom from the long list? Perhaps one that works on all versions? Because I'm dutch but my mobile has always been in english so I'm not sure what rom version I had. Except that it was identified as an R2 Rom by the Sony updater before it killed my X1...

Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that

Mopral said:
Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that
Click to expand...
Click to collapse
I'm now downloading the initial dutch R1 firmwire, could that one work?

Mopral said:
Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that
Click to expand...
Click to collapse
Alright so I got an R1 original rom (I now realize that the R3's were originals aswell) and it worked! I'm not sure if it was the different rom or the formatting with FAT32 that did but it works again. So I'd like to thank everyone who was kind enough to reply.
The device is incredibly slow now but now I can use the hard-DSL installer, right? DOes anyone have a suggestion for a good rom to use?

laurence0609 said:
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.
Click to expand...
Click to collapse
DON'T hard-spl if you're going to flash a stock ROM. And especially if you're going to use SEUS.
Try flashing the R3A first. The R1s are way slow, as you've seen.

Rebooting on sleep

Hi,
I've recently rooted my phone and moved from WM to Myn's Donut NAND build. I like it a like except for a couple things. The most annoying is that my phone reboots every time it enters sleep mode, either from timing out or from me sending it into sleep manually.
I've reflashed the ROM a number of times with different builds, and even some of the other ROMs. Same problem.
I tried flashing back to one of the custom WM builds and that was even worse, it rebooted soon after coming up to the WM desktop. I never had problems prior to unlocking and doing the initial ROM flash.
It seems odd that I would have picked up a hardware problem right as I did the unlock and first ROM flash. Does anyone have any ideas?
Thanks

what unlocker did you use?

I have the 2.31 CoKE HardSPL unlocker that is referenced in the how-to guides such as the paragraph below. Think something is wrong with the install?
First and foremost, make sure you have unlocked your phone with the "2.31 CoKe" HardSPL. If you have ever flashed a custom Windows ROM from this site or ppcgeeks.com, to your device, then you most likely have already done this. If not, perform the steps HERE first, before continuing.
Click to expand...
Click to collapse

tsrich said:
I have the 2.31 CoKE HardSPL unlocker that is referenced in the how-to guides such as the paragraph below. Think something is wrong with the install?
Click to expand...
Click to collapse
I know that there are vogues that are different than others. That may be the case with yours. Some don't work right with android, some do. I'm not sure if it's something with the unlockr or slightly different hardware. For example, my wifes vogue is a funny one;
I can't flash a new nbh from the SDcard. I have to use the htc flash app, also for a long time she couldn't update her build because the kernel was incompatible. However now, the most recent kernels are fine.
Since unlocking some of the 6.5 builds won't work, they would randomly hard reset. but the 6.1 builds were perfectly fine..

mssmison said:
I know that there are vogues that are different than others. That may be the case with yours. Some don't work right with android, some do. I'm not sure if it's something with the unlockr or slightly different hardware. For example, my wifes vogue is a funny one;
I can't flash a new nbh from the SDcard. I have to use the htc flash app, also for a long time she couldn't update her build because the kernel was incompatible. However now, the most recent kernels are fine.
Since unlocking some of the 6.5 builds won't work, they would randomly hard reset. but the 6.1 builds were perfectly fine..
Click to expand...
Click to collapse
I had that problem where it would reboot on sleep, even in windows mobile, i figured out that it was the unlocker, so i relocked it, then unlocked it again with .31 and that fixed it.

mrono said:
I had that problem where it would reboot on sleep, even in windows mobile, i figured out that it was the unlocker, so i relocked it, then unlocked it again with .31 and that fixed it.
Click to expand...
Click to collapse
I've already unlocked my Sprint Vogue.
Can you please provide URL for "relocking"?
Will need it in the event that it needs servicing.
Thank you...

JM-PDA said:
I've already unlocked my Sprint Vogue.
Can you please provide URL for "relocking"?
Will need it in the event that it needs servicing.
Thank you...
Click to expand...
Click to collapse
just use the unlocker v.40 then flash stock rom, then unlock again with the .31
as for the url, just google vogue unlocker .40

How did you install the .40 unlocker? It uses activesync to connect to the Vogue. Did you have a WM ROM installed first?

tsrich said:
How did you install the .40 unlocker? It uses activesync to connect to the Vogue. Did you have a WM ROM installed first?
Click to expand...
Click to collapse
flash it via sdcard or through bootloader

cp0020 said:
flash it via sdcard or through bootloader
Click to expand...
Click to collapse
Maybe I'm doing it wrong then.
I opened up the vogue_unlocker.exe and extracted all the files to a dir. I changed into that dir and copied the VOGUIMG.NBH file to RUU_signed.nbh. I've had to do that for other ROMs, so I did it just to be safe. I then put the phone in bootloader mode, and connected it via USB. Then I ran the ROMUpdateUtility.exe from that dir.
It wanted to update from image ver ' <blanks>' to image ver ' 1.00.000.0'
It runs through the install, but doesn't seem to update the ROM. The bootloader still shows SPL-0.41.CoKE

I ended up flashing to a custom WM ROM, which let me establish an Activesync connection, so then I could run the full .40 install from windows, which worked.

HTC Tytn ii not booting

My htc which is still default from factory freezes on start up. i have been advised that it needs a firmware upgrade but as i am unable to boot the phone up i am unable to upgrade the firmware. i am lost here i have been searching for hours to find a solution and can;t seem to find one so i thought i would ask you guys. it freezes on the screen smart mobility and doesn;t move from there.

Have you tryed to hard-reset?
To flash the original stock ROM via bootloader? as doesn't need to fully load os to flash.

i have tried to hard reset it now and it wont turn on now.

i got it to boot again after the hard reset but it did the same thing just froze on the smart mobility screen again. i had sent it in to be fixed but they wanted to charge me quite a bit to update the software and since i have 4 months till my contract is up i don;t want to pay it is there anyway i can give it the update whilst it is freezing during boot up

Try flash stock ROM via bootloader.
Camera button hold in press in stylus, stock rom "from wiki" now flash via usb or sd.

would you be able to suggest the best rom for me to use i have wm 6.1 the info it givews me is kais130 spl-3.29.0000 cpld-8 i have never done this before i just want to be sure i get the right one

You will need your carrier ROM as when flash will vendor check since not hard-spl'd.

thankyou so much for the help i was able to locate the correct rom and now my phone is working again you have been a great help

Glad you sorted, happy to help