(reposted, I *think* this is the right forum... if not, mod, please move to where appropriate.
Phone: AT&T HTC OneX+
TWRP 2.6.0.0 installed
Bootloader says:
***UNLOCKED***
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.40.0000
CPLD-None
MICROP-None
RADIO-SSD:2.14.55.01
eMMC-bootmode: DISABLED
CPU-BOOTMODE: DISABLED
HW SECURE BOOT: ENABLED
MODEM TYPE: MDM9215M
DEC 28 2012
I have tried using Windroid universal toolkit v1.2; Hasson2000's all in one toolkit v3.0; command line included in adt-bundle-windows-x86_64-20140702 (Eclipse 23.0.2.19...)
So, I was trying to unlock, root and flash the phone with a new ROM. I have managed to bugger the phone beyond recognition. There is no OS on at this time, and I am unable to flash any ROM. I was shooting for AOKP-42-20130714 with gapps-jb-20130301-signed, but the phone kept complaining about all the google suite apps stopping, over and over.
I tried a gazillion searches, tried all kinds of methods, nothing.
In my frustration, I ended up doing an advance wipe thinking a fresh install of everything would help. Well, not even ADB sideload is helping any and fails miserably.
TWRP constantly complains that ""device does not appear to be rooted. Install SuperSU now?" Over and over, so apparently that is failing too.
So, if you have a solution beyond the plain vanilla answers, let me know. I am tempted to say that I'll paypal $50 to the person that actually can figure out the problem AND helps walk me through the steps to get this effing phone going again.
Related
Hi there,
I'm trying to flash a new recovery via fastboot but all I get is this strange error-message.
Do you guys know, how to fix the problem?
Thank you!
(Reason for flashing: cmd seems to went crazy, and it's not working anymore. It's saying it can't find the pathes/partitions)
Ok, now I can't even reach the bootloader anymore (pwr+voldown).
I just don't get on what level my phone has the problem.
Ridicilously enaugh it even boots my (still very bad working) system again, which I thought would by numerous flashing attemps be totally destroyed by now.
Can someone give a hint what's going on there?
Ok, well. Had a closer look to the Header of Bootloader (which is working now again, for no reason).
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.39.0000
CPLD-None
MICROP-None
RADIO-5.1204.163U1.30
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Dec 17 2012,13:59:37
It's saying something about "S-ON". Might this be the reason why my recovery wasn't working properly?
Do I have to put it back to S-OFF? How can I do this?
Thank you
my phone's OS has been wiped via twrp v2.6.0 because i screwed something up and thought wiping the system would just wipe the change i made. clearly it wiped the entire OS and so now all i have is a device that can boot into botloader. i have tried several times to use th RUU that everyone said to use in order to revert it to the factory condition, but every time it comes back with the 158 error saying i dont have the correct ROM to put on it just after it attempts to update the signature. the RUU i downloaded is titled RUU_EVITARE_UL_JB_45_Cingular_US_1.15.502.9_Radio_1.09.55.17_18.20.95.55L_release_290329_signed.exe and i have had multiple sources say this is the one i need for my device yet every time i run the RUU it comes back with the same error. everything else about the RUU seemed to work. when i boot the device into bootloader the section at the top reads
*** RELOCKED ***
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MICROP-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot:enabled
MODEM TYPE : MDM9215M
Sep 30 2013, 17:16:15
all i want is the correct RUU for my device and a working phone. i cant afford another phone and i need a working phone. please please somebody help.
Farrric said:
my phone's OS has been wiped via twrp v2.6.0 because i screwed something up and thought wiping the system would just wipe the change i made. clearly it wiped the entire OS and so now all i have is a device that can boot into botloader. i have tried several times to use th RUU that everyone said to use in order to revert it to the factory condition, but every time it comes back with the 158 error saying i dont have the correct ROM to put on it just after it attempts to update the signature. the RUU i downloaded is titled RUU_EVITARE_UL_JB_45_Cingular_US_1.15.502.9_Radio_1.09.55.17_18.20.95.55L_release_290329_signed.exe and i have had multiple sources say this is the one i need for my device yet every time i run the RUU it comes back with the same error. everything else about the RUU seemed to work. when i boot the device into bootloader the section at the top reads
*** RELOCKED ***
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MICROP-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot:enabled
MODEM TYPE : MDM9215M
Sep 30 2013, 17:16:15
all i want is the correct RUU for my device and a working phone. i cant afford another phone and i need a working phone. please please somebody help.
Click to expand...
Click to collapse
I imagine you can have TWRP mount the storage and put one of the ROMs (like Elegencia) and then flash it.
Farrric said:
my phone's OS has been wiped via twrp v2.6.0 because i screwed something up and thought wiping the system would just wipe the change i made. clearly it wiped the entire OS and so now all i have is a device that can boot into botloader. i have tried several times to use th RUU that everyone said to use in order to revert it to the factory condition, but every time it comes back with the 158 error saying i dont have the correct ROM to put on it just after it attempts to update the signature. the RUU i downloaded is titled RUU_EVITARE_UL_JB_45_Cingular_US_1.15.502.9_Radio_1.09.55.17_18.20.95.55L_release_290329_signed.exe and i have had multiple sources say this is the one i need for my device yet every time i run the RUU it comes back with the same error. everything else about the RUU seemed to work. when i boot the device into bootloader the section at the top reads
*** RELOCKED ***
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MICROP-None
RADIO-SSD:2.21.5517.15
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot:enabled
MODEM TYPE : MDM9215M
Sep 30 2013, 17:16:15
all i want is the correct RUU for my device and a working phone. i cant afford another phone and i need a working phone. please please somebody help.
Click to expand...
Click to collapse
according to your hboot you have the newest hboot (1.73)for the android 4.2.2 sense5 which is why the ruu you have wont flash that is the old 4.1.1 ruu meant for hboot 1.40 so youll either need to sideload a rom or wait for the official RUU to be released.
So I've been struggling for the last 4 days now with the following situation:
A part of my touchscreen (a horizontal line in the middle of my screen), stopped working and I want to make use of the warranty.
Since I've unlocked and flashed my phone I'll need to return it to stock first.
I've tried a lot of RUU's all saying "ROM Image Error". (Of course relocked my phone everytime before running a RUU).
The things I already tried hoping the RUU would work:
- flashing different roms
- flashing different kernels
- flashing different recovery's
- restoring someone else's backup using TWRP
At the moment I'm close to giving up, leaving me with this actual state:
***UNLOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT 1.72.0000
CPLD-NONE
MICROP-NONE
RADIO 3.1204.171.33
eMMC-bootmode: Disabled
CPU-bootmode: Disabled
HW Secure boot: Enabled
MODEM PATH: OFF
TWRP 2.3.2.3
CyanogenMod 10.2.1-enrc2b
Android 4.3.1
Kernel version 3.1.10-g0324fc1
(also tried it on Windows 7 instead of a Windows 8.1)
I can't imagine there isn't a solution to get a RUU working.
jimscheltus said:
So I've been struggling for the last 4 days now with the following situation:
A part of my touchscreen (a horizontal line in the middle of my screen), stopped working and I want to make use of the warranty.
Since I've unlocked and flashed my phone I'll need to return it to stock first.
I've tried a lot of RUU's all saying "ROM Image Error". (Of course relocked my phone everytime before running a RUU).
The things I already tried hoping the RUU would work:
- flashing different roms
- flashing different kernels
- flashing different recovery's
- restoring someone else's backup using TWRP
At the moment I'm close to giving up, leaving me with this actual state:
***UNLOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT 1.72.0000
CPLD-NONE
MICROP-NONE
RADIO 3.1204.171.33
eMMC-bootmode: Disabled
CPU-bootmode: Disabled
HW Secure boot: Enabled
MODEM PATH: OFF
TWRP 2.3.2.3
CyanogenMod 10.2.1-enrc2b
Android 4.3.1
Kernel version 3.1.10-g0324fc1
(also tried it on Windows 7 instead of a Windows 8.1)
I can't imagine there isn't a solution to get a RUU working.
Click to expand...
Click to collapse
Your right, you can't restore using an RUU past hboot version 0.4. However here is the latest stock backup. If you restore in TWRP and then flash the firmware.zip you end up with at least a look alike stock. I think you can also modify the "relocked" message in the bootloader to "locked" once more. This should fool the shop/retailer easily!
file are here: http://forum.xda-developers.com/showthread.php?t=2414238
I had an issue with the file service though. If that happens then just download the megadownloader program to download it properly
Hope this helps.
Dr.ripsaw said:
Your right, you can't restore using an RUU past hboot version 0.4. However here is the latest stock backup. If you restore in TWRP and then flash the firmware.zip you end up with at least a look alike stock. I think you can also modify the "relocked" message in the bootloader to "locked" once more. This should fool the shop/retailer easily!
file are here: http://forum.xda-developers.com/showthread.php?t=2414238
I had an issue with the file service though. If that happens then just download the megadownloader program to download it properly
Hope this helps.
Click to expand...
Click to collapse
Alright, It's worth the try. Also, will this change my Hboot version?
I also found out it's impossible to get the 'LOCKED' message back. Relocked is as close we can get :')
But that doesn't automatically mean that the warranty won't pay the repair. When they find a custom rom on your phone it's a different story though. This because a custom rom could mean I overclocked my CPU for example.
jimscheltus said:
Alright, It's worth the try. Also, will this change my Hboot version?
I also found out it's impossible to get the 'LOCKED' message back. Relocked is as close we can get :')
But that doesn't automatically mean that the warranty won't pay the repair. When they find a custom rom on your phone it's a different story though. This because a custom rom could mean I overclocked my CPU for example.
Click to expand...
Click to collapse
Well When I got my phone I allowed it to update to the latest version of android and so it upgraded my Hboot version. To get the latest version you need to flash the latest firmware. I think restoring a backup that is the newest version of stock will automatically update your Hboot. Don't take my word for it as I've said my Hboot was fully updated before I started Modding.
Good day,
So, i searched the forums on how to root the HTC One X+, and got to the point of unlocking the bootloader, everything was fine until i tried to install the custom recovery, I'm going to be honest, I had no idea what i was doing and ended up trying to factory reset from the hboot, and now I'm stuck at the HTB boot screen, it wont go further.
I have no idea what to do next, i tried searching but its too confusing to go for each solution.
So the question is, can i install a custom ROM from here or should i go for the stock ROM?
I don't think i have an SD mount done either.
I have stock recovery and here's the info on the bootloader screen:
Code:
*** UNLOCKED ***
EVITARE_UL PVT SHIP S-ON RL
HBOOT - 1.40.0000
CPLD - None
MICROP - None
RADIO-SSD: 2.14.55.01
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Dec 28 2012,22:18:14
The MID is: PM6310000
The CID is: CWS_001
EDIT:
Ok so i got TWRP recovery working, and tried sideload, i'm trying to use the Android Revolution HD ROM but its apparently too big...
In windows the memory size is of 156MB, which is strange.
I think i have to use an RUU from what i have read, but i have no idea which file i should actually use.
EDIT 2:
I Got it working, so this is no further needed.
Any help would be highly appreciated.
Thanks in advance!
hello. Going to give all the facts and what i know. Would really appreciate some help!
1. rooted phone and unlocked bootloader
2. downloaded liquidsmooth
3. DID NOT BACKUP!!!! (stupid...i forgot)
4. Accidentally erased os from my phone! Why? because i am used to clockwork recovery. first time using twrp and thought i was resetting phone....accidentally erased everything.
5. NEVER S OFFED!!! (again...stupid, i forgot
6. learned how to push custom ROM into phone after 6 hours of downloads and tinkering.
7. phone did not run well on liquid smooth, regretted rooting the phone all together but i tried a few different ROMS and none worked well.
8. tried to revert back to stock......FAILED. Cannot load RUU because s on. every single RUU file attempt fails
9. here is a list of things i cannot do. A. cannot s off B. cannot download RUU file C. cannot getvar from command prompt. it is empty.
10 I JUST WANT TO GET BACK TO STOCK!!!!!
I've been rooting and custom romming for years. This phone really got me by the balls! Makes me feel like a noob. On the plus side, I've learned a lot about command prompts
Phone info.
att m7
M7_UL PVT SHIP S ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
childspsongs said:
hello. Going to give all the facts and what i know. Would really appreciate some help!
1. rooted phone and unlocked bootloader
2. downloaded liquidsmooth
3. DID NOT BACKUP!!!! (stupid...i forgot)
4. Accidentally erased os from my phone! Why? because i am used to clockwork recovery. first time using twrp and thought i was resetting phone....accidentally erased everything.
5. NEVER S OFFED!!! (again...stupid, i forgot
6. learned how to push custom ROM into phone after 6 hours of downloads and tinkering.
7. phone did not run well on liquid smooth, regretted rooting the phone all together but i tried a few different ROMS and none worked well.
8. tried to revert back to stock......FAILED. Cannot load RUU because s on. every single RUU file attempt fails
9. here is a list of things i cannot do. A. cannot s off B. cannot download RUU file C. cannot getvar from command prompt. it is empty.
10 I JUST WANT TO GET BACK TO STOCK!!!!!
I've been rooting and custom romming for years. This phone really got me by the balls! Makes me feel like a noob. On the plus side, I've learned a lot about command prompts
Phone info.
att m7
M7_UL PVT SHIP S ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Click to expand...
Click to collapse
CID: 90014a4842473465040101b7ff3330be