Related
Hello there!
I know there are many threads and questions about unrooting, but I haven't found anything useful to me (or I just don't understand them) and also I'm new to the whole root/unroot thing.
Here is the story. I rooted my device via TWRP Recovery. Then I tried to get S-OFF using Firewater. When I wasted like a few days trying to get this done I discovered that my device is "Patched by HTC" so I cannot use Firewater anymore to get this S-OFF.
The whole thing was to convert my M8 into a GPE version. Now I'm trying to revert my phone back to stock ver. because I have no need in root.
So is it possible to unroot my phone?
My CID is HTC_622
Software number is 1.60.708.2
Thanks in advance!
Funky_Noises said:
Hello there!
I know there are many threads and questions about unrooting, but I haven't found anything useful to me (or I just don't understand them) and also I'm new to the whole root/unroot thing.
Here is the story. I rooted my device via TWRP Recovery. Then I tried to get S-OFF using Firewater. When I wasted like a few days trying to get this done I discovered that my device is "Patched by HTC" so I cannot use Firewater anymore to get this S-OFF.
The whole thing was to convert my M8 into a GPE version. Now I'm trying to revert my phone back to stock ver. because I have no need in root.
So is it possible to unroot my phone?
My CID is HTC_622
Software number is 1.60.708.2
Thanks in advance!
Click to expand...
Click to collapse
just flash stock then flash stock recovery and your done
but bootloader will still say tampered
jaythenut said:
just flash stock then flash stock recovery and your done
but bootloader will still say tampered
Click to expand...
Click to collapse
Thanks for the reply.
I wish there was more detail in your post: like what software should I use to flash stock?
Should I download some rom for that?
As I said, I'm really new to the whole thing.
1. Flash your backup in TWRP
2. Once restored and confirmed working, flash the stock recovery image for your software version in fastboot the same way you flashed TWRP (fastboot flash recovery <nameofrecovery>.img
3419
EddyOS said:
1. Flash your backup in TWRP
2. Once restored and confirmed working, flash the stock recovery image for your software version in fastboot the same way you flashed TWRP (fastboot flash recovery <nameofrecovery>.img
Click to expand...
Click to collapse
I see! Thanks a lot!
Will try that.
Damn, I wish I could do S-OFF and convert my phone into GPE ;|
stock recovery
EddyOS said:
1. Flash your backup in TWRP
2. Once restored and confirmed working, flash the stock recovery image for your software version in fastboot the same way you flashed TWRP (fastboot flash recovery <nameofrecovery>.img
Click to expand...
Click to collapse
Hey I've been googling for hours for this too.I know this is an old post.
I am one of the unfortunate people do get a 1.60 up
Update on CID HTC__622
I have surfed the page with the list of nandroids, however there is no stock recovery that begins with 1.60. From other research it states that the first two numbers are the most important whilst flashing recoveries.
Any information would be really helpful
Thanks
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
marawan31 said:
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
Click to expand...
Click to collapse
Go back to stock, and take the OTAs. Then re-root and enjoy your new firmware.
Visit this thread:
http://forum.xda-developers.com/showthread.php?t=2701376
or this thread:
http://forum.xda-developers.com/showthread.php?t=2710735
I cant do that because i am not s-off
marawan31 said:
I cant do that because i am not s-off
Click to expand...
Click to collapse
Incorrect. This is the method that you use if you are not S-Off.
If you were S-Off, you would just update firmware manually, with no need to go back to stock.
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
marawan31 said:
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
Click to expand...
Click to collapse
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
xunholyx said:
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
Click to expand...
Click to collapse
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
marawan31 said:
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
Click to expand...
Click to collapse
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
ckpv5 said:
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
Click to expand...
Click to collapse
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
marawan31 said:
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
Click to expand...
Click to collapse
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. relock bootloader - fastboot oem lock
4. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
5. check software update
6. accept, download, install
7. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
ckpv5 said:
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip hbootMOD3.zip
fastboot flash zip hbootMOD3.zip <---- again for the 2nd time
fastboot reboot
4. check software update
5. accept, download, install
6. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
Click to expand...
Click to collapse
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
marawan31 said:
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
Click to expand...
Click to collapse
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
ckpv5 said:
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
Click to expand...
Click to collapse
oh ok thanks man!!
ill post back with the result
marawan31 said:
oh ok thanks man!!
ill post back with the result
Click to expand...
Click to collapse
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
ckpv5 said:
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
Click to expand...
Click to collapse
yea i was going to do it and also for the sake of completeness flashing the stock recovery(3.34.661.4) after the restore, just in case someone else has the same problem
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
ckpv5 said:
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
Click to expand...
Click to collapse
oh didnt know that, i guess i wont then
I just wanted to thank you guys for helping me out!
I did everything and now i am on android 5.0.1 (although i ran into a small problem: process com.android.phone is not responding, factory reset from recovery fixed it)
Hope this thread helps someone else with similar problems
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it, I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it. There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
Please see my comments in red font below:
350Rocket said:
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Photo link is coming up with 404 error for me. Better to do fastboot getvar all, then post the results (cut and paste from command prompt), so we can see all the info on the phone (delete IMEI and serial number before posting).
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it,
If you can be more specific about which ROMs you tried (plus info about your device from getvar as noted above), then we might be able to advise why they did not flash. Did you get error messages, and if so, what exactly were they?
I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it.
What exactly did you do (step by step, with any relevant file names, etc. - more detail is better).
I presume you intentionally relocked the bootloader in attempt to run some RUU. But would like clarification on this (and where that happened in the sequence of events)
There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
Far as I know, Canadian versions don't have RUU.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
One option (maybe the best one) is to restore a stock TWRP back from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You will need to unlock the bootloader to do this. You can either reuse the unlock bin code you used originally (if you still have it). Otherwise, you should be able to request a new bin code from HTCDev.com. Far as I know, that still works for this phone.
Click to expand...
Click to collapse
Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx
You have to be 100% stock to get OTAs successfully. Since you're s-off, just running an earlier RUU exe should do it, but you may need to relock.
Under no circumstances should you go back to s-on.
DroidShift79 said:
Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx
Click to expand...
Click to collapse
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
MAX 404 said:
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Click to expand...
Click to collapse
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.
DroidShift79 said:
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.
Click to expand...
Click to collapse
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck
MAX 404 said:
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck
Click to expand...
Click to collapse
Thought of this,
just not sure if I need to relock bootloader to get official otas
DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk
THX kingvortex. I just do it and report back.
Thanks all of you.
DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
kingvortex said:
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
Well, what I did so far, was to use the 1.32.401.17 ruu.exe
Flash went fine, but no OTA did show up.
So I wanted to flash the 1.32.401.8 ruu zip.
But putting it on sdcard or using fastboot flash zip failed.
Wonder why!?
Later on I'll try Max 404 find.
MAX 404 said:
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
Click to expand...
Click to collapse
My HTC Desire 816 Dual SIM,
1. does not boot normally,
2. only boots into FASTBOOT page,
3. in FASTBOOT page I can select and enter Hboot page,
4. in Hboot menu, when I select RECOVERY, or FACTORY RESET, it returns only to FASTBOOT page.
5. as the attachment shows, there is nothing written in front of "OS-"; it is blank.
Questions:
1. In these conditions, is it possible to flash the ZIP ROM from sdcard via Hboot?
2. Is it not necessary to flash stock recovery, wipe some partitions, etc first, and only then proceed to flashing ZIP ROM from sdcard via Hboot?
Hi
I have the same problem as you only my. HTC is the sIngle sim A5-UL Version.
So far I have not had any replies regarding the problem.
Hopefully we will get a resolution
sometime.
Sent from my LG-H815 using Tapatalk
[/COLOR]
Dr.Ghobar said:
My HTC Desire 816 Dual SIM,
1. does not boot normally,
2. boots directly into Fastboot page,
3. in fastboot page I can select and enter Hboot page,
4. in Hboot menu, when I select Recovery, or Factory Reset, it returns only to Fastboot page.
5. as the attachment shows, the OS- is blank
Questions:
1. In these conditions, is it possible to flash the ZIP ROM from sdcard via Hboot?
2. Is it not necessary to flash stock recovery, wipe some partitions, etc first, and only then proceed to flashing ZIP ROM from sdcard via Hboot?
Click to expand...
Click to collapse
It should be but you will need to have the stock recovery reinstalled by first unlocking your bootloader then flashing back your stock recovery then relock bootloader and then flash the RUU or stock zip file thru either ADB /fastboot on your computer or via SD card and renaming the image OP9CIMG and hboot should pick it up and flash it automatically. Did you accidentally wipe your system or try to flash something that corrupted it? In other words what happened before all this? We're you rooted with a custom recovery or still on stock?
---------- Post added at 11:09 PM ---------- Previous post was at 11:01 PM ----------
Stransky said:
Hi
I have the same problem as you only my. HTC is the sIngle sim A5-UL Version.
So far I have not had any replies regarding the problem.
Hopefully we will get a resolution
sometime.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Didn't nukaru's a5_ul forum link I gave you earlier this month help? Sorry your still having issues.
Stransky said:
Hi
I have the same problem as you only my. HTC is the sIngle sim A5-UL Version.
So far I have not had any replies regarding the problem.
Hopefully we will get a resolution
sometime.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Dr.Ghobar said:
My HTC Desire 816 Dual SIM,
1. does not boot normally,
2. boots directly into Fastboot page,
3. in fastboot page I can select and enter Hboot page,
4. in Hboot menu, when I select Recovery, or Factory Reset, it returns only to Fastboot page.
5. as the attachment shows, the OS- is blank
Questions:
1. In these conditions, is it possible to flash the ZIP ROM from sdcard via Hboot?
2. Is it not necessary to flash stock recovery, wipe some partitions, etc first, and only then proceed to flashing ZIP ROM from sdcard via Hboot?
Click to expand...
Click to collapse
Dwnload ur respective RUU zip file,rename the file to. "0P9CIMG.zip". put in ext.sd card ,put the phone in hboot mode..it will autimatically detect the file and will ask for permission
Stransky said:
Hi
So far I have not had any replies regarding the problem.
Click to expand...
Click to collapse
Did you find ROM zip and did you try to flash it via sdcard and Hboot?
thoctor said:
It should be but you will need to have the stock recovery reinstalled by first unlocking your bootloader then flashing back your stock recovery then relock bootloader and then flash the RUU or stock zip file thru either ADB /fastboot on your computer or via SD card and renaming the image OP9CIMG and hboot should pick it up and flash it automatically. Did you accidentally wipe your system or try to flash something that corrupted it? In other words what happened before all this? We're you rooted with a custom recovery or still on stock?
Click to expand...
Click to collapse
1. I tried to unlock bootloader but the last stage that asks Yes or No, did not appear on my phone and therefore no unlocking happened as the attachment shows. Can you help me with this problem?
2. I wiped nothing and flashed nothing. The phone was working normally and the battery finished. I plugged the charger but when I tried to turn on the phone it only booted to fastboot mode as I explained in the original post.
3. I was on the original ROM that came with phone. I never did any manipulation.
ajeshmanu said:
Dwnload ur respective RUU zip file,rename the file to. "0P9CIMG.zip". put in ext.sd card ,put the phone in hboot mode..it will autimatically detect the file and will ask for permission
Click to expand...
Click to collapse
Because my phone has behaved abnormally (OS- is blank, as attachment shows; unlocking bootloader did not show Yes or No page; and other abnormalities), I am not sure whether to download a file over 1.20GB, or not? I am afraid about failure! Is not my phone in a situation that needs some preparations before doing what you said?
Hi
Thanks for reply. I was attempting to go back to stock and had installed stock recovery and then relocked the bootloader and when i tried to install the RUU it said it was the wrong one.
I then tried the Hboot way but received the same error. I need to find several RUUs to be able to find the correct version for my 816 which i believe is Asian but not sure where.
Sent from my LG-H815 using Tapatalk
Stransky said:
Hi
Thanks for reply. I was attempting to go back to stock and had installed stock recovery and then relocked the bootloader and when i tried to install the RUU it said it was the wrong one.
I then tried the Hboot way but received the same error. I need to find several RUUs to be able to find the correct version for my 816 which i believe is Asian but not sure where.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Oh, ok I get it now. Think the forum I linked you to was for the European a5_ul. Here's a link to some a5_ul roms kitkat and lollipop. I see one of the lollipop versions is Asia. Try to match your CID and version ID or at least your radio ID's before flashing it. "fastboot getvar all" will give you most of that info but it looks like that might be your firmware. Also make sure you relocked your bootloader before flashing. Good luck
http://forum.gsmhosting.com/vbb/f485/htc-desire-816-official-stock-roms-always-updated-1948682/
Dr.Ghobar said:
Did you find ROM zip and did you try to flash it via sdcard and Hboot?
1. I tried to unlock bootloader but the last stage that asks Yes or No, did not appear on my phone and therefore no unlocking happened as the attachment shows. Can you help me with this problem?
2. I wiped nothing and flashed nothing. The phone was working normally and the battery finished. I plugged the charger but when I tried to turn on the phone it only booted to fastboot mode as I explained in the original post.
3. I was on the original ROM that came with phone. I never did any manipulation.
Because my phone has behaved abnormally (OS- is blank, as attachment shows; unlocking bootloader did not show Yes or No page; and other abnormalities), I am not sure whether to download a file over 1.20GB, or not? I am afraid about failure! Is not my phone in a situation that needs some preparations before doing what you said?
Click to expand...
Click to collapse
Sorry, I wasn't trying to accuse you of doing something to your phone but those pictures don't show me any of that. It just shows that you seem to no longer have an OS with your lack of a CID and something happened to cause this. It's not about finger pointing but getting the issue resolved for you I know. As for helping you unlock your bootloader the method is pretty straight forward and if it didn't work for whatever reason the only real advice I can give is to just try it again. That's how I unlocked mine so maybe it was just a glitch and another attempt will work. For now I'm more concerned that you didn't wipe anything yet your recovery and firmware seen too be missing or at least inaccessible from your bootloader. The factory reset was going to be my first suggestion but since your already done that have you tried to enter your recovery thru ADB/fastboot? (fastboot reboot recovery.) The other thing is what region are you in( India, Asia, European) and does " fastboot getvar all" work from using ADB? Also if your OS is wiped then any RUU flash will reformat your partitions for you and restore your rom. Also were you on kitkat or lollipop stock rom?
thoctor said:
Oh, ok I get it now. Think the forum I linked you to was for the European a5_ul. Here's a link to some a5_ul roms kitkat and lollipop. I see one of the lollipop versions is Asia. Try to match your CID and version ID or at least your radio ID's before flashing it. "fastboot getvar all" will give you most of that info but it looks like that might be your firmware. Also make sure you relocked your bootloader before flashing. Good luck
http://forum.gsmhosting.com/vbb/f485/htc-desire-816-official-stock-roms-always-updated-1948682/
Click to expand...
Click to collapse
Hi
Again thanks for the reply.
My 816 A5UL is Asia-HK-CHT
CID-622
I cannot find a RUU that matches.
I believe the Rom could be OPc21000
Which i cannot find anywhere.
Sent from my LG-H815 using Tapatalk
Stransky said:
Hi
Again thanks for the reply.
My 816 A5UL is Asia-HK-CHT
CID-622
I cannot find a RUU that matches.
I believe the Rom could be OPc21000
Which i cannot find anywhere.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Yeah I've never heard of that version before. I only found one link here below that even mentions that CID but no solution. If you haven't flashed the one I linked I'd try it anyway because as long as your S on the signed rom won't flash if it's the wrong one but if your sure it's wrong then save the data hit to your ISP cap. Sorry I wasn't of more help to you.
http://forum.xda-developers.com/des...pop-a5dug-firmware-to-fix-wifi-t3126905/page5
1. I did not mean that you were trying to... 2. Answers
thoctor said:
Sorry, I wasn't trying to accuse you of doing something to your phone but those pictures don't show me any of that. It just shows that you seem to no longer have an OS with your lack of a CID and something happened to cause this. It's not about finger pointing but getting the issue resolved for you I know. As for helping you unlock your bootloader the method is pretty straight forward and if it didn't work for whatever reason the only real advice I can give is to just try it again. That's how I unlocked mine so maybe it was just a glitch and another attempt will work. For now I'm more concerned that you didn't wipe anything yet your recovery and firmware seen too be missing or at least inaccessible from your bootloader. The factory reset was going to be my first suggestion but since your already done that have you tried to enter your recovery thru ADB/fastboot? (fastboot reboot recovery.) The other thing is what region are you in( India, Asia, European) and does " fastboot getvar all" work from using ADB? Also if your OS is wiped then any RUU flash will reformat your partitions for you and restore your rom. Also were you on kitkat or lollipop stock rom?
Click to expand...
Click to collapse
You are being kind to me by trying to resolve my problem.
1. I tried again but it did not help.
2. I will try "fastboot reboot recovery", and tell you about the result.
3. Through online chat I gave my IMEI to HTC middle east and they told me that my Software Version is 2.34.401.2.
4. " fastboot getvar all" works.
5. You said "if your OS is wiped then any RUU flash will reformat your partitions". Can we be sure that it is wiped? If we can not be sure, is it necessary to do wipes and formats?
6. I was on Lollipop. 5.0.2.
Since you never unlocked the bootloader before, flashing the stock rom(ruu) should work. Give it a shot. Just make sure you flash the same Android version that you had before as downgrading might not work.
Dr.Ghobar said:
You are being kind to me by trying to resolve my problem.
1. I tried again but it did not help.
2. I will try "fastboot reboot recovery", and tell you about the result.
3. Through online chat I gave my IMEI to HTC middle east and they told me that my Software Version is 2.34.401.2.
4. " fastboot getvar all" works.
5. You said "if your OS is wiped then any RUU flash will reformat your partitions". Can we be sure that it is wiped? If we can not be sure, is it necessary to do wipes and formats?
6. I was on Lollipop. 5.0.2.
Click to expand...
Click to collapse
1. That's fine. For now it's OK that it's locked. It's only if your stock recovery is gone that you would need to unlock the bootloader and reflash the stock recovery zip file that you would need to find and flash. Hopefully it's still there just inaccessible for now.
2. Just an idea to verify your recovery is still there
3. OK then that's the firmware you want to flash or higher version
4. From that it should have your CID and version ID but if it's corrupted or wiped it may not show. Those 2 are what you usually use to verify the firmware your flashing is the correct version for your region. You can also verify your radio ID as well as most firmware zips show those numbers as well.
5. It's OK an RUU file will reformat everything and bring it all back to stock. It has all the images in it (radio, system, recovery etc.)
6. That's good. Just make sure you flash that version or higher as going down in firmware isn't possible without S off. If you flash the wrong firmware then the signed RUU shouldn't flash.
Also what region are you in ( India, Asia, Europe?) your phones firmware (CID is your carriers region) that you flash needs to match you're CID.
thoctor said:
1. That's fine. For now it's OK that it's locked. It's only if your stock recovery is gone that you would need to unlock the bootloader and reflash the stock recovery zip file that you would need to find and flash. Hopefully it's still there just inaccessible for now.
2. Just an idea to verify your recovery is still there
3. OK then that's the firmware you want to flash or higher version
4. From that it should have your CID and version ID but if it's corrupted or wiped it may not show. Those 2 are what you usually use to verify the firmware your flashing is the correct version for your region. You can also verify your radio ID as well as most firmware zips show those numbers as well.
5. It's OK an RUU file will reformat everything and bring it all back to stock. It has all the images in it (radio, system, recovery etc.)
6. That's good. Just make sure you flash that version or higher as going down in firmware isn't possible without S off. If you flash the wrong firmware then the signed RUU shouldn't flash.
Also what region are you in ( India, Asia, Europe?) your phones firmware (CID is your carriers region) that you flash needs to match you're CID.
Click to expand...
Click to collapse
1. How did you know that the stock recovery is "still there just inaccessible for now"?
2. I will try after 35 hours from now.
4. INFOmodelid: 0P9C70***
INFOcidnum: HTC__J15
The picture attached to original post shows: RADIO-INVALID_VER_INFO
In getvar: INFOversion-baseband: INVALID_VER_INFO
About region: my CID is HTC_J15. And as my search shows, 401 (in my Software Version 2.34.401.2) means Europe.
Dr.Ghobar said:
1. How did you know that the stock recovery is "still there just inaccessible for now"?
2. I will try after 35 hours from now.
4. INFOmodelid: 0P9C70***
INFOcidnum: HTC__J15
The picture attached to original post shows: RADIO-INVALID_VER_INFO
In getvar: INFOversion-baseband: INVALID_VER_INFO
About region: my CID is HTC_J15. And as my search shows, 401 (in my Software Version 2.34.401.2) means Europe.
Click to expand...
Click to collapse
1. I don't know it's still there that's why I used the word "hopefully. " You should be glad that you can still get into your bootloader because without that access your phone is an expensive paper weight. Thanks for the other info. It's exactly what you need to know to find and flash your firmware.
ajeshmanu said:
Dwnload ur respective RUU zip file,rename the file to. "0P9CIMG.zip". put in ext.sd card ,put the phone in hboot mode..it will autimatically detect the file and will ask for permission
Click to expand...
Click to collapse
You said rename the file to "0P9CIMG.zip".
As getvar shows, my phone's exact modelid is: 0P9C70***
So what is the principle according to which the file should be renamed? that is, what characters of MID should be mentioned before .zip?
thoctor said:
1. I don't know it's still there that's why I used the word "hopefully. " You should be glad that you can still get into your bootloader because without that access your phone is an expensive paper weight. Thanks for the other info. It's exactly what you need to know to find and flash your firmware.
Click to expand...
Click to collapse
If "fastboot reboot recovery" cannot work, it means that I have lost stock recovery.
1. Am I right?
2. If it is not there, is it still possible to flash the rom? Or I must first flash the stock recovery?
3. Is possible lacking of stock recovery what prevents the phone from showing Yes or No page ("Unlocking bootloader?" page)
4. Is it possible just to flask stock recovery for now and leave flashing ROM to some time later?
Dr.Ghobar said:
If "fastboot reboot recovery" cannot work, it means that I have lost stock recovery.
1. Am I right?
2. If it is not there, is it still possible to flash the rom? Or I must first flash the stock recovery?
3. Is possible lacking of stock recovery what prevents the phone from showing Yes or No page ("Unlocking bootloader?" page)
Click to expand...
Click to collapse
1. Or it's corrupted but it could still be there.
2. Usually you need to flash back the stock recovery but I've heard of people flashing over their custom recovery with an RUU(rom utility upgrade) and the RUU replaced everything including the stock recovery which is in the file.
3. Not 100% sure on that one. The bootloader is a separate kernel provided with every Android OS so the recovery is separate from it. That one I can't figure out as when you were trying to unlock your bootloader you're firmware was fine at that time I assume. That's the strange part.
thoctor said:
That one I can't figure out as when you were trying to unlock your bootloader you're firmware was fine at that time I assume. That's the strange part.
Click to expand...
Click to collapse
You seem to mean I have had problem with unlocking bootloader when my phone was normal.
No. I did not try then. Only after problem I tried unlocking. Please read my post: No "Yes or No" page when Unlocking bootloader! http://forum.xda-developers.com/des...via-htcdev-t3316781/post65371393#post65371393
Stransky said:
Hi
Again thanks for the reply.
My 816 A5UL is Asia-HK-CHT
CID-622
I cannot find a RUU that matches.
I believe the Rom could be OPc21000
Which i cannot find anywhere.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
What is your "getvar all" information?
(Perhaps I can be able to give you some points.)
Hi guys, I'm a complete noob with these things. The phone I have is an
> HTC One M8 Harman Kardon Edition,
> S-ON and has ViperOneM8 1.8.0, running on
> Android 4.4.2 and
> HTC sense version 6.0.
> TWRP version 2.8.1.0
I want to update the android as this version is slowly becoming obsolete and the only time I have to do it is now.
Can you please help me with a detailed guide as I am a noob and really do not understand any guide on this website.
Help would really, really be appreciated
periodicGB said:
Hi guys, I'm a complete noob with these things. The phone I have is an
> HTC One M8 Harman Kardon Edition,
> S-ON and has ViperOneM8 1.8.0, running on
> Android 4.4.2 and
> HTC sense version 6.0.
> TWRP version 2.8.1.0
I want to update the android as this version is slowly becoming obsolete and the only time I have to do it is now.
Can you please help me with a detailed guide as I am a noob and really do not understand any guide on this website.
Help would really, really be appreciated
Click to expand...
Click to collapse
If u want to upgrade to marshmallow then it is quite simple. But before you do becareful, you will lose all your data and the phone will be completely stock condition. If you have the bootloader locked then you can directly go to the process as you are s-on. However if you have an unlocked bootloader you have to relock it first. So the next steps are simple. Download the marshmallow firmware ( the version should be 6.20.654.3) and marsmallow rom file ( same version number) keep both of those in your micro sd card and first rename the firmware file into (0P6BIMG.zip) note that the name should be exactly like this and no bracket. Now go to hboot. Enter fastboot of your phone.sitback and relax for 1min. The firmware will be automatically upgraded in your phone. Next after the phone restarts, delete the firmare file from your micro sd card and rename the rom file into the same name 0P6BIMG.zip and follow the same process like before. I mean enter hboot...go to fastboot ..sit back and relax. If u want to upgrade by flashing custom rom like the one u have now, flash via twrp and u can get plenty of guidelines for this and this is easier. Hope i kept it simple u will get the links to download necessary files in the OMJ,s thread
Tahsin005 said:
If u want to upgrade to marshmallow then it is quite simple. But before you do becareful, you will lose all your data and the phone will be completely stock condition. If you have the bootloader locked then you can directly go to the process as you are s-on. However if you have an unlocked bootloader you have to relock it first. So the next steps are simple. Download the marshmallow firmware ( the version should be 6.20.654.3) and marsmallow rom file ( same version number) keep both of those in your micro sd card and first rename the firmware file into (0P6BIMG.zip) note that the name should be exactly like this and no bracket. Now go to hboot. Enter fastboot of your phone.sitback and relax for 1min. The firmware will be automatically upgraded in your phone. Next after the phone restarts, delete the firmare file from your micro sd card and rename the rom file into the same name 0P6BIMG.zip and follow the same process like before. I mean enter hboot...go to fastboot ..sit back and relax. If u want to upgrade by flashing custom rom like the one u have now, flash via twrp and u can get plenty of guidelines for this and this is easier. Hope i kept it simple u will get the links to download necessary files in the OMJ,s thread
Click to expand...
Click to collapse
Hi, is there any way that I could do it using my PC.. Also, sorry for asking you so much repeatedly, but could you please point out where I could get the files for the firmware etc from?
Does it matter that I already have a custom ROM installed?
periodicGB said:
Hi, is there any way that I could do it using my PC.. Also, sorry for asking you so much repeatedly, but could you please point out where I could get the files for the firmware etc from?
Does it matter that I already have a custom ROM installed?
Click to expand...
Click to collapse
Yes you can upgrade by using pc too. In that case you have to download the adb tool in your pc and write few commands manually in the command prompt which is a huge bother :3. The process i mentioned is the easiest way. And the link of the firmware and rom is given below respectively
https://www.androidfilehost.com/?w=search&s=6.20.654.3_firmware_no_recovery_no_boot
https://www.androidfilehost.com/?fid=24391638059059360
periodicGB said:
Hi, is there any way that I could do it using my PC.. Also, sorry for asking you so much repeatedly, but could you please point out where I could get the files for the firmware etc from?
Does it matter that I already have a custom ROM installed?
Click to expand...
Click to collapse
To flash the firmware linked above with your PC:
adb reboot bootloader (if you aren't in bootloader already)
fastboot oem rebootRUU
fastboot flash zip 6.20.654.3_firmware_no_recovery_no_boot.zip
fastboot reboot bootloader
To flash the RUU.zip, you may have problems with the file size with regular adb/fastboot. You could get HTC's fastboot and flash it with that, but the SDcard method is much easier and quicker.
If you want to get HTC's fastboot (and more information on flashing firmware and RUU.zips), read the first couple of posts in this thread. It's a very comprehensive guide. That thread only covers GSM firmware, but the commands are the same. You'll just not be able to find any downloads there.
Good luck!