Related
Aloha everyone,
I'm currently running Innefabilis 1.0 (Gingerbread) and running DSB's Kernel (Stock but tweaked). I'm a little confused on how to update my Firmware and Radio after reading many threads in the Development Section.
Recently I flashed an ICS ROM and had the mainver error every time I tried to revert back to Gingerbread. I finally fixed the mainver error and would like to update my phone to the latest Firmware AND Radio.
As far as I've read, in order for me to update my Firmware and Radio, I have to do a NAND Backup, relock my device, install the latest update via bootloader, and unlock again and restore my ROM. Though I've seen in other threads some people didn't need to relock their devices to install the latest update.
My questions are:
1) Do I need to flash a Stock Rooted ROM before I relock my phone to do the update? Because I've removed some bloatware from my current ROM.
2) Is there an easier method to Update my Firmware and Radio on my Rooted Rezound? If so, would someone like to provide me easy steps to doing so?
Any help would be much appreciated. Thanks in advance!
Nandroid backup
Flash radios via hboot
Relock
Flash kernel for ICS. You can find it in Nils kernel thread.
Unlock
Restore amon ra recovery
Reroot via amon ra
Restore nandroid.
That is ofcourse if you mainver is below or at 2.10. If not then you have to play that game again.
That is the short and sweet version. If you need more I can lay it out again in a more detailed way later tonight.
Sent from my ADR6425LVW using xda premium
Or flash the kernel you need. Nils kernel thread explains it all.
Sent from my ADR6425LVW using xda premium
Thanks EmerikL,
I do have a couple more questions, I currently have CWM installed.
Is it okay to flash Amon Ra over CWM?
Also, can you tell me how to unlock and relock my Rezound please? LOL.
I know how to unlock via HTCDev website but unsure about locking.
Yes you can flash over CWM with Amon Ra.
In fastboot type fastboot oem lock. To unlock type fastboot oem unlock unlockrohen.bin
Sent from my VTAB1008 using xda premium
madhomey752002 said:
Aloha everyone,
I'm currently running Innefabilis 1.0 (Gingerbread) and running DSB's Kernel (Stock but tweaked). I'm a little confused on how to update my Firmware and Radio after reading many threads in the Development Section.
Recently I flashed an ICS ROM and had the mainver error every time I tried to revert back to Gingerbread. I finally fixed the mainver error and would like to update my phone to the latest Firmware AND Radio.
As far as I've read, in order for me to update my Firmware and Radio, I have to do a NAND Backup, relock my device, install the latest update via bootloader, and unlock again and restore my ROM. Though I've seen in other threads some people didn't need to relock their devices to install the latest update.
My questions are:
1) Do I need to flash a Stock Rooted ROM before I relock my phone to do the update? Because I've removed some bloatware from my current ROM.
2) Is there an easier method to Update my Firmware and Radio on my Rooted Rezound? If so, would someone like to provide me easy steps to doing so?
Any help would be much appreciated. Thanks in advance!
Click to expand...
Click to collapse
Here's a post of directions I made for someone else recently. Hope it helps.
Also, if you want to get back on Ineffabilis you can either restore a nand or flash it again without issue, then if you want to use the dsb kernel you will need to either 1) edit the android-info.txt file inside the dsb zip file or 2) flash it up to the point where it wants to "update", don't update, go to fastboot and copy out the boot.img from the dsb zip into your sdk folder and flash it from there. If you want to use Ineffabilis and the new stock kernel you'll need to flash the new kernel modules from here:
http://forum.xda-developers.com/showthread.php?t=1467793 since Ineffabilis has the old ones. *Unless they've updated the ROM, I haven't checked the last couple days.
fastboot flash boot boot.img
You'll then have to delete the PHzip file from your sd card.
Now back to getting the OTA update...
1) get the sdk working on your computer
2) On your phone, do a battery pull, then boot it into fastboot and then connect it to your computer.
3) Type the following at your computer's cmd prompt:
fastboot getvar all
and find out what mainver you are on.
* If you are on a mainver that starts with 3.x then you cannot run the RUUs. If your mainver starts with 1.x or 2.x then continue onto step 4.
4) Relock your phone by typing the following:
fastboot oem lock
5) Download the RUU for your mainver to your computer. Use the file from here that corresponds to your mainver:
http://www.filefactory.com/f/c2e320ee1d5c7886/
This is an exe file so just run it on your pc with your phone attached. I know you need to be locked, I think you need HTC Sync installed, so if it's not working search for those answers, it will work, others have done it. Now you are back to stock.
5) Unlock your phone again using the same unlock bin file you got before by putting it in the same folder you are now using for sdk. Type the following command:
fastboot flash unlocktoken Unlock_code.bin
If you don't have it obtain a new one by following the same steps you did before to get it originally. Here is a guide for that:
http://forum.xda-developers.com/showpost.php?p=20780879&postcount=1
Now you should be stock and unlocked.
6) Flash Amon Ra in fastboot. Get the lateset version, 3.13. here:
http://www.mediafire.com/?chpoxzb8bl4nn2b
Type the following command to flash it:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Now you should have Amon Ra on your phone.
7) Root your phone by installing su using Amon Ra. Go to the developer menu and find the option in there.
Now you should be stock, unlocked and rooted.
8) MAKE A NANDROID BACK UP NOW AND LABEL IT.
9) Flash a new ROM.
*** If your mainver is 3.x try this thread to see if you can come up with a method to go back to stock. I haven't looked into this since I have not ventured into ICS land as of yet.
http://forum.xda-developers.com/showthread.php?t=1459347
There are also some threads about getting back to stock from ICS I think so here are my search results for "stock ics" in the thread title and you can probably find an answer in there somewhere.
Here's another post I had made with an alternative method in it in case you have any trouble with the RUU:
ATERNATIVE METHOD:
You can also use con247's Stock OTA ROM instead of running the RUU.
http://forum.xda-developers.com/showthread.php?p=21880389
Here are the steps to take to accomplish that:
1) use Amon Ra to flash con's vigorStock OTA ROM. It will do its thing then reboot to hboot. I think it then asks you if you want to update. Don't do it yet.
2) At this point you want to relock. So go into fastboot on the phone. Using adb/fastboot type the following at the cmd prompt:
fastboot oem lock
3) Reboot phone and let it flash the PHzip file. It should reboot completely when it's finished.
4) delete the PHzip file using a file explorer app like ES File Explorer or Root Explorer.
5) get the phone back into fastboot. Unlock again using adb/fastboot. I don't remember the exact command but you can find that in the guide for unlocking.
6) reinstall su using Amon Ra.
Now you should be stock OTA rooted with the new goodies.
Check in Settings > About phone > Software info > More to see that you got all the new stuff.
Mahalo EmerikL and feralicious for your responses and help. I think I'm gonna give these instructions a shot over the weekend. The instructions you both provided were well written, now I just have to be able to actually do it without messing anything up, lol.
If I do need further assistance, I will definitely report back with my questions, lol.
Thanks,
Linda
feralicious said:
Here's a post of directions I made for someone else recently. Hope it helps.
Also, if you want to get back on Ineffabilis you can either restore a nand or flash it again without issue, then if you want to use the dsb kernel you will need to either 1) edit the android-info.txt file inside the dsb zip file or 2) flash it up to the point where it wants to "update", don't update, go to fastboot and copy out the boot.img from the dsb zip into your sdk folder and flash it from there. If you want to use Ineffabilis and the new stock kernel you'll need to flash the new kernel modules from here:
http://forum.xda-developers.com/showthread.php?t=1467793 since Ineffabilis has the old ones. *Unless they've updated the ROM, I haven't checked the last couple days.
fastboot flash boot boot.img
You'll then have to delete the PHzip file from your sd card.
Now back to getting the OTA update...
1) get the sdk working on your computer
2) On your phone, do a battery pull, then boot it into fastboot and then connect it to your computer.
3) Type the following at your computer's cmd prompt:
fastboot getvar all
and find out what mainver you are on.
* If you are on a mainver that starts with 3.x then you cannot run the RUUs. If your mainver starts with 1.x or 2.x then continue onto step 4.
4) Relock your phone by typing the following:
fastboot oem lock
5) Download the RUU for your mainver to your computer. Use the file from here that corresponds to your mainver:
http://www.filefactory.com/f/c2e320ee1d5c7886/
This is an exe file so just run it on your pc with your phone attached. I know you need to be locked, I think you need HTC Sync installed, so if it's not working search for those answers, it will work, others have done it. Now you are back to stock.
5) Unlock your phone again using the same unlock bin file you got before by putting it in the same folder you are now using for sdk. Type the following command:
fastboot flash unlocktoken Unlock_code.bin
If you don't have it obtain a new one by following the same steps you did before to get it originally. Here is a guide for that:
http://forum.xda-developers.com/showpost.php?p=20780879&postcount=1
Now you should be stock and unlocked.
6) Flash Amon Ra in fastboot. Get the lateset version, 3.13. here:
http://www.mediafire.com/?chpoxzb8bl4nn2b
Type the following command to flash it:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Now you should have Amon Ra on your phone.
7) Root your phone by installing su using Amon Ra. Go to the developer menu and find the option in there.
Now you should be stock, unlocked and rooted.
8) MAKE A NANDROID BACK UP NOW AND LABEL IT.
9) Flash a new ROM.
*** If your mainver is 3.x try this thread to see if you can come up with a method to go back to stock. I haven't looked into this since I have not ventured into ICS land as of yet.
http://forum.xda-developers.com/showthread.php?t=1459347
There are also some threads about getting back to stock from ICS I think so here are my search results for "stock ics" in the thread title and you can probably find an answer in there somewhere.
Here's another post I had made with an alternative method in it in case you have any trouble with the RUU:
ATERNATIVE METHOD:
You can also use con247's Stock OTA ROM instead of running the RUU.
http://forum.xda-developers.com/showthread.php?p=21880389
Here are the steps to take to accomplish that:
1) use Amon Ra to flash con's vigorStock OTA ROM. It will do its thing then reboot to hboot. I think it then asks you if you want to update. Don't do it yet.
2) At this point you want to relock. So go into fastboot on the phone. Using adb/fastboot type the following at the cmd prompt:
fastboot oem lock
3) Reboot phone and let it flash the PHzip file. It should reboot completely when it's finished.
4) delete the PHzip file using a file explorer app like ES File Explorer or Root Explorer.
5) get the phone back into fastboot. Unlock again using adb/fastboot. I don't remember the exact command but you can find that in the guide for unlocking.
6) reinstall su using Amon Ra.
Now you should be stock OTA rooted with the new goodies.
Check in Settings > About phone > Software info > More to see that you got all the new stuff.
Click to expand...
Click to collapse
Thank you feralicious. I'm actually gonna give this a shot today. But I have one more small question, the radio is also included in this RUU/OTA update, correct?
Another thank you for this one, this is going to be very helpful .
Sent from my ADR6425LVW using XDA App
EmerikL said:
Yes you can flash over CWM with Amon Ra.
In fastboot type fastboot oem lock. To unlock type fastboot oem unlock unlockrohen.bin
Sent from my VTAB1008 using xda premium
Click to expand...
Click to collapse
Hey emerikL,
I've already updated my radio and firmware to the latest versions. I was wondering, is it okay to still reflash Ineffabilis v1.0 with the latest update?
Yeah there isnt a pronlem with that i think. Just dont restore you nandroid over top of it. You'll need to do pretty much a clean install.
Sent from my VTAB1008 using xda premium
So I take it that I will not get to update my phone? I have the main ver 3.x.x, so that will mean the waiting game won't it?
vlen22 said:
So I take it that I will not get to update my phone? I have the main ver 3.x.x, so that will mean the waiting game won't it?
Click to expand...
Click to collapse
unless you hex your bootloader... I Downloaded the Official RUU .. locked the bootloader ran the update, unlocked... booted into android enabled debugging.. pulled that thing and changed my mainver down to 1.. sent the file back and rebooted
If your already on a mainver pass 3.602.11 (some****) then you need to find a way to flash the radio via a PH98IMG or hex your bootloader down and flash the RUU /OTA
Guess I have to deal with the stupid audio hiss then, until the real one comes out, thanks for your response.
vlen22 said:
Guess I have to deal with the stupid audio hiss then, until the real one comes out, thanks for your response.
Click to expand...
Click to collapse
No, you can get the OTA without editing your actual phone file.
There's a link to that in my lengthy post above. See the part where it says if you are on mainver 3.x, there's a link to a thread about dealing with that there. Also try searching using the terms "stock ics" and you should come up with threads about getting back to stock from 3.x mainver. I guess I forgot to paste my results in that post cuz I see I mentioned it.
Basically you need to edit a text file included in whatever package you are flashing OR you should be able to flash in fastboot without worrying about it. I successfully flashed a kernel in fastboot that had given me a mainver error when I tried to flash in recovery.
EmerikL said:
Nandroid backup
Flash radios via hboot
Relock
Flash kernel for ICS. You can find it in Nils kernel thread.
Unlock
Restore amon ra recovery
Reroot via amon ra
Restore nandroid.
That is ofcourse if you mainver is below or at 2.10. If not then you have to play that game again.
That is the short and sweet version. If you need more I can lay it out again in a more detailed way later tonight.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Sorry to post in another users topic but after I "relock" my phone wont boot it sits at white screen, adb reboot recovery just says waiting for devices and if I go to fastboot or try to open recovery I can not.
Sorry it should have been in this order:
Nandroid backup
Relock
Flash radios via hboot
Unlock
Flash kernel for ICS. You can find it in Nils kernel thread.
Restore amon ra recovery
Reroot via amon ra
Restore nandroid.
You are probably on the wrong kernel.
I'm on the 3.15 RUU with 2.09 HBOOT. I used dirty racun for s-off and am HTCdev unlocked obviously. I know I can't undo the HTCdev unlock.
In what order do I need to do these things to relock bootloader/unroot and restore to stock 3.15?
I'm thinking:
1.) Flash stock recovery image then flash stock 3.15 RUU.
2.) Relock bootloader
3.) profit?
4.) skip like a fairy
If I flash the stock RUU that will restore S-ON correct?
BTW, is there an active link for the stock JB 3.15? HTCruu is no more and that was the only place I knew.
Bueller?
Any feedback on where I can get the stock 3.15 RUU?
Stock Rooted 3.15.651 rom
heroisnotdead said:
Any feedback on where I can get the stock 3.15 RUU?
Click to expand...
Click to collapse
This is all I know for now, a stock, rooted rom. I'm trying to find the full RUU dot exe file. I have the link around here somewhere.
I was trying to post the link, and didn't notice at first, that I'm too new. I was going to spell out the URL, but didn't want to offend the moderators. I guess you can send me private message, if you want it. The link was sent to me by a senior member of xda, and member of dev team for a well-known rom.
See here for zips which include the files for rooting + the RUU exe's:
http://forum.xda-developers.com/showthread.php?t=2026938
When I was HTCdev unlocked and wanted to get back to stock ICS and take the OTA to get Jellybean, I followed the Youtube link at the bottom of that post to relock the bootloader. After that, I then ran the RUU from my computer. That brought my phone back to stock. (Then I took the OTA to Jellybean, unlocked again, and installed a new ROM, but that's not what you're looking to do, it sounds like)
1. Reboot into bootloader
2. Set phone to fastboot option
3. Connect phone to pc with adb folder already setup on computer (htc drivers etc).
4. Make sure computer says "fastboot usb"
5. Open command prompt from your adb folder
6. Type "fastboot oem lock"
7. Run 3.15.651.16 RUU exe file on computer and sit back.
Since you have 2.09 hboot then you're stuck using the 3.15 ruu file....hope that helps...let us know how it ended up.
Sent from my EVO using xda app-developers app
Thanks
Damn I'm blind. I've had that file the whole time and kept looking right over it due to the way I had files displaying. These RUU files will overwrite everything, including the recovery image, correct?
How I miss doing this stuff on nexus device, oh well.
heroisnotdead said:
Damn I'm blind. I've had that file the whole time and kept looking right over it due to the way I had files displaying. These RUU files will overwrite everything, including the recovery image, correct?
How I miss doing this stuff on nexus device, oh well.
Click to expand...
Click to collapse
Yea the ruu will overwrite EVERYTHING...it'll basically make your phone as if you just opened the box....only thing is to make absolutely sure you have the correct one that matches your current hboot....
Sent from my EVO using xda app-developers app
Ok, I have been away from the site and havent messed with my phone for over a year so I am really rusty but I want to flash to ICS. However after many hours today without success I have restored the GB. Hoping someone can give me some insight to my mistake as things have changed a far bit in a year.
I currently have Nils Business Sense Gingerbread and want to go flash Nils Business ICS 4.0.3 Sense. http://forum.xda-developers.com/showthread.php?t=1508118
I believe I followed direction as described on the above page but I could never get the recent RUU to install. Looking at the directions on the above thread post #3 "Latest RUU Leak and Installation Instructions" I can get it to step #6 but things fall apart there. It finds the PH98IMG.zip and scans it like the directions say but never prompts me to say "yes" as describes. It does have the progress bar on the right side that will complete and then returns to the bootloader screen but at no point does it actually go to the white HTC load screen. Is there something missing from the directions or could I have missed something?
The phone was unlocked thru HTC website over a year ago. I believe its s-off but dont remember and unable to figure out how to tell.
Thanks in advance. Mark
Okay, first of all, to check if you are s-off boot into bootloader and look up top. Around the 2nd or 3rd line I believe, it will say Vigor and either s-off or s-on in there.
If you are s-on you need to relock the bootloader in fastboot.
fastboot oem lock
If you didn't do that and you are s-on that's probably the issue.
I ran the RUU a week or so ago so I'm trying to remember exactly what happened.
I don't recall if it just automatically ran or if it asked me if I wanted to "update".
When you say you see a progress bar, do you see a list of items and does it say "updating" next to each item as it gets to it? Can you say exactly what is on the screen after it starts? Also you are using the latest global, 4.03.605.2?
After it makes a first pass it will go to a black screen for a couple minutes then back to bootloader to run again. Then you'll see the same screen with the list and "updating" next to each item.
Then it will boot back into bootloader and ask you if you want to reboot iirc. Or else it reboots itself but I think it asked me. Then you'll see a normal boot but it will take a while so just be patient.
Thanks for the quick reply.
No it never gets to the point of updating anything. I finds then scans the img, it has a blue completion bar on the right side of the screen when it is scanning. That will complete but it never updates anything and returns to the recovery screen. I even tried just loading the ROM without installing the RUU and it sat on the white HTC screen for an hour so clearly I have to update the RUU before I can flash Nils ROM.
Ok apparently I am S-on so need to relock bootloader.
Can you give me a little more details on how to do it. Guessing I'm not grasping fastboot oem lock.
Are you s-off or s-on? If s-on, did you relock first?
You might try running the 3.14.xxxxxx from here:
http://androidfiles.org/ruu/?dir=Vigor
It's an exe file so just double click it on the desktop and it will run.
Or you can give these commands in fastboot:
fastboot oem rebootRUU
fastboot flash zip NameOfZip.zip
Then if that works you can try the global again. Double the work, but unless someone else comes along with a solution it's something you can try while waiting.
mbrudolph said:
Ok apparently I am S-on so need to relock bootloader.
Can you give me a little more details on how to do it. Guessing I'm not grasping fastboot oem lock.
Click to expand...
Click to collapse
Okay, that's probably it then. Was writing my last post when you posted.
So power down the phone, pull the battery then put it back in and boot into bootloader. Switch to fastboot and connect to your pc.
Open up your command window and navigate to where you have your fastboot/adb folder (I attached what you need in case you no longer have it, just place the folder on the root of your pc so you would navigate to c:\android).
Then type
fastboot oem lock
That will lock you so you can run the RUU.
Afterwards you will need to unlock again. If you no longer have your unlock code you can get it again from HTCDev. If you go to their site it explains how.
http://www.htcdev.com/bootloader/
Once you receive your token put it in the "android" folder (or whatever the name of your folder you use for fastboot is).
Then type
fastboot flash unlocktoken Unlock_code.bin
I keep my android folder with the unlock token and latest Amon Ra recovery in there so I always know they're there if I need them.
Then you'll need to flash the newest AmonRa, it's up to 3.16 now.
Root ( didn't have to do anything, was already set to flash ROM)
Flash Nils' ROM.
Also, since you are s-on you will need to flash the kernel from the ROM after you flash the ROM. I don't know if he has it set to make a PH98IMG file or not - some ROMs create one on your sd card. If not, you need to pull it from the ROM, put it in the "android" folder and flash in fastboot. I would pull it out ahead of time in case so you're ready.
fastboot flash boot boot.img (or whatever the name of his kernel is)
Then you should be able to boot up and enjoy.
feralicious said:
Okay, that's probably it then. Was writing my last post when you posted.
So power down the phone, pull the battery then put it back in and boot into bootloader. Switch to fastboot and connect to your pc.
Open up your command window and navigate to where you have your fastboot/adb folder (I attached what you need in case you no longer have it, just place the folder on the root of your pc so you would navigate to c:\android).
Then type
fastboot oem lock
That will lock you so you can run the RUU.
Afterwards you will need to unlock again. If you no longer have your unlock code you can get it again from HTCDev. If you go to their site it explains how.
http://www.htcdev.com/bootloader/
Once you receive your token put it in the "android" folder (or whatever the name of your folder you use for fastboot is).
Then type
fastboot flash unlocktoken Unlock_code.bin
I keep my android folder with the unlock token and latest Amon Ra recovery in there so I always know they're there if I need them.
Then you'll need to flash the newest AmonRa, it's up to 3.16 now.
Root ( didn't have to do anything, was already set to flash ROM)
Flash Nils' ROM.
Also, since you are s-on you will need to flash the kernel from the ROM after you flash the ROM. I don't know if he has it set to make a PH98IMG file or not - some ROMs create one on your sd card. If not, you need to pull it from the ROM, put it in the "android" folder and flash in fastboot. I would pull it out ahead of time in case so you're ready.
fastboot flash boot boot.img (or whatever the name of his kernel is)
Then you should be able to boot up and enjoy.
Click to expand...
Click to collapse
Hey feralicious,
Been reading this and with my white screen issue, I have two questions.....first is like you I have an android folder where I keep the unlock token and amonRa recovery but mine is 3.15. Where can I get 3.16 from? I saw a thread with zip files but it said you had to be S-off and I am not.
My second question is what is file you attached here?
318sugarhill said:
Hey feralicious,
Been reading this and with my white screen issue, I have two questions.....first is like you I have an android folder where I keep the unlock token and amonRa recovery but mine is 3.15. Where can I get 3.16 from? I saw a thread with zip files but it said you had to be S-off and I am not.
My second question is what is file you attached here?
Click to expand...
Click to collapse
There's a link for 3.16 at the bottom of the Amon Ra thread in development. Not the attachments, the link right above those.
I attached the folder with the files needed to use fastboot/adb.
feralicious said:
There's a link for 3.16 at the bottom of the Amon Ra thread in development. Not the attachments, the link right above those.
I attached the folder with the files needed to use fastboot/adb.
Click to expand...
Click to collapse
Ok. I don't need those. I have adb all set. I will check that thread again. Any real difference in 3.16 vs 3.15?
318sugarhill said:
Ok. I don't need those. I have adb all set. I will check that thread again. Any real difference in 3.16 vs 3.15?
Click to expand...
Click to collapse
The only difference I know of is that 3.16 has a working root option.
Feralicious,
Just wanted to thank you again. Today, I finally got everything updated and working well. Couldn't have done it without your help.
THANKS!!! :highfive:
Mark
mbrudolph said:
Feralicious,
Just wanted to thank you again. Today, I finally got everything updated and working well. Couldn't have done it without your help.
THANKS!!! :highfive:
Mark
Click to expand...
Click to collapse
You're welcome! Glad I could help. :good:
I just got a warranty replacement a few days ago. I unlocked it via HTC method and flashed a recovery and all is fine. Flashed a few ROMs and was happy. I decided that I wanted to get S-OFF again tho, and to do that i need to be back on the stock ROM. So i went to flash the latest Verizon ICS OTA's RUU in the bootloader and it see's the zip file, scans it and then just goes to the main bootloader menu and gives me no option to flash. I haven't tried the global RUU because i wasn't sure I can do the S-OFF exploit on the global RUU. Is this normal? I did accept the little OTA verizon is pushing out now and i didn't think that did anything to the bootloader but i wouldn't really know. I have used this exact zip to revert back to stock very recently prior to getting the replacement. It worked fine always, and I would just rename it and leave in in the SDs root directory.
vonhinkle said:
I just got a warranty replacement a few days ago. I unlocked it via HTC method and flashed a recovery and all is fine. Flashed a few ROMs and was happy. I decided that I wanted to get S-OFF again tho, and to do that i need to be back on the stock ROM. So i went to flash the latest Verizon ICS OTA's RUU in the bootloader and it see's the zip file, scans it and then just goes to the main bootloader menu and gives me no option to flash. I haven't tried the global RUU because i wasn't sure I can do the S-OFF exploit on the global RUU. Is this normal? I did accept the little OTA verizon is pushing out now and i didn't think that did anything to the bootloader but i wouldn't really know. I have used this exact zip to revert back to stock very recently prior to getting the replacement. It worked fine always, and I would just rename it and leave in in the SDs root directory.
Click to expand...
Click to collapse
In order to RUU you need to relock your device on HTCdev.com if you still have you unlock_cod.bin file you can skip going to HTC dev and put it in you Android folder you created back when you first unlock. S-off will not be lost nor do you need to S-On to flash the RUU.
make sure you have the SDK and HTC Sync installed. Go to fastboot in bootloader connect your USB cable so its says fastboot usb. Open a command window in the Android folder where you have adb fastboot files. Easiest way is shift right click open command window here. Once your device is connected just type in the command fastboot oem lock this will relock your device and you can now RUU. Once that is over you need to re unlock using the unlock code.bin file from HTC DEV and then flash amon ra recovery using the fastboot flash recovery(name).img and then you may install roms as you please. double check those commands although I am 90 percent positive they are correct commcands. The process I have described is corecct though as I just did this last night to update my radios. Good luck hope this helps
Also rename to the correct file name with the global RUU PH98IMG.img
zkrp5108 said:
In order to RUU you need to relock your device on HTCdev.com if you still have you unlock_cod.bin file you can skip going to HTC dev and put it in you Android folder you created back when you first unlock. S-off will not be lost nor do you need to S-On to flash the RUU.
make sure you have the SDK and HTC Sync installed. Go to fastboot in bootloader connect your USB cable so its says fastboot usb. Open a command window in the Android folder where you have adb fastboot files. Easiest way is shift right click open command window here. Once your device is connected just type in the command fastboot oem lock this will relock your device and you can now RUU. Once that is over you need to re unlock using the unlock code.bin file from HTC DEV and then flash amon ra recovery using the fastboot flash recovery(name).img and then you may install roms as you please. double check those commands although I am 90 percent positive they are correct commcands. The process I have described is corecct though as I just did this last night to update my radios. Good luck hope this helps
Also rename to the correct file name with the global RUU PH98IMG.img
Click to expand...
Click to collapse
AHHHHH, i thought i needed to be unlocked to flash an RUU. THANKS!
No problem my friend.
Sent from my ADR6425LVW using xda app-developers app
So I've explored different options on XDA's site for returning to stock and I guess this is why I'm here. I screwed the hell up. I posted this on Phaded's How-To page, but I figured it would also be best to post this in the general Help & Troubleshooting page.
Here's the best way I can explain my issue. Someone please help.
1. My phone is COMPLETELY formatted. No OS now. Zero data.
2. TWRP is installed as my recovery.
3. I can fastboot and adb (only from the recovery obviously)
4. I moonshined the phone in order to S-Off
5. I tried the method to remove S-Off by Phaded
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Click to expand...
Click to collapse
When I ran the RUU, I got that error 158 problem. I couldn't flash the HBOOT. downloaded it several times and tried.
6. I flashed it with an AOSP rom and tried the RUU again. No luck.
Now I'm stuck. u_u I tried
adb push "file name" "file directory"
Click to expand...
Click to collapse
so I can drop a zip file in the phone, but it seems to not work. Idk if I did it right. I was hoping to flash a ROM by doing that. smh.
Let me know if there's any other info I can provide. Considering the phone still turns on and I can still get to fastboot and adb, I don't think I'm a lost cause.
Thanks everyone!
UPDATE
I sideloaded a ROM (Carbon) and now I'm up and running. But I still can't RUU it! Figured this detail will help.
I'll keep reading and researching, posting my progress.
Thanks!
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
xlxcrossing said:
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
1. I obtained s-off with moonshine. I used the above command suggested by Phaded and when I put in
fastboot oem lock
Click to expand...
Click to collapse
(or something like that) it says my phone is locked.
2. What do you mean what bootloader? I guess moonshine, cause that's what comes up when I go to my bootloader screen.
3. I trying flashing the ruu and I get this (see image attached) which the suggested fix for error 158 was to flash the hboot 1.15 (or something). But I can't seem to flash it correctly. I can't even find straight forward instructions on how to do it.
Thanks for responding.
The reason I asked about the bootloader version and I'm not 100% sure about this so someone else may need to chime in is that when you ruu you are flashing firmware which includes hboot so if you upgraded hboot before doing s-off or otherwise went up a version then I'm pretty sure the ruu won't downgrade your hboot airgo the error message. Again this might not be true. At this point all that matters is that your s-off and NOT bricked so instead of toying with an ruu I would choose a stock Rom .zip to flash if its truly stock that you want. Your firmware should be up to date if you took 2.06. There is no ruu for 2.06.
Sent from my HTC6435LVW using Tapatalk 4 Beta
What is s-off?
Sent from my Galaxy Nexus using xda premium
93fuelslut said:
What is s-off?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
xlxcrossing said:
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
Click to expand...
Click to collapse
I'm not finding a solid explanation for error 158 which is disheartening - the best offerings are to change USB ports or restart the ruu. Like I said before you are fine on the software end, you can verify you have up to date firmware by comparing the latest below with what you have.
Baseband (radio) 1.01.04.0308
PRI 2.44_002
As for the hboot, how are you trying to flash it? In recovery?
The hboot needs to match the RUU. You need to find the original hboot . It is in a thread with hboot versions and radio versions.
Link to HBOOT please? and answering your questions
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was:
fastboot flash "file name.zip"
Click to expand...
Click to collapse
and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Moonshine isn't working because you are still s-off.
My thread has the original hboot and instructions to flash it. You do not flash in recovery. You do not put it on your phone at all. Do not push the file in recovery. Read and follow the instructions in the stock thread.
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
You're doing the command wrong or you renamed it PL83IMG.zip.zip
Please, go in my thread, read each step perfectly and follow. It's really quite simple.
Difference
Is s-off/s-on and being locked/unlocked two different things?
Screenshot
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Strike.
From my S-Off BadSeed DNA
ibthevivin said:
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
Click to expand...
Click to collapse
You need to cd to the directory the file is in, which should be where fastboot.exe is
So if it's in say C:\sdk\
Type cd C:\sdk\
Then run command to fastboot
BOOM!
Alright. Worked. I'll keep you all posted. No one really mentioned in any of the tutorials and how-to's that it is VERY important to make sure to CD to the directory. Like there are developers who say just add it to the PATH in Environment Variables. I figured it was enough, but hey, I was wrong.
Live and learn right?
Thank you Phaded.
So basically my problem was, calling the hboot.zip file is not included under Environmental Variables. I have to intentionally CD to that directory.
Hmm, I must have missed putting in the cd step for the hboot. I'll go edit it.