Related
I ran it according to farias instructions I thought. It flashed but now I cant install anything and I cannot write to the storage card or the phone, any cab i try to install is unsuccessful and I cannot save any files to the storage card or the phones memory.
And it appears that I cannot flash the rom again. Am I screwed?
What is you IPL / SPL? IS your phone a G3 or G4? Can you get to the bootloader? (turn off your phone (pull the battery if you have to) then hold the camera key down while you turn it on). You can flash directly to the bootloader (even though activesync won't connect.
BTW: If this stuff makes you nervous, you probably shouldn't be cooking... Your phone will do all sorts of weird stuff when you screw up a build. And you should really know how to recover from most things that can happen...
I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.
beowolf said:
I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.
Click to expand...
Click to collapse
ok, cool... wasn't sure... So can you get to the bootloader?
yes I can get to it
I am flashing back to the t-mobile 2.26 rom. Working so far, I will leave the cooking alone. Can you recommend a good wm6 rom that doesnt have any problems?
"doesn't have problems" is the catch
I'm partial to my own Crossbow Reloaded ones, but they aren't perfect. If you don't hit the keypad issue with 1.7 though, its pretty close
Core 2.0n is very good and nice and clean.
Also NBD and Wizard Mobile 6 are both supposed to work well.
The new "official" rom we are playing with is beta, but I have to say its really fast and we aren't seeing much wrong with it (but its only been 12 hours since its been released). There are a couple of issues that are fixed with cabs (CommManager for one).
As for cooking, you probably eith had something wrong in a .rgu or somesuch. Just takes a number of builds and flashes to get it right to where it boots (then you debug what you forgot in packages and start over )
hey Guyz. I have a Tilt that a customer gave me that got bricked while trying to flash one of dutty's roms...Problem is that the genius didn't load up Hard SPL even tho he told me that he did...now He wants me to fix it...even tho he didn't follow my instructions and read the WiKi...I kno that on the Hermes it was able to be unbricked. Is the same for the Kaiser possible? I would greatly appreciate your help as my customers are loving the work you guyz do here in nyc..
Thanks in Advance!
Cristian
What is the current status of the phone?
Can you get into the bootloader at all?
If you can get to the bootloader you should be able to load the AT&T AKU v0.4.4 ROM (the unoffical upgraded AT&T ROM). Once you get that loaded you should flash HardSPL immediately.
Let me know how it goes...
Cheers.
I bricked my tilt when it was less than 24 hours old... I recovered it with a BETA of the ATT rom and THEN redoing the hardspl thingy - worked a treat.
Do a search for tolt bricked and you should find afew threads for it.
The rom is called something like RUU_Kaiser_ATT_WWE....._Internal.exe
It goes to the Tri-Color Screen but stays there..I'll go ahead and research it so I can find the original AT&T and load it up...It shows a lot..workin for at&t and being a member on xda...U guyz have no idea how ya make life easier for my tilt customers b/c at&t truly dropped the ball on the rom...and by offering alternatives..u make the user experience so much better...thanks!
HTCFAN0923 said:
It goes to the Tri-Color Screen but stays there..I'll go ahead and research it so I can find the original AT&T and load it up...It shows a lot..workin for at&t and being a member on xda...U guyz have no idea how ya make life easier for my tilt customers b/c at&t truly dropped the ball on the rom...and by offering alternatives..u make the user experience so much better...thanks!
Click to expand...
Click to collapse
If you are at the bootloader screen (Tri-Color) then the phone is not bricked. In the sticky at the top on how to revert back for warranty replacement, it has links for the various roms. Just flash an official AT&T rom on it and you should be good to go. Then do the HardSPL.
Cool that you work for AT&T and hang out here! If you have any other warranty returns, I can give you my address as I wouldn't mind having a backup or two...
BTW: The AT&T ROM for the Tilt is actually quite good in the big picture of things. At least the phone is usable (slower than it should be and less memory than it should have, but its still very usable and stable on the official rom). If you want to ***** about official roms, go back to the 8125 and its official rom. The while the device (at the time) was great, that rom made the phone almost worthless (super slow, battery problems, bad radio, dropped calls, freezing, etc). I can't tell you how many people that run custom roms on the Wizard just can't believe what that phone is actually capable of.
Ok, sorry, got off topic there...
does Hard-SPL needs to be flashed just once on a device or does it need to be installed every tome a new ROM is going to be Flashed onto it?
mfrazzz said:
If you are at the bootloader screen (Tri-Color) then the phone is not bricked. In the sticky at the top on how to revert back for warranty replacement, it has links for the various roms. Just flash an official AT&T rom on it and you should be good to go. Then do the HardSPL.
Cool that you work for AT&T and hang out here! If you have any other warranty returns, I can give you my address as I wouldn't mind having a backup or two...
Click to expand...
Click to collapse
For some reason, it's not being recognized by my Activesync. I got it to recognize it but now it sayz Error 294: Invalid Vendor ID...I'm using the RUU_Cingular_WWE Rom for the Kaiser...so I'm flabbergasted at this point...
Quick Silver said:
does Hard-SPL needs to be flashed just once on a device or does it need to be installed every tome a new ROM is going to be Flashed onto it?
Click to expand...
Click to collapse
Only once! Than you can flash as much as you like!
HTCFAN0923 said:
For some reason, it's not being recognized by my Activesync. I got it to recognize it but now it sayz Error 294: Invalid Vendor ID...I'm using the RUU_Cingular_WWE Rom for the Kaiser...so I'm flabbergasted at this point...
Click to expand...
Click to collapse
ActiveSync will not recognize your device when in BootLoader mode!
The Vendor ID error means the ROM cannot be loaded on the Tilt without HardSPL. You need an original Tilt ROM. (That's what I think about this)
HTCFAN0923 said:
It goes to the Tri-Color Screen but stays there..I'll go ahead and research it so I can find the original AT&T and load it up...It shows a lot..workin for at&t and being a member on xda...U guyz have no idea how ya make life easier for my tilt customers b/c at&t truly dropped the ball on the rom...and by offering alternatives..u make the user experience so much better...thanks!
Click to expand...
Click to collapse
Oddly enough the "Original" Tilt ROM will not install on a Tilt that does not already have HardSPL on it (to spell it out for you, the CID of the ROM does not match the Tilt's stock SPL). If you check the "reverting back" sticky you'll find all this info already, though it is deep in the thread.
The AKU v.0.4.4 ATT Beta ROM does have the correct CID and will flash on a stock Tilt. SO that is what you are forced to resort to at this point. Once you get the beta ROM installed you can (and probably should) install HardSPL.
After all that, if you decide you want to return or warranty the phone follow the "revert" thread to restore it to "stock" form.
Some additional notes on your problem...
ActiveSync will not connect in Bootloader mode (this is expected). You should see a device show up in Device Manager however, I can't recall the exact description however.
quick flash procedure:
put phone in bootloader
connect usb cable
install ROM
FYI, the problem may not be a bricked tilt... you could try Pof's fix which involves using MTTY.exe to boot the phone, depending on how your "customer" tried to flash it it may just need a kick in the pants to restore it. (search Pof's SSPL for the Kaiser thread for instructions, the thread was closed so you will have to look deep).
<climbing on my soapbox>
Lastly... your use of the word "customer" concerns me... are you charging people for the work you do to their phones? If so, do you donate to the people who make it possible? I'm probably just misunderstanding you, but if you're profiting from others work, perhaps you should contribute (especially if you're coming here to ask for help).
</climbing down>
Good Luck!
Cheers.
Customers as in I work for an AT&T corporate owned Retail location and they have bought Tilts from me. They kno my Tilt has been modded and they usually want to do the same. I don't charge them for doing mods to their Tilts. This still remains a community where we help each other and I cherish that. Greed has no place here.
as far as ur suggestions...It looks like I'm gonna be drunk @ 4am on XDA tonite...lol...
HTCFAN0923 said:
Customers as in I work for an AT&T corporate owned Retail location and they have bought Tilts from me. They kno my Tilt has been modded and they usually want to do the same. I don't charge them for doing mods to their Tilts. This still remains a community where we help each other and I cherish that. Greed has no place here.
Click to expand...
Click to collapse
That's cool... my misunderstanding then. Hopefully no hard feelings .
All in all it sounds like the guy wants a custom ROM so you should probably get the ATT Beta ROM and install that. And then install HardSPL.
Check Kyphur's second post in the thread below for the ROM you want.
http://forum.xda-developers.com/showthread.php?t=343198
Thanks for the info sycho...I'll get to it after work..
Good news! The AKU 0.33 worked! Thanks for ur help sycho!
how can i re-install the window? at tilt 8925
i have wm6.1
i want to reset it so the error message shud gone like Recover ?
@kaal,
It seems what you want to do is a HARD RESET. Please visit Kaiser Wiki and read through. You'll know your phone better that way.
@HTCFan & Sirsycho, Glad you both sort it out in the community spirit Cheers!
sirsycho said:
Oddly enough the "Original" Tilt ROM will not install on a Tilt that does not already have HardSPL on it (to spell it out for you, the CID of the ROM does not match the Tilt's stock SPL). If you check the "reverting back" sticky you'll find all this info already, though it is deep in the thread.
The AKU v.0.4.4 ATT Beta ROM does have the correct CID and will flash on a stock Tilt. SO that is what you are forced to resort to at this point. Once you get the beta ROM installed you can (and probably should) install HardSPL.
After all that, if you decide you want to return or warranty the phone follow the "revert" thread to restore it to "stock" form.
Some additional notes on your problem...
ActiveSync will not connect in Bootloader mode (this is expected). You should see a device show up in Device Manager however, I can't recall the exact description however.
quick flash procedure:
put phone in bootloader
connect usb cable
install ROM
FYI, the problem may not be a bricked tilt... you could try Pof's fix which involves using MTTY.exe to boot the phone, depending on how your "customer" tried to flash it it may just need a kick in the pants to restore it. (search Pof's SSPL for the Kaiser thread for instructions, the thread was closed so you will have to look deep).
<climbing on my soapbox>
Lastly... your use of the word "customer" concerns me... are you charging people for the work you do to their phones? If so, do you donate to the people who make it possible? I'm probably just misunderstanding you, but if you're profiting from others work, perhaps you should contribute (especially if you're coming here to ask for help).
</climbing down>
Good Luck!
Cheers.
Click to expand...
Click to collapse
Because of you folks and this thread, I have a working device as opposed to a paperweight...Thanks!!!
Hi,
Was changing the ROM on my Kaiser, using JUMPspl as I had got the white screen using Hardspl. During the upgrade got an error at about 18%, went through the recovery procedure only to get back to the Bootloader screen with the screen saying
SPL-1.93.0000
I think it should say something different here!
At the moment can only get the the tri-colour bootloader screen with usb at the bottom.
Please any help would be much appreaciated.
Thanks
If you are at the tri-color bootloader screen, reflash a ROM.
that's where the process starts at anyhow,the bootscreen.
But doesn't the SPL have to be either Hardspl or jumpSPL.
I have tried to do the rom update again but sticks on 0% and gives error 262
Alemaker said:
If you are at the tri-color bootloader screen, reflash a ROM.
that's where the process starts at anyhow,the bootscreen.
Click to expand...
Click to collapse
Not advisable if he has the default SPL still though which by the number appearing at the tri col screen it appears to be the case.
Try doing a hard reset and see if it boots into the original ROM then at least you will find out if it is bricked or not, however, i'm not sure it will work based on the fact you got part way through in the first place.
Hold down the keys directly next to the Send and End (green and Red) Hold in the stylus and keep them all held untill you get a screen telling you to press the green (send) key.
Tried the hard reset, takes me back into the bootloader. Any other ideas?
Hmm... ok then.... you are pretty much looking at a very expensive paperweight at this moment in time then.
Look at this thread...it "may" (i'm not promising anything but it may point you in the right direction) help you out. Let us know how it goes.
http://forum.xda-developers.com/showthread.php?t=361612&highlight=bricked
cmcmill01 said:
Hi,
Was changing the ROM on my Kaiser, using JUMPspl as I had got the white screen using Hardspl. During the upgrade got an error at about 18%, went through the recovery procedure only to get back to the Bootloader screen with the screen saying
SPL-1.93.0000
I think it should say something different here!
At the moment can only get the the tri-colour bootloader screen with usb at the bottom.
Please any help would be much appreaciated.
Thanks
Click to expand...
Click to collapse
Hate to joint the parade, but the exact same thing happened here - 18% now stuck at 1.93.0000
For anyone else reading this BEFORE flashing a new ROM please read, read and read again EVERYTHING related to flashing on this site, wikis and wherever else you can get info.
Another idea for you. Search around here for how to flash from an SD card that may solve the issue out for you. As previously noted though....READ READ READ and be 110% certain you understand what you are doing before you do anything.
http://forum.xda-developers.com/showthread.php?t=276963&highlight=stuck+bootloader
details some info for a Wizard, should it be the same for a Kaiser?
Will Mtty get me any further?
MTTY will at least give you a USB connection to the device it is worth a shot given your current situation.
There is hope!
I did a clean reboot of my PC and disabled my antivirus (avast) and was able to sucessfully reflash the new 1.62 rom (released from ATT site today).
Thanks will try the new 1.62 rom.
What commands can you use with MTTY?
tried the At&t rom gives me an error on the vendor id. Will try a HTC rom
I have tried multiple roms and they all give me the same error Error 294:Invalid Vender ID
Any ideas
Am starting to get worried because if the misses finds out that I have bricked the new phone, I am up to my neck i it.
If you are stuck in boot loader & would like some help via MSN Messenger, please PM me or look for me on MSM messenger at [email protected]. I will be available to help later this evening or tomorrow morning.
I have most of the files to fix these issues & can use MSN fileshare folders to help you.
Good chance that you can be up again in a matter of minutes
cmcmill01 said:
I have tried multiple roms and they all give me the same error Error 294:Invalid Vender ID
Any ideas
Am starting to get worried because if the misses finds out that I have bricked the new phone, I am up to my neck i it.
Click to expand...
Click to collapse
Invalid Vendor I.D. is cuz it's locked.
Had the exact issue myself and found a ATT ROM that will boot. It saved me bigtime, so I saved it. It's in one of the posts on one of the threads but I have the actual ROM, it'll overide that lock.- PM me if ya need it.
Got the same solution, Holy S**t about to have a heart attack. Tried nearly ever ROM out there, it was the Asia one that got me going.
Lesson learned: make sure you Hardspl after jumpspl.
Thanks for all the help folks
Glad ya got it fixed. One quick question?
Is your original ROM ATT or HTC ?
It is a HTC ROM. Done My Hardspl and got Sleuth v3.0 on it already
Happy days
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...