I think i must have the worst luck or else I'm doing something stupidily wrong...
I fried my device when trying to apply the bigstorage hack on ROM version 1.12WWE.
A week later my mate asked me to do the same on his JAM- same thing again- device just totally fried!
I had successfully applied the bigstorage hack on both the above devices with the original T-Mobile Rom (1.01 or something)- this went without a single hitch.
The method I used was using the 'Bigstorage software'
Do i need overwite the first 416 bytes even if im using my own rom and not a downloaded one?
What am I doing wrong?? This has really got me frustrated now.
Any insight as to what I could be doing wrong would be very much appreciated.
Thanks
Quite a few people have reported to get a totally "dead" magician using the "Make BigStorage" method. The good news is that when they return the machine to the service center, it can be fixed.
This is different from the "stuck at bootloader or splash screen" cases, which can be easily recovered by the user without the need to return it for repair.
It is much more safe to use the "edit two bytes at two locations" method to get BigStorage.
Talents- I was guessing that it would be you to reply- much appreciated for that . I was/am 99.9% confident that the service centre would get it working again. My frustrastion comes from figuring out what I am doing wrong. I am stumbled even with professional background (IT/PCs!).
So is it just my worst luck- or could I have done something wrong, unknowningly?
As much I want the latest ROM and bigstorage- i dont think i can run that risk again- even with the 'two bytes' method.
P.S. I was using a 128MB SD to perform hack- surely this is enough?
I recently did the bigrom hack, and had the same problem. after the device took the hacked rom, i soft reset, and it stayed on the boot screen for 25 mins.
I re-flashed the original non edited dumped rom to the device and it worked, copied the hacked rom to the card, and tried to flash again....and it worked.
My heart stopped when i just hung on the boot logo originaly.
Imp
Impossible,
From what I can gather the problem that you had is (was) not fatal... when I performed the bigstorage hack the device was TRUELY dead- nothing showing on the screen whatsoever... as Talents has also mentioned.
Anyway I had it sent off to the repair centre and have a brand new JAM back. Performed the 'two bytes' bigstorage method (thanks to Talents) and all is running well
Glad you didnt loose will in the upgrade.
Where abouts did you have to send your dead handset to, how long did it take to get a replacement.
Imp
In the end performing the upgrade was purely for the fact of doing it for the sake of it and frustration.
My original JAM was only about 2 and bit months old so it was still under warranty- returned to the place of purchase- T-mobile centre.
My one took 8 working days for me to get back but my mate's one took only 3 days.
Hello,
I experience same trouble as u all, still wasn't able to get the big storage to work. Let me tell u what I already tried:
Had a good working Dutch Orange M500 device with 1.06 original ROM. Udated it to 1.11 WWE I-mate ROM, no prob. Opend the storagespace with the mksBigStorage method, no problem,had 27MB free.
Updated to latest 1.12 original new Orange ROM via USB-cable method, no problem.
Now I want to open bigstorage on this original Orange 1.12 ROM, and no matter what I try, I cant get it to work.
-Tried yesterday all day, got a backup from CLEAN Orange 1.12 ROM, edited it with mksbigstorage program, no success at all. Got through all the steps, it goes to 100 %, checksum fale, upgrade fail message. Now it is stuck in bootloader mode.
-Edited original clean ROM with "edit two bytes at two locations" method, got through all the steps, it goes to 100 %, checksum fale, upgrade fail message. Again stuck in bootloader mode. Funny thing was that when I edited the rom, I only found 1 location in the ROM to edit, not 2. Went through it with the following query in the Bytes field: 02 00 00 80 00 20.
Maybe this is my mistake? Anyhow:
- got an external reader today, after trying all day yesterday with internal reader. Doesn't seem to make any difference, no matter what method, still no big storage. Did the whole process again, both metods. No luck until now. WHAT AM I DOING WRONG???
Yoho, I did it! It turns out that my 128 MB SD-card is giving me trouble, when I used the 512 card it finally worked!!
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!
Can anybody help me?
I was upgrading with faria's roms.
It all went ok until it reached 99%. after waiting for around 5 minute at that point, it sad that there was a communication error with the phone, and i need to do some recovery actions(remove from the usb, remove the batteries) It said that if i can see 3 bars, then everything is ok.I could see it, so i restarted the upgrade utility. But it did not want to do anything. It said to get a newer version of the upgrade utility. and my phone remained in that 3 color state, having 3 messages on it: IPL 2.16 then on the other corner saying RUU, then in a next row SPL 2.16
Can anybody help me to fix this phone?
Thank you in advance
ghola_2 said:
Hi!
Can anybody help me?
I was upgrading with faria's roms.
It all went ok until it reached 99%. after waiting for around 5 minute at that point, it sad that there was a communication error with the phone, and i need to do some recovery actions(remove from the usb, remove the batteries) It said that if i can see 3 bars, then everything is ok.I could see it, so i restarted the upgrade utility. But it did not want to do anything. It said to get a newer version of the upgrade utility. and my phone remained in that 3 color state, having 3 messages on it: IPL 2.16 then on the other corner saying RUU, then in a next row SPL 2.16
Can anybody help me to fix this phone?
Thank you in advance
Click to expand...
Click to collapse
Mine did something similar - PC Blue-screened about half way through the upgrade and left the Wizard at the Bootloader screen. I tried to re-run the upgrade and it said I needed a different version of the upgrade utility. I just re-installed the WM6 MB version and this worked fine, once it was back up and working I re-ran the Faria upgrade and it worked fine.
I think if you just copy the 'nk.nbf' file from Faria's ROM and use the upgrade utility from the MB version it will work.
HTH
Andy
ok.. here are the steps.. its very easy.. i had the samething..
your phone is probably CID locked.. so what you need to do is just download the original tmobile ROM.. and connect the phone and install the original ROM.. You didnt birck the phone because you get the bootloader screen.. which means, you can still save the phone..
anyway.. connect the phone via usb and install after you install the original wm5, download the shelltool from here and follow the instructions.. and install the ROM via shelltool.. Then you should be good to go with the new
wm6.
http://forum.xda-developers.com/showthread.php?t=271043&highlight=CID+unlock
DR.P'S UNLOCKING THREAD worked wonders for me.
BTW, after following Dr. P's instructions and loading Faria's ROM, my MDA took approx. 13-15 minutes at 99% before I hit the glorious 100%. Like a wise person before me said, patience is a virtue. I waited until the 5 minute mark, got up, used the restroom, grabbed an ice cold Pepsi and then waited some more.
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....
Thanks to WMExperts who announced the 'official' Verizon rom.
Anyone sitting with a bricked Ozone patiently waiting for an official, signed, rom....here's how your long-bricked Ozone comes back to life:
- Get a hold of the 'Official' WinMO 6.5 Shipped Ozone ROM.
- Remove the SD card and SIM card if one is inserted in the phone.
- Unplug & remove the battery from your phone for a few seconds; Ookba found this step to be essential to reset the device. Put the battery back in.
- While holding volume down button, press the power button. NOTE: The D-PAD is not Volume Control. Utilization of the D-Pad in this operation will result is user failure.
- The phone will enter "bootloader" mode and you will see a tricolor bootscreen.
- While in this mode, plug in your USB cable and wait until you hear the "ba-bing" USB sounds as the device connects.
- Extract the ROM package you just downloaded and run RomUpdateUtility.exe. Follow the steps, check the appropriate boxes, and start the flash.
Assuming all goes well, your phone will flash to the factory ROM and you can then troubleshoot what went wrong the first time that bricked your phone.
Thanks Ookba for the instructions!
0 ram free?
So i flashed my phone to the signed 6.5 rom, and now the phone boots but i have 0mb free on my phone. I have tried to delete some files, to no avail, as well as doing a hard reset. I tried to flash it again and no change. I am not sure what went wrong, any ideas?
schoenkn6 said:
So i flashed my phone to the signed 6.5 rom, and now the phone boots but i have 0mb free on my phone. I have tried to delete some files, to no avail, as well as doing a hard reset. I tried to flash it again and no change. I am not sure what went wrong, any ideas?
Click to expand...
Click to collapse
Maybe try a soft reset? I just did it and I have 18mb in storage and 64mb free in available memeory.
nope, no change
one more peice of info, it thinks it only has a 10mb drive
schoenkn6 said:
So i flashed my phone to the signed 6.5 rom, and now the phone boots but i have 0mb free on my phone. I have tried to delete some files, to no avail, as well as doing a hard reset. I tried to flash it again and no change. I am not sure what went wrong, any ideas?
Click to expand...
Click to collapse
same problem here ...
cheers
I'm noticing the same thing now. Hmmm. I'll have more of a look tonight. I'd really like to jailbreak it and put anonther ROM on it regardless.
I'll let you know my progress.
Glad I haven't flashed it yet, then...thanks for the heads up. Think I'll stay with the new 3VO ROM until further notice...
I noticed that problem with the 3V0 ROM on one phone but not on another... Seems there is something different in the versions that are out there. My guess is that if you did the 3V0 and didn't see a memory problem you wont with this one. Maybe that is why Verizon is holding back...
I know the problem must lie with the nbh file being 125 MB in size... If you looked at the 3vo roms they all are around 80-90 mb per NBH file, which leaves you with at least 30 megs of free storage. Perhaps they just need to shrink the rom or remove the 0 bytes or something.
I am stuck in the same boat 0Megs free so I can't do anything with the phone. If I try to reload custom 6.5 from bootloader it sticks at 0%. What can we do to get our phones back?
Verizon officially released the 6.5 rom today. From everything I can tell it is the same rom as the unofficially released rom last week.
I'm going to see if it has the same memory leak as the other one.
No change, I installed the new rom and still no memory.
Count me in also, have the memory problem and cant flash withanything but the original 6.5 signed rom...
Has anyone contacted either VZW or HTC regarding this issue? My Ozone is on PagePlus right now, but i am going to see if I can go into VZW and get it replaced if this is not fixed in a few days lol.
I wish I could reproduce this problem on my Ozone so I can help you guys troubleshoot it.
It might have to do with the Bootloader and new SPL version. I will try to cook the OS portion into an NBH and see if the problem persists. You will need to HardSPL to flash it though. Anyone willing to try it and see if it fixes the memory issue?
I'd be willing to try, how do I know if I have a hardSPL though. I'm not a newbie to flashing but I have always followed directions and never had a problem.
Edit: When I start the phone using the power and volume button I have
CEDA100
SPL-0.44.0000
MicroP-Cedar#W (LED) v58B
After doing some research I don't see how to get a hardSPL if I am not able to get it run anything unless its already installed
Burn242 said:
After doing some research I don't see how to get a hardSPL if I am not able to get it run anything unless its already installed
Click to expand...
Click to collapse
Yeah I can't HardSPL due to there not being any free memory on the phone. Is there a way to cook the stock rom and remove some of the un necessary files and still be able to flash it without hardspl? That would be our savior as we would not need that much room to run hardspl after we get the stock rom running.
Same exact response here, Burn...
JC
PS Have one working Ozone up on "official" 6.5, but have been having signal issues, i.e. dropped calls, no calls received, etc...