Database Info

Question about hboot versions...

Does the 1.06 hboot (just downgraded yesterday) allow you to flash roms without flashing the boot.img seperately or is that only possible with S-Off? I reverted my supercid back to TMOB-010 after downgrading if that makes any diff.

Daiskei said:
Does the 1.06 hboot (just downgraded yesterday) allow you to flash roms without flashing the boot.img seperately or is that only possible with S-Off? I reverted my supercid back to TMOB-010 after downgrading if that makes any diff.
Click to expand...
Click to collapse
If you use TWRP then it does, its the reason I downgraded.

I'll sneak in a question here...
Apart from the official OTA not working, which doesnt work with unlocked bootloader anyway, is there any downside with downgrading hboot?
Im still not sure why the hboot would need downgrading, but everyones talking about it so I guess there gotta be a reason for it lol

Goatshocker said:
I'll sneak in a question here...
Apart from the official OTA not working, which doesnt work with unlocked bootloader anyway, is there any downside with downgrading hboot?
Im still not sure why the hboot would need downgrading, but everyones talking about it so I guess there gotta be a reason for it lol
Click to expand...
Click to collapse
OTA can be flashed on unlocked bootloader but need to have stock recovery. there is no downsides but a bunch of upsides like TWRP flashing boot.img also change radio and wifi partitions and also do this sweet mod.

Concur with Darknites--
I was lucky and got .06 "out of the box". Don't need ADB/Fastboot/Flash Image GUI for boot images.
Can flash all roms with boot image inside them and any radio/recovery I want thru Fastboot.
Only now just started using CM Installer to flash whatever radio I want on CM roms--but, that is a different matter.

I just did the last official OTA update (I actually found nothing wrong with that update except the battery history screen) and now i have Hboot 2.15.
Can I downgrade to Hboot 1.06 (the original Hboot i got with the device) and then root the device?
Thanks

yz250il said:
I just did the last official OTA update (I actually found nothing wrong with that update except the battery history screen) and now i have Hboot 2.15.
Can I downgrade to Hboot 1.06 (the original Hboot i got with the device) and then root the device?
Thanks
Click to expand...
Click to collapse
Yes, you can

[Q] 1.73.502 ruu question

Background story:
I was trying to unlock and s-off 1.73 at&t one x phone with 1.09 hboot so that i could install a custom rom... Having experience with some other phones I prepared myself, software, drivers and everything else and plunged into action... I successfully unlocked the phone using a compilation of tutorials since it's so old bootloader and all, as for root i'm not sure I actually managed to get it work, it complained most of the time of missing bin files although I flashed su through recovery again and it settled down. I couldn't s-off it in any of the way tutorials were suggesting, gathering that i would have to update with some newer RUU, so I quit and phone is still s-on. And then I did an incredibly stupid thing, i didn't do nandroid backup, i just wiped system and tried to flash a new rom to no avail... None of the roms won't get flashed, i tryed sense and cm based ones, i'm getting some partition error, something about 2,14 and 2,15, not sure since error reporting is not consistent... Now I'm stuck within recovery and bootloader, i'm unlocked but s-on, i can't flash system img through fastboot nor a custom rom through adb sideload it says that partition is too small.
So question is what am I to do? What is my safest way out? Should i try flashing RUU (the one that should be the original one 1.73.502) or could I run some newer RUU and which would be preferable? If I'm to run RUU 1.73, should I run it as an exe or should I try to flash it as a zip file? Does it matter that the phone is unlocked and s-on? Why won't the smaller cm roms flash, how small could the partition be and does it have something to do with android version (4.1, 4.2 etc)?

To get a working ROM on your phone you can download an old build of cm and flash that. The new builds require updated firmware but the older builds don't. Go here and download the bottom build (stable cm10), and you'll need to get the 4.1 gapps package from here.
Sent from my Evita

What recovery and version number? I have a feeling this is recovery related, more than anything.
Also, newer builds of CM10.2 require hboot 2.14 or 2.15, so that is probably what the error message you mentioned is about.
We should be able to get you back up in and running on the custom ROM of your choice. But if you do decide to go the RUU route, in order to run an RUU, you must relock the bootloader in fastboot. Then you should be able to run the RUU. 1.73 RUU is fine. DO NOT run the 3.18, as there is a bug where with SuperCID and S-on (and you now have both) will BRICK THE PHONE. But the 1.73 or 1.85 RUUs will be fine.
Run the RUU as an .exe. I don't see the point in extracting and running the ROM.zip. You would just be making the process harder than it should be, and also removing some of the safeguards, if I remember properly.
S-off should work on any hboot version. I believe I got s-off while on hboot 1.09.

I'm running twrp 2.5.0.0 recovery, is there newer version? It never crossed my mind that it could something to do with recovery, so I never looked it up... Perhaps I could change it, it's not like that's gonna ruin chance of restoring any previous backups i didn't make...But i'd rather update the phone's firmware just to get those hboot glitches off the way because it, i'm quite sure, obstructed the s-off process (i was getting few 9x errors during s-offing, mostly 99).
So I'd be safe running 1.85 RUU. Is there some other RUU you would recommend, preferably some which will make the whole process of rooting, SuperCIDing and s-offing easier?
Thank you for helping me out!
edit> I tried flashing oldest CM and it worked! Then, feeling safe and all, I flashed newest twrp recovery and then, to my utter amazement, it flashed other rom I was aiming for... So thanks, for that recovery tip, it saved me a lot of pain! Now all is left for me is to figure out that s-off thing...

Stuck at boot loop???

Hi, i had a S4 which got a broken screen and costs too much to fix a the moment so i brought a Telstra HTC ONE XL off a friend for $100.
I do like the phone but was over the 4.2.1 software as used to the 4.3 on the S4 which i rooted and put on CM10.
I tried with this phone to put on the nightly cm 10.3 but i hit a problem ,when install the nightlies it boot loops and when i try install the stable 10.1 it fails with an error which i do belive is to do with my V2 hboot.
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial
I have unlocked through htcdev and rooted it ok.
Im stuck now though as i pressed backup current original rom which turns out its not.
The phone details are
CID TELST001
Model: HTC ONE XL TELSTRA
If someone can tell where to either find the newest telstra rru for my phone or how to update my hboot so i can use cm10?
My phone is pretty useless at the moment

stueee said:
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
Click to expand...
Click to collapse
Where are you getting CM from (link it) and what is the file named? CM will typically have the phone's code name (EVITA) in the file name. If the code name ENDEAVORU is in the file name, it is in fact for the wrong device, as the ENDEAVORU is for the quad core Tegra3 (non-LTE) version, which is completely different hardware.
Also, I don't know if 10.3 is even released yet for our device, or for the ENDEAVORU for that matter. I think you might be confused about what you are flashing. So again, link what you are trying to install.

The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have. Getting s-off disables the security check which would let you run any Evita RUU but you need to get a ROM to boot first before you try that. You also need SuperCID.
Your best bet is probably to flash an older Sense ROM (4.0 or 4.1), then you can at least boot, and get SuperCID and s-off so you can run the 3.18 RUU to meet the requirements for the latest cm ROMs.
Sent from my Evita

timmaaa said:
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have.
Click to expand...
Click to collapse
For some reason, I got confused and thought the OP was saying that the ROM install was failing. But it clearly says the RUU (or "rru" anyway) failed.
But yes, you can only run an RUU for your carrier version. So you will need s-off to run the AT&T RUU (the RUU referenced in the OP).
But still confused about the mention of CM10.3. From what I can see, it doesn't exist for either our EVITA, or the ENDEAVORU.

Maybe he meant cm10.2 and it was a typo?
Sent from my Evita

timmaaa said:
Maybe he meant cm10.2 and it was a typo?
Click to expand...
Click to collapse
Could be. Although if so, its a type that appears twice.
It seems fairly common for folks to try to install the wrong CM (wrong device). So I want to make sure the OP isn't doing that.

redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.

stueee said:
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
Click to expand...
Click to collapse
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.

Hi Red,
Sorry i typed out that post at almost 1am after pulling my hair out over a few hours and got a little confused.
My hboot is 2.15 and twrp is 2.6.3.0 which I believe is the latest.
What sense rom would work on mine as i really need this working now as i cant find a rom to suit anywhere with my lesser expertees.
I tried changing the cid using the super cid Telstra bat file but it won't recognize the phone as its not loaded, i tried in off state, bootloader, fastboot and twrp but is just keeps saying cant find phone.
I also tried the hex editor method but it didnt seem to update the CID after i completed it without errors.
thanks for you help.
redpoint73 said:
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Click to expand...
Click to collapse

With 2.15 hboot, you cannot modify the files required for supercid.
You can try the ever so risky jet tool. But this tool deliberately bricks to downgrade your hboot.
Sent from my HTC One XL using xda app-developers app

Any recent Sense ROM will suit your current setup, have a look here and you'll find a whole bunch. Unfortunately for you the 2.15 hboot has write protection enabled so there's no way you can get SuperCID (abd therefore can't get s-off), at least not until an exploit is released.
When you tried to flash CM did you also flash the boot.img via fastboot afterwards? You're s-on so that's necessary to get it to boot. Phones on a higher hboot like yours are unable to flash the boot.img through recovery so it must be done manually.
All you do is retrieve the boot.img from the root of the ROM zip, put it in your fastboot folder on your PC, and after you've flashed the ROM in recovery you reboot to bootloader, connect the phone to the PC, open a command prompt from within your fastboot folder (shift + right click anywhere in the folder then select open command prompt here), then give the following command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the ROM.
Sent from my Evita

stueee said:
My hboot is 2.15
Click to expand...
Click to collapse
That's pretty important. This is the reason why the older CM10.1 failed to install. CM was having issues with older hboots, so a script was added to require hboot 2.14.
Once hboot 2.15 came along, folks found that CM failed to install since the install script explicitly requires 2.14. Later versions include hboot 2.15 in the install script.
As exad and timmaaa mention, SuperCID (and therefore s-off) are not possible on hboot 2.15. So you are stuck with s-on (assuming that is what you are on now). It also means you can't currently run any RUU. Reason being, with s-on you can't run older RUUs, RUUs from another carrier, and there are no RUUs based on hboot 2.15. No "current" RUU exists (for your hboot), you can't run "previous" RUUs with the S-on restriction. So therefore you can't currently run any RUU.
But hboot 2.15 will work with newer versions of CM (and other AOSP ROMs which have been recently updated) as well as any Sense ROMs. But with s-on, you need to extract boot.img and flash manually with fastboot every time you install a ROM (as timmaaa points out). If you did not do this, this is why flashing the recent CM10.2 nightly resulted in a bootloop. Failure to falsh boot.img is the most common reason for bootloop after flashing a ROM.

stuck in bootloop
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..

martin-m7 said:
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
Click to expand...
Click to collapse
You're in the wrong forum, buddy. This is the HTC One XL forum.

[q] 2.16 s-off tmous

This is more of a clarification request than a help question
As I understand it, mind you I am not that well versed in Android dev, you cannot obtain SuperCID/S-OFF either through Moonshine or Facepalm methods when you are on 2.16 HBOOT. Is that correct?
Given this is fact, the only way to have 2.16 + S-OFF is to be S-OFF before upgrading HBOOT to 2.16?
So let's say for my phone I have 2.15 HBOOT Moonshine'd S-OFF, if I upgrade to HBOOT 2.16 will i still maintain my S-OFF status?
And as a side question, what methods are available to upgrade my HBOOT from 2.15 to 2.16? Current phone is TMOUS CM10.1.3 with the latest *.17 firmware.

pyrocide said:
This is more of a clarification request than a help question
As I understand it, mind you I am not that well versed in Android dev, you cannot obtain SuperCID/S-OFF either through Moonshine or Facepalm methods when you are on 2.16 HBOOT. Is that correct?
Given this is fact, the only way to have 2.16 + S-OFF is to be S-OFF before upgrading HBOOT to 2.16?
So let's say for my phone I have 2.15 HBOOT Moonshine'd S-OFF, if I upgrade to HBOOT 2.16 will i still maintain my S-OFF status?
And as a side question, what methods are available to upgrade my HBOOT from 2.15 to 2.16? Current phone is TMOUS CM10.1.3 with the latest *.17 firmware.
Click to expand...
Click to collapse
Yes you stay s-off unless you give a certain command in fastboot. I'm not going to say the command because someone will type it and mess up their phone.
(FYI do not Go back to S-on unless your phone is completely back to stock)
Follow the original post in the Maximus HD thread, that flashes the new firmware that will update the HBoot, Radio, Repartition for new Android. Also the modified TWRP in that post is the only recovery that will work with the new firmware.
Oh, and yes, Moonshine and Facepalm do not work with 2.16. But there is a new way to S-off using rumrunner, that will even work with 2.16.
http://forum.xda-developers.com/showthread.php?t=2558334

tivofool said:
Yes you stay s-off unless you give a certain command in fastboot. I'm not going to say the command because someone will type it and mess up their phone.
(FYI do not Go back to S-on unless your phone is completely back to stock)
Follow the original post in the Maximus HD thread, that flashes the new firmware that will update the HBoot, Radio, Repartition for new Android. Also the modified TWRP in that post is the only recovery that will work with the new firmware.
Oh, and yes, Moonshine and Facepalm do not work with 2.16. But there is a new way to S-off using rumrunner, that will even work with 2.16.
http://forum.xda-developers.com/showthread.php?t=2558334
Click to expand...
Click to collapse
Do i have to be on stock to follow the Maximus install or can I be on a different rom with a different recovery than what is provided in the install package until I flash the provided recovery at the end of the install?

pyrocide said:
Do i have to be on stock to follow the Maximus install or can I be on a different rom with a different recovery than what is provided in the install package until I flash the provided recovery at the end of the install?
Click to expand...
Click to collapse
Ya, that is fine to be on a different ROM and Recovery.
Follow the directions exactly. (for example downloading and installing maximus before installing the new firmware and recovery and then reinstalling Maximus.
-------------------------------------------
Here is another post related to MagioRom. It has firmware update instructions and also a link to a tool if you don't want to manually enter commands.
http://forum.xda-developers.com/showpost.php?p=47403627&postcount=3

tivofool said:
Ya, that is fine to be on a different ROM and Recovery.
Follow the directions exactly. (for example downloading and installing maximus before installing the new firmware and recovery and then reinstalling Maximus.
-------------------------------------------
Here is another post related to MagioRom. It has firmware update instructions and also a link to a tool if you don't want to manually enter commands.
http://forum.xda-developers.com/showpost.php?p=47403627&postcount=3
Click to expand...
Click to collapse
Welp i got past the first install but after rebooting into fastboot and oemReboot trying to flash the recovery (after the firmware.zip was successful) I am stuck at the black screen w/ silver HTC logo and an incomplete green bar. Power down and try again? Or wait some more, been about 5 minutes so far.

pyrocide said:
Welp i got past the first install but after rebooting into fastboot and oemReboot trying to flash the recovery (after the firmware.zip was successful) I am stuck at the black screen w/ silver HTC logo and an incomplete green bar. Power down and try again? Or wait some more, been about 5 minutes so far.
Click to expand...
Click to collapse
I believe you are still in RUU mode, so since the firmware successfully flashed, reboot phone into bootloader and fastboot flash recovery recovery.img

tivofool said:
I believe you are still in RUU mode, so since the firmware successfully flashed, reboot phone into bootloader and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
that is correct, following maximus to the letter it did not mention going back to bootloader after flashing the firmware.zip. What about the incomplete green bar should I be worried about that?

pyrocide said:
that is correct, following maximus to the letter it did not mention going back to bootloader after flashing the firmware.zip. What about the incomplete green bar should I be worried about that?
Click to expand...
Click to collapse
Nope, I'm almost positive you have done everything correctly. Just my memory is a little fuzzy, but I'm pretty sure that is exactly what has happened to me. (I've installed Maximus and firmware 3 different occasions)

tivofool said:
Nope, I'm almost positive you have done everything correctly. Just my memory is a little fuzzy, but I'm pretty sure that is exactly what has happened to me. (I've installed Maximus and firmware 3 different occasions)
Click to expand...
Click to collapse
Still not able to flash recovery after rebooting to bootloader fastboot USB mode.
Device now shows instead of Moonshine at the top
***Tampered***
***Locked***
S-OFF
CID T-MOB010
HBoot 2.16
Code:
C:\adb\Install Package>fastboot flash recovery recovery.img
sending 'recovery' (8900 KB)...
OKAY [ 1.077s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.114s
It shouldnt matter still being s-off, but I still have my unlock token to unlock the bootloader.

pyrocide said:
Still not able to flash recovery after rebooting to bootloader fastboot USB mode.
Device now shows instead of Moonshine at the top
***Tampered***
***Locked***
S-OFF
CID T-MOB010
HBoot 2.16
Code:
C:\adb\Install Package>fastboot flash recovery recovery.img
sending 'recovery' (8900 KB)...
OKAY [ 1.077s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.114s
It shouldnt matter still being s-off, but I still have my unlock token to unlock the bootloader.
Click to expand...
Click to collapse
Yep, that is why. Unlock that bootloader.

tivofool said:
Yep, that is why. Unlock that bootloader.
Click to expand...
Click to collapse
Forgive my ignorance but wasnt the entire point of being S-OFF was not having to jack with the bootloader being locked and unlocked/relocked etc?
Got it to boot, working on second maximus install now.

pyrocide said:
Forgive my ignorance but wasnt the entire point of being S-OFF was not having to jack with the bootloader being locked and unlocked/relocked etc?
Got it to boot, working on second maximus install now.
Click to expand...
Click to collapse
I know what you mean, but no, the bootloader needs to be unlocked to root and flash custom roms. But there is still some security that needs to be turned off to be able to change some things, like HBoot and other things.

tivofool said:
I know what you mean, but no, the bootloader needs to be unlocked to root and flash custom roms. But there is still some security that needs to be turned off to be able to change some things, like HBoot and other things.
Click to expand...
Click to collapse
Thanks for the help, got it booting and charging. Gonna test the battery with the extended battery from the One X+ and see how much better this battery is vs CM10.1.3 and bootloops/reboots etc.

[HELP] How to downgrade hboot

Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person

the_ziom said:
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
Click to expand...
Click to collapse
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !

benJX said:
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
Click to expand...
Click to collapse
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right

the_ziom said:
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
Click to expand...
Click to collapse
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.

I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks

dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!

rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.

dr3amsINdigital said:
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
Click to expand...
Click to collapse
Wise choice, yeah you are right, the bricks were when they were flashing the zips in recovery. Its actually pretty safe in RUU mode but what's the point of risking it.

benJX said:
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
Click to expand...
Click to collapse
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
HELP my device does not see any memory and i cant flash any rom hellpp

the_ziom said:
HELP my device does not see any memory and i cant flash any rom hellpp
Click to expand...
Click to collapse
What hboot are you on now? Did you run an RUU to downgrade?

rosswhite said:
What hboot are you on now? Did you run an RUU to downgrade?
Click to expand...
Click to collapse
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone

the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Which recovery did you flash? Try TWRP 2.7.0.0.

the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Can you boot on stock android rom installed by the ruu ?

rosswhite said:
Which recovery did you flash? Try TWRP 2.7.0.0.
Click to expand...
Click to collapse
i already have twrp 2.7 and i flashed phillz and still nothing

benJX said:
Can you boot on stock android rom installed by the ruu ?
Click to expand...
Click to collapse
yes but i formated my memory to instal a pac man rom

the_ziom said:
yes but i formated my memory to instal a pac man rom
Click to expand...
Click to collapse
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.

####

benJX said:
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
Click to expand...
Click to collapse
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp

So many developers and only 2 can help me
Please I'm begging for help

the_ziom said:
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
Click to expand...
Click to collapse
Flash stock recovery : http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Then Clear Storage from bootloader and flash TWRP recovery