Related
Has anyone experienced this? I have to force reboot when I load into recovery.
It's a new phone from the factory, it's unlocked and has TWRP 2.6.00
Drakeskakes said:
Has anyone experienced this? I have to force reboot when I load into recovery.
It's a new phone from the factory, it's unlocked and has TWRP 2.6.00
Click to expand...
Click to collapse
please specify the device, or just post a fastboot getvar all (excluding IMEI and s/n)
2.6.0.0 sound kind of outdated
Sounds like a firmware issue, you need be firnware with new touch screen driver
HTC One
Like nkk71 said get TWRP 2.6.3.4
I just went with Clockwork. I only wanted to use TRWP because my old phone had it, and I hate learning new things. Now I'm trying to do the OTA Kitkat update and it's not working. I hate these stupid phones
Drakeskakes said:
I just went with Clockwork. I only wanted to use TRWP because my old phone had it, and I hate learning new things. Now I'm trying to do the OTA Kitkat update and it's not working. I hate these stupid phones
Click to expand...
Click to collapse
you can't get OTA update with any custom recovery
you need stock recovery....
If you want help, post your fastboot getvar all minus serial no and IMEI
clsA said:
you can't get OTA update with any custom recovery
you need stock recovery....
If you want help, post your fastboot getvar all minus serial no and IMEI
Click to expand...
Click to collapse
So, to upgrade to Kit-kat then CM11 ....do I have to do a complete factory reset, then OTA update, then do unlock/root/s-off and install rom?
Why would you install kitkat then Cm 11?
Sent from my HTC One using Tapatalk 4
clsA said:
Why would you install kitkat then Cm 11?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Doesn't CM11 need to piggy back off Kitkat? I always hear "CM for Kitkat" and when I go to Goomanager, it doesn't give me CM11 only 10.1
All I want to CM on my phone, Im rooted, have CMW premium, SUperSU and unlocked...
When I go to CWM, it doesn't work, when I try and DL from Goo, it doesn't work, when I try to download from CM app, doesn't work. I'm going to throw this phone across the room. I hve done custom roms before, but always using a toolkit for PC. I only have access to a mac for the time being
Drakeskakes said:
Doesn't CM11 need to piggy back off Kitkat? I always hear "CM for Kitkat" and when I go to Goomanager, it doesn't give me CM11 only 10.1
Click to expand...
Click to collapse
No and why do you have 2 threads going ?
here's CM 11
http://forum.xda-developers.com/showthread.php?t=2579229
The Device must be unlocked and equipped with a Recovery,
you need a ROM.zip and optional GAPPS,the Download Links will you find here.
At first,make a Nandroid-Backup of your existing system!
When you first time flash the ROM or you changed from another ROM-Base,
do a Full Wipe via Recovery,flash the ROM, and then the GAPPS.
Restart to System,configure and enjoy CM11.
Click to expand...
Click to collapse
Are you still with hboot 1.44? Upgrade to have a newer touch driver pls
Sent from my HTC One using xda app-developers app
clsA said:
No and why do you have 2 threads going ?
here's CM 11
http://forum.xda-developers.com/showthread.php?t=2579229
Click to expand...
Click to collapse
This thread was only about TWRP not working, but someone piggy backed off this conversations after I started the other one.
clsA said:
No and why do you have 2 threads going ?
here's CM 11
http://forum.xda-developers.com/showthread.php?t=2579229
Click to expand...
Click to collapse
is GSM version for Sprint...before I go through with the DL
Drakeskakes said:
is GSM version for Sprint...before I go through with the DL
Click to expand...
Click to collapse
No... Why are you in the GSM forums ??
you most likely have the wrong recovery installed also
does your recovery file say m7wls ?
you need to be here getting your files
http://forum.xda-developers.com/sprint-htc-one
clsA said:
No... Why are you in the GSM forums ??
you most likely have the wrong recovery installed also
does your recovery file say m7wls ?
you need to be here getting your files
http://forum.xda-developers.com/sprint-htc-one
Click to expand...
Click to collapse
I have the proper recovery installed
Recovery-clockwork-touch-6.0.3.2-m7spr.img
I just tried this
Install zip from sdcard->
choose zip from sdcard->
0/ ->
Download ->
cm-11-20140309-NIGHTLY-myspr.zip
The log says
Installing update...
set_metadata_recursive:some changes failed
E:Error in /sdcard/o/Downoad/cm-11-20140309-NIGHTLY-M7spr.zip
(Status 7)
Installion Aborted
Drakeskakes said:
I have the proper recovery installed
Recovery-clockwork-touch-6.0.3.2-m7spr.img
I just tried this
Install zip from sdcard->
choose zip from sdcard->
0/ ->
Download ->
cm-11-20140309-NIGHTLY-myspr.zip
The log says
Installing update...
set_metadata_recursive:some changes failed
E:Error in /sdcard/o/Downoad/cm-11-20140309-NIGHTLY-M7spr.zip
(Status 7)
Installion Aborted
Click to expand...
Click to collapse
During the install, it aborted and now the stock rom won't load. It keep going into recovery and I have nothing to load it to. I can't shut it off, and I would like to just work on it tommorow. If it dies, I'm worried I wont be able to charge it back up to work on it. Now I'm pretty worried
Nevermind CM11 now working, switched from CWM to TWRP andf it works great
Hello, I'm new to this forum. So I'm trying to get ViperOne ROM to work, but after install it just goes into a boot loop. It says the install was successful...
HTC One m7 Verizon
android 4.4.2
was on stock rom before
TWRP recovery 2.7.1.1
Already tried:
factory reset before flashing
wiping cache and dalvik cache
flashing the boot.img separately via fastboot
wiping cache with fastboot after flashing rom
Everything I look at just says to factory reset and wipe cache to fix boot loop, but it's not working for me. What do I do?
Thanks for the help!
kyle7kyle said:
Hello, I'm new to this forum. So I'm trying to get ViperOne ROM to work, but after install it just goes into a boot loop. It says the install was successful...
HTC One m7 Verizon
android 4.4.2
was on stock rom before
TWRP recovery 2.7.0.1
Already tried:
factory reset before flashing
wiping cache and dalvik cache
flashing the boot.img separately via fastboot
wiping cache with fastboot after flashing rom
Everything I look at just says to factory reset and wipe cache to fix boot loop, but it's not working for me. What do I do?
Thanks for the help!
Click to expand...
Click to collapse
Do a clean install with TWRP 2.6.3.3...
iBalajiS said:
Do a clean install with TWRP 2.6.3.3...
Click to expand...
Click to collapse
Thanks I'll try that and let you know how it goes...
iBalajiS said:
Do a clean install with TWRP 2.6.3.3...
Click to expand...
Click to collapse
I flahsed TWRP 2.6.3.3 for the htc one m7 and now when I try to go into recovery it reboots the phone. I can't get into recovery now
kyle7kyle said:
I flahsed TWRP 2.6.3.3 for the htc one m7 and now when I try to go into recovery it reboots the phone. I can't get into recovery now
Click to expand...
Click to collapse
Okay... This is what I did. Downloaded TWRP 2.6.3.3, installed it with "Flashify", rebooted to recovery, wiped cache/dalvik, flashed Viper One ROM, rebooted the device..
Sent from my HTC One (On Viper One) using Tapatalk
iBalajiS said:
Okay... This is what I did. Downloaded TWRP 2.6.3.3, installed it with "Flashify", rebooted to recovery, wiped cache/dalvik, flashed Viper One ROM, rebooted the device..
Sent from my HTC One (On Viper One) using Tapatalk
Click to expand...
Click to collapse
Tried installing TWRP 2.6.3.3 with Flashify instead of fastboot way but it still didn't work, it said entering recovery then rebooted phone.
kyle7kyle said:
Tried installing TWRP 2.6.3.3 with Flashify instead of fastboot way but it still didn't work, it said entering recovery then rebooted phone.
Click to expand...
Click to collapse
I guess some senior members alone would be able to assist you with this... Sorry
First thing, read the first post properly.
He has a Verizon one M7 completely different to the normal gsm version of these phones, normal twrp recovery won't work and nor will gsm roms.
Have a look in the M7 Verizon forum for roms you can flash and recoveries built for your device
http://forum.xda-developers.com/verizon-htc-one?nocache=1&z=9962053797207772
Seanie280672 said:
First thing, read the first post properly.
He has a Verizon one M7 completely different to the normal gsm version of these phones, normal twrp recovery won't work and nor will gsm roms.
Have a look in the M7 Verizon forum for roms you can flash and recoveries built for your device
http://forum.xda-developers.com/verizon-htc-one?nocache=1&z=9962053797207772
Click to expand...
Click to collapse
Yes.... You are right, sorry.
iBalajiS said:
Yes.... You are right, sorry.
Click to expand...
Click to collapse
No need to be sorry chief, we are only human and all make mistakes, just a learning curve.
Seanie280672 said:
First thing, read the first post properly.
He has a Verizon one M7 completely different to the normal gsm version of these phones, normal twrp recovery won't work and nor will gsm roms.
Have a look in the M7 Verizon forum for roms you can flash and recoveries built for your device
http://forum.xda-developers.com/verizon-htc-one?nocache=1&z=9962053797207772
Click to expand...
Click to collapse
So are you saying that the Viper One ROM is not compatible with the Verizon HTC one?
kyle7kyle said:
So are you saying that the Viper One ROM is not compatible with the Verizon HTC one?
Click to expand...
Click to collapse
You need to use Verizon TWRP ... find it yourself.
Verizon Viper One: http://forum.xda-developers.com/showthread.php?t=2590358
kyle7kyle said:
So are you saying that the Viper One ROM is not compatible with the Verizon HTC one?
Click to expand...
Click to collapse
You flashed the wrong version of viper one for your phone, see the link above, but first you need to find the correct TWRP for your phone.
Here it is: http://goo.im/devs/Flyhalf205/M7VZW you want TWRP 2.6.3.3
Seanie280672 said:
You flashed the wrong version of viper one for your phone, see the link above, but first you need to find the correct TWRP for your phone.
Here it is: http://goo.im/devs/Flyhalf205/M7VZW you want TWRP 2.6.3.3
Click to expand...
Click to collapse
I got it working thank you! The viper one rom was the right version but I guess I didn't download the twrp for verizon, my bad.
kyle7kyle said:
I got it working thank you! The viper one rom was the right version but I guess I didn't download the twrp for verizon, my bad.
Click to expand...
Click to collapse
Cheers...
+1
Hey guys. I've got TWRP 2.7.1.1 installed, but have been unable to flash 4.4.4 ROMs. They fail every time. Those who know my situation know my phone was recently soft bricked after I installed tdhite's TWRP 2.7.1.3 for Sprint HTC One m7. After restoring using RUU and reunlocking the bootloader and flashing SuperSU, I got everything working again and luckily had a backup of one of my favorite HTC One setups using the stock ROM only, along with Xposed framework.
Anyway:I was playing around in TWRP today and went to Mount and noticed that the system partition is not mounted. I'm thinking this may be why I am having trouble flashing ROMs. Should I just click on the system partition to mount it and then try to flash one of the custom AOSP ROMS?
MarkBell said:
Hey guys. I've got TWRP 2.7.1.1 installed, but have been unable to flash 4.4.4 ROMs. They fail every time. Those who know my situation know my phone was recently soft bricked after I installed tdhite's TWRP 2.7.1.3 for Sprint HTC One m7. After restoring using RUU and reunlocking the bootloader and flashing SuperSU, I got everything working again and luckily had a backup of one of my favorite HTC One setups using the stock ROM only, along with Xposed framework.
Anyway:I was playing around in TWRP today and went to Mount and noticed that the system partition is not mounted. I'm thinking this may be why I am having trouble flashing ROMs. Should I just click on the system partition to mount it and then try to flash one of the custom AOSP ROMS?
Click to expand...
Click to collapse
no, I don't be-leave it will do anything for you
clsA said:
no, I don't be-leave it will do anything for you
Click to expand...
Click to collapse
What about flashing an earlier version of TWRP and then flashing 2.7.1.1 again? I'm really wanting to try out the GPS fix recommended for the AOSP ROMs.
MarkBell said:
What about flashing an earlier version of TWRP and then flashing 2.7.1.1 again? I'm really wanting to try out the GPS fix recommended for the AOSP ROMs.
Click to expand...
Click to collapse
use that CWM recovery you have
clsA said:
use that CWM recovery you have
Click to expand...
Click to collapse
Still no dice using TWRP or CWM. I'm screwed. Can't flash ANYTHING at all through any version of TWRP or CWM.
Stuck on rooted stock with Xposed tweaks for now, I suppose.
Anyone think it's worth a try to sideload a rom?
MarkBell said:
Those who know my situation
Click to expand...
Click to collapse
Why do you expect us to be familiar with your situation?
MarkBell said:
Anyway:I was playing around in TWRP today and went to Mount and noticed that the system partition is not mounted. I'm thinking this may be why I am having trouble flashing ROMs. Should I just click on the system partition to mount it and then try to flash one of the custom AOSP ROMS?
Click to expand...
Click to collapse
most (probably all) installer scripts mount and unmount (possibly even format) the partitions it needs.
MarkBell said:
Hey guys. I've got TWRP 2.7.1.1 installed, but have been unable to flash 4.4.4 ROMs.
Click to expand...
Click to collapse
you need to start providing more details, a good starting point is usually:
1- a "fastboot getvar all" (excluding IMEI, MEID, S/N)
2- name and version of recovery you are using (yes, you did mention that, next time add it's the sprint variant as most of us are on m7_u/ul)
3- what you are trying flash (including link)
4- what error does the installer throw? "unable to flash" is very vague
nkk71 said:
Why do you expect us to be familiar with your situation?
most (probably all) installer scripts mount and unmount (possibly even format) the partitions it needs.
you need to start providing more details, a good starting point is usually:
1- a "fastboot getvar all" (excluding IMEI, MEID, S/N)
2- name and version of recovery you are using (yes, you did mention that, next time add it's the sprint variant as most of us are on m7_u/ul)
3- what you are trying flash (including link)
4- what error does the installer throw? "unable to flash" is very vague
Click to expand...
Click to collapse
It's ok ..I been helping him for a few days
he has a sprint phone and was softbricked from a bad recovery install. So he's kinda gun shy on flashing recovery's.
He wants to use an AOSP Rom that's kitkat 4.4.4 but all the normal versions of recovery have trouble flashing.
Hello, this is my first time on XDA so if I make any mistakes please forgive me .
I have unlocked the bootloader on my Sprint HTC One m7, and I can't find any guides on how to root my phone with its current stock Andriod version. It has version 4.4.2 with HTC version 6.0. Can anyone point me towards a good guide?
Thanks!
Lifehags said:
Hello, this is my first time on XDA so if I make any mistakes please forgive me .
I have unlocked the bootloader on my Sprint HTC One m7, and I can't find any guides on how to root my phone with its current stock Andriod version. It has version 4.4.2 with HTC version 6.0. Can anyone point me towards a good guide?
Thanks!
Click to expand...
Click to collapse
Welcome to xda!
Since your bootloader is already unlocked, then all you need to do is to flash a custom recovery like TWRP.
With the recovery.img in the same folder where you have adb and fastboot and your phone booted in bootloader/fastboot usb mode, open a command prompt and type:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then reboot in recovery mode by selecting "recovery" in the bootloader. Once booted in TWRP recovery, just select to reboot to system and the recovery will detect that your phone isn't rooted and will ask if you want to root it. Select "yes". Then once rebooted in the OS, you should have supersu in your app drawer.
Don't forget sprint variant of the One isn't the same phone as the international gsm variant so always flash files (Custom recovery/ custom roms/ Custom kernel) compatible for sprint (M7WLS sometime called M7SPR)
alray said:
Welcome to xda!
Since your bootloader is already unlocked, then all you need to do is to flash a custom recovery like
With the recovery.img in the same folder where you have adb and fastboot and your phone booted in bootloader/fastboot usb mode, open a command prompt and type:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then reboot in recovery mode by selecting "recovery" in the bootloader. Once booted in TWRP recovery, just select to reboot to system and the recovery will detect that your phone isn't rooted and will ask if you want to root it. Select "yes". Then once rebooted in the OS, you should have supersu in your app drawer.
Don't forget sprint variant of the One isn't the same phone as the international gsm variant so always flash files (Custom recovery/ custom roms/ Custom kernel) compatible for sprint (M7WLS sometime called M7SPR)
Click to expand...
Click to collapse
That's all? Also, using this procedure, if I update will my root be broken or Will I still have root? Also if it brakes my root what will happenen to the stuff that I gave root permission too? And stuff like that? Thanks for all the help!
Lifehags said:
That's all? Also, using this procedure, if I update
Click to expand...
Click to collapse
You'll maybe not be able to update. When you unlock the bootloader, /data/preload and its content is wiped (some of HTC preloaded apps, weather animations etc). These apps are sometime updated during an ota update and if they are missing, like after unlocking the bootloader. the ota installation will fail. You also need to flash your stock recovery back before an ota update.
will my root be broken or Will I still have root?
Click to expand...
Click to collapse
You'll loose root. All you have to do is to root again after the ota update.
Also if it brakes my root what will happenen to the stuff that I gave root permission too? And stuff like that? Thanks for all the help!
Click to expand...
Click to collapse
They will still be installed but they won't work, or at least, there functions requiring root will not work.
alray said:
You'll maybe not be able to update. When you unlock the bootloader, /data/preload and its content is wiped (some of HTC preloaded apps, weather animations etc). These apps are sometime updated during an ota update and if they are missing, like after unlocking the bootloader. the ota installation will fail. You also need to flash your stock recovery back before an ota update.
You'll loose root. All you have to do is to root again after the ota update.
They will still be installed but they won't work, or at least, there functions requiring root will not work.
Click to expand...
Click to collapse
Thanks for all the help!
alray said:
You'll maybe not be able to update. When you unlock the bootloader, /data/preload and its content is wiped (some of HTC preloaded apps, weather animations etc). These apps are sometime updated during an ota update and if they are missing, like after unlocking the bootloader. the ota installation will fail. You also need to flash your stock recovery back before an ota update.
You'll loose root. All you have to do is to root again after the ota update.
They will still be installed but they won't work, or at least, there functions requiring root will not work.
Click to expand...
Click to collapse
I used adb to make a backup and restore so I should be able to install ota updates
Lifehags said:
I used adb to make a backup and restore so I should be able to install ota updates
Click to expand...
Click to collapse
So you have backed up /data/preload before unlocking?
alray said:
You'll maybe not be able to update. When you unlock the bootloader, /data/preload and its content is wiped (some of HTC preloaded apps, weather animations etc). These apps are sometime updated during an ota update and if they are missing, like after unlocking the bootloader. the ota installation will fail. You also need to flash your stock recovery back before an ota update.
You'll loose root. All you have to do is to root again after the ota update.
They will still be installed but they won't work, or at least, there functions requiring root will not work.
Click to expand...
Click to collapse
alray said:
So you have backed up /data/preload before unlocking?
Click to expand...
Click to collapse
Yup
Lifehags said:
Yup
Click to expand...
Click to collapse
:good:
alray said:
:good:
Click to expand...
Click to collapse
Any alternative to twrp, it seems like a lot of people are having problems with it.
Lifehags said:
Any alternative to twrp, it seems like a lot of people are having problems with it.
Click to expand...
Click to collapse
TWRP is the preferred recovery of M7 but you can also use CWM
alray said:
:good:
Click to expand...
Click to collapse
Lifehags said:
Any alternative to twrp, it seems like a lot of people are having problems with it.
Click to expand...
Click to collapse
Should I go with the latest version of 2.8, or do you suggest a eilear version?
Lifehags said:
Should I go with the latest version of 2.8, or do you suggest a eilear version?
Click to expand...
Click to collapse
if you are only going to root and not flashing rom then use any version you want, the latest should be fine. If you want to flash a custom rom, use the recovery mentioned in the rom OP.
alray said:
if you are only going to root and not flashing rom then use any version you want, the latest should be fine. If you want to flash a custom rom, use the recovery mentioned in the rom OP.
Click to expand...
Click to collapse
Alright, thanka for all of the help!
Lifehags said:
Alright, thanka for all of the help!
Click to expand...
Click to collapse
youre welcome
So i have a htc one phone but...i tried every root programs,none work
Is there an toolkit or some thing i am doing wrong?
cod3_r3mors3 said:
So i have a htc one phone but...i tried every root programs,none work
Is there an toolkit or some thing i am doing wrong?
Click to expand...
Click to collapse
Don't use any programs, just flash SuperSU.zip
Sent from my One using XDA Labs
cod3_r3mors3 said:
So i have a htc one phone but...i tried every root programs,none work
Is there an toolkit or some thing i am doing wrong?
Click to expand...
Click to collapse
You should give more information like your bootloader version, recovery version, what programs have you tried etc.
Usually to root m7 you'll need:
1 - htc dev unlocked bootloader
2 - custom recovery like TWRP
3 - Supersu.zip to flash in recovery
macicgangsta said:
3 - Supersu.zip to flash in recovery
Click to expand...
Click to collapse
I'll also add "make sure to use the latest supersu version" because old versions are known to cause bootloops when used on Lollipop+ roms. :good:
So i tried installing supersu with twrp but it was giving errors,I saw that i needed to wipe cache and stuff and so i did...Plus my stock htc one os.Now i am trying to install AOKP rom on my device but its giving error with the zip file and binaries
tried wiping still not worked.Please help me asap
bump
cod3_r3mors3 said:
So i tried installing supersu with twrp but it was giving errors,I saw that i needed to wipe cache and stuff and so i did...Plus my stock htc one os.Now i am trying to install AOKP rom on my device but its giving error with the zip file and binaries
tried wiping still not worked.Please help me asap
bump
Click to expand...
Click to collapse
You haven't provided any information about your phone yet, like suggested by @macicgangsta. Please post the output of "fastboot getvar all" (hide your IMEI and SerialNo). What twrp version are you using and what supersu version? What was the errors when flashing supersu? When flashing the rom? What rom version is it exactly...? ideally post a link to that rom and/or everything else you've tried to flash.
reporting problems precisely = fast & efficient troubleshooting :good: