Hi everyone. New to the forum and new to flashing etc. I have been playing with my phone for a couple of nights now but finally gave in and think I need to ask for help.
Here is a bit of background info so far. The last few weeks my One X+ has been suffering from getting stuck coming out of airplane mode. I am currently using an old Desire HD so thought I have nothing to lose by trying to fix the +.
I have managed so far to unlock the bootloader and root the phone. I have flashed TWRP and created a backup.
I have tried to load Android Revolution 8 which complete successfully along with the boot image but when the phone starts I get the HTC splash screen (quietly Brilliant & One X Beats Audio) but it then goes to just HTC then the phone turns itself off.
Have tried a couple of time but end up having to flash my recovery to revert back to how it was.
I feel I may be missing something and would appreciate it if someone could help me out.
Many Thanks :good:
Battery empty?
Sent from my Find 5 using Tapatalk
Lloir said:
Battery empty?
Sent from my Find 5 using Tapatalk
Click to expand...
Click to collapse
No I don't think so. Like I say I have had a few goes at it now and from reading some of the guides on here which say it is important to make sure it has plenty of charge, I have made sure it is well charged before starting.
If it helps, here is some info phone the phone:
HTC One X+
CID-HTC__001
ENRC2B
HBOOT-1.72.0000
Model ID-PM3511000
Have you tried doing a full wipe before or during flashing ARHD? Can you still get into the bootloader or recovery? I had similar problem, changed the cable then flashed the boot image again.
qasimrb said:
Have you tried doing a full wipe before or during flashing ARHD? Can you still get into the bootloader or recovery? I had similar problem, changed the cable then flashed the boot image again.
Click to expand...
Click to collapse
I have done a wipe yes. I have been picking my way through these guides which all have small differences.
http://forum.xda-developers.com/showthread.php?t=2066390
http://forum.xda-developers.com/showthread.php?t=1987885
http://forum.xda-developers.com/showthread.php?t=1995685
Yes I can still access the bootloader and TWRP recovery. The phone is currently restored back to how it was originally.
Are you flashing the boot image before or after you install the rom? With the ARHD he recommends flashing his firmware.zip before flashing the rom.
But from what I remember when my phone was stuck on the splash screen I went back into the bootloader, used another cable and flashed the firmware.zip again, restarted it and it was fine.
Info when I'm in bootloader is:
***UNLOCKED***
ENRC2B_U S-ON
HBOOT-1.30
CPLD- None
MICROP- None
RADIO- None
(Don't know why it says "none" next to radio, network etc is fine, Vodafone UK)
qasimrb said:
Are you flashing the boot image before or after you install the rom? With the ARHD he recommends flashing his firmware.zip before flashing the rom.
But from what I remember when my phone was stuck on the splash screen I went back into the bootloader, used another cable and flashed the firmware.zip again, restarted it and it was fine.
Info when I'm in bootloader is:
***UNLOCKED***
ENRC2B_U S-ON
HBOOT-1.30
CPLD- None
MICROP- None
RADIO- None
(Don't know why it says "none" next to radio, network etc is fine, Vodafone UK)
Click to expand...
Click to collapse
I have tried both ways. Flashing the boot image before and after the installing the ROM and both ways reproduce the same effect.
I have read the page where it mentions loading the firmware but as I have just set out about learning the in's and out's of loading ROMS I wasn't sure what this was. I now understand what the boot image is and what the ROM is but take it the firmware is something different. Should loading the firmware be the first step before falshing the boot image and ROM?
I have been over to his download page with the two 401 firmwares which I believe are the ones I require. The only issue I have is, it seems these are earlier versions so wasn't sure they would be correct to use. I cannot check currently as I'm at work but I think I am running firmware version 2.18.401.3.
So which one should I load?
Also here is the info from my bootloader screen:
HTC One X+
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.171.33
eMMC-bootmode: disabled
CPU-boomode: disabled
HW Secure Path: enabled
MODEM PATH: OFF
Model ID-PM3511000
Software Number - 2.18.401.3
CID-HTC__001
Related
Hi all:
I think I´ve definitely broken my brand new HTC One. The problem is that the phone is stuck in the initial animation (white screen with the HTC One logo. This screen) and I cannot do anything. I tell you the story.
I rooted the phone with this tutorial http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
At first, everything seems to go fine, but the SuperUser app started to fail and ask for updates. I installed RomManager and I changed to CWM Recovery instead of the TWRP recovery installed while rooting. I unistalled Super SU and installed the Google Play version and everything was fine again.
Today I tried this mod http://forum.xda-developers.com/showthread.php?t=2251788 to remove the 3 dot menu and I flashed the file bkbtnmenu.zip with CWM. I flashed the file, I did a wipe cache and a wipe dalvik and when I tried to reboot, the HTC got stuck in the animation screen.
I cannot switch it off, neither entering in recovery or anything else. When I try to restart or enter in recovery it simply restarts to the same screen and cannot do anything but waiting for the device to empty the battery.
I´ve made something terribly wrong. Hope some of you guys can help me. Every little help will be appreciated. Absolutely desperated
For future reference I'd say not to use anything from zedomax because someone always has issues with his tutorials. Anyway, you said you're not able to boot into hboot?
Sent from my HTC One using Tapatalk 4 Beta
Some progress
First of all, thanks for the advice.
After reading your reply I´ve tried again and now I´m able to start the phone in recovery mode. Sorry but cannot post images. I already can go into the HBoot screen.
But don´t know how to continue.
If you're able to boot into recovery try to factory reset, you'll lose all your apps and settings but that should work
Sent from my HTC One using Tapatalk 4 Beta
No progress
I´ve done the factory reset, but after rebooting I´m still stuck in the boot animation screen.
Absolutely no idea of what I can do.
Try downloading an ruu if you just want full stock, otherwise try pushing a rom to the sd card and flashing it that should get you back up and running
Sent from my HTC One using Tapatalk 4 Beta
Lost
Nick281051 said:
Try downloading an ruu if you just want full stock, otherwise try pushing a rom to the sd card and flashing it that should get you back up and running
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
I´m a bit newbie in this kind of things. Before the crash, I had Android 4.2.2 and even though I´m Spanish, I live in Singapore and I´ve bought my HTC here.
I´ve noticed that there are a lot of RUU and no idea of which to choose. I don´t have any problem in pushing a new rom, but how can I push it to the SD card? Please can you send me a link or two? I´ve found a lot of info in the forum but I´m a bit overwhelmed because most of the posts are for people with more experience than me and don´t know which one I have to choose.
ziereis said:
I´m a bit newbie in this kind of things. Before the crash, I had Android 4.2.2 and even though I´m Spanish, I live in Singapore and I´ve bought my HTC here.
I´ve noticed that there are a lot of RUU and no idea of which to choose. I don´t have any problem in pushing a new rom, but how can I push it to the SD card? Please can you send me a link or two? I´ve found a lot of info in the forum but I´m a bit overwhelmed because most of the posts are for people with more experience than me and don´t know which one I have to choose.
Click to expand...
Click to collapse
First you have to tell me which cid you have, it will tell you in hboot
Sent from my HTC One using Tapatalk 4 Beta
OK, here you have what I see in the HBOOT screen
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.707.1
eMMC-boot 2048MB
Jun 23 2013,04:07:35.14299
ziereis said:
OK, here you have what I see in the HBOOT screen
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.707.1
eMMC-boot 2048MB
Jun 23 2013,04:07:35.14299
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2370800
Go to this thread, there you will find your resolution.
Sorry for bothering you again but it doesn´t work.
I followed the steps of the video. My HBoot screen now shows that it´s RELOCKED instead of UNLOCKED
I started the RUU file and it showed me that currently I have a 2.x.x.x. ROM and I´ll change to a 1.x.x.x. ROM. I clicked next and the software got stuck sending. After a few minutes, I received this message
ERROR[130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Maybe It´s something related to the drivers?
ziereis said:
Sorry for bothering you again but it doesn´t work.
I followed the steps of the video. My HBoot screen now shows that it´s RELOCKED instead of UNLOCKED
I started the RUU file and it showed me that currently I have a 2.x.x.x. ROM and I´ll change to a 1.x.x.x. ROM. I clicked next and the software got stuck sending. After a few minutes, I received this message
ERROR[130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Maybe It´s something related to the drivers?
Click to expand...
Click to collapse
Did you change your CID?
Sent from my HTC One using xda premium
How can I know if I´ve changed my CID?. I don´t think so, but I´m not sure. I´m so frightened
currently: boot loader unlocked
RUBY PVT SHIP S-ON RL
HBOOT-1.93.003
eMMC-boot
Aug 14 2012, 17:22:50
I am also using 4ext as a recovery installed from hasoons toolkit, ive tried multiple roms and always the same outcome. wifi may or may not work on first install, if it does its only periodic sometimes hours sometimes days sometimes never turns on at all. Anyone know how to fix this problem ? is it a problem with my s-on or hboot ?
hrsa_13 said:
currently: boot loader unlocked
RUBY PVT SHIP S-ON RL
HBOOT-1.93.003
eMMC-boot
Aug 14 2012, 17:22:50
I am also using 4ext as a recovery installed from hasoons toolkit, ive tried multiple roms and always the same outcome. wifi may or may not work on first install, if it does its only periodic sometimes hours sometimes days sometimes never turns on at all. Anyone know how to fix this problem ? is it a problem with my s-on or hboot ?
Click to expand...
Click to collapse
Is your wifi not picking up access points, or is it that the wifi activation box won't tick to "ON"? I'm running the same HBOOT and am also S-On. With the newer roms (CM10.2 for example) I've noticed a similar behavior that it seems to take a while to find the access point, however never taking longer than 5-10 minutes. Have you tried going back to an older series rom and seeing if it works better?
voodoodude said:
Is your wifi not picking up access points, or is it that the wifi activation box won't tick to "ON"? I'm running the same HBOOT and am also S-On. With the newer roms (CM10.2 for example) I've noticed a similar behavior that it seems to take a while to find the access point, however never taking longer than 5-10 minutes. Have you tried going back to an older series rom and seeing if it works better?
Click to expand...
Click to collapse
that's exactly what happens it just says turning wifi on but never ticks to on. I ended up relocking bootloader and flashing the r2 ruu but its still having the same problem :/
Seems like there are 2 reasons for the problem
1. You have faulty hardware (which likely isnt the case, since it still works...kinda, and you also wouldnt want to accept it)
2. It is a kernel issue
I am not sure of your method of flashing a new rom, or restoring with RUU, but the only explantion for the WiFi module not functioning properly after a RUU is done, is the radio, since the kernel is being replaced constantly with the rom flashing...
Do some googleing about bootloaders, especially radios, etc. and you will understand how flashing the incorrect bootloader/radio combination coudl damage and fatally brick your device
Hope this helps
since your S-ON my guess is your kernel isn't flashing properly...make sure to flash the rom with correct modules then flash the kernel through adb or flash the whole zip (modules+boot.img) while enabling smart flash
I know I'm late to the party (more like the party is over and Im putting on clothes... none the less) I really need help (dont we all) my problem is Im stuck on a boot loop. I can access twrp all functional but I cant get the OS to boot. I've read about all the post I can find about the situation without resolution. I beg of you adroid god reading this to help me out.
----My Rig----
HTC Evo 4g lte
***Tampered****
***Unlocked****
Jewel PVT Ship S-on RL
Hboot- 2.09.0000
Radio 1.12.11.1210
Open DSP-V 31.1.0.45.0815
eMMC-boot
----story---
I was running fine on 4.3.rom (beanstalk), I flashed Haunted kernel through GUI. I rebooted and then flashed beanstalk again, wiped d /c and got stuck in boot loop. I set up ADB tried to flash recovery ( after exhausting TWRP option) didnt work, then I started reading threads so far cant seem to get it going. As I stated I have access to TWRP functions, I tried RUU (unlocked and relocked) didnt work. I am at a loss please help.
Im sure it can be fixed, but I dont know how.
AndroidIsland said:
I know I'm late to the party (more like the party is over and Im putting on clothes... none the less) I really need help (dont we all) my problem is Im stuck on a boot loop. I can access twrp all functional but I cant get the OS to boot. I've read about all the post I can find about the situation without resolution. I beg of you adroid god reading this to help me out.
----My Rig----
HTC Evo 4g lte
***Tampered****
***Unlocked****
Jewel PVT Ship S-on RL
Hboot- 2.09.0000
Radio 1.12.11.1210
Open DSP-V 31.1.0.45.0815
eMMC-boot
----story---
I was running fine on 4.3.rom (beanstalk), I flashed Haunted kernel through GUI. I rebooted and then flashed beanstalk again, wiped d /c and got stuck in boot loop. I set up ADB tried to flash recovery ( after exhausting TWRP option) didnt work, then I started reading threads so far cant seem to get it going. As I stated I have access to TWRP functions, I tried RUU (unlocked and relocked) didnt work. I am at a loss please help.
Im sure it can be fixed, but I dont know how.
Click to expand...
Click to collapse
You of course checked the md5 on the kernel before flashing, right? You should really get s-off to save yourself some issues. If you are certain you have a good download of the kernel, do a full wipe system, data, and cache. Flash the ROM in TWRP, do not reboot, then adb the boot.img and reboot. Should take care of you.
Here is some light reading for you: http://forum.xda-developers.com/showthread.php?t=2256478
wolfclan68 said:
You of course checked the md5 on the kernel before flashing, right? You should really get s-off to save yourself some issues. If you are certain you have a good download of the kernel, do a full wipe system, data, and cache. Flash the ROM in TWRP, do not reboot, then adb the boot.img and reboot. Should take care of you.
Here is some light reading for you: http://forum.xda-developers.com/showthread.php?t=2256478
Click to expand...
Click to collapse
Md5? I didnt check it...I tried the moonshine s-off method but it didnt work (i was already boot looping by then tho) I am downloading a new version of the kernel now. Ill let you know how it works. Thank you for responding....
AndroidIsland said:
Md5? I didnt check it...I tried the moonshine s-off method but it didnt work (i was already boot looping by then tho) I am downloading a new version of the kernel now. Ill let you know how it works. Thank you for responding....
Click to expand...
Click to collapse
nope didnt work.... I entered TWRP reloaded the kernel file flashed it, then flashed the rom (beanstalk) used twrp to boot into the bootloader fastboot flash the boot.img file used cmd command to reboot phone no dice. any other suggestions (or problems evident in my process) ? Im game to try anything at this point. I on a supersonic I borrowed from a friend. try the same process with just flashing the rom now. BTW Haunted-Kernel-AOSP-v29.3. I try version 30.2 of haunted next
Hi everyone,
My phone specifications:
TAMPERED
UNLOCKED
T6UL PVT SHIP S-ON RH
HBOOT- 2.47.0000
RADIO-4T.21.3218.31
OpenDSP-V33.120.274_T6.0829
QSC-
OS-1.54.401.1
eMMC-boot 2048mb
My phone freeze at boot, when i switched it off, it reboots automatically. Yesterday I've unlocked my bootloader install cwm touch version and rooted my phone. installing superuser. but could not s-off my phone using Rumrunner.
So i leave it like this but today i notice that my battery was draining. I decided to install the unsecure kernel. I found only the sprint verizon version unless i'm not using Sprint cause I read somewhere that only the CWM needs to be international. (I think this was the mistake)
I flashed it using CWM. The phone switched on normally and noticed no network at all on the phone. when i restarted the phone, it freeze at boot.
Is my phone bricked??
I can access fastboot menu and recovery.
Thanks and sorry for my bad English.
Your phone is definitely not bricked. You should not flash the Sprint kernel on your phone - yours is an International Model.
Since your OS is 1.54.401.1 - its the European version, you could download the ROM and flash it and your phone should be back to normal.
You could also just flash the stock kernel and it should work, the only reason i suggest to install a complete ROM is to have a clean install.
PS: CWM seems to have issues, please use TWRP for flashing ROM.
pradeepvizz said:
Your phone is definitely not bricked. You should not flash the Sprint kernel on your phone - yours is an International Model.
Since your OS is 1.54.401.1 - its the European version, you could download the ROM and flash it and your phone should be back to normal.
You could also just flash the stock kernel and it should work, the only reason i suggest to install a complete ROM is to have a clean install.
PS: CWM seems to have issues, please use TWRP for flashing ROM.
Click to expand...
Click to collapse
Thank you very much Pradeep.
Just flash the stock rom you uploaded. Camera not working, and no network signal but did not get the message sim invalid like i was getting before.
All other stuff running fine.
That is weird! was your bootloader LOCKED or UNLOCKED when you performed this?
i would suggest to do it when it's UNLOCKED or i would ask you to you to flash the boot.img from the zip file using fastboot flash boot boot.img
Hope you used TWRP and not CWM.
pradeepvizz said:
That is weird! was your bootloader LOCKED or UNLOCKED when you performed this?
i would suggest to do it when it's UNLOCKED or i would ask you to you to flash the boot.img from the zip file using fastboot flash boot boot.img
Hope you used TWRP and not CWM.
Click to expand...
Click to collapse
Problem solved! :laugh: i ran the same procedure again and now everything running fine and smooth. battery very good.
Thanks for your help Pradeep. You made my day. When switching on the phone i get the red message about the build and so on, but i don't care as the running very well.
Bootloader now indicating unlock and s off by firewater.
hellxprexx said:
Problem solved! :laugh: i ran the same procedure again and now everything running fine and smooth. battery very good.
Thanks for your help Pradeep. You made my day. When switching on the phone i get the red message about the build and so on, but i don't care as the running very well.
Bootloader now indicating unlock and s off by firewater.
Click to expand...
Click to collapse
Welcome! we get the red message as well, don't care about it too.
pradeepvizz said:
Welcome! we get the red message as well, don't care about it too.
Click to expand...
Click to collapse
I found that once I re-locked the bootloader (which you must do if you have any intention of using your fingerprint scanner again), I no longer get the red developer disclaimer message during a normal boot. The only time I see it is if I boot into recovery from hboot, and that doesn't bother me at all!
Sprint HTC One Max - Stock Android (barely ) 4.3 JB rooted, s-off, locked BL - HTC EVO 3D - Android 4.0.3 ICS rooted, s-off + a few Galaxies lol
A couple of years ago I came up on a third party boot loader for my Ruby in the development or general forum. I installed this unlocked boot loader and havent been able to remove or revert it to stock. I also cannot flash a rom even though I have clockwork installed. An additional serious issue with this bootloader is that if my battery dies it wont detect it and charge. The device will turn its charging lite on and touching my capacitive buttons will cause my phone to vibrate... but no charging. I confirmed the battery is good by purchasing an external battery charger and successfully charging it. The phone will reboot with charged battery. The phone will charge while it is on but if the battery dies it will no longer charge. I just want to remove this boot loader and revert to the stock booloader so i can re-ROM and charge normally.
Any ideas? I tried the 5.2 toolkit but the adb tools included wont detect my device when rebooted into boot loader.
whitephenix said:
third party boot loader
Click to expand...
Click to collapse
Is it bootloader or custom recovery?
Can you use any of the identifying information at boot to google this site or the web to learn more about the "bootloader" and to put some more info here?
It was a bootloader. I flashed it using adb. Unfortunately it looks like the op I got the bootloader from is gone...
I have also never seen another post for a bootloader for this device... My info reads
*** Unlocked ***
RUBY PVT SHIP S-OFF RL
HBOOT-1.93.0002
eMMC-boot
Mar 15 2012,21:46:51
... I think the menu options might be slightly different all though I have no reference so I'll tell you the two I don't recall originally being in my boot loader excluding my recovery of course.
CLEAR STORAGE
IMAGE CRC
As a further update I have managed to update my recovery to twrp 2.8.1.1 and I have flashed cm11 also I did relock and flash stock ROM. I attempted stock radio but no luck as the bootloader would detect and load but not give me the option to install it instead goes to its stock menus. I have also had device not detected using adb. Killing the server has no affect and I have the correct drivers installed. Specifically I can not initiate the Mainver Error Fix from Hasoon2000's HTC All-In-One Toolkit...
whitephenix said:
As a further update I have managed to update my recovery to twrp 2.8.1.1
Click to expand...
Click to collapse
Might check this, courtesy google:
http://www.igottadroid.com/ModMarket/Listings/electronicrice1612475.html
And some more returns:
https://www.google.com/search?q=hboot-1.93.0002&gws_rd=ssl
Thank you this looks like it will help solve this problem. I will let you know what happens. Thanks.
Ruby is working well, wish their was a firmware to get LTE working on it... Similar or same ship as other LTE phones... Would be nice...
firmware?
whitephenix said:
Ruby is working well, wish their was a firmware to get LTE working on it... Similar or same ship as other LTE phones... Would be nice...
Click to expand...
Click to collapse
The firmware is non-existent--that means it should work just fine on the non-existent hardware.