Develop Bugs

[WARNING] Do not flash a new official RUU/ROM/OTA if you have root and/or S-OFF

DO NOT FLASH A NEW RUU OR OFFICIAL ROM IMAGE UNLESS YOU *REALLY* KNOW WHAT YOU ARE DOING !
Sorry for shouting, but this is very important. Thanks to the mods for making this sticky.
The latest official RUU that has been released - http://forum.xda-developers.com/showthread.php?t=870369 - has been found to break the existing methods of rooting and getting full S-OFF.
This shouldn't be a big suprise, because when HTC saw that the amazing devs on XDA had cracked the existing security, we should expect them to put something even tougher in later releases.
So flashing any later release, whether that's an official RUU or just the ROM image (PC10IMG.zip) is a very dangerous thing to do until it has been fully tested and "cleared" by the devs here. i.e. your previously rooted and S-OFF'd phone might lose root and go back to S-ON, and be unable to be rooted and S-OFF'd again.
It's of course fine if your phone came with a particular ROM release to flash that *exact same* release back onto the phone if you want to return to stock. What I'm referring to is flashing a brand new release that isn't the one that came with your phone.
It's fine to flash custom ROMs of course, because those have already been tested out. In general, it's probably best to steer very clear of new official releases, and wait till the devs have pulled them apart and put any cool new stuff into a custom ROM. Then you know it'll be safe to flash.
Currently I don't think it's entirely clear what just flashing a new *radio* on its own will do, as opposed to the entire ROM/RUU. That's still being worked on. But steer clear of even that if you're not sure what you're doing or dont' want to take any chances of losing root/S-OFF.
Thanks for reading

Thanks for the heads up.

I flashed the ROM you mentioned.
For those who want to try:
Just remember to get REAL S-OFF using gfree before flashing it.
This provide you a medicine for regret. You can get back to WWE ROM using WWE RUU and root/recover your old ROM.

What is RUU? What is it to do with ROMs? Did HTC provide a change log for newer Radio? Or does anyone know what changes are , in the latest Radio?
Just to be clear. Don’t flame me for this please. I’m still learning just like many others in here.

androidtoy09 said:
What is RUU? What is it to do with ROMs? Did HTC provide a change log for newer Radio? Or does anyone know what changes are , in the latest Radio?
Just to be clear. Don’t flame me for this please. I’m still learning just like many others in here.
Click to expand...
Click to collapse
We don't have a changelog, no.
RUU is ROM Update Utility. It's a program to run on Windows (.exe) which flashes your new ROM for you, and holds your hand through the process. It's possible to extract just the ROM zip file from the exe so you can flash it yourself if you want.
The thing about the RUU and stock ROMs is that they will flash pretty much *everything* on your phone. So as well as a new system partition (the main stuff for Android), you'll probably get a new hboot, new radio, new recovery. Those *might* all have increased security which is a lot more difficult to crack. So generally you should not flash it until we know it's "safe" to do so, i.e. it can be re-rooted and S-OFF'd etc.

steviewevie said:
We don't have a changelog, no.
RUU is ROM Update Utility. It's a program to run on Windows (.exe) which flashes your new ROM for you, and holds your hand through the process. It's possible to extract just the ROM zip file from the exe so you can flash it yourself if you want.
The thing about the RUU and stock ROMs is that they will flash pretty much *everything* on your phone. So as well as a new system partition (the main stuff for Android), you'll probably get a new hboot, new radio, new recovery. Those *might* all have increased security which is a lot more difficult to crack. So generally you should not flash it until we know it's "safe" to do so, i.e. it can be re-rooted and S-OFF'd etc.
Click to expand...
Click to collapse
Ok, thanks for clearing it up. So, RUU is pretty much similar to the method RIM uses to flash its OS on the Blackberries.

Im a little confused here.. So just to clear some things up i hope someone will answer these questions i have.
I have the software on my Desire Z that it came with (1.34.405.5), which i've rooted, S-off'ed and installed another kernel for OC porpuses. This is working fine, but lets say that i wanted to try another rom .. After some time i decide to go back to the stock software and then update to the newest software, would that be a problem? And has HTC released some newer software than the one iam using?

If you flashed back to stock, that would be fine. But if you flashed a new official update (e.g OTA), then you run the risk of installing something that you can't root/S-OFF.
It is best to steer clear of any official upgrades until they've been checked by the devs here and been given the all-clear.
Given that the phone came with certain areas write-protected, and the devs managed to crack that, we should be expecting HTC to release an even more secure update.
Yes, there is a new ROM out, at the moment for Egypt, that seems to have increased security. It would not be a suprise if HTC rolled out similar security as an OTA update for all existing ROMs. Right now there is something in that Egypt ROM (probably the hboot, at the minimum) which mean existing permanent root and S-OFF methods fail. It may be this is easily cracked again, or maybe it will take some time, who knows.
Bottom line - don't apply any official updates to your phone if it is rooted/S-OFF or you plan to root/S-OFF.
Sent from my HTC Desire Z

perm-rooted g2 stock tmobile rom s-off
ok, my question is....i perm-rooted my g2 and have s-off, does this mean that i cant except the new gingerbread OTA update? ive had my fill of flashing roms with my old windows phone.. att tilt, tmobile touch pro 2, and tmobile hd2. im not looking to flash my g2 with a new rom...no offense to the chefs. love there work. but i only rooted the g2 to get rid of the bs apps that tmobile and google added to the phone. and i thought i heard that wen u root the phone tmobile cant tell wen u tether, so there for no more throttle b/s but thats not true...i must have miss read. but i would like to stay w/the stock rom and still b able to install the Gingerbread OTA. please someone provide an answer for me or point me in the right direction. thank you in advance.... sorry if the answer is already provided somewhere and i over looked it, i tend to do that a lot.

blitz69 said:
ok, my question is....i perm-rooted my g2 and have s-off, does this mean that i cant except the new gingerbread OTA update? ive had my fill of flashing roms with my old windows phone.. att tilt, tmobile touch pro 2, and tmobile hd2. im not looking to flash my g2 with a new rom...no offense to the chefs. love there work. but i only rooted the g2 to get rid of the bs apps that tmobile and google added to the phone. and i thought i heard that wen u root the phone tmobile cant tell wen u tether, so there for no more throttle b/s but thats not true...i must have miss read. but i would like to stay w/the stock rom and still b able to install the Gingerbread OTA. please someone provide an answer for me or point me in the right direction. thank you in advance.... sorry if the answer is already provided somewhere and i over looked it, i tend to do that a lot.
Click to expand...
Click to collapse
The trouble is, HTC/T-Mobile don't want you to root and/or S-OFF your phone, because it's a lot easier to end up bricking the phone if you don't know what you're doing. They put greatly increased security on the G2/DZ/DHD when they came out, in order to help prevent this.
Now this security has been cracked, we can expect HTC/T-Mobile to try and increase security even further (e.g. closing loopholes that let our current methods of root/S-OFF work) in future updates.
So if you accept any future OTA, you run a high risk of accepting something that will lock you out of root and S-OFF, at least temporarily, and possibly permanently (depending on how good a solution they come up with).
If you are not bothered about root/S-OFF, then that's fine of course.
This doesn't mean that you necessarily have to switch to a custom ROM to get updates though. If you stay with the stock ROM (and I'm still on a stock ROM too right now), then just do not accept the update when an OTA comes out, and keep checking these forums to see when the devs say that they can root/S-OFF with the new version. When they say it's ok then you know you can apply the update and still get root/S-OFF.
This already happened with the G2. Very soon after release, but after rooting had been achieved, there was an OTA. Most people here decided to wait until the OTA had been looked at, and sure enough there was a small adjustment needed to the rooting method. But of course this OTA was before HTC had a chance to respond to the cracking of the security, so as I said, any future updates may well require a lot more time and effort from the devs to investigate and crack again.

Ok. Thank you very much

Will this muff up my phone if I factory reset it by using the Power+Volume Down option?

Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!

Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
What do you mean with gfree?
Is my waranty broken When i execute radio s-off?
Is it possible to make it radio s-on?

Yes,warranty is broken,but with the new gfree method
you can go back to S-ON:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2

ericjosepi said:
Will this muff up my phone if I factory reset it by using the Power+Volume Down option?
Click to expand...
Click to collapse
If you do a factory reset then I think you'll lose root, but you can get it back again easily enough. The issue for this thread is flashing new updated stuff from HTC etc.

Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
You might still need that backup, e.g. if you don't know what your old CID was and you want to un-do that bit too. I would keep it.
Sorry I don't think I understand your last question though, or why you say the uberroot method (I'm personally not keen on that name, it's just the usual method using Visionary/rage with gfree, not a new method) doesn't work.

Ok,so I can go back to S-ON with gfree commands from here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
If you are only interested in permanent root you only need radio S-OFF and then it is sufficient to use
# ./gfree -s off
instead of
# ./gfree -f
in the following commands.
And gfree can now also be used to set radio S-ON by using the "-s on" option and to change the CID back to the original value be using i.e. "-c T-MOB010" if you want or have to go back.
Click to expand...
Click to collapse
But for CID (you mean SuperCid right?) I need the backup?
And with the last question which you don`t understand,I mean
with flashing the HTC RUU 1.34.405.5 I don`t go back to S-ON
and original CID whether I use UBERROT method or this from here:
(Rooting the Vision (G2/DZ) and DHD)
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2

Thanks for the advice, I will stick myself with the current rom for a while

Ganii said:
Ok,so I can go back to S-ON with gfree commands from here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
But for CID (you mean SuperCid right?) I need the backup?
Click to expand...
Click to collapse
Yes, I mean to go from your SuperCID back to your regular CID. You might not know what your original CID was.
And with the last question which you don`t understand,I mean
with flashing the HTC RUU 1.34.405.5 I don`t go back to S-ON
and original CID whether I use UBERROT method or this from here:
(Rooting the Vision (G2/DZ) and DHD)
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Click to expand...
Click to collapse
Yes, if you flash a stock ROM then it won't affect your S-OFF and CID status (or SIM unlock). These are stored in your radio configuration partition, and not in any of the partitions which are overwritten by the ROM flash.

[Q] First Time Flashing and Bricking It!

Right please forgive my noobishness (is this even a word?) but Im really worried about flashing my phone for the first time.
I have partitioned my card, titanium backed up and created a nandroid back up now all thats left is flashing.
Im planning to flash this rom: http://forum.xda-developers.com/showthread.php?t=768703
What I am worried about is bricking it without lack of knowledge of radio files and how to properly do it. Something about GSM and CDMA?
Plus I saw in the thread this: "Use either Amon RA or clockworkmod Recovery < also available via rom manager from the market"
Why do I need to use them?
Help please preferably with a step-to-step guide?
Thanks in advance.

Read this:
http://forum.xda-developers.com/showthread.php?t=696189

Do I need to switch S-off?
Do I need to flash the radio files and what is the difference if I do or not?
Plus should I use ROM Manager to install the new ROM?

Wait just noticed my current baseband version is one you can download from the Leedroid site, so does that mean I dont have to flash a radio file?

you never MUST flash radios, it is only a possibility
my advice, since you are obviously new to this, dont change radio, i used the radio that came with the phone since december and it worked OK.
usually you should consider upgrading your radio if it doesnt work well e.g. bad reception, data or wifi problems etc.
when you are more confident with flashing, go S-OFF (which is super easy, seriously) and learn to use FASTBOOT which is the safest method of flashing radios or recoveries

[Q] RIL Firmware Drivers

Hi everyone,
I'm new at xda developers, and I recently started experimenting with rooting, custom ROMs, etc. I have a question about the RIL firmware drivers. Hope you guys can help me out.
Lately I've been following the progression of baadnewz's InsertCoin ROM (http://forum.xda-developers.com/showthread.php?t=1016940), a Desire port of the Desire S ROM (with sense 2.1); you probably already know it. I want to give it a try, but - coming from CM7/prerooted stock roms - I noticed that baadnewz recommends upgrading the radio to the latest version, as well as the ril-firmware-drivers.
I understand the RIL is some kind of mediator between the ROM and the radio. Therefore, is it true that a specific RIL can only be used with a corresponding ROM (version), or has the ROM nothing to do with it? The reason I'm asking this question is because I want to make sure the newer radio+ril will still work in case I decide to return to my old stock ROM. And in general, is it ok to presume that a newer radio+ril will be at least as good as an older radio, regardless of the ROM installed? (I've never upgraded my radio btw)
Thank you!

RIL is not neccesary, use it if things dont work well, it may improve situation, but it is likely that you will have to experiment till you found one that works best for your phone & rom & radio.
RIL is stored in ROM part, so every time you change ROMs, RIL you flashed is gone.
also you do not need to upgrade your radio, do it only if stuff doesnt work fine after flashing a custom ROM.
you also mentiond coming back to stock rom - when you ran a RUU, it also flashes a RADIO and a RIL, so no worries there
every radio comes with its own RIL, but experience showed, that not necessairly they work well together when it comes do diffrent devices on diffrent networks and diffrent roms.
so - flash your rom, if it is ok that leave things be, if not - upgrade your radio, and then you can start flashing RILs
remmember to make NANDROID before flashing RIL and also that in order to flash RIL you must mount \system in recovery.
radio flashes are safest from fastboot if you are S-OFF, if not you can do them from recovery

Thank you for your reply, really appreciate it
I have one last question, just out of curiosity.. You mentioned that radio flashes are safest from fastboot. Why is that?
I'm still S-ON so I won't be able to use fastboot for flashing... Would you recommend S-OFFing to minimize the risk of bricking my phone, in case I decide to flash a new radio?
Thnx

well you can flash radio from recovery, lots of ppl do that without any problems. i never tried it myself.
i think fastboot method is safer since it doesnt involve rebooting your phone during the procedure but not sure how exactly is this safer, it just has been stated many times, that flashing radio fastboot method is SAFEST.
anyway going S-OFF (cd method i used) is super easy, just be sure not to have a2sd+ or data2xxx rom while doing that.
oh and apart from minor advantages like changing your splashscreen or the ability to delete apps from \system while booted up in android there is one BIG advantage - the option to use custom partion table. I am running InsertCoin v19 on CM7 hboot version, and is not only super fast but also it provides lots of space for apps
it definietly faster than insertcoin HD data2ext i used before going S-OFF

[Q] Must I downgrade?

Hello,
I have Android 2.3.3 right now on my Desire HD and the following:
HBOOT 0.85.0024
RADIO 26.09.04.11_M2
Software number: 2.36.405.8
Kernal: 2.6.35.10-g0956377
Is this good enough to install a custom rom? (currently I have my sight set on LeeDroid) or must I downgrade? If so; is there a tutorial for it?

You don't need to downgrade, just check that your device's rooted and S-off (many tutorials around)
Check if your Radio is fine with the rom (though it includes its own radio)
But it seems fine.
If you really don't know and want to be sure, send a pm to Lee, he'll tell you all about his rom and if you can upgrate
(You'll probably have to wipe to ext4.

Well alright. I'm going to root it now etc.

neodesco said:
You don't need to downgrade, just check that your device's rooted and S-off (many tutorials around)
Check if your Radio is fine with the rom (though it includes its own radio)
But it seems fine.
If you really don't know and want to be sure, send a pm to Lee, he'll tell you all about his rom and if you can upgrate
(You'll probably have to wipe to ext4.
Click to expand...
Click to collapse
ROMs do not include, normally, there own radios as amatter of course I would stick with your current radio and change it only if you have problems

I'm trying to temproot, but the screen just stays black. And once I press home, I can't get back into visionary+

ghostofcain said:
ROMs do not include, normally, there own radios as amatter of course I would stick with your current radio and change it only if you have problems
Click to expand...
Click to collapse
Depending on your needs, it could be better to stick the the creator's rom and radio. It doesn't change that many things.
@impy101 : Your Kernel will be upgraded too but it's fine
Follow a tutorial and backup before doing anything ^^
This one seems fine : http://forum.xda-developers.com/showthread.php?t=841076

neodesco said:
Depending on your needs, it could be better to stick the the creator's rom and radio. It doesn't change that many things.
@impy101 : Your Kernel will be upgraded too but it's fine
Follow a tutorial and backup before doing anything ^^
This one seems fine : http://forum.xda-developers.com/showthread.php?t=841076
Click to expand...
Click to collapse
The radio is HTCs not the rom creators and isn't flashed when installing a rom it must be done seperately

Well i'm trying to temproot, but eveytime the screen just goes black (I can still see the battery etc) and once I press home it goes back to the home android screen, but I can no longer start up visionary+
What do I do?

Personally I'd try rooting by hand, have a look at the instructions on the cyanogen wiki pages

If your device is not S-OFF yet, you can not root 2.36 with visionary. You have to downgrade to 1.32.
http://forum.xda-developers.com/showthread.php?t=905003

[Q] CID, firmware, jellybean etc...

Hi all,
I have installed RD-MIUI Jelly Bean 4.1.2 (http://miuiandroid.com/community/th...-bean-4-1-2-2-11-16-en-cm10-16-11-2012.17645/) on my HOX and it is working fine (a few bugs, but they are known).
My question is: why could I install it in the first place??? I didn't touch the hboot, but for many roms it looks like I need to upgrade it.
Why, for example; I am not supposed to be able to install Android Revolution HD 15?
See:
http://forum.xda-developers.com/showthread.php?t=1843585
http://forum.xda-developers.com/showthread.php?t=1957376
http://forum.xda-developers.com/showthread.php?t=1843585
My CID is HTCCN701 - so no firmware for it.
Can someone can explain to me how:
cid
hboot
kernel
rom
are related? And, although I understand the word and the wiki description, maybe a bit of explanation of what are concretely these entities, like which file is responsible for what, how these are layered, etc... I have a programming background, but I am still a bit lost concerning the architecture of android and its devices...
Thanks in advance!

froal said:
Hi all,
I have installed RD-MIUI Jelly Bean 4.1.2 (http://miuiandroid.com/community/th...-bean-4-1-2-2-11-16-en-cm10-16-11-2012.17645/) on my HOX and it is working fine (a few bugs, but they are known).
My question is: why could I install it in the first place??? I didn't touch the hboot, but for many roms it looks like I need to upgrade it.
Why, for example; I am not supposed to be able to install Android Revolution HD 15?
See:
http://forum.xda-developers.com/showthread.php?t=1843585
http://forum.xda-developers.com/showthread.php?t=1957376
http://forum.xda-developers.com/showthread.php?t=1843585
My CID is HTCCN701 - so no firmware for it.
Can someone can explain to me how:
cid
hboot
kernel
rom
are related? And, although I understand the word and the wiki description, maybe a bit of explanation of what are concretely these entities, like which file is responsible for what, how these are layered, etc... I have a programming background, but I am still a bit lost concerning the architecture of android and its devices...
Thanks in advance!
Click to expand...
Click to collapse
Upgrading the hboot is only required for Sense-based Jelly Bean ROMs. You will not require an upgraded Hboot to use AOSP/AOKP/CM10 based ROMs.
CID - basically just identifies region/carrier of phone
ROM - variations of the android OS, usually comes with custom software/tweaks etc.
Hboot - not too sure, but different versions have an effect on wifi, reception.
kernel - basically a component that serves as the bridge between software and hardware and allows them to communicate between each other.

tomascus said:
Upgrading the hboot is only required for Sense-based Jelly Bean ROMs. You will not require an upgraded Hboot to use AOSP/AOKP/CM10 based ROMs.
CID - basically just identifies region/carrier of phone
ROM - variations of the android OS, usually comes with custom software/tweaks etc.
Hboot - not too sure, but different versions have an effect on wifi, reception.
kernel - basically a component that serves as the bridge between software and hardware and allows them to communicate between each other.
Click to expand...
Click to collapse
Just see the hboot as the BIOS on a pc

Guys, thanks for the clarification!
Another question though... How come I would need to upgrade my hboot (keeping the BIOS analogy) so that Jellybean-based Sense can be ran properly? Is that because Sense has access to low layers? From your explanation, I would have thought the kernel would do that job...
Indeed, if we compare to a PC, I usually don't need to upgrade my BIOS when I want to change my OS... Hence the reason why I am confused

Well the hboot (bootloader) part interacts with the kernel and this will talk with the rom....
Because the kernel and rom are updated with the new JB update, it needed an update from the hboot too so it can interact in correct way. I think this is the easiest way to explain it
hboot - kernel - rom.
PLEASE CORRECT ME IF I'M WRONG

I have been unclear about this as well (great question). This sounds like a good explanation (hey Marcel!). But I'm curious as to why my CID is HTC_203 and I'm on ARHD v15.0 and it says in the OP of that rom that I need to "upgrade my firmware" and when I look on the firmware thread http://forum.xda-developers.com/showthread.php?t=1957376 it says that my CID should have hboot 1.31. So, apparently it's not absolutely necessary to have the latest firmware? My rom seems to be working fine. Also, if I now want to use an ICS rom, will my CID/firmware (hboot) be an issue?
Ugh, can't believe how much more complex this phone is compared to my old Nexus! lol (but it sure is beautiful!)

scott62185 said:
I have been unclear about this as well (great question). This sounds like a good explanation (hey Marcel!). But I'm curious as to why my CID is HTC_203 and I'm on ARHD v15.0 and it says in the OP of that rom that I need to "upgrade my firmware" and when I look on the firmware thread http://forum.xda-developers.com/showthread.php?t=1957376 it says that my CID should have hboot 1.31. So, apparently it's not absolutely necessary to have the latest firmware? My rom seems to be working fine. Also, if I now want to use an ICS rom, will my CID/firmware (hboot) be an issue?
Ugh, can't believe how much more complex this phone is compared to my old Nexus! lol (but it sure is beautiful!)
Click to expand...
Click to collapse
You have to check the hboot number if its higher as 1.12 then you have the JB hboot update. A JB rom will run on a lower hboot but that is only for the de-sensed roms !
And hboot number for ICS roms is irrelevant :thumbup:

MarcelHofs said:
You have to check the hboot number if its higher as 1.12 then you have the JB hboot update. A JB rom will run on a lower hboot but that is only for the de-sensed roms !
And hboot number for ICS roms is irrelevant :thumbup:
Click to expand...
Click to collapse
Oh, wow. I see. :good:

Hboot can communicate with the hardware directly and controls all the security of the phone partitions.
Aside from booting the kernel
WiFi and other hardware bugs(dead sensors/sound and touch static electricity) were caused by incompatible hardware code between different hardware versions.
Edit: you only need to upgrade the hboot if you want to install a jb sense rom(stock or custom, restricted by sense+ software)
Sent from my EndeavorU

Vcek said:
Hboot can communicate with the hardware directly and controls all the security of the phone partitions.
Aside from booting the kernel
WiFi and other hardware bugs(dead sensors/sound and touch static electricity) were caused by incompatible hardware code between different hardware versions.
Edit: you only need to upgrade the hboot if you want to install a jb sense rom(stock or custom, restricted by sense+ software)
Sent from my EndeavorU
Click to expand...
Click to collapse
You mean I can flash a non-sense rom such as CM10 on my phone although I don't have a compatible cid?
From what i've read from the guide threads, you're supposed to have a cid similar to "HTC_001" or something like that to be able to flash a JB rom into the HTC one X. Am I wrong?

7ind said:
You mean I can flash a non-sense rom such as CM10 on my phone although I don't have a compatible cid?
From what i've read from the guide threads, you're supposed to have a cid similar to "HTC_001" or something like that to be able to flash a JB rom into the HTC one X. Am I wrong?
Click to expand...
Click to collapse
Yeah. In fact, you're better off not upgrading hboot for non Sense JB.

BenPope said:
Yeah. In fact, you're better off not upgrading hboot for non Sense JB.
Click to expand...
Click to collapse
Hmm, why is it better not to upgrade your hboot? (just curious)
Sent from my EndeavorU using Tapatalk 2

BenPope said:
Yeah. In fact, you're better off not upgrading hboot for non Sense JB.
Click to expand...
Click to collapse
Thanks! My night has just changed.
Would it be too much asking for the best CM10 rom link? I know they're there, but they're a bunch and I'm not really sure which I should flash.
Actually, I think I may flash this one: youtube. com/watch?v=elDvcVot7qo
Good enough?
Thanks again (Incredibly quick answer btw, I'm impressed)

scott62185 said:
Hmm, why is it better not to upgrade your hboot? (just curious)
Click to expand...
Click to collapse
Depending on which version you can go to, you might have problems. 1.33 and 1.36 should be ok, but with earlier versions you might find bugs.
Also, if you update it, for non Sense ROMs, you'll need a non standard boot.img, and at the moment, most of them don't work with GPS.

7ind said:
Thanks! My night has just changed.
Would it be too much asking for the best CM10 rom link? I know they're there, but they're a bunch and I'm not really sure which I should flash.
Actually, I think I may flash this one: youtube. com/watch?v=elDvcVot7qo
Good enough?
Thanks again (Incredibly quick answer btw, I'm impressed)
Click to expand...
Click to collapse
i would personally go for the official CM10(4.1.2) nightlies at cyanogenmod.com because i don't mind flashing a daily new update(doesn't require wipe data). I had defy with CM10 and as fast as I noticed any bug it was fixed in the next day's release. But I don't recommend this if you are looking for a permanent rom.
---------- Post added at 04:48 AM ---------- Previous post was at 04:45 AM ----------
BenPope said:
Depending on which version you can go to, you might have problems. 1.33 and 1.36 should be ok, but with earlier versions you might find bugs.
Also, if you update it, for non Sense ROMs, you'll need a non standard boot.img, and at the moment, most of them don't work with GPS.
Click to expand...
Click to collapse
I would like to add that the chance of finding a security hole in newer hboots is smaller , and I bet that no one would want to miss applying an S-OFF exploit.

Vcek said:
i would personally go for the official CM10(4.1.2) nightlies at cyanogenmod because i don't mind flashing a daily new update(doesn't require wipe data). I had defy with CM10 and as fast as I noticed any bug it was fixed in the next day's release. But I don't recommend this if you are looking for a permanent rom.
---------- Post added at 04:48 AM ---------- Previous post was at 04:45 AM ----------
I would like to add that the chance of finding a security hole in newer hboots is smaller , and I bet that no one would want to miss applying an S-OFF exploit.
Click to expand...
Click to collapse
Does GPS work on these nighties?
I just flashed the one that I mentioned and I've already gotten 3 reboots. Definitely not keeping it.

Gps should work if you didn't update the hboot.
Sent from my EndeavorU

Vcek said:
Gps should work if you didn't update the hboot.
Sent from my EndeavorU
Click to expand...
Click to collapse
I ****ed it up.
I was getting reboot after reboot so I tried restoring my stock rom from de clockwork mode. Now all I get is the HTC One X boot logo.
I forgot to move the stock boot.img from my phone to the pc and now I don't know how to push it from the phone to the pc without system.
Any ideas?
edit: alright, I really need some help right now. I'm freaking out. All I need is to send the stock boot.img I have on my backup to my pc so i can flash it via fastboot usb.

7ind said:
I forgot to move the stock boot.img from my phone to the pc and now I don't know how to push it from the phone to the pc without system.
Any ideas?
Click to expand...
Click to collapse
Mount the storage as USB from CWM.

BenPope said:
Mount the storage as USB from CWM.
Click to expand...
Click to collapse
"E: Unable to open ums lunfile (No such file or di...)"
It's getting scary. I don't want my phone to die.
btw, I hit "mount usb storage", I guess that's what you told to me, right?
I think the problem may be usb debugging. Idk if i have it enabled.
edit: I pulled it of, flash the buggy cm10 rom again, put the other rom files in the SD car and enabled usb debugging. It's charging now, I'll flash this new rom later, maybe at 40%.