Related
Updated
Please read the instructions completely and carefully before you attempt anything.
Disclaimer:
What ever you do with your device is your own responsibility. In no way shall I, any other member of XDA or HTC, be held responsible in case you brick, destroy your device or even cause any bodily injury to you, by following these instructions
Click to expand...
Click to collapse
Before you start meddling with your device, please read, search XDA for related information, use wiki.
Those people who are trying to gain S-off to flash ICS ROMs with sense 4.0... You do not have to flash the new firmware as a compulsion. The older Radio works well with the sense 4 ROMs. It is not an absolute necessity to upgrade the firmware. You can skip that. And you can flash any ROM in 4ext touch recovery even with S-ON. Proceed to S-off only if you accept the risks of bricking your device completely without any possibility of recovering it again. And also keep in mind, you will lose all your personal data on the device by following these instructions.
Resources:
1. Windows running computer(PC).
2. HTC EVO 3D android smartphone.
3. USB cable that came with your Evo 3D.
4. Micro SD card with adequate space in it.(At least 4 GB)
5. Basic computer knowledge of how to open a command prompt and how to run commands in command prompt.
6. 7z / winrar archiver.
Prerequisites for doing anything with your device.
1. Download and install the HTC drivers.
(You can get this from HERE)
2. Unlock your device the htcdev way. Visit http://www.htcdev.com and follow the instructions.
You can take a preview of all the steps in attached zip below.
3. Read this post by flashmaniac, http://forum.xda-developers.com/showpost.php?p=22494488&postcount=1
4. Read this post by happyhallsy8 http://forum.xda-developers.com/showpost.php?p=17233858&postcount=1
5. Uninstall the HTC sync application from your computer.
6. Download the adb and fastboot files attached below in fastboot-cmd.rar and extract this to the root of the C drive on your computer and rename the folder to Android.
You need to understand a few important terminologies before going forward:
1. Root: It is the basic file system of the android operating system on your device. This has all the important files and programs and drivers which make your device run. And to access this you need to have administrator privileges. Which is obtained by flashing a custom rom which gives you administrator privileges by default, or you need to flash superuser from a custom recovery and then install busy box.
2. Custome ROM: It is an installable zip archive which contains all essential programs and files found in the operating system released for your device by the manufacturer with some modifications so as to enhance the functionality according each individuals taste.
3. RUU/shipped ROM: RUU is an executable which re-installs the original manufacturer released version of the ROM onto your device.
4. Bootloader: It is the part of the firmware which resides in your device which runs the most basic function of starting the device and switches the control to the operating system once the bootstrap of the operating system has loaded on.
5. Locked bootloader: The device manufactures lock this firmware so that your device does not fail to boot and bad programs don't ruin the essential files.
6. adb: A program which can control your device when your device is connected to the computer through a USB cable.
7. cid: This is your manufacturer provided general hardware/firmware id.
8. Serial number: Unique identification number of your device.
9. Unlocking: Unlocking your device the HTCDEV way gives you ability to flash custom ROMS which are not authenticated by HTC and it does not enable you to flash custom kernels on to your devices.
10: Kernels: These are the files that determine how your device perfomes, so if you do not intend to meddle with your kernels, all you will ever need is unlocking the HTCDEV way
Click to expand...
Click to collapse
If you just want to flash a new ROM you do not need to s-off your device
S-off is required only to flash custom kernels
The instructions for each different procedure are posted in a new post.
Continued in the next post.
Getting started... Up to flashing a rooted custom ROM
Now lets get started.
1. Unlock your device HTCDEV way. There are ways in which you can achieve S-OFF without unlocking your device first. Search for them in the forum. Unlocking HTCdev way has been shown to be consistently successful.
By unlocking HTCDEV way, you will loose all your personal data from your device, so please make a nandroid backup before doing this.
Also use any of the apps and contacts backup and restore apps available in the market and restore all your messages, contacts, apps and settings.
2. Download Clockworkmod recovery by clockworkmod. This tool is essential to flash any custom ROM. Copy this file to your adb folder on your cumputer, That is c:\android.
3. Download a fully rooted custom ROM like one from LeeDroid or any other custom ROM which is rooted.
4. Additionally you can download superuser rooting app.
5. Go to settings in your device, and select applications-->development-->check the USB debugging. Connect your device to your computer by USB cable.
6. Click start and run cmd prompt.
7. Enter the following code
Code:
cd\(Hit Enter button)
cd android(Hit Enter Button)
adb reboot bootloader(Hit Enter button)
The result will look like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Your device will boot into bootloader mode and it will show fastboot USB.
9. Now Enter this code
Code:
fastboot flash recovery cwm_4.0.1.4-shooteru.img
Wait for it to finish.
Once done, reboot your device.
Once rebooted, enter the code:
Code:
adb reboot recovery
You will enter the clockworkmod recovery.
10. Select the option mounts and storage.
next select mount USB storage.
Wait for your computer to recognize and install the driver, now copy and paste the superuser.zip which you downloaded earlier into the sdcard.
Also copy and paste the LeeDroid ROM which you downloaded into the root of your sdcard.
Right click your removable disk on the computer and select eject.
11. Select Unmount in the recovery on your phone. and then select go back.
12. Now on your computer, in the command prompt enter the following code
Code:
adb reboot recovery
13. Your device reboots into the recovery again.
14. Now select install zip from sd card.
then select choose zip.
Then choose the superuser zip and press power button to select.
Reboot the device normally and do the following.
Code:
adb shell (Hit enter, and you will see $, as shown below)
$su(hit enter)
#(Now you have to allow the superuser privileges on your device)
#exit(ENTER)
$exit(ENTER)
c:\Android>adb reboot(hit enter)
once the device is booted into android, visit the google play store, and search for busy box, download it and install, you will have root access.
Now your device is fully rooted.
15. Another way of rooting your phone is by flashing a pre-rooted rom. Download any Gingerbread rom which has been pre-rooted, copy that to your SD card, reboot into CWM recovery and select the rom you downloaded and flash it.
16. If the device gets stuck in the HTC white screen, then follow these steps.
a. Enter the following code in the command prompt.
Code:
adb reboot bootloader
Then go to the folder where you had downloaded the LeeDroid zip, you extract one particular file by the name boot (It is a .img type of file)
Now copy this file to the android folder in C:\ drive (C:\android)
Now in command prompt enter this code.
Code:
fastboot flash boot boot.img(Press enter)
fastboot reboot
You are done flashing a fully rooted custom ROM with latest superuser app.
Means you are fully rooted and unlocked and have a custom recovery through which you can flash any other ROM if you want to.
CREDITS: IN NO PARTICULAR ORDER,
Clockworkmod, Chad.goodman, Flashmaniac, happyhallsy8, frigid, and many more.
Downgrading your Hboot
Now that you have unlocked and got rooted, lets get your device S-off.
As I understand, till date this following way has been successful in getting your device HBoot down and achieve S-OFF, Important thing for that is to change your CID to a universal CID, that is HTC__001.
I do not know that MY way will work for every device, you are welcome to try my way, for at least the unbranded devices.
There are two ways of changing your device cid.
1. Through fastboot. Open the command prompt, connect your device by USB cable, check USB debugging is enabled. and enter the following code
Code:
adb reboot bootloader
wait till your device enters bootloader and shows fastboot USB, now enter the following code.
a. For unbranded devices.
Code:
fastboot oem writecid HTC__001
fastboot oem lock
fastboot oem reboot bootloader
Please note that in the cid there are 2 underscores before 001.
b. For branded devices such as Vodafone.
Code:
fastboot oem writecid VODAP001
fastboot oem lock
fastboot reboot bootloader
You can even change that CID to HTC__001.
Once you have achieved S-OFF you can change your cid back to original.
2. Manually.
For this you need to download xvi32 hex editor from here
Extract this anywhere, run the xvi32 and open mmcblk0p31.img which you had copied to your device sdcard.
Now change the cid as shown in these pictures.
Initial
Changed
Now save the file.
For branded devices.
Initial,
Changed.
Now save the file and exit.
Now go to adb shell and do as shown:
After this you can check your cid and it will show the changed cid and software build number.
You will get best results if you do this before you flash the custom ROM.
Now you can downgrade the Hboot also in two ways, one is automated as demonstrated by flashmaniac in his thread and the other one is manual.
Downgrading flashmaniac's way does not require you to unlock your device the HTCDEV way.
1. Flashmaniac's way.
Download his tool (Makes sure there are step1.exe, step2.exe and step3.exe in the folder).
Extract the entire folder to root of C drive on your computer.
Run step1.exe
If do not get any errors run step2.exe
Then run the step3.exe
Wait for it to flash the European version of RUU onto your device.
This RUU/Rom.zip in the downloaded folder has the Hboot version 1.49.0007.
2. A little bit cumbersome and manual way of doing it,
Download the tools from Flashmaniac's thread. Extract the zip. Copy the mmcblk0p31.img to your sdcard.
Then run this code in adb. (Your device will be booted normally into android and USB debugging mode should be enabled)
Code:
c:\android>adb shell (Hit enter)
#dd if=/mnt/sdcard/mmcblk0p31.img of=/dev/block/mmcblk0p31 (Hit enter)
You will see copied successfully.
You might face problems here if you are not rooted fully or if your device is still locked.
Then you check the cid and if it shows non workable cid, then write the new cid and relock your device.
Code:
fastboot oem readcid
fastboot getvar cid
Code:
fastboot oem writecid HTC__001 (or)
fastboot oem writecid VODAP001
Code:
fastboot oem lock
Now boot your device into recovery:
Code:
fastboot reboot
adb reboot recovery
In your computer, from the tool folder downloaded from Flashmanic'c thread, rename the Rom.zip to PG86IMG
Copy this zip to your sdcard by mounting your sdcard in recovery.
Reboot into bootloader.
Code:
adb reboot bootloader
now check that your device bootloader shows as Relocked.
If it doesn't show Relocked.
Try this method to Relock it.
Code:
fastboot flash unlocktoken unlock_code.bin
YOU MIGHT HAVE TO RE-DO THE ENTIRE PROCESS OF HTCDEV WAY OF UNLOCKING AGAIN AT THIS POINT. WORKS 100% OF THE TIME
Accept the disclaimer by HTC and let it reboot.
Now pull the battery, and then reboot into bootloader by pressing volume down button and then pressing the power button.(You should keep the volume down button pressed till you boot into the bootloader)
Now relock your bootloader again.
Code:
fastboot oem lock (hit enter)
fastboot reboot-bootloader(hit enter)
Now your device will start reading the zip then it will check it for a signature and will ask you if you want to flash.
select yes by pressing the volume up button.
Let it finish.
You may see some error in the end, stating fail. Don't worry.
Just reboot your device.
You are done.
Now you have a Hboot version 1.49.007.
CREDITS: IN NO PARTICULAR ORDER,
Clockworkmod, Chad.goodman, Flashmaniac, happyhallsy8, frigid, and many more.
Now Finally to S-OFF
Finally the much awaited S-OFF
The need to do all the above steps was to finally arrive here.
It is essential to make sure that, your device has a Hboot 1.49.007.
The whole point of this tutorial up to here has been this.
There is one way getting S-OFF on your device, that is by using the revolutionary tool.
Visit http://revolutionary.io
Select the appropriate operating system.
The download will start as soon as you click on the operating system shown.
Enable USB debugging mode on your device and connect it to your computer by the USB cable.
Extract the downloaded zip from revolutionary site to your C drive.
Run the revolutionary.exe as administrator.
This will give you your device serial number.
Enter the serial number in the space given on the revolutionary.io site and copy the S-off code generated, and paste it your notepad.
For the revelotutionary tool to work you must have an identifiable software build number on your device (You can change that in mmcblk0p31.img with a hex editor).. Better still just flash the European ROM with Hboot 1.49.007.. This is safer and avoids problems while running the revolutionary tool.
Now type the code in the program.
Hit enter and wait for it to finish.
If something goes wrong, or if it says failed.
Then recheck your device's boot loader is locked.
And try again and again till you succeed.
The second way is just download this supertool by frigid and run it and you are done.
Now your device has been successfully S-OFF.
Reboot your device.
Copy which ever custom ROM you want to your device's sdcard.
copy any kernel you want.
Then flash them using the CWM recovery in the recovery.
Or use the fastboot commands to flash the kernels and ROMs as you like.
Hope This tutorial will benefit all the noobs as well as members who face problems while trying to S-OFF their devices.
CREDITS: IN NO PARTICULAR ORDER,
Clockworkmod, Chad.goodman, Flashmaniac, happyhallsy8, frigid, and many more.
Thank you guys.
For warranty issues you can revert back to your original version by following these steps
Visit this thread
Download the appropriate RUU version for your region.
Make sure that you have your original cid written back on your device.
You can do this by entering the following code
Code:
//to check the current cid//
C:\android>fastboot oem getvar cid
//to change the cid//
C:\android>fastboot oem writecid HTC__044
//You must enter your device cid which you wrote down before you changed it//
Repeat these steps two to three times and reboot into bootloader and re_lock your device
Code:
C:\android>fastboot oem lock
Run the .exe and follow the onscreen instructions.
If this does not work, then, RUN THE .EXE FILE and do as described below.
When the RUU asks you accept, minimize the RUU/drag it down.
Start the task manager on your computer, go to processes, look for a process which has a name ARUwizard, right click on that and select go to location.
Now you can see a zip archive called rom.zip
Open that, and find the android-info.txt, extract it or just open it within winrar.
This will contain the cidnumber, note down the cidnum which was similar to your cid number, and note down the software build number.
Now make these changes in the mmcblk0p31.img with the help of xvi32 hex editor, copy back the file to your device in adb.
Instead, if you remember your original cid and software build number, you can write them back.
Please also remember to write the original cid of your device back in fastboot.
Copy that rom.zip to the root of your sd card, and then reboot into bootloader and flash it in bootloader.
Now reboot the device and run the RUU, once done, do the following.
Enter this code in fastboot:
Code:
fastboot oem lock
Remember to lock your device bootloader first, before writing the secureflag 3, If you don't lock the bootloader, you will brick your device.
Code:
fastboot oem write secureflag 3
fastboot reboot-bootloader
You will see that your bootloader is S-ON and shows RELOCKED.
You are done.
Just in case I fall short of space
Just in case one more
Thanks for this...I already have a custom recovery, and a fully rooted rom...awaiting S-OFF instructions...
I assume that your instructions will work for CID: VODAP021... with HBOOT: 1.49.0013
Thanks
Thanks - Is it worth trying the touch version of Clockworkmod recovery?
also there's no point flashing the superuser.zip and then flashing a rooted rom on top as the superuser.zip would only give root on the current rom - which is then overwritten by the rooted (leeroid) rom
sorry but this post is useless....
how to root is already explained... there are automated recovery flashers... there is an automatically way of gaining s-off.
you destroy the chance that people get the right tutorial on first try...
43D again.... you will never get S-OFF.
Lothaen said:
Thanks - Is it worth trying the touch version of Clockworkmod recovery?
Click to expand...
Click to collapse
No... it's buggy as hell.
Flashmaniac said:
No... it's buggy as hell.
Click to expand...
Click to collapse
that's a shame - worked perfectly on the HTC Desire
Flashmaniac said:
sorry but this post is useless....
how to root is already explained... there are automated recovery flashers... there is an automatically way of gaining s-off.
you destroy the chance that people get the right tutorial on first try...
43D again.... you will never get S-OFF.
No... it's buggy as hell.
Click to expand...
Click to collapse
This tutorial is not yet complete flashmaniac, this will give every possible way of getting s off. That's the point of this. If you don't mind... I will use your links here and will explain your automated way in the beginning. That is my intention.
Please wait till it is complete.
There are some workarounds, those will also be explained.
Flashmaniac said:
43D again.... you will never get S-OFF
Click to expand...
Click to collapse
BS you are the only one posting this...WTF IS YOUR ISSUE...tell me why or STFU!
4D3 said:
BS you are the only one posting this...WTF IS YOUR ISSUE...tell me why or STFU!
Click to expand...
Click to collapse
I am just telling you, that it is not possible. but try and try - you will know why I told you that a hundred times already
dryogeshd said:
This tutorial is not yet complete flashmaniac, this will give every possible way of getting s off. That's the point of this. If you don't mind... I will use your links here and will explain your automated way in the beginning. That is my intention.
Please wait till it is complete.
There are some workarounds, those will also be explained.
Click to expand...
Click to collapse
this will confuse people. there are plenty of none-working ways. now you add one more....
downgrading only works for the cid's that I listed on my thread...
edit: I see that you are advicing people to change their cid.
It usually does not work
if it is working you cannot lock the bootloader
Flashmaniac said:
I am just telling you, that it is not possible. but try and try - you will know why I told you that a hundred times already
this will confuse people. there are plenty of none-working ways. now you add one more....
downgrading only works for the cid's that I listed on my thread...
edit: I see that you are advicing people to change their cid.
It usually does not work
if it is working you cannot lock the bootloader
Click to expand...
Click to collapse
I have done that.. my cid wasn't listed, now I am s off. What do you say for that?
dryogeshd said:
I have done that.. my cid wasn't listed, now I am s off. What do you say for that?
Click to expand...
Click to collapse
As I said - usually it does not work. If there are RUU'S with CID's for your carrier and region you can change them but you cannot lock the bootloader. it says succesfull but stays unlocked
Flashmaniac said:
As I said - usually it does not work. If there are RUU'S with CID's for your carrier you can change them but you cannot lock the bootloader. it says succesfull but stays unlocked
Click to expand...
Click to collapse
There is a workaround for that as I have written dude..
dryogeshd said:
There is a workaround for that as I have written dude..
Click to expand...
Click to collapse
and what is if you CID is TELST001? right! it is not working and it will never work.
This is just one of a thousand examples.
I tried changing the CID with a guy that has TELST001, it has never worked.
never mind... go on with this.
If I downgrade hboot from 1.49.0018, to 1.49.0007, what I'm losing?
Flashmaniac said:
and what is if you CID is TELST001? right! it is not working and it will never work.
This is just one of a thousand examples.
I tried changing the CID with a guy that has TELST001, it has never worked.
never mind... go on with this.
Click to expand...
Click to collapse
Will update as and when I find out the workarounds for not supported cids..
This thread needs support from guys like you. Please wait till I finish the tutorial. You will see why I started this.
So, I justed S-off'd my friends phone, and then updated the RUU to the latest ICS one. Now I'm trying to flash recovery, but using cmd, it says Failed
What's up?
if you're doing adb then make sure you have usb debugging enabled.
if you're doing it through fastboot then you need to install a modded hboot first for fastboot commands
how do u do it with abd?
you can use the jboot that came with control bear or download the one you want, rename it to PH98IMG.zip and flash in bootloader. you will then have full functionality of fastboot commands and can then flash a recovery.
Yeah, when I s-off'd, I thought the script automatically flashed a h-boot that allows fastboot commands. I just replaced the h-boot with one that does, and I could use fastboot just fine. It's all good.
[FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-13
My friend's phone had the annoying bootloop problem. I'm posting this because after a lot of searching, I found nothing to fix the bootloop, just people asking about it. Here's a simply fix.
BOOTLOOP FIX:
If you already tried unlocking/ and you're still S-On, then set everything back to stock:
Flash the attached stock recovery,
fastboot oem lock to be locked again.
Use the latest RUU to update the phone.
At this point the stock, locked phone should function normally.
I have busted this phone a ton of times trying to get different recoveries and roms to work, and this method has always fixed the bootloop.
At this point you can try whatever tutorial you like to downgrade or customize the phone...and if it breaks, hopefully this method will still work for you. If it doesn't work the first time, try running the RUU a second time. Or third.
CUSTOM RECOVERY:
If you want to unlock and install custom stuff:
Use the HTC Dev unlock method.
Fastboot install CWM Recovery v5.8.0.1 from their website -
The ONLY recovery that I've found to be compatible with HBOOT 1.58 is CWM v5.8.0.1. Everything else leaves the phone in an infinite bootloop. Maybe others have had different experiences.
To fastboot install the CWM recovery, rename the file to recovery.img (for simplicity) and type in a command prompt (same directory as fastboot and recovery.img):
fastboot flash recovery recovery.img
Then, to enter into recovery, either pull the battery and enter recovery through the bootloader menu, or type in:
fastboot boot recovery.img
This should get you into the working CWM recovery. If it doesn't, it's because HTC hates people that buy their phones.
If you feel like giving up and running stock, all you need to do is reflash the stock recovery, and relock the phone using fastboot oem lock - and now it should run the stock rom...and if it doesn't, then rerun the RUU. Tedious.
HBOOT Downgrade & S-Off:
If you have: Stock 2.89 RUU / Locked / S-On
Unlocked with HTC Dev method
Flash CWM 5.8.0.1 from the CWM website:
fastboot flash recovery recovery.img - then
fastboot boot recovery.img (to enter recovery)
Flash the SetMainVersionLOW.zip file attached (thanks ramjet73)
Relock the phone with: fastboot oem lock
Use the Unknownforce/closeone hboot downgrade with live CD using the 2.89 RUU's rom.zip (from windows temp folder) renamed to PG86IMG.zip - go to the Unknownforce/closeone thread for this part: http://forum.xda-developers.com/showthread.php?t=1563342
Then flash the standard 1.13 RUU on your windows system (may also work with the PG86IMG.zip method, have not tested)
Then use revolutionary 0.4pre4 to S-Off
Finally, you need to flash a custom recovery which you can do from revolutionary, or from fastboot as listed above. Once the recovery is installed, you should be able to install a compatible custom rom and kernel.
You bootloader screen should now say REVOLUTIONARY on top instead of UNLOCKED or RELOCKED etc... and show HBOOT 1.40.1100.
Thanks to Unkownforce, closeone, and ramjet73 for making this possible.
PS. Screw up your phone at your own risk.
In case anybody was wondering, the RUU I've been using is the latest one at the time of this post: RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to be one of the stock versions I guess, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
mnomaanw said:
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to one of the stock versions, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
Click to expand...
Click to collapse
Yeah, don't ever do the write secure flag command. That's bad news. Running a ruu will not s- on, and you're better staying s-off
Sent from my PG86100 using xda app-developers app
Reset s-on, and
fastboot oem lock to be locked again.
Click to expand...
Click to collapse
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
xHausx said:
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
Click to expand...
Click to collapse
@xHausX
Totally agree. The only reason to set S-ON once S-OFF is achieved is to return to 100% stock for warranty service or to sell the phone.
Nice to see you in these parts again and Happy New Year!
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
I updated the OP. I read somewhere else that it was necessary, this phone was never S-Off, so I wasn't sure.
Thanks
Everytime i run the ruu for my 3d it will finish as it has completed and boot. But whenever i remove my battery to switch it with a secondary, i used to do this before bed every night, i get a bootloop and cant boot untill i boot into bootloader and select the recovery option which wipes the phone and boots untill then next time i remove the battery. Why wont the RUU fix this? ive ran it multiple times. And also whenever im in the stock recovery and i select factory reset or any of the options i get "invalid option" "sucess rebooting by reason oem-00" what does this mean!?! can this be my sd? cause i cant mount cache recovery command or mount anything in recovery for that matter. if i need an sd ill buy one. just dont wanna find out its not my sd. and ive run the RUU about 7 times in total and nothing helps. thanks
ramjet73 said:
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
Click to expand...
Click to collapse
Yeah, I put WIP because it still never worked right, it was just the only one that ever actually loaded. I still hate this phone, I wish HTC was as nice as Samsung. It's so easy to work with Samsung, I always get mad trying to work around HTC's crippling B.S. Still better than Motorola though.
bootloop in my Htc Evo 3D hboot 1.53.007
How do you flash the stock recovery?
jcthelight said:
How do you flash the stock recovery?
Click to expand...
Click to collapse
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
i have hboot 1.53 with s-on stuck on bootloop and i did as u said i flashed stocked recovery from temp folder from ruu-ics-35-ara.exe still my phone is in boot loop. Even i tried oem lock and run ruu.exe file upto 65% process goes fine then suddenly shows 100% process complete and reboot device(still stuck on bootloop).... plz give me suggestion to get rid of this thing.....
"RUU_SHOOTER_U_ICS_35_S_HTC_ARA_3.28.415.2_Radio_11.77.3504.00U_11.25.3504.06_M_release_264795_signed.exe"
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
I'm a little confused. I've never rooted this phone so it's completely stock. My phone keeps powercycling. When I type in "fastboot flash recovery recovery.img" my cmd prompt tells me FAILED (remote: signature verify fail).
Any suggestions?
Re: [FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-
Dang it! Why does it seem like developers have quit developing fully functioning roms for this phone? I live in a good 4g area so those roms without it are out of the question for me. And the others are having major issues with cameras, video playing, text messaging that keep it from being a daily....
And after using jellybean these ICS roms feel very incomplete even though they're more functional. I know you developers are busy people but please, can ICS get freshened up. Or just ignore me if y'all think the camera/text thing will be resolved very soon.
Sent from my PG86100 using xda premium
ONLY FOLLOW THIS GUIDE FOR WARRANTY REPLACEMENTS OR IF YOU NEED TO BE STOCK FOR A SALE. THERE IS NO OTHER REASON TO FOLLOW THIS GUIDE.
ALSO MAKE SURE YOU FOLLOW THE GUIDE PROPERLY. FAR TOO MANY ERRORS ARE BEING MADE BY NOT READING OR FOLLOWING STEPS IN ORDER.
This guide will help you get your phone back to stock after using any of the 5 S-Off methods that either have been or are currently available to us.
Credit to Scotty1223. I edited his One S guide for the DNA.
First post is for Facepalm and JTAG S-off only. RevOne instructions are in the second post. Moonshine and Rumrunner is in post 3.
***IF YOU HAVE A CUSTOM SPLASH SCREEN INSTALLED, THE STOCK SPLASH SCREEN MUST BE FLASHED BEFORE DOING ANYTHING! SEE FOURTH POST FOR LINKS AND INSTRUCTIONS FOR FLASHING THE STOCK SPLASH SCREEN***
***DO NOT ISSUE ANY OF THE WRITESECUREFLAG COMMANDS ON AN ENG HBOOT AS IT WILL BRICK THE DEVICE. JUST FOLLOW THE GUIDE.***
For those who want to return to stock and have used the JTAG method for achieving S-Off, this guide will also work for you. It all depends on what you did AFTER you got your JTAG phone back. If you wrote a new CID using fastboot and HTCDev unlocked, follow the guide as it is written out.
If you didn't write a new CID and use HTCDev unlock and just merely flashed a modified/ENG HBOOT, then the process would be: Fastboot flash stock hboot, RUU to stock, fastboot oem writesecureflag 3, then allow phone to update using the OTA process. You can find the commands/files/steps for these 3 simple steps below as well.
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED** If not, re-flash the zip. If still not locked, try downloading the file again and re-flashing.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writecid VZW__001 (2 underscores)
fastboot reboot-bootloader
fastboot getvar cid (verify your stock CID)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Should now be 100% stock, S-ON, with CID 100% stock as well.
Returning to stock from RevOne
It is pretty much the same process, but with a slight deviation.
AGAIN, IF YOU HAVE A MODIFIED/ENG HBOOT, DO NOT ISSUE ANY WRITESECURE FLAG COMMANDS. JUST FOLLOW THE GUIDE.
First, download these two files:
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED** If not, re-flash the zip. If still not locked, try downloading the file again and re-flashing.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
You are now out of box stock.
Return to stock on Moonshine, Rumrunner and Firewater S-Off
Files needed:
Lock bootloader zip: lock bootloader MD5: f335f78f9f46469c823da0c671026de5
3.06 RUU: 3.06 RUU
Steps:
1.Copy the "lock bootloader zip" onto root of internal storage and flash in recovery of your choice. Once it is flashed Reboot your phone.
2.Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
You are locked. The s-off process removes the flag from displaying, but it is now locked.
IF YOU ARE RUNNING ANY HBOOT THAT IS NOT THE 3.06 HBOOT (1.54 in bootloader), YOU MUST FLASH 3.06 HBOOT BEFORE CONTINUING - SEE POST 4
3. run the RUU as admin (right click, run as administrator)
4. After RUU completes and phone reboots, make sure usb debugging is on and in charge only mode and open cmd prompt
5. Run the following:
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
You are now out of box stock.
FLASHING THE STOCK HBOOT:
*Credit to .torrented*
1. download 3.06 HBOOT: 3.06 HBOOT
2. Rename stock hboot file to : PL83IMG.zip and place in the folder that contains your fastboot.exe file (On your computer)
3. Flash hboot
Code:
Step 1) adb reboot bootloader
Step 2) fastboot oem rebootRUU
Step 3) CD to directory containing hboot zip (i.e. cd C:\sdk\)
Step 4) fastboot flash zip PL83IMG.zip
*** When it says it is done in the terminal/cmdprompt execute the following ***
[The green bar only fills up about 75% of the way]
Step 5) fastboot reboot-bootloader
Flashing the Stock Splash Image
*All credit goes to E.T.Heil
1. Download the stock splash image here.
2. Rename file to splash1.img
3. Place the file in the same folder you have adb.exe and fastboot.exe located.
4. Plug in your phone to a USB port, turn on USB debugging and open a command prompt. cd to the directory your adb/fastboot is located
5. Run the following:
Code:
adb devices (your device ID should be displayed)
adb reboot bootloader
Once in the bootloader, run:
Code:
fastboot flash splash1 splash1.img
Once complete, reboot the phone using the menu or
Code:
fastboot reboot
updated with RevOne and Moonshine...
If anyone sees anything I missed let me know. Otherwise guide is complete.
Thank you so much for making this post. This is exactly what I needed. I am not quite sure which method I uses but it was the first one that required changing the CID, unlocking via htc dev and all that stuff. Would that be facepalm? Sorry if this is a dumb question, it was so long ago that I don't quite remember.
Imacellist said:
Thank you so much for making this post. This is exactly what I needed. I am not quite sure which method I uses but it was the first one that required changing the CID, unlocking via htc dev and all that stuff. Would that be facepalm? Sorry if this is a dumb question, it was so long ago that I don't quite remember.
Click to expand...
Click to collapse
Yes that was the Facepalm method. So follow the OP guide for that.
I love you! (no homo).
when i run RUU i get error 155 so i tried to flash the 1.15 hboot and i get this error in cmd
D:\Documents and Settings\Jonathan\My Documents\HTC\adt-bundle-windows-x86-20130
219\sdk\platform-tools>fastboot flash zip PL83IMG.zip
sending 'zip' (2047 KB)...
OKAY [ 0.375s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.562s
am i doing something wrong? i want to get my phone back to complete stock because i flashed a rom after moonshining without making a backup first. so i really want to get to stock so i can do the whole process over again (moonshine again if needed)
Prodiigy said:
when i run RUU i get error 155 so i tried to flash the 1.15 hboot and i get this error in cmd
D:\Documents and Settings\Jonathan\My Documents\HTC\adt-bundle-windows-x86-20130
219\sdk\platform-tools>fastboot flash zip PL83IMG.zip
sending 'zip' (2047 KB)...
OKAY [ 0.375s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 0.562s
am i doing something wrong? i want to get my phone back to complete stock because i flashed a rom after moonshining without making a backup first. so i really want to get to stock so i can do the whole process over again (moonshine again if needed)
Click to expand...
Click to collapse
Possibly a bad download, Download the HBOOT again and give it another go.
Also, with that error you are getting during the RUU process, did you lock the bootloader back up before running the RUU? That error sometimes shows up from not doing that.
I don't know if this will help anyone or not, or if this was known and I was just being stupid, but I was getting the ERROR [155] as well when running the RUU and I knew my hboot was correct as well as locked so that wasn't the problem, so I attempted to run the RUU again and saw that it was saying my current version was 1.28.xxxxxx which made me realize that that was the Sense 5 roms version number and not the actual version number of my phone causing it to fail. What I then did was i downloaded an AOSP based rom (but I would surmise that a sense 4 DNA rom would work as well) and flashed that then tried again. After doing that it showed the correct version number in the RUU and processed correctly!!
For a little more in site I was on the following setup:
Moonshine S-OFF
Joelz Stock Sense 5 <-- What caused the Error 155
Carbon ROM (Built by Pio) <--- What fixed the error (Would work with any AOSP or Sense 4 Rom ***Needs tested***)
**Edit**
Also incase anyone was wondering I was doing this to fix my phones radio, for some reason when flashing certain roms it gets stuck in Roaming no matter what you do. To fix it I just take my phone completely back to stock S-ON etc, then go into the bootloader and hit factory reset with the stock recovery and it seems to fix it, then S-Off and unlock again and go about my business. I couldn't actually find an answer besides "RMA the thing" to fix the radio roaming issue, so i figured i'd add that incase anyone else was/is in the same boat.
Hmm... I'll do a bit of testing on that with random Sense 5 vs AOSP/Sense 4 ROMs. If that is the case, I'll edit the guide.
I successfully restored my droid dna to untouched stock with this method. I had to exchange my DNA for a new one due to problems I was having and I am trying to do everything I can to make sure that there is no evidence of my tampering. One thing someone mentioned was to take the OTA's to get the device up to current 2.06 since I have been rooted and such since the first day it was available and am on 1.15. I have tried manually checking for software updates and it doesn't seem to find anything. It hasn't prompted me yet and I am wondering if because I am so far behind if they update system isn't checking or something else it wrong. Any thoughts? Any ways to manually update to 2.06 like flashing a new RUU (if that exists)? Thanks.
Just leave the phone on... I did it a few weeks back. It will eventually update.
Phaded said:
Just leave the phone on... I did it a few weeks back. It will eventually update.
Click to expand...
Click to collapse
Thanks. Verizon is only giving me 5 days to ship it back haha. So I just wanted to figure it out as quickly as possible.
Confirmed that on Sense 5 ROMs it randomly errors out. Editing guide.
I flashed the hboot zip and the hboot version is1.33 The phone is s-off and locked on viper rom. The RUU will reboot the phone into the black screen with the silver HTC logo, then the RUU stops working and asks to close the program. I downloaded three times and checked the md5 each time and its good. I am stuck. Any suggestions?
gris1016 said:
I flashed the hboot zip and the hboot version is1.33 The phone is s-off and locked on viper rom. The RUU will reboot the phone into the black screen with the silver HTC logo, then the RUU stops working and asks to close the program. I downloaded three times and checked the md5 each time and its good. I am stuck. Any suggestions?
Click to expand...
Click to collapse
The RUU itself crashes on the computer or the phone crashes and reboots?
Also the hboot I have linked should give you version 1.31 I do believe.
Thanks for this, worked perfectly!
Phaded said:
Return to stock on Moonshine S-Off
First, download the stock RUU
Stock RUU: 1.15 RUU: Mirror #1 or Mirror #2
Plug your phone into a USB port, turn on USB debugging and open a command prompt. cd to the directory that has adb/fastboot.
**NOTE** I noticed on the XDA mobile app that it breaks the echo command line up and makes it look like 2 separate commands. Do not separate it. The command starts at echo and ends at 33796.
Run:
Code:
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
Your bootloader is now locked. Lets verify...
Reboot into bootloader either using 4 in 1 power menu (if your ROM supports it). Or plug your phone into a USB port, turn on USB debugging and open a command prompt and type:
Code:
adb devices (Your device ID should be listed)
adb reboot bootloader
Verify you are **LOCKED**
Click to expand...
Click to collapse
I am having issues not getting the phone to return to "Locked" status. I have and am running the stock ROM. Just reset back to factory. I am following the commands to the T. Below is what my CMD prompt shows that I typed in, or copied and pasted for the echo command. I was trying to follow the note about the echo command but I could see nothing wrong with it... also in the end I had to type exit command twice for it exit and go back to the prompt for the next folder.
C:\android-adb>adb devices
List of devices attached
FA2C2S510423 device
C:\android-adb>adb shell
[email protected]:/ # su
su
[email protected]:/ # echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 s
eek=33796
d of=/dev/block/mmcblk0p3 bs=1 seek=33796 <
4+0 records in
4+0 records out
4 bytes transferred in 0.007 secs (571 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
C:\android-adb>
Click to expand...
Click to collapse
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You need to unlock again in order to flash back a custom recovery. You also need to have the stock splash screen before you ruu. Had the exact same issue you had. Stock h-boot, stock splash screen and relock and all should be good.
That is my main problem. All of the unlock methods require me to load load an apk to change the CID. I can't do that in fastboot. Is there another unlock method I'm missing that allows you to do it from the fast boot mode?
Sent from my LG-D800 using Tapatalk
if u have your original unlock code from htc dev I think u can fastboot flash that code to unlock again. its in the forum somewhere just not sure where it is.
try this thread, good luck
http://forum.xda-developers.com/showthread.php?t=2160677
You don't have to run a apk to change the cid just Google change cid commands, you do it through adb change it to 22222222 then redo the HTC dev to get your unlock.bin again if u don't have it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You device most likely can't downgrade due to having a locked device. Have you tried flashing the 2.07 ruu
Thank you for all of the replies. Actually the change of the CID command might have worked but I didn't see that reply before I had tried another method found in this thread: http://forum.xda-developers.com/showthread.php?t=2570548.
I was truly stuck in fastboot and couldn't flash a custom recovery at all. Well I used the advice from a previous thread and edited the firmware .zip posted in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2314771. I had initially tried to flash the .zip posted but when I tried to boot into the recovery it wouldn't work. So I opened the .zip file without extracting it and removed the recovery.img from the .zip, I then took the TWRP custom recovery and inserted it into the .zip (if you extract the zip this will not work; you need to use software that can edit a zip without extracting it. On the Mac, which I was using, I used Spring). I renamed the TWRP recovery to "recovery.img" to match what I had previously deleted.
Then I flashed this edited firmware.zip by using the following command in usb fastboot mode (here's the link for my edited file):
fastboot oem rebootRUU
fastboot flash zip YOUREDITEDFILE.zip
fastboot reboot
This then allowed me to boot into recovery. I thought I had figured it out and could now sideload a ROM using the "adb sideload" command and flash some type of ROM that would boot. This failed miserably; it would allow me to push the file, but the install would always fail before it completed.
So then I found this thread here: http://forum.xda-developers.com/showthread.php?t=2570548. I first flashed the two .zip files that were posted in post #44. then I flashed the full RUU posted in post #1. This gave me a bootable stock ROM. Praise God!!!
Finally I went back to this thread: http://forum.xda-developers.com/showthread.php?t=2293919, and flashed the following code.
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Not sure why I had such a terrible time, but I'm glad its over and the DNA is finally sold. Thank you for all your help!
trying to restore my dna back to stock
I got my dna locked again and now I am running the ruu file and i am stuck at 6%. Can someone help please!! Tried it by double clicking the ruu file and running it like that, and i also ran it in administration and both ways i am stuck at 6%