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.
Related
Hey all, I am thinking about selling my HOX+ and the buyer doesn't want the phone rooted for warranty purposes. Is there a way for me to remove root and restore everything to stock? Thanks in advance!
Please reboot in bootloader and tell me your hboot version and confirm AT&T/TELUS version.
I see HBOOT version but not the AT&T/Telus version.
Here's everything I see
EVITARE_UL PVT SHIP S-ON RL
HBOOT 1.32.0000
CPLD-None
MICROP-None
RADIO-SSD:1.09.55.17
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM921
Oct 20 2012, 13:45:56
eyecrispy said:
I see HBOOT version but not the AT&T/Telus version.
EVITARE_UL PVT SHIP S-ON RL
Click to expand...
Click to collapse
Sure, this is the confirmation.
You need this RUU for your AT&T
Reboot in bootloader mode
Plug in your USB cable
Open a adb command window
At the prompt type>fastboot oem lock
Your phone will reboot.
Again in bootloader mode with FASTBOOT USB highlighted simply run the RUU downloaded
Your phone will be completely wiped including SD card.
What exactly is the RUU? What does it do?
Also, once I do that, how do I get the stock ROM back on it?
Also, once I get back to stock recovery how do I get back to bootloader?
RUU = ROM Update Utility
This will update and restore your phone to it's original state including boot, recovery, rom, etc. Your phone will be exactly like it was the first time you press the Power button.
To access Bootloader simply hold your Volume down rocker and press Power button.
I ran the RUU a few times and it has been stuck on the "Verifying information on your Android phone. Please wait ..." screen for a long time. How long does the RUU run?
I am running win7 from a virtual machine. Not sure if that makes a difference. But the RUU didn't seem to work. Do you have a MD5 for the RUU file you posted?
Would that work if you registered your phone on htcdev.com? Warranty will be void if you unlocked your device, it doesn't matter if its locked again.
eyecrispy said:
I ran the RUU a few times and it has been stuck on the "Verifying information on your Android phone. Please wait ..." screen for a long time. How long does the RUU run?
I am running win7 from a virtual machine. Not sure if that makes a difference. But the RUU didn't seem to work. Do you have a MD5 for the RUU file you posted?
Click to expand...
Click to collapse
Yes maybe the VM can be a problem, I will do search about this. One thing I know. some people says the needed many try before it worked.
MD5 : 3B951A3195E60712A62A4DB6AC181CC7
You can try this one if you want an alternative : RUU_EVITARE_UL_JB_45_Cingular_US
Thanks. What's the difference between the two exe files?
They are the same, only the source is different. Since I am having an TELUS phone I can't test if any of those files are working so I gave you two different source to download the file just "in case..."
In bootloader it will state re-locked after locking bootloader again so its not possible to get back all stock again.
Sent from my HTC One X+ using xda premium
Good day friends.
I hav got a htc one x+ sent to me recently. I turned on the phone to discover it gets stucked at boot logo.....
I hav tried running the ruu for the phone but it wouldnt go through, i guess its because of s-on... I dont kno if there is any other way to fix this issue...
log
***locked***
Enrc28 pvt ship s-on rl
Hboot-1.35.0000
Cplld-none
Microp-none
Radio-3.1204.168.32
Emmc-bootmode: disabled
CPU: bootmode disabled
Hw secure boot: enable
Modem path : off
Nov 14 2012, 16:38:06
Pls help
ebemka said:
***locked***
Enrc28 pvt ship s-on rl
Hboot-1.35.0000
Cplld-none
Microp-none
Radio-3.1204.168.32
Emmc-bootmode: disabled
CPU: bootmode disabled
Hw secure boot: enable
Modem path : off
Nov 14 2012, 16:38:06
Pls help
Click to expand...
Click to collapse
Your bootloader version would still allow using one of the available RUUs (i think the only possible RUU for this bootloader version is 1.17.401.1), but maybe your phone has the "wrong" cid for that RUU. There's a fastboot command that can read your phone's cid, but i don't know what it was right now and since i don't know how much experience you have using ADB & Fastboot, the easiest way is to get yourself some Toolkit from One X+ Forums (for example this: http://forum.xda-developers.com/showthread.php?t=2430358) that can do this for you.
If your phone has an HTC__xxx CID you're lucky and should be able to use the 1.17.401.1 RUU.
Otherwise fastest way to make the phone boot again (my opinion) is unlocking the bootloader, installing a custom recovery and then use any custom rom you like (don't forget flashing the boot.img!).
Ok thanks for ur reply.... Let me try wat u saud
i get stuck on error 132 (customer ID error) whenever itry to run the ruu.... wat might the problerm be????.
ok i hav just unlocked the bootloader, and im trying to run ruu (v1.17.707).... it gives me unknown error...
pls someone should help me out here.
my htc cid is HTC_J15
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!
So today a client brings in her One Max to our shop and explains she bought it on eBay and it never mentioned being modded. The phone boots with a warning message and without doing the correct processes, manages to make it even worse. Currently we are able to boot it into recovery mode and we see:
*** UNLOCKED ***
T6WL PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-2.49.0000
RADIO-1.36.60.0520
OpenDSP-v33.120.274_T6.0829
QSC-
OS-
eMMC-boot 2048MB
Sept 1 2015, 12:43:04.0
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
and at this point, I'm trying just to find a way to load the OEM ROM/Firmware to restore the phone back to factory. Any help/ideas?
@computermikes
Best thing is to run a RUU which will take it all back to factory defaults...
This right here should get it to work. http://flyhalf205.com/RUU/t6vzw/0P3...0_NV_VZW_4.60_002_release_385874_signed_1.exe
You'll need to make sure you have the fastboot drivers installed before attempting to run the file. Google is your friend to get that working...
If that doesn't work. I've always heard that running http://www.htc.com/us/software/htc-sync-manager/ you can recover the latest OEM software for Verizon phones.
NOTE: After running either one. You will need to get back into that HBOOT screen you typed out and select the option for factory reset.