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.
Related
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
navenine said:
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
Click to expand...
Click to collapse
Try this, starting over. You shouldnt run into any hiccups.
tailsthecat3 said:
Try this, starting over. You shouldnt run into any hiccups.
Click to expand...
Click to collapse
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
navenine said:
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
Click to expand...
Click to collapse
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
tailsthecat3 said:
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
Click to expand...
Click to collapse
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
hey im trying to use the ruu to get back to stock , just re locked the phone , and im STILL getting errors with ruu, its saying Update Failed : Hboot version is older , im on hboot 1.5000 .........Im losing my mind trying to get this thing back to stock and out of htc screen logo bootlooping.........any ideas?
navenine said:
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
Click to expand...
Click to collapse
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
tailsthecat3 said:
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
Click to expand...
Click to collapse
this just got even worse, I uninstalled the drivers, and now I can't reinstall them. I can't find them. My computer wont recognize my phone at all. I've tried to goto the device manager and find them online automatically, and I've tried the google USB drivers from the extra folder from the SDK Manager...
if you can point me toward the USB drivers that'd be great, but regardless, what your saying is I need to connect my phone while its in the bootloader? not once its booted? or are you saying I need to boot my phone through the bootloader selecting "fastboot" first?
thanks again
-Nave
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
navenine said:
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
Click to expand...
Click to collapse
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I pushed everything over, got it into the fastboot USB and then typed the "fastboot flash recovery recovery.img" command line
my script was:
sending 'recovery' <5068 KB>...
Okay [ 1.207s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote:signature verify fail>
finished. total time: 1.855s
any ideas?
tailsthecat3 said:
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
Click to expand...
Click to collapse
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
navenine said:
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
Click to expand...
Click to collapse
Where were you going wrong? And what'd you do to correct it? So everyone knows, in case they encounter the same issues.
Sent from my Google Nexus S 4G via XDA Premium
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
navenine said:
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
Click to expand...
Click to collapse
I appreciate that, thank you.
My name is David, I'm a noob, and I need help. I rooted my EVO3D about a year ago. Until yesterday, things were great. I used the HTC unlock method originally. For at least the past six months I've been running Scott's Clean Rom Gingerbread Reborn with no issues. Over the past two or three weeks, my phone has been rebooting itself in the middle of phone calls. I decided it was time to upgrade to a different ROM in hopes of correcting the issue. I chose the RC2 version of Scott's Clean Rom ICS. I used the app Flash Image GUI to flash the Kernel, and then flashed the ROM using Revolutionary. The ROM booted up, installed an update, and rebooted the phone. The system reloaded, and within 5 seconds rebooted again. The system kept rebooting each time after reloading. I tried a recovery to my Gingerbread ROM, but that ROM would no longer load either. I tried flashing a Team 420 ICS ROM as well as a MEANROM ICS ROM, and they were both rebooting just like the Clean Rom did, loading for about 3 seconds then powering down the phone. I even used the superwipe program as suggested by MEANROM and that didn't help. I'm out of ideas. Do you guys have any suggestions? Here are my specs:
HBOOT-1.50.000 S-ON
Revolutionary CWM v4.0.1.4
I've wiped the memory, cache, dalvik, even repartitioned my memory card. Nothing has helped.
I would suggest you to follow this guide and get s-off. will also update you to the latest ics firmware and newer radios
http://forum.xda-developers.com/showthread.php?t=1889438
EM|NEM said:
I would suggest you to follow this guide and get s-off. will also update you to the latest ics firmware and newer radios
http://forum.xda-developers.com/showthread.php?t=1889438
Click to expand...
Click to collapse
Thank you for the advice. I'm trying to work through the directions and get to s-off, but I'm already hitting a road block. The first thing the thread tells me to do is to lock the boot loader, which my phone apparently will not allow me to do. I have updated all of the necessary software on my PC so that I can connect to the bootloader, and I have achieved fastboot USB connection according to my device. However, when I execute the command "fastboot lock oem", the command prompt tells me "< waiting for device >". I wonder if this could be the result of a bad boot image? To some degree, the ROM's and kernels have worked, with the system simply rebooting after a few moments of operation.
davidmech21 said:
Thank you for the advice. I'm trying to work through the directions and get to s-off, but I'm already hitting a road block. The first thing the thread tells me to do is to lock the boot loader, which my phone apparently will not allow me to do. I have updated all of the necessary software on my PC so that I can connect to the bootloader, and I have achieved fastboot USB connection according to my device. However, when I execute the command "fastboot lock oem", the command prompt tells me "< waiting for device >". I wonder if this could be the result of a bad boot image? To some degree, the ROM's and kernels have worked, with the system simply rebooting after a few moments of operation.
Click to expand...
Click to collapse
Connecting to the device in "fastboot usb" mode does not depend on the boot image or anything other than the bootloader (hboot), and should work with any hboot. Try issuing the "fastboot devices" command and if you don't get a response with your serial number, starting with an "HT", you are not properly connected to the phone.
See the tips for Step1 and the post here, which is linked after Step3 of that guide, for additional tips for troubleshooting RUU.exe problems.
ramjet73
ramjet73 said:
Connecting to the device in "fastboot usb" mode does not depend on the boot image or anything other than the bootloader (hboot), and should work with any hboot. Try issuing the "fastboot devices" command and if you don't get a response with your serial number, starting with an "HT", you are not properly connected to the phone.
See the tips for Step1 and the post here, which is linked after Step3 of that guide, for additional tips for troubleshooting RUU.exe problems.
ramjet73
Click to expand...
Click to collapse
EM|NEM and Ramjet73, thank you so much for the help. I finally got the fastboot to connect correctly. I was able to lock the bootloader as outlined, and install the RUU. Now I'm on to the next steps of S-OFF. I cannot thank you guys enough. EM|NEM, I see your donate button, and the goods are coming. Ramjet73, do you also have a button?
David
I really didn't do it for donations my friend. Just glad you got it to work
Sent from my Evo 3D GSM
I suggest all of the above.
Also, try to flash the rom before the kernel. This may solve your issue.
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.
Hello,
This is an odd request, but I'm in need of some help with this HTC Rezound. A bit of background first. It's not mine. I'm a G2 user (rooted and I know my way around Android hacking). This phone belongs to a friend and despite having it rooted he knows nothing about how he got there or how to fix a problem. Currently it's stuck in a bootloop. He mailed the phone to me (we live 750 miles apart) and he's hoping I might be able to assist. I can get into recovery (I'm assuming it's a custom recovery - looks like ClockworkMod) and my hope was to flash a new ROM but he stupidly neglected to send the phone to me with an SD Card. I'm wondering if there's a way to get a ROM/gapps onto the phone (internal storage) and flash from there. I see there's an option for USB-MS toggle and I've tried playing around in the internal_sd area, and I can get a G: drive to appear when choosing this and connected via USB to my computer, but when I put the ROM/gapps on there I cannot seem to access it for flashing purposes.
Sorry for the long-winded description. But is this a simple solution? Do I just need to get a hold of an SD card and put the files needed on there for flashing? Or is there a way to flash the ROM directly from internal storage?
Thanks in advance for any help you might provide.
Could you post a "fastboot getvar all" ? Without the commas.
Also one thing I would do. Flash twrp 2.6.3.0 Then mount the phone. Push the ROM using a adb push. But first could you post a fastboot getvar all ?
Sent from my Rezound running Sense 5. S-OFF
pball52998 said:
Could you post a "fastboot getvar all" ? Without the commas.
Also one thing I would do. Flash twrp 2.6.3.0 Then mount the phone. Push the ROM using a adb push. But first could you post a fastboot getvar all ?
Sent from my Rezound running Sense 5. S-OFF
Click to expand...
Click to collapse
Sorry for my noobness, but I have no idea how to do that with this phone. I know nothing about HTC devices - never owned one before.
No problem at all man, we all start somewhere for every phone company.
Okay, pull the battery out. Put it back in, volume down, power button. It should show up a white screen. With I think like 5 options, I know the first two are: fastboot and recovery. When highlighted over fastboot, press power. Then will bring you to fastboot. It'll say in red letters "FASTBOOT USB" at the top. Plug it into the computer open a cmd prompt where you fastboot/adb also known as platform-tools is. Type fastboot getvar all
Sent from my Rezound running Sense 5. S-OFF
pball52998 said:
No problem at all man, we all start somewhere for every phone company.
Okay, pull the battery out. Put it back in, volume down, power button. It should show up a white screen. With I think like 5 options, I know the first two are: fastboot and recovery. When highlighted over fastboot, press power. Then will bring you to fastboot. It'll say in red letters "FASTBOOT USB" at the top. Plug it into the computer open a cmd prompt where you fastboot/adb also known as platform-tools is. Type fastboot getvar all
Sent from my Rezound running Sense 5. S-OFF
Click to expand...
Click to collapse
Thanks for the reply. My time messing with the phone is done for the night, but I'll give that a try tomorrow.
Okay sounds good
Sent from my crappy Jailbroken apple iPad.....
Freedoms just another word for nothing left to do... Nothin' ain't worth nothing but it's free.....
It should say something in the bootloader at the top like below:
***unlocked***
Pvt ship s-off (or s-on)
Hboot version # stuff here
Radio version # stuff here
Is it s-off or s-on?
If it's secure flag is still on, you would need to extract the boot.IMG from your ROM zip and do the following command after pushing and flashing the ROM in recovery. After you do flash the ROM, boot back into bootloader and into fastboot and type the following command in PC terminal
Fastboot flash boot boot.img
Sent from my Rezound
Uzephi said:
It should say something in the bootloader at the top like below:
***unlocked***
Pvt ship s-off (or s-on)
Hboot version # stuff here
Radio version # stuff here
Is it s-off or s-on?
If it's secure flag is still on, you would need to extract the boot.IMG from your ROM zip and do the following command after pushing and flashing the ROM in recovery. After you do flash the ROM, boot back into bootloader and into fastboot and type the following command in PC terminal
Fastboot flash boot boot.img
Sent from my Rezound
Click to expand...
Click to collapse
Yep, pretty much, what I was trying to get him through first was actually pushing a ROM to the phone, also the fastboot getvar all gives almost all info. But true with that, that's probably the MOST important part of rooting and ROMing HTC lol. Although he never stated what rom he has. Trying to get him through some basics of HTC too.
Sent from my Rezound running Sense 5. S-OFF
Yeah, just wanted to put that out there in case he found it how to flash a ROM without us, he will see that post to fix his boot loop (if s-on)
Sent from my Rezound
Thanks again for the replies everyone. Very helpful. As stated before, this is an odd situation because I know nothing about rooting/ROMs for HTC and this isn't my phone.
Anyway, a bit of where I'm at and some better info regarding the phone's situation. The phone, upon attempting to boot, would just bootloop. I don't remember exactly which ROM was on there as I've since done a factory reset, but needless to say it wasn't working. Also, I happened to track down an SD card from an old phone of mine and I used the USB-MS feature in recovery to put a ROM on there for flashing. Wiped everything as I would any other phone, flashed the ROM (which stated was successful) and upon a reboot the phone just hangs on the white HTC screen. Did a bit of digging and decided to try returning to stock (he doesn't care if this phone is still rooted, just wants it working). Found this link http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ and followed the instructions exactly. Update seemed to take just fine, but again a reboot just got me stuck on the white HTC screen.
I've yet to hook this up to try the fastboot getvar thing as the computer I'm using didn't have ADB installed and I didn't have the time to do so. In the meantime any additional suggestions?
I'm attaching a pic of the phone in hboot so you can see some info that might be helpful.
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Uzephi said:
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Click to expand...
Click to collapse
Thanks for this. I think I get what you're saying, but just for the sake of clarification, one more question regarding this process.
I extract the boot.IMG from my ROM of choice, flash the ROM/gapps as I would on any other device, then go back to fastboot and run the adb commands posted earlier? Correct?
Rodeojones said:
Thanks for this. I think I get what you're saying, but just for the sake of clarification, one more question regarding this process.
I extract the boot.IMG from my ROM of choice, flash the ROM/gapps as I would on any other device, then go back to fastboot and run the adb commands posted earlier? Correct?
Click to expand...
Click to collapse
Exactly. Be sure to do exactly that command not
Fastboot boot boot.img
If you forget to say flash boot, it will just temporarily boot that kernel/boot image and not flash it to the device. Then upon reboot you will be back at step one.
Sent from my Rezound
Uzephi said:
Exactly. Be sure to do exactly that command not
Fastboot boot boot.img
If you forget to say flash boot, it will just temporarily boot that kernel/boot image and not flash it to the device. Then upon reboot you will be back at step one.
Sent from my Rezound
Click to expand...
Click to collapse
Again, thank you. Going to give this a go after my son's t-ball game. I feel like more of a noob than when I rooted my OG Droid years ago.
@Uzephi, @pball52998, thank you to for your assistance. I felt like a total noob working on a phone that wasn't mine. But I've got it up and running again. My friend Jake will be very happy (I've also told him that this is the last ROM he will ever put on here unless he learns how to do everything I just did - he didn't even know what ADB was when I told him).
Rodeojones said:
@Uzephi, @pball52998, thank you to for your assistance. I felt like a total noob working on a phone that wasn't mine. But I've got it up and running again. My friend Jake will be very happy (I've also told him that this is the last ROM he will ever put on here unless he learns how to do everything I just did - he didn't even know what ADB was when I told him).
Click to expand...
Click to collapse
Wait! He has old HBOOT and Radios, the newest radio is 1.28 he has 1.21 I think I saw.... I would suggest s-off then RUU and doing a RUU.... Or if anyone has em, the HBOOT and Radios you can flash in recovery.
pball52998 said:
Wait! He has old HBOOT and Radios, the newest radio is 1.28 he has 1.21 I think I saw.... I would suggest s-off then RUU and doing a RUU.... Or if anyone has em, the HBOOT and Radios you can flash in recovery.
Click to expand...
Click to collapse
Flashing them in recovery would be great, if there's a link to download the files. But just to be clear, despite this phone finally booking up there's more I need to do to make it 100% usable?
It is 100% usable, but you will experience less overheats and better battery life with the new firmware. I know the hboot ph98img zip is somewhere in this forum for the updated hboot and radio (for that zip you would just put in root of external SD card and in hboot it will automatically flash)
Sent from my Rezound
Uzephi said:
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Click to expand...
Click to collapse
Hello, I have been preparing to RUU back to 4.03.605.2 and want to be sure of process. I read REV3NT3CH's post on downgrading, so I downloaded the latest 2 PH89IMGs via his instructions and here's where I stand:
S Off
Hboot 2.28
Radio 2.23.10.0123r/1.23.10.0124r
also running CleanRom 4.5
Can I just place PH89IMG on sdcard to RUU or am I missing a step? Thank you in advance
Just place it in the root of SD card and reboot to your boot loader
Sent from my Rezound
I tried to s-off my phone today with plenty of methods so I could put my phone back to stock. My hboot is 1.44 but I believe it is a patched version as the date is July 5 2013. Revone gives me error code 6 and firewater gives the chaser error. On a mac so can't use rum runner, and can't use ruu.exe files. Anything I could try? I would think either find a way to update or maybe flash a custom kernel would work?
ADarkKnight said:
I tried to s-off my phone today with plenty of methods so I could put my phone back to stock. My hboot is 1.44 but I believe it is a patched version as the date is July 5 2013. Revone gives me error code 6 and firewater gives the chaser error. On a mac so can't use rum runner, and can't use ruu.exe files. Anything I could try? I would think either find a way to update or maybe flash a custom kernel would work?
Click to expand...
Click to collapse
Post a fastboot getvar all (except for imei and serialno).
majmoz said:
Post a fastboot getvar all (except for imei and serialno).
Click to expand...
Click to collapse
Thanks for the reply. Not home right now but have an update. When running firewater, the last command /data/local/tmp/firewater does nothing except delete the file. Know what to do?
ADarkKnight said:
Thanks for the reply. Not home right now but have an update. When running firewater, the last command /data/local/tmp/firewater does nothing except delete the file. Know what to do?
Click to expand...
Click to collapse
I didn't use firewater so I'm not sure about that. However, you could update to the RUU 3.17.502.3.rom.zip then try firewater again. I don't think firewater really works well with that low of a hboot. Here are the commands for running the rom.zip:
Code:
[B][I]./adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]./fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]./fastboot flash zip 3.17.502.3.rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]./fastboot flash zip 3.17.502.3.rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]./fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Good luck I got to get some sleep!
majmoz said:
I didn't use firewater so I'm not sure about that. However, you could update to the RUU 3.17.502.3.rom.zip then try firewater again. I don't think firewater really works well with that low of a hboot. Here are the commands for running the rom.zip:
Good luck I got to get some sleep!
Click to expand...
Click to collapse
Thanks for the instructions, actually ended up flashing stock recovery and took ota's up to that version. Still no dice for s-off. Oh well, doesn't really matter, was just going to do it because i'm replacing my phone with att, but what are the odds they know how to get into the bootloader Getting the replacement today, and funny beaups replied to me saying he'll update a fix today. Hopefully I can s-off the replacement.