Related
I have managed to root and S-OFF my phone (so I'm told), but no matter how I try I can't manage to flash the radio that goes with the android revolution ROM. I've not been able to get ENG S-OFF so I'm trying to flash the radio from the SD Card, but that failed as well.
My radio performance is pretty bad. I really need the new radio flashed to my phone to corrected radio issues.
Is there someone who understands radio flashing process well enough to walk me through it? I am willing to pay for the personal assistance.
Thanks,
Jacquie
http://forum.xda-developers.com/showthread.php?t=877295
rohithksaj said:
http://forum.xda-developers.com/showthread.php?t=877295
Click to expand...
Click to collapse
Thansk for the attempt to help. I have gotten as far as to tell the phone through android sdk fastboot flash radio radio.img. I get an error that says cannot load radio.img. Is there a particular format for the radio.img file? My appears to be in a zip file.
Thanks a million for getting me this far.
if your flashing the radio you downloaded from the android revolution ROM page unzip the file into a new folder then follow the instructions in the read me .. i have always done it that way and has worked for me every time and quite simple to follow ...
jacquiegardner said:
Thansk for the attempt to help. I have gotten as far as to tell the phone through android sdk fastboot flash radio radio.img. I get an error that says cannot load radio.img. Is there a particular format for the radio.img file? My appears to be in a zip file.
Thanks a million for getting me this far.
Click to expand...
Click to collapse
Check in the zip file; you should have a file named 'radio.img' - extract this file and copy it to the folder that you're running fastboot from (if you're using the SDK this is probably the tools folder). The file must be named 'radio.img' for that command to work.
If that doesn't work, exactly what error are you getting?
Edit: or do what sslysi says if you're wanting that radio; everything you need's in the download from that thread.
//sent from my HTC Desire HD using Tapatalk; all errors entirely intentional.
I can't follow android revolution for flashing radio because I can't get the tool to get ENG S-OFF. Already tried this method.
Any other suggestions?
Sent from my HTC Desire HD A9191 using XDA App
This is exactly what I did. Extracted the zip file and copied out the radio.IMG file into android SDK tools folder. I don't remember the exact error. I will follow up with another post. I should have put it in my original post reporting the problem. Maybe I'm just too frustrated with all this. In addition I can never get my phone into bootloader using vol- and power button. I'm sure there is a reason why all this stuff isn't working. I just don't know enough to put it all together.
Sent from my HTC Desire HD A9191 using XDA App
I used this app to root AMT and also to flash my latest radio.
radixon said:
I used this app to root AMT and also to flash my latest radio.
Click to expand...
Click to collapse
I was just going to post this. You cannot flash a radio with ENG-S ON, it needs to be OFF before flashing the radio.
Error says cannot load radio.
Sent from my HTC Desire HD A9191 using XDA App
fuzzbeans said:
I was just going to post this. You cannot flash a radio with ENG-S ON, it needs to be OFF before flashing the radio.
Click to expand...
Click to collapse
It is my understanding that some processes can flash with ENG S-OFF. I tried a number of methods to achieve ENG S-OFF, but can't get there. I am open to suggestions.
Thanks again,
Are you sure you are rooted? Hold down the vol - button whilst switching phone on to enter the bootloader. Once there it will tell you if you have eng s-off. If not use the tool from the link I posted before. I successfully used this app to root my phone after I had downgraded my phone.
Sent from my HTC Desire HD using XDA App
jacquiegardner said:
It is my understanding that some processes can flash with ENG S-OFF. I tried a number of methods to achieve ENG S-OFF, but can't get there. I am open to suggestions.
Thanks again,
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=855403
try this..it will work to ENG s-off...dont forget to turn usb debugging on
This is a much easier method to flash radios:
http://forum.xda-developers.com/showthread.php?t=1054304
Just download the radio file of your choice, put it in the root of your sdcard and boot into the bootloader.
Hi jacquiegardner
jacquiegardner said:
I have managed to root and S-OFF my phone (so I'm told), but no matter how I try I can't manage to flash the radio that goes with the android revolution ROM. I've not been able to get ENG S-OFF so I'm trying to flash the radio from the SD Card, but that failed as well.
My radio performance is pretty bad. I really need the new radio flashed to my phone to corrected radio issues.
Is there someone who understands radio flashing process well enough to walk me through it? I am willing to pay for the personal assistance.
Thanks,
Jacquie
Click to expand...
Click to collapse
I find your offer to Pay for help somewhat strange , simply because you have had numerous replies trying to help you, and you have so far ignored to use the FREE to use thanks button to those trying to help you.
Take Care
TheQuest
Help with flashing radio Desire HD
Hey,
I am an experienced and an advanced Android user/modder with a Desire HD. Here's how I flash a radio
First of all, you'll need to check if you're s-off. To do that, power off the phone, remove the battery, then replace the battery. Then, while pressing the volume down button, press the power button to start the phone in fastboot mode.
When the screen loads, check and see if it's S-OFF or if it's S-ON. If it's S-OFF, continue by following the instructions here: http://forum.xda-developers.com/showthread.php?t=1054304
I'll summarise it for you according to my own experience for you. I'll assume you're rooted and S-OFF
1. Download the radio of your choice. Rename it to PD98IMG.zip
2. Copy the PD98IMG.zip file to the root of your SD card.
3. Turn off the phone
4. Remove the battery, then replace it
5. Press VOLUME-DOWN while pressing POWER ON at the same time. Keep holding those buttons and do not release them until the fastboot screen shows up
6. At this screen, choose the BOOTLOADER option using the VOL-UP and DOWN to select, POWER button to confirm
7. The phone should then be scanning the SD card for the PD98IMG.zip file. When it's done scanning, it'll install it automatically.
8. Reboot and enjoy!
Also, you might wanna check the md5sum key after downloading your radio to prevent corruption of data.
P/S- You don't have to pay me, just hit the thank button.
jazztin_smith
jazztin_smith said:
Hey,
I am an experienced and an advanced Android user/modder with a Desire HD. Here's how I flash a radio
First of all, you'll need to check if you're s-off. To do that, power off the phone, remove the battery, then replace the battery. Then, while pressing the volume down button, press the power button to start the phone in fastboot mode.
When the screen loads, check and see if it's S-OFF or if it's S-ON. If it's S-OFF, continue by following the instructions here: http://forum.xda-developers.com/showthread.php?t=1054304
I'll summarise it for you according to my own experience for you. I'll assume you're rooted and S-OFF
1. Download the radio of your choice. Rename it to PD98IMG.zip
2. Copy the PD98IMG.zip file to the root of your SD card.
3. Turn off the phone
4. Remove the battery, then replace it
5. Press VOLUME-DOWN while pressing POWER ON at the same time. Keep holding those buttons and do not release them until the fastboot screen shows up
6. At this screen, choose the BOOTLOADER option using the VOL-UP and DOWN to select, POWER button to confirm
7. The phone should then be scanning the SD card for the PD98IMG.zip file. When it's done scanning, it'll install it automatically.
8. Reboot and enjoy!
Also, you might wanna check the md5sum key after downloading your radio to prevent corruption of data.
P/S- You don't have to pay me, just hit the thank button.
jazztin_smith
Click to expand...
Click to collapse
Yes? Why the dots? Did i say something wrong?
Edit: Oops, my browser showed those smileys as dots. lol. Anyway, do hit the thanks button! I'm a veteran android modder, but new at xda. Need to collect stats to upload my mods in the development forums =S
Hawks556 said:
This is a much easier method to flash radios:
http://forum.xda-developers.com/showthread.php?t=1054304
Just download the radio file of your choice, put it in the root of your sdcard and boot into the bootloader.
Click to expand...
Click to collapse
Tried this one too! It just said "failed."
rohithksaj said:
Click to expand...
Click to collapse
Thanks for trying, but already tried this method. Had to get into bootloader via command prompt, but it works, can't do it any other way. Navigated to the file and it started to load, then came back "failed."
I do have S-OFF and have been rooted. No ENG S-OFF.
Thanks again,
Hi. Firstly yes I have read, thread after thread after thread and I am now the owner of a useless phone.
Rom RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed
Kernal no clue right now
Radio 3.35.15.19
Hboot 6.01.1002
s- off
Tweaks / coustomizations you installed. none now
Memory card partitions info. it is partitioned but I cant remember now what size.
Brief history.
I was running latest CM7 but could not get GPS at all. I tried to flash various radio updates and got nowhere. In fact I only successfully flashed one and then I lost all my contacts and the damn phone decided not to sync with gmail so I thought sod it I will go back to stock and ran RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed exe.
Now I am stuck on the safety screen and bootloader is saying there is no backup etc.
Now. I have read through various threads, tried various things but I cant get teh damn thing to work.
Please dont say I should read this thread etc because I can assure you I have just been through 4 hours worth of them today and christ knows how many on this and other sites over the past month trying to get this bloody phone to work properly.
Can anyone give me some clear instructions where I can find out what my exact modle is, as I am beginning to think the processor etc in this phone is different to the ave Wildfire.
I dont care if its branded, stock, modded. I need it to txt, phone, www and GPS. Right no I just got the safety bar and no way of accessing the menus.
Chers. Chris
Im guessing I need to drop a rom in the SD card and recover that image.
But what ROM Ive downloaded every single one I can find. When I run recovery, there is a picture of a phone with a caution sign on it.
Step 1 - Recovery fix
Hi there!
The problem is that you don't have the correct recovery installed or this has been corrupted. Now, before we get started I just need to ask one question, as stupid as it may seem, I just need to make sure.
Do you own a HTC Wildfire (i.e. Buzz) or a HTC Wildfire S?
If it's the S one DO NOT try this fix! It may be that you have been trying to install the wrong soft on your phone an that's why it's not working. Instead, go to the HTC Wildfire S section of the forum.
However, if it's the regular HTC Wildfire (i.e. Buzz) you can proceed.
I've put together a little fix for you, just follow the steps below:
0. Download attached file and extract it somewhere easy to access.
1. Start phone in bootloader. ( volume down + power button)
2. Wait for phone to settle. (detects SD card, etc.)
3. Using volume buttons go to FASTBOOT and then select it by pressing the power button.
4. Connect your phone to the computer via USB cable.
6. Browse to the folder where you extracted the attachement and run as administrator the file flashrecovery.bat (right-click and select 'Run as administrator')
7. Follow the steps on screen.
8. All done! Now you should be able to go into RECOVERY to install a custom ROM.
OK I finally flashed a RUU that is working. Its from Japan with English option. But I have a working phone. It just wont access the market or any email and thinks im asian.
Has anyone got a working stock rom for a UK buzz please.
Krizztoff said:
OK I finally flashed a RUU that is working. Its from Japan with English option. But I have a working phone. It just wont access the market or any email and thinks im asian.
Has anyone got a working stock rom for a UK buzz please.
Click to expand...
Click to collapse
I was just about to write step 2 of the fix I gave above.
However, if you just want a HTC stock ROM just install the one below:
RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
Since your phone is S-OFF with the Revolutionary HBOOT, the HTC stock ROM won't be able to overwrite the HBOOT which is a good thing.
However, it WILL overwrite the recovery so if you want to install the recovery at a later date you will have to go through the Step 1 listeb above.
ovimunt said:
Hi there!
The problem is that you don't have the correct recovery installed or this has been corrupted. Now, before we get started I just need to ask one question, as stupid as it may seem, I just need to make sure.
Do you own a HTC Wildfire (i.e. Buzz) or a HTC Wildfire S?
If it's the S one DO NOT try this fix! It may be that you have been trying to install the wrong soft on your phone an that's why it's not working. Instead, go to the HTC Wildfire S section of the forum.
However, if it's the regular HTC Wildfire (i.e. Buzz) you can proceed.
I've put together a little fix for you, just follow the steps below:
0. Download attached file and extract it somewhere easy to access.
1. Start phone in bootloader. ( volume down + power button)
2. Wait for phone to settle. (detects SD card, etc.)
3. Using volume buttons go to FASTBOOT and then select it by pressing the power button.
4. Connect your phone to the computer via USB cable.
6. Browse to the folder where you extracted the attachement and run as administrator the file flashrecovery.bat (right-click and select 'Run as administrator')
7. Follow the steps on screen.
8. All done! Now you should be able to go into RECOVERY to install a custom ROM.
Click to expand...
Click to collapse
Hi yes its a Wildfire (buzz). something odd about it as I flashed 5 RUU's and none of them worked and now im up and running on a Korean language with English option.
Just stick onto that Korean ROM and then run the one in my previous link. That is the HTC Stock World Wide ROM - it should work on ANY HTC Wildfire (Buzz).
ovimunt said:
Just stick onto that Korean ROM and then run the one in my previous link. That is the HTC Stock World Wide ROM - it should work on ANY HTC Wildfire (Buzz).
Click to expand...
Click to collapse
Cheers. I am not a lover of the stock HTC rom, but I need the GPS to work and CM7 just doesnt and I have no intention of becoming a wizzkid at tweaking phones just to get them to do what they should, which it seems CM7 will make me.
At least I got teh phone to work without help which I am chuffed about. But I cannot even connect to market contacts or facefarce with this present one.
ovimunt said:
Just stick onto that Korean ROM and then run the one in my previous link. That is the HTC Stock World Wide ROM - it should work on ANY HTC Wildfire (Buzz).
Click to expand...
Click to collapse
What I meant is that now that you have a ROM installed you don't need to go through the steps that I was planning to explain.
Instead, if you want to get the stock HTC ROM all you have to do is to run the RUU that I mentioned in one of my previous posts.
RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe
As I was also saying, this ROM is definitely going to work fine on your phone.
ovimunt said:
What I meant is that now that you have a ROM installed you don't need to go through the steps that I was planning to explain.
Instead, if you want to get the stock HTC ROM all you have to do is to run the RUU that I mentioned in one of my previous posts.
RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe
As I was also saying, this ROM is definitely going to work fine on your phone.
Click to expand...
Click to collapse
Cheers. I overlooked this file as I thought it might be in a foreign language. Its all working except a training app that needs root and I really cannot be bothered. Owe you a beer.
Rooting you phone, again
Krizztoff said:
Cheers. I overlooked this file as I thought it might be in a foreign language. Its all working except a training app that needs root and I really cannot be bothered. Owe you a beer.
Click to expand...
Click to collapse
If you really want ROOT, that's easy enough to do now that you have the ROM I recommended. There's 2 ways depending on the HBOOT that you now have now your Wildfire. The stock ROM may have overwritten the Revolutionary HBOOT so you first need to check that:
1. Start you phone in boot mode (volume down + power) and see what the version number is.
2. If it's Hboot 1.01.0001 then you have HTC stock HBOOT so now you also have to look at the very first line to see if it's S-OFF or S-ON.
3. Otherwise, if it's Hboot 6.01.1002 (or anything that starts with 6) then you're still on Revolutionary HBOOT.
Now, based on the findings of the above, chose the option that suits you:
Option 1: for Revolutionary HBOOT 6.01.1002
1. Simply follow the steps in my very first post in this thread to restore your recovery. (this will have been overwritten by the stock RUU).
2. Copy the Superuser-3.0.7-efgh-signed.zip (see attached) file to your SD card, boot into recovery and install the zip. Now, you'll have root.
3. [Optional - only needed for some apps to run in root] Go to the Market and download BusyBox then install it in both locations, i.e. system/bin and then system/xbin.
4. That's it! You're all rooted now!
Option 2: for HTC stock HBOOT 1.01.1001 with S-ON
1. Go through the Revolutionary process again and at the end it will ask you if you want to install a recovery. Make sure that you DO!
Now follow steps 2 - 4 from Option 1 above.
Option 3: for HTC stock HBOOT 1.01.1001 with S-OFF
Well, this is very unlikely to happen but if it does you can either:
1. Try to use Unrevoked and then you may need to do step 3 from Option 1.
2. Or simply go straight to steps 2 - 4 from Option 1 above.
THAT'S IT! Now you should have root again!
Hi, so I've been trying to get the right radio for me and my friend with DHD (I have Inspire 4G and do not get any 3G signal) has this radio: 12.65.60.29_26.14.04.28_M. I found a download link on this site ( http://forum.xda-developers.com/showpost.php?p=9891546&postcount=1 but I am unable to flash it. I noticed the ZIP file does not contain "android-info.txt" file. I know how to flash a radio with bootloader and I was successful in flashing other radios but it seems that it cannot be flashed without the file or the file itself is corrupted.
So does anyone know how to flash it or does anybody have the ZIP file with android-info.txt ? thanks a lot people!
edit: oh and... the downloaded file does not pass the checksum test.
edit2: just wondering. there are three antennas on DHD. One for GPS (under flashlight cover), one at sim cover and one at battery cover. which one of these last two is for 3G signals? contacts might be bad or damaged
Xaverek said:
Hi, so I've been trying to get the right radio for me and my friend with DHD (I have Inspire 4G and do not get any 3G signal) has this radio: 12.65.60.29_26.14.04.28_M. I found a download link on this site ( http://forum.xda-developers.com/showpost.php?p=9891546&postcount=1 but I am unable to flash it. I noticed the ZIP file does not contain "android-info.txt" file. I know how to flash a radio with bootloader and I was successful in flashing other radios but it seems that it cannot be flashed without the file or the file itself is corrupted.
So does anyone know how to flash it or does anybody have the ZIP file with android-info.txt ? thanks a lot people!
edit: oh and... the downloaded file does not pass the checksum test.
edit2: just wondering. there are three antennas on DHD. One for GPS (under flashlight cover), one at sim cover and one at battery cover. which one of these last two is for 3G signals? contacts might be bad or damaged
Click to expand...
Click to collapse
To flash radio from that site you need ENG S-OFF which WILL MESS YOUR DEVICE. Check this thread (Inspire 4G and DHD radios are compatible as they are the same phone with different frequencies) to get a PD98IMG folder or use the guide in my signature to get an empty one:
http://forum.xda-developers.com/showthread.php?t=1106324
glevitan said:
To flash radio from that site you need ENG S-OFF which WILL MESS YOUR DEVICE. Check this thread (Inspire 4G and DHD radios are compatible as they are the same phone with different frequencies) to get a PD98IMG folder or use the guide in my signature to get an empty one:
http://forum.xda-developers.com/showthread.php?t=1106324
Click to expand...
Click to collapse
since I have been successful in flashing radios from that site I guess I already have ENG S-OFF (although I don't know how to determine it, I know I did some S-OFF). The thing is, I think I need the exact radio version I posted above since it should finally give me 3G. I am located in Central Europe and I believe those radios are mainly for USA, are they not? Also,
Q. Why not just go to the Desire HD thread for Radio and RIL files?
A. Because we own an Inspire. While these phones are almost identical, the software used on each is NOT always compatible. This includes Radio images.
Click to expand...
Click to collapse
so now I just don't get it
Xaverek said:
since I have been successful in flashing radios from that site I guess I already have ENG S-OFF (although I don't know how to determine it, I know I did some S-OFF). The thing is, I think I need the exact radio version I posted above since it should finally give me 3G. I am located in Central Europe and I believe those radios are mainly for USA, are they not? Also,
so now I just don't get it
Click to expand...
Click to collapse
S-OFF is not ENG S-OFF...so if you have ENG S-OFF in the bootloader you will see ACE PVT ENG S-OFF....
From the thread I linked you, you have compatible radios for DHD and Inspire...many of the radios are compatible thou not all of them have been tested. I have used many DHD radios in my Inspire and had no issues at all.
glevitan said:
S-OFF is not ENG S-OFF...
Click to expand...
Click to collapse
I figured as much.
since I have ACE PVT SHIP S-OFF RL in my bootloader, I don't understand HOW could I flash that radio if I need to be ENG S-OFF in order to do so... or does it just seem to be flashed and in fact it is not?
Xaverek said:
I figured as much.
since I have ACE PVT SHIP S-OFF RL in my bootloader, I don't understand HOW could I flash that radio if I need to be ENG S-OFF in order to do so... or does it just seem to be flashed and in fact it is not?
Click to expand...
Click to collapse
Have you read the thread I linked you? there is the key....you have to flash radios as PD98IMG.zip files in the bootloader. That is the safest way, anyway.
glevitan said:
Have you read the thread I linked you? there is the key....you have to flash radios as PD98IMG.zip files in the bootloader. That is the safest way, anyway.
Click to expand...
Click to collapse
I always download the ZIP package, rename to PD98IMG.zip, copy it to my SD card, reboot to bootloader, flash the radio, reboot the phone. Never did it different. And gave me error only once, only when the radio I need does not have android-something.txt file in the package.
I just need those packages with correct radio version and according RIL. and I'd like to know which antenna is which. so if anybody has or knows, please, do tell me.
Xaverek said:
I always download the ZIP package, rename to PD98IMG.zip, copy it to my SD card, reboot to bootloader, flash the radio, reboot the phone. Never did it different. And gave me error only once, only when the radio I need does not have android-something.txt file in the package.
I just need the package with correct radio version. and I'd like to know which antenna is which. so if anybody has or knows, please, do tell me.
Click to expand...
Click to collapse
For the 3rd time...read what I linked. I can not do your job, can I? why are you not reading?
glevitan said:
For the 3rd time...read what I linked. I can not do your job, can I? why are you not reading?
Click to expand...
Click to collapse
is there anything specific you want me to read outloud? there is NOT the correct version I need (well there is, but it is just incomplete). I know how to flash it, I know there are "slight differences" between inspire 4g and DHD (according to the topic) but I do not have the correct package so I could rename it and flash it. I tried. Oh yes I tried. Did not work. Wouldnt flash. So I just need a link to the correct version. If you don't have it, please, leave it.
MD5 is not the same in the post as on the file and there is one file less in the package than in other packages of different radios.
BTW, I am not asking you to do my work, I am just asking if anyone has it. I tried to google it, all of the links I have found are dead (or making me download some youtube downloader). Oh and I am reading.
you know what? somebody lock this thread, please... I think I want to figure this one out myself. Even if it means not having 3G in my phone. I am not going to let glevitan make fun of me. dunno who's not reading.
I've brought back my rooted (S-off) HTC Desire Bravo with a custom recovery
(4EXT)
and a custom Rom (RunnymedeAIO)
back to stock Software-number 3.14.405.1 by only using my SDcard.
I've used the Aplharev downgrader and the HTC RUU 2.3.3. Europe GSM.
I found all information I needed in Bortak's Troubleshooting Guide. Thanks :good:
#1
Check your battery or hook up your adapter! It all takes about 15 minutes.
I downgraded my HBoot by copying the dowgrader in the root of my SDcard and renamed it PB99IMG,
I installed it directly in the bootloader [volume-down + power button] and select 'Yes' in HBoot-menu when asked to start update?
And 'Yes' again to confirm reboot the device.
#2
Then I copied the extracted RUU (= a extracted rom.zip from HTC's RUU) so it could be used directly in the root of my SDcard by renaming it to PB99IMG
(remove or rename the previous PB99IMG) and I installed it again in the bootloader [volume-down + power button] and select 'Yes' in HBoot-menu when asked to start update?
(During the process the device will reboot once and will continue the update, just wait and follow the status onscreen)
Then select 'Yes' again to confirm reboot the device. Watch the magic work. :fingers-crossed:
All my data was erased and my phone was (S-on) like it came fresh from the store!!:fingers-crossed:
HBoot -1.02.0001
RADIO 5.17.05.23
SWnr.3.14.405.1
If you need more information or need more options just check Bortak's Troubleshooting Guide. Thanks :good:
Please send me your comments or ideas to help me and other Desire users, thanks.
If you want to make a real guide, you should give a bit more details.
Although this is a method the majority know, many won't know how to install a PB99IMG.zip file, nor how to extract the rom.zip from a RUU. Explain the whole process for both.
If you're gonna do something, do it properly.
Thanks OP
abaaaabbbb63 said:
If you want to make a real guide, you should give a bit more details.
Although this is a method the majority know, many won't know how to install a PB99IMG.zip file, nor how to extract the rom.zip from a RUU. Explain the whole process for both.
If you're gonna do something, do it properly.
Click to expand...
Click to collapse
I agree the OP could have provided more information (or links to the guide).
I however found this post extremely useful if only beacuse it was the first place I found where I could actually get the file I needed on my rubbish internet connection.
So thanks a lot OP, you fixed my phone.
abaaaabbbb63 said:
If you want to make a real guide, you should give a bit more details.
Although this is a method the majority know, many won't know how to install a PB99IMG.zip file, nor how to extract the rom.zip from a RUU. Explain the whole process for both.
If you're gonna do something, do it properly.
Click to expand...
Click to collapse
Hi abaaaabbbb63,
I tried to keep this as simple as possible because I am just an enthusiast who wants to help others HTC Bravo users (with no experience at all or less),
to get back to stock in a simple way. I hope it will do just that.
I added some extra information as requested and hope to please you to.
Greetings from Holland, IErkens
Thanks mate!
I found this guide very usefull..:good::good:
A CLARIFICATION before error!
Hi guys,
At the risk of appearing pretty stupid (fine by me!! ) rather than making a fatal error, would you mind guiding me through the following:
My HTC Desire BRAVO is currently S-OFF and has a CUSTOM ROM installed (Oxygen). Runs beautifully. The original 0.93 HBOOT was replaced using AlphaRev to current 6.93 in order to install OXYGEN ROM.
I need to hand this phone on to a friend and so would like to return it to stock: either to HTC factory stock or to its original TELSTRA Australia stock. REASON? simply to make it a clean stock standard unit ready for his use. There is no matter of returning it to stock for warranty purposes.
Question: Do I need to DOWNGRADE the bootloader first to theoriginal v.HBOOT 0.93 before running the stock RUU? or
BECAUSE it is already S-OFF, can I simply copy the Telstra RUU or HTC RUU (.exe file) to the external ext4 SD card and then access and run it through BOOT menu.(Clockwork - Revolutionary etc.)
What would you advise on this - plus any additional thoughts you may have!
Heaps of thanks in anticipation!
MattGloss said:
Hi guys,
At the risk of appearing pretty stupid (fine by me!! ) rather than making a fatal error, would you mind guiding me through the following:
My HTC Desire BRAVO is currently S-OFF and has a CUSTOM ROM installed (Oxygen). Runs beautifully. The original 0.93 HBOOT was replaced using AlphaRev to current 6.93 in order to install OXYGEN ROM.
I need to hand this phone on to a friend and so would like to return it to stock: either to HTC factory stock or to its original TELSTRA Australia stock. REASON? simply to make it a clean stock standard unit ready for his use. There is no matter of returning it to stock for warranty purposes.
Question: Do I need to DOWNGRADE the bootloader first to theoriginal v.HBOOT 0.93 before running the stock RUU? or
BECAUSE it is already S-OFF, can I simply copy the Telstra RUU or HTC RUU (.exe file) to the external ext4 SD card and then access and run it through BOOT menu.(Clockwork - Revolutionary etc.)
What would you advise on this - plus any additional thoughts you may have!
Heaps of thanks in anticipation!
Click to expand...
Click to collapse
Do this:
Download this ZIP (It's a RUU)
http://d-h.st/d44
And install it this way:
http://forum.xda-developers.com/showpost.php?p=45298337&postcount=21
What can I say...
abaaaabbbb63 said:
Do this:
Download this ZIP (It's a RUU)
http://d-h.st/d44
And install it this way:
http://forum.xda-developers.com/showpost.php?p=45298337&postcount=21
Click to expand...
Click to collapse
Many thanks... I'll follow the guru's way! Very grateful for your help. Matt
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 !