Installing TWRP Recovery... - One (M7) Q&A, Help & Troubleshooting

Hello,
This is a really weird situation I have with my phone. Recently my phone got ran over and just had new whole front (Screen) replaced. Before the indecent I could flash ANY ROM, ANY RECOVERY!!
but since I've had my phone fixed I can't install certain custom ROMS or Recoverys? My phone will only allow TWRP 2.6.3.3 why won't it let me install any latest recovery?
My Handset:
- HTC One
- TWRP Recovery 2.6.3.3
- ROOTED
- S-OFF
It's really strange.

i have kind of a similar problem.
i gave my m7 to a vodafone store to get my display repaired. they sent the phone to HTC. When i got it back, the screen was fixed, but a stock rom was installed on it including stock recovery and a locked bootloader. I still had s-off though.
I reopened the Bootloader, but for some reason i was not able to install custom recoveries at all (well i only tried TWRP 2.7.xx and 2.8.xx as well as the latest cwm touch recovery). Cmd on my Windows Pc was telling me that it successfully installed the recovery but everytime i was booting into recovery it booted for some reason to system.
I then ran the prerooted Android 5.0 GPE RUU so i could at least get root acces. But still cannot install custom recoveries :/

seem's to be alot of this about at the moment, im not sure if HTC have somehow put a new block on things like they did with the s-off tools, unfortunatly, currently there is no fix.

Yeah, i've read about similar problems on the AndroidPit-forum and some other german forum.
This freaks me out

Related

[Q] Problems with OTA Upgrade

I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Check PM
sgiitk said:
I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Click to expand...
Click to collapse
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
BUT remember you cannot root again, as over i am facing problems,,,
check : http://forum.xda-developers.com/showthread.php?t=2494594
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
[email protected] said:
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
Click to expand...
Click to collapse
It is Sprint, and from Hetal. Unrooting and relocking can be a pain, reloading everything. However, for almost two years I did not do any work on the Android side, so have forgotten everything.
I do not mind a locked phone it I can get to 4.3
Can you please pm me with the unrooting, relocking and the 4.3! Root for 4.3 is inevitable - just a matter of time.
Following the GooManager route I managed to get TWRP 2.6.3.0 installed, except the phone did not reboot. I did check it is 2.6.3.0.
Now the problem of the OTA remains. Maybe I will be forced to follow pm.mohanani's route of relocking. I cannot understand if I relock the bootloader then is not the unrooting automatic!
Also, Mr Mohanani GooManager requires root, so do not bother.
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
sgiitk said:
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
Click to expand...
Click to collapse
There is no need to accept the OTA if you are s-off
bigdaddy619 said:
There is no need to accept the OTA if you are s-off
Click to expand...
Click to collapse
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
sgiitk said:
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
Click to expand...
Click to collapse
Install TWRP 2.6.3.0
Option 1 flash SuperSU or another superuser file and run stock rooted
Option 2 flash a custom rom
Still stuck. I downloaded GooManager, and it will go into download > nowstarting and hang forever. I was advised to go the adb fastboot way, i.e.
download latestTWRP image filethen
adb reboot bootloader
then when I get
ui fstboot
fastboot flash recovery <twrp-recovery-name.img>
and its done.
I downloaded the .img file. Put everything into c:\recovery. Moved there under the command prompt. Plugged the phone into the computer, got both the drives (htc sync manager, and HTCONE) . So the connection was kosher.
Then gave adb reboot bootloader
The adb daemon started, but it found no device.
Obviously I being a noob in this game was missing something.
Also, I hear that the ROMs are available which to not reformat the storage. Are these the Deodexed versions or something.
Also, once in ten calls or so the screen goes totally blank at the end and is pain to restart the phone.
Checked up with http://forum.xda-developers.com/showthread.php?t=2497712
Seems that I am S-off but no rooted! Now what??
After a day or so and some cool thought I think I may have the problem identified. It is likely to be the lack of a root. I tried the following and the responses there from:
adb reboot bootloader
rebooted into bootloader Showing relocked and S-off. No fastboot option in the lower menu!
Now:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
I get
sending recovery <8600kB>...
Okay [ 1.140s]
writing 'recovery'...
FAILED <remote not allowed>
finished. total time 1.170s
Any ideas, and when may I expect root for 4.3. At the moment the phone appears to be working file, but no recovery!! HELP!!
Do I need to unlock again despite S-off. Also, then what is the bitstream I send it from 4.3 - the same as the old one!!
Yes you need to unlock your bootloader again to be able to flash twrp
I did as per the htc route - Do the unlock, reinstalled the OS, download the bitstream, etc, and then the OS reloaded. Still Goomanager could not get TWRP 2.6.3.0 so used the fastboot route and succeeded in downloading it to the phone. Thanks for encouraging me and putting me on the right track.
Now ho to root. Then I may as well get Titanium up!
You can get SuperSU or Superuser from the playstore or install a custom rom.
A very interesting experience. I could not enter bootloader [Down-vol + power was just restarting the phone], even adb devices was drawing a blank. So I decided to do a factory reset from phone. Lo and behold it dropped me into the TWRP screen. I managed to root, restarted to the main Downloaded su checker which completed the root. Confirmed. Then downloaded Titanium with Pro license (I have it) and did a recovery. Also, TWRP Manager (downloaded) is working and I am able to start into bootloader, etc.
When I try and look for upgrades with TWRP installer it says none. I know 2.6.3.0 has been upgraded to 2.6.3.2 Let sleeping dogs lie.
Also, I have not checked with adb devices but I am sure that too will now work.
Thanks, but what is going on. Is it only God and maybe Google know what happened?
Thanks for helping, and keeping me going.
I had more or less decided to revert to 4.1 and do an S-on <fastboot oem writesecureflag 3> and bootloader lock and look for OTA!
Added on 25th November
adb still not recognising the beast. adb devices gets a blank list. Phone is available under Windows so drivers etc are Ok.
A noob question. I saw
Stock Rooted 3.04.651.2 Odex & De-Odexed
Insecure Boot img. init.d support, data/app support
Stock Rooted 3.04.651.2 Odex
Stock Rooted 3.04.651.2 De-Odexed
on the upgrade thread. Now what do the terms Rootedm Odex and De-Odexed mean to the average user. Stock means the basic htc ROM I presume.
Also, rooted means what stages are covered.
afaik to upgrade you lock the bootloader, do the upgrade, and then in normal situations again unlock the bootloader, root and install a custom recovery (TWRP does the rooting - hopefully).
Do these ROMs take care of some or more of these stages?

[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] PLEASE POST full STOCK HTC ONE ROM exe for AT&T new kitkat Vers: 4.18.502.7

ISSUE RESOLVED: keeping post since active since I still need the rom exe. But boot looping fixed.
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!
more info
by the way, when it crashed i had installed the ota update and then restarted play around with it, then rebooted in bootloader and unlocked, reinstalled twrp and AndRev HD 51. I've noticed two problems there. The first is that the Xposed module's latest update totally defeats my internet wifi and especially crashes vpn sevice. prior versions did not and I could not down-install to prior version (is preinstalled in HD 51). The other problem is that in looking around for this boot loop probably, turns out that TWRP apparently doesn't get along well with the encryption. don't know why. this stuff may or may not be part of the problem, but at this point i have no OS, an erased cache and can't even get into recovery (tried flashing twrp, older twrps and CWM. thanks.
You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device
randomOne1111 said:
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!
Click to expand...
Click to collapse
This RUU does not exist yet, only the FOTA version - I've been in talks with HTC about this very thing. They do not have an ETA for the RUU, unfortunately.
SaHiLzZ said:
You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device
Click to expand...
Click to collapse
Hm. I did flash the firmware from an OTA. But couldn't actually boot into recovery after that. I can flash custom recoveries but can sideload without the intall stalling about a third of the way through (just hangs, no error messages). Then after that if I restart it loops. I can maybe fix the "tampered" warning and swap it out somewhere. I think it's the encryption while using twrp maybe resulted in some hiccup. But I thought the firmware flash would fix that. And I'm not sure how you can actually tell whether the flashed firmware is successful. (it says it is in the command prompt, but the phone doesn't really do anything all that different and i already updated with the OTA so the numbers won't change).
Looking at the board today and reading through the posts I see many people reporting basically being in the same boot loop boat after the OTA update, though with diff versions maybe there's some FW problem. weird so many posts of similar boot looping.
Thanks for responding.
This issue is temporarily resolved, was able to push ARHD in TWRP (would not sideload without erroring out during install, but was able to push zip to sdcard and then install from there) after much wiping using both twrp and cwm. Did notice when using CWM recovery would not install ARHD off sdcard push, and would flag unknown files .... android..security during wipes, so i am guessing that encrypting a custom ROM at least with TWRP as recovery was a bad idea. hopefully this will stay stable until the KK OEM RUU EXE is available. Thanks for the help.

[Q] Hboot 1.57 OS 5.11.401.10 reboot loop

Hi,
I just got a brand new HTC One 7 (WWE, CID E_11) after my last one died. Im trying to root it and install a custom recovery to install arhd or insertcoin. I used htc one toolkit for this. Everything seemed to work ok, but after booting the installed rom (ARHD or insertcoin) the phone reboots after i see the login screen. I somehow managed to reinstall my phone again yesterday, as it was a complete (soft) brick.
I used this to return to stock:
http://forum.xda-developers.com/showthread.php?t=2759000
Now does anyone know why I get a reboot loop? Does anyone know if i installed this stock rom if I get the normal OTA updates again? And do i need to relock the bootloader for this? I would really like to install stock roms again but I'm a little anxious after yesterday. (I've installed custom roms since the old HD2/HTC desire, and also on my old HTC One M7, never had any problems, I think it has to do with the Hboot).
Hoping to hear from you guys,
best wishes,
Olaf
Agil1ty said:
Hi,
I just got a brand new HTC One 7 (WWE, CID E_11) after my last one died. Im trying to root it and install a custom recovery to install arhd or insertcoin. I used htc one toolkit for this. Everything seemed to work ok, but after booting the installed rom (ARHD or insertcoin) the phone reboots after i see the login screen. I somehow managed to reinstall my phone again yesterday, as it was a complete (soft) brick.
I used this to return to stock:
http://forum.xda-developers.com/showthread.php?t=2759000
Now does anyone know why I get a reboot loop? Does anyone know if i installed this stock rom if I get the normal OTA updates again? And do i need to relock the bootloader for this? I would really like to install stock roms again but I'm a little anxious after yesterday. (I've installed custom roms since the old HD2/HTC desire, and also on my old HTC One M7, never had any problems, I think it has to do with the Hboot).
Hoping to hear from you guys,
best wishes,
Olaf
Click to expand...
Click to collapse
Flash the stock firmware 5.11.401.10! I think your firmware is mismatched.
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Agil1ty said:
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Flashing the firmware might fix the boot-loop, since you flashed the stock rom! If it does stop the boot-loops, you can re-install TWRP or CWM to get the custom recovery.
Agil1ty said:
By flashing the firmware after installing the Rom I might fix the bootloop? Or is the stock firmware necesarry to go back to stock? Sorry bit confused, thanks for your response btw
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
when using a sense custom rom you need to make sure you use twrp 2.6.3.3 recovery, do not use the toolkits, most of the time they are out of date and not updated, this would explain the bootloops, take the time to learn how to use adb and fastboot, you'll never look back.
nothing to do with the firmware and no need to flash it, if your firmware was knackered, you would have a hard brick.
Seanie280672 said:
when using a sense custom rom you need to make sure you use twrp 2.6.3.3 recovery, do not use the toolkits, most of the time they are out of date and not updated, this would explain the bootloops, take the time to learn how to use adb and fastboot, you'll never look back.
nothing to do with the firmware and no need to flash it, if your firmware was knackered, you would have a hard brick.
Click to expand...
Click to collapse
First of all thanks for the quick response. I know how to use adb and fastboot (at least I think).
If i would (in this order) do the following, would that be correct?:
unlock using htdev
Flash twrp 2.6.3.3 using fastboot command: "fastboot flash recovery recovery.img" (naming twrp 2.6.3.3.img = recovery.img)
reboot bootloader
Flash SuperSU.zip in TWRP
reboot twrp
flash custom rom (ARHD).
The thing is it isn't a normal bootloop (which normally would come with the HTC logo all the time)
It reboots when I try to setup the phone (in the setup menu). Restoring the phone with the link in the OP, ive recoverd my phone, but I would still love to use custom roms again.
Agil1ty said:
First of all thanks for the quick response. I know how to use adb and fastboot (at least I think).
If i would (in this order) do the following, would that be correct?:
unlock using htdev
Flash twrp 2.6.3.3 using fastboot command: "fastboot flash recovery recovery.img" (naming twrp 2.6.3.3.img = recovery.img)
reboot bootloader
Flash SuperSU.zip in TWRP
reboot twrp
flash custom rom (ARHD)
Click to expand...
Click to collapse
unlock using HTC Dev
flash TWRP 2.6.3.3
fastboot erase cache
fastboot reboot-bootloader
enter recovery
no need to flash super user it will be included in the rom you flash
flash custom rom, or stock reset rom, if its not rooted, twrp will ask you if you would like to root upon exit.
Seanie280672 said:
unlock using HTC Dev
flash TWRP 2.6.3.3
fastboot erase cache
fastboot reboot-bootloader
enter recovery
no need to flash super user it will be included in the rom you flash
flash custom rom, or stock reset rom, if its not rooted, twrp will ask you if you would like to root upon exit.
Click to expand...
Click to collapse
It seems that insertcoin had a problem in it's installer:
http://insertcoin-roms.org/category/devices/one_m7/one_sense6/
the changelog says: Fixed SuperSU install (might solve the sudden reboot issue in SetupWizard)
It left me without any rom to install, so i had to sideload ARHD, which it didnt want to install via sideload... The next step I isntalled stock again, which I'm using right now.. but I miss xposed framework and other tweaks too much..
I'm gonna try to unlock it again this afternoon and install insertcoin again, but this time ill make a backup first. Does installing the recovery wipe anything?
Agil1ty said:
It seems that insertcoin had a problem in it's installer:
http://insertcoin-roms.org/category/devices/one_m7/one_sense6/
the changelog says: Fixed SuperSU install (might solve the sudden reboot issue in SetupWizard)
It left me without any rom to install, so i had to sideload ARHD, which it didnt want to install via sideload... The next step I isntalled stock again, which I'm using right now.. but I miss xposed framework and other tweaks too much..
I'm gonna try to unlock it again this afternoon and install insertcoin again, but this time ill make a backup first. Does installing the recovery wipe anything?
Click to expand...
Click to collapse
no it doesn't wipe anything, but you can use xposed and its tweaks on stock rom, you just need to root first, just install TWRP, enter recovery and again upon exit it will offer to root stock rom for you.

Problems with updating CM12

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.

Categories

Resources