[Q] Wont boot after bad CWM backup/restore - One (M7) Q&A, Help & Troubleshooting

Hi Folks,
I'm hoping someone might be able to offer a bit of advice. Here's the situation:
I was happily running MaximusHD 46, but fancied trying something more recent. I flashed MaximusHD 53, which ran just fine.
I'd got things set up nicely and made a backup using Rom Manager/CWM (touch, 2.0.4.8).
Then I tried a couple of other ROMs and didn't have any issues, but didn't really get on with them.
I preferred MaximusHD 53 so went to restore the backup using ROM manager. ROM manager didn't list the backup, but I could see it in the usual location using ES Explorer. I booted into CWM, which seemed to restore the backup OK.
..but my phone then wouldn't boot past the animated boot screen. The animation played, but then it just stopped there.
I've cleared cache partition and dalvik cache through CWM, but found the same. I've got no ROM.zip on the phone to flash over what's currently there.
Trying to sideload a ROM results in a 'protocol error' at 70+ %
Trying to ADB Push a ROM gives Error: Closed
Trying to mount a FAT32 formatted USB drive using a USB OTG cable makes the CWM menu refresh, but nothing's mounted
Re-flashed CWM and retried everything with the same result.
The phone currently shows:
*** Unlocked ***
S-OFF
CID: HTC__001
HBoot: 1.56.0000 (with no red txt)
Radio: 4T.33.3218.15
OS: 4.19.401.11
Could anyone make any suggestions which might help me resurrect it please?
TIA!

mad_tunes said:
Hi Folks,
I'm hoping someone might be able to offer a bit of advice. Here's the situation:
I was happily running MaximusHD 46, but fancied trying something more recent. I flashed MaximusHD 53, which ran just fine.
I'd got things set up nicely and made a backup using Rom Manager/CWM (touch, 2.0.4.8).
Then I tried a couple of other ROMs and didn't have any issues, but didn't really get on with them.
I preferred MaximusHD 53 so went to restore the backup using ROM manager. ROM manager didn't list the backup, but I could see it in the usual location using ES Explorer. I booted into CWM, which seemed to restore the backup OK.
..but my phone then wouldn't boot past the animated boot screen. The animation played, but then it just stopped there.
I've cleared cache partition and dalvik cache through CWM, but found the same. I've got no ROM.zip on the phone to flash over what's currently there.
Trying to sideload a ROM results in a 'protocol error' at 70+ %
Trying to ADB Push a ROM gives Error: Closed
Trying to mount a FAT32 formatted USB drive using a USB OTG cable makes the CWM menu refresh, but nothing's mounted
Re-flashed CWM and retried everything with the same result.
The phone currently shows:
*** Unlocked ***
S-OFF
CID: HTC__001
HBoot: 1.56.0000 (with no red txt)
Radio: 4T.33.3218.15
OS: 4.19.401.11
Could anyone make any suggestions which might help me resurrect it please?
TIA!
Click to expand...
Click to collapse
Try to flasha rom using TWRP instead of CWM.
Also you have s-off so you can simply flash any .401 ruu.zip to restore your phone.

mad_tunes said:
Hi Folks,
I'm hoping someone might be able to offer a bit of advice. Here's the situation:
I was happily running MaximusHD 46, but fancied trying something more recent. I flashed MaximusHD 53, which ran just fine.
I'd got things set up nicely and made a backup using Rom Manager/CWM (touch, 2.0.4.8).
Then I tried a couple of other ROMs and didn't have any issues, but didn't really get on with them.
I preferred MaximusHD 53 so went to restore the backup using ROM manager. ROM manager didn't list the backup, but I could see it in the usual location using ES Explorer. I booted into CWM, which seemed to restore the backup OK.
..but my phone then wouldn't boot past the animated boot screen. The animation played, but then it just stopped there.
I've cleared cache partition and dalvik cache through CWM, but found the same. I've got no ROM.zip on the phone to flash over what's currently there.
Trying to sideload a ROM results in a 'protocol error' at 70+ %
Trying to ADB Push a ROM gives Error: Closed
Trying to mount a FAT32 formatted USB drive using a USB OTG cable makes the CWM menu refresh, but nothing's mounted
Re-flashed CWM and retried everything with the same result.
The phone currently shows:
*** Unlocked ***
S-OFF
CID: HTC__001
HBoot: 1.56.0000 (with no red txt)
Radio: 4T.33.3218.15
OS: 4.19.401.11
Could anyone make any suggestions which might help me resurrect it please?
TIA!
Click to expand...
Click to collapse
AS advised Use TWRP or RUU to get back running again.
A bit of advise. Avoid CWM and Rom manager. They are both outdated and buggy beyond beyond believe.

TWRPs flashed fine and I'm sideloading MaximusHD53 as I type.
Thanks for the tip, both of you (especially if you're on the same time as me, 0345 here).
I'll post results shortly..

It went through the installer, but it finished way too quickly and what would usually be an 'everything's OK, restart' prompt was blank.
ADB showed * failed to read command:
Tried again and it seems to be behaving itself, just restarting after sideloading without error.

Android is upgrading..
Thanks very much.
I noticed that when it was done applying the ROM and scripts, I clicked to restart and cmd showed:
serving: 'C:\MaximusHD53.zip' (~58%) * failed to read command:
Is that normal when sideloading, it's not something I do regularly?

ROM's running great and I've been able to back it up and restore it using TWRP - and it still boots!
I've no idea what got CWM confused, but switching to TWRP seems to have made everything happy again.

mad_tunes said:
ROM's running great and I've been able to back it up and restore it using TWRP - and it still boots!
I've no idea what got CWM confused, but switching to TWRP seems to have made everything happy again.
Click to expand...
Click to collapse
Better to use TWRP with the M7, don't get me wrong, CWM is also a great recovery but everything for the M7 seems to works best with TWRP.
If you have flashed twrp 2.8.6.0 and your drivers are correctly installed, then sideloading isn'T necessary. 2.8.6.0 is MTP enabled so you should see your phone storage on your computer (like a usb stick) when booted in twrp. Just drag and drop the rom zip file from your computer to your phone storage. No need to "adb sideload" or "adb push" anymore.
Anyway glad it worked :good:

Related

[Q] PLEASE HELP flash TrickDroid - FROZEN - REBOOT = BRICKED

in short:
i used the ALL IN ONE TOOLS to unlock boot loader from HTC DEV as instrcutions.
then took a few times to install CWM, CWM TOUCH, TWRP finally end up with CWM TOUCH
then i flashed TRICKDROID successfully
Thing went bad when TRICKDROID installation completed and asked to reboot, i didn't do that but continue flash the theme zip as i used to do it with gapps. During the AROMA INSTALL its frozen at 40% for 30 mins. I try to reboot and my PHONE STUCK at the boot screen. At fist i couldn't access to RECOVERY but after a few try to Re-lock and reset Iam able to get into CWM to re-flash TRICKDROID, it kept stuck when i select options randomly for a few times until i end up with error mounting sdcard the error is similar no mater what recovery i use.
Now my phone is almost useless, the only thing i can do to get CWM to see couldn't mount SdCard error. I read and many solutions to re-flash to stock but always came up with signature checking failed ... i follow [HOW-TO] Fix soft brick & error mounting sdcard from HTC ONE S without successful. NAROID BACKUP ZIP AND RUU re-flash also failed so far. i used my back up and TELSTRA backup from HTC M7 RUU Collection, the trouble now is I have no ways to access to SD CARD.
Please help, it took me almost 12 hours continuously already,
my phone details is
based Band 4A.14.3250.13
hboot 1.44.0000
main 1.29.841.2
model id PN0714000
cid TELSTRA001
hdt_anh said:
in short:
i used the ALL IN ONE TOOLS to unlock boot loader from HTC DEV as instrcutions.
then took a few times to install CWM, CWM TOUCH, TWRP finally end up with CWM TOUCH
then i flashed TRICKDROID successfully
Thing went bad when TRICKDROID installation completed and asked to reboot, i didn't do that but continue flash the theme zip as i used to do it with gapps. During the AROMA INSTALL its frozen at 40% for 30 mins. I try to reboot and my PHONE STUCK at the boot screen. At fist i couldn't access to RECOVERY but after a few try to Re-lock and reset Iam able to get into CWM to re-flash TRICKDROID, it kept stuck when i select options randomly for a few times until i end up with error mounting sdcard the error is similar no mater what recovery i use.
Now my phone is almost useless, the only thing i can do to get CWM to see couldn't mount SdCard error. I read and many solutions to re-flash to stock but always came up with signature checking failed ... i follow [HOW-TO] Fix soft brick & error mounting sdcard from HTC ONE S without successful. NAROID BACKUP ZIP AND RUU re-flash also failed so far. i used my back up and TELSTRA backup from HTC M7 RUU Collection, the trouble now is I have no ways to access to SD CARD.
Please help, it took me almost 12 hours continuously already,
my phone details is
based Band 4A.14.3250.13
hboot 1.44.0000
main 1.29.841.2
model id PN0714000
cid TELSTRA001
Click to expand...
Click to collapse
Choose install zip from sideload in recovery
Put your ROM.zip in your adb folder on your computer and open a terminal from the folder
Command
adb sideload name_of_your_rom.zip
Or try using the toolkit to sideload but I'm unfamiliar with the toolkit method as I use a Mac
Sent from my HTC One using xda premium
I enabled ADB side from TWRP then your command, it said * can not read 'sideload' *
Using ALL IN ONE TOOLS the CMD windows is all black for about 5 minite, device not found, from bottloader it's clearly seen FASTBOOT USB before enter RECOVERY. I can hear the sound from my LAPTOP whenever turn on/off ADB Sideload, so my LAP should see my phone
i am pretty sure that the ZIP is okie and flash-able before.
i found one thing my HTC ONE is the TELSTRA BRAND in AUSTRALIA with the base mainbase 1.29.841.2 while the Trickdroid is from 401 brand 1.29.401.16 R (WWE). according to my understand my HTC able to use m7_UL ROMS which should be fine, iwonder i might the reason cause my phone bricked like that?
i tried ti find the stock base RUU for my TELSTRA TELST001 but no luck so far. NO ONE have seen that RUU before.
If that's is the case what should i do next? thanks in advance

[Q] HTC one reboots - Regardless of rom flashed

Hello everyone,
I've got a weird issue where I can recovery/fastboot/adb just fine.
But no matter what rom I install on my HTC One it boots up to a certain point (past the HTC logo to a midpoint of google boot up logo, sometimes into the os)
I had GPE 4.3
I tried to install 4.4 with the new radios. (S-Off)
It messed up once, I re-flashed cwm (had twrp) through fast boot - tried GPE 4.3 again .. still rebooting
re-flashed through fast new twrp again (just in case) - did advanced wipe - tried both roms still the same thing.
I've tried adb push and sideload.
Am I overlooking something here ? Any help or point to some reading material would be greatly appreciated.
I've been searching and searching and it seems most in similar situations can adb sideload roms when internal storage is not accessible and be right back up. I m stil stuck in the boot loop.
Currently downloading htc one sense 4.4. if I could get GPE 4.4 to work it'd be great.
Thank You in advance.
EDIT:
Phone is HTC ONE Rogers (Canadian)
Rooted - S-Off
Downloaded New ROM from - http://forum.xda-developers.com/showthread.php?t=2341395
Original ROM - http://htconeroot.com/htc-one-root/google-play-edition-rom-android-4-3-for-htc-one/
yasink said:
Hello everyone,
I've got a weird issue where I can recovery/fastboot/adb just fine.
But no matter what rom I install on my HTC One it boots up to a certain point (past the HTC logo to a midpoint of google boot up logo, sometimes into the os)
I had GPE 4.3
I tried to install 4.4 with the new radios. (S-Off)
It messed up once, I re-flashed cwm (had twrp) through fast boot - tried GPE 4.3 again .. still rebooting
re-flashed through fast new twrp again (just in case) - did advanced wipe - tried both roms still the same thing.
I've tried adb push and sideload.
Am I overlooking something here ? Any help or point to some reading material would be greatly appreciated.
I've been searching and searching and it seems most in similar situations can adb sideload roms when internal storage is not accessible and be right back up. I m stil stuck in the boot loop.
Currently downloading htc one sense 4.4. if I could get GPE 4.4 to work it'd be great.
Thank You in advance.
EDIT:
Phone is HTC ONE Rogers (Canadian)
Rooted - S-Off
Downloaded New ROM from - http://forum.xda-developers.com/showthread.php?t=2341395
Original ROM - http://htconeroot.com/htc-one-root/google-play-edition-rom-android-4-3-for-htc-one/
Click to expand...
Click to collapse
are you flashing the required version of TWRP ? TWRP_2.6.3.3_m7
also flashing rom's doesn't update radios .. flashing radios or firmware updates radios
Roger that
clsA said:
are you flashing the required version of TWRP ? TWRP_2.6.3.3_m7
Click to expand...
Click to collapse
Yep ... that is the exact one I got.
openrecovery-twrp-2.3.3.3-m7
yasink said:
Yep ... that is the exact one I got.
openrecovery-twrp-2.3.3.3-m7
Click to expand...
Click to collapse
are you doing fastboot erase cache after updating the recovery ?
As you are S-off, run a full RUU to remove any problematic flashes.
Thank you for the replys.
I've tried this fastboot cache erase .. didnt work
ruu is quite hard to find for Rogers HTC one (so far no luck ../ found some old ones links broken ... will keep looking)
I also got a chance to try and flash htc stock sense 5.5 with 4.4 kitkat from here:
(durm it .. can't post outside links yet sorry ..)
Phone still reboots before fully getting to os.
Weirdly enough, if I turn it off during this cycle. It turns back on by itself too.
So far to stop the loop, I have to boot to recovery (TWRP currently) and lock it.
I am guessing I should find a way to S-ON then flash an older rom.
Anything else I could try? :fingers-crossed:
Thank You everyone.
yasink said:
Thank you for the replys.
I've tried this fastboot cache erase .. didnt work
ruu is quite hard to find for Rogers HTC one (so far no luck ../ found some old ones links broken ... will keep looking)
I also got a chance to try and flash htc stock sense 5.5 with 4.4 kitkat from here:
(durm it .. can't post outside links yet sorry ..)
Phone still reboots before fully getting to os.
Weirdly enough, if I turn it off during this cycle. It turns back on by itself too.
So far to stop the loop, I have to boot to recovery (TWRP currently) and lock it.
I am guessing I should find a way to S-ON then flash an older rom.
Anything else I could try? :fingers-crossed:
Thank You everyone.
Click to expand...
Click to collapse
try this TWRP Nandroid Backup
http://www.htc1guru.com/dld/m7-twrp-nandroid-backup-cid-roger001-3-22-631-1-zip/
To use – download the latest version of the needed recovery and install it via fastboot:
fastboot flash recovery CWM.img
or
fastboot flash recovery TWRP.img
Then enter recovery either by holding power and vol down button until bootloader displays and then select recovery or if device is booted into the OS use this adb command:
adb reboot recovery
Now perform a test backup and allow it to complete. Then make a note of the folder in which the backup was created. Now copy the downloaded stock Nandroid into that same folder so that recovery will see the backup and allow you to restore it.
Click to expand...
Click to collapse
That nandroid backup method did take me the furthest so far.
(did wipe before doing it also)
The phone went into the os ... but only to reboot about 30 seconds later.
On the second reboot .. it said an app is asking for super user permission, before i could select allow or anything,
the phone has been boot looping again.
Weird.
yasink said:
That nandroid backup method did take me the furthest so far.
(did wipe before doing it also)
The phone went into the os ... but only to reboot about 30 seconds later.
On the second reboot .. it said an app is asking for super user permission, before i could select allow or anything,
the phone has been boot looping again.
Weird.
Click to expand...
Click to collapse
try wiping everything and try again
hi clsA,
thank you for replying.
I did try that, still bootloops. I also further tried:
install teaMseven - sense55 - kk - v2.3.6 with the new stock sense 5.5 rom flashed first.
I forgot to mention earlier, I did flash a radio after initially trying to upgrade to GPE 4.4.
The radio flashed was: RadioUpdate_4T.21.3218.21_10.16.1718.01L.zip
only because it was mentioned i'd get a boot loop going to GPE 4.4 without that update.
Theres no sim in the tray, could this radio update be causing this ? I tried re-downloading this radio for a fresh copy of the file also.
IF the radio is/could be causing this, is there a way to determine which radio to try?
I found: http://forum.xda-developers.com/showthread.php?t=2325564
Out of any further ideas for now
[SOLVED]
Hello everyone,
After so many days of trying, I finally found a way to fix my phone.
I noticed a lot of requests all over the web of a Rogers RUU. This is how I was able to bring my Rogers HTC back to life and stock.
I found this guide:
http://www.htc1guru.com/guides/return-stock-guide/
(Same website, that has the nandroid backup posted earlier by clsA)
follow ... that guide. Should be good.
I flashed 4.4 GP afterwards (as originally intended) and then OTA'd to 4.4.2. Everything seems to be running perfectly.
Thank You for the nandroid backup and leading me to that website clsA.

[Q] Stuck in Boot After Flashing ARHD41.0 ROM

Hello All,
Sorry if this has already been solved before, and thanks in advance for help. (I tried to post this in the ARHD41.0 thread, but as a newbie I cannot post there.)
I have an HTC One (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remained S-On. Made a backup through CWM recovery, transferred that to my PC, then figured I might as well celebrate the holidays by flashing my first ROM.
I downloaded the Android Revolution HD 41.0 ROM (forum.xda-developers.com/showthread.php?t=2183023), transferred to the SD, and then installed the zip through the CWM ROM manager (it seemed at least from what I read in the posts that followed that the ROM worked just fine with CWM). After going through the option selection process (I believe that this was the Aroma installer), I opted to wipe data since I was starting from a different ROM altogether (of course, silly me, this also wiped the backup on the SD). Seemed to install just fine, booted into what appears to be some part of the recovery where it asked if I wanted to root, I selected yes, and the phone rebooted.
Or, at least, tried to. It has been stuck at the beginning of the boot, where there is a white background with the HTC logo and "quietly brilliant" underneath, and it remains stuck there. If I press power and volume down for an abnormally long time, I can get into the bootloader and the recovery from there, but rebooting from there just leaves me at the boot screen again. As I said, there is no backup on the SD for me to restore. When in bootloader, I connected to the PC and fastboot turns to fastboot USB, but adb isn't showing anything when I enter abd devices.
I'm sure I probably did something very silly and am missing something very simple, but given that this is my first time, I have no idea what it is and how to go about fixing it.
Thanks again for all your help!
lyciansarpedon said:
Hello All,
Sorry if this has already been solved before, and thanks in advance for help. (I tried to post this in the ARHD41.0 thread, but as a newbie I cannot post there.)
I have an HTC One (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remained S-On. Made a backup through CWM recovery, transferred that to my PC, then figured I might as well celebrate the holidays by flashing my first ROM.
I downloaded the Android Revolution HD 41.0 ROM (forum.xda-developers.com/showthread.php?t=2183023), transferred to the SD, and then installed the zip through the CWM ROM manager (it seemed at least from what I read in the posts that followed that the ROM worked just fine with CWM). After going through the option selection process (I believe that this was the Aroma installer), I opted to wipe data since I was starting from a different ROM altogether (of course, silly me, this also wiped the backup on the SD). Seemed to install just fine, booted into what appears to be some part of the recovery where it asked if I wanted to root, I selected yes, and the phone rebooted.
Or, at least, tried to. It has been stuck at the beginning of the boot, where there is a white background with the HTC logo and "quietly brilliant" underneath, and it remains stuck there. If I press power and volume down for an abnormally long time, I can get into the bootloader and the recovery from there, but rebooting from there just leaves me at the boot screen again. As I said, there is no backup on the SD for me to restore. When in bootloader, I connected to the PC and fastboot turns to fastboot USB, but adb isn't showing anything when I enter abd devices.
I'm sure I probably did something very silly and am missing something very simple, but given that this is my first time, I have no idea what it is and how to go about fixing it.
Thanks again for all your help!
Click to expand...
Click to collapse
Hey,
Not to worry just run this command from fastboot (Power button +vol down while booting-> fastboot) plug your phone in and run
fastboot erase cache
Click to expand...
Click to collapse
and if its not fixed, just flash again. Make a back up next time! BTW if you need adb just get it from HERE (hint clickn 'here') if you need more help PM me, im always available
You need TRWP 2.6.3.3 or latest version (2.6.3.4) recovery!
Some members successfully flashed by CWM but also some of them face problems, so its better to you to follow FAQ to get good results : )
http://forum.xda-developers.com/showpost.php?p=48035061&postcount=62237
Ba7rani said:
You need TRWP 2.6.3.3 or latest version (2.6.3.4) recovery!
Some members successfully flashed by CWM but also some of them face problems, so its better to you to follow FAQ to get good results : )
http://forum.xda-developers.com/showpost.php?p=48035061&postcount=62237
Click to expand...
Click to collapse
I actually just saw the posts about the CWM issue a little while ago - that's what I get for not reading all the posts! I flashed with TWRP, the ROM installed, and the phone booted.
Now, this is where things get interesting. My backup that I had made with CWM before I initially tried to flash the ROM was still in \data\media\clockworkmod (where it had initially backed up to), and I wanted to check if I was still able to restore from it. TWRP doesn't recognize it as a backup folder/file (not sure if it would be compatible; this is also my first time restoring), and I flashed back to CWM recovery (phone still boots fine after that)...which doesn't recognize it either. I tried moving it to \sdcard\clockworkmod (where the md5 checksum file was originally generated), \sdcard (just in case, since the recovery option says "restore from \sdcard"), as well as \mnt\shell\emulated\clockworkmod (that's where the CWM ROM manager says that it would have backed up to), but the recovery says "No files found" for any of those as well. Any thoughts on where the backup ought to be located?
lyciansarpedon said:
I actually just saw the posts about the CWM issue a little while ago - that's what I get for not reading all the posts! I flashed with TWRP, the ROM installed, and the phone booted.
Now, this is where things get interesting. My backup that I had made with CWM before I initially tried to flash the ROM was still in \data\media\clockworkmod (where it had initially backed up to), and I wanted to check if I was still able to restore from it. TWRP doesn't recognize it as a backup folder/file (not sure if it would be compatible; this is also my first time restoring), and I flashed back to CWM recovery (phone still boots fine after that)...which doesn't recognize it either. I tried moving it to \sdcard\clockworkmod (where the md5 checksum file was originally generated), \sdcard (just in case, since the recovery option says "restore from \sdcard"), as well as \mnt\shell\emulated\clockworkmod (that's where the CWM ROM manager says that it would have backed up to), but the recovery says "No files found" for any of those as well. Any thoughts on where the backup ought to be located?
Click to expand...
Click to collapse
If you have Titanium backup pro you can restore from nandroid file
Menu > restore from Nandroid ..
* Its not recommended to restore system apps or data by Titanium
Found my mistake:
lyciansarpedon said:
\mnt\shell\emulated\clockworkmod\backup (that's where the CWM ROM manager says that it would have backed up to)
Click to expand...
Click to collapse
Missed that I needed to create that directory, oy. Recovery found it just fine, and restored it just as I left it.
Thanks all!

[RESOLVED] ViperOne Boot Loop HTC One VZW

RESOLVED: So of course, taking 10+ minutes to type this out magically fixed the issue, huh? :silly:
What I did was I restored my backup, installed TWRP 2.7.0.1 from a download on this forum, and tried it again. Made sure to factory reset both times, etc.
I'm booted into ViperOne 5.8.0 now! Sorry for wasting anybody's time...
So, I've searched around the forums, and I haven't found anything that quite sounds like what's going on with my phone. My issue is that I get put in a boot loop after flashing ViperOne 5.8.0.
First, some info about my phone:
Unlocked (S-OFF)
CID: VZW__001
HBOOT: 1.56.0000
OS: 3.11.605.1
Steps leading to the issue:
Used rumrunner to s-off and root phone back when it came out for VZW in August.
Had CWM recovery for the longest time. Didn't update the phone since then.
The other day, I backed up my phone with CWM and then later decided to switch to TWRP (got the newest version I could find - 2.7.0.0).
I put TWRP on my phone and then tried flashing ViperOne 5.8.0 from it.
It seemed to have put me in a bootloop, so I tried a few factory resets and cache clearing, etc.
Then, I went into ViperOne's installer and installed the older version of TWRP.
At that point, I couldn't even get back into recovery, so I used fastboot to put the latest TWRP back on.
I threw out my old backup and used a RUU to get back to stock 1.10.605.1 (RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted) from here.
At this point, my phone was working again. I installed all of the updates through the phone to get to KitKat 4.4.2.
From here, I installed a bunch of apps I used, reacquired root (my phone still said S-OFF/Unlocked from the first ever time I did it) and performed a TWRP backup.
I decided to give ViperOne a shot again since my phone had been updated and I wasn't sure if the newer hboot or stuff like that would help.
I followed the instructions on some site that said to fastboot flash the boot.img in the zip first and then flash the zip from TWRP.
Everything seemed fine again. I factory reset BEFORE and AFTER flashing ViperOne. However, it's giving me the same issues; I'm stuck in a boot loop.
I got ViperOne from here. The ViperOne Verizon page seemed to just link there (I couldn't find a download specific to Verizon) so I'm assuming that's the right one.
If anyone could offer any suggestions on what to do? The next think I'll try is downgrading my version of TWRP I guess?
If more details are needed, please let me know. Also, sorry if this is in the wrong section?

[Q] Flashing a ROM with Unlocked Bootloader but S-ON. Possible ?

Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
anirudhgargi said:
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
Click to expand...
Click to collapse
as mentioned in the previous post you made, you need to install a custom ROM first in order to boot back into your phone. You have unlocked the bootloader and installed TWRP recovery. Now you need to sideload the ROM by adb sideload commands in order to boot the phone up again
Do not run an earlier RUU.zip as you will brick your phone. Firewater needs a working ROM, there are no ways to bypass this
Flash ARHD 81 or Insert Coin or Team Venom Rom
Step 1. Unlock Bootloader and Install TWRP 2.7.x.x recovery. Don't install Twrp v2.8.x.x, wont work with any roms.
Step 2. Boot to Recovery.
Step 3. Mount the system using twrp. I am assuming that you don't have custom rom on your phone storage.
Note that TWRP v2.7.x.x wont mount the phone storage. v2.7 and above always had issues. My recommendation is to install TWRP v2.8 for temporary purposes. Now mount the phone storage copy any rom you downloaded to the system.
Step 4. Assuming that you install TWRP v2.8 to copy rom files to phone storage. Boot to bootloader again and Install TWRP using fastboot. Command: "Fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img"
Step 5. Reboot to recovery. WIPE DATA, CACHE, DALVIK CACHE, SYSTEM > Install Rom.
Note do not wipe "internal storage." Otherwise you have to go back and start again with installing twrp v2.8, then copy rom...
Step 6: follow the steps.
IMO ARHD 81 is a stable rom, provides better battery life. If you like Sense then stick with this Rom, if you want Stock Android aka AOSP then try aospa legacy, CM, SlimKAT, AOSB and many more.
Moreover, i haven't found RUU for Sense 6 KK4.4.3, if you do please provide me a link as well.
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Not able to copy my custom rom in phone.
stovie_steve said:
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Click to expand...
Click to collapse
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
anirudhgargi said:
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
Click to expand...
Click to collapse
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
No luck ! Fastboot mode also not getting detected now.
stovie_steve said:
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
Click to expand...
Click to collapse
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
anirudhgargi said:
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
Click to expand...
Click to collapse
Sounds also like a driver issue
Try instling HTC sync to get the up to date HTC drivers and retry. Use different usb ports (2.0 preferably) and different cables. If it's saying fastboot ac then the phone is not being detected correctly, so it's a driver issue
You can also try manually installing the driver by searching for I think the Google naked driver

Categories

Resources