Related
Hi all,
Have purchased a German MDA_C and flashed it to the latest dutch WWE rom (1.13). I use the NOID updater and get an error message at 99% of the update.
After this my MDA hangs at the splash screen (but showing updated rom and radio versions).
Doing a lot of soft and hard resets I managed to get by the splash screen 1 time...
Tried a lot of different rom versions but each time I get the same problem
I've read that the SPLASH screen problem is more or less common but I wasn't able to find a solution on the forum.
Now I made one stupid mistake... I did not backup the original rom...
Any suggestions how to get up and running?
Thanks in advance...
BuDDaH
The very first boot takes a long time, 15 mins for some! If you're not waiting for around 15 mins ....
Thanks for this valuable information kta.
This time I waited 1 hour after upgrading just to be sure.
same result. flashing stops at 99% of the CE Rom.
Hard reset shows splash screen with version numbers (radio 1.13 rom 1.13 wwe) and then just hangs.
From bad to worse
So I had a MDA_C that did not boot further than the splash screen.
Updated using the MaUpgradeUt_noID.exe. Thought I'd give the SD way a try since I already tried about 6 different roms all with the same result.
First I made a backup to SD card of what was in my MDA using romupdate.exe
extracted the file to my HD.
After extracting (and securing the device ID) I tried rebooting my MDA.
Now things got worse!!! instead of the splashscreen I now have the BLACK SCREEN......
Have tried resetting and hard resetting dozens of times (more like a thousand times) and only occasionaly the splash screen comes up. :roll:
But over the last couple of days I only managed to get the bootloader 1 time (and at that time there was no SD card inside) :shock:
this is behaviour I haven't read about on the forum.
Guess I will have to get it serviced.
Is there anyone on the board that has an address in the Netherlands that can flash or repair my mda? Not sure T-Mobile NL services German devices...
Thanks!
Not dead yet?
Here's some more info.
My 'almost dead' Magician is showing signs of life.
I had the BLACK SCREEN.... (first couple of lines of pixels were not black)
After thousands of hard and soft resets (soft resets seemed to have the best results) I managed to get into the bootloader!! Flashed with an older rom and at least I'm getting the splash screen again. (but still getting an error at 99% of update of the CE rom).
I'm updating using the exe in bootloader mode btw....
Since there's always an error at 99% when I use the exe method and the device is not booting I thought about giving the SD method a shot.
My device didn's show the SD option but fortunately tadzio explained about the MBR (didn't even know a SD card had one!!! :lol:
http://forum.xda-developers.com/viewtopic.php?t=32849
When I decode a nbf file using nbfdec.exe and flashing afterwards I get a message that my ROM is to small.
Size is same as nbf file.
How do I correctly decode a nbf file?
Thanks for the help.
BuDDaH
Don't use a nbf, get a dumped or bs rom from the ftp & follow instructions with copying bytes etc.
M
Ok OLTP I'll skip the nbf decoding route.
Think one of the problems is the way the newer roms are encoded.....
Saw you're using a 1.13 bigstorage rom?
That one is not on the ftp is it?
Modified your own rom image?
Hi BuDDaH,
I downloaded at the Dutch TMO site the shipped-rom, unzipped the exe file & decoded the nk.nbf nbfdec. In this nk.nb1 I altered the usual BS bit patterns and re-encoded the nk.nb1, again with nbfdec, to the nk.nbf. After that it was just running, the extracted, upgrade program & it worked like the usual shipped-rom upgrade. you might have to use the maupgrade_noid version, sometimes twice.
This method is better described in the thread about upgrading to radio 1.13 which you can add along the road as well.
So yes I made it myself, not so fond of using other people's rom unless I have to. Please don't let anyone be offended by this, cause a replaced bit can cause serious harm, like I encountered myself, with my own corrupted rom-dump.
Good luck, M
Just wanted to update you all on the latest status.
I managed to flash a german rom (as I've got a German device) although I always get an error message at 99%.....
Fist it just stuck on the splash screen but this somehow deteriorated. Now I get a black screen covering about 5/6th of the screen. the first 1/6th shows a part of the splash screen. No backlight and it hangs.
No more bootloader so I need to have it serviced (anybody knows what the techies do with such a device?)....
Now the question remains where.
T-Mobile NL refuses to service it since the IMEI is unknown to their system
T-mobile Germany doesn't have a service center but only takes repairs through a T-Punkt shop..
Any ideas?
Thanks,
BuDDaH
Latest update...
I sent it in for repair and it turns out that the ROM is damaged and the phone needs a mainboard replacement..... which costs about the same as a new unit...
Anyone got a spare one laying around for me?
So much for my Magician!
Cheers,
BuDDaH....
Sorry to hear...did you try another SD card?
Yep I did; but unfotunately the situation deteriorated and I'm completely unable to get into bootloader mode.....
Well.. :idea: maybe I must see this as a great opportunity to get wild with a set of scewdrivers
Hey BuddaH,
There enough people interested in the parts here at the forum, so there's a tiny brightside on your adventure :-(, man i do feel sorry for you.
Regards, M
Yup, i need some parts also
BuDDaH said:
Yep I did; but unfotunately the situation deteriorated and I'm completely unable to get into bootloader mode.....
Well.. :idea: maybe I must see this as a great opportunity to get wild with a set of scewdrivers
Click to expand...
Click to collapse
You probably ran the battery down. I don't think it charges unless the ROM is working. That is why it is highly recommended that you start with a full charge before commencing a ROM update.
Hi Stevedebbi,
Even in my situation the it still seemed possible to charge the battery (at least the red light went out and the battery got hot).
Sent my device to apexlaptops.co.uk cause they claimed they reflash...
Got the reply back that they couldn't get it too bootloader mode and were unable to repair. (guess they could not do some JTAG debugging).
I may be able to buy a working device that's damaged on the outside....
Hi there,
My currently installed Rom was RUU-Prophet-G4-AKU2.2-2.20-2.47.21-Jester-r1.exe. (thank you jester for you good job)
Nevertheless, this ROM is in English and I wanted to downgrade to a French One before the selling of my device.
I have tried to install the downgrade kit detailed in this topic : http://forum.xda-developers.com/showthread.php?t=267344
The first step went OK but while trying to make the secnd step, my qtek is blocked at the boot splash screen showing the Jesterz picture and red information about the SPL and so on on the upper left corner... without starting... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Don't worry, its nowhere close to being dead. If you have superCid, then use the SD card image to restore in bootloader mode. However, if the Cid is locked, then you would need a utility that can unlock Cid without Activesync mode (coz in your case, you would not be able to get an Activesync connection). imei-check.co.uk has a utility ($38 i guess) that unlocks Cid in bootloader.--- else show it to a professional. (in my country, I would have to shell out around $20 to get such a problem fixed at a mobile repair shop)
illanz said:
... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Click to expand...
Click to collapse
Just take out the battery for about 10 minutes and re-insert. If it does not re-start, do a soft resert with the stylus and hopefully you should be fine
Hy,please help!
after downgrade, it doesnt work anymore.... i mean... i cant start the mobile!
after the downgrade i disable the USB data cable and now the mobile is dead... it doesnt starts from the ON/OFF Button and even if i connect the USB cable it makes nothing! No Led on... nothing! absolutly DEAD!!!
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Try this in order to reach the bootloader:
Hold down the camera button and reset the device. (Boot Loader Mode is: Press Camara + Soft Reset, then release soft reset and KEEP PRESSING camara button till appear the Boot Loader.)
it doesnt work
I seem to have a simular problem. this is my post in another topic. It seems to fit better here.
This is what I tired so far:....
I used the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_S hip-NoVendorID and it often hangs and was slow with Push Email over GPRS.
I tried to find a way to downgrade but hadn't had time sofar. When I logged on XDA Developers Site I saw there was a new Image.
So I thought Great I dont need to find how to downgrade.
I don't know what G4 and G3 is so as everybody let's try the higest best one.
I uploaded the RUU-Prophet-G4-AKU3.3-Jester-b1
Wrong...
Now as previously stated I get to the multicolor screen with IPL 2.09 and the SPL 2.20..0001 on the screen and that's it.
I can get to the bootloader and load the same image again and get the same result.
I can load another image on and it loads to 80 Percent and says error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file.
If I try an older Version it tells me upgrad only
And when I try to upload the G3 version it tells me error[300] invalid upgrade tool. This upgrade utility canot be used for your PDA Phone. Please get newer Upgrade utility.
Trying to use the nf.nbf or the G3 with the ROMUpdateUtility_NoID of the G4 doesn't work either.
If I would like to do the downgrade tool I need a Active Sync connection which I don't have.
I have no more thoughts. Please Help.
If you would have just read the forums better you would have known if your device is a G3 or a G4. (read this!).
Now it appears you have tried both for an update. Which may possibly have bricked your phone.
But... first things first. Can you get into the bootloader? (read wiki HERE on how to do that).
If you can still get into the bootloader then there is still a possibility for updating.
Try upgrading with the latest Qtek rom (note: this is an official rom, this one works for both G3 and G4! And since it's the latest you should be able to upgrade to this one).
Instructions quoted from another post of me:
You could try the 2.20 qtek rom which seems to be working well for quite some people (found here).
Although you have to make sure you read that thread good and use the ROMUpdateUtility_NoID.exe (found here ) to upgrade.
Update instructions:
1: With the qtek 2.20 rom you need to extract the zip and the exe file in the zip with WinRAR.
2: Then there is one folder called 'OutputFile' and a folder called 'RUU_TOOLS'.
Inside the RUU_TOOLS there is prophet and in that one WWE, when you go through them and in the WWE folder you see a bunch of files (readme.doc, enterbootloader.exe etc etc).
You need to copy ROMUpdateUtility_NoID.exe to the WWE folder with all the files. And you also need to copy the 'nk.nbf' file to the WWE folder (from the 'OutputFile' folder).
3: And then you need to put your phone in bootloader mode and run ROMUpdateUtility_NoID.exe to upgrade, which should work nicely then.
Click to expand...
Click to collapse
This should give you a good enough idea of what to do. This should work (new rom combined with no NoID updater).
However, if it's impossible to get yourself into the bootloader your options of upgrading your device are getting smaller.
Downgrading of a complete rom is only possible on a CID unlocked G3 (when it's CID unlocked you would know! because you would have done that yourself) and not on a G4 device.
Flasing a G3 device with a G4 rom or G4 device with a G3 rom might possibly turn your phone into a brick. This can easily be avoided by reading the forums properly and know what you are doing.
If anything (even if it's a small thing) is not completely clear to you about upgrading/downgrading your device I'd recommend not doing so.
edit: oh yeah... if you have a G4 device (which you should know by now) you cannot downgrade from this rom (well, only via a payed online service). And when you have a G3 device you could try and CID unlock it (read wiki + forums) before you want to downgrade, or don't downgrade at all.
But whatever you do, don't try to downgrade it without doing any of those things because you'll get into trouble. (to put it down bluntly)
illanz said:
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Click to expand...
Click to collapse
If you have reached the bootloader screen, just run my installer (or any official ROM) to get your phone working again.
My Prophet Died
I need help, to restore my Prophet, i upgrade wrong rom, i need will try the SD Backup, where can i see this process ?
Sorry my Inglish is too bad.
I've merged a couple of threads under this one, as they are all about the same problem (mostly)
Opening a new thread for the same problem isnt very useful
Hi RaptorRVL
Thank you very much for your patience in resuming all this for me.
I do try to read the forum but it isn't like a manual where you find the procedure stepby step. Like the G3 and G4 version I have newer come across until now. Sorry.
I tried the image you metioned and I have the result that at 80% it tells me error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file
Any more thoughts?
As you seem to be an expert Can you let me know more about goldcard solution.
Cheers
Mick
From a readme I once found inside an update:
* ERROR [320~328] : INVALID COMMAND
These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.
Click to expand...
Click to collapse
Doesn't sound too good really. Maybe someone else here on the forums know what to do with this error :/
You did use the ROMUpdateUtility_NoID.exe and not the normal updater right? Can remember someone getting a similar error when using the wrong updater, but I'm not sure about that though...
edit: try doing a search on the prophet forums for "INVALID COMMAND" maybe there is a helpful post in there somewhere...
THANKS!! I was worried b/c i had the same problem today. I've been looking for so many threads abt this problem. Thanks for ur help guys!
same problem
so i have the same problem. I want to downgrade and it break at 95% invalid file. But now XDA is still alive. I can`t go into the bootloader but i tried this file: RUU_Prophet_220734_2207114_024721_NVID.exe
and now my Prophet is still running again. Hope i can help you. Good luck.
peter paul
P.S. sorry for my english, but its good to learn it again
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
Hello guys...
Iam not new, and i have already flashed my first(it was wasted not by my fault)KAISER, it was one year ago and i did it with HARDSLPv1, and lately added some new roms cooked by sakajati(respect)...
Yesterday i bought new one(but one year old) so i tried to flash him as well, i have used HARDSPL 1.93, and then i tried to put Sakajati"s 4th feb ROM, but i come across one big trouble, everytime i try to put it on i encounter the same RUU error:
ERROR [262] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process. Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue. Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
what to do...????
i am very afraid that i destroyed my Kaiser...???
what it means that Wince is destroyed...
Please help me, i am desperate...
Iam not new,
Click to expand...
Click to collapse
But the solution could be found here (search)
If you see the tri color screen everythng is ok, just win mobile is destroyed. Try to flash a rom from your sd card
Thank you very much...
I hope it will work, i really did search for about an hour and tried to put rom on sevral times, but i didnt find nothing 100% secure, i dont want to indanger the unit any more that i did...
thanks again, i will try it tommorow morning at my job, thats where my SD card is...
)))
greganovak said:
Thank you very much...
I hope it will work, i really did search for about an hour and tried to put rom on sevral times, but i didnt find nothing 100% secure, i dont want to indanger the unit any more that i did...
thanks again, i will try it tommorow morning at my job, thats where my SD card is...
)))
Click to expand...
Click to collapse
Part of the problem is that 1.93 is a jump spl and should be used to upgrade to Hard spl 3.29 or 3.56, not as an spl on its own. You need to run jump spl 1.93 from your device and make sure you are connected to your computer, when you see the bootloader you need to unplug your USB, count to 10 and plug your USB back in then flash a hard spl to your phone! Again 1.93 is not a Hard Spl by itself, it is only a middle man to flash a Hard Spl.
I think the best would be to flash a stock rom at first, cause therefore you don't need an other bootloader. Then flash Hardspl (3.29 if you have a kaiser or 3.56 if you have a tilt) and then flash any rom you want
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
greganovak said:
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
Click to expand...
Click to collapse
It realy doesnt make that much of a difference, I have a tilt and I use 3.29 and I would recomend it to anyone over 3.56 so flash either one, they will both work! And your english is great so no need to say sorry!
greganovak said:
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
Click to expand...
Click to collapse
A Tilt is a At$T branded Kaiser, a TyNT II is a HTC branded Kaiser. Tilt has a different keyboard and OEM rom., only differences. People say use 3.56 if you have a Tilt because that is an AT$T Spl, but I use 3.29 on My Tilt and it works great so it doesn't really matter.
hey...
nothing seems to work...
I have tried to put default rom dl from here: http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs but the problem is that it is not bootable from SD, that has to be because the USB conection isnt on (i selected the 3.34.721.2) so i given up that way
Then i flashed the HARD spl 3.29(have kaiser) via SD steb by step first with this instruction: http://forum.xda-developers.com/showthread.php?t=433835; and it dint go through
so i tried with this instruction: http://forum.xda-developers.com/showthread.php?t=420683
it didnt work either, they are the same I know(noticed later);
So problem is that i stuck at WHITE screen that says "LOADING..."
nothig else...???
finally i manage to load/boot the htc rom from xda-wiki site, but i have to chose another one
I have tried to put default rom dl from here: http://wiki.xda-developers.com/index...me=Kaiser_ROMs but the problem is that it is not bootable from SD, that has to be because the USB conection isnt on (i selected the 3.34.721.2) so i given up that way
Click to expand...
Click to collapse
Hey man, nice to see that your device rewakes, you can flash every rom from sd card, simply rename the nbh file to kaisimg.nbh than restart into bootloader and it will automatically take the one from the card
Unfortanly, althought i would like you to be right, you are not. When i tried to do it via SD, i stuck at white screen saying LOADING...(blue) and nothih further... and i tried also the Cmonex_s Hard SPL3.29_SD which also stucks at same screen
So now (after updatig with default rom) that i have basicly normal working device i startet from the top. Using @mskip"[email protected] tutorial called: Flasing your first rom (for noobs); it all goes well, till i start to update RUU(sakajati 4 feb) if it matters, and i tried both (spls 1.56 and 1.93), it stops updatig at 17% and notrhin else then works just puting back the HTC default rom from wikiXDA side(thank god for that)
i am thinking of MTTY, although i dont know what it does guys here almoste all say it fix bad rom flash, but i am not sure if thats my main problem, i rahter think it has something with spls...
if someone has some good advice i will be very grateful...
greganovak said:
Unfortanly, althought i would like you to be right, you are not. When i tried to do it via SD, i stuck at white screen saying LOADING...(blue) and nothih further... and i tried also the Cmonex_s Hard SPL3.29_SD which also stucks at same screen
So now (after updatig with default rom) that i have basicly normal working device i startet from the top. Using @mskip"[email protected] tutorial called: Flasing your first rom (for noobs); it all goes well, till i start to update RUU(sakajati 4 feb) if it matters, and i tried both (spls 1.56 and 1.93), it stops updatig at 17% and notrhin else then works just puting back the HTC default rom from wikiXDA side(thank god for that)
i am thinking of MTTY, although i dont know what it does guys here almoste all say it fix bad rom flash, but i am not sure if thats my main problem, i rahter think it has something with spls...
if someone has some good advice i will be very grateful...
Click to expand...
Click to collapse
Hi,
I couldn´t flash my Kaiser via SD at the first time and tried something that worked.
The SD´s are formatted in Fat16 usually, try to format to Fat32... It seems like a stupid thing, but worked for me.
Reagards and good luck.
SD must be formated FAT32, to work, also I sugest a smal card, 512 or something like that, SHDC usual doesn't work
I have 1GB SD and its not shdc, so thats ok.and i have done it right now, like you two guys said so i formated it with FAT32 but still no succes.
I guess that this tree lines in red/green/blue screen arent right:
KAIS130
SPL-3.02.0000
CPLD-8
i thing this SPL has to da something to do with all this mess a have done
I have flashed a couple of roms( i had three devices) and i flashed a few for my friends and all was OK till now, and i dont know what else to do...
greganovak said:
I have 1GB SD and its not shdc, so thats ok.and i have done it right now, like you two guys said so i formated it with FAT32 but still no succes.
I guess that this tree lines in red/green/blue screen arent right:
KAIS130
SPL-3.02.0000
CPLD-8
i thing this SPL has to da something to do with all this mess a have done
I have flashed a couple of roms( i had three devices) and i flashed a few for my friends and all was OK till now, and i dont know what else to do...
Click to expand...
Click to collapse
Yes, you still have a stock spl on there. It needs to be hard spl'd before you flash anymore. Check out the stickies at the top of the forum.
hi again...
Well, I respect the "rules" of forum, thats why i wouldnt ask for insructions that are already written(thanks for the authors) with that i mean stickys, because i read them, almost all...
But I still tried once again, and I came across the same thing, i stuck at 17% when loading RUU or if i choose the VIA SD i stuck at white screen with blue text saying (LOADING...)...
nothing else helps than loading the dafault ROM by HTC... as i already said once again...
if i manage to solve the problem i will be in touch; what do you thing about MTTY
Edit 1:
i have done everything as it says in the instruction, and just like some of you "replyed" me...
but i always stuck at 17%when loading RUU, when i flash it with SPL 1.56 or 1.93 i never get stuck at white screen it always apeare the mentioned SPLs nimbers and some other text in yellow but when i then load RUUs i stuck at excatly 17% nothing less nothing more
edit 2:
yupi....yupi
i made it...
http://forum.xda-developers.com/showthread.php?t=354061 here is my lifesavior...
those instruction were the one that helped my problem...
it is very nice to ba a part of this community....
Hello All,
Normally I don't post and do a lot of reading, there is a lot of reading and a lots of headaches.. But never the less it is a bobbyist game. So this is the few time that I post I hope it help some of you guys out there having problem with the flashing of your Rom. But if you brick you Treo don't blame me O.K.
First of all..follow the unlock and unblock guide by navenedrob in this forum. till step 11..I can't do the SD card flashing either..so I just put the (whatever rom file without renaming it) in the tempche directory( that is the directory it generate itself when you run the Cheetah unlocker program.) then run the RUUWrapper program, then it should do the update for whtever rom you want..sometime it will tkae a few second before it takes off to update..so be very patient..and wait...
Once that is done you have to do a hard reset while the Palm logo is showing. then you should be able to do whichever rom you want..
I was able to flash back and fore from the WM6.5 to WM6.1 without any problems.
BTW I am running this in WIndows 7, I don't think it matters..but I can put the Treo in a Boot mode( the tre color screen) and the Cheetah unlock program still find it. IMF I think the cheetah program find it fast in that mode..so give it a try.
If that still don't still don't get you to where you want to be, then I guess do some more reading. there is a tons of good reading material in this forum.
Sorry for the long post..and Good Luck
yup, before that you must had step 1 running as well (connected your treo to activesync)..
How can I connected and run the unlocker if I stuck in palm logo ?? If I runs the cheetahunlocker it will stop at error connection...
Nothing to do if the phone alreary stop the activesync ... isn't it ???