I'm running the stock at&t ROM with Android 6. I've successfully unlocked the Bootloader, and have taken S Off (paid SunShine!)
When I boot into Recovery Mode I cannot install from SD without getting a Signature Error. When I attempt to flash TWRP via ADB/Fastboot the bootloader will freeze at prompting the Recovery Mode (only way to overcome is to reflash stock rom).
Any ideas? Was hoping to install LineageOS as I read at&t won't be issuing an OTA for HTC as they've discontinued offering the brand.
Set download mode. Then flash twrp with fastboot command. Fastboot flash recovery twrp.img Should workout just fine.
Nope. Read initial post. After flashing handset hangs when Recovery Mode is selected
StarSage said:
Nope. Read initial post. After flashing handset hangs when Recovery Mode is selected
Click to expand...
Click to collapse
Perhaps its the version of TWRP you are trying to install? Maybe you might have to try an older version since your on 6.0....?
Also, I have the same AT&T device (unlocked bootloader, but S-ON) and am curious about installing custom bootloader/ROM on this device.
Let us know if/when your able to solve it!
So, I downloaded the Windroid Toolkit at https://forum.xda-developers.com/showthread.php?t=2499926 but now I can't get passed the HTC boot screen. I installed Lineage OS, did Wipe Dalvik Cache, then installed Gapps. But no desktop after install. HELP!
Related
Problem: After installing CWM, the phone won't boot fully. It goes to the HTC screen (with some new red text about this being a development-only build) and then reboots to the same screen over and over.
What I've done based on what I've read here:
Cleared the caches in fastboot and rebooted.
Run the unlock token script again.
Installed TWRP, wiped everything.
Attempted to flash CM9 through TWRP (fails).
Attempted to install Scott's Roms 1.85 ROM throught TWRP (failed).
Reinstalled CWM to try to flash Scott's 1.85, but CWM will not go into recovery mode (just goes to the HTC screen and starts boot loop again).
Attempted to install CM9 and Scott's 1.85 through flashboot, no luck because of missing text files (am I using the wrong package?).
Factory reset just takes me to TWRP, and when I try to factory reset from there it goes back into bootloop.
What does work:
I can get to Fastboot on phone.
With TWRP installed, I can into TWRP recovery.
Does anyone have any thoughts on this?
Thanks.
makanai said:
Problem: After installing CWM, the phone won't boot fully. It goes to the HTC screen (with some new red text about this being a development-only build) and then reboots to the same screen over and over.
What I've done based on what I've read here:
Cleared the caches in fastboot and rebooted.
Run the unlock token script again.
Installed TWRP, wiped everything.
Attempted to flash CM9 through TWRP (fails).
Attempted to install Scott's Roms 1.85 ROM throught TWRP (failed).
Reinstalled CWM to try to flash Scott's 1.85, but CWM will not go into recovery mode (just goes to the HTC screen and starts boot loop again).
Attempted to install CM9 and Scott's 1.85 through flashboot, no luck because of missing text files (am I using the wrong package?).
Factory reset just takes me to TWRP, and when I try to factory reset from there it goes back into bootloop.
What does work:
I can get to Fastboot on phone.
With TWRP installed, I can into TWRP recovery.
Does anyone have any thoughts on this?
Thanks.
Click to expand...
Click to collapse
Uhhhhh...try to relock your bootloader (fastboot oem lock) and run an RUU. You'll go back to stock. Then follow these steps:
1. Re-unlock your bootloader using the same unlock token you used before
2. Flash TWRP from fastboot (or a one-click)
3. Reboot into TWRP
4. Mount storage and put whatever rom you want into whatever folder you want on the sdcard (CM9 Alpha 5, CleanROM, AOKP M6.2, etc etc)
5. Factory Reset
6. Flash the rom and anything that needs to go with the rom (like Gapps if you're flashing CM9 or AOKP)
7. Reboot and enjoy, be sure to update your SU binaries immediately after booting by opening up the SuperUser app
Also, do not use CWM, our device is not officially supported by the CWM team. Only TWRP is an officially supported recovery for our HOX.
stnguyen09 said:
Uhhhhh...try to relock your bootloader (fastboot oem lock) and run an RUU. You'll go back to stock. Then follow these steps:
1. Re-unlock your bootloader using the same unlock token you used before
2. Flash TWRP from fastboot (or a one-click)
3. Reboot into TWRP
4. Mount storage and put whatever rom you want into whatever folder you want on the sdcard (CM9 Alpha 5, CleanROM, AOKP M6.2, etc etc)
5. Factory Reset
6. Flash the rom and anything that needs to go with the rom (like Gapps if you're flashing CM9 or AOKP)
7. Reboot and enjoy, be sure to update your SU binaries immediately after booting by opening up the SuperUser app
Also, do not use CWM, our device is not officially supported by the CWM team. Only TWRP is an officially supported recovery for our HOX.
Click to expand...
Click to collapse
Worked. I had to leave town for a week as I was reading your reply stnguyen, so I didn't get a chance to try it until I got home tonight. I'm up and running again. Thanks a ton!
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
benjmiester said:
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
Click to expand...
Click to collapse
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
LetMeKnow said:
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
Click to expand...
Click to collapse
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
benjmiester said:
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
Click to expand...
Click to collapse
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Unlocked bootloader is allowed you to install the custom recovery so you can install the custom ROM, I believed..... You can check this guide out to see if you can setup your fastboot/adb. It is very easy to follow for the beginners, good luck....:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2688891
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Once you unlocked the bootloader you can flash a custom recovery and after that - the sky's the limit.
Flashify works great, and it is a wonderful tool as long as you're able to boot into Android.
My problem with Flashify and Goomanager and TwrpManger is that it saves users from setting up a proper ADB/fastboot connection from PC to tablet.
As long as you can boot Android, these apps are great. But what if you can't? Once the tablet doesn't boot it's so much harder (and often too late) to get the correct drivers installed for ADB and fastboot.
So if you flash your recovery with any of those apps still make sure you have access with ADB and fastboot from your PC.
You will regret it if you don't - I (almost) guarantee it.
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
benjmiester said:
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
Click to expand...
Click to collapse
The instructions in the OP actually say that you have to do a full wipe (Factory Wipe) in TWRP coming from a different rom base. Which would be you unless you had a version of CROMBi-KK installed prior to this.
It's the default selection under the Wipe menu in TWRP. Just do that and then flash the rom and your ok.
Do not use the Factory Reset option from Settings or the Wipe Data option from the BL menu! Do this in TWRP only!
Cool thanks. I figured so because that's the norm with roms on all my phones. Thanks a lot for the help guys. So happy to be get KK running on my new toy!
Just wanted to update. KK 4.4.3 rom flashed and booted in. It's much nicer. The stock was a little laggy, and KK breathed a lot of new life into my ancient single core 1.0 ghz Galaxy S that I use as a music player so I figured it would help make the tab real nice and snappy too. Gotta go now, much fun to be had!!
hello all,
I need some help here; never seen this before and it's wierd.
I got a replacement HTC OneM8 (Verizon) yesterday, today I tried to setup with a copy of my Viper rom (5.01) but phone came with Android 4.4.4 so I did the following:
• used "sunshine" to unlock the bootloader and install SuperSU.
• install TWRP version 2.8.7.0
• backup stock rooted rom
• install lollipop vzw firmaware
all the steps completed successfully
Now my phone is all weird:
If I boot to bootloader it works fine but if I select "recovery" phone goes to TWRP Recovery v2.8.6.1 FROM here (recovery) any option that I choose to reboot the phone reboots to TWRP v2.8.7 even if I asked to reboot system.
I can never boot to the phone itself (system).
I want to completely remove TWRP 2.8.7 and keep TWRP v2.8.6.1
I already tried to flash the recovery over (was successful) but I'm still with this issue.
kpitao said:
hello all,
I need some help here; never seen this before and it's wierd.
I got a replacement HTC OneM8 (Verizon) yesterday, today I tried to setup with a copy of my Viper rom (5.01) but phone came with Android 4.4.4 so I did the following:
• used "sunshine" to unlock the bootloader and install SuperSU.
• install TWRP version 2.8.7.0
• backup stock rooted rom
• install lollipop vzw firmaware
all the steps completed successfully
Now my phone is all weird:
If I boot to bootloader it works fine but if I select "recovery" phone goes to TWRP Recovery v2.8.6.1 FROM here (recovery) any option that I choose to reboot the phone reboots to TWRP v2.8.7 even if I asked to reboot system.
I can never boot to the phone itself (system).
I want to completely remove TWRP 2.8.7 and keep TWRP v2.8.6.1
I already tried to flash the recovery over (was successful) but I'm still with this issue.
Click to expand...
Click to collapse
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1
andybones said:
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1
Click to expand...
Click to collapse
I already completed those steps and when I reboot my phone still shows TWRP 2.8.7...... is there a way to manually delete the recovery
kpitao said:
I already completed those steps and when I reboot my phone still shows TWRP 2.8.7...... is there a way to manually delete the recovery
Click to expand...
Click to collapse
Flash the firmware.. Has stock recovery. If it boots to twrp after that, you're doing it wrong.
andybones said:
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1
Click to expand...
Click to collapse
andybones said:
Flash the firmware.. Has stock recovery. If it boots to twrp after that, you're doing it wrong.
Click to expand...
Click to collapse
the first couples times I did, I choose the firmware "m8vzw_AllInOne_Firmware" and " 4.17.605.9 Modified Firmware ".... both did not work in my case but then I did again with full wipe firmware "4.17.605.9 Full Firmware" and did work.... I didn't have nothing on my phone anyway so, the full firmware which wiped worked..
Thanks
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
PHYN1X said:
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
Click to expand...
Click to collapse
What version of SuperSU did you attempt to install? It sounds like you may have used a version that didn't patch dm verity and attempted to install to system, or something went wrong with the installation process.
I suggest you boot to download mode and flash the latest RUU for your version. You'd then have a clean slate to flash TWRP and the latest SuperSU to.
PHYN1X said:
So I decided I wanted to try to root my HTC One A9 today, I unlocked my bootloader, worked fine, installed TWRP, worked fine, attempted to install superSU, and now I'm stuck in a boot loop, I tried to do a reset through TWRP, that didn't work, still in loop, so I decided to install CWM recovery, but when I boot to recovery mode, i get red text that says "Failed to boot to recovery mode". So after that I decided to try to reinstall TWRP just to try that again, but now my phone isn't connected to my computer, but it's not because anything is corrupted, it's because I can't get past the boot screen to actually make my phone trust my computer. Any tips?
Click to expand...
Click to collapse
I would also suggest starting over with the RUU for your model. Once you get TWRP back however you may want to take a look at this thread http://forum.xda-developers.com/one-a9/development/rom-a9-base-roms-recovery-flashable-t3282335 for some pre-rooted stock ROMS. I'm running the Sprint one with Xposed/GravityBox right now and it's great.
CSnowRules said:
What version of SuperSU did you attempt to install? It sounds like you may have used a version that didn't patch dm verity and attempted to install to system, or something went wrong with the installation process.
I suggest you boot to download mode and flash the latest RUU for your version. You'd then have a clean slate to flash TWRP and the latest SuperSU to.
Click to expand...
Click to collapse
I used 2.46
I ordered a micro sd to usb stick so I'll be able to actually get the RUU file onto the sd card so it can flash it, I have to do it the SD card way because it isnt recignized by my computer because it doesnt trust it
Did you try re-installing drivers and flashing new recovery with fastboot?
PHYN1X said:
I used 2.46
I ordered a micro sd to usb stick so I'll be able to actually get the RUU file onto the sd card so it can flash it, I have to do it the SD card way because it isnt recignized by my computer because it doesnt trust it
Click to expand...
Click to collapse
I believe SuperSU 2.46 was your problem and that a RUU is not required to fix this. The older SuperSU broke the dm-verity for your system partition, which is enforced by your kernel. Flash SuperSU 2.76 (the latest stable release). This will automatically patch your boot partition. You will not be able to take an OTA until flashing the stock system image, though.
You just need to fastboot flash TWRP back to your device, first (fastboot flash recovery twrp.img) just like the first time from download mode--not the bootloader. Unlike ADB, your phone doesn't need to trust your computer.
If fastboot doesn't work, check what creusset said.
creusset said:
Did you try re-installing drivers and flashing new recovery with fastboot?
Click to expand...
Click to collapse
I have unlocked the boot loader on oneplus one long back. I tried to upgrade my rom to Resurrection Remix 7.1.1
I successfully upgraded the ROM and also flashed SuperSu in it. I wanted to flash the Opengaps Aroma 7.1 and that is where I ran into issue because of my stupidity.
I found from GitHub that there were some issues with twrp versions to run the aroma installer thus I tried multiple TWRP versions via (Google play - official TWRP recovery app) by downloading them and flashing it to recovery.
I have taken the full nandroid backup but unfortunately didn't keep it on external devices. So it was in the phone itself.
Now the issue -
When I tried flashing TWRP 3.0.2.0 from existing 2.8.4.1 I tried to run the Aroma but it didn't work. Then I tried to flash the recovery with TWRP 2.8.6.1 but Aroma failed again.
However, on the GitHub there was a info stating that known working TWRP recovery on Oneplus one is of TWRP 2.8.4.1
I tried to flash that into recovery and flash the Aroma, but it didn't boot into recovery with that image. Later I restarted the phone, and again flashed the latest recovery version 3.0.2.0
From here I ran into issue. When tried again to flash the Aroma, it didn't work. So I booted recovery again and in that I selected the recovery version 2.8.4.0 for both recovery and boot partition.
After that, phone is neither booting the system nor into recovery. I don't want to loose my data (which is in phone backup) and neither want to try Aroma again. (Even if all the 900mb data needs to be deleted.).
Can the XDA members confirm can I reinstall recovery working image (2.8.4.1) once again through the adb flash recovery <image>. And boot into recovery mode so that I can delete the boot partition once again and reinstall the ROM and data ?
I tried doing that once but one of the laptops which I had access didn't recognize the adb devices. May be the driver was not working for Win10 OS. However, on my personal laptop earlier I was able to run adb commands through CMD prompt. Currently, I don't have personal laptop and may get it by next week.
Can anybody please share me the links of working android driver so that I can install them on current laptop and then try adb commands from SDK to connect my phone.
Any suggestion from members would be of great help.
Note: Please don't suggest the methods to factory reset or lock bootloader to factory settings. As I don't want to loose all my contacts and data.
If there is a way to get just recovery working on the phone, it would be of great help. So that I can wipe other partitions and rebuild it again.
Thank You.