Related
Flashed Xoom back to stock after rooting it and now it will not boot unless its unlocked through fastboot. If the device is locked all I get is "Failed to boot LNX 0X0004" "Starting RDS mode 2". If I lock it using fastboot it will boot with no problems then shortly after it will prompt me to install the latest update. Install will start as normal and it will all of a sudden stop.
Can some one please help me. Let me know if you need more details.
goran1459 said:
Flashed Xoom back to stock after rooting it and now it will not boot unless its unlocked through fastboot. If the device is locked all I get is "Failed to boot LNX 0X0004" "Starting RDS mode 2". If I lock it using fastboot it will boot with no problems then shortly after it will prompt me to install the latest update. Install will start as normal and it will all of a sudden stop.
Can some one please help me. Let me know if you need more details.
Click to expand...
Click to collapse
Do you have a CDMA Xoom (MZ600)?
If so, did you flash back to stock using the images provided at the Motodev site?
If not, you presumably need to use Motorola signed images to re-lock the system, and there are none yet available for the Wi-Fi Xoom.
ydaraishy said:
Do you have a CDMA Xoom (MZ600)?
If so, did you flash back to stock using the images provided at the Motodev site?
If not, you presumably need to use Motorola signed images to re-lock the system, and there are none yet available for the Wi-Fi Xoom.
Click to expand...
Click to collapse
Yeah its the CDMA version. I tried flashing the system using the file and directions on MOTODEV but no luck. It fails to flash the system.img. It hangs for a long time and then displays the message that it has failed. Does anyone know what might be causing it to fail?
Hi all, I am going to be as thorough as I can. I am rather new, and I'm stuck trying to downgrade my MT4G to froyo (PD15IMG). I have read the tutorials, and learned enough about adb to attempt this task, but I think by doing the HTC Bootloader unlocking update last week, it may be the reason I'm stuck. I follow the instructions on the tutorial, to gain temp root, until I get to the part where I should get a "#" in the command Window when I type "adb shell" but I keep getting "$" instead, although everything seems to be going ok until I get to that point.
*Also, I put the PD15IMG.zip on the root of my sd card, and start my phone in bootloader mode, and it finds the PD15IMG.zip, and a blue progress bar appears in the top right corner of my phone for about 90 seconds, it then displays "parsing PD15IMG.zip" then stops at the hboot screen and does nothing. I just select power down, then power on my phone and nothing will have been done to my phone. I guess what I need to know is, by doing the HTC bootloader unlock update (which I did before I read that it was a bad idea), can I still downgrade and root with normal methods, or will I have to do something different?
Sent from my HTC Glacier using Tapatalk
You can start differently. Since you've unlocked the bootloader, try to flash recovery directly, by downloading recovery image directly from Clockworkmod site, rebooting to FASTBOOT (adb reboot bootloader) and using the command "fastboot flash recovery your_just_downloaded_recovery.img".
If recovery flash doesn't work for you - download the 2.2.1 PD15IMG, unzip it, and flash the following 2 files from it:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
Then reboot. You should end up on 2.2.1, which is perm-rootable using the guide (Visionary for temp-root, gfree for S-OFF, and then perm-root if you want).
Then flash the recovery and the engineering bootloader.
Here is what I did, I am giving a link to pastebin as instructed, it seems to go perfectly until I try to flash the StockRom. In the meantime I will attempt what was just posted above^^^^^^^ http://pastebin.com/fYrC6tAZ
One last thing before i have to throw away my phone. I couldnt leave well enough alone. I did this "fastboot flash boot boot.img" as you stated in the post above. It was successful. I then entered this one "fastboot flash system system.img", and it failed (said the img was too big or something) so I did the "fastboot-windows reboot" command and it is now stuck on the white HTC MyTouch 4g splashscreen. Is my phone toast? My PC no longer recognizes that my phone is connected to the USB port, however I can hold the volume dwn & power button and it comes on in the hboot mode.Is there any hope?
Also, when I boot it up by vol/dwn & pwr, the Hboot screen comes up and finds the PD15IMG that is on my sd card, goes through a 1 minute or so process (a blue status bar loads in top right corner), then it just stays on the hboot. It did that before it stuck on the splash screen, but never actually wrote anything i dont beleive.
OK its letting me use FASTBOOT and here is exactly what I got when i tried to flash the 2nd file in your post above. It came from the PD15IMG.zip as you instructed:
C:\adb>fastboot flash system system.img
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.016s
Can someone please let me know if there is hope for my phone? I can communicate with it through Fastboot (on my PC) and it will boot up in hboot mode. But it WON'T go past the Tmobile/MyTouch splash screen. If I get it fixed, I promise to never touch it again until I study! I truly feel there is hope, but I think don't know enough to figure it out. I loaded the PD15IMG on my SD, and it attempts to flash it, (a blue status bar appears in top right corner and fills up in about 90 seconds), but afterwards, it still sticks on splashscreen. Is there anything I can do to fix it? Anything I can flash it with in Fastboot? Please anyone?
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Jack_R1 said:
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Click to expand...
Click to collapse
Thank for your response. I have tried doing the PD15IMG.zip by booting my phone in bootloader mode. It finds the PD15IMG.zip and then a blue progress bar appears in the top right corner of the phone, finishes in about 90 seconds, the a message appears that says "wrong zip file". I would be happy just to get my phone back on with the gingerbread 2.3.4 on it, and simply leave it alone until I know what Im doing. Is there a way to just flash the original s/w back on it? If so if you could tell me how I will not mess with it again until I study alot more. But flashing the PD15IMG doesnt appear to be working for me.
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Jack_R1 said:
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Click to expand...
Click to collapse
Ok you were right, the one I had the wrong MD5SUM, but i d/l the correct one, it had the correct MD5SUM, but it still gave me the "wrong zip file error". I feel like there is hope, but I cant figure this out!! Thank you for trying, is there anything else I can do? I also tried going into recovery and doing factory reset/ data wipe etc...but it continues to get stuck on the splash screen....
How did you copy the correct one to the phone's SD card, and where did you put it? You either didn't copy it to your SD card, or named it wrong, or put it in wrong location, not overwriting the older file.
In any case, if flashing PD15IMG fails for you:
Download CWM recovery from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-glacier.img
Boot to bootloader.
Enter FASTBOOT.
Execute:
fastboot flash recovery recovery-clockwork-5.0.2.0-glacier.img
Boot to recovery. You should have Clockworkmod.
Download a stock rooted 2.2.1 ROM from Development section.
Flash it in Clockworkmod recovery.
Extract boot.img from this ROM.
Flash it in fastboot, using "fastboot flash boot boot.img".
Boot into the ROM.
Proceed with gfree.
OK!! I got it fixed and it all makes sense to me now! I flashed the 2.2.1 boot.img to my phone, when it still had the 2.3.4 on it. It was as simple as that. I hadnt flashed the downgrade on it when I flashed the boot.img and I guess it was a mismatch. I read your last post to extract the "boot.img" from the rom and then it clicked! Yesterday I wrote the 2.2.1 boot img. to a phone that had 2.3.4...so I found a stock 2.3.4 rom, extracted the boot.img from it a BAM! its rolling again....thank you so much....
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Jack_R1 said:
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Click to expand...
Click to collapse
Well I will soon attempt it again, however I think I need to read a little more so I can understand the concept of what I am doing. I learned a ton by making that mistake. But as soo as I got it fixed, I couldnt resist, I used revovery and flashed [ROM]:: ProjectMIUI 2.2.17 [R6]- UPDATED 2/21/12 - [Stable + Smooth from the DEV section and I have never been happier with my phones performance! I will soon try the cyanmod, but I want to chill with this rom for a week or so. Again, I appreciate your help, I learned alot.
As long as you don't mind flashing kernels separately using fastboot for each ROM you flash, you can go indefinitely and flash ROMs as much as you like with your current setup, not needing anything else. The only good reason for you to go for S-OFF would be to flash Engineering HBOOT, to be able to flash kernels from recovery directly, avoiding extra fastboot step.
Also, thanks for finally confirming that you can flash recovery using fastboot on HTC-Dev-unlocked device. There was one device that didn't allow it (I think Incredible S, but not sure), so it's good to know that on MT4G it works as it should.
Hello all!
Please help me
I have pretty good understanding of rooting procedures and custom roms, I have put custom roms on about 10 different phone models, including one previous HTC (CHA CHA)
Tried to flash custom rom, everything goes ok but the phone displays white logo with htc symbol and stays like that.
I still have access to bootloader and cwm recovery.
Sometimes cwm recovery displays message :
E: cant mount cache:recovery/command
E: cant mount CACHE:recovery/log
e:cant open CACHE:recovery/log
Sometimes it does not show though.
I've read that it may be beacuse of emmc chip which gets damaged during taking the battery off when the phone is working.
What to do now ? I tried flashing different roms but nothing happens, when flashing them from CWM i get no error messages,
but when i reboot I get the white screen with htc logo.
Please help ... ;(
This is bootloader info :
*** Unlocked ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_m
eMMC-boot
dec 22 2011
CLOCKWORK MOD IS clockwork mod recovery v2.5.1.2 (MODACO r2)
Another curious thing, it says that it is s-on, but I did dev unlock before !?!?!?!
here is complete history of my actions
I got this desire HD from my friend, he wanted me to put some unofficial 4.0 rom on it.
I remember from when I had htc cha cha that you should first do dev unlock.
Trying to do dev unlock, I selected european RUU but ruu update program told me that it can not be upgraded.
Somewhere on forums , I've read that I could just continue with procedure.So I did.
I got the codes, sent them to HTC and they mailed me the bin file.I got the prompt about unlocking on the phones display, i choose to unlock it.
Then i flashed clockwork mod on it via terminal.
Then i downloaded custom rom and flashed it , but i just get white screen.
Bad thing is I have not made backup (
what to do now please help (((
You have to flash the boot.img separately when flashing roms on a HTC dev unlocked device. That's why it doesent start after a flash. Get it relocked and get S-OFF instead. Search "advanced ace hack kit attn1" on goggle and use it.
Get the ruu for your device and run it from fastboot menu then get S-OFF with advanced aace hack kit.
Sent from my HTC Desire HD using xda premium
OK I have found the aahk thing you told me, when I get home I will try to relock it (usin fastboot oem unlock command ? )
then to unlock the s-on thing....
I send the fastboot flash unlocktoken Unlock_code.bin command and on prompt it says ok but on the phone nothing happens
Also, under device manager phone is registered as android 1.0
anyone help please
When I enter fastboot flash unlocktoken Unlock_code.bin
I get ok messages , but nothing happens on the screen of the phone
I repaired the drivers, when i enter other fastboot commands, like reboot, device reacts.
http://forum.xda-developers.com/showthread.php?t=1810058
this guy here in this post says that when messed bootloader its not ok to work with aahk so im bit scared now
I got this problem solved with help from irc channel of aahk ... big big thans to them...they gudied me to downgrade and flash the stock rom
i saved the log I can send it to who needs it...
trouble help please!
hi, i upgrade my evo 3d from sprint to ICS (2.89.651.2 710RD).
in the 13th step about bootloader unlock,(when i put fastboot flash unlocktoken Unlock_code.bin) the pc says ok, but nothing happens in the device, can you help me please?
retrorobot said:
Hello all!
Please help me
I have pretty good understanding of rooting procedures and custom roms, I have put custom roms on about 10 different phone models, including one previous HTC (CHA CHA)
Tried to flash custom rom, everything goes ok but the phone displays white logo with htc symbol and stays like that.
I still have access to bootloader and cwm recovery.
Sometimes cwm recovery displays message :
E: cant mount cache:recovery/command
E: cant mount CACHE:recovery/log
e:cant open CACHE:recovery/log
Sometimes it does not show though.
I've read that it may be beacuse of emmc chip which gets damaged during taking the battery off when the phone is working.
What to do now ? I tried flashing different roms but nothing happens, when flashing them from CWM i get no error messages,
but when i reboot I get the white screen with htc logo.
Please help ... ;(
This is bootloader info :
*** Unlocked ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_m
eMMC-boot
dec 22 2011
CLOCKWORK MOD IS clockwork mod recovery v2.5.1.2 (MODACO r2)
Another curious thing, it says that it is s-on, but I did dev unlock before !?!?!?!
here is complete history of my actions
I got this desire HD from my friend, he wanted me to put some unofficial 4.0 rom on it.
I remember from when I had htc cha cha that you should first do dev unlock.
Trying to do dev unlock, I selected european RUU but ruu update program told me that it can not be upgraded.
Somewhere on forums , I've read that I could just continue with procedure.So I did.
I got the codes, sent them to HTC and they mailed me the bin file.I got the prompt about unlocking on the phones display, i choose to unlock it.
Then i flashed clockwork mod on it via terminal.
Then i downloaded custom rom and flashed it , but i just get white screen.
Bad thing is I have not made backup (
what to do now please help (((
Click to expand...
Click to collapse
To flash a custom rom with an unlocked bootloader you have to flash the rom in CWM first and then flash the boot.img of the rom in fastboot.
Follow this:
Get the boot.img file from inside the .zip file and place it in the PC, somewhere where u can easily find it.
Put the zip in the sdcard
Boot in CWM. Full wipe and flash the rom
Go to advaced options and reboot bootloader
Toggle to fastboot and plug the phone to the PC (you will see fastboot usb in red)
Open a CMD as admin or Terminal as root in the PC
Navigate in CMD to the folder where the boot.img file is located
Type: fastboot flash boot boot.img
Then reboot, and you should be ok....:good:
I'm looking for a way to get my phone back to a stock state, I don't care if it's unrooted in the process, I just want a fresh OTA capable stock rom. I have a couple PD15 images, and they flash in the boot loader, however, after trying to boot, it just stays stuck at the mytouch startup screen.
I'm looking at the tutorials found here, but none seem to be working. What exactly do I need to do?
Well do u still have a custom recovery or s-off
I have the completly stock rooted ROM 2.3.4 no ota after that
Sent from my T-Mobile myTouch 4G using xda premium
I'm using the PD15 images from here: https://www.4shared.com/folder/xDsyJF52/_online.html
I used the HTCDev unlock method. I have S-On
My issue is, is i want the official HTC kernel that comes with the latest stock rom. I cant find it to flash anywhere. So I'm trying to just go back to the regular rom, probably selling this phone soon anyway.
Son=T-Mobile
soff= the world
You can sell it for more with soff and rooted anyways the ROM I have has the stock kernel its completely stock just rooted
Sent from my T-Mobile myTouch 4G using xda premium
demoncamber said:
I'm looking for a way to get my phone back to a stock state, I don't care if it's unrooted in the process, I just want a fresh OTA capable stock rom. I have a couple PD15 images, and they flash in the boot loader, however, after trying to boot, it just stays stuck at the mytouch startup screen.
I'm looking at the tutorials found here, but none seem to be w/orking. What exactly do I need to do?
Click to expand...
Click to collapse
are yuo trying to flash a gingerbread stock or a froyo stock rom? which PD15IMG.zip files are you using? did you download the stock rom yourself and then rename it to PD15IMG.zip? are you sure your using the correct radio version .img as well? if all that is correct and youre still having trouble then you could try flashing the stock rom via fastboot mode
rename the rom to StockRom.zip (spelled exactly) then connect your phone in fastboot mode, then in the terminal enter fastboot oem rebootRUU it should then reboot into a black screen with a silver htc logo on it
make sure your StockRom.zip is in the same directory as your fastboot executable and run fastboot flash zip StockRom.zip
if it doesnt finish flashing or tells you to repeat the flash just re enter the command and it will work. then fastboot reboot.
haxin said:
are yuo trying to flash a gingerbread stock or a froyo stock rom? which PD15IMG.zip files are you using? did you download the stock rom yourself and then rename it to PD15IMG.zip? are you sure your using the correct radio version .img as well? if all that is correct and youre still having trouble then you could try flashing the stock rom via fastboot mode
rename the rom to StockRom.zip (spelled exactly) then connect your phone in fastboot mode, then in the terminal enter fastboot oem rebootRUU it should then reboot into a black screen with a silver htc logo on it
make sure your StockRom.zip is in the same directory as your fastboot executable and run fastboot flash zip StockRom.zip
if it doesnt finish flashing or tells you to repeat the flash just re enter the command and it will work. then fastboot reboot.
Click to expand...
Click to collapse
I was doing all of the above, except checking the radio version and the fastboot oem rebootRUU! That could be it, thanks for that. I'll check it out and report back when I get some time.
mymeatb18 said:
Son=T-Mobile
soff= the world
You can sell it for more with soff and rooted anyways the ROM I have has the stock kernel its completely stock just rooted
Sent from my T-Mobile myTouch 4G using xda premium
Click to expand...
Click to collapse
I'm interested in your kernel that you are using actually, shoot me a PM or something if you feel like providing me links to download
So i tried the rebootRUU method, and still nothing (it says it works fine but will just hang at the white mytouch screen). I'm on HBOOT 0.89.0007 and RADIO 26.13.04.19_M
I'm trying to flash both the 2.3.4 before and the latest updated 2.3.4 stock rom.
Wish i could figure this out! Any ideas?
try to flash the stock froyo rom first.
http://d-h.st/ytv59wps2wzc heres a link to the PD15IMG.zip make sure the spelling is exactly like that all upper case except for the file extention .zip. and make sure its on the root of your sd card when you reboot into bootloader. the file shoild be about 312megs in size.
Tried, still stuck at the splash screen. I used HTCDev unlock originally with this phone, does that mean I also have to manually flash the boot.img from these zip's as well?
I'm obviously missing some step.
demoncamber said:
Tried, still stuck at the splash screen. I used HTCDev unlock originally with this phone, does that mean I also have to manually flash the boot.img from these zip's as well?
I'm obviously missing some step.
Click to expand...
Click to collapse
*scratch that* it just worked, after trying to do the latest GB version after downgrading to froyo, thanks man.
This Guide will help you reset your HTC One back to 100% stock form with no trace of modifications. S-Off Required!
In order for you to be able to reset your device to complete stock it will require that you have S-Off.
For those that still have S-On and cannot gain S-Off due to having one of the updated firmwares there is not much you can do other than restore a stock rom and stock recovery. S-On users can find my 2.24.401.x stock rom with recovery included here:
http://www.htc1guru.com/2013/09/gurureset-aroma/
I am working on more versions now.
If you restore one of the stock Nandroid backups with a 1.2x version, you will probably have issues with the touch screen not working since the updated touchscreen drivers in the newer firmware updates, prevent the touch screen from working in the stock level 4.1.2 software. Keep checking the Download section for Guru Resets as I will be adding more stock rom versions.
If you have a working touch screen on the stock software, after restoring the stock kernel and stock recovery, your bootloader will show RELOCKED instead of LOCKED once you lock it.
I have easily unlocked bootloader, got S-off and super CID for many different HTC One devices from a few carriers, but that is because they came with hboot 1.44 so revone worked without issues to gain S-Off. If you buy a new phone now, regardless if what firmware version and/or software it come with, after you unlock the bootloader be sure the first thing you do is to make a Nandroid backup of your phone in its stock form. If it is a stock Nandroid on the newer 2.24.401.x base, please contact me as I would love to host it as many people could use that if not s-off.
If you are lucky enough to buy a new phone that comes with early hboot 1.44, I advise you get S-off right after you make that stock Nandroid backup. S-off really comes in handy for so many things. There is no danger of bricking your phone unless you start flashing things you don;t understand and other actions without fully understanding the repercussions. If you are unsure about something then just make a post and someone here should be able to provide you with the correct information.
If you don’t know what these terms mean do a search, they have been answered many, many times. Here are some quick links to some common items for modifications::
–Easily unlock bootloader, flash custom recovery, flash ROM, and ADB sideload (in case you forgot to copy your ROM to your phone) plus much more:
http://forum.xda-developers.com/showthread.php?t=2242635
–Easily get S-off by using revone (We will also use this tool reset Security back to S-On)
http://forum.xda-developers.com/showthread.php?t=2314582
***I advise you to get S-off before doing anything else and keep S-off unless you are going to return the device. The latest OTA/firmware contains an hboot that revone will not currently unlock, but if you have s-off you can downgrade your hboot if needed***
–Easily get Super CID
http://forum.xda-developers.com/showthread.php?t=2317536
Now you can do some of these things easily:
*Remove red warning from boot screen + custom hboot:
http://forum.xda-developers.com/showthread.php?t=2316726
http://forum.xda-developers.com/showthread.php?t=2156368
*Flash custom splash screens:
http://forum.xda-developers.com/showthread.php?t=2324746
*Flash new firmware:
Concise and easy for noobs: http://forum.xda-developers.com/showpost.php?p=43551752&postcount=5082
Also http://forum.xda-developers.com/showpost.php?p=43328416&postcount=33758
Post #2 has the download for the custom firmware to flash without screwing anything else up:
http://forum.xda-developers.com/showthread.php?t=2182823
______________________________________________________________________________________
Resetting your device to stock
—————————————————————————
So now for the good stuff. You totally modded the hell out of your One and something happens where you need to return the device to your carrier/vendor. First thing, always go to your carrier/vendor for hardware exchanges NOT direct to HTC. For the most part US carriers don’t care much about modded software on the devices in regards to warranty but HTC does. However just because the person in the device exchange center doesn’t check for root, doesn’t mean someone won’t flag your phone when repairing it. So why take the chance, it only takes a few minutes to return to 100% stock.
Secondly unless your device is totally unusable, I advise you to call the ATT(or your carrier) warranty number and they will send you a replacement and a return shipping label, and then you have 12 days to return it. This way you can access data and settings on your first device if needed and make sure that everything is cool with your replacement before you reset your first device to stock and send it back.
As it is required for most of the modifications mentioned above these steps require that you have your devices drivers installed on your PC and also ADB. If you need help setting up ADB: http://forum.xda-developers.com/showthread.php?t=1427008
---Instructions for returning to 100% stock from S-off:
Before we begin please note that these instructions are for a device with S-off and the stock CID. Your CID should be stock unless you changed it in order to get a specific country/region OTA or as a lot do for flashing ease and just use Super CID.
In order to run the RUU to reset everything to stock, the CID will have to match the device for which the RUU was intended.
So you can’t really mess anything up because if your CID is not correct the RUU will not run and not flash anything.
**-Technically if you have S-off you can run any RUU and it should run fine but your phones image won’t be stock from your carrier if not the correct RUU. I like to set the stock CID back now so we don’t forget. However if using another variant/RUU, since you are s-off, you can do this step after running the RUU.**
If you have stock CID or the CID matches the RUU you can proceed to step 1.
If you have any other CID you need to change it before beginning. In this example I am talking about the US ATT variant for which he stock CID is CWS__001
Code:
adb reboot-bootloader
Phone should boot to the bootloader. Now run:
Code:
fastboot oem writecid CWS__001
Now verify that the stock CID shows on the bootloader screen by running:
Code:
fastboot reboot-bootloader
Reboot device if CID on bootloader screen shows the stock CID. If not retry
*****The next step will wipe the entire contents of the device which includes all of your data. Be sure to back it up to a PC so you can transfer it onto the new device if needed.*****
These instructions are assuming you are running a Windows OS. If you are not then these exe RUU’s won’t be of much use. You will have to use the RUU.zip files which can accomplish the same results as a RUU from flashing in fastboot. You can replace step 1 below with these steps:
Restoring using a RUU.zip
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
Code:
adb reboot-bootloader
Now use these fastboot commands:
Code:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
Code:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
Code:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
Code:
fastboot reboot
or
Code:
fastboot reboot-bootloader
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.
Restoring using a RUU.exe
1. - Now we need to download the RUU (ROM Update Utility) that flash our device back to mostly stock. It can be downloaded HERE for US AT&T users. Other carriers should be able to find their appropriate RUU in this thread:
http://forum.xda-developers.com/showthread.php?t=2428276 or here: http://www.htc1guru.com/downloads/
If there is not a RUU for your phone, but there is a Stock Nandroid backup, you should still complete the step above. Just make note of your original CID and change yours to CWS__001 so the RUU will run. This will reset all your firmware and other modifications (like modified hboot and splash screens) back to the default stock level regardless of region.
Once downloaded run the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe and it will guide you through resetting the device. After it finishes your device will be almost back to stock. It will have the stock images for recovery, boot, ROM, radio, firmware hboot, etc.
Stock Nandroid restores will require these additional steps before proceeding to step 2:
When you ran the RUU (Either EXE or ZIP) all data was wiped and your custom recovery was reset back to stock, It is recommended to keep this stock recovery in place and use a command that only works on the hboot 1.44 (which you know have form the RUU)
Download the latest version of the recovery that matches the stock Nandroid backup (Either CWM or TWRP) and place it in your ADB/fastboot folder.
Now use this command to boot that custom recovery without installing it:
Code:
fastboot boot TWRP.img or fastboot boot CWM.img
It should load the custom recovery. Now make a test backup and allow it to complete.
Now boot your phone (Do not take OTA updates if prompted) and look to see where exactly the recovery placed the backup. You can install a simple file manager from the play store for this. Take note of the location and folder structure that the recovery has used for the backup.
Now copy the downloaded stock backup files from your PC to that location in the last step. Be sure the folders are in the correct place.
Now reboot into the bootloader and then boot the custom recovery again using that same command as before:
Code:
fastboot boot TWRP.img or fastboot boot CWM.img
Restore the backup and reboot when finished. Important – Do not accept any OTA updates until the complete phone reset process is finished.
Now delete all your backup files and installed applications by doing a factory reset from Settings – Backup and Reset – Erase All Data From Phone. Software and firmware on your phone should be back to stock and you can continue with the next step in the guide.
**Before continuing with the guide make sure you have changed your CID back to stock if you changed it to a non stock one in order to run a RUU to downgrade firmware.**
******If you continue with the next 2 steps to lock the bootloader and you do not have a stock hboot, you will instantly BRICK your device. Shouldn't be an issue if the RUU ran correctly, however you may want to boot into the bootloader and verify that it shows version 1.44.0000 for the hboot. Also your custom recovery should be gone and back to stock (If you boot into the stock recovery it will just look like a red warning triangle with no options). If you are still able to boot into your custom recovery, it is a sign that not all partitions have been flashed back to stock and you should find out why before proceeding]******
Now that we have lots of users who have S-Off from other methods than revone, mainly the new rumrunner method here are the generic instructions for any S-Off device and not just for user with revone:
Before you can proceed with the 2 following threads for removing Tampered and then Locking you need to have Superuser installed. There are links to how to do this in each thread. You can also use this toolkit. Just remember to delete the SuperUser and busybox apk if installed before you return the phone.
2. - First remove the Tampered Flag. Instructions are in this thread
http://forum.xda-developers.com/showthread.php?t=2477792
3. - Second Lock the bootloader. Instructions are in this thread
http://forum.xda-developers.com/showthread.php?t=2475914
The older REVONE commands/instructions for Tampered and Locking:
I recommended using revone to gain S-off, so that is how we will undo it. If you don't still have it we will need the revone file again. It can be downloaded here: http://revolutionary.io/revone (From thread: http://forum.xda-developers.com/showthread.php?t=2314582and http://forum.xda-developers.com/showthread.php?t=2315467)
Push revone to your device:
Put the downloaded revone file in your adb/fastboot folder and push it using this command:
Code:
adb push revone /data/local/tmp/
open a adb shell by typing:
Code:
adb shell
Now change to that directory:
Code:
cd /data/local/tmp
Now set permissions
Code:
chmod 755 revone
Now re-lock the bootloader:
Code:
./revone -l
Remove Tampered flag:
Code:
./revone -t
The newer revisions of revone don't do the actual locking any longer but it should output the command you need to run to fully re-lock:
Type exit to exit the adb shell session and issue the command to re-lock the device:
Code:
fastboot oem writesecureflag 3
Now verify that it worked by booting into the bootloader:
Code:
adb reboot bootloader
You should see it say LOCKED at the top and S-On, just like it was out of the box!
I doubt anyone at the warranty repair center is going to snoop around a device that says Locked and S-On, but I like to cleanup and remove the revone file.
Just reboot the phone and skip over the setup wizard
Now start another adb shell session:
Code:
adb shell
Now change back to the folder where we put revone
Code:
cd /data/local/tmp
Now run this command to delete the revone file
Code:
rm revone
Now since you had to install SuperUser to perform the previous 2 steps make sure you unroot by deleting the Superuser.apk and busybox.apk (If installed) from the /system/app folder and also the su binary from /system/xbin on your phone.
If you ran a RUU your systems firmware and software is all reset back to stock. If you restored via Stock ROM reset or Nandroid you should be running the stock software but it could be on non stock (version mismatch) firmware.
In either case your bootloader should display Locked and no Tampered just like out of the box. Now all that’s left is to S-On. To do that issue this fastboot command:
Code:
fastboot oem writesecureflag 3
Done - device should be just like it was out of the box with no indication of any modding.
*******I am not responsible for any problems you encounter. I am simply informing you of what is needed to complete a restoration to Stock. Read all steps and commands carefully and perform them in the correct order.********
Credits/Thanks
Thanks to all those with threads I mentioned that contain great info and support. Especially scotty1223 for his Tampered removal and Locking threads.
This Guide is always available at my site: http://www.htc1guru.com/guides/return-stock-guide/
[EDIT]9-10-13 Post overhaul with how to combine Nandroid and RUU process to reset.
[EDIT]10-19-13 Post was changed to reflect new S-off, so changed the Tampered and Locking steps from revone
Great guide, this should be a sticky!
Kindly excuse me and no offense to the OP. But if you have S-OFF, all you have to do is change your CID back to your original and then run the RUU and you are nearly done Next thing is you have to lock the bootloader and have S-ON and that is it. You are now back to stock.
Very helpful guide. But it can't be said enough times YOU WILL BRICK YOUR DEVICE going S-ON with a non-stock HBOOT
The guide does mention this in the relevant section, but it should probably be noted somewhere near the top of the OP. In big red letters.
Sent from my HTC One using xda app-developers app
NxNW said:
Very helpful guide. But it can't be said enough times YOU WILL BRICK YOUR DEVICE going S-ON with a non-stock HBOOT
The guide does mention this in the relevant section, but it should probably be noted somewhere near the top of the OP. In big red letters.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
That's why I think it's safer to just run the RUU because that will flash the stock HBOOT and then you can have S-ON back without the worry of bricking the device.
Nice work. But this block is incorrect and may lead to problems:
crushalot said:
2. - You will need the stock splash screen so we need to do the same procedure as above with the stock splash screen. Download the stock splash screen here: http://d-h.st/F7H (From thread:http://forum.xda-developers.com/showthread.php?t=2324746)
Rename the file so it has no spaces like stock_splash.zip and put it in your ADB/fastboot folder.
Reboot into bootloader:
Code:
adb reboot bootloader
Now run this command:
Code:
fastboot oem rebootRUU
You should see the screen turn to a silver HTC logo. Now run this command:
Code:
fastboot flash zip stock_splash.zip
If you get an output in the console that says "(bootloader) ...... Successful" proceed to next step. If any errors use this thread for troubleshooting: http://forum.xda-developers.com/showthread.php?t=2324746
Click to expand...
Click to collapse
Those splashes in my thread are designed to be flashed in recovery. They will not work in RUU mode because the zip file is constructed incorrectly for it. Best approach would be to just flash the stock splash in recovery in step one.
Alternatively, keep the instructions as is and use the stock splash from this post: http://forum.xda-developers.com/showpost.php?p=42374127&postcount=1
iElvis said:
Nice work. But this block is incorrect and may lead to problems:
Those splashes in my thread are designed to be flashed in recovery. They will not work in RUU mode because the zip file is constructed incorrectly for it. Best approach would be to just flash the stock splash in recovery in step one.
Alternatively, keep the instructions as is and use the stock splash from this post: http://forum.xda-developers.com/showpost.php?p=42374127&postcount=1
Click to expand...
Click to collapse
Yes, you are right sorry. So many threads I messed up the link. Kinda the reason I wanted to put all this in one place. I will update the OP and revise the first few steps to make it easier since the RUU should include the stock hboot and splash.
Thanks for all the feedback.
I thought you needed SU permission to run revone? Am I mistaken?
Do you need root access to push revone to the /data/local/tmp directory?
After running the RUU.exe file, wouldn't you lose root?
I just want to double check.
Dan37tz said:
I thought you needed SU permission to run revone? Am I mistaken?
Do you need root access to push revone to the /data/local/tmp directory?
After running the RUU.exe file, wouldn't you lose root?
I just want to double check.
Click to expand...
Click to collapse
No you don't need root to use it as it has a root hack in the binary itself. That's why in ieftm's post on the usage of revone to S-off has optional wording on step 3
"3. (optional) If your device is unlocked and rooted please switch to root using su."
However I can confirm that it has worked better for me when I didn't run it as SU.
No you do not need root to push files using adb, well at least not to /data. You probably would to push to /system
Correct, after running the RUU you lose root. That is why I manually flashed the hboot and splash back myself while still on my rooted rom with utilities and most importantly a recovery in which I could use to get back running and try again if something failed.
Rex2369 said:
Kindly excuse me and no offense to the OP. But if you have S-OFF, all you have to do is change your CID back to your original and then run the RUU and you are nearly done Next thing is you have to lock the bootloader and have S-ON and that is it. You are now back to stock.
Click to expand...
Click to collapse
Thanks updated post to simplify.
NxNW said:
Very helpful guide. But it can't be said enough times YOU WILL BRICK YOUR DEVICE going S-ON with a non-stock HBOOT
The guide does mention this in the relevant section, but it should probably be noted somewhere near the top of the OP. In big red letters.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks but the updated post now avoids the possibility as we just let RUU flash all stock parts
Rex2369 said:
That's why I think it's safer to just run the RUU because that will flash the stock HBOOT and then you can have S-ON back without the worry of bricking the device.
Click to expand...
Click to collapse
Thanks. Reflected in updated OP
Very nice!!! Concise and to the point!!! THANK YOU !!!
It worked like a charm, I have AT&T Version, had S-ON, SuperCID, 1.29.401.12 firmware (not AT&T), and custom ROM. This brought me back right to Stock.
Now back to AT&T, my camera lens on the inside for some reason got hazy with a hue to it after having the phone for about a month.
To the OP you have done well. Hope to see more tutorials from you.
Sent from my HTC One
great guide!
TIP for Mac Users: I couldn't get the RUU to run in Windows 7 or Windows 8 VMware environments, but Windows XP did the trick.
Use VMWare with Windows XP Pro SP3.
what ruu i need for HTC_001?
what ruu i need for HTC_001?
So running RUU does not remove S-OFF? Also does updating from stock 4.1.2 to 4.2.2 with the official OTA remove S-OFF? I want to try the OTA but I'm a bit paranoid about losing the lovely S-OFF .
No running the RUU does not remove S-off. It just resets everything else except bootloader and Security (S-off) back to stock form.
The 4.2.2 OTA does not remove remove S-off, however if you have s-off I would recommend running a custom ROM as they are already way better than the stock 4.2.2 rom.
If you want a pure stock like rom that is 4.2.2 based and better than the HTC version I would recommend ARHD or RGUI. If you like to be able to customize things a little but stay close to stock then TrickDroid is they way to go. If you really like to tinker and customize than Viper will blow your mind.
tomer861 said:
what ruu i need for HTC_001?
Click to expand...
Click to collapse
from the CID, I assume your in Europe somewhere. What is your location and carrier?
Others that I saw with that CID said there is no RUU for that CID yet. I am not sure is that has changed or not. You will have to read through this thread:
http://forum.xda-developers.com/showthread.php?p=39588860
They at least have a nandroid backup of a HTC__001 so you could restore that and as long as your hboot, splash screen and firmware are stock, you could proceed with relocking.
isnt it possible to get completly back to the way it was by putting back a nandroid backup by clockwork? (by starting clockwork, not with the flashed version)
borgqueenx said:
isnt it possible to get completly back to the way it was by putting back a nandroid backup by clockwork? (by starting clockwork, not with the flashed version)
Click to expand...
Click to collapse
Not impossible. I just went back to stock on my first HTC One using TWRP. After restoring I flashed the stock recovery, used revone to lock the bootloader and put S-ON.