I know this is asked a lot n believe meive searched a lot...I need an ruu but cant find it anywhere.
the reason for this is my phone kept on rebooting, but not in recovery or bootloader so it made me think its a software issue. Ive tried a new rom but no luck,,,,it still happens. I though returning to stock would be to back it up before flashing roms. I guess im wrong? my back up has disappeared n I cant find a working ruu link anywhere n I have searched for absolutely hours!!
can anyone help please
phone in bootloader says
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-none
MI CROP-none
RADIO-3.1204.171.33
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW secure boot: enabled
MODEM PATH: OFF
Jun 21 2013,17:36:36
orange uk if that helps
I'm guessing you didn't manually flash the kernel via fastboot. Do this before you even consider an ruu flash.
Sent from my HTC One X+ using Tapatalk
sixcarnage said:
I'm guessing you didn't manually flash the kernel via fastboot. Do this before you even consider an ruu flash.
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
i did everything right buddy. the problem I had with the ruu is that I couldn't find one for my phone n if I did the link ended up being a load of rubbish. I had no choice but to claim for a new phone again anyway
Related
okay so sometimes the touch panel on my phone wasnt working right so i decided to make it stock so i can return it to htc so they can fix the screen.
so i first relocked the bootloader using qbking77 instructions and then i tries to ruu but i used the wrong ruu and now my phone is stuck at the bootloader
here is the information
***TAMPERED***
***RELOCKED***
***SECURITY WARNING***
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.000
RADIO-1.12.11.1210
OPENDSP-v31.1.0.45.0815
eMMC-boot
OCT 18 2012, 15:46:20
if i try to reboot or factory reset it doesnt just boots and comes to the bootloader so i need help determining which ruu i need to use and where i can find it. if any one canhelpp id most dearly appreciate it
thanks
afgomar said:
okay so sometimes the touch panel on my phone wasnt working right so i decided to make it stock so i can return it to htc so they can fix the screen.
so i first relocked the bootloader using qbking77 instructions and then i tries to ruu but i used the wrong ruu and now my phone is stuck at the bootloader
here is the information
***TAMPERED***
***RELOCKED***
***SECURITY WARNING***
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.000
RADIO-1.12.11.1210
OPENDSP-v31.1.0.45.0815
eMMC-boot
OCT 18 2012, 15:46:20
if i try to reboot or factory reset it doesnt just boots and comes to the bootloader so i need help determining which ruu i need to use and where i can find it. if any one canhelpp id most dearly appreciate it
thanks
Click to expand...
Click to collapse
You need to get s-off via dirty racun... Then if you wanna go back to completely stock/unroot use VipeRuu, this because it looks like you are on the latest firmware for which we do not have an official RUU...
Sent from my EVO using xda app-developers app
You will have to unlock your bootloader again and install a 3.16 based rom. Your touch screen problems are most likely not the screen but are caused by the touch panel drivers that were installed when you upgraded your firmware. Once you are on the latest firmware you can only use roms based on 3.16 and twrp recoveries that are 2.4 or newer. If you want to use older roms or AOSP roms you will need to go s-off and downgrade your touch panel drivers. Also, HTC won't do anything to fix your screen because you used the developer unlock and voided your warranty.
WOW thank you guys so much for ur help.this is the reason why i love the xda members so much they always come through with the help. :good:
i thought my device was done for good but i worked on it for a couple hours and i fixed it and its now rooted.
now my only issue is with the touch screen anyone know how i can fix that?
afgomar said:
WOW thank you guys so much for ur help.this is the reason why i love the xda members so much they always come through with the help. :good:
i thought my device was done for good but i worked on it for a couple hours and i fixed it and its now rooted.
now my only issue is with the touch screen anyone know how i can fix that?
Click to expand...
Click to collapse
If your touch screen isn't responding once your phone boots, you have the updated touch panel driver and will have to use ROM's based off software version 3.16. You also must use TWRP version 2.4+. Once you gain S-off you can downgrade your touch panel driver and run whatever ROM you wish
Sent from my EVO using xda premium
I have an unlocked HTC One X+ (international)
Can someone help me to install stock ROM on my phone? Something went wrong when I wanted to install a new ROM.
After start-up, it boot only into bootloader or recovery (no ROM installed) and can not mound /sdcard.
I cant find the correct version of stock ROM or RUU and dont know how to put it to the phone.
Unlocked
ENRCB_U PVT SHIP S-ON RL
HBOOT-1.35.0000
CPLD-NONE
MICROP-NONE
RADIO-3.1204.168.32
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
CID: O2___001
Hi,
U cant find the ruu bcuz there is none for hboot 1.35 and above on O2.
Adb still working? Did u try to sideload the rom-btw. Which rom?
Sent from my HTC One X+ using xda premium
subAlot said:
Hi,
U cant find the ruu bcuz there is none for hboot 1.35 and above on O2.
Adb still working? Did u try to sideload the rom-btw. Which rom?
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
I also tried through Sideload from different PCs, but without results.....error: device not found
Is there any solution for me to run my phone or downgrade the hboot?
mabe a ´lil off-topic:
a few weeks(or was it month already?) ago there was an update for the htc sync manager-after installing the update adb stopped working 4 me.
i had to uninstall htc driver & reinstall it- otherwise adb did not show my device via adb devices...
sorry man...as far as i know there is no option to downgrade hboot due to no s-off??? (i could be wrong...)
maybe som other guys over here hav som ideas???
cheers
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.
i tried iinstalling every rom i could find for htc 4g lte using twrp 2.7 i neither stock or custom
ive tried using the stock RUU while on fastboot still no luck. i'm thinking if i could only get S OFF
or find a good rom thats compataible with my phone ed i really wanted sense 5 but right now
i just want my pnhone working again :/
tamper
unlocked
jewel pvt ship S-ON RL
Hboot-2.09.0000
radio 1.13.110330.015
emmc-boot
open dsp--v31.1.0.45
You'll have to relock your bootloader first if you want to run the RUU. (fastboot oem lock) Also, check out @Magnum_Enforcer he has a guide for S-on Rom and kernel flashing.
Sent from my LGLS990 using Tapatalk
kinggizmoe said:
i tried iinstalling every rom i could find for htc 4g lte using twrp 2.7 i neither stock or custom
ive tried using the stock RUU while on fastboot still no luck. i'm thinking if i could only get S OFF
or find a good rom thats compataible with my phone ed i really wanted sense 5 but right now
i just want my pnhone working again :/
tamper
unlocked
jewel pvt ship S-ON RL
Hboot-2.09.0000
radio 1.13.110330.015
emmc-boot
open dsp--v31.1.0.45
Click to expand...
Click to collapse
Hit the top link in my sig and take a read. Lots of useful info:thumbup:
Your issue is that while your phone is S-on you have to install the kernel separately from the ROM either via fastboot or the Flash Image GUI app, unless you install a ROM that includes a kernel installer (for example, MeanBean ROM).