Database Info

Newbie, Got the RAW files off Ozone

Ok, trying my best using the search engine, lol. I got the dump using the correct memory locations
Part 00 3.12mb 0x31f000
Part 01 3.38mb 0x360000
Part 02 88Mb 0x5800000
Part 03 91mb 0x5b00000
So I have 4 part0?.raw files. How do I put them together correctly, then is there a consolidated location to send the file to for use by everyone.
This is a stock new rom from verizon

What build is this? Could you upload them?

does this mean that someone will be able to build a decent rom off of this?
what exactly are "raw files"?

SoCalSpecialist said:
does this mean that someone will be able to build a decent rom off of this?
what exactly are "raw files"?
Click to expand...
Click to collapse
Building a ROM is one thing. Getting it to flash onto the phone is another. Understand that our phones are CID locked to the specific carriers meaning that you can't just flash ANY cooked ROM. I am working on a JumpSPL for the Maple with JockyW. Once thats ready we can "trick" the phone into thinking the ROM is signed and flash any part of the phone we want.

Were should I upload them to?
the phone says OS 5.2.21041 (Build 21043.1.6.2)

ookba said:
Building a ROM is one thing. Getting it to flash onto the phone is another. Understand that our phones are CID locked to the specific carriers meaning that you can't just flash ANY cooked ROM. I am working on a JumpSPL for the Maple with JockyW. Once thats ready we can "trick" the phone into thinking the ROM is signed and flash any part of the phone we want.
Click to expand...
Click to collapse
soo...im guessing the JumpSPL makes the device SPL unlocked?
i havent done that yet, BUT i did notice when first programming the phone thru Verizon it said SPL Unlocked...and also after my first hard reset it said SPL Unlocked, does that mean im ready to go?

SoCalSpecialist said:
soo...im guessing the JumpSPL makes the device SPL unlocked?
i havent done that yet, BUT i did notice when first programming the phone thru Verizon it said SPL Unlocked...and also after my first hard reset it said SPL Unlocked, does that mean im ready to go?
Click to expand...
Click to collapse
Could be. Just have to get my hands on the stock shipped ROM and do a quick build to see.

mbardsley said:
Were should I upload them to?
the phone says OS 5.2.21041 (Build 21043.1.6.2)
Click to expand...
Click to collapse
Just open a quick account with Mediafire.com and ZIP them up and upload the ZIP and post the link. I'd like to get my hands on them too if possible. :-D

Here is the Link, Downloading now.
http://www.mediafire.com/?sharekey=065cff73c99e2c602fb2ca15d7ea42d9e04e75f6e8ebb871

mbardsley said:
Here is the Link, Downloading now.
http://www.mediafire.com/?sharekey=065cff73c99e2c602fb2ca15d7ea42d9e04e75f6e8ebb871
Click to expand...
Click to collapse
Your RAW files were perfect!! I got all the files I need to build an Ozone kitchen now!

Holy christ! Suddenly, I am very exited about the Ozone. I can't wait to see what you cook up.

Me too, give me first shot at bricking my phone, lol

mbardsley said:
Me too, give me first shot at bricking my phone, lol
Click to expand...
Click to collapse
HAHA! Well, some people say their Ozone is CID unlocked because it says SPL unlocked. I created a test RUU if you guys are brave enough to try it. It will only flash the first "Splash" screen and nothing else. If in fact it is CID unlocked out of the box, which I doubt, this should give you the "HTC 3VO SERIES ROMS" black splash after it finishes. It should'nt affect anything else but again, please try at your own risk. The picture will show a TMO Dash 3G because thats the only RUU Utility I have until the Ozone gets a ROM upgrade from the factory. Should still work.
Let me know!

Results of try. Get the rainbow screen, resets into a bootloader, get the % screen on both devices, stayes there.

Lucky no brick, lol pulled battery, and back operational.

yup...same for me.
i let it sit on the percentage screen for about 5 min before i decided to pull the battery.
close...oh so close

SoCalSpecialist said:
yup...same for me.
i let it sit on the percentage screen for about 5 min before i decided to pull the battery.
close...oh so close
Click to expand...
Click to collapse
Yea, well, just like I thought. That means you're CID locked. Bummer. Battery pull will reset it. Also since it went into bootloader and started to flash means we can probably apply the same JumpSPL we're building for the Dash3G for the Ozone as well.
I talked to jockyw2001 and he's free this coming week to finish this so thats good news. Once thats done we'll do some more tests. Almost!!!

Can someone post the RUU.exe please for this

Can someone post the RUU.exe please for this
or the .nbh....

Whosdaman said:
Can someone post the RUU.exe please for this
or the .nbh....
Click to expand...
Click to collapse
There is no "RUU.exe" for the Ozone.

Need to unroot and s-on.

My phone's flex cable is damaged some how and I need to unroot it and turn s-on, anyone able to give me some helpful links? I searched and not sure if anything I found was still viable to use.
I am running 2.3 and have updated radio.

Just run the ruu. You can get the 2.2 ruu from the hboot downgrade thread or the 2.3 here http://forum.xda-developers.com/showthread.php?t=1335068
Sent from my PG06100 using Tapatalk

Thanks, to add to it, my screen now won't come on at all, any one can give me a bit of step by step?

Will the screen come on while in bootloader or it doesn't work at all? Either way, as long as your pc will recognize the phone you should be able to run the RUU exe. Just plug in your phone with it powered on and run the RUU on your pc.

Will that turn my s-off to s-on also?

gigermunit said:
Will that turn my s-off to s-on also?
Click to expand...
Click to collapse
Yup, the RUU will bring you completely back to stock with s-on.

crump84 said:
Yup, the RUU will bring you completely back to stock with s-on.
Click to expand...
Click to collapse
Thank you, I hope this works fine, friend is taking me to the store tomorrow to get it checked to see if they can put in a new cable or send me a new phone, if they tell me any bull I am raising hell, I have taken care of this phone like a new born since I got it and then **** happens.

gigermunit said:
Thank you, I hope this works fine, friend is taking me to the store tomorrow to get it checked to see if they can put in a new cable or send me a new phone, if they tell me any bull I am raising hell, I have taken care of this phone like a new born since I got it and then **** happens.
Click to expand...
Click to collapse
Haha. Well good luck man.

Getting a free replacement so all was well.

[Q] HTC Aria will not boot if plugged in

EDIT: Wrong category, sorry. I'm new.
Rooted Aria/Liberty won't turn on if it's plugged in (wall charger or USB). The orange charging light is on and the screen is lit but black. The menu buttons do not turn on. I have to remove the battery after unplugging it for it to turn on.
The phone is rooted and the problem is consistent no matter what ROM I use. I believe it is a problem with the bootloader, but I'm not very advanced with these things.
I rooted the phone with Unrevoked and whenever I boot into recovery mode it says "Revolutionary CWM v4.0.1.4."
Any suggestions on how to make this problem go away? I know it's minor, but it is my mother's phone and every time I'm on the phone with her she complains about it.

The only way to fix a bootloader issue like this is to reflash the stock one, which you can accomplish by sourcing an HTC RUU (ROM Update Utility) for your Aria. This will flash everything back to stock so you'll lose everything, but it will fix these issues that tend to pop up occasionally
Good luck!

juzz86 said:
The only way to fix a bootloader issue like this is to reflash the stock one, which you can accomplish by sourcing an HTC RUU (ROM Update Utility) for your Aria. This will flash everything back to stock so you'll lose everything, but it will fix these issues that tend to pop up occasionally
Good luck!
Click to expand...
Click to collapse
I just did this and the problem is still occuring. I used the RUU on HTC's website that was the upgrade to 2.2. The process went without a hitch, but it did not do anything except change to the stock Froyo ROM. I checked and it was still Revolutionary's bootloader and the same HBOOT (6.02.1002).
I believe I read that Revolutionary is a protected bootloader and fairly difficult to remove, but I'm not sure. I've been researching this for 11 hours now. I've read a lot. >.< I'm up for a challenge, though, so if you or anyone else have instructions/link on how to replace it, I'll try.

ellaizee said:
I just did this and the problem is still occuring. I used the RUU on HTC's website that was the upgrade to 2.2. The process went without a hitch, but it did not do anything except change to the stock Froyo ROM. I checked and it was still Revolutionary's bootloader and the same HBOOT (6.02.1002).
I believe I read that Revolutionary is a protected bootloader and fairly difficult to remove, but I'm not sure. I've been researching this for 11 hours now. I've read a lot. >.< I'm up for a challenge, though, so if you or anyone else have instructions/link on how to replace it, I'll try.
Click to expand...
Click to collapse
Tried this one mate?

juzz86 said:
Tried this one mate?
Click to expand...
Click to collapse
I followed that and the only thing it did was change the top of the bootloader screen from "Revolutionary" to "AlphaRev Unlock." The hboot is still the same. The problem is still happening.
Is there a way to downgrade my hboot even though it is protected? Heck, I can't even turn S-ON because of that.
NOTE: The major problem I'm running into with all the forum posts I find is that they used megaupload to host their downloads and those links no longer work.

ellaizee said:
I followed that and the only thing it did was change the top of the bootloader screen from "Revolutionary" to "AlphaRev Unlock." The hboot is still the same. The problem is still happening.
Is there a way to downgrade my hboot even though it is protected? Heck, I can't even turn S-ON because of that.
NOTE: The major problem I'm running into with all the forum posts I find is that they used megaupload to host their downloads and those links no longer work.
Click to expand...
Click to collapse
Try flashing this recovery....it happened to my wife's Aria, that whenever the phone was charging off I couldn't turn it on until I pulled the battery...after flashing this everything returned to normal....hope it helps
http://forum.xda-developers.com/showthread.php?t=1025704

glevitan said:
Try flashing this recovery....it happened to my wife's Aria, that whenever the phone was charging off I couldn't turn it on until I pulled the battery...after flashing this everything returned to normal....hope it helps
http://forum.xda-developers.com/showthread.php?t=1025704
Click to expand...
Click to collapse
You are MAGICAL. Thank you so much! And thanks to juzz86 for the suggestions as well.
I used fastboot to flash the recovery and now it does the normal battery image when the phone is off and charging.

No problem. When that happened to me, I panicked but after a couple of google searches I came across that...glad you solved it.
Sent from my Inspire 4G using XDA

All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.

ellaizee said:
All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.
Click to expand...
Click to collapse
hahaha sorry for that. As u can see, I realised after writing it and erased it, but you probably saw it first.....

ellaizee said:
All of this mate/buddy calling makes me think women aren't a very common occurrence here. I guess I'll have to get used to it.
Click to expand...
Click to collapse
Sorry, no offence intended You'd be surprised how common mate/buddy is in Australia, even when ladies are involved.
In my defence, you can still be a mate or buddy as a female
Take care!

juzz86 said:
Sorry, no offence intended You'd be surprised how common mate/buddy is in Australia, even when ladies are involved.
In my defence, you can still be a mate or buddy as a female
Take care!
Click to expand...
Click to collapse
Even in UK they use mate a lot....but it is no defense for me...I am in Argentina... lol

Reverting OTA?

The latest OTA update has made my phone useless as a
phone, as it now gets no mobile reception...
Is there a way to reverse this upgrade?
My other option is a custom ROM, but i would prefer to stay stock at the moment if at all possible.

you can always run an RUU - One that doesnt contain the update

I was just educating myself on RUUs.
does it matter which one i run? i think my phone is unlocked/unbranded (i bought it second hand) but i'm not sure
EDIT: Nevermind, i checked my baseband against the list of RUUs and found that it is in fact unbranded. Now i know which one to get... just need FileFsctory to let me get it...

which is it you need ? Chances are there's a mirror somewhere

found a mirror, thanks

back to start... i tried to install the 1.53 version and it game an error 140 (bootloader)

I think its because the OTA updated the bootloader !
you cannot downgrade using RUU unless you have S-OFF

Well, i guess i'll have to root and install a custom ROM.
Thanks for the help!

what part do you want to revert ? The radio update ? Cause if so, there is a way to do this

Yeah, the radio. When i was 0.15 radio it worked, now with 0.16 it doesn't

Ok have a look at this http://forum.xda-developers.com/showthread.php?t=1684477
I dont think you have to have CWM installed on your device, You just need it on your PC, So you can boot into it.

Thanks! can't seem to find a 0.15 radio though

kuroyume_cl said:
The latest OTA update has made my phone useless as a
phone, as it now gets no mobile reception...
Is there a way to reverse this upgrade?
My other option is a custom ROM, but i would prefer to stay stock at the moment if at all possible.
Click to expand...
Click to collapse
OP does know the consequences of rooting devices right? It avoids your warrenty.
So just want to make sure, do you not get reception anywhere or only at certain area? If the former, it may indicate a fault on your phone caused by the update and you should not deal with it by rooting cos there is a chance rooting and downgrading may not fix it then you would have no where to go. The right move IMO, is to take the phone back to point of sale and demand an exchange. Most of users like me do not have such problem after update.
Just to remind, if you know what you are doing, by all means.
Sent from my HTC One S using XDA

kuroyume_cl said:
Thanks! can't seem to find a 0.15 radio though
Click to expand...
Click to collapse
extract it from an ruu

h.han said:
OP does know the consequences of rooting devices right? It avoids your warrenty.
So just want to make sure, do you not get reception anywhere or only at certain area? If the former, it may indicate a fault on your phone caused by the update and you should not deal with it by rooting cos there is a chance rooting and downgrading may not fix it then you would have no where to go. The right move IMO, is to take the phone back to point of sale and demand an exchange. Most of users like me do not have such problem after update.
Just to remind, if you know what you are doing, by all means.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
The point of sale is a few thousand kilometers away
No warranty in my country, so i have to figure this out by myself
I have rooted and installed roms on previous phones, but this one seems more... complicated
azzledazzle said:
extract it from an ruu
Click to expand...
Click to collapse
how? (sorry about all of this, but never had an HTC before)

kuroyume_cl said:
how? (sorry about all of this, but never had an HTC before)
Click to expand...
Click to collapse
Look here http://www.freeyourandroid.com/guide/extract-rom-from-ruu once extracted the rom.zip, open it up and take out the radio.img.
put it in the place where you keep all your adb stuff. and flash it using the method linked a few posts back

Went though the whole process but baseband version still reads 0.16xxxxxxxx
It doesn't seem to have worked

Well, at this point i'm fairly certain i need to rollback my radio, as i installed CM9 and still no cell signal. I checked and it had the same baseband as the 1.78 ROM.

Bricked HTC One X

Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.

Andrew10567 said:
Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Click to expand...
Click to collapse
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck

tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....

Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Don't panic.right now there is no solution.There will be one soon.
GOOD LUCK

Wrong section ...... And not to be a **** the but hahaha people really need to Stop and read
Sent from my Nexus 7 using Tapatalk 2

Andrew10567 said:
Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Taking the time to research before flashing a ROM that is not even meant for your phone would have saved a lot of heartache:
http://forum.xda-developers.com/showthread.php?t=1974101

I thought the ICJ Bricking Crew was no more. I guess those clowns are trying to make a comeback.

tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
I have downgraded using JET from 1.14 to 2.20. Process includes bricking your phone to get into special recovery mode that give RW access to hboot, but you do need TWRP at some point I think (not sure though) to get in bricked, before you start downgrade, so you might not be able to downgrade.
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
OP gives you there way to verify that device is connected and part of the steps is listing partitions. If you can get partitions listed on your PC, then I think you can just dd system image and it should come back to life... also have you tried 2.20 RUU? I had a corrupted system partition (bad sector causing reboot when I would try to access system - including booting phone or into twrp recovery). I ended up using RUU (which also failed from the same bug, but It actually reformatted my system partition giving me access to twrp and then I was able to restore).

http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2

Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Lol. wow kid.
Sent from my HTC One XL

rpomponio said:
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It hurts to laugh so hard.

igagnidz said:
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
Click to expand...
Click to collapse
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.

iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Sent from my One X using xda premium

Myrder said:
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Click to expand...
Click to collapse
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.

iElvis said:
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
Click to expand...
Click to collapse
I don't ever wipe /system when flashing ROMs. It gets wiped when you flash anyway. I always wipe user data (factor reset), Dalvik and cache. But that's it.

iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
Yep, if you format /system, the build.prop is gone, and the assert looks to the build.prop.. why it flashes, I don't know.
The way its set up seems like it would only flash if "ro.device=endeavoru" or whatever the line is, is present. I guess there is no fail safe to stop the process if the build.prop isn't present

Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.

Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They do and you're not the first to ask. I think they just swap up the motherboard.

Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They can fix any software corruption they have the tools too they know their phones front to back and can rewrite anything to them...just tell them what happened and they'll tell you the cost( maybe they'll feel bad and give a nice price) honesty can get you in good places sometimes

Thanks. Will send everyone who replied a thank button. Regardless of what type of comment...... I'll need to check the cost. Hopefully its below 100....