Related
Hi, I hope I didn't miss the thread where this is explained, but:
Yesterday I unlocked und rooted my OneX, successfully. One of the two main reasons I did it was the removal of the 3-dot-bar, so I flashed the fix for that.
After it my phone is stuck at bootloop, factory reset didn't help.
So I tried to recover through an RUU, in my case an 1.26 and 1.28 vodafone RUU, but when I try, it gives me an error 140 wrong bootloader (or something).
Now I'm stuck at this point, as I can't recover with an RUU, and I can't do anything with fastboot, because it throws an "unknown bootloader status" error with any command... so I couldn't flash die boot.img neither...
Now I'm hoping that there is a way to help me and I just missed the right thread in my dispair
Can please someone tell me what I can do now? Thanks in advance.
Have you flashed the stock recovery back?
Sent from my HTC One X using xda app-developers app
will444 said:
Have you flashed the stock recovery back?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes I did, extracted from the correct RUU for Vodafone Germany (which is the UK RUU).
/edit: I also tried recovery from international RUU
What hboot do you have? I can't remember what that error means. You can't flash an RUU with an older hboot, if you have the 1.29 OTA, you have a newer hboot.
What the firmware you have now?
Ah right, as just been mentioned you will need to have the lastest firmware, if you have OTA updated you will have never hboot
Sent from my HTC One X
BenPope said:
What hboot do you have? I can't remember what that error means. You can't flash an RUU with an older hboot, if you have the 1.29 OTA, you have a newer hboot.
What the firmware you have now?
Click to expand...
Click to collapse
I have hboot 0.95 as of 1.29.161.13, hboot of 1.26 is 0.94, so that seems to be the problem, ok.
Somehow I managed to get fastboot running again, means bootloader is unlockable and I tried boot.img and recovery.img from stock RUU, hboot is not allowed...
But there must be anything I can do about it now?
Actually run the correct RUU for your radio and hboot? Revert to stock, the unlock bootloader straight away and restore one of your nandroid backups? That's what I did when I bricked my HOX
Sent from my HTC One X
will444 said:
Actually run the correct RUU for your radio and hboot? Revert to stock, the unlock bootloader straight away and restore one of your nandroid backups? That's what I did when I bricked my HOX
Sent from my HTC One X
Click to expand...
Click to collapse
Well I ran RUU_ENDEAVOR_U_ICS_40_Vodafone_UK_1.28.161.9_Radio_1.1204.103.14_release_256488_signed.exe, but I'm on the OTA updated 1.29, so there is no "correct" RUU, it seems.
This means I'm stuck and can't do nothing about it?
I will try to install a custom firmware, maybe this works...
If you have a backup, just restore a backup through cwm, same thing happened to me.
DoeBoi said:
If you have a backup, just restore a backup through cwm, same thing happened to me.
Click to expand...
Click to collapse
Yeah, I would, but I was very dumb and didn't make one :/
Anyway, Android Revolution HD is up and running and first thing I do now is a nandroid backup ^^
Download a stock Rom so if ARHD fails you always have that glad to hear you haven't totally killed your phone!
Sent from my HTC One X
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
mayashoval said:
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
Click to expand...
Click to collapse
Have you tried relocking your bootloader? 'fastboot oem lock'
Also, maybe try flashing the stock kernel as well?
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
ArmedandDangerous said:
Also, maybe try flashing the stock kernel as well?
Click to expand...
Click to collapse
I'm hesitant about flashing a kernel, as I did not change the original stock one, and it feels too risky.
BenPope said:
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
Click to expand...
Click to collapse
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
mayashoval said:
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
Click to expand...
Click to collapse
I think the update to hboot requires it to be locked, your previous update was most likely ok with the hboot it was on.
mayashoval said:
I thought about that
Click to expand...
Click to collapse
Then look for a backup of your ROM version in the backup thread.
BenPope said:
Then look for a backup of your ROM version in the backup thread.
Click to expand...
Click to collapse
Sorry to be a noob but what do you mean? I thought I couldn't use a backup older than the one listed under "main version". Or am I confusing things?
Edit:
Can I install the most recent RUU?
INFOversion-main: 2.18.751.7.
latest RUU is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_ 2.1204.136.21_release_275588_signed.
Update: locking the phone did not help
I locked the phone, but the update still fails at the same location. The green bar expands for about 20 seconds, covering about a quarter of the bar, and the the red triangle appears.
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
sorry for being a noob
gffmac said:
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
Click to expand...
Click to collapse
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
mayashoval said:
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
Click to expand...
Click to collapse
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
exocetdj said:
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
Click to expand...
Click to collapse
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
mayashoval said:
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
Click to expand...
Click to collapse
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
exocetdj said:
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
Click to expand...
Click to collapse
don't really have a choice now...
downloading maXimus as per your recommendation (and because ADHD will take another 9 hours
You can restore an older backup, it's just like installing a custom ROM.
You might also be able to install a 2.17 RUU on 2.18, I'm not sure the hboot was updated. It's also possible to dissect an RUU and install the bits manually.
You have a few options.
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
Sorry did not find a solution. Ended up installing a custom rom, even though I wanted to keep using the stock one
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
I hope you did this the other way around......first flash the recovery and the relock the bootloader.....
But if you are on stock rom, kernel and recovery you do not have to relock the bootloader, it updates fine with a unlocked one.
Well I tried custom firmware after successfully unlocking my HTC One X. It says Unlocked but S-ON so not sure whats going on there? But since S-On I cannot change the CID as get the error (status read failed (too many links)) MY CID is H3G_001 and since I rooted my phone refuses to let me upgrade to OTA Jellybean which is frustrating forcing custom firmware.
Without updating CID I got stuck in a bootloop at least I guess it was as it was just stuck on the quitely brilliant screen for 20 minutes before I shut it off and tried another firmware which did the same. I am now in the process of a Nandroid recovery so I can at least use the phone. Three have a ton of bloatware which sucks. But I gotta stick with it as cannot figure out why it wont let me flash.. All help is appreciated. This phone is alot harder to flash than my HTC Desire which was a breeze.
Vhero said:
Well I tried custom firmware after successfully unlocking my HTC One X. It says Unlocked but S-ON so not sure whats going on there? But since S-On I cannot change the CID as get the error (status read failed (too many links)) MY CID is H3G_001 and since I rooted my phone refuses to let me upgrade to OTA Jellybean which is frustrating forcing custom firmware.
Without updating CID I got stuck in a bootloop at least I guess it was as it was just stuck on the quitely brilliant screen for 20 minutes before I shut it off and tried another firmware which did the same. I am now in the process of a Nandroid recovery so I can at least use the phone. Three have a ton of bloatware which sucks. But I gotta stick with it as cannot figure out why it wont let me flash.. All help is appreciated. This phone is alot harder to flash than my HTC Desire which was a breeze.
Click to expand...
Click to collapse
you cannot s-off the one x, all you have done is unlock the bootloader which will allow you to flash clockwork recovery and flash su etc.
Unlocked s-on is normal.
Unlocking has nothing to do with s-off
At present there is no way to change your cid.
2x errors have occurred here
Ota updates fail after rooting if you leave the custom recovery on there.
You needed to unlock. Flash or boot custom recovery.
Flash supersu binaries
Flash stock recovery
Then boot ROM.
That way it would have been rooted and still allow ota updates.
You have made things worse by flashing the firmware.zip
By flashing the firmware you have updated your hboot. Probably to 1.36
Which will no longer work for the ICS ROM that is on your phone.
You need to find a nandroid backup for jellybean for your cid.
Just switching to PC to find you some links
ok looked more into it
you should still be able to boot after restoring your nandroid.
dont forget to pull the boot.img from your backup and reflash it as flashing the firmware will have put the JB boot.img on
you will want to restore the stock recovery which you can find in the firmware.zip once you have restored your backup
reboot into your rom and do the OTA that way
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
Unlocked s-on is normal.
Unlocking has nothing to do with s-off
At present there is no way to change your cid.
2x errors have occurred here
Ota updates fail after rooting if you leave the custom recovery on there.
You needed to unlock. Flash or boot custom recovery.
Flash supersu binaries
Flash stock recovery
Then boot ROM.
That way it would have been rooted and still allow ota updates.
You have made things worse by flashing the firmware.zip
By flashing the firmware you have updated your hboot. Probably to 1.36
Which will no longer work for the ICS ROM that is on your phone.
You need to find a nandroid backup for jellybean for your cid.
Just switching to PC to find you some links
ok looked more into it
you should still be able to boot after restoring your nandroid.
dont forget to pull the boot.img from your backup and reflash it as flashing the firmware will have put the JB boot.img on
you will want to restore the stock recovery which you can find in the firmware.zip once you have restored your backup
reboot into your rom and do the OTA that way
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I restored from my nandroid and its working fine, all back to 4.0.4 with the phone unlocked I used CWM-SuperSU-v0.96.zip when i rooted my phone (or at least im sure I did as I did root over 6 months ago now).
So how would I go about updating to a custom firmware then?? Instead of the OTA as would prefer to get rid of the bloatware as half the apps aren't even English..
If you want a custom ROM
Try looking at something like latest android revolution HD
Very similar to stock but no bloat.
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
If you want a custom ROM
Try looking at something like latest android revolution HD
Very similar to stock but no bloat.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Okay thanks for that but how do I get it to work with my CID is what I would like to know do I have to first get OTA jellybean working then a custom firmware to update the CID? It seems a little confusing.. I listed my CID in first post but like I also said all custom firmwares I tried Viper X 3.3.4 and skydragon both left me with a phone stuck on boot screen for 20 minutes until i gave up and just turned off.
Your cid is irrelevant for anything except going to stock.
Custom ROMs arnt dependent on cid.
But they are dependent on hboot versions.
Cm10 ROMs will not work on any hboot>1.12
Any sense jellybean ROMs or ROMs with 3.1 kernels need a hboot version of at least 1.23
Couldn't saw viperx ROM but dragon is based on 3.17 so your hboot has to be minimum of 1.23
After installing the custom ROM you did flash the boot.IMG in fastboot didn't you?
Sent from my HTC One X using xda app-developers app
where i get the boot.img? I think i may have missed that part *duh* OKAY nm found that hboot is 1.12 need to update... Updating the Hboot means I have to go back to stock right? Then update OTA to get Hboot update then I can get JB..
Odp: Bootloop and changing CID issues
Vhero said:
where i get the boot.img? I think i may have missed that part *duh* OKAY nm found that hboot is 1.12 need to update... Updating the Hboot means I have to go back to stock right? Then update OTA to get Hboot update then I can get JB..
Click to expand...
Click to collapse
You need a stock boot.img, stock recovery and a stock ICS Rom. Then you will get OTA to JB, upgrading that way your hboot. Then you can flash any custom JB Rom.
P.s. The correct boot.img is in the rom's zip folder. Every time you change the rom you should flash the proper boot.img.
Wysyłane z mojego HTC One X za pomocą Tapatalk 2
bartdeli said:
You need a stock boot.img, stock recovery and a stock ICS Rom. Then you will get OTA to JB, upgrading that way your hboot. Then you can flash any custom JB Rom.
P.s. The correct boot.img is in the rom's zip folder. Every time you change the rom you should flash the proper boot.img.
Wysyłane z mojego HTC One X za pomocą Tapatalk 2
Click to expand...
Click to collapse
Yeah problem is I need RUU_ENDEAVOR_U_ICS_40_H3G_UK_2.17.771.3 to go back to stock and it doesn't exist.. Anyway around the RUU exe ?
EDIT NM found I can use the nandroid method.. Giving it a shot now.
Go here
http://forum.xda-developers.com/showthread.php?t=1975140
And download your matching nandroid ! Restore it including flashing the boot.img from the nandroid. After that you flash this recovery back
http://db.tt/U5CK4noo
And you are on stock again. And also able to update to JB
That did NOT work I got back to stock but without the RUU exe file it seems it will not install I loveked my phone aswell and when i try to install the OTA update i just get kicked to bootloader.
Edit didnt see above post sorry
So did it work.....I know my method works !
Sorry yeah it worked Was up till stupidly late trying to do it as I was following another method as I never saw yours (a really old one) Where I locked my phone so had to unlock etc.. Plus download that update OTA each time took 1 hour. I'm now on stock with Hboot 1.39 thankyou so much really appreciate! So now I just reflash recovery yeah? And backup nandroid then go for my custom rom?
Yes exactly !
I now have Android Revolution working perfectly and since I paid for Nova Prime I decided to go for lite after all and removed Sense thank so much for that method so much easier than the guides on here which make it sound so difficult I really was pulling my hair out!
Nice ! Glad it worked :thumbup:
CASE CLOSED !
Helloou, i made nandroid twrp backup my stock rom and flashed Ice cold jelly to my phone, i didnt liked so i decided to restore nandroid and stock recovery and relock my bootloader. I restored and booted up my phone and everything worked. Then i flashed stock recovery and relocked phone and it boots only in bootloader and flashes something developer purposes only whatsoever and then goes to bootloader and then it says relocked security warning and only boots in bootloader when trying to reboot. When i unlock my bootloader - stock rom works perfectly but as soon as i relock it says security warning. Dafuq my phone is doing?
Sent from my HTC One X using xda premium
Why do you want to relock the bootloader?? You can get OTA updates with unlocked bootloader...
About the issue, did you flash the correct stock recovery??
I didnt know that i dont have to lock bootloader to get ota updates now i know but still why when relocking this error comes? I flashed stock recovery 3.14 hboot 1.39 and my main version is 3.20.401.1 cid htc y13. And when might the 3.20.401.3 update come to cid y13? In cid 032 its already got and main version is same?
Sent from my HTC One X using xda premium
The .3 update is just a minor software update... even if you don't get it, it's ok...
No idea about the lock thing though... If you are on full stock with stock recovery, then try factory resetting your phone from bootloader...
Maybe i try it in weekend but weird thing still
Sent from my HTC One X using xda premium
Problem solved! I relocked again but now i used linux mint and not win xp and everything works now.
Sent from my HTC One X using xda premium
I was helping out a friend to flash a custom rom , to update his device to a newer version , as a former LG optimus 3d owner i figured nothing can be more problematic , so we went on to unlock the device with easyunlocker tool , then flashed the latest twrp recovery from fastboot. We first tried Legacycarbon , it was stuck in a bootloop with htc logo without the quietly brilliant bit. Then we tried pac-man 4.2.2 bootloop again , lastly we tried cyanogenmod 10.1 again bootloop... First i thought maybe it's the recovery , i flashed the latest clockwork non-touch and flashed all these roms , still bootloop... My friend accidentally wiped the backup we made of the stock rom. Now the device is soft bricked. I've heard people talk about 4ext recovery , so i thought maybe i should give it a try but as it turns out , the only way to install it is with the play store app. As the device is soft bricked i need a fastboot image.
So my question is , what could be the problem ?
If you think the the problem is with the recovery can you export your recovery partition so i can use it through fastboot?
Sent from my Nexus 4 using XDA Premium 4 mobile app
You can flash the. .img file from fastboot, but recovery is not the problem. Try wiping all partitions (/data /cache and /system), and flashing a rom
Inviato dal mio GT-I9100
totalnoob34 said:
You can flash the. .img file from fastboot, but recovery is not the problem. Try wiping all partitions (/data /cache and /system), and flashing a rom
Inviato dal mio GT-I9100
Click to expand...
Click to collapse
Yeah , i left that out. As a nexus owner i have a habit of wiping my system , data , cache and dalvik-cache partitions. I've managed to get a recovery backup from another friend who owns the same device , and flashed it to the phone , now it's working.
Although i'm very curious as to why it gets stuck in a bootloop...
I think it may be because of the partition size difference , then the ROMs that i downloaded didn't contain partition images , still it was through teamviewer , i couldn't really extract his partition table to take a look at it , i'll do that when i get my hands on the device.
Hi! It seems to be the same problem I met since friday. My HTC DESIRE HD doesn't want to start, it goes on a bootloop at the logo cyanogenmod.. I had the CM 10.1, so I have now tested to make a new installation by replacing it with a newer version of CM 10.1 but it's always the same problem.. bootloop again and again.
Moreover I have flashed the boot.img which was in the folder off CM 10.1 but no result.. I've tried to do it with MIUANDROID rom and it seems to be the same bootlooping again..
Please can someone help me?
Thanks
sosointello said:
Hi! It seems to be the same problem I met since friday. My HTC DESIRE HD doesn't want to start, it goes on a bootloop at the logo cyanogenmod.. I had the CM 10.1, so I have now tested to make a new installation by replacing it with a newer version of CM 10.1 but it's always the same problem.. bootloop again and again.
Moreover I have flashed the boot.img which was in the folder off CM 10.1 but no result.. I've tried to do it with MIUANDROID rom and it seems to be the same bootlooping again..
Please can someone help me?
Thanks
Click to expand...
Click to collapse
Try flashing a RUU. If that is not working and you are still on a bootloop then it might be a motherboard issue.
glevitan said:
Try flashing a RUU. If that is not working and you are still on a bootloop then it might be a motherboard issue.
Click to expand...
Click to collapse
be careful as re installing RUU might not let you re rooting it ...
zinedzine said:
be careful as re installing RUU might not let you re rooting it ...
Click to expand...
Click to collapse
How come?
Sent from my Nexus 7 using xda app-developers app
zinedzine said:
be careful as re installing RUU might not let you re rooting it ...
Click to expand...
Click to collapse
He should be able to unlock with HTCDev and root, or use the AAHK2 to s-off and root. I'm not sure if OP had already unlocked the bootloader, but there's a chance that the ruu won't update it (newer/same version as included in the ruu) meaning he'd keep his BL unlock
Sent from my Desire HD using Tapatalk
from what i've read here on the forum, and if my understanding is correct, ruu are like "original" roms. files that we don't flash from recovry.
it's a différent method and in the end we obtain a stock phone with an "untouched" os like an original one.
if it is the case then you should install a ruu with android 2.3.5 on it, as if you update up to a ruu with android 2.3.7, again from what i've read, it won't be possible to root back the phone then.
i might be wrong but just thought i'll point it out to you so you can research on that.
it's possible that by now there is a way, but i havn't read or heard about it.
Justice™ said:
He should be able to unlock with HTCDev and root, or use the AAHK2 to s-off and root. I'm not sure if OP had already unlocked the bootloader, but there's a chance that the ruu won't update it (newer/same version as included in the ruu) meaning he'd keep his BL unlock
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Well you are definitely wrong. All versions are rootable. Ruu stands for remote update utility and it is the stock firmware of the device.
You cannot flash a ruu in recovery but have to do it in fastboot. From there you can unlock the bootloader and root.
Sent from my Nexus 7 using xda app-developers app
glevitan said:
Well you are definitely wrong. All versions are rootable. Ruu stands for remote update utility and it is the stock firmware of the device.
You cannot flash a ruu in recovery but have to do it in fastboot. From there you can unlock the bootloader and root.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I think I might've completely screwed up what I was trying to say or you may have misunderstood what I was saying. So I'm just going to refer back to what I was trying to explain in context of an older HTC device (Wildfire, in this case).
In some scenarios with the Wildfire, we were able to run an RUU and successfully roll back to a stock rom whilst retaining a S-OFF bootloader (Meaning the ability to use fastboot to flash a recovery and root using a su zip was possible). I think I was trying to say this may be possible/may occur with the DHD. Meaning that OP would just have to use fastboot to flash a recovery and an appropriate superuser zip to get root, and therefore any version would be rootable (even if he rolled back). However at this point I'm not sure if the DHD RUU's overwrite the hboot/bootloader. (I've never really felt like flashing one and I don't feel like getting another sim unlock code at this point)
Justice™ said:
I think I might've completely screwed up what I was trying to say or you may have misunderstood what I was saying. So I'm just going to refer back to what I was trying to explain in context of an older HTC device (Wildfire, in this case).
In some scenarios with the Wildfire, we were able to run an RUU and successfully roll back to a stock rom whilst retaining a S-OFF bootloader (Meaning the ability to use fastboot to flash a recovery and root using a su zip was possible). I think I was trying to say this may be possible/may occur with the DHD. Meaning that OP would just have to use fastboot to flash a recovery and an appropriate superuser zip to get root, and therefore any version would be rootable (even if he rolled back). However at this point I'm not sure if the DHD RUU's overwrite the hboot/bootloader. (I've never really felt like flashing one and I don't feel like getting another sim unlock code at this point)
Click to expand...
Click to collapse
No problem man, but Hboot and S-OFF are not the same. All RUU's have partitions in them including bootloader, however nand partition is not reverted to S-ON by flashing an stock rom, unless you specifically do that. There is no risk to lose the S-OFF state by flashing a RUU.
glevitan said:
Well you are definitely wrong. All versions are rootable. Ruu stands for remote update utility and it is the stock firmware of the device.
You cannot flash a ruu in recovery but have to do it in fastboot. From there you can unlock the bootloader and root.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I stand corrected Monsieur :highfive:
??
i dont now .......:cyclops:
I didn't see mention of s-off in your question. If you are not s-off, you have to extract the rom's boot.IMG and fastboot flash it after rom installation.
Sent from my Nexus 5 using xda app-developers app
You can install with RUU, then u can downgrade, root, s-off it with AAHK2. So it's possible to root it