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.
Related
I've looked around so far and can't really find any topics with updated radios for the Rezound. Can anyone point me In The right direction? Sorry if I just happened to miss any threads on this issue. And if it matters I'm running CleanROM ICS 2.3
Sent from my ADR6425LVW using xda premium
YoU need to relock it, ruu and then take the Verizon OTA update.
jmorton10 said:
YoU need to relock it, ruu and then take the Verizon OTA update.
Click to expand...
Click to collapse
Ah..... I see..... Guess we gotta wait for S-Off to do it with the phone itself. When you say ruu what do you mean. I have no clue what that is.
Sent from my ADR6425LVW using xda premium
dalvear88 said:
Ah..... I see..... Guess we gotta wait for S-Off to do it with the phone itself. When you say ruu what do you mean. I have no clue what that is.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
RUU will return you to stock. It's an exe file you run on your pc. Here's a lengthy post I made for someone else earlier today with instuctions:
p.s. I looked up that ICS Rom and it says "Updated: Mainver to 2.01.605.11" so you should run the RUU with that mainver number in the file name.
feralicious said:
Everything you need can be found in these Rezound forums.
So you can get into fastboot. That's good.
Do you still have your computer set up from when you unlocked the phone? If not, download the mini sdk that MrSmith317 made that I've attached and place that in the C: directory of your computer and name it something easy, mine is named android-flasher. Then just always keep it there as you will need to use it often when modding your phone.
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. I will try to find out what you should do in that case. 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.
Hope this helps you get back up and running.
Click to expand...
Click to collapse
I'm struggling with all the terminology and methods with flashing. Basically I just wanted root, so I read several different guides and got a rooted status and managed to install the Amon Ra recovery. However my bootloader (also called HBOOT - is that correct?) shows tampered / unlocked now. Basically, I want to flash back to the most current build and try again.
Would the link on the Android Police forums to download RUU 4.03.605.2 be latest Verizon build as if it were fresh out of the box?
I checked on the wiki, but didn't see anything for the Rezound there.
Also, to use this utility, I relock my bootloader using HTCDev and then move this zipped file to my sd card and reboot to the bootloader either using adb or the power + volume down, correct? It will see the zip file and begin flashing or do I run an executable from my PC with the phone connected? I'm not S-Off because I figured that is way above my head at this point.
I appreciate any help anyone can offer.
The tampered just means you have a custom recovery like Amon Ra installed.
Sent from my ADR6425LVW using xda app-developers app
oatlord said:
I'm struggling with all the terminology and methods with flashing. Basically I just wanted root, so I read several different guides and got a rooted status and managed to install the Amon Ra recovery. However my bootloader (also called HBOOT - is that correct?) shows tampered / unlocked now. Basically, I want to flash back to the most current build and try again.
Would the link on the Android Police forums to download RUU 4.03.605.2 be latest Verizon build as if it were fresh out of the box?
I checked on the wiki, but didn't see anything for the Rezound there.
Also, to use this utility, I relock my bootloader using HTCDev and then move this zipped file to my sd card and reboot to the bootloader either using adb or the power + volume down, correct? It will see the zip file and begin flashing or do I run an executable from my PC with the phone connected? I'm not S-Off because I figured that is way above my head at this point.
I appreciate any help anyone can offer.
Click to expand...
Click to collapse
4.03.605..2 is the latest vzw build.
jbh00jh said:
4.03.605..2 is the latest vzw build.
Click to expand...
Click to collapse
If I want to load that RUU, do I have to relock my bootloader? Will I be able to load the file from the Android Police forum without being S-OFF since I've rooted and loaded a recovery?
oatlord said:
If I want to load that RUU, do I have to relock my bootloader? Will I be able to load the file from the Android Police forum without being S-OFF since I've rooted and loaded a recovery?
Click to expand...
Click to collapse
Having S-OFF negates the need to relock your bootloader.
You should be able to flash the "RUU" zip file with your phone in its current condition.
If you do some research in this section in the S-OFF threads, you'll get some good info about not re locking after s-off.
Re-locking is only necessary if you don't have s-off.
Sent from my ADR6425LVW using Tapatalk 2
to reinstall the RUU, first make sure you have fastboot on your PC and your phone is in the fastboot menu of the bootloader and connected to your PC. It should say "fastboot USB". (If you don't have the HTC drivers installed, download HTC Sync 3.0 and that should install it. I haven't gotten it to work on Windows 8 so if you use Windows 8 use these drivers)
Open a command prompt, change the directory to where your fastboot.exe is (example: cd c:\fastboot_directory). Type in 'fastboot oem lock'. Your phone will restart, then boot up. Turn it off, reboot to the bootloader and make sure it says *RELOCKED* on the top. Then, go back to fastboot and in your cmd window, type in 'fastboot oem rebootRUU'. Your phone will reboot and show a black screen with a grey HTC logo. Copy the RUU (doesn't matter if it's named PH98IMG.zip or something else) into the same folder as fastboot.exe and type in 'fastboot flash zip ruu_zip_name.zip' (obviously replacing ruu_zip_name.zip with the zip's actual name). The terminal will start sending the zip and details will be displayed on your computer screen. Your phone will also have a progress bar. Once the terminal on your computer says it's finished, you can reboot your phone.
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Yes, you can use the above method fine. However, going S-Off is very easy. It seems like a daunting task, but if you read the directions thoroughly it is very easy. I used the .5 version of Juopunutbear and it worked without a hitch. You are already unlocked and rooted, so if you S-Off, you won't have to do it all over again. From there you can flash the RUU, flash a FLASHABLE version of AR 3.15, then reflash any rom that you want. You will only get the benefit from global with roms that are built aroung the .2 base, but you will get updated radios. I haven't honestly noticed much of a difference with the new radios though.
layneja said:
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Click to expand...
Click to collapse
Flash stock recovery here's a link http://www.mediafire.com/?wb21d2gdurui2c6 then lock bootloader. (Fastboot OEM lock)
After locking bootloader(cuz your s-on) rename the ruu you downloaded from android police To PH98IMG put on your sd return sd phone boot into bootloader run update, if it stops and powers off mid update remove battery and start it again, It flashed the hboot first then you gotta go back In And finish the update.
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
---------- Post added at 11:41 AM ---------- Previous post was at 10:59 AM ----------
layneja said:
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Click to expand...
Click to collapse
Also to avoid any problems do a factory reset in hboot after update is installed. Being that we're s-on when we re-unlock it does it for us but I've heard some people are having problems after the ruu if they didn't FDR while on stock recovery.. just a heads up
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
famouscollin said:
Flash stock recovery here's a link (removed cause I'm too new) then lock bootloader. (Fastboot OEM lock)
After locking bootloader(cuz your s-on) rename the ruu you downloaded from android police To PH98IMG put on your sd return sd phone boot into bootloader run update, if it stops and powers off mid update remove battery and start it again, It flashed the hboot first then you gotta go back In And finish the update.
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
---------- Post added at 11:41 AM ---------- Previous post was at 10:59 AM ----------
Also to avoid any problems do a factory reset in hboot after update is installed. Being that we're s-on when we re-unlock it does it for us but I've heard some people are having problems after the ruu if they didn't FDR while on stock recovery.. just a heads up
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
Click to expand...
Click to collapse
Just to clarify: when you reboot using "adb reboot" or power + volume down, are you booting into the bootloader or hboot? I've read the guides but still a little confused there.
Also, what does the stock recovery do versus something like Amon Ra? Does the stock recovery allow for creating backups and what-not? Sorry to be a total noob here. I can bake cookies or something for you all for your help, hehe.
WookieFan said:
Having S-OFF negates the need to relock your bootloader.
You should be able to flash the "RUU" zip file with your phone in its current condition.
If you do some research in this section in the S-OFF threads, you'll get some good info about not re locking after s-off.
Re-locking is only necessary if you don't have s-off.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
if you're s-off you shouldn't have to unlock.
---------- Post added at 07:17 PM ---------- Previous post was at 07:11 PM ----------
oatlord said:
Just to clarify: when you reboot using "adb reboot" or power + volume down, are you booting into the bootloader or hboot? I've read the guides but still a little confused there.
Also, what does the stock recovery do versus something like Amon Ra? Does the stock recovery allow for creating backups and what-not? Sorry to be a total noob here. I can bake cookies or something for you all for your help, hehe.
Click to expand...
Click to collapse
The bootloader is the hboot. You power on holding vol down to get there.
The stock recovery does not allow you to create backups, or do much at all I'm pretty sure. That is why we have custom ones.
If i helped throw me a thanks
iamwalterwhite said:
Yes, you can use the above method fine. However, going S-Off is very easy. It seems like a daunting task, but if you read the directions thoroughly it is very easy. I used the .5 version of Juopunutbear and it worked without a hitch. You are already unlocked and rooted, so if you S-Off, you won't have to do it all over again. From there you can flash the RUU, flash a FLASHABLE version of AR 3.15, then reflash any rom that you want. You will only get the benefit from global with roms that are built aroung the .2 base, but you will get updated radios. I haven't honestly noticed much of a difference with the new radios though.
Click to expand...
Click to collapse
Do you mean flash the RUU in the bootloader and then the recovery also in bootloader? i only ask cause im at school and i forgot my microsd adapter so i cant rename the zips so that I can flash both of them from there, but if i can do it from recovery then im set
xxtsxx said:
Do you mean flash the RUU in the bootloader and then the recovery also in bootloader? i only ask cause im at school and i forgot my microsd adapter so i cant rename the zips so that I can flash both of them from there, but if i can do it from recovery then im set
Click to expand...
Click to collapse
Sorry that you never got an answer to this. Yes, you should flash both recovery (stock) and the RUU as PH98IMG zip files. Wait to start this process until you have a pc/sd card reader available. Trying this without those basic tools is going to make this a frustrating process for you.
Sent from my ADR6425LVW using Tapatalk 2
-DISCLAIMER: DO THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY DAMAGE THIS GUIDE CAUSES YOU TO DO. THIS WORKED FOR ME, BUT RESULTS MAY VARY.-
-PLEASE READ THE ENTIRE GUIDE BEFORE FOLLOWING ANY STEPS TO AVOID ANY CONFUSION-
-THIS GUIDE ONLY APPLIES IF YOU ARE ROOTED WITH S-OFF ON HBOOT 1.58-
-IF YOU HAVE INSTALLED THE ICS OTA UPDATE THEN YOU SHOULD HAVE HBOOT 1.58, UNLESS YOU HAVE DOWNGRADED.-
-IF YOU HAVE DOWNGRADED YOUR BOOTLOADER AND ARE NOT ON HBOOT 1.58, LEAVE THIS PAGE-
-I ALSO RECOMMEND THAT YOU HAVE TWO SEPARATE SD CARDS YOU CAN USE FOR THIS. NO DATA WILL BE DELETED OFF OF EITHER-
-KEEP IN MIND, THAT IF YOU DO THIS, YOU MAY NOT BE ABLE TO BOOT BACK INTO YOUR STOCK ICS ROM FROM THE OTA UPDATE-
-YOU WILL ALSO NEED A MICRO SD CARD READER TO PLUG YOUR SD CARD STRAIGHT INTO YOUR COMPUTER-
If you are not rooted, and do not have S-OFF, check out this guide by crimsy. It has all the instructions you need to root and obtain S-OFF. It worked for me.
Now for the fun part. You're positive you're on HBoot 1.58, and you're getting bootloops when you flash roms. The fix is actually quite simple.
First, go to this thread by mpgrimm2
Scroll down until you see a post on the thread by ramjet73. This post contains a list of HBoot downloads. These are all free.
First, find the one that says "PG86IMG_JBear_1.58.5858_hboot_Sprint_ICS.zip". Download that to use as a backup.
Now, we're gonna go by exactly what I did. But I recommend you do your own research on which Hboot is the best for whatever ROM you're trying to flash.
First off, all of these are already S-OFF, so you wont need to redo the wire trick.
Anyway, I downloaded the first one on the list, "PG86IMG_1.40-hboot.zip".
Now, to install this, you're pretty much gonna trick your phone into "updating" to it.
To do this, just download the HBoot you've chosen to be the best for you (in my case it was the first one on the list, 1.4).
Now just rename that file to "PG86IMG" without quotation marks.
Next, copy it to the root of your SD card.
The rest takes place on your phone. Power off your phone, and boot into the bootloader (Hold volume down + power button).
If you've done the previous steps correctly, your bootloader should detect the HBoot you downloaded, and ask if you want to update.
Volume up= Yes
Volume down = No
If you're positive about this, then choose "Yes".
It should update and tell you to reboot.
This is where I ran into a problem. I was still running stock ICS from the OTA update, and I got stuck in a bootloop. My phone would freeze at the the Sprint animation, turn off, and repeat. I thought I could just disregard it, boot into recovery, and flash my new ROM. But every time I booted into the bootloader all I could do was either update or reboot. This is where that micro SD card reader comes in. Just pop your SD card into your computer, and remove the HBoot you downloaded. Then put your SD card back in your phone and try rebooting into the bootloader again.
If it boots into your bootloader as normal, then that should be it. You should be on whatever HBoot version you chose to download (this worked for me with 1.4)
Now try flashing that ROM again and let me know how it goes.
Keep in mind, different ROMS may have different results. You may still need to flash certain kernals or wipe specific partitions as instructed by the developer of the ROM you want to flash.
Feedback is appreciated.
I prefer to put the PG86IMG file on my sd card while booted up normally. Then reboot straight into recovery bypassing the hboot screen. Wipe, flash rom then boot into bootloader and run the update. This prevents getting bootloops and keeps you from having to use the computer to rename or remove the file. Saves you some work!
Sent from my PG86100 using Tapatalk 2
If you are S-OFF you can also flash a different bootloader from fastboot on a PC avoiding the need to deal with the PG86IMG.zip file at all, then boot directly into recovery from the new bootloader. See my post here for alternative methods to flash a new bootloader when S-OFF, including multiple ways to delete the the PG86IMG.zip file when flashing one from the current bootloader.
ramjet73
Theres also
fastboot oem rebootRUU
fastboot flash zip PG86IMG.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
enter recovery & clear cache then reboot.
I believe this is the fastest way to flash a different hboot
iTzLOLtrain said:
I believe this is the fastest way to flash a different hboot
Click to expand...
Click to collapse
If you look at the guide I linked in my previous post which has similar instructions that I took from the unlimited.io website and tested, you can do this fastboot sequence to clear cache, flash a different bootloader, then reboot back to your current ROM:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip new_hboot.zip
fastboot reboot
Click to expand...
Click to collapse
The hboot filename can be anything you want, and doesn't necessarily have to be "PG86IMG.zip" using this method.
If you need to flash another ROM before the reboot or do something else in recovery, you can issue the "fastboot boot recovery.img" command instead of "fastboot reboot" to go directly to your custom recovery since there is no "fastboot reboot-recovery" command.
ramjet73
ramjet73 said:
The hboot filename can be anything you want, and doesn't necessarily have to be "PG86IMG.zip" using this method.
Click to expand...
Click to collapse
I know.. & because this thread is about bootloaders I thought that's how I would explain myself. Instead of going into more detail & say how you can flash .img files through that process....
iTzLOLtrain said:
I know.. & because this thread is about bootloaders I thought that's how I would explain myself. Instead of going into more detail & say how you can flash .img files through that process....
Click to expand...
Click to collapse
That's fine.
For clarification, the command I suggested to get back to recovery (fastboot boot recovery.img) is not flashing it, only booting it directly to avoid having to go to the bootloader first to get to recovery.
ramjet73
Guys, I made this guide because it seemed like the most basic and simple way to do it. I speak from experience when I say that the command prompt can be a little intimidating. It can be get pretty nerve wrecking when you dont have a back up phone and you feel like you have lots of room for error and you're terrified you might brick your device. This guide doesn't use any sort of external commands, making it seem a lot less manual. I wasn't trying to show people the fastest way. Just the easiest, less nerve wrecking way.
sawyerbenjamin said:
Guys, I made this guide because it seemed like the most basic and simple way to do it. I speak from experience when I say that the command prompt can be a little intimidating. It can be get pretty nerve wrecking when you dont have a back up phone and you feel like you have lots of room for error and you're terrified you might brick your device. This guide doesn't use any sort of external commands, making it seem a lot less manual. I wasn't trying to show people the fastest way. Just the easiest, less nerve wrecking way.
Click to expand...
Click to collapse
The guide I linked in post #3 of this thread provides alternatives for flashing a different bootloader and for deleting the PG86IMG.zip file if you choose that method. Some people are very comfortable with the fastboot commands and that method saves having to worry about deleting the PG86IMG.zip. It's always good to have alternatives because one size never fits all.
You asked for feedback in the OP and we're providing that.
ramjet73
ramjet73 said:
The guide I linked in post #3 of this thread provides alternatives for flashing a different bootloader and for deleting the PG86IMG.zip file if you choose that method. Some people are very comfortable with the fastboot commands and that method saves having to worry about deleting the PG86IMG.zip. It's always good to have alternatives because one size never fits all.
You asked for feedback in the OP and we're providing that.
ramjet73
Click to expand...
Click to collapse
Feedback - Information about reactions to a product, a person's performance of a task, etc., used as a basis for improvement.
You were promoting your own threads, not giving feedback. I have to thank you for the post that helped in making this guide, but your alternate methods aren't really necessary. I'm not sure how to say that without sounding rude or hostile, but Im sure you get my point.
sawyerbenjamin said:
You were promoting your own threads, not giving feedback. I have to thank you for the post that helped in making this guide, but your alternate methods aren't really necessary. I'm not sure how to say that without sounding rude or hostile, but Im sure you get my point.
Click to expand...
Click to collapse
OK, and if you want to be blunt my point was that your guide wasn't really necessary, and I think that's feedback on your "product", since the content was already covered in the guide I setup for people that want to change bootloaders when S-OFF, but if people prefer to use your version in the OP of this thread that's fine with me.
As I already stated, alternatives are good.
ramjet73
ramjet73 said:
OK, and if you want to be blunt my point was that your guide wasn't really necessary, and I think that's feedback on your "product", since the content was already covered in the guide I setup for people that want to change bootloaders when S-OFF, but if people prefer to use your version in the OP of this thread that's fine with me.
As I already stated, alternatives are good.
ramjet73
Click to expand...
Click to collapse
Ouch. That was uncalled for. To far bro. This is just a guide trying to help people. Not a place to get all ugly. Lol.
Dear sir
i have the same problem my phone get stuck on white htc screen
unrooted
s-on
relocked
hboot 1.5.0007
so can any one help me how to solve this problem
thanks
i also tried factory reset and to setup ICS ruu but it got stop when it try to reboot boat-loader and still the same problem
when trying to flash any thing recovery or boot failed and trying to put rom as pg86img also failed any one help me please this phone part of my daily life:crying::crying::crying:
The problem with s-on is that the kernel does not flash when you flash a rom. That is why it won't boot.
To fix the issue after flashing a rom, you need to pull the boot.img from the rom.zip and use fastboot to flash it.
fastboot flash boot boot.img
There are two options when you are s-on and flashing roms to flash the kernel with the rom and avoid bootloop.
The no pc method:
The easiest method is to use 4ext recovery with smart flash enabled. That will allow you to flash roms and kernel and avoid bootloop.
The PC method:
Keep a recovery.img in your fastboot directory. When you want to flash a rom, boot your recovery into the phones memory which allows you to flash the kernel with the rom.
You use: fastboot boot recovery.img
Then just install the rom once booted into recovery. While it seems the same, Booting into recovery using fastboot is different and will allow the kernel to flash.
I am currently S-on and I have not been able to successfully flash any new ROM at all. I have tried several times to do a super wipe, flash the new ROM and Gapps but I get stuck in a boot loop and I can't quite figure out the problem. Never had this problem flashing any ROM or even updating my RUU so I am puzzled as to where these issues are coming from. Any insight would be greatly appreciated. I am not complaining about me being there is a very stable rom but I would not mind upgrade to 4.2 or 4.3 and maybe a different ROM. Oh and I'm using TWRP 2.63 I believe is the newest.
Sent from my EVO using Tapatalk 4
hillje1 said:
I am currently S-on and I have not been able to successfully flash any new ROM at all. I have tried several times to do a super wipe, flash the new ROM and Gapps but I get stuck in a boot loop and I can't quite figure out the problem. Never had this problem flashing any ROM or even updating my RUU so I am puzzled as to where these issues are coming from. Any insight would be greatly appreciated. I am not complaining about me being there is a very stable rom but I would not mind upgrade to 4.2 or 4.3 and maybe a different ROM. Oh and I'm using TWRP 2.63 I believe is the newest.
Sent from my EVO using Tapatalk 4
Click to expand...
Click to collapse
Because you are s-on you have to fastboot flash the kernel/boot.img then flash the rom
Look here to fastboot flash kernels/boot.img while s-on
http://forum.xda-developers.com/showthread.php?t=2256478
okay I will definitely try that, was there a point in time when this method change because I have always been S-on
never had to flash and that particular order?
lol in response to the attached photo I am still S-On because my phone would not take the dirty raccoon S off flas.
but lately my phone has been completely spazzing out on me it will do random lock ups and start swyping characters, in opening and closing menus without me pressing any buttons I almost feel like it is on its last leg. Not to mention random shut offs with black screens but still powered on if that makes sense. Normally when that happens it'll get stuck in a boot loop and I'll have to restore a previous backup... #itsucks
hillje1 said:
okay I will definitely try that, was there a point in time when this method change because I have always been S-on
never had to flash and that particular order?
lol in response to the attached photo I am still S-On because my phone would not take the dirty raccoon S off flas.
but lately my phone has been completely spazzing out on me it will do random lock ups and start swyping characters, in opening and closing menus without me pressing any buttons I almost feel like it is on its last leg. Not to mention random shut offs with black screens but still powered on if that makes sense. Normally when that happens it'll get stuck in a boot loop and I'll have to restore a previous backup... #itsucks
Click to expand...
Click to collapse
Some roms have kernel installers for s-on folks MeanBean being one of those roms.
As for s-off DirtyRacun may not be your only option tell me your baseband number.
The spazzing out sounds like a similar problem my buddy was having, he was s-off I ran an RUU and he says it sems to have fixed the problem.
bigdaddy619 said:
Some roms have kernel installers for s-on folks MeanBean being one of those roms.
As for s-off DirtyRacun may not be your only option tell me your baseband number.
The spazzing out sounds like a similar problem my buddy was having, he was s-off I ran an RUU and he says it sems to have fixed the problem.
Click to expand...
Click to collapse
Baseband 1.12.11.1119
hillje1 said:
Baseband 1.12.11.1119
Click to expand...
Click to collapse
Good news you can use FacePalm if you want assistance PM me I'll help you out
bigdaddy619 said:
Good news you can use FacePalm if you want assistance PM me I'll help you out
Click to expand...
Click to collapse
What is facepalm?
It's an s-off exploit
http://forum.xda-developers.com/showthread.php?t=2163013
Facepalm
bigdaddy619 said:
It's an s-off exploit
http://forum.xda-developers.com/showthread.php?t=2163013
Click to expand...
Click to collapse
Are you still able to help me get S-Off with my device. Hopefully that'll fix the issues I mentioned before b/c this is getting ridiculous!
Do you have ADB & Fastboot set up on your computer? If not, look here. This is a small file and the setup is very easy. You may also want to install HTC Sync on your computer so your drivers are up to date. Once you've done this you need to go to the Facepalm thread that Bigdaddy provided a link to previously. In the first post, there are two files to download, the modified boot.img and signed firmware. Download both of these and place them in your ADB-Fastboot folder (if you downloaded and installed the one I linked above, it should be named android-tools). Once you've done this, connect your computer and phone via USB cable. Use your mouse curser and place it on the android-tools folder, then press Shift+right click on the mouse, then select the option to open a command window. Type the following command:
Code:
adb devices
The serial number of your phone should be output on the line below. If not, you might need to change the device type in the notification pull-down on your phone from sync manager to disk drive. Once you're able to successfully run the adb devices command, you are ready to start.
Type:
Code:
adb shell
press enter, then type:
Code:
su
and hit enter. Once you've done this, you can run the command to gain SuperCID on your device. The easiest thing to do is copy the command from the line below and paste it into the command terminal. The command is:
Code:
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
Hit enter. Once you've done this, you can begin at step 1, which will reboot your phone to the bootloader. To verify that you've got SuperCID, you should see a line underneath your Hboot version that says something like "CID-22222222". If so, you're ready to move on to step 2, making sure that you're connected via Fastboot USB mode. Just follow the commands in the Facepalm thread and you should be good to go. If after you're done your phone doesn't reboot, simply press the power button to start the phone. You can reboot to the bootloader once the phone powers on to confirm that you're S-off. Also, once you're done gaining S-off, I recommend deleting the two files you downloaded from your android-tools folder to prevent any issues in the future.
Please help. I have unlocked this phone through HTC Dev. I have flashed a custom recovery. Somewhere through this process, the original installation of the factory rom from VM was deleted. That doesn't bother me because I was never going back to it anyway, but If I had it right now, I wouldn't be here. I have tried to use the RUU exe in fastboot and the RUU zip in recovery from here. Neither will install, exe throws errors and the zip returns [bad]. I have also tried the [ROM] NegaLite-BluRom-JCFunk | 2.95 | Sprint/VM | Sense/Apex/Nova | 03/25/2014. This eventually installed, but will not boot even with installing boot.img separately. I followed all directions to the best of my ability, but by no means am I saying I did correctly, but I am pretty sure I did. So to recap - I have whats in the title, but no rom whatsoever installed that can be accessed. Any takers?
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Click to expand...
Click to collapse
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
oD33z said:
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
D33z
Click to expand...
Click to collapse
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Click to expand...
Click to collapse
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
oD33z said:
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
Click to expand...
Click to collapse
here's the thread
http://forum.xda-developers.com/showthread.php?t=2831444
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I am great with linux, but was under the assumption it needed to be burned to cd and that USB was not an option, please advise if not the case. I have read a ton and I remember reading about Unknownforce, but cant remember if thats the case or not.
Off topic: I learned from you that it has to be locked to go stock, but does it need to be unlocked to flash your rom or locked as well?
Unlocked for custom, locked for stock.
Here is unknownforce ultimate tool,
there was a live cd version made for windows users scared of linux.
I use tiny core linux for this, Ubuntu tries to mount all the partitions and you only have a 5 second window when they are writeable. I have used Ubuntu, at first, but preferred tinycore.
But first you are going to need to get stock.zip to install.
http://forum.xda-developers.com/showthread.php?t=1653777
I would do fastboot boot recovery.img
Then install negalite, so atless you can boot the phone
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
---------- Post added at 12:37 AM ---------- Previous post was at 12:24 AM ----------
here is 4ext recovery I would use this one first until you get used to things, best recovery for 3d.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
oD33z said:
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
Click to expand...
Click to collapse
did you fastboot boot?
There are several custom recoveries out there.
Here is thread for 4ext
http://forum.xda-developers.com/showthread.php?t=1408936
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
What I meant was, in your opinion, is the 4ext a better recovery than the unofficial TWRP?
During the install of Negalite at the point of -Setting Up Kernel Over-Clock Settings
under this it reads: assert failed: write_raw_image("/tmp/newboot.img","boot")
Is this a red flag of something not going right in any way?
After this I click Next>Recovery>Wipe Dalvik>Reboot and it boots into Fastboot. Whats happening at this point?
Since I am basically starting from scratch and the end goal is to have a kitkat rom and possibly S-OFF(if its a must to do so).
What all needs to be done as far as formatting, tweaks, or anything else to achieve the best performance, space, or anything you can think of?
Thats if you dont mind sharing. I appreciate your time and if I can be of service to you in any way, I will.
I am currently on the 4ext recovery with 1GB sd-ext 0 swap and formatted Ext4.
fastboot boot recovery.img
flashrom.zip from recovery
reboot, wipe dalvik, reboot
Negalite.zip installed with no errors whatsoever.
Thank You.
Beautiful smooth running rom btw.
Does all that above sound like I did the right things as for setting up and installing?
4ext is most stable, the unofficial has new features like f2fs and selinux, but 95% stable.
fastboot boot recovery.img is an old work around, also used to flash boot.img with fastboot. That is ok with roms that include a whole boot.img but roms like mine use a dynamic boot.img. Basically the installer makes the boot.img using your choices.
From what I know about Kitty kat I think you need to downgrade hboot or be s-off. Not sure I've stayed on ics for stability because I still use this phone. Also there is a new version of negalite on svn, just takes hours for me to upload a zip version.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Revision 7
Are you sure this is the latest?
oD33z said:
Revision 7
Are you sure this is the latest?
Click to expand...
Click to collapse
Lol, yes since I updated it a few weeks ago
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
I should have worded that different really, the revision numbers threw me, I honestly was just making sure I was in the right place. 48mb smaller, anything stripped?
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Click to expand...
Click to collapse
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
oD33z said:
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
Click to expand...
Click to collapse
Here. Try this
https://www.androidfilehost.com/?fid=23578570567720169
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer