Develop Bugs

Htc one x stuck on logo

Hello,
I'm having a big problem with my Htc one x, i have tried to root my deviece and it was 100% rooted. After that I decided to install a rom.
I saw the good chermeleon rom that posted here at xda.. After the rom was installed the device stuckes on Htc logo and didn't start properly. I have tried to flash the boot again and to format and install the rom again and again and doesn't help.
I have treied to use ruu but it was not for my device, and I can't find the correct one for my device. Now I'm stuck with the logo and couldnt go to sdcard, not at the device and not at computer. My CID is 044.
Thanks for helpers

Can you still access recovery?
You must have done something wrong when flashing. Explain the exact steps you took to flash the rom.

Which rom did you flash, I'm not aware of any "chermeleon rom" for the One X? The ruu you need for cid HTC__044 is x.xx.707.x. The exact version will depend on the hboot version you have, but the latest version is 2.17.707.3 which you can find here, but you will need to boot to fastboot and lock your bootloader before running the ruu. When the device is connected can you run either the adb devices or fastboot devices command ? Does either of these return the devices serial number?

ClydeB1 said:
Which rom did you flash, I'm not aware of any "chermeleon rom" for the One X? The ruu you need for cid HTC__044 is x.xx.707.x. The exact version will depend on the hboot version you have, but the latest version is 2.17.707.3 which you can find here, but you will need to boot to fastboot and lock your bootloader before running the ruu. When the device is connected can you run either the adb devices or fastboot devices command ? Does either of these return the devices serial number?
Click to expand...
Click to collapse
OT: Charmeleon ROM was a ROM popular back in the day, it's succeeded by ViperX

I can access to recovery but when I try to access sdcard he says that the folder is empty. Can I access my sdcard throw pc? my hboot is 1.12.00 something like that. Do you think the ruu you meantion is the correct one?

[Q] Problem after root

I tried to root my friends HOX.
I used this root method - http://forum.xda-developers.com/showthread.php?t=1577671
The problem is after i have unlocked the bootloader, and was going to root the phone
I did what it said, Open "'install-insecure-windows.bat'"
And let the magic begin. But no.. now the phone keeps restarting and seems like the network is no longer working when the phone stays on.
So what can be the problem for this?
And i dont think it ever got rooted.
This phone is international HTC__Y13
I really need help, because im really lost, and need to fix this problem.

Try these 2 videos . Totally noob-proof .

The problem with the reboot is still there. Everything seems ok, after flashing recovery.img and entering CMW for installing SU.
But when rebooting, the phone is constantly rebooting.
Spec on enter bootload.
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.12.0000
CPLD-NONE
RADIO-1.1204.135.20
eMMC -bootmode: disabled
CPU –bootmode: disabled
HW Secured boot: enabled
MODEM PATH: OFF
Jun 28 2012,11:31:28
HTC__Y13
Can it help install the RUU?
If yes, what RUU do i need.
And last, how do i install the RUU?

I assume you have .401 software version since you have CID Y13 and you're trying to go back to stock .
Follow this video .

No, i want to root the phone, but i want to make the reboot to stop.
And want to know if there is any solution to this problem.
And this happend after i pressed "install-insecure-windows.bat"
I noticed one thing that we did not do under rooting process.
We never did put it back to charge only after putting recovery.img and superSU in root of SD-card.

VikingNor said:
No, i want to root the phone, but i want to make the reboot to stop.
And want to know if there is any solution to this problem.
And this happend after i pressed "install-insecure-windows.bat"
I noticed one thing that we did not do under rooting process.
We never did put it back to charge only after putting recovery.img and superSU in root of SD-card.
Click to expand...
Click to collapse
That's not necessary ... But , did you enable USB-Debugging and Unknown sources ?

Edit: The guide states it's only tested on 1.27.401.2 / 1.27.401.7.
So probably the insecure_boot.img is incompatible, try to find the correct boot.img for your ROM and flash it via fastboot. If it's stock, you can try to download the RUU, run it until it's unpacked, but not install it and find the rom.zip in the Users\[username]\AppData\Local\Temp\[guid]\[guid]\ before you closing the ROM Update Utility.
The boot.img can be found in the rom.zip.
You probably won't have ROOT then, but you won't have bootloops anymore.
Or you can install a custom ROM which already has been rooted.
Good luck!

Can you help me find the right RUU file?
So i dont mess more up
Sent from my GT-I9300 using xda premium

Go to fastboot and enter command fastboot getvar main-version . And then go to download the RUU file with the correct version or higher version of your current version .

[Q] RUU USB Error

I've been trying to update my HOX using the RUU but I keep getting error 170, I've got the latest WORKING USB drivers install(4.0.0.009 doesn't install) but for some reason I'm continuously getting the error, can someone tell me which USB connection type to use and what other settings I should apply and what should be disabled
Thanks
Edit: I've solved my first error but now I'm getting Error 159 which states that I'm using the wrong ROM Image to update my phone, but I'm not because my current firmware version is 2.17.401.2 and the RUU updates to 3.14.401.27, any help would be appereciated
Thanks

hi ,
you need to update your hboot to vers 1.36
read this thread.....
http://forum.xda-developers.com/showthread.php?t=1543604&page=268
you can read ClydeB1 instructions etc .post 2671 and next post 2672..etc etc
i also tried with only the RUU but failed,also said wrong ROM , after reading up on above thread and following advise given !!!
i download the hboot firmware zip file ( link given in thread by ClydeB1( few pages back ) and flashed it to upgrade hboot and then ran Ruu .straight afterwards ,(all done from pc using" commands
,as given in relevant thread,)
plse note....As i understood it you can't flash upgraded hboot and boot into ics and then try to flash Ruu ,it wont work.!(While in fastboot on phone you run Ruu straight afterwards .)
The firmware zip for hboot update, is placed in adb folder on pc and flashed with easy commands (copy and paste if you want to..!!)
...you just have to put phone debug mode ,and in fastboot (power and vol down )and usb connect to pc.
it took me about 20 min ? i am on 4.1 now !
smooth and no problems ..but you have to read up and understand,then whole process is very, very easy.. and quick!!
(my phone is not rooted or unlocked )
good luck

Would I need an Unlocked bootloader or need to be rooted to use this method or can my phone be completely stock and untouched?
Edit: Also where could I get hboot 1.36
Edit: I figured it out, thanks a lot for the help

Naveon said:
Edit: I've solved my first error but now I'm getting Error 159 which states that I'm using the wrong ROM Image to update my phone, but I'm not because my current firmware version is 2.17.401.2 and the RUU updates to 3.14.401.27, any help would be appereciated
Click to expand...
Click to collapse
willcor said:
hi ,
you need to update your hboot to vers 1.36
read this thread.....
Click to expand...
Click to collapse
I was having this exact problem when I was trying to flash the RUU last night, will try this method tonight. Thanks willcor for pointing out the step by step process.

HTC One M8 5.0.1- Blacked After OTA Update Failed

HELP, I've bricked my phone.
I'll try to be as brief as possible.
I had android 5.0.1 (4.16.401.10). unlocked bootloader, installed TWRP, rooted.
a few months later today, my phone had an OTA update notification (4.16.401.13), tried to do it, failed and it kept sending me to TWRP.
Googled it, people said I should restore the stock recovery, I did, tried to install the OTA again. phone got stuck on splash screen.
From there I have been online for hours trying to fix this but nothing. (there has been many flashing attempts, some fail some success) so the phone is pretty much a mess now.
My question is, what's the easiest way (if there is) to just restore the phone to stock firmware? I don't care if it's going to be rooted or not, I don't care if It's going to be wiped, I just need it to work.
Currently I have (relocked) bootloader, S-On
Thanks.

Same problem here, Got this update yesterday and stuck at the splash screen.
rooted, S-on, stock recovery
tried everything from changing recovery, FUU, RUU, nothing worked
Fortunately, I have full NAND backup months ago ( old,but better than nothing), restore it, update the new update and everything looks ok so far.
I suspect its related to the xposed relared problem as the old backup its not installed.

AHOHA said:
Fortunately, I have full NAND backup months ago ( old,but better than nothing), restore it, update the new update and everything looks ok so far.
Click to expand...
Click to collapse
Sorry if this is a noob question, but how can I do that? is there somewhere where I can download backups and restore them on my phone? And if so, will I need anything like an S-Off or something?
Because I've tried everything else I think, I tried RUU (both from PC or from bootloader, and with both Unlocked and Relocked bootloader) and nothing seems to work.

Hi there, got the same problem just dont have nan backup so i'm stucked.
Phone is rooted, unlocked, s-on
cid: VODAP001
mid: 0P6B10000
got latest twrp.
Tried to flash 2 (diferent date builds) roms acording to my cid, NO LUCK,
tried ruu - no luck
read hundrets of pages and found only one thing that I need is S-OFF, but how can I do s-off when my phone doesnt boot up?
pls help

mizaras said:
Hi there, got the same problem just dont have nan backup so i'm stucked.
Phone is rooted, unlocked, s-on
cid: VODAP001
mid: 0P6B10000
got latest twrp.
Tried to flash 2 (diferent date builds) roms acording to my cid, NO LUCK,
tried ruu - no luck
read hundrets of pages and found only one thing that I need is S-OFF, but how can I do s-off when my phone doesnt boot up?
pls help
Click to expand...
Click to collapse
I finally got mine to work today!!
What worked with me is this:
I got the RUU Zip file for my CID, renamed it to 0P6BIMG.zip , and copied it to the root of my SD Card (using an adapter or using TWRP to mount it)
then I flashed the stock recovery for my phone, then RELOCK your bootloader (fastboot oem lock)
Onve you've done all that just put the SD card in your phone and boot it in bootloader mode (Vol Down + Power) and it should detect the 0P6BIMG.zip file automatically and ask you if you want to update it.
P.S: I have S-On and it worked.
I hope this helps.

n00b stuck on old CM because too dumb to be able to upgrade bootloader

My ATT HTC One M8 was rooted using the 'official HTC' method soon after purchase and I was able to get CyanogenMod installed via their windows install tool back in the day so I didn't have to really understand what I was doing. It still runs CM11 quite well, but I'd really like to upgrade to CM12 if for no other reasons then the security updates. When I try to upgrade to CM12 though I get this error:
This package supports bootloader(s): 3.18.0.0000, 3.19.0.00000; this device has bootloader 3.16.0.00000, Installation aborted.
My recovery is ClockworkMod Recovery v6.0.4.8
Here's my bootloader screen:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.58.502.1
eMMC-boot 2048MB
Apr 18 2014,16:06:33.0
I don't know what I'm doing.
After six months of occasionally messing with this I still haven't figured out how to upload the boatloader. I only barely understand the stuff I read on this site. Most things have pointed me to do this:
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
But I'm not s-off, there is a ton of downloads and steps and 150 pages of comments (!) so if there is something burried in there that will help me I can't find it. I tried blindly applying one of the firmware downloads but it didn't work. and it was probably the wrong one anyway.
Everything else pointed me to return to stock and accept the OTA update with this thread:
http://forum.xda-developers.com/showthread.php?t=2696282
But I again got lost, and never got this working. Once I got brave and spent the better part of a day trying to return everything to stock, but I couldn't figure out how to do it in the end and was super-happy to get back where I started and have a working phone again. I don't recall the exact problem I had, but I remember trying several RUUs - not being sure which one was the right one - and they wouldn't apply and that was after changing recovery versions and types several times and following random forum advice and thinking I bricked the thing a dozen times.
My question is: Is there a simple way to upgrade my bootloader ? Simple meaning exact steps to follow to just upgrade the bootloader without doing a bunch of other stuff that could brick me and I don't understand? I'm not really sure where to begin, even though I've tried a bunch of stuff, this stuff is so confusing.
Is there any help for noob like me?

You have AT&T - those threads are not for you.
You need to see this - http://forum.xda-developers.com/showthread.php?t=2751432
1. Download RUU 4.28.502.2 RUU
2. Boot your device to bootloader/fastboot and connect to PC
2. relock bootloader - command fastboot oem lock
3. Install RUU
4. re-unlock your bootloader with the unlock_code.bin that you got from HTCDev
5. reinstall custom recovery
6. install your preferred custom ROM
To run a RUU .. you need USB2.0 and latest HTC USB driver installed. If not sure, download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
install it as it will install the latest HTC USB driver then uninstall the HTC Sync Manager but leave the driver.
This will wipe everything on internal storage - backup your photos, musics & etc to PC first.

Wow, thanks for taking the time with specific steps and links! I'll try again this weekend and let you know!

thanks!
This worked perfect! I think the key was the ATT RUU, which I definitly wasn't using it before. Once done getting back to CM was a snap and I'm now in great shape! Thanks so much!

You're welcome.
Correct RUU for correct device always fix things