I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
blackplague1347 said:
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
Click to expand...
Click to collapse
I had this issue, if you boot into bootloader does it say tampered? If not turn your phone completely off and then boot it into bootloader. Then you should be able to enter recovery. I ciuldnt enter recovery until my bootloader read tampered.
Sent from my HTC One using Tapatalk 4 Beta
You're right, it won't boot to custom recovery until it says tampered. I'm pretty sure I've rebooted several times since installing TWRP, but either way it's working (for) now. I'm not sure what the hell made it "click," but I'll take it. Thanks.
blackplague1347 said:
You're right, it won't boot to custom recovery until it says tampered. I'm pretty sure I've rebooted several times since installing TWRP, but either way it's working (for) now. I'm not sure what the hell made it "click," but I'll take it. Thanks.
Click to expand...
Click to collapse
Yeah it took me more then 10 tries until I just shut it off and then went into bootloader and there was the tampered. Glad it worked out for you.
Sent from my HTC One using Tapatalk 4 Beta
I had the same problem. I just did "adb reboot recovery" once and it worked, and it boots to recovery from the phone now every time.
blackplague1347 said:
I just unlocked my bootloader (via the toolkit) and then proceeded to install TWRP 2.5 (manually, via fastboot).
The next goal is to root the phone, but I cannot find a way to boot to recovery. I've tried using adb and I've tried it by using the volume keys and power/lock button while in bootloader mode.
The white HTC splash screen comes up with the red warning text at the bottom (the message that comes up when you're booting into a custom recovery -- I forget what it says offhand: something about a build being for development purposes or something). This splash screen is on the screen for maybe half a second before disappearing. After this happens, the normal HTC splash screen (same thing without the red text) pops up and the phone proceeds to boot normally.
This is my second One and the second time I've attempted this. The first time I had no issues, so I'm not sure what I'm doing wrong.
I've tried re-downloading/re-installing TWRP and I've tried fastboot erase cache (which I didn't know about until having searched for a fix). No error messages popped up at any point during the flashing process, so I'm quite confused.
Has anyone else had this happen and if so, how did you fix it?
Click to expand...
Click to collapse
im still having the same problem after allot of tries is there some sort of fix ?
Fastboot Tampered?
im still having the same problem after allot of tries is there some sort of fix ?
Click to expand...
Click to collapse
At the top of your devices when at the fastboot screen does it say Tampered?
Corey.C said:
At the top of your devices when at the fastboot screen does it say Tampered?
Click to expand...
Click to collapse
Yes mine says that. I am a new to this, what do i need to do
I kept getting the "set metadata error" on the latest Android Revolution HD rom so installed the latest version of CWM recovery but I kept getting the same error upon installing the rom. However, this time my phone is really screwed up. I cannot get back into CWM to restore my last backup, when I get the little "entering recovery" text on the top of my phone the screen goes black and then flashes something on the screen and that's it. I plugged the phone into my pc and followed the instructions for flashing TWRP recovery but again...when I try to enter recovery this time the TWRP log flashes and then it disappears. For some reason it also appears I am S-ON now as well! I can connect the phone and go to FASTBOOT USB and type "fastboot devices" and my phone shows up but no matter what I do I cannot get into TWRP to restore. What the heck do I do?!
type fastboot clear cache and try again
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 (starting BL unlocked w most recent Sony stock .291 firmware) rooted and flashed with TWRP and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using rocker00's guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) and Gapps (A-GAPPS+6.0.1_14.05.2016_v5.2.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen (cm-12.1-20161016-NIGHTLY-sirius.zip). Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I rooted fine (same SuperSU as before) and started installing apps via Google restore. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP using the tool from rocker00's post with the phone in fastboot mode. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect, although I would get the android robot with the blue progress once before it reboot into the bootloop.
2) With the phone in flashmode I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect (i think the phone needs to be booted for this tool to work).
3) I've tried all the relevant commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
epeace said:
Hi Im new to the forum but I am finding it to be a massive resource for all things technical android. I am also new to rooting android but am technically savvy, (10 years in IT will do that). Initially it went just fine, even if a speed bump here or there. I got my Sony Z2 rooted and flashed with TWRP (twrp-3.0.2-0-sirius.img) and SuperSU (UPDATE-SuperSU-v2.76-20160630161323.zip) using this guide. I was then able to successfully flash ParanoidAndroid's latest (pa_sirius-6.0.3-20160809-signed.zip) using TWRP recovery. I got a minor bootloop trying to get PA running, but re-flashing seemed to clear it up. It seemed to work fine although I couldn't figure out how to get the pie controls or the halo notifications to work. Without those things i couldn't see the point, so I decided to try Cyanogen. Apparently this uses a different recovery (CWM), I was a little worried but went for it anyway. It seemed to be fine after the first reboot. I started installing apps, rooted fine. But after the next reboot, it started bootlooping. First it would cycle between the Sony screen and a blank screen, But after trying a bunch of things (I'll detail below), it just hangs at the Sony screen indefinitely.
So, what I've tried till now to fix it is:
1) First I tried to reinstall TWRP. The flash went without error, but did not fix the problem. I have not been able to get into recovery since the bootloop. In the process I also did a fastboot -w, which also seemed to have relatively no effect.
2) I tried flashtooling the kernel again with the same from rocker00's post (D6503_23.5.A.0.575_kernel.ftf). No effect. I also tried flashing recovery a few more times using the script from his post to no effect.
3) I've tried all the commands from this page and this page, hoping to eradicate whatever errant code is screwing with my phone. Since fastboot seems to be the only way to interact with my phone. I tried:
Code:
fastboot flash recovery /path/to/twrp-3.0.2-0-sirius.img
fastboot -w
fastboot update /path/to/pa_sirius-6.0.3-20160809-signed.zip
the attempt to flash PA through fastboot errored with a message about not having "android-info.txt".
I also desperately tried:
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
the one about data errored. the others seemed fine, but didn't change the situation.
This guide was informative yet quite useless to me, since I definitely don't want to start scripting my phone 2 days after starting this stuff. I've also scoured this forum and others for similar situations, which I've found but they all seemed to get resolved by either doing stuff I've already tried or from having a completely irrelevant problem to my own..
I'm really scratching my head here because it is all stock TWRP and Android or should be by now. adb commands aren't connecting due to stock android not having USB debugging enabled, and without being able to boot into the settings I can do nothing to change that. So all I have is fastboot. I also have a TWRP backup image I made before installing PA but till now Ive seen no way to restore it without booting into recovery.
Any help please!!!! This can't be bricked!!
Click to expand...
Click to collapse
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
iXaidyiu said:
Welcome to XDA!
May I know what fw version did you initially start with? .575 or .291 or any others?
Click to expand...
Click to collapse
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
epeace said:
Hi iXaidyiu,
I started with .291. i stopped going back to it after the first time as I noticed that the custom recovery stopped working in .291. I have had it at .575 since then. And of course now that I can't get into recovery .291 is not an option unless I find an ftf of it for flashtool.
Another observation I forgot to mention is that I cannot turn the thing off. I have to force quit it (vol up + power) and after a second it boots up again to get stuck at Sony screen. I have noticed that if I do the flash boot buttons (vol down + power) I get a different Sony screen (without the xperia logo). But it sticks just the same. I don't even know if the phone is charging at this point, although it was on the Sony screen all night so there must be some charging happening. How could this have gotten so screwed up? It was working fine and I was doing benign activities at the time it choked
Click to expand...
Click to collapse
Well if so, let's just start from scratch, because you seems to have screwed quite badly and complicated.
Firstly, flash .291 firmware with the three boxes under "Wipes:" ALL CHECKED, check also "AUTO_BOOT" on the right column. These steps will return your device into factory state.
After the flashing process has finished, if your device turned on automatically, turn it off, then unplug the device and replug it when pressing vol+ key, this will enter fastboot mode, you can have two ways to follow now:
(1) Select "Flash", "Fastboot Mode", "Select kernel to flash", navigate to the directory that contain the kernel downloaded (I personally recommand Elite Kernel and extracted), then flash the .IMG file;
(2) Open a cmd using shift+R mouse on the blank space in the directory that stores your twrp.IMG (you can download it here), and type in:
Code:
fastboot flash recovery <filename>.img
and press Enter.
In both method, after you have pressed Enter and see there are two "Okay" printed in the CLI, unplug your device and boot it.
During boot, you will see yellow or green LED light blinked, press vol+ button once and hurray, you will be booted into TWRP recovery!
Now you can load your zip onto your SD card and start flashing! Happy flashing!
P's1 When you tried to boot up your device with the vol- button pressed together, you will be booted into SAFE_MODE, in this mode all 3rd party applications will be disabled.
P's2 I personally DO NOT recommend you to flash zip or erase anything using fastboot commands, use TWRP instead
Thank you iXaidyiu. Option 1, although it fails to boot normally, was successful in getting me back into recovery! Now that I'm in recovery, I first tried to restore my back up. But this failed with errors:
Code:
Failed to mount '/system' (Invalid Argument)
Failed to mount '/data' (Invalid Argument)
Failed to mount '/cache' (Invalid Argument)
So then I tried to flash PA again (since that was the only rom I had on my sd card right now) which also failed with the same errors plus new ones:
Code:
Failed to mount '/data' (Invalid Argument)
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Download/pa_sirius-6.0.3-20160809-signed.zip'
It also said that "This package is for "sirius" devices; this is a "".". Apparently my Z2 is no longer identifying as 'sirius'. I checked the file system, and I can see that the /data, /cache, and /system folders are physically there. Why are they not mounting? Permissions? :s What to do from here?
UPDATE: This "Failed to mount /data error" seemed to be the root of all the problems till now. Others on the net with this error also see boot hanging at the mfr logo. However, I was able to solve it by formatting /data. I still couldn't flash PA due to the 'This package is for "sirius" devices' error, but I was able to restore my TWRP backup, which then solved the "sirius" ID issue, after which I could flash PA just fine! Thanks iXaidyiu for your help in getting me back into recovery! That was clutch to me finding the solution!
@epeace
If you ever face the device id issue again, unzip the ROM, navigate down /META-INF/com/Google/Android/updater-script and delete the following line:
Code:
getprop("ro.product.device") == "sirius" ||
abort("E3004: This package is for \"sirius\" devices; this is a \"" +
getprop("ro.product.device") + "\".");
(probably the first of the code till a semi-colon)
This disable the Device ID check when you flash the ROM.
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Ok great tip, I'll make that edit for next time. Re: the charging, I think it's charging, but it's definitely charging very slow. But a number of things could be contributing to that, I'm constantly on it right now (setting it up), i'm charging off of my computer (usually slow to begin with), and this phone is a few years old so the battery is not what it used to be. I'll keep an eye on it the next days, and report back here and let you know what I've observed. Thanks again for your help!
iXaidyiu said:
@epeace
P's May I know how's your phone charging status? I am curious cuz' I once tried flashing PA 6.0.3 and all working good EXCEPT the battery cannot be charged. It keeps draining itself even though it can sense the presence of the charger but it still cannot charge:crying:
Click to expand...
Click to collapse
Hey @iXaidyiu,
I no longer have PA installed, but in the couple days with it I didn't notice any difference in battery performance compared to other ROMs. I think that shouldn't be a deterrent. At the moment I'm trying out GarvityBox on rcstar6696's vanilla MM/Nougat. So far it feels right, although rooting was a little tricky for some reason. We'll see how that goes!
My One M9 is stuck on boot screen and I've tried everything. This was just given to me it wasn't brand new though. When I do volume down and power button it just goes to HTC black screen and silver logo then reboots after 2 seconds. When I go to recovery mode to format data and cache it shows data can't be mounted. When I try to install RUU it says low battery when I go on Fastboot mode. And I also tried to install the ruu zip on recovery and it also shows the mount error. I also tried to unlock the bootloader but I can't do it because the OEM UNLOCK option in developer mode is not checked.
My bootloader screen shows
Software: modified
Locked
S-on
I'm so desperate right now I don't know what to do.
I'm having a similar issue. It started with the settings application on my phone apparently getting corrupted. I could no longer open it and couldn't do things like turn WIFI and GPS on and off, also Maps would crash just after launching. This was...inconvenient, as I was on a business trip at the time. Fortunately I had my work phone as a backup. Unfortunately, as I had just bought a larger SD card, I hadn't copied any of my backups over. By the time I got home, the phone would not reboot to the system at all, it just gets stuck on the white HTC screen.
I can still get into recovery/fastboot/download mode, and can still connect via USB in these modes. I first tried to reflash a few different backup ROMS, and some fresh ones. They all had the error "cannot mount /system". I also found out that I couldn't get to the data or system image partitions. After digging around in TWRP, I found that they have a size of 0MB. Looking around various threads, I read that an RUU has a good chance of restoring this, so I tried that out.
I ran into another problem with the RUU...no matter what my battery is charged to, the RUU will not start the install. It fails saying that the battery must be charged above 30%. This is was after I left it plugged in overnight. When powered off, it reads 100%. TWRP also registers it at 100%.
I have also tried extracting the stock ROM from the RUU to flash in TWRP, but no matter how many times I try the .zip that I find in the temp directory says that it is corrupted.
I am Modified/UNLOCKED/S-ON, does anyone have any ideas? I really appreciate any help!
Someone help us, please. Thank you!
Real quick back story: Originally this device was being rooted to try to perform some data recovery after a factory reset. Everything went fine to unlock boot loader and root phone, TWRP was used as a recovery manager, but after installing SuperSU it wouldn't load from the booted device (error about binaries missing when clicking its icon). So a newer SuperSU zip was found and installed, and then the phone bricked on reboot. Just would freeze at the HTC logo with white background.
Fast forward to no longer needing the data recovery, just want to restore back to working condition. The boot loader was relocked and the latest RUU package from HTC was downloaded for AT&T build. Booting to the boot loader and setting it to fastboot USB, everything works fine running RUU (tells me current OS version and what it will flash to, etc) until it gets to the point where it says it needs to reboot to the bootloader on the RUU software (even though that is where I am initiating RUU flash from in the first place). The phone reboots to a black screen with HTC logo, and then the RUU software gets error 171 that it cannot communicate with the device. When RUU gets an error, there is no retry, only exit and start again. I read on another post someone said don't worry if this happens, just hit exit, run RUU again and it will pick up and continue to flash. However when you click exit on RUU, the phone reboots back to the white screen with HTC logo and hangs there.
Does anyone have any advice to get this device back to a stock android install? Thanks. If there is a better sub forum for this question, please let me know and I will post there.