Hello there!
I have an international HTC One with ViperOne 5.5.1.
I recently made my phone S-OFF (it has 1.54).
Now the problem: As soon as I try to flash either a kernel or a bootscreen, the phone reboots. I currently have CWM Touch (just 5 minutes now, I flashed CWMT because TWRP had the same problem). The problem is not in the recovery, since they both don't work. Fastboot works (I could flash a different recovery). It's just that as soon as something tries to flash into /system, the phone reboots itself. I tried pushing the bootscreen via adb, but that gave a 'protocol failure.'
tl;dr: Phone reboots while flashing in both TWRP and CWM Touch, eventually it didn't flash anything at all.
I am beyond reasoning and have no clue on what to do.
R3NC0N said:
Hello there!
I have an international HTC One with ViperOne 5.5.1.
I recently made my phone S-OFF (it has 1.54).
Now the problem: As soon as I try to flash either a kernel or a bootscreen, the phone reboots. I currently have CWM Touch (just 5 minutes now, I flashed CWMT because TWRP had the same problem). The problem is not in the recovery, since they both don't work. Fastboot works (I could flash a different recovery). It's just that as soon as something tries to flash into /system, the phone reboots itself. I tried pushing the bootscreen via adb, but that gave a 'protocol failure.'
tl;dr: Phone reboots while flashing in both TWRP and CWM Touch, eventually it didn't flash anything at all.
I am beyond reasoning and have no clue on what to do.
Click to expand...
Click to collapse
Try this: go back to recovery (TWRP 2.6.3.3. or .4 recommended for 4.4 ROMs at the moment)
dirty-flash the ROM, then while still in recovery (no reboot), flash kernel, etc.
then reboot
Wow, that actually worked. Weird stuff if you ask me.
edit: okay it didn't entirely work. The bootscreen didn't work, but I'll retry that after again rebooting.
edit 2: Weird, the bootscreen just won't work. I guess that's just a problem with the bootscreen then.
R3NC0N said:
Wow, that actually worked. Weird stuff if you ask me.
edit: okay it didn't entirely work. The bootscreen didn't work, but I'll retry that after again rebooting.
edit 2: Weird, the bootscreen just won't work. I guess that's just a problem with the bootscreen then.
Click to expand...
Click to collapse
You sure the "bootscreen" zip is for your ROM? they changed the file-naming in 4.4 or 4.3 (don't remember as i never use them), so double check that part
Yeah, I already fixed it!
Thanks for the help!
[THIS THREAD CAN BE CLOSED]
Related
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.
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!
Hey guys,
Terribly sorry if this is a common question, but after two days of searching and being unable to use my phone, I decided to post instead.
I have previously succesfully installed Cyanogen on my HTC One, using CWM. After talking to some family and friends, I decided to try out ARHD instead, as it seemed more fitting to my needs.
I download the zip, flash it from CWM, but I constantly get the error "set_metadata_recursive: some changes failed" at end of installation. I am able to continue and install seems succesful, but I can never boot past the inital white screen HTC logo. I searched for info on this, and some reported it might be due to outdated recovery. However, I have tried with CWM 6.0.4.8 and I am currently running 6.0.4.6 Touch, but no luck with either version.
At one point, I also soft-bricked my phone. I were able to flash new recovery, but had to reset my SD card and I also lost all backups. Somehow the phone booted up in Cyanogen after this, and I were able to download a zip for ARHD 81. I tried flashing this, got "set_metadata_recursive: some changes failed" and I am now unable to boot my phone again.
I have tried pushing and sideloading, however neither seems to work. Since there's no progress bar for pushing, I had to be patient, but after two hours without result I have to assume it's not working. Sideloading always gets stuck at either 3% or 8%, I can't seem to find a cause for this.
I really hope you guys might be able to work out a fix for this issue with me, as I've reached a dead end.
Unlock
I have also unlocked the phone with HTCDev unlock tool, so that should be fine.
TalkingWaterfall said:
I have also unlocked the phone with HTCDev unlock tool, so that should be fine.
Click to expand...
Click to collapse
ARHD requires TWRP Recovery
download TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
then flash it
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
now your rom will install without error
Alright. I have tried installing TWRP, but I always came up with errors booting into TWRP. I got it working once, but at that point in time I didn't have the ROM zip on my phone... I'll try it out asap and get back. Thanks.
That did it. Honestly I feel a little silly at this point, but I wish it were mentioned in the main ARHD thread that you needed TWRP, since in the "You Need" section, it simply requires a custom recovery.
I'd never seen the fastboot erase cache command before, so that helped out a lot getting TWRP working
Thank you so much!
TalkingWaterfall said:
That did it. Honestly I feel a little silly at this point, but I wish it were mentioned in the main ARHD thread that you needed TWRP, since in the "You Need" section, it simply requires a custom recovery.
I'd never seen the fastboot erase cache command before, so that helped out a lot getting TWRP working
Thank you so much!
Click to expand...
Click to collapse
Your welcome
I believe the root problem of this may be using TWRP manager to update recovery, because it happens after I attempt to do that. It asks if /dev/block/mmcblk0p43 is the correct partition, which i believe it is, and attempts to flash it. Once it attempts, it says it is failed, but when I reboot into recovery it is the updated version of TWRP. I think it may be messing up my partitions somehow.
The problem is, I RUU'd last night with the official Sprint exe, and all was fine. Rooted, installed recovery and flashed the latest of CM12. Get it up and running, go about re installing all my apps, and use TWRP manager to update the recovery. Today the new nightly has some M8 specific updates to it, so I decided to flash it. I flash in recovery, get no errors, but once I reboot it stays stuck at the white HTC screen where they threaten to send you into poverty for misusing their software.
Does anyone have any input on how to correct this issue, outside of RUU'ing again?
Krunk_Kracker said:
I believe the root problem of this may be using TWRP manager to update recovery, because it happens after I attempt to do that. It asks if /dev/block/mmcblk0p43 is the correct partition, which i believe it is, and attempts to flash it. Once it attempts, it says it is failed, but when I reboot into recovery it is the updated version of TWRP. I think it may be messing up my partitions somehow.
The problem is, I RUU'd last night with the official Sprint exe, and all was fine. Rooted, installed recovery and flashed the latest of CM12. Get it up and running, go about re installing all my apps, and use TWRP manager to update the recovery. Today the new nightly has some M8 specific updates to it, so I decided to flash it. I flash in recovery, get no errors, but once I reboot it stays stuck at the white HTC screen where they threaten to send you into poverty for misusing their software.
Does anyone have any input on how to correct this issue, outside of RUU'ing again?
Click to expand...
Click to collapse
S-on or S-off? If S-on you have to flash the kernel separately from the ROM.
Magnum_Enforcer said:
S-on or S-off? If S-on you have to flash the kernel separately from the ROM.
Click to expand...
Click to collapse
I've been s-off'd since day one, and I just booted into bootloader and double checked, still s-off.
I did however this morning flash the Blissful kernel and it booted, and noticed your comment when I came to update. It's very strange that it needed the kernel flashed.
I use TWRP 2.8.7.1(which was flashed to the phone) and now after flashing this nightly version, the recovery gets stuck on the TWRP screen and flashes every 60 seconds, but never lets me use it.
I've searched through all the forums, but can't find anyone else with this problem. I just want to flash CM12.1 Snapshot, but I can't without the recovery working.
Everytime I flash the same recovery(TWRP2.8.7.1), the bootloader gives me the error "Mismatched partition size". I've tried "Fastboot boot TWRP2.8.7.1.img, but it sits stuck on the loading TWRP screen. I've cleared the cache, but still nothing.
The only recovery that I can get to work is CWM by booting the .img from the bootloader, but that still does nothing because none of the directories will mount, so I cant flash from the recovery.
I'm waiting on motorola to send me the stock files and just reflash stock and start from scratch, but I really want to save my data.
Does anybody have any clue as to what I'm doing wrong before I reset to stock?
Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom
uluf said:
Try this one:
http://forum.xda-developers.com/showthread.php?p=61558425
If this recovery doesn't work, you may have to reflash the full stock rom
Click to expand...
Click to collapse
Nope.. didn't work. I had the 5.0 files from motorola that I flashed, and I'll update from there.
I really wish motorola would leave those files open to download instead of having to wait... sucks not having a phone, but I survived.
i have the same issue, any idea how to fix it ?