Related
Maybe some of you are already aware of this procedure, maybe not.
Anyway, it worked for me and I decided to share how to do it. Simple.
This procedure should only be used in case you really need enter into a bootloader mode and all other ways to do it has failed! Hold Camera button is one of these I am mentioning.
My Wizard was almost bricked at that time and after I speak with an I-mate technical guy, I got the following:
1. Make sure your i-mate™ K-JAM is not Connected to the PC and remove the dummy card or SD/MMC card
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. Reconnect your i-mate K-JAM to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t use the IrDA or Bluetooth for the Upgrade)
4. Run the Upgrade again and it will work fine without any problems.
While upgrading, the ActiveSync program will not go on, however the upgrade is running.
Hope it helps!
this realy worked for my (ex)bricked dutch tmobile mda vario !!!!
tip: REALY make shure that there is no wcescomm.exe running all the time and realy remove the sd card else is nogo
btw: my wizard is CID locked! and works like a charm
Thanks buddy!
I'm happy that worked for ya!
Take care!
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Hi!
Have you already flashed your device once?
Which ipl/spl do you have?
I had problems over 1.05 ROM in the beggining.
If you stuck on bootloader mode, that's a good signal your device is not bricked.
I'd recommend you to disable activesync as you did and reflash it again! Check also if your device is CID unlocked! Search for a thread in the xda developers root.
Try to upgrade to ipl/spl 2.26 first and later to others you want.
Regarding the old file error...can be related to a missing file called enterbootloader.exe.
Hope it works for ya!
Take care
Ironman273 said:
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Click to expand...
Click to collapse
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Sounds great to hear that!
I had play around with pdaviet3, underground and another ROM just today without any problems at all. I don't think that this is the case. Now you get your device back to normal, try to reflash it again. Hope it works this time!
BTW,...São Paulo is a nice city. Thanks! Let me know if you decide to come here!
Take care
Ironman273 said:
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
Click to expand...
Click to collapse
It seems you got the idea!
You did the right thing! Sometimes, use the official ROM can solve many issues out there!
Keep walking!
enlite_de said:
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Click to expand...
Click to collapse
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
In my opinion this thread is so helpful to people who brick their device, it should go "sticky". Mods anything you can do about it?
Thanks buddy! I really appreciate!
We survive here over tips like that!
jt_armstrong said:
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
Click to expand...
Click to collapse
Help me similar problem
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Hi there!
It seems that you just need to enter into the bootloader mode and reflash it again!
I had similar problems and more during my brick "false" stage!
So, just try to follow my steps here and you should be fine! Once you get into bootloader mode, just use any ROM out there to reflash.
Good [email protected]
thaiphong said:
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Click to expand...
Click to collapse
I was about to start a EMERGENCY HELP thread, but I *think* this is the right place instead.
The "touch" of my screen went dead today. It got progressively worse over a few hours, starting with difficulty in using the phone dialer, then random incorrect stuff getting triggered by screen taps.
So I hard reset, and got no response on the fifth alignment cross, meaning 1) "Tap on the screen...; 2) center; 3) top left; 4) bottom left; 5) bottom right. In that I could not proceed with alignment, I hard reset again, and now, at the first alignment screen, i.e. "Tap on the screen...", I have no screen response at all.
I called T-mo, and they are being great about sending a replacement ASAP (and getting me a loaner in the meantime).
BUT, I am running Faria+ AKU3.3 V2... so I clearly have to flash back to T-mo 2.26. I can;t figure out how to do it though, as no matter what I do I am stuck at the first alignment screen!!
HELP!! EMERGENCY!!!
(I have three or four days to get this done, so it's not THAT urgent)
Do a search for Broken Screen. Someone (either in Wizard Upgrading or in the Wizard forum) just had a similar issue with a cracked screen. They downloaded something that allowed them to get around the welcome page.
Actually, if you are just trying to flash a new ROM, don't even mess with it. Go straight to the Boot Loader screen (see the first post of this thread). No tapping necessary until the new rom is on (and that will be the Tmobile then so you would be good.
Thanks for the quick reply. Charging up to green now, and then will try to enter bootloader and flash T-mo 2.26. Will report back.
Worked great. Back to T-mo she goes!!!
BootLoader Mode
Excellent thread but you left out one thing.....exactly how to place your device in bootloader mode.
To clear up any misunderstanding because this is very important....this is how you do it:
Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up .... That's it !!!!!!
When the unit is connected, USB is displayed at the bottom left.
There is a problem with my MDA: It continually flashes the volume/ringer control on the screen with the circle with the loudspeaker and mic turned off. This flashes every second or two and when it flashes, prevents pretty much anything else from working or command from executing.
I had a very old TMobile software version on it. I down loaded a much newer version from TMobile in an attempt to get rid of this problem before upgrading to XDA firmware: (The whole thing is very out of warranty)
The upgrade went successfully but the flashing volume / ringer control still flashes.
Does anyone know what this means or if upgrading to XDA will get rid of this problem (or exacerbate it!)
Has anyone noticed IF there is a problem with Puttenham's "Step 17"?
I got around my nerves about upgrading this G3 with a hardware problem in place and appear to be encountering a severe problem with Step 17 which is that it says it is "Your Choice" to go to a 3.08 SPL/IPL. Nowhere however does it say which later ROMs you can apply if you DO choose to go with the 3.08. I applied this to correct what I thought was the hardware issue (reinstalling the T-Mobile ROM at SPL 2.26 didn’t seem to cure it) and the 3.08 did install properly and cured the hardware problem.
I tried different ROMs because I cant seem to understand how to use VoIP or which ROM will let me use this 'feature' or which ROM has this feature built it as some say they have deliberately taken it out.
Suddenly I am getting error messages telling me that the unit needs a later ROM revision to install perfectly.
(WizardLove was the first to do this: It executes in Italian and as I mentioned, just tells me that it needs a later version to work)
So I reflashed with the Molski ROM which is the only one which seems to be around and the flash worked up until 94%. At that stage the progress bar turned to red and there was an error message telling me that I can recover and try again. I did this a few times and SEEM to have bricked my Wizard (When the Molski upgrade failed, attempts to chkdsk, reboot, delete all temp files etc failed). The unit will now only boot to the three-colour screen? Further attempts to flash seem to see and read the device and tell me either that there is no ROM on it and would I like to upgrade? Followed by this unexplained 'USE LATER ROM'. (There may be a problem with installing the T-Mobile ROM on an unlocked Wizard with a 3.08 IPL/SPL However it has to be said that Molski is, still, the only ROM which runs and it inevitably stops at the same position, the 94% mark when the MDA progress bar goes red, the unit shuts down, the upgrade process thinks about it for a while and ultimately reports ERROR [302] UPDATE ERROR)
Alternatively they (for example ROM Update Utility 2.00.1) tell me that there is no communication between the PC and the Wizard. Actually ActiveSync 4.5 does show no connection between the device and the PC, which I suppose I would expect if the Molski ROM failed to complete? Device Manager seems OK with the unit being in place though? And I cant believe this is important as there obviously IS connection between the computer and the PDA
Easymob said he would let users have a path to a ROM they could use but no where is it set out which ROMs you can use of the ones you actually CAN find?
I have also tried the Xelencin ROM which initially tells me that it cant see the PDA. Then it admits that it can and tries to unlock the CID (which surely must be already unlocked by now if I have upgraded to the later SPL??)
I am not sure I have a totally bricked unit, - The Xelencin T-Mobile ROM MUST be doing something because it does successfully run the RAPI unlock and after a few error messages telling me it can't access the MDA, reports DONE! But then it tries to run Machinagod's HTC Wizard Unlocker and gets stuck. It shouldnt get stuck at this step as I must already BE unlocked! It should pass this step.
I can hear hdd movement (not churning) but the program doesn’t progress past this step. Ultimately this carries on for hours and the Wizard shuts down I presume when the battery fails as the charge function doesn’t seem to work in ROM upgrade three colour screen mode. Plugging the charger in now doesnt seem to do anything
Again as the program was built for the 2.26 SPL, I still cant figure out whether these available ROMs should run on the 3.08 which I followed in the STEP 17.
MEANWHILE BACK AT THE RANCH: Is there a more obvious answer to why Molski always fails at precisely the same 94% position?
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 don't know if I can help you but will try since this forum has helped me.
My P3600 is basically screwed. It's a walking zombie brick phone.
Why zombie? Because I bring it back from the dead everytime!
I dropped my phone quite badly twice in a day a few days back,
Next day I woke up... my pocket alarm had hung and I had to hard reset because a soft reset brought about the Tri-colored bootloader screen.
After that, everything was GONE... so I decided I might as well load a new up-to-date ROM. Was using Akeo's rom happily before that.
Did the usual SPL routine, new radio, new OS rom.
Installed new stuff...
But then phone would continually enter bootloader screen most of the time when I did a soft-reset. Except that it would have a terrible error message that only gave me the option of trying to restart without changes or basically reset everything to original settings (or something like that which meant everything is gone again). With the error message in place... nothing would work.
Could not reset into normal bootloader. (without the error message)
Windows mtty.exe method could not connect. (it would under normal bootloader)
Activesync was obviously disabledsync.
Flashed radio, spl and OS roms repeatedly using Des' SSPL and Olio's HardSPL 1.20 and 1.30 to no effect. It would always come back with that error on a random reset.
Then I read about the method of flashing with SD card. But this didn't solve my problem... it would come back still after a reset.
Mtty.exe from Windows XP to format nand and mark bad blocks etc.
Nothing found.
Finally, I almost gave up.
Then out of desperate measure.
I decided to leave a copy of a TRINIMG.nbh in the SDcard for GOOD!
It's basically an SPL image. Done with the NBHutil.
Used it to split out the HardSPL 1.30 spl.nb and merged it with the splash.nb and sub-splash.nb from my current OS rom.
Everytime I reset... there's still a chance it will enter bootloader mode with that horrible error message. But in such a situation... I now simply choose not to reset settings to default and instead simply pull out the battery.
Then plug it back in and power it on again. 80% of the time... it boots back into Windows mobile like normal on the first try! No loss of settings... nothing nasty. Back to normal! The other 20% of the time? I just pull out the battery and power it on more times! Till it works! Hasn't failed me yet in 5 days. Mind you, I was bricking it twice a day before this. That's progress!
I simply use SPL backup to make a full backup anyway whenever I install any new software etc, contacts etc.
Give it a shot.
I don't know why it worked for me...
Maybe I have bad sectors or something where the SPL is.
Whatever it is... the SDcard's TRINIMG.nbh works as my SPL now.
Think of it as a case of a bad bootup sequence on an old dos system needing a backup msdos bootdisk to do the trick!
Good luck!
Hi, i'm totally new to flashing phones etc. I have a tytn II and was running windows 6 on it.
I Flashed it with Hard SPL, and then downloaded TPC 23053 Titanium Ultimate. It's the one on the thread that says you don't need to flash a stock ROM first.
I flashed it and all went fine, booted up and alligned the screen etc. It then rebooted itself then loaded back up. All seemed to be ok, sound and camera wasn't working. In the fourth post of the titanium thread, it says the recommened SPL and radio.
which are Recommended SPL 3.34 Radio 1.70.18.02
So i downloaded both, flashed the SPL and then the radio. Now when i boot i get a black and white image of a tribal kind of dragon. It asked me to setup the phone again so i alligned the screen again. Sound and camera now worked.
However, i was usuing it for a while and then for some reason programs stop loading, it says something like, it's write protected or make sure you have the correct security permissions. When i plug into the pc i can't get anything off the storage card or the phone, it says permission denied.
So when i reboot the phone, it keeps asking me to setup again so i lose all my contacts that i have added etc. I can turn the phone on and off and it's fine, but then eventually does the wierd permissions and access denied thing and when i reboot always asks me to setup the phone.
Can anyone help me as to why this is doing this? I read something about CID unlock etc, is it to do with that because i didn't perform this step.
Not sure why everytime i reboot the phone it asks me to setup the phone again, sometimes it doesn't, it's usually after it stops letting me open programs.
Thanks in advance and sorry for the long post.
Maybe reflash.
You should have posted this in the thread made for the rom.
Thanks for the reply, sorry it's in the wrong place.
Can i flash back to windows 6, is this possible as titanium is 6.5 and do you know where i can find the "stock rom" for the tytn ii.
I think the problem is i didn't flash to stock rom first, but i was already running the stock rom. What was on itwhen i bought it from the shop so it's the same thing isn't it?
Obviously you must have flashed Hardspl and sim/cid unlocked your phone. Upgrade your hardspl reflash with a stock 6.1 rom from the wiki .I know it says that you don't have to flash stock first, but when flashing 6.5 roms, it is always a good to flash stock first to clean out the extended rom.
Flash a stock rom , flash ultimate, hard eset and the set up.
Thanks, i will try it now. I'm following these instructions. Do i need to do all of this including the bootloader, or just to restore the OS to step 2? Also once done do i need to reinstall HardSPL?
1. Get the original ROM for your device (HTC or ATT)
2. Flash the OEM ROM to your device (this will restore your OS but not the bootloader, we'll get to that below)
3. Copy the ROM to a temp folder and extract it, I use WinRAR, just right click on it and select "Extract to Here"
4. After extracting the ROM you should have a several files here, one called RUU_signed.nbh is the one we're looking for. Copy this file to another empty temp directory.
5. Download NBHExtract and follow the instructions in the link to extract the NB files from the ROM (essentially just copy nbhextract.exe to the temp folder where the nbh file is and run it from a command line - like so C:\temp\kitchen\>nbhextract.exe RUU_signed.nbh
6. You should now have several .nb files in that directory, the one we're interested in is the 01_SPL.nb.
7. Now you have to create an NBH file with just the SPL, to do that download htcrt (HTC Rom Tool).
8. Run the tool and under the ROM Builder tab select Kaiser, the rest on the left side doesn't matter right now. On the right side of this window click the "..." next to SPL and select the 01_SPL.nb you extracted from the OEM ROM. This should be the only thing added under Firmware Contents. Click Build ROM.
9. You should now have a NBH file that is relatively small (about 258K), copy this NBH file to a new empty directory
10. Download pof's KaiserCustomRUU.exe and put this in the same directory used in step 9. Don't run this yet.
11. Download pof's SSPL-KAIS.exe and copy it to your phone
12. Run SSPL.KAIS.exe from your phone (make sure you do this on your actual device and not your PC)
13. When you have the bootloader screen on your phone run KaiserCustomRUU.exe from the folder used in step 10.
14. After it's finished verify your SPL by holding down power and camera buttons while doing a soft reset.
15. Send your device back for warranty repair or replacement.
No you don't have to do all that. That is just if you want to restore your phone for warranty return. All you have to do is go to the wiki. http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs and download a stock rom to your desktop. Connect your phone and run the RUU and follow the onscreen.
After your phone is flashed with stock, just reflash Ultimate the same way.
First however , enter bootloader , depress camera and power button while soft resetting, and check your spl, if it is still 1.0 olipro , upgrade it first to 3.29 or 3.34 using this guide. http://forum.xda-developers.com/showthread.php?t=498320
Once your phone is hardspl'd you never have to do it again
Thanks very much for your help. I have 3.29 on there at the moment, should i flash to 3.34, then flash to stock rom, and then to ultimate again.
Or flash stock rom, then 3.34 SPL and then ultimate?
Mitchsnake said:
Thanks very much for your help. I have 3.29 on there at the moment, should i flash to 3.34, then flash to stock rom, and then to ultimate again.
Or flash stock rom, then 3.34 SPL and then ultimate?
Click to expand...
Click to collapse
You can do it both ways it doesn't matter since you already have hardspl on your device and basically you are updating the current 3.29 to 3.34 to have a better performance with the ultimate rom.
I downloaded 3.34 SPL, and transfered the 3 files, JumpSPL1.56-KAIS.exe and JumpSPL1.93-KAIS etc to my device, it then says to take the battery out.
However, when i do this my device hard resets, i have to setup the phone again. Because it hard resets it deletes the 3 files so i can't run JumpSPL1.56
How important is taking the battery out after transferring the files to my device. How can i get round this, shall i just run the file without removing the battery?
Mitchsnake said:
I downloaded 3.34 SPL, and transfered the 3 files, JumpSPL1.56-KAIS.exe and JumpSPL1.93-KAIS etc to my device, it then says to take the battery out.
However, when i do this my device hard resets, i have to setup the phone again. Because it hard resets it deletes the 3 files so i can't run JumpSPL1.56
How important is taking the battery out after transferring the files to my device. How can i get round this, shall i just run the file without removing the battery?
Click to expand...
Click to collapse
No, it's important to remove it. How long are you leaving the battery out for? And was it over 50% charge before you removed it?
I'm assuming you followed steps 1-4 to the letter.
1. Copy JumpSPL1.56-KAIS.exe, JumpSPL1.93-KAIS.exe and JumpSPL1.94-KAIS.exe to your device memory (NOT STORAGE CARD)
2. Pull out the battery and reinsert it (this step IS important) *DONT turn phone back on yet*
3. REMOVE SIM and SD CARDS!!
4. Turn phone back on and let it boot back into your operating system
It sounds like there could be a hardware problem from all the hard resets happening there. Have you made sure that the reset button at the bottom is functioning correctly and isnt blocked by any dirt etc?
Mitchsnake said:
I downloaded 3.34 SPL, and transfered the 3 files, JumpSPL1.56-KAIS.exe and JumpSPL1.93-KAIS etc to my device, it then says to take the battery out.
However, when i do this my device hard resets, i have to setup the phone again. Because it hard resets it deletes the 3 files so i can't run JumpSPL1.56
How important is taking the battery out after transferring the files to my device. How can i get round this, shall i just run the file without removing the battery?
Click to expand...
Click to collapse
I wouldn't complicate things that are more than clear. The intructions literally says the following: 2. Pull out the battery and reinsert it (this step IS important) *DONT turn phone back on yet*. Just follow them, probably mskip for doing this tutorial spent a lot of time "trial n error". It really won't take anytime to do this step
Yep i follow those steps. I leave the battery out for about 30 seconds as it says. But obviously it hard resets so i can't do this at all as the files aren't there when i put battery back in. I have to set up the phone again.
I suppose i could just flash the stock rom, then see if that works when i remove the battery and then i can update the SPL? soft reset isn't blocked by dirt either.
If that fails i'm stuck with a bad phone
Mitchsnake said:
Yep i follow those steps. I leave the battery out for about 30 seconds as it says. But obviously it hard resets so i can't do this at all as the files aren't there when i put battery back in. I have to set up the phone again.
I suppose i could just flash the stock rom, then see if that works when i remove the battery and then i can update the SPL? soft reset isn't blocked by dirt either.
If that fails i'm stuck with a bad phone
Click to expand...
Click to collapse
Well yeah... if you had read it all you would know that you are meant to be doing all of this using a stock rom on your device. There's your problem right there.
If you already have hard spl on your phone so you don't need to go through all the steps of flashing hardspl for the first time. Just upgrade the easy way from the SD card.
I have had 3.29 on my phone and have flashed over a hundred times with never a problem, including Ultimate several times. Just try flashing a stock rom first and then Ultimate. Then hard rest and then setup the rom. If i works great, if nt then you can always upgrade your spl later.
Stuntdouble, theres no need to be like that, some people are new to this, and if you had read my previous posts you'll see that i didn't flash to stock rom first, because i'd just got it from the shop, so the stock ROM was already on it. I didn't think i needed to flash it with the same one again first. Thanks for the help though everyone, I've now flashed stock rom, and gonna try ultimate again/
Sorry, but the amount of people on here who don't actually read FAQ's/Stickies before flashing their device don't get much sympathy from me. I think people underestimate the risks involved when flashing for the 1st time. However i've been having a bad day so I apologise for snapping.
Yeah no worries, it annoys me too when there are tutorials yet people can't be bothered and just post asking how to do something. But the only reason i didn't flash a stock ROM was because i got it from the shop so didn't think i needed too.
There is something i would like to know though that i can't find how to do. I'm trying to install 3.34 Hard SPL now, i have 3.29 at the mo. I don't have a card reader unforunatley so can't format my card to FAT32 like it says to if installing from card.
Is there an easy way to upgrade it other than using storage card? Or can i do the same steps as when i first did it. i.e, run the JumpSPL 1.56 but instead of opening the 3.29 KaiserCustomRUU, i open the 3.34 Kaisercustomruu?
I apologise if this info is anywhere, but i've read all the faqs and searched google and can't seem to find a guide on upgrading SPL from 3.29, it only tells you how to first install 3.29.
Thanks.
Off with their heads!
Ok i ran JumpSPL 1.56 and then ran the KaiserCustomRUU of the 3.34 Hard SPL, now when booting i get the dragon spaslh screen, but when i go to bootloader, it still says 1.29.
What am i doing wrong?
Fixed this now, thanks for everyones help appretiated