I'm running into a few problems trying to wipe all my data/revert to stock using a RUU.
The first problem I'm running into is relocking my bootloader. When the device is on, the computer recognized the adb interface (adb devices), but as soon as I reboot to bootloader (adb reboot bootloader), the device isn't recognized anymore.
Additionally, the RUU won't recognize the device either.
I speculate that the CM 13 (I'm running the resurrection remix ROM) installed on my M9 is the culprit. I will try to flash the stock rooted rom (Badboys) and lock the bootloader after that.
I'm currently on OS-3.41.651.4 firmware.
UPDATE: I went ahead and downloaded official RUU from HTC, extracted the rom.zip via processing monitory, and then manually flashed it using the OPJAIMG method. Fingers crossed for working adb so I can relock the bootloader.
Related
So I just got my One a few days ago and decided to root, unlock my bootloader, and flash a new rom. I unlocked, rooted, flashed twrp recovery and before I flashed a new rom, i wiped and ended up removing the roms from storage. Now i have no os to boot up into. No way to transfer a rom to the phone because clockwork and twrp dont support usb storage, adb sideload keeps failing, and ruu's wont install...on stock 4.3 ota from att....plz help.....
jm5503 said:
So I just got my One a few days ago and decided to root, unlock my bootloader, and flash a new rom. I unlocked, rooted, flashed twrp recovery and before I flashed a new rom, i wiped and ended up removing the roms from storage. Now i have no os to boot up into. No way to transfer a rom to the phone because clockwork and twrp dont support usb storage, adb sideload keeps failing, and ruu's wont install...on stock 4.3 ota from att....plz help.....
Click to expand...
Click to collapse
I use a usb OTG in TWRP almost everyday
and if sideload is failing it's likely because you don't have the drivers installed properly
and so you know the unlock is what wiped the phone not TWRP (unless you choose advanced and selected to wipe the sdcard which no one does)
get you drivers working
to test from recovery on the phone and command on the PC do adb devices and make sure you device is listed.
then in twrp you choose advanced/adb sideload
Connect phone to PC
Open command line where you have the file of ROM assuming you have ADB in Path of system, if you have not just copy the ROM to same place you have ADB files.
Type:
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
jm5503 said:
So I just got my One a few days ago and decided to root, unlock my bootloader, and flash a new rom. I unlocked, rooted, flashed twrp recovery and before I flashed a new rom, i wiped and ended up removing the roms from storage. Now i have no os to boot up into. No way to transfer a rom to the phone because clockwork and twrp dont support usb storage, adb sideload keeps failing, and ruu's wont install...on stock 4.3 ota from att....plz help.....
Click to expand...
Click to collapse
Thank you....
Sent from my HTC One using xda app-developers app
Hi all,
chronological steps to bootloop after rebooting, when no os warning sign appeared.
Successfully Unlocked boot loader.
Successfully install twrp custom recovery
installing root wasn't successful.
Then I tried to check features of TWRP which resulted in always booting to recovery.
I might have deleted some data accidentally​
Then after many attempts to restore to stock rom I flashed RUU 1.26 from guru's website ...
Phone booted but had touch screen issues.
In an attempt to fix I realized that I could only do with s-off and then tried to flash the correct RUU for 3.17.502.3 firmware but wasn't successful.
I realized the present RUU(1.26.X) might be the reason for all(any .zip) failures from twrp.
I tried to format system and push RUU for 3.17.502.3. But I accidentally rebooted when there was no OS warning came up. It got stuck in Bootloop with HTC logo. My attempts to power it down didn't work and when I press power button + volume down or just power button the led back lights on the home and back buttons flash.
firmware version 3.17.502.3
hboot 1.55 s-on
Phone shows up as HTC MTP device because of which adb/fastboot doesn't recognize the phone.
I guess this is what a brick is called. Is there a way to recover from this ?
Few questions:
1. How can I power off the device? Its been in bootloop for 6 hrs now. I'm afraid the screen will go bad
2. How can I use adb/fastboot in mtp modes to get it to power off / reboot to boot loader?
Thanks in advance.
PS: I have tried all these stuff(rooting, flashing custom recovery / kernels) on 3 samsung phones with out any issue, the procedure was much easier than it is for htc devices. After a day long attempt to root my phone I might have bricked it
Sriram
clrsri2006 said:
Hi all,
chronological steps to bootloop after rebooting, when no os warning sign appeared.
Successfully Unlocked boot loader.
Successfully install twrp custom recovery
installing root wasn't successful.
Then I tried to check features of TWRP which resulted in always booting to recovery.
I might have deleted some data accidentally​
Then after many attempts to restore to stock rom I flashed RUU 1.26 from guru's website ...
Phone booted but had touch screen issues.
In an attempt to fix I realized that I could only do with s-off and then tried to flash the correct RUU for 3.17.502.3 firmware but wasn't successful.
I realized the present RUU(1.26.X) might be the reason for all(any .zip) failures from twrp.
I tried to format system and push RUU for 3.17.502.3. But I accidentally rebooted when there was no OS warning came up. It got stuck in Bootloop with HTC logo. My attempts to power it down didn't work and when I press power button + volume down or just power button the led back lights on the home and back buttons flash.
firmware version 3.17.502.3
hboot 1.55 s-on
Phone shows up as HTC MTP device because of which adb/fastboot doesn't recognize the phone.
I guess this is what a brick is called. Is there a way to recover from this ?
Few questions:
1. How can I power off the device? Its been in bootloop for 6 hrs now. I'm afraid the screen will go bad
2. How can I use adb/fastboot in mtp modes to get it to power off / reboot to boot loader?
Thanks in advance.
PS: I have tried all these stuff(rooting, flashing custom recovery / kernels) on 3 samsung phones with out any issue, the procedure was much easier than it is for htc devices. After a day long attempt to root my phone I might have bricked it
Sriram
Click to expand...
Click to collapse
UPDATE : The reboot to boot loader via power button + volume down works but it took about 2 mins of holding those buttons, which is unusually long time. So its not a brick As experienced developers say DO NOT PANIC, staying calm and read the forums thoroughly has helped.
I'm trying to see how I can fix the .zip install failures now.
Search for adb sideload, adb push or usb-otg
Sent from my HTC One using XDA Premium 4 mobile app
TopoX84 said:
Search for adb sideload, adb push or usb-otg
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
adb sideload isn't working though adb / fastboot work fine.
did try adb push a dirty unicorn rom and tried to install, just to test, it didn't work either
The problem i'm facing now is:
I have installed 1.26 RUU on 3.17.502.3 because that is the only RUU with cid CWS_001 which started all the issues.
From then i'm not able to install any zip files. Now that i deleted the system thinking i can flash another RUU I keep getting error: unable to mount cache. when ever i try to install something.This is one problem the other is for flashing an RUU i need s-off and for getting s-off i need to have ROM that matches with my firmware version(which i'm not able to get) Its kind of deadlock situation i guess.
As I have 1.55 hboot revone doesn't work and tools based on rumrunner fail at second test because when they reboot its going to fastboot usb mode and fails at that point.
clrsri2006 said:
adb sideload isn't working though adb / fastboot work fine.
did try adb push a dirty unicorn rom and tried to install, just to test, it didn't work either
The problem i'm facing now is:
I have installed 1.26 RUU on 3.17.502.3 because that is the only RUU with cid CWS_001 which started all the issues.
From then i'm not able to install any zip files. Now that i deleted the system thinking i can flash another RUU I keep getting error: unable to mount cache. when ever i try to install something.This is one problem the other is for flashing an RUU i need s-off and for getting s-off i need to have ROM that matches with my firmware version(which i'm not able to get) Its kind of deadlock situation i guess.
As I have 1.55 hboot revone doesn't work and tools based on rumrunner fail at second test because when they reboot its going to fastboot usb mode and fails at that point.
Click to expand...
Click to collapse
UPDATE : After many attempts I could work it out by using guru reset .zip file (1.26.502.12). I did this before as well but was not able to get s-off previously. This time I asked to install superuser when resetting using guru reset file. I got the 1.26 one back with disabled touchscreen. Then I used rumrunners and got s-off and then used the ruu for 3.17.502.3 exe file to get the working on.
Now the bootloader just says unlocked but not tampered. I got the twrp recovery again as it was very handy for me.
I was able to get supercid. Now trying for ARHD 51.0.
After I got the RUU for 3.17.502.3 the only issue i noticed is that when phone boots up I just see HTC instead of "HTC quitely brilliant"
Basically, I need the 4.4.2 OTA.
I unlocked the bootloader. I need root to get S-off. Except I'm currently on S-on and the only way to install a recovery and get root is to have S-off (correct me if I'm wrong). Any workaround to this that isn't super complicated?
I've checked USB ports, and I can't seem to get my device to be recognized. "fastboot devices" shows up nothing. Currently unlocked, and S-on.
Forgot that unlocking bootloader again would wipe my phone, forgot to make backup, so everything's deleted ;(. Not possible to get s-off anymore?
Any help would be appreciated.
mch277 said:
Basically, I need the 4.4.2 OTA.
I unlocked the bootloader. I need root to get S-off. Except I'm currently on S-on and the only way to install a recovery and get root is to have S-off (correct me if I'm wrong). Any workaround to this that isn't super complicated?
I've checked USB ports, and I can't seem to get my device to be recognized. "fastboot devices" shows up nothing. Currently unlocked, and S-on.
Forgot that unlocking bootloader again would wipe my phone, forgot to make backup, so everything's deleted ;(. Not possible to get s-off anymore?
Any help would be appreciated.
Click to expand...
Click to collapse
You just need an unlocked bootloader to install a recovery, when you are in fastboot (if you turn the phone on and do adb reboot fastboot, or hold down vol down and power and select fastboot when the HBOOT menu comes up) you can do the command line fastboot flash recovery recovery.img (recovery.img being your recovery you want to load) you can then start the phone up, copy superuser.zip on there somewhere and install with your custom recovery.
All that said, you don't need to do any of that to do 4.4.2 OTA, and in fact it wont install if you have a custom recovery. Are you having a problem that it wont download/install. If your phone is stock other than an unlocked bootloader it will install (trust me i just did it). If you have stock recovery just download the 4.4.2 OTA file from the other thread, then save it to the phone somewhere, the go to recovery in HBOOT, wait 1 second and then hold up vol and power for 5 seconds (may have to do this more than once). Menu comes up, do wipe cache, and then do install from device storage.
After thats done you can follow my above instructions and root it
Sorry if I didn't state it more clearly, but my issue is I can't install a recovery. I can boot into bootloader and fastboot but when I type in "fastboot" devices on my PC nothing comes up.
mch277 said:
Sorry if I didn't state it more clearly, but my issue is I can't install a recovery. I can boot into bootloader and fastboot but when I type in "fastboot" devices on my PC nothing comes up.
Click to expand...
Click to collapse
Have you installed HTC Sync? When you boot into the bootloader then fastboot and then plug in your usb cable does it say "fastboot usb" on screen?
Rogue Leader said:
Have you installed HTC Sync? When you boot into the bootloader then fastboot and then plug in your usb cable does it say "fastboot usb" on screen?
Click to expand...
Click to collapse
I uninstalled HTC sync so as to not have it interfere with any s-off/etc. programs. I still have HTC drivers installed. Re-install both HTC sync and drivers?
mch277 said:
I uninstalled HTC sync so as to not have it interfere with any s-off/etc. programs. I still have HTC drivers installed. Re-install both HTC sync and drivers?
Click to expand...
Click to collapse
HTC Sync won't interfere with anything. You need that and the drivers installed for it to work, I would start there and see what happens.
I'll re-install it again.
Is there anything I can do to just completely get back to stock everything? Willing to manually update it but I'd like to be able to just go to settings and just update via OTA from there.
mch277 said:
I'll re-install it again.
Is there anything I can do to just completely get back to stock everything? Willing to manually update it but I'd like to be able to just go to settings and just update via OTA from there.
Click to expand...
Click to collapse
As long as you have an active AT&T SIM card in there it will update even with an unlocked bootloader, even if its rooted. As long as you didn't mod anything. I just did the update like this, it worked fine.
I've rooted and unlocked the bootloader before but I've unrooted since then. Is there still a chance I just haven't gotten the update pushed to my device yet?
mch277 said:
I've rooted and unlocked the bootloader before but I've unrooted since then. Is there still a chance I just haven't gotten the update pushed to my device yet?
Click to expand...
Click to collapse
here's the OTAPkg.zip with instructions
http://forum.xda-developers.com/showthread.php?t=2659374
clsA said:
here's the OTAPkg.zip with instructions
http://forum.xda-developers.com/showthread.php?t=2659374
Click to expand...
Click to collapse
Thanks. I have that file all ready to go in my folder. Only problem I have now is that I can't get s-off. I've installed recovery + custom kernel but the su binaries are outdated for both superSU and superuser. I've tried to flash a 4.3 version of superSU only to have the same error.
I followed instructions for root after I flashed a super tool I also flashed a custom kernel. After I rebooted is where I started to get the "outdated binaries" prompts.
mch277 said:
Thanks. I have that file all ready to go in my folder. Only problem I have now is that I can't get s-off. I've installed recovery + custom kernel but the su binaries are outdated for both superSU and superuser. I've tried to flash a 4.3 version of superSU only to have the same error.
I followed instructions for root after I flashed a super tool I also flashed a custom kernel. After I rebooted is where I started to get the "outdated binaries" prompts.
Click to expand...
Click to collapse
Ok that changes things. IMO you need to backup your data, install the 4.3 RUU to wipe everything out and make sure you have stock recovery, then you can install the OTA zip from stock recovery, or go ahead and download it direct from AT&T. You can then root and go from there. Now as for S-Off if you have HBOOT 1.55 or newer I don't think you can get it. I can't get it on mine I tried every way possible. You don't need S-Off for this to work
So I have a HTC One M8 (at&t) on Android 4.4.2.
Its a Deodexed pre-rooted Sense rom
it has TWRP as the bootloader
if it matters, xposed framework is installed.
I cannot S-Off. Out of the question. I am S-On.
I go do the OTA, it downloads, it reboots into TWRP, then does nothing when it goes to the main menu. I can reboot the phone to system and it boots normally into 4.4.2, but I cant update to 4.4.4
How do I fix this?
*Edit* Did some looking around, I think the issue is I have to be stock recovery and stock rom, so I downloaded them from http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966 and got the firmware 1.58.502.1 versions, I checked with my phone to make sure its the right version.
*Edit 2* Will just installing the stock bootloader work? If not, I got the stock backup as well.
LightningKitsune said:
So I have a HTC One M8 (at&t) on Android 4.4.2.
Its a Deodexed pre-rooted Sense rom
it has TWRP as the bootloader
if it matters, xposed framework is installed.
I cannot S-Off. Out of the question. I am S-On.
I go do the OTA, it downloads, it reboots into TWRP, then does nothing when it goes to the main menu. I can reboot the phone to system and it boots normally into 4.4.2, but I cant update to 4.4.4
How do I fix this?
*Edit* Did some looking around, I think the issue is I have to be stock recovery and stock rom, so I downloaded them from http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966 and got the firmware 1.58.502.1 versions, I checked with my phone to make sure its the right version.
*Edit 2* Will just installing the stock bootloader work? If not, I got the stock backup as well.
Click to expand...
Click to collapse
Copy the recovery to the folder where you have ADB and Fastboot executables/drivers on your computer and rename the file recovery.img
0. Make sure you have drivers required to use ADB and Fastboot loaded on your computer
1. TWRP is the recovery, not the bootloader
2. Boot into recovery (TWRP) and do a backup
3. From TWRP, reboot to bootloader
4. Connect your phone to your computer while the phone is still in fastboot mode
5. Make sure your phone's bootloader lists Fastboot as how it's connected
6. Make sure you have drivers required to ADB and Fastboot to your phone. Search this forum for info
7. On your computer, from a command prompt, go to the folder with the ADB/Fastboot drivers/exe files and that also contains the new recovery you downloaded and renamed.
8. In the command prompt, issue the following command:
fastboot flash recovery recovery.img
You will now have the original Stock HTC recovery for your 4.4.2 1.58.502.1 version.
Reboot the phone and check for an OTA update.
Once you have upgraded the phone, it will still have stock recovery, and won't have root, so you'll need to re-load TWRP (look for the latest version on this forum) just like you loaded the stock recovery, and then re-root.
Note:
I did this yesterday (OTA) and don't like 4.4.4. I reverted back to 4.4.2 and it's fine for me. Nothing in 4.4.4 is an advantage for me. Just my personal opinion, though.
DanGeorges said:
Note:
I did this yesterday (OTA) and don't like 4.4.4. I reverted back to 4.4.2 and it's fine for me. Nothing in 4.4.4 is an advantage for me. Just my personal opinion, though.
Click to expand...
Click to collapse
Well it's not only just for 4.4.4, but to return to stock seeing as I rooted to get firewater to work after a failed rom flash. That and my 2 year contract is almost over so I'll be able to get the m9, so I'll be able to sell my phone as stock.
Does anyone have a link to the OTA?
toby12188 said:
Does anyone have a link to the OTA?
Click to expand...
Click to collapse
PM me for the link to the actual OTA zip file. I'm not sure how it can be used, but I grabbed it.
DanGeorges said:
Copy the recovery to the folder where you have ADB and Fastboot executables/drivers on your computer and rename the file recovery.img
0. Make sure you have drivers required to use ADB and Fastboot loaded on your computer
1. TWRP is the recovery, not the bootloader
2. Boot into recovery (TWRP) and do a backup
3. From TWRP, reboot to bootloader
4. Connect your phone to your computer while the phone is still in fastboot mode
5. Make sure your phone's bootloader lists Fastboot as how it's connected
6. Make sure you have drivers required to ADB and Fastboot to your phone. Search this forum for info
7. On your computer, from a command prompt, go to the folder with the ADB/Fastboot drivers/exe files and that also contains the new recovery you downloaded and renamed.
8. In the command prompt, issue the following command:
fastboot flash recovery recovery.img
You will now have the original Stock HTC recovery for your 4.4.2 1.58.502.1 version.
Reboot the phone and check for an OTA update.
Once you have upgraded the phone, it will still have stock recovery, and won't have root, so you'll need to re-load TWRP (look for the latest version on this forum) just like you loaded the stock recovery, and then re-root.
Note:
I did this yesterday (OTA) and don't like 4.4.4. I reverted back to 4.4.2 and it's fine for me. Nothing in 4.4.4 is an advantage for me. Just my personal opinion, though.
Click to expand...
Click to collapse
All of this would work great except for one thing.
Stock is odex not deodex. So the ota would fail.
To take an ota you need to be 100% stock on /system (root is fine ) and on stock recovery.
LightningKitsune said:
Well it's not only just for 4.4.4, but to return to stock seeing as I rooted to get firewater to work after a failed rom flash. That and my 2 year contract is almost over so I'll be able to get the m9, so I'll be able to sell my phone as stock.
Click to expand...
Click to collapse
dottat said:
All of this would work great except for one thing.
Stock is odex not deodex. So the ota would fail.
To take an ota you need to be 100% stock on /system (root is fine ) and on stock recovery.
Click to expand...
Click to collapse
I missed the deodexed part. Sorry about that.
Another way:
Backup your personal data
Relock bootloader
RUU: http://www.htc.com/us/support/htc-one-m8-att/news/
Hi there,
I would really appreciate any help at all. My device is stuck in bootloop but its adb and fastboot work properly. USB debugging is off and bootloader is locked.
What I have already tried:
1 - to flash any rom through fastboot: impossible, bootloader is locked
2 - to adb sideload an older rom OTA: no rom will be accepted, since NBD90W is the last one and you can't downgrade this way
3 - to adb sideload current rom OTA: works just fine, only thing I could do so far, but the phone remains in bootloop
4 - install a custom recovery through fastboot image.img: impossible, bootloader is locked
ipaulino84 said:
Hi there,
I would really appreciate any help at all. My device is stuck in bootloop but its adb and fastboot work properly. USB debugging is off and bootloader is locked.
What I have already tried:
1 - to flash any rom through fastboot: impossible, bootloader is locked
2 - to adb sideload an older rom OTA: no rom will be accepted, since NBD90W is the last one and you can't downgrade this way
3 - to adb sideload current rom OTA: works just fine, only thing I could do so far, but the phone remains in bootloop
4 - install a custom recovery through fastboot image.img: impossible, bootloader is locked
Click to expand...
Click to collapse
You're better off looking in the device-specific forum.
http://forum.xda-developers.com/nexus-5x
Unfortunately, I don't see a way to fix your problem that doesn't involve erasing your user data. You may have better luck in the subforum.
I don't care about my data. I'm giving up this phone after the last thing I've tried: I have successfully installed marshmallow (finally) through LGUP, and after I reboot it... stuck in bootloop! I don't know what this device problem is, but believe its a tiny hardware problem that will allow it to flash roms through various methods, while keep it stuck in bootloop. Does this make any sense at all?
Unlock the bootloader and flash a factory image.
Do a factory reset then flash latest stock rom