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.
Related
i have an htc flyer 3g/wifi with gingerbread..,and it was S-ON and the Hboot was 1.10.0000
So Recently there was a problem using the facebook App so to solve that problem i had to root it
and i did a S-OFF through that http://forum.xda-developers.com/showthread.php?t=1194709
and i did all the procedures ..,and the Status of the flyer Right now is the Following:
-Revolutionary-
FLYER PVT SHIP S-OFF RL
HBOOT-6.10.1002
MICROP-xxxx
RADIO-xxxxxxxxxxx
eMMC-boot
May 4 2011, 11:04:45
So After Rooting i made some changes in the rom to fix the facebook problem and it completely ruined it ! and now facebook is working again in the normal rom .,but not working with me .,so i want to get back to the stock status and install new unrooted stock g.b rom
so i tried to follow this http://forum.xda-developers.com/showpost.php?p=19339909&postcount=1 and i understood all the procedures but i can't get an hboot downgrade to 1.10.0000 and i don't know from where to get it + i don't really know where to get a stock rom that is compatible
Please i know i'm a noob and probably will be a huge pain in the ass but please someone help me ...,as this matter killing me !!
That hboot number looks weird, you sure its right? Did you do anything besides the S-Off procedure that changed your hboot (S-Off should not have changed that, I don't believe).
I'm assuming you didn't to a nandroid backup through Clockworkmod before messing with the ROM? If you did, just restore it. If not, you should always always always do a nandroid before messing with the ROM and/or doing any mods.
I don't see how returning to S-on is going to help your case at all. Its just a flag that basically allows all security measure to be bypassed. Going back to S-On isn't going to fix the mistakes you made, doesn't get you anything you don't already have, and will actually limit your options. I don't recommend it for that reason.
You can try to flash the stock rooted GB ROM here: http://forum.xda-developers.com/showthread.php?t=1175589
Normally I'd say to just run the correct RUU for your current hboot/firmware. But if you hboot version is messed up, that might be easier said than done.
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
GSM version. I was originally trying to solve my 'wifi-wont turn on' problem, ended up trying to flash a custom ROM, which meant I had to perform the S-OFF wire trick, which was a pain in the ass, but successful.
Right now I'm at the following specs, and no idea how to continue. No matter what I do seems to leave me in the same place. Ive tried multiple ROMs now and every time I try to upgrade/downgrade the hboot or the radio it gives me "model ID incorrect" and reboot.
*** LOCKED ***
SHOOTER_U PVT S-OFF RL
HBOOT-1.53.0007
RADIO-11.253504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
May 22 blah blah
Also have Revolutionary CWM v4.0.1.4
Any help is appreciated!
Ultimately plan on putting a data-only SIM in and mounting it in my car. Don't make me use my Xperia Play instead!
[edit]Forgot to mention I have the PG86310, which after some googling indicates is a bad thing
i dont know about the the PG86310 but you could try using this method to downgrade hboot. then wipe data+caches in recovery and flash a custom rom
Okay I successfully downgraded my hboot to 1.49.008 using a combination of the above link, and files from the original Rogers RUU. I was able to boot the stock ROM and re-unlock my device. I'm now at HBoot 1.49.008, unlocked, S-Off
Stock ROM wifi,bluetooth,gps not working
Tried a 4.2.2 custom ROM (it booted this time!!) and wifi, bluetooth, gps not working.
Dang, this phone never had hardware problems, hoping its something stupid i'm overlooking
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.
Hi I was running insert coin rom and prior to that had updated to kitkat. I've been trying to find the proper RUUs to get back to stock or something like it but I'm stuck in the bootloader and can't use anything at all. I used one RUU but it kept giving me an error and i relocked the device same error so i'm lost.
ZARA_CL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.14.50.0516
OPENDSP-V18 2.0268.0925
OS-2.15.652.2
EMMC-BOOT 1024MB
I got it back to normal after going through HTC DEV and unlocking the bootloader. However I'm trying to re-activate this phone on virgin mobile and while running insertcoin you can't re program the phone so in turn the service isn't working, is there a workaround to this or do i have to somehow go back to stock to get it to work?
We dont have ruu for kk. U can restore a rom http://forum.xda-developers.com/showthread.php?t=2865955