I've been using custom ROM's on my DHD for a couple of months now but have never flashed off the stock Radio.
Im thinking about it now, and have read this guide http://forum.xda-developers.com/showthread.php?t=896597 but want to make sure I know a couple of things before trying it cus i know it can screw stuff up
First, do I have both Radio S-off and Eng s-off? I've checked the first line of my bootloader which is ' ACE PVT ENG S-OFF ' which I guess means I have ENG S-OFF but what about Radio S-OFF?
Also, what precautions should be taken before flashing a radio? I know with ROM's it's Nandroid etc, but what about Radios?
Cheers!
Hi,
If you look at "system info" in the bootloader, what does your CID read? If you used the all in one tool to Radio S-OFF, SIM Unlock, etc then your CID should read CID-11111111
You should always double check the MD5 of the radio before flashing, just to ensure you don't flash a corrupted file.
I assume you know you have to flash radios with fastboot?
id say b4 u actually flash, type
fastboot devices
if it reads your phones serial numnber, u should b good 2 go
LINKSLOVESANDROID said:
if it reads your phones serial numnber, u should b good 2 go
Click to expand...
Click to collapse
That does not tell anything about radio s-off.
Hey guys thanks for all the quick replies! I know about flashing vi adb which I'm ok with, is there any kinds of back ups to do first?
Also, since I already have my ROM installed, will it need redoing after the radio? I read somewhere that the Radio needs doing before ROM...
Cheers
It does not matter when you flash the radio, before or after the ROM. ROM is not affected by radio, so you do not need any backups. Just go ahead and flash.
hi
i just downgraded my desire hd and then did a radio s-off but then i wanted to do a S-OFF.
i used the easyS-off but then it said bootloader corrupt do not reboot.
i already tried without "I Have Radio S-OFF" then it just says connection problem
i have charged only and debugging turned on
what now?
thnx
hmm what about Easy Radio Tools?
i used that for radio s-off
it worked now!! thnx to this guy
http://forum.xda-developers.com/showthread.php?t=999219
second post!!
I would be hesitamt to reboot though, haven't used the easytool as I personally prefer to know what steps are being carried out, but if it warns that the bootloader is corrupt I wouldn't reboot until I knew the situation is corrected.
Hello guys (I suppose most of the visitors are in fact guys ),
I downgraded my DHD to 1.32 this week and managed to get root-access and did a successful Radio S-OFF using the One click Radio S-OFF.
However; this morning I tried the One click ENG S-OFF but the first time I tried to run the tool I got an error stating "Connection error (SD)". Rebooted my phone and tried again.
This time I got the error "Bootloader corrupt, contact XDA".
After I almost crapped myself I started to search for a solution; someone on this forum stated to go to application settings - superuser - and clear data. Did it and then I got a bunch of applications which did a forced close.
Tried the One click tool again and got the same error (Bootloader corrupt).
In the meanwhile I got all this popups regarding android.process.acore needed to close which finally resulted in an unusable phone so I rebooted...
Thank god this went alright and my phone is up and running again but...
I think the last failure was probably caused by the One click app that doesn't have root access (didn' t get a popup though), but I'm a little afraid to try it again.
Does anyone know if it's save to try it again?
enz0123 said:
Does anyone know if it's save to try it again?
Click to expand...
Click to collapse
Why not do it longhand? Concise instructions are available here, I realise you already have root but even if you follow the instructions from the begining they aren't gonna do any harm.
Thanks, that could be a solution however I found out that I didn't check the box "I have Radio S-OFF
Tried again with the checkbox checked but got the same error again.
The files that were copied to my SD-card at the first attempt are still there.
Is it safe to remove these files?
Maybe that solves it...
It is very important, that you agree the super user request while the tool does its job.
I had the same problems some weeks ago (bootloader corrupt), because during the flash my display timeout was reached and the super user request failed (black locked screen).
If the tool can not get root, it can not copy the bootloader. The message "bootloader is corrupt" is confusing, because nothing has happend.
KaseDesire said:
If the tool can not get root, it can not copy the bootloader. The message "bootloader is corrupt" is confusing, because nothing has happend.
Click to expand...
Click to collapse
Which is one reason I favour doing it long hand at least then youd know it's failed to flash the bootloader
Hmm, strange.
When I boot into the bootmenu (vol. down + power) it states the I'm already ENG s-OFF and hav CID 111111...
Something must have gone right....
However I can't find the line anymore that states that I have Radio S-OFF, is this normal behaviour?
KaseDesire said:
It is very important, that you agree the super user request while the tool does its job.
Click to expand...
Click to collapse
Exactly! The instructions don't mention it, but when you run the easy s-off exe, it goes through a few steps and then your phone will ask you to allow superuser access. So have your screen on and be ready, and THEN run the easy s-off utility. That's all it was for me. I hit "OK" on the error message, tried it again but this time watched my phone and allowed SU access, and it worked fine.
Hi,
I'm posting here because i had the same problem ( Bootloader corrupt etc ... ).
First I rooted my DHD, and made it Eng s-off and installed a rom a few month ago.
Today I wanted to install another rom, and flash the radio.
But I did not remenbered if I already had the radio s-off, so i installed the 1.32 stokified rom, used the easy radio tool ( v2.2 ) and when i wanted to use the easy s-off tool ( v05 ), the program gave me the error message concerning the bootloader corrupt and stuff. I tried it with "I have radio s-off" ticked, and when I try it with unticked, I have a connection error message.
I tried to delete the data from SU, but it didn't help, and then I noticied ( remenbered ) that SU did not asked me the authorizations when I used easy radio tool ans easy s-off.
Anyone have an idea how I can fix that ? Maybe unistall/reinstall SU ?
HTC Desire HD radio S-OFF steps
http://www.youtube.com/watch?v=dTFphGbgqbQ&feature=player_embedded
Yes I did that after reinstalling the 1.32 rom, excepted the Visionary steps.
The root is permanent no ? I did it on my previous rom, so I don't have to root it again when I install another rom ?
Anyway, my DHD rebooted when I tried to secure the battery compartment, the bootloader wasn't corrupted, it's fine.
So I checked the bootload, I have ENG s-off and Cid 1111... this mean that my device is radio s-off too right ?
HornAdama said:
I have ENG s-off and Cid 1111... this mean that my device is radio s-off too right ?
Click to expand...
Click to collapse
Yes, you can install custom roms and flash radios now.
I installed the eng hboot .76 on an old evo that had the latest hboot 2.16. I wiped everything using fastboot command and had plan on restore everything to stock. but now nothing I will do will flash. I keep getting the "model id Error" every time I try to flash using the RUU utility and through hboot. I tried even using fastboot commands to flash the system.img but it says it's too large to flash through remote. I tried updating the hboot back to 2.16 but gives me the same error. Anyone has any suggestions? What is causing the evo to keep thinking I have the wrong model? thanks
I've never had that happen but make sure you have the right RUU for our phone also make sure you have the correct radios combo for the RUU your flashing.
linsalata28 said:
I've never had that happen but make sure you have the right RUU for our phone also make sure you have the correct radios combo for the RUU your flashing.
Click to expand...
Click to collapse
Unfortunately that didn't help either. I used a RUU image with the exact same radio version and still gives me the model id error
edit: Ok after some more research I found what my problem is but I have not found the solution. The problem is that I flashed an engineering hboot on an evo with the new partition cause other's that had done it are getting the same error messages I am. But I still haven't seen any of them finding a solution to get the evo working again. If anyone has any insight on this issue please help.
I don't think it is fixable now. Look in dev for RA like 3.08 gnm recovery. If you can get that to flash, then u may be able to use it to rewrite the blocks. Read about it in its thread
Support TrevE! Fuh Q CIQ!
I'm just stumped on why you would want to downgrade the Hboot?
{ParanoiA} said:
I don't think it is fixable now. Look in dev for RA like 3.08 gnm recovery. If you can get that to flash, then u may be able to use it to rewrite the blocks. Read about it in its thread
Support TrevE! Fuh Q CIQ!
Click to expand...
Click to collapse
Thanks that didn't seem to work either guess i'm out of luck. The reason I downgraded the Hboot was because I was replacing a broken evo with a blacklisted evo and this was a fast method to do that. But I forgot about the issue with the new hardware version.
HipKat said:
I'm just stumped on why you would want to downgrade the Hboot?
Click to expand...
Click to collapse
HipKat, I downgraded my HBOOT so I could flash a custom splash screen, just sayin'.
Sent from my PC36100 using XDA App
Well, I'm still trying to fix it so I'm going to post my progress just in case someone has any new ideas. First off I did make some progress as I no longer get the model id error and was able to start the flashing process now. But the process never finishes successfully. I started taking a different approach on how to fix the problem. Instead of looking for an EVO fix I research all the fastboot commands and what they can do. I managed to figure out that some how the model ID on my evo was removed and replace with a symbol that looks like a *. This was the cause of my error because it was comparing this to the mode id in the roms and failing. I found the fastboot command to update the model id and was actually able to start the flashing process. But 3/4 into the flashing it failed and gave me an error of "51 partition update fail". Now I can't get into the bootloader anymore and I only see the HTC Logo with 4 Exclamation marks at the corners. I still am able to execute fastboot commands so I'm continuing the research. So hopefully someone has a fix for this new error. thanks
Hello:
I have a rooted InC2 , Android 2.3.4
Hboot 6.13.1002 (not sure how I went from 0.98 to this version after S-OFF)
I need to return the phone because the earpiece does not work
Need back to stock (Android 2.3.4 Hboot 0.98)
I have the zip file for v2.3.4 but it is bypassing flashing the Bootloader.
My question is where can I get the Hboot 0.98 for INC2 and remove revolutionary?
I found a procedure for HTC Desire S where someone created a an EngBoot.img loader that you flash by using
" fastboot flash hboot engHBOOToverARX.img "and this version allows you to upgrade the next version
using the same command for the Hboot you want.
Then, I assume you can flash stock with the zip file
Has anyone done this ?
Is the hboot for HTC Desire the same as INC2? Can I use these files?
I know there some dd commands that can be used (I understand the risk) but I don't have Hboot 0.98 for INC2 , if the procedure above does not work for INC2, where can I find Hboot 0.98 and the dd procedure to flash it?
Can some one help me ?
thank you very much
vlsi99 said:
Hello:
I have a rooted InC2 , Android 2.3.4
Hboot 6.13.1002 (not sure how I went from 0.98 to this version after S-OFF)
I need to return the phone because the earpiece does not work
Need back to stock (Android 2.3.4 Hboot 0.98)
I have the zip file for v2.3.4 but it is bypassing flashing the Bootloader.
My question is where can I get the Hboot 0.98 for INC2 and remove revolutionary?
I found a procedure for HTC Desire S where someone created a an EngBoot.img loader that you flash by using
" fastboot flash hboot engHBOOToverARX.img "and this version allows you to upgrade the next version
using the same command for the Hboot you want.
Then, I assume you can flash stock with the zip file
Has anyone done this ?
Is the hboot for HTC Desire the same as INC2? Can I use these files?
I know there some dd commands that can be used (I understand the risk) but I don't have Hboot 0.98 for INC2 , if the procedure above does not work for INC2, where can I find Hboot 0.98 and the dd procedure to flash it?
Can some one help me ?
thank you very much
Click to expand...
Click to collapse
My educated guess is that you're flashing one of the newer custom DI2 Rom here (ported from 2.3.6 or 2.3.7 or based on the Chinese Rom) and it changed your HB too. As I recall when this sub-forum was very active then, WiFi and 3G data also become unresponsive or "buggy" at times. In any event, you should read this link carefully & follow the steps -
http://forum.xda-developers.com/showthread.php?t=1298990
The reference RUU file, if you cannot find it on VZW's linked website as it is a discontinued model, here is a working link that you can follow, housed on one of my Dropbox account, it is the original untouched one, clean & all. - skip to post #7 - http://forum.xda-developers.com/showthread.php?t=2427581
I do not recall whether it specifically restore the HB to the earlier one, but everything else will be OEM/stock fresh, ready to activate - as if it's just unboxed. Besides, techs will most likely not be checking yours for HB verison as long as it boot up normally and appeared working, assuming that you are returning it for repairs/exchange and within the warranty coverage period.
Good luck !
Letitride said:
My educated guess is that you're flashing one of the newer custom DI2 Rom here (ported from 2.3.6 or 2.3.7 or based on the Chinese Rom) and it changed your HB too. As I recall when this sub-forum was very active then, WiFi and 3G data also become unresponsive or "buggy" at times. In any event, you should read this link carefully & follow the steps -
http://forum.xda-developers.com/showthread.php?t=1298990
The reference RUU file, if you cannot find it on VZW's linked website as it is a discontinued model, here is a working link that you can follow, housed on one of my Dropbox account, it is the original untouched one, clean & all. - skip to post #7 - http://forum.xda-developers.com/showthread.php?t=2427581
I do not recall whether it specifically restore the HB to the earlier one, but everything else will be OEM/stock fresh, ready to activate - as if it's just unboxed. Besides, techs will most likely not be checking yours for HB verison as long as it boot up normally and appeared working, assuming that you are returning it for repairs/exchange and within the warranty coverage period.
Good luck !
Click to expand...
Click to collapse
I want to be sure I understand you instructions, I will perform these commands below . Should I flash the zip indicated or are you saying the last step "fastboot flash zip " I should replace the zip file for another from one of your links??
In post #7 there are 2 links :
To this file which is an executable
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Radio_1.09.01.1111_NV_VZW1.92_release_225831_signed
Will this executable generate a zip file?
the other link :
is a zip file All_Stock_PG32IMG.zip Or should I use this zip
adb shell rm -r /data/local/tmp/*
adb push zergRush /data/local/tmp/zergRush
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/zergRush
adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
fastboot reboot
Will this reflash Hboot to 0.98
and basically remove S-OFF correct?
thank you
vlsi99 said:
I want to be sure I understand you instructions, I will perform these commands below . Should I flash the zip indicated or are you saying the last step "fastboot flash zip " I should replace the zip file for another from one of your links??
In post #7 there are 2 links :
To this file which is an executable
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Radio_1.09.01.1111_NV_VZW1.92_release_225831_signed
Will this executable generate a zip file?
the other link :
is a zip file All_Stock_PG32IMG.zip Or should I use this zip
...
Click to expand...
Click to collapse
Ok, the RUU...signed file that is in one of my Dropbox account now (next 72 hours or so) is the *.exe file from VZW, it will NOT generate a Zip file and it does NOT run inside ADB. Just download it to your preferred drive/subfolder. Connect your DI2 and assuming the HTC drivers were installed and it recognized yours (as it should) - click on the RUU file name and it should launch, with VZW's disclaimers and warnings, etc. - read & click thru it, and proceed - AT YOUR OWN RISK, of course. It will take 5 to 10 minutes to flash, when it's done - follow the prompts & reboot the phone. EVERYTHING, everything will be wiped clean & sysem reset, UNrooted - back in stock form as shipped.
If there are errors for whatever reasons, it might failed and stop proceeding with the flashing.
THE PG32IMG.zip file from Condemned will NOT change/restore your bootloader to HB98 or HB97, it will only restore the ROM portion to factory stock conditions and is for rooted devices with working CWM/TWRP recoveries installed - since it is in ZIP file format.
So, backup & save your settings with TB and CWM Backup first, save them to a safe location (i.e. USB or standalone external drive, etc.) before proceeding with the more basic PG*.zip file if you just wanted to get a feel for restoring it to stock looking rom. Running the RUU file in *.exe format will reset and wipe everything completely - you will lose ROOT and custom recovery will be gone too, and you should also see HB9x restored as part of the process - I just don't recall, but it will otherwise be 99%+ stock in general. The outsourced tech geeks at VZW's service counter will most likely not be looking to see if you've "messed" with the bootloader to disallow your repair claims or warranty coverage.
Good luck & please post your outcome/results - and/or if you run into other problems in the process.
Letitride said:
Ok, the RUU...signed file that is in one of my Dropbox account now (next 72 hours or so) is the *.exe file from VZW, it will NOT generate a Zip file and it does NOT run inside ADB. Just download it to your preferred drive/subfolder. Connect your DI2 and assuming the HTC drivers were installed and it recognized yours (as it should) - click on the RUU file name and it should launch, with VZW's disclaimers and warnings, etc. - read & click thru it, and proceed - AT YOUR OWN RISK, of course. It will take 5 to 10 minutes to flash, when it's done - follow the prompts & reboot the phone. EVERYTHING, everything will be wiped clean & sysem reset, UNrooted - back in stock form as shipped.
If there are errors for whatever reasons, it might failed and stop proceeding with the flashing.
THE PG32IMG.zip file from Condemned will NOT change/restore your bootloader to HB98 or HB97, it will only restore the ROM portion to factory stock conditions and is for rooted devices with working CWM/TWRP recoveries installed - since it is in ZIP file format.
So, backup & save your settings with TB and CWM Backup first, save them to a safe location (i.e. USB or standalone external drive, etc.) before proceeding with the more basic PG*.zip file if you just wanted to get a feel for restoring it to stock looking rom. Running the RUU file in *.exe format will reset and wipe everything completely - you will lose ROOT and custom recovery will be gone too, and you should also see HB9x restored as part of the process - I just don't recall, but it will otherwise be 99%+ stock in general. The outsourced tech geeks at VZW's service counter will most likely not be looking to see if you've "messed" with the bootloader to disallow your repair claims or warranty coverage.
Good luck & please post your outcome/results - and/or if you run into other problems in the process.
Click to expand...
Click to collapse
Sorry, I got confused because this link http://forum.xda-developers.com/show....php?t=1298990 has the instructions I posted and I thought I needed to execute. However, it seems all I have to do is run the executable to be stock.
I am just curious what are those commands for in the above link?
thank you very much
vlsi99 said:
Sorry, I got confused because this link http://forum.xda-developers.com/show....php?t=1298990 has the instructions I posted and I thought I needed to execute. However, it seems all I have to do is run the executable to be stock.
I am just curious what are those commands for in the above link?
thank you very much
Click to expand...
Click to collapse
I may have misunderstood you.. running the executable just re-flashed ROM still S-OFF and @ hboot 6.13.1002
I though I saw the message flashing Hboot and it completed successfully. Did I miss a step?
thanks
vlsi99 said:
I may have misunderstood you.. running the executable just re-flashed ROM still S-OFF and @ hboot 6.13.1002
I though I saw the message flashing Hboot and it completed successfully. Did I miss a step?
Click to expand...
Click to collapse
I see, okay - so you have the stock ROM on the device but it's still S-OFF with HB 6.13.1002 .... I went back to the older posts as it's been a while.
Well, if you feel you must get it to stock conditions, then I would say you need to run the ADB scripts as some users did have problems and it took more than one attempt to get it to work - http://forum.xda-developers.com/showthread.php?t=1298990&page=17
Check that you have only HTC drivers installed and other USB device drivers uninstalled from the PC (running Vista or Win7, correct - or XP ??)
reboot the computer and connect DI2 with the micro-USB cable, and make sure that all the files needed are in the same sub-folder, including the RUU file as you've downloaded. Turn off your anti-virus & firewall temporary - restore them/ON afterward.
Log into command prompt as administrator on the PC, run the adb scripts - and as it continued, you should see the progress and/or error messages across the screen.
Let's try that - also look at, starting from post #161 from the linked post above.
Please advise as to your results afterward or whether you are still S-OFF with the same HB. Thanks.
fortified wardaid
Letitride said:
I see, okay - so you have the stock ROM on the device but it's still S-OFF with HB 6.13.1002 .... I went back to the older posts as it's been a while.
Well, if you feel you must get it to stock conditions, then I would say you need to run the ADB scripts as some users did have problems and it took more than one attempt to get it to work - http://forum.xda-developers.com/showthread.php?t=1298990&page=17
Check that you have only HTC drivers installed and other USB device drivers uninstalled from the PC (running Vista or Win7, correct - or XP ??)
reboot the computer and connect DI2 with the micro-USB cable, and make sure that all the files needed are in the same sub-folder, including the RUU file as you've downloaded. Turn off your anti-virus & firewall temporary - restore them/ON afterward.
Log into command prompt as administrator on the PC, run the adb scripts - and as it continued, you should see the progress and/or error messages across the screen.
Let's try that - also look at, starting from post #161 from the linked post above.
Please advise as to your results afterward or whether you are still S-OFF with the same HB. Thanks.
Click to expand...
Click to collapse
Android 2.3.3 S-OFF same boot 6.13.1002 :crying:
One concern, if I do something else where S-OFF is removed and it does not leave me at Stock 2.3.4 , will still be able to use the executable to get back to Android 2.3.4 (with S-ON this time)?
Another comment that may or may not be related , through all these flashing sequences that I have tried , if a new radio is re-flashed, I get into the loop reboot mode and I need to reflash version
1.09.01.0312_vivow_Radio_PG32IMG.zip to stop it.
Any other ideas to remove S-off?
thank you
vlsi99 said:
Android 2.3.3 S-OFF same boot 6.13.1002 :crying:
One concern, if I do something else where S-OFF is removed and it does not leave me at Stock 2.3.4 , will still be able to use the executable to get back to Android 2.3.4 (with S-ON this time)?
Another comment that may or may not be related , through all these flashing sequences that I have tried , if a new radio is re-flashed, I get into the loop reboot mode and I need to reflash version
1.09.01.0312_vivow_Radio_PG32IMG.zip to stop it.
Any other ideas to remove S-off? ...
Click to expand...
Click to collapse
See this hosted link to a full collection of RUU / roms for the DI2, including those outside US and overseas - please only consider using the last 7 at the bottom as you scroll down, the final 3 might be the older ones (2.3.3 ??) - I've never used this link's files to reflash our DI2, but the download links are working and MD5's provided to verify its integrity upon d/l completion. Use at your own risks & discretion. http://www.androidruu.com/index.php?developer=Vivo_VivoW
The x.0312 radio isn't the newest one, if I am not mistaken - the x.0320 radio is the newest official VZW release for the DI2 & compatible with Gingerbread roms. The older ones x.0622 or x.0722 and there was another one in between 0.1111 radio - these might be causing problems with the newer Roms. Most of the custom Rom offered here usually (but not always) as a matter of practice, does not change or re-flash to a newer radio unless it specifically stated so in the instructions - so I would just keep extra copies named with its version available, and rename it to PG32IMG.ZIP before moving it onto the mSD card to flash from the Bootloader in case of boot-looping. Just be careful as flashing a non DI2 radio will permanently brick your device.
Our DI2 are on SkyRaider (2.3.4) and runs great with the .0320 radio (the 0.312 radio was used earlier.)
More reading for you - http://forum.xda-developers.com/showthread.php?t=1751796 - with the TACOROOT method, it will downgrade and result in S-ON, prior to running Revolutionary to get S-OFF again with additional steps. Consider this as it sounded like you are comfortable with using ADB.
If you manage to get S-ON somehow via other discovered means, flashing the *.exe again should not affect S-ON/OFF setting.
Generally speaking, if you managed to get the device back to 99% stock look & functioning, and there is no water damage or physical breakage due to accidental dropping, etc. - you shouldn't have any problems with warranty repair or exchange at VZW - I have yet to come across hearing/reading about anyone being denied a claim for updating the radio, HB or kernel, etc. Just bring/send it back to nearly as stock as possible, move/delete anything "unusual" that might be on your mSD card (i.e. empty subdirectory of CWM or Titanium Backup, etc.) and I think you will be fine.
Letitride said:
See this hosted link to a full collection of RUU / roms for the DI2, including those outside US and overseas - please only consider using the last 7 at the bottom as you scroll down, the final 3 might be the older ones (2.3.3 ??) - I've never used this link's files to reflash our DI2, but the download links are working and MD5's provided to verify its integrity upon d/l completion. Use at your own risks & discretion. http://www.androidruu.com/index.php?developer=Vivo_VivoW
The x.0312 radio isn't the newest one, if I am not mistaken - the x.0320 radio is the newest official VZW release for the DI2 & compatible with Gingerbread roms. The older ones x.0622 or x.0722 and there was another one in between 0.1111 radio - these might be causing problems with the newer Roms. Most of the custom Rom offered here usually (but not always) as a matter of practice, does not change or re-flash to a newer radio unless it specifically stated so in the instructions - so I would just keep extra copies named with its version available, and rename it to PG32IMG.ZIP before moving it onto the mSD card to flash from the Bootloader in case of boot-looping. Just be careful as flashing a non DI2 radio will permanently brick your device.
Our DI2 are on SkyRaider (2.3.4) and runs great with the .0320 radio (the 0.312 radio was used earlier.)
More reading for you - http://forum.xda-developers.com/showthread.php?t=1751796 - with the TACOROOT method, it will downgrade and result in S-ON, prior to running Revolutionary to get S-OFF again with additional steps. Consider this as it sounded like you are comfortable with using ADB.
If you manage to get S-ON somehow via other discovered means, flashing the *.exe again should not affect S-ON/OFF setting.
Generally speaking, if you managed to get the device back to 99% stock look & functioning, and there is no water damage or physical breakage due to accidental dropping, etc. - you shouldn't have any problems with warranty repair or exchange at VZW - I have yet to come across hearing/reading about anyone being denied a claim for updating the radio, HB or kernel, etc. Just bring/send it back to nearly as stock as possible, move/delete anything "unusual" that might be on your mSD card (i.e. empty subdirectory of CWM or Titanium Backup, etc.) and I think you will be fine.
Click to expand...
Click to collapse
One question, the *exe you first gave me had a radio 1111 with 2.3.4 , however it had the bootloop problem. The last downgrade to 2.3.3 that I did had another radio that also caused the bootloop problem. My fear is that if I accomplish S-ON and use any *exe to go back to stock 2.3.4 , I will have the bootproble without a way to reflash the radio 302 since I am S-ON at that point.
Is there a way to fix the bootloop problem with S-ON?
Is this make sense to you?
Just to be sure , doing this below, downgrades only the Hboot or also does S-ON, Reading the post is a procedure for phones that S-ON with a particular Hboot and FW version below certain number. Are you recommending this just to downgrade Hboot?
DOWNGRADE TOOL
Versions: HBOOT .98, firmware below 6.01.605.05
This will not work with firmware version 6.01.605.05! Use the tacoroot method!
This tool will downgrade you to 2.3.3, which will allow you to use Revolutionary to gain S-OFF.
Download the tool here, and extract it to a folder where you can easily get to it in a command prompt/terminal.
Now, connect your device to your computer with a USB cable, and turn on USB Debugging in settings. To ensure you are connected, open a command prompt/terminal and type "adb devices". If you see a bunch of letters and numbers followed by "device," you're good to go.
It is more like a challenge now..but may be I should send the phone back with 2.3.4 and S-OFF. I will appreciate if you can answer my questions above.
thanks again
vlsi99 said:
One question, the *exe you first gave me had a radio 1111 with 2.3.4 , however it had the bootloop problem. The last downgrade to 2.3.3 that I did had another radio that also caused the bootloop problem. My fear is that if I accomplish S-ON and use any *exe to go back to stock 2.3.4 , I will have the bootproble without a way to reflash the radio 302 since I am S-ON at that point.
Is there a way to fix the bootloop problem with S-ON? Is this make sense to you?
Just to be sure , doing this below, downgrades only the Hboot or also does S-ON, Reading the post is a procedure for phones that S-ON with a particular Hboot and FW version below certain number. Are you recommending this just to downgrade Hboot?
DOWNGRADE TOOL
Versions: HBOOT .98, firmware below 6.01.605.05
This will not work with firmware version 6.01.605.05! Use the tacoroot method!
This tool will downgrade you to 2.3.3, which will allow you to use Revolutionary to gain S-OFF.
Download the tool here, and extract it to a folder where you can easily get to it in a command prompt/terminal.
Now, connect your device to your computer with a USB cable, and turn on USB Debugging in settings. To ensure you are connected, open a command prompt/terminal and type "adb devices". If you see a bunch of letters and numbers followed by "device," you're good to go.
It is more like a challenge now..but may be I should send the phone back with 2.3.4 and S-OFF ...
Click to expand...
Click to collapse
I have been searching other related Android sources for answers in addition to what's been discussed & shared here - some of the older "tools" or linked files are no longer available (due to various file hosting sites being offline, etc.) so practical options are limited.
A number of older radios apparently bootlooped with 2.3.4 roms (including 622, 722 and 1111 radios) 312 radio works fine and we have them on 2 of our DI2's, the 320 radio is for ICS roms and newer without bootloop issues. If you managed to find a way to lock up the bootloader and S-ON again, and reflashing a stock ROM - it is possible you will experience continuous looping - or, worst, end up bricking the device for good.
Other users have noted that with the newer bootloader that you are on - that downgrading or going back to HB98 or HB97 has been a challenge, if not impossible. Additional attempts could cause more harm than good, bricking the phone - maybe it's time to just leave it alone & send it back for repair/exchange as IS - due to earpiece/volumne issue. If the phone boot & behave normally, have no water damage and other physical breakage, your warranty should be honored.
At this moment, just to be clear - do you still have CWM or custom recovery on the DI2, what kernel & radio are you using?
Letitride said:
I have been searching other related Android sources for answers in addition to what's been discussed & shared here - some of the older "tools" or linked files are no longer available (due to various file hosting sites being offline, etc.) so practical options are limited.
A number of older radios apparently bootlooped with 2.3.4 roms (including 622, 722 and 1111 radios) 312 radio works fine and we have them on 2 of our DI2's, the 320 radio is for ICS roms and newer without bootloop issues. If you managed to find a way to lock up the bootloader and S-ON again, and reflashing a stock ROM - it is possible you will experience continuous looping - or, worst, end up bricking the device for good.
Other users have noted that with the newer bootloader that you are on - that downgrading or going back to HB98 or HB97 has been a challenge, if not impossible. Additional attempts could cause more harm than good, bricking the phone - maybe it's time to just leave it alone & send it back for repair/exchange as IS - due to earpiece/volumne issue. If the phone boot & behave normally, have no water damage and other physical breakage, your warranty should be honored.
At this moment, just to be clear - do you still have CWM or custom recovery on the DI2, what kernel & radio are you using?
Click to expand...
Click to collapse
I am at 2.3.3 ,radio 302 , K 2.6.35.9 (from my last downgrade attempt). Since your *.exe brought me to 2.3.4 (with 1111 radio) , I will re-flash this and put radio 302 back. I have already done this so it is pretty safe. I did not find a *exe RRU with 5.10.605.9 with radio 302.
I have CSW
Doe sit make sense?
thank you so much for all your help
vlsi99 said:
I am at 2.3.3 ,radio 302 , K 2.6.35.9 (from my last downgrade attempt). Since your *.exe brought me to 2.3.4 (with 1111 radio) , I will re-flash this and put radio 302 back. I have already done this so it is pretty safe. I did not find a *exe RRU with 5.10.605.9 with radio 302. ... I have CSW ... Doe sit make sense? /QUOTE]
Hmm, interesting - the 302 radio was only for 2.3.3 Froyo - the earliest batch of DI2 and mostdefinitely had HB.97 bootloader.
Our black DI2 had HB.97 bootloader but was already on GingerBread ROM when unboxed (back in Oct. 2011) and DW's red DI2 had HB.98 bootloader w. GB - we had 622, 722 and 1111 radio - both running .0312 radios now (320 for ICS didn't do anything for us running 2.3.4 Sense-based SkyRaider)
CondemnedSoul isn't active these days (great developer to the HTC Eris days) - has a Return to Stock PG32IMG zip file, that is based on 5.10.605 RUU that you can flash from Custom Recovery (CWM) after downloading, verifying MD5 and moving to mSD card. He does good stuff and everything should be self-contained and should not result in bootlooping, regardless of the radio that is being used.
Here is the link again - http://forum.xda-developers.com/showthread.php?t=1599767
Link to various DI2 radios - http://forum.xda-developers.com/showthread.php?t=1134451
For comparison, I'm @ 2.3.4 with SkyRaider Zeus v1.3 - Kernel 2.6.35. and .0312 radio (Hardware ver is 0001) Since you still have Custom Recovery with S-OFF, you knew already how to fix or stop the bootloop by reflashing the radio - you might want to try the Return to stock PG32IMG zip from CS (link is good & valid) and see what happened then - not sure if it is going to help downgrade the Bootloader. The worst is that you will run the RUU again - how's that sound to you?
From the AndroidRUU host site - the last one on the bottom is the Froyo-based RUU file for the DI2 - http://www.androidruu.com/getdownlo...1.0225_2_NV_VZW1.92_release_182876_signed.exe
D/L it first if you are daring enough to flash it - proceed at your OWN RISKS - to see whether it can downgrade the bootloader as well. http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
Click to expand...
Click to collapse
curti was
Letitride said:
I have been searching other related Android sources for answers in addition to what's been discussed & shared here - some of the older "tools" or linked files are no longer available (due to various file hosting sites being offline, etc.) so practical options are limited.
A number of older radios apparently bootlooped with 2.3.4 roms (including 622, 722 and 1111 radios) 312 radio works fine and we have them on 2 of our DI2's, the 320 radio is for ICS roms and newer without bootloop issues. If you managed to find a way to lock up the bootloader and S-ON again, and reflashing a stock ROM - it is possible you will experience continuous looping - or, worst, end up bricking the device for good.
Other users have noted that with the newer bootloader that you are on - that downgrading or going back to HB98 or HB97 has been a challenge, if not impossible. Additional attempts could cause more harm than good, bricking the phone - maybe it's time to just leave it alone & send it back for repair/exchange as IS - due to earpiece/volumne issue. If the phone boot & behave normally, have no water damage and other physical breakage, your warranty should be honored.
At this moment, just to be clear - do you still have CWM or custom recovery on the DI2, what kernel & radio are you using?
Click to expand...
Click to collapse
Ok here is how to S-ON and go back to v2,3,4 only if your phone works with radio 1111, IMPORTANT ---< You need to try this version with S-OFF first in case you get into booloop and can re-flash the radio 312
Follow this link
http://www.iball99.com/2013/04/htc-incredible-2-gingerbread-rooted-stock/
Revert to Stock Froyo
Re-flash Hboot 0.97 ---<At this point you are S-off but the next stock flash will take you back to S-ON
Update back to Gingerbread ----< WARNING assuming you don't get into booloop with radio 1111
Otherwise, I assume you can't recover from with S-ON and bootloop mode?? Is this true??
I did not try to reflash stock because my phone gets into bootloop with radio 1111.
But I was able to downgrade and re-flash Hboot 0.97 . I only need a to find a zip or ^exe with radio 312
I really appreciate your help!!
vlsi99 said:
Ok here is how to S-ON and go back to v2,3,4 only if your phone works with radio 1111, IMPORTANT ---< You need to try this version with S-OFF first in case you get into booloop and can re-flash the radio 312
Follow this link http://www.iball99.com/2013/04/htc-incredible-2-gingerbread-rooted-stock/
Revert to Stock Froyo
Re-flash Hboot 0.97 ---<At this point you are S-off but the next stock flash will take you back to S-ON
Update back to Gingerbread ----< WARNING assuming you don't get into booloop with radio 1111
Otherwise, I assume you can't recover from with S-ON and bootloop mode?? Is this true??
I did not try to reflash stock because my phone gets into bootloop with radio 1111.
But I was able to downgrade and re-flash Hboot 0.97 . I only need a to find a zip or ^exe with radio 312
Click to expand...
Click to collapse
Thanks for the info - for the time being, my motto is "if it ain't broke, don't mess with it or change it" but I'm downloading those patches via my Linux server to offline storage, just in case that I want to or need it later on, once I'm done with using the DI2 as my daily device, LOL - less than 2 months left on my contract & seriously considering Nexus 4 now the price drop - whether there's a Gen II or now, just to team up with the beloved Nexus 7 running JB 4.3
If I am going to play - and mine doesn't bootloop with the 1111 radio (nor the 722 or 622 radios based on Froyos) - flash the stock RUU files - it's been a while in dealing with those *.nb0 - once it's back to S-ON and locked bootloader with stock recovery, it's much harder to recover if the Rom run into a continuous looping. Our warranty has expired long ago and I don't plan on selling these on *Bay with its low resale/market value, so just going to keep it as a backup even if I'm going to switch to GSM services - 3G CDMA coverage is barely working inside our house but thankfully for Fios, I have ultra fast broadband coverage 85% to 90% of the time that smoked the best 4G LTE out there today.
I dont' recall either, whether one of the GB RUU from VZW has the 312 radio included in the *.exe download, it could've been an OTA file on a stock Rom, but the 1111 radio was definitely in one of the stock RUU in the link - the discussions on where the developers (AndyBone, CS or Nit's) pulled the 312 radio were "buried" in their development Rom's, if only I have time to dig thru them.
Sounds like your DI2 is where you wanted it to be in restoring to stock form, good luck in getting the warranty exchange or repair done. Regards !