Related
Im currently having problems installing the official ruu, it requires for me to download and install htc sync which i have, my mate did a factory reset on the custom rom which messed it up!, Im having difficulty installing custom roms, I only managed to install miui that works, but htc sync isnt picking it up, the rest dont boot up just stay at htc screen, is there any way to install it via bootloader? or anyone provide a official rom that will install?, Its got cm7/r2 hboot, I just need to make it official please, any help will do, thanks
shaky153 said:
...Its got cm7/r2 hboot...
Click to expand...
Click to collapse
Try with the stock hboot...(or the downgrader hboot only if u need s-on again)
after, u can run the ruu
shaky153 said:
Im currently having problems installing the official ruu, it requires for me to download and install htc sync which i have, my mate did a factory reset on the custom rom which messed it up!, Im having difficulty installing custom roms, I only managed to install miui that works, but htc sync isnt picking it up, the rest dont boot up just stay at htc screen, is there any way to install it via bootloader? or anyone provide a official rom that will install?, Its got cm7/r2 hboot, I just need to make it official please, any help will do, thanks
Click to expand...
Click to collapse
try my guide. Since you're on cm7r2 hboot remember to flash bravo stock before you use the RUU
Essentially, all you can do is fastboot flash hboot downgrade.img then RUU again.
This is a record. Twice in one day. We need a sticky just for this issue
Sent from my HTC Desire using xda premium
rootSU said:
This is a record. Twice in one day. We need a sticky just for this issue
Click to expand...
Click to collapse
changed the title of my thread.. so now maybe it's a little more obvious as to what it contains and maybe people will actually bother to look..
The problem is partly possibly that the stickies in the app are in a different tab
Sent from my HTC Desire using xda premium
I seem to be having a problem flashing the stock + rooted rom.
I get the error message..
e:cant open sdcard/dhd_wwe_3.12.405.1............zip (bad) installation aborted.
I have also tried a stock unrooted copy which didnt work either. I am pretty sure i use to be able to flash it(many months ago).
I believe i can still flash sum custom roms (just formated the newest leedroid rom) but stock is being a ***** to install.
I want to go back to stock as I feel my gps was more accurate under stock
Any ideas?
Im using a unbranded UK desire HD with AHK Clockwork Recovery v4.0.1.4. i did wipe data/factory reset, wipe cache and even wipe Dalvik
Any questions just ask
You don't have to flash stock rom from recovery like custom roms or nandroid backups.
Run stock RUU.exe or flash the rom from bootloader if in PG58IMG format if you want to go back to complete stock rom.
You can download RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_R_Radio_12.65.60.29_26.14.04.28_M_release_233505_signed form HERE
kualmente said:
You don't have to flash stock rom from recovery like custom roms or nandroid backups.
Run stock RUU.exe or flash the rom from bootloader if in PG58IMG format if you want to go back to complete stock rom.
You can download RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_R_Radio_12.65.60.29_26.14.04.28_M_release_233505_signed form HERE
Click to expand...
Click to collapse
Ok, thanks... Which one of these if any would you recommend? (they seem to be exe files which i dont understand why)
http://shipped-roms.com/index.php?category=android&model=Ace
see above. Run the RUU exe from pc while phone is plugged with usb cable.
I uploaded it for you. That is the latest stock GB RUU.
Hope it helps
Hit thanks button if it did
kualmente said:
You don't have to flash stock rom from recovery like custom roms or nandroid backups.
Run stock RUU.exe or flash the rom from bootloader if in PG58IMG format if you want to go back to complete stock rom.
You can download RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_R_Radio_12.65.60.29_26.14.04.28_M_release_233505_signed form HERE
Click to expand...
Click to collapse
Hey mate, maybe u can help me out a little. I need to flash back to stock, vodafone au branded for warrenty purposes. if I used above would I still be rooted and s-off, and can all the Vodafone bloat be flashed afterwards. just weighing if the above link is any easy option then flashing rom, then radio, reverse s off, root, etc etc etc.....etc.?
The link I gave is for stock unbranded WWE (world wide english) RUU. No idea where you can find Vodafone AU, sorry.
Running the RUU.exe will unroot your device but s-off remains. Also it deletes all apps and data.
Conclusion: it will be as out of the box but S-Off.
Sent from my HTC Desire HD using XDA
kualmente said:
The link I gave is for stock unbranded WWE (world wide english) RUU. No idea where you can find Vodafone AU, sorry.
Running the RUU.exe will unroot your device but s-off remains. Also it deletes all apps and data.
Conclusion: it will be as out of the box but S-Off.
Sent from my HTC Desire HD using XDA
Click to expand...
Click to collapse
Cheers mate. I found the stock au Rom...not an ruu unfortunately, returning back to out of box is a bit of a tedious ordeal
kualmente said:
You don't have to flash stock rom from recovery like custom roms or nandroid backups.
Run stock RUU.exe or flash the rom from bootloader if in PG58IMG format if you want to go back to complete stock rom.
You can download RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_R_Radio_12.65.60.29_26.14.04.28_M_release_233505_signed form HERE
Click to expand...
Click to collapse
hey,
i have got the same problem but with S-on,i really cant do anything with phone as its not booting up,
i cant only access hboot and recovery but cant flash any radio or rom.
will this rom help me?
if u need more information bout my dhd u can check:
http://forum.xda-developers.com/showthread.php?t=1604510
please help me
sinahidden said:
hey,
i have got the same problem but with S-on,i really cant do anything with phone as its not booting up,
i cant only access hboot and recovery but cant flash any radio or rom.
will this rom help me?
if u need more information bout my dhd u can check:
http://forum.xda-developers.com/showthread.php?t=1604510
please help me
Click to expand...
Click to collapse
--I noticed your using advanced ace hack kit. Question- are you renaming the Rom file to "update.zip," and then selecting "install update from zip"???
If so, there s your problem.
Just select "install from zip" instead. Shouldn't matter if the file has been renamed.
Hopefully this is a quick fix for you. Let us know, because if you can get to bootloader and recovery, there is a fix.
Don't be shy to use the thanks button.
---------- Post added at 10:06 AM ---------- Previous post was at 09:49 AM ----------
kualmente said:
The link I gave is for stock unbranded WWE (world wide english) RUU. No idea where you can find Vodafone AU, sorry.
Running the RUU.exe will unroot your device but s-off remains. Also it deletes all apps and data.
Conclusion: it will be as out of the box but S-Off.
Sent from my HTC Desire HD using XDA
Click to expand...
Click to collapse
--Cheers mate. I found a Vodafone branded RoM. Maybe you can help me before I post a thread in Q&A's, because I'm getting nowhere with it. I'd appreciate any suggestions. Heres whats happening:
Just read this guys post and its exactly to a tee, what is happening with me:
http://forum.xda-developers.com/showthread.php?t=1575300
haha, you can probably tell im getting a little desperate.
Please answer these questions in order to summarize the situation:
1) are you S-ON or S-OFF?
2) What your bootloader says and what version is is (there is a **locked** on top?)
3) have you tried the hack kit or not?
4) do you have stock recovery or CWM/4EXT?
5) is your phone branded Vodafone or is just your carrier which is Vodafone?
6) what was your original RUU and what RUU did you find. RUU.exe should be run from a computer not flashed by recovery.
kualmente said:
Please answer these questions in order to summarize the situation:
1) are you S-ON or S-OFF?
2) What your bootloader says and what version is is (there is a **locked** on top?)
3) have you tried the hack kit or not?
4) do you have stock recovery or CWM/4EXT?
5) is your phone branded Vodafone or is just your carrier which is Vodafone?
6) what was your original RUU and what RUU did you find. RUU.exe should be run from a computer not flashed by recovery.
Click to expand...
Click to collapse
Hi, are u asking me? If so here u go.
1- S-OFF. Don't think I'm eng s-off.
2- boot loader reads as follows:
Ace PVT Ship S-off RL
Hboot 0.85.0024
Microphone 0438
Radio 26.10.04.03_m
eMMC-boot
3- advance ace hack kit is how I rooted my device...?
4- clockwork mod recovery touch 5.8
5- Vodafone branded phone originally, with all the crap
6-original ruu unknown? But the rom I can't install is titled:
Ace_Vodafone_AU_1.32.178.5_Radio_12.28b.60.140eU_26.03.02.26_M_BACKUP
Its a zip file which I've tried to install from recovery as a zip(error message 'install aborted')and also restore after extracting to cwm/backup (error message md5 mismatch)
I'm completely lost.
Install 4ext recovery, if I'm not mistaken it has an option to ignore md5 mismatches.
Edit - just checked and it does, its in the recovery settings
Sent from my Inspire 4G using XDA
marsdta said:
Install 4ext recovery, if I'm not mistaken it has an option to ignore md5 mismatches.
Edit - just checked and it does, its in the recovery settings
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
Alright, well I installed 4ext, disabled md5 check. All that happened when it restored (finished in only 3secs)was rebooted with a freshly wiped copy of the rom I've been using-cookies & cream ics.
It seems like the file is empty, though I've explored its content and all seems intact. Its about the 5th download of the rom too, so unlikely a bad dl. Someone installed it successfully by deleting nandroid. md5, then using the md5 sum recreate it as md5sum*img > nandroid.md5... Don't know how or what this means
I believe they are talking about this. In the app go to recovery >manage backups. Choose the file then click correct md5 sum
Sent from my Inspire 4G using XDA
marsdta said:
I believe they are talking about this. In the app go to recovery >manage backups. Choose the file then click correct md5 sum
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
-Alright well I got the md5 sorted, and installed the rom. Now I have a blackscreen... It appears nothing has changed. the green htc letters slowly fade to white lines then to black, thats about it. Still got 4ext so I can restore, but this is a pain in the rectum.
I'm restoring it again and it reads its restoring: boot system data cache. In the process, .android_secure not found...Should be alright?
That should be fine. Not sure why its not working and others got it to work
Sent from my Inspire 4G using XDA
marsdta said:
That should be fine. Not sure why its not working and others got it to work
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
--I dont know. Will try to download and install again, in the off chance I have "bad install."
Wondering if I could insall the WWE Ruu.exe and then temp root and somehow flash all the vodafone australia crap...I'm just swinging in the dark here.
I thought about that. You won't be able to fully be on your stock firmware but it might be close enough for warranty purposes.
So here is my thinking. Flash the 1.32.405 ruu. Next flash your stock radio that came with your carrier via a pd98. Then root with visionary and use jkoljos easy radio tool to flash back your cid and get back son. Finally unroot with visionary and remove any traces of root like super user. I think that's as close as well be able to get if the nandroid doesn't work
Sent from my Inspire 4G using XDA
marsdta said:
I thought about that. You won't be able to fully be on your stock firmware but it might be close enough for warranty purposes.
So here is my thinking. Flash the 1.32.405 ruu. Next flash your stock radio that came with your carrier via a pd98. Then root with visionary and use jkoljos easy radio tool to flash back your cid and get back son. Finally unroot with visionary and remove any traces of root like super user. I think that's as close as well be able to get if the nandroid doesn't work
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
Thanks for ur help mate ... haven't had a chance to try re install of this yet. If it isn't one thing its another, I did Eng s off and now my battery is dieing by like, 1-2% every minute, don't think its associated with Eng s off, but the battery coincidentally nearing its end. Then my charger died.
Alright so ill give it a go and post the outcome. Cheers dude. I think I have the vodafone splash screen downloaded so if so that's a plus
Hi Guys, I've been using Custom Roms a long time so It came... Jelly Beans finally.
I tried to go back to stock...basically I installed a NANDROID compatible with my system...everything went fine till the last update JB...
I downloaded it...OK ,
After INSTALL NOW...It reboots the phone to install...After that, shows a message and go back to BOOTLOADER...I cannot see well the message... What can I do?? It's driving me crazy
Logo HTC and this message...after that...goes back to bootloader...What Happened??
QUOTE
"This build if for development purposes only
do not distribute ourside of HTC
without HTC a writter permission
Failure to comply may
lead to legal action"
blankfile99 said:
Hi Guys, I've been using Custom Roms a long time so It came... Jelly Beans finally.
I tried to go back to stock...basically I installed a NANDROID compatible with my system...everything went fine till the last update JB...
I downloaded it...OK ,
After INSTALL NOW...It reboots the phone to install...After that, shows a message and go back to BOOTLOADER...I cannot see well the message... What can I do?? It's driving me crazy
Logo HTC and this message...after that...goes back to bootloader...What Happened??
QUOTE
"This build if for development purposes only
do not distribute ourside of HTC
without HTC a writter permission
Failure to comply may
lead to legal action"
Click to expand...
Click to collapse
you installed an OTA?
I'm using a Stock from a recovery Nandroid, not mine but the same CID 044... I guess I shold go back to RUU...but I've tried without any success
I can't even use my RUU file...donno why... I have this file: (RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed) and It works, not now but It used it once...do you have a suggestion so I can use it again??
blankfile99 said:
I can't even use my RUU file...donno why... I have this file: (RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed) and It works, not now but It used it once...do you have a suggestion so I can use it again??
Click to expand...
Click to collapse
you are on JB now and you can't run ICS RUUs, you can't downgrade...
matt95 said:
you are on JB now and you can't run ICS RUUs, you can't downgrade...
Click to expand...
Click to collapse
I'm not...I'm on 2.17 yet...JB update does not install...that's the main problem
and I have noticed that NO MATTER I CHANGE...IT WONT CHANGE THIS VERSION... OMG
tks man!
You need to relock your bootloader (if you haven't already) and run THIS RUU.
The problem is that the version of software you're running (2.17) is newer than the RUU you're trying to install (1.29). you can't revert to an older RUU. you can only flash the same version or newer.
Once you've flashed the RUU, you'll be able to download and install the JB OTA.
Sentinel196 said:
You need to relock your bootloader (if you haven't already) and run THIS RUU.
The problem is that the version of software you're running (2.17) is newer than the RUU you're trying to install (1.29). you can't revert to an older RUU. you can only flash the same version or newer.
Once you've flashed the RUU, you'll be able to download and install the JB OTA.
Click to expand...
Click to collapse
Thank you very much man, You renew my faith!!
It will work like a FORMAT SYSTEM with the same Rom?
I'll keep in touch!!
Also, this may sound silly but did you reflash stock RECOVERY?
blankfile99 said:
Thank you very much man, You renew my faith!!
It will work like a FORMAT SYSTEM with the same Rom?
I'll keep in touch!!
Click to expand...
Click to collapse
No worries, let us know how you go, and don't forget the Thanks button.
ArmedandDangerous said:
Also, this may sound silly but did you reflash stock RECOVERY?
Click to expand...
Click to collapse
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Well I am currently running Team Venom's Viper but I have HBOOT 1.31. My device's CID is HTC_J15.
I have checked the list of RUUs but unfortunately all of them are older than the version I need, which has to be 3+.
Does anybody know if there's an RUU available for my device? It is an ubranded WWE version, 401 if I remember correctly.
ArmedandDangerous said:
Also, this may sound silly but did you reflash stock RECOVERY?
Click to expand...
Click to collapse
I'm using the same as the NANDROID, taken from it...right?
Sentinel196 said:
No worries, let us know how you go, and don't forget the Thanks button.
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Click to expand...
Click to collapse
That's all I need... I'll give my feedback later.
Sentinel196 said:
No worries, let us know how you go, and don't forget the Thanks button.
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Click to expand...
Click to collapse
In my experience the 2.17.707.xx RUU Asia WWE does not work properly. It does its thing installing everything, relocks the bootloader but somehow it does not reflash the recovery. After 4 hours trying everything under the sun, I gave up and looked for a nandroid of 2.17 for CID_044 and restored from that, reflashed stock recovery and went to town with the OTA.
That's very strange, no such problem when I did the same thing. You'd think it would throw an error or something if a component of the image failed to flash.
Glad you managed to figure it out!
Did you run it when your bootloader was unlocked? Maybe that's the problem? I ran it with the bootloader relocked and didn't ahve any problems. I was under the impression you couldn't run an RUU with an unlocked bootloader, but haven't tried it myself.
Refer custom to stock thread posted earlier. Go through step by step procedure. It will help u to be on stock Rom. After that flash any Rom suitable to your CID only
http://forum.xda-developers.com/showthread.php?t=1859714
Hit Thanks if u like.
Sent from my HTC One X using xda app-developers app
Got It guys!!
What I did... NOTHING else...
Only Reboot the phone...wait to initialize completely, then reboot again, when came a little update about 1.25mb...installed and reboot...after that...JB update installed correctly.
If someone else needs...Someone like me who relocked the phone waiting for JB and Has problems
1. Unlock Phone
2. fastboot flash recovery recovery.img (from nandroid 2.17)
3. fastboot flash boot boot.img (from nandroid 2.17)
4. fastboot erase cache
5. restart bootloader (I like to do this way)
6. Install RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed on windows
7. Wait to boot completely, then restart phone.
8. Update Software ...a little update came before JB. (about 1.25mb)
9 Reboot phone.
10. Update Software... finally to JB.
Thanks guys!
Sentinel196 said:
That's very strange, no such problem when I did the same thing. You'd think it would throw an error or something if a component of the image failed to flash.
Glad you managed to figure it out!
Did you run it when your bootloader was unlocked? Maybe that's the problem? I ran it with the bootloader relocked and didn't ahve any problems. I was under the impression you couldn't run an RUU with an unlocked bootloader, but haven't tried it myself.
Click to expand...
Click to collapse
The RUU ran with no problem, and it relocked my bootloader, but it still did not receive any OTAs. So I had no choice but to do a nandroid restore instead (recommended anyway )
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
Okay, so my phone is stuck in a boot loop after flashing a new ROM. I tried wiping the cache before and after and doing factory reset. I have tried different ROMs and the same thing always happens, it boots up and opmimizes apps then tells me "Unfortunately gapps or google play services or system ui or phone or something failed" and then restarts. Could someone please help me out.
korbs710 said:
Okay, so my phone is stuck in a boot loop after flashing a new ROM. I tried wiping the cache before and after and doing factory reset. I have tried different ROMs and the same thing always happens, it boots up and opmimizes apps then tells me "Unfortunately gapps or google play services or system ui or phone or something failed" and then restarts. Could someone please help me out.
Click to expand...
Click to collapse
What ROM, what recovery version, what firmware version, what model version, are you S-ON or S-OFF, did you do a clean flash or dirty flash? and the wipe is preferably before the ROM installation in my experience.
I started with CM 12.1 but it had a reboot loop issue when the screen would be put to sleep so I changed to Venom 3.50. I am using TWRP 2.8.7.0. Not sure what firmware, can I check that from recovery? It is a North American version on Rogers, can't find model version in bootloader or recovery. S-ON, what'e the difference between dirty and clean? I do a factory rest on recovery and then click install and flash the ROM and then reboot.
korbs710 said:
I started with CM 12.1 but it had a reboot loop issue when the screen would be put to sleep so I changed to Venom 3.50. I am using TWRP 2.8.7.0. Not sure what firmware, can I check that from recovery? It is a North American version on Rogers, can't find model version in bootloader or recovery. S-ON, what'e the difference between dirty and clean? I do a factory rest on recovery and then click install and flash the ROM and then reboot.
Click to expand...
Click to collapse
For clean in recovery click advanced wipe, check system, data , and both caches. Dirty install for example would be just flashing the ROM again if there was an update where you don't delete any of your data. Also the screen off reboot comes from not having the correct firmware for the ROM. Boot into download mode to see what firmware you are on. Then make sure you flash a ROM that is based off the firmware you are on.
BUBBA DUB'S said:
For clean in recovery click advanced wipe, check system, data , and both caches. Dirty install for example would be just flashing the ROM again if there was an update where you don't delete any of your data. Also the screen off reboot comes from not having the correct firmware for the ROM. Boot into download mode to see what firmware you are on. Then make sure you flash a ROM that is based off the firmware you are on.
Click to expand...
Click to collapse
I have been doing clean installs. I am on firmware 2.11 and I don't think any ROMs exist yet. The phone won't stay on long enough to use sunshine. Should I wait for a new ROM to come on based on my firmware? The phone just keeps rebooting and sometimes it won't even go to a homescreen. Is there anything else I should try? I am out of ideas at this point.
korbs710 said:
I have been doing clean installs. I am on firmware 2.11 and I don't think any ROMs exist yet. The phone won't stay on long enough to use sunshine. Should I wait for a new ROM to come on based on my firmware? The phone just keeps rebooting and sometimes it won't even go to a homescreen. Is there anything else I should try? I am out of ideas at this point.
Click to expand...
Click to collapse
Do you have the OEM lock disabled?
DeadPotato said:
Do you have the OEM lock disabled?
Click to expand...
Click to collapse
Says Unlocked on the Bootloader screen. Is that what you mean?
korbs710 said:
Says Unlocked on the Bootloader screen. Is that what you mean?
Click to expand...
Click to collapse
Go into settings, developer options , and then look for OEM lock setting.
BUBBA DUB'S said:
Go into settings, developer options , and then look for OEM lock setting.
Click to expand...
Click to collapse
The phone won't even get through the setup so it would be impossible to get to developer options without it rebooting before. I went through all the steps to root it and it worked good for a day then the reboots started and I reflashed and it is basically bricked now.
korbs710 said:
The phone won't even get through the setup so it would be impossible to get to developer options without it rebooting before. I went through all the steps to root it and it worked good for a day then the reboots started and I reflashed and it is basically bricked now.
Click to expand...
Click to collapse
If it boots up into anything it is not bricked. Can you hold power plus volume up and get into download mode? You could try fastboot flashing your RUU for your device to start over from scratch.
BUBBA DUB'S said:
If it boots up into anything it is not bricked. Can you hold power plus volume up and get into download mode? You could try fastboot flashing your RUU for your device to start over from scratch.
Click to expand...
Click to collapse
It will boot into TWRP 2.8.7.0 recovery mode and I downloaded the RUU for Rogers in Canada but it is based on a different firmware build. But do I have to lock my bootloader again with fastboot oem lock? I haven't tried that yet. Will the firmware matter in this case? I will try the relock and load RUU if you think firmware doesn't matter, I am on 2.11 and the RUU is based on 1.32.
korbs710 said:
It will boot into TWRP 2.8.7.0 recovery mode and I downloaded the RUU for Rogers in Canada but it is based on a different firmware build. But do I have to lock my bootloader again with fastboot oem lock? I haven't tried that yet. Will the firmware matter in this case? I will try the relock and load RUU if you think firmware doesn't matter, I am on 2.11 and the RUU is based on 1.32.
Click to expand...
Click to collapse
I am not sure @DeadPotato do you know if it's ok to go backwards with an RUU regarding firmware?
korbs710 said:
The phone won't even get through the setup so it would be impossible to get to developer options without it rebooting before. I went through all the steps to root it and it worked good for a day then the reboots started and I reflashed and it is basically bricked now.
Click to expand...
Click to collapse
DO NOT RELOCK OR YOU MAY BRICK YOUR PHONE.
You probably can't run that ruu because you're not s-off and can't downgrade unless the aboot has not changed.
To confirm, you went into download mode and it says OS-2.11.x? What is your CID?
My suggestion would be to do another complete wipe (system, data, cache, dalvik) and then flash a different rom, preferably one of the stockish ones like ARHD or Maximus. If you can boot up most of the way, the problem is likely just getting your OS straightened out.
iElvis said:
DO NOT RELOCK OR YOU MAY BRICK YOUR PHONE.
You probably can't run that ruu because you're not s-off and can't downgrade unless the aboot has not changed.
To confirm, you went into download mode and it says OS-2.11.x? What is your CID?
My suggestion would be to do another complete wipe (system, data, cache, dalvik) and then flash a different rom, preferably one of the stockish ones like ARHD or Maximus. If you can boot up most of the way, the problem is likely just getting your OS straightened out.
Click to expand...
Click to collapse
Correct, I am not S-OFF as of now. Not sure if it is possible without being able to boot into an OS.
Yes I am OS-2.11.631.2. CID: ROGER001.
I have tried many ROMs, including ARHD 12.0 but the problem is all the ROMs are based on 1.32 and not 2.11. When I flash ARHD it will get to Optimizing apps once then it will reboot and be stuck on splash screen forever.
korbs710 said:
Correct, I am not S-OFF as of now. Not sure if it is possible without being able to boot into an OS.
Yes I am OS-2.11.631.2. CID: ROGER001.
I have tried many ROMs, including ARHD 12.0 but the problem is all the ROMs are based on 1.32 and not 2.11. When I flash ARHD it will get to Optimizing apps once then it will reboot and be stuck on splash screen forever.
Click to expand...
Click to collapse
There are many 2.x roms. If you're flashing 1.x roms, there's your problem. Download one of the latest 2.x-based roms.
iElvis said:
There are many 2.x roms. If you're flashing 1.x roms, there's your problem. Download one of the latest 2.x-based roms.
Click to expand...
Click to collapse
I have not been able to find one... ARHD 12.0 (the newst release is 1.x based I think). I could be wrong but even so, I have flashed that ROM and just have a boot loop error. How can I tell what the ROM is based on? I have tried many google searches and looked through many forums... At this point I just want the stupid phone to turn on. Sorry to be bothering you and I appreciate the help but I am just extremely frustrated at this point and I do realize it is all my fault.
korbs710 said:
I have not been able to find one... ARHD 12.0 (the newst release is 1.x based I think). I could be wrong but even so, I have flashed that ROM and just have a boot loop error. How can I tell what the ROM is based on? I have tried many google searches and looked through many forums... At this point I just want the stupid phone to turn on. Sorry to be bothering you and I appreciate the help but I am just extremely frustrated at this point and I do realize it is all my fault.
Click to expand...
Click to collapse
12.0 is based on 2.10.401. It's possible there is a conflict with the 2.11 Rogers firmware, though I have not seen anyone else post about this.
On the RUU, did you ever tick the "Allow OEM Unlocking" setting in Developer Options since you upgraded to 2.x? If you did not, you cannot relock in your current state because you won't be able to boot up (because of your custom recovery), and won't be able to unlock again, even through HTCdev, because this setting will block it. You would be stuck in bootloader until you could run a RUU, or flash a stock Rogers recovery.
The RUU might run if the aboot version has not changed since 1.32, but it's a risk. If it did not, you'd be stuck until there is a 2.11 Rogers RUU, if ever.
@iElvis , good looking out, if someone is s-on do they have to re lock the boot in order to flash RUU? I thought I saw somewhere you could could still flash via download being s-on.
@korbs710 hopefully you will get it all squared away. If you do I'd also recommend getting s-off via sunshine. It's totally worth the 25 bucks.
iElvis said:
12.0 is based on 2.10.401. It's possible there is a conflict with the 2.11 Rogers firmware, though I have not seen anyone else post about this.
On the RUU, did you ever tick the "Allow OEM Unlocking" setting in Developer Options since you upgraded to 2.x? If you did not, you cannot relock in your current state because you won't be able to boot up (because of your custom recovery), and won't be able to unlock again, even through HTCdev, because this setting will block it. You would be stuck in bootloader until you could run a RUU, or flash a stock Rogers recovery.
The RUU might run if the aboot version has not changed since 1.32, but it's a risk. If it did not, you'd be stuck until there is a 2.11 Rogers RUU, if ever.
Click to expand...
Click to collapse
No, I did not select Allow OEM Unlocking. So am I screwed then? I am trying to flash Maximus 6.0 but if it doesn't work I don't want to fully lock the device by trying the RUU.
BUBBA DUB'S said:
@iElvis , good looking out, if someone is s-on do they have to re lock the boot in order to flash RUU? I thought I saw somewhere you could could still flash via download being s-on.
@korbs710 hopefully you will get it all squared away. If you do I'd also recommend getting s-off via sunshine. It's totally worth the 25 bucks.
Click to expand...
Click to collapse
Ya I was going to gladly pay the 25 bucks if it meant being able to use my phone and supporting the devs is good.