flashing radio firmware - Verizon Droid Incredible 2

i recently flashed my rom to ICS currently using this rom: http://forum.xda-developers.com/showthread.php?t=1846304
had this rom about a month but no matter what i do i cannot get the radio firmware to flash i have tried relocking my device that did not help, have mostly tried using Hboot it comes back and says pgimg32.zip is not the correct file, also CWM wont let me flash it
can someone tell me or point me to the info?
I DONT HAVE S OFF, I AM USING DEV UNLOCK
thanks in advance

camdizawg said:
i recently flashed my rom to ICS currently using this rom: http://forum.xda-developers.com/showthread.php?t=1846304
had this rom about a month but no matter what i do i cannot get the radio firmware to flash i have tried relocking my device that did not help, have mostly tried using Hboot it comes back and says pgimg32.zip is not the correct file, also CWM wont let me flash it
can someone tell me or point me to the info?
I DONT HAVE S OFF, I AM USING DEV UNLOCK
thanks in advance
Click to expand...
Click to collapse
Then the short answer is stop trying to flash it until you go s-off. As far as I understand one limitation of dev unlock is that you can't flash things like radios.

gtdtm said:
Then the short answer is stop trying to flash it until you go s-off. As far as I understand one limitation of dev unlock is that you can't flash things like radios.
Click to expand...
Click to collapse
^^^What he said, and you have the file named incorrectly (should be PG321IMG.zip). If you want to flash the firmware, obtain S-OFF first. After obtaining S-OFF, you must place the renamed file onto the sd-card. Make sure fastboot is unchecked under your phone settings. Boot into the bootloader and let it do its thing, then reboot.

brymaster5000 said:
^^^What he said, and you have the file named incorrectly (should be PG321IMG.zip). If you want to flash the firmware, obtain S-OFF first. After obtaining S-OFF, you must place the renamed file onto the sd-card. Make sure fastboot is unchecked under your phone settings. Boot into the bootloader and let it do its thing, then reboot.
Click to expand...
Click to collapse
Small correction to your post...Should be PG32IMG.zip (yours has a 1 in it).

Related

[Q] Finding CID for bricked phone

I'm so confused as to how to do this
I saw a thread that said:
Since you can go to hboot, that is good enough to check your CID.
Be in fastboot mode and type this :
fastboot getvar cid
I don't know how to do this at all...I just got Android
I have an HTC One V through Virgin Mobile in the USA , I accidentally wiped E:system because as I said i'm new, so I need the CID for the RUU file *have questions about that too, but let's find my CID first*
EDIT: I was trying to install the titanium kernel for overclocking, i erased the cache's and did a factory reset, accidentally cleared the system which means now it has no OS. Before anyone asks, yes i'm obviously rooted and have the bootloader unlocked.
As you have a VM device, you don't really need to find the CID.
Put your device in fastboot mode, relock your bootloader fastboot oem lock and run this RUU RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
Download from : http://htcruu.com/?dir=Primo
Or put in any cdma custom rom and use that to have a working phone. Just follow each ROM instruction carefully.
Yea I wanted the stock RUU. I relocked my bootloader it said "relocked" at the top when at the boot menu, is that correct? Also once I download and run this program you linked, what do I do then? Thank you so much in advanced for the help
That's correct. Just run the RUU and sit back.
If there are errors, maybe you need flash the stock boot.img and stock recovery.img first.
Just run the RUU first and report back any error. There are stock images around this Q&A section if needed.
Here you can have the stock boot.img : http://forum.xda-developers.com/showpost.php?p=31902114&postcount=8
Here you can have the stock recovery.img : http://forum.xda-developers.com/attachment.php?attachmentid=1193349&stc=1&d=1342100874
(rename it to recovery.img after you download).
Or here is a good explanation on how to get it done : http://forum.xda-developers.com/showpost.php?p=32849485&postcount=5
Also, the kernel you were trying to use is for the GSM version. Make sure anything you flash is for the Primoc/CDMA.
ckpv5 said:
That's correct. Just run the RUU and sit back.
If there are errors, maybe you need flash the stock boot.img and stock recovery.img first.
Just run the RUU first and report back any error. There are stock images around this Q&A section if needed.
Click to expand...
Click to collapse
Ok, downloaded it, about to run it:
OMG IT WORKED. I LOVE YOU SO MUCH. I WAS ALMOST IN TEARS FROM FRUSTRATION.
riggerman0421 said:
Also, the kernel you were trying to use is for the GSM version. Make sure anything you flash is for the Primoc/CDMA.
Click to expand...
Click to collapse
would this be the correct kernel?
http://forum.xda-developers.com/showthread.php?t=1844049
ItachiLvrX said:
Ok, downloaded it, about to run it:
OMG IT WORKED. I LOVE YOU SO MUCH. I WAS ALMOST IN TEARS FROM FRUSTRATION.
Click to expand...
Click to collapse
:good:
Can anyone confirm is this is the proper kernel for my phone?
http://forum.xda-developers.com/showthread.php?t=1844049
Sorry for all the questions, but we're all noobs once right?
ItachiLvrX said:
Can anyone confirm is this is the proper kernel for my phone?
http://forum.xda-developers.com/showthread.php?t=1844049
Sorry for all the questions, but we're all noobs once right?
Click to expand...
Click to collapse
I think most of CDMA users are sleeping at the moment.
That is the kernel for CDMA device, whether it is proper or not, not so sure as I am not a CDMA user. You can always try, if it is not working well then you can revert back with the kernel that I posted earlier as that is the stock kernel for your device.
So just try anything that said work with CDMA or PrimoC but NEVER the GSM or PrimoU
ckpv5 said:
I think most of CDMA users are sleeping at the moment.
That is the kernel for CDMA device, whether it is proper or not, not so sure as I am not a CDMA user. You can always try, if it is not working well then you can revert back with the kernel that I posted earlier as that is the stock kernel for your device.
So just try anything that said work with CDMA or PrimoC but NEVER the GSM or PrimoU
Click to expand...
Click to collapse
Well I tried that one, went into recovery and installed from Zip, it said success in TWRP, but I go into SetCPU to mess with the overclock stuff, and it says only 1000mhz, it's supposed to be at least 2k from the Kernel...
Nevermind, I think I got it. I can now set it to over 2.0 ghz, but that will be unstable and mess with my battery so i'll keep it between 1.2 and 1.4 Thanks again everyone so much for the help =)
If you are still running the stock rom or any ICS rom, I would recommend the latest Sickkernel from Simonsimons34(don't remember the version number). Download the zip, open the archive with 7zip, copy the boot.img to your fastboot folder. Reboot your to bootloader, flash boot.img in fastboot, "fastboot flash boot boot.img". Then reboot to recovery and flash the zip file.

Missing Firmware

Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.
yasha.sinitski said:
Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.
Click to expand...
Click to collapse
The Bootloader 3.18. tells you, you have 2.x firmware
So what is stopping me from flashing new firmware each time?
yasha.sinitski said:
So what is stopping me from flashing new firmware each time?
Click to expand...
Click to collapse
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.
xunholyx said:
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.
Click to expand...
Click to collapse
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.
yasha.sinitski said:
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.
Click to expand...
Click to collapse
It might be because you have a modified /system partition. Do you use Xposed?
xunholyx said:
It might be because you have a modified /system partition. Do you use Xposed?
Click to expand...
Click to collapse
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.
yasha.sinitski said:
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.
Click to expand...
Click to collapse
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
EDIT: I'm mistaken here. You need them unzipped. PM sent.
For others with the same issue of returning to Canadian stock, go to this thread for links and a guide on how to do so.
xunholyx said:
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
Click to expand...
Click to collapse
Are you going to post links? No matter what you do, I cant thank you enough for your help.
yasha.sinitski said:
Are you going to post links? No matter what you do, I cant thank you enough for your help.
Click to expand...
Click to collapse
Whoops!
Here ya go.
xunholyx said:
Whoops!
Here ya go.
Click to expand...
Click to collapse
Doing all that right now. I'll update how it goes.
yasha.sinitski said:
Doing all that right now. I'll update how it goes.
Click to expand...
Click to collapse
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Otherwise you brick your phone.
That the firmware number is not showing is not critical i think. Its a symtom of some roms.
I flashed the newest firmware to my m7, number was showing. Then i flash Viper 7.0.1 and after that, my number is hidden.
But everything works, so i think its not critical.
Roma80 said:
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Click to expand...
Click to collapse
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.
BerndM14 said:
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.
Click to expand...
Click to collapse
Oh okay, good to know.
I read wrong / missunderstood on other thread.
Roma80 said:
Oh okay, good to know.
I read wrong / missunderstood on other thread.
Click to expand...
Click to collapse
Yeah, Mike's guide has some good info. A lot of misinformation out there about some stuff.
He also has an excellent blog with plenty of info/resources if you're bored and what to read up on some stuff. Great site.
Android Revolution HD :good:

HTC One M8 Canadian RUU

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

[Q] Unlocked bootloader with wrong file

So I just spent the last couple hours trying to root my phone. Only to realize that when I unlocked the bootloader i requested the wrong unlock.bin file. Instead of selecting the htc m8 file, I selected all other supported devices. I don't know if this is the cause of my problem, but since I can't reboot to bootloader, I feel that it is. Is the solution as simple as relocking the bootloader and then unlocking it with the correct unlock.bin file. Or can i just get the correct file and unlock it again. I don't know if any of it will work since the phone won't go into the bootloader. Thought I would as people that know more than me before I brick my phone.
Getting all the stock files from here and then using your cpu to flash everything you should be fine.
jayandare said:
Getting all the stock files from here and then using your cpu to flash everything you should be fine.
Click to expand...
Click to collapse
Ok, Thought I would have to be able to reboot to bootloader in order to flash but I will give that a try. Was there supposed to be a link or did you just mean "from here" as in the xda site?
Tskizzle said:
Ok, Thought I would have to be able to reboot to bootloader in order to flash but I will give that a try. Was there supposed to be a link or did you just mean "from here" as in the xda site?
Click to expand...
Click to collapse
Stock ruu method ,lock bootloader first
manish dubey said:
Stock ruu method ,lock bootloader first
Click to expand...
Click to collapse
Ok thanks. I'll do some searching and figure out how to do that, then try and flash the stock ruu. I'll report back if I have any issues. Thank you again.
Tskizzle said:
Ok thanks. I'll do some searching and figure out how to do that, then try and flash the stock ruu. I'll report back if I have any issues. Thank you again.
Click to expand...
Click to collapse
So I've been reading around and come across some conflicting info. So I finally found the fastboot command to lock the bootloader but some have said to flash the stock ruu first while others say after. Can anyone clear this up for me and let me know if it makes a difference?
S-OFF - no need to relock the bootloader, just run the appropriate RUU
S-ON - relock the bootloader and then run the appropriate RUU
cheers.
Mr Hofs said:
S-OFF - no need to relock the bootloader, just run the appropriate RUU
S-ON - relock the bootloader and then run the appropriate RUU
cheers.
Click to expand...
Click to collapse
Thanks for the help. I think I can handle this now. Is it worth it to go S-off? I'm gonna root once I am back to stock
Tskizzle said:
Thanks for the help. I think I can handle this now. Is it worth it to go S-off? I'm gonna root once I am back to stock
Click to expand...
Click to collapse
Quick reattack on this. I never actually went away from stock. As I couldn't get into the bootloader I never flashed twrp or anything so do I really need to flash the stock RUU? Just trying to figure out for knowledge purposes. Am I basically flashing the RUU to start over from scratch or is it just a precautionary thing?

HTC Desire 816 Dual SIM, only boots into Fastboot!

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.)

Categories

Resources