Help needed - One (M7) Q&A, Help & Troubleshooting

I've posted this in the sprint m7 forums with no help so far. Going fishing here to see if i can get some help
I was updating my m7spr to the latest cm12 nightly, which i've been doing about once a week, and all of a sudden I cannot update apps from the play store or install any apks from my storage. I go to factory reset or uninstall some apps to make some room, and the apps won't uninstall and my recovery, TWRP, is gone. It flashes the TWRP logo and then restarts. I am currently at the bootloader screen unlocked s-on and have been trying to fastboot flash everything i can think of from a cm12 rom zip, a stock sense zip, a twrp recovery zip and img. nothing is working. I have tried to relock my bootloader and run a RUU, from the latest RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.6_Radio_1.01.20.1225_CNV_CNV_SPCS_4.38_003_release_425282_signed_2 to an earlier version Sprint_HTC_One_m7wls_1.29.651.10_RUU and that didn't work either. sat at the htc/ruu screen for a half hour with no result.
I am at a loss as to what to do next and what will work to get my damn phone back to working order.
My h-boot is 1.56.0000 and again i am S-ON
Thanks in advance for your assistance
Sent from my MoPhoKing using XDA Free mobile app

bullfrog527 said:
I've posted this in the sprint m7 forums with no help so far. Going fishing here to see if i can get some help
I am at a loss as to what to do next and what will work to get my damn phone back to working order.
My h-boot is 1.56.0000 and again i am S-ON
Thanks in advance for your assistance
Sent from my MoPhoKing using XDA Free mobile app
Click to expand...
Click to collapse
flash same version firmware as now you have then flash TWRP again

yatindroid said:
flash same version firmware as now you have then flash TWRP again
Click to expand...
Click to collapse
So, flash a ruu? Or something else
Sent from my MoPhoKing phone

bullfrog527 said:
So, flash a ruu? Or something else
Sent from my MoPhoKing phone
Click to expand...
Click to collapse
my answer was for twrp issues
After that flash whatever you like
RUU need locked bootloader cid mid match flash same or higher version ruu

I can't flash TWRP, it says it flashed but when I reboot recovery it just flashes the TWRP splash screen then goes to the.bootloader
Sent from my MoPhoKing phone

bullfrog527 said:
I can't flash TWRP, it says it flashed but when I reboot recovery it just flashes the TWRP splash screen then goes to the.bootloader
Sent from my MoPhoKing phone
Click to expand...
Click to collapse
did yoy flashed firmware ?

yatindroid said:
did yoy flashed firmware ?
Click to expand...
Click to collapse
Found a ruu that finally worked from here
http://forum.xda-developers.com/showthread.php?t=2363516
[Unbrick Service] Bricked Phone? Need Help? Look Here.

Related

HTC One stock recovery

Hi guys,
I have been searching everywhere for a link to download the HTC one stock recovery, but I just seem to not be able to find it. Could anyone please give me the link to a stock recovery, and a guide as to how I would install it.
Thanks
Sent from my HTC One using xda app-developers app
Flash this in your current custom recovery and reboot
https://www.dropbox.com/s/88goq8ipbsfbxp4/StockRecovery-signed.zip
Thanks do much
Sent from my HTC One using xda app-developers app
sam_hoddi said:
Thanks do much
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
are you going to flash the stock recovery to get the 4.2.2 ota?
shaggydiamond said:
are you going to flash the stock recovery to get the 4.2.2 ota?
Click to expand...
Click to collapse
I'm about to do the same, is there something I should know?
shaggydiamond said:
are you going to flash the stock recovery to get the 4.2.2 ota?
Click to expand...
Click to collapse
Newbie question ...
I have htc one 801n unlocked bootloader and rooted ..
version 1.29.401.16
I want to get 4.2.2 ota ... should I relock bootloader then flash this stock recovery ???
any advice ???
sadek169 said:
Newbie question ...
I have htc one 801n unlocked bootloader and rooted ..
version 1.29.401.16
I want to get 4.2.2 ota ... should I relock bootloader then flash this stock recovery ???
any advice ???
Click to expand...
Click to collapse
1. Flash Stock Recovery
2. RElock BootLoader
3. Flash RUU ( If You Have Custom Rom )
4. Upgrade To 4.2.2
Hi guys, im trying flash the stock recovery to get the 4.2.2 ota. my ver is 1.28.771.6/ CID H3G__001
so i found on xda:
CWM Nandroid Backup / CID H3G__001 / 1.28.771.x
trying flash it(CWM) and got message instalation aborted, what i do wrong ?
A.H.GH said:
1. Flash Stock Recovery
2. RElock BootLoader
3. Flash RUU ( If You Have Custom Rom )
4. Upgrade To 4.2.2
Click to expand...
Click to collapse
do you have any stock recovery image?
Won't Flash
Matt said:
Flash this in your current custom recovery and reboot
Click to expand...
Click to collapse
I just tried doing this, but I am getting an error when I try to flash the stock recovery. It just says "(status 6) Installation aborted." I'm using CWM Recovery, should I maybe try using TWRP instead or should that not matter?
goldenninja said:
I just tried doing this, but I am getting an error when I try to flash the stock recovery. It just says "(status 6) Installation aborted." I'm using CWM Recovery, should I maybe try using TWRP instead or should that not matter?
Click to expand...
Click to collapse
Maybe check if others have flashed it correctly, as I didn't test it and maybe you can't flash a stock recovery in a custom one
Confirmation
Hi,
I've just installed this recovery to my HTC ONE 32GB VODAP001.
My method was to extract the recovery.img from the zip file and flash via fastboot (fastboot flash recovery recovery.img)
worked fine - no issues, boots to the phone picture with a green arrow.
Hope that helps.
Solcenva
EDIT: My previous recovery was TWRP 2.6.0.1
tommykwan222 said:
do you have any stock recovery image?
Click to expand...
Click to collapse
for u ...
http://forum.xda-developers.com/showthread.php?p=43850756#post43850756
Sorry to bring this thread back...
For anyone still trying to update to 4.2.2 on a rooted phone here are the steps I took to do it.
1.Flash stock recovery (link earlier in thread)
2.Update
3.Reflash your custom recovery (I used TWRP)
4.Reinstall superuser
That should be it
Sent from my HTC One using xda app-developers app
Could somebody please repost the file? Link doesn't work for me
jeroenpico said:
Could somebody please repost the file? Link doesn't work for me
Click to expand...
Click to collapse
https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
Flashed stock recovery
Thanks! Now hopefully I can get the latest HTC Google Edition OTA update. Clockworkmod rejected the latest one: JWR66Y
Noob question: What does the stock recovery actually do?
I havn't unlocked bootloader yet, and accidentially started stock recovery from the bootloader screen and started to panic when an image with a red triangle was shown for what seemed like ages. Fortunately the phone booted up normally, but I wonder what I actually did?
BTW how does OTA update work, how to get it?
sblar said:
Noob question: What does the stock recovery actually do?
I havn't unlocked bootloader yet, and accidentially started stock recovery from the bootloader screen and started to panic when an image with a red triangle was shown for what seemed like ages. Fortunately the phone booted up normally, but I wonder what I actually did?
BTW how does OTA update work, how to get it?
Click to expand...
Click to collapse
All I know is I flashed the Google Edition ROM on my HTC One in July (was T-Mobile Sense version). 2 days ago I got an OTA notification for an Android 4.3 update (JWR66Y). I couldn't install it because I had Clockworkmod as a custom recovery. My hope is that with this stock recovery I can receive this OTA update fine. I haven't gotten the notification yet, so I don't know if it'll work. If it does work, then I'll be ready for Google Edition Kit Kat in October.
sblar said:
BTW how does OTA update work, how to get it?
Click to expand...
Click to collapse
This method works:
Go to Settings > Apps (or Applications) and select show All. Then find Google Services Framework and click the Clear Data button. Then click the Force Stop button. Then go to Settings > About phone > System updates
The stock recovery also worked! I was able to get an OTA update and install it on HTC One which I turned into a Google Edition (originally a T-Mobile with Sense). Now with JWR66Y.H1. Just let the phone do its thing. It takes a while and there are no real status messages. It'll reboot a few times. Don't worry it works. Just be patient.
I think the same method will work when Kit Kat comes out in October.
I am not rooted, I have S-off, and I didn't change model or carrier IDs. I still received the OTA update.

HELP PLEASE Can't get past boot splash screen on my phone?

Hi all, I just tried to update my firmware to remove the red text on the boot screen and now I can't get any further than the boot screen.
I can still get in to the bootloader but it won't go any further than the boot splash.
Could someone help please??
Cheers all.
Seems rom isn't installed.
Which rom did you have?
And, you can boot in recovery?
Guich said:
Seems rom isn't installed.
Which rom did you have?
And, you can boot in recovery?
Click to expand...
Click to collapse
Thanks. Yeah I had Viperom 2.7.
And yeah I can get in to TWRP no problems
happysteveo said:
Thanks. Yeah I had Viperom 2.7.
And yeah I can get in to TWRP no problems
Click to expand...
Click to collapse
So reflash the rom without any wipe
And which firmware you've installed?
Guich said:
So reflash the rom without any wipe
And which firmware you've installed?
Click to expand...
Click to collapse
Thanks. I tried to flash the rom in adb but it said
writing zip...
then
failed <remote: not allowed>
Do you know what I can do next?
It was this firmware: 14.06.2013 Update: added 1.54.0000 from Base 2.17 Modified - red warning removed.
happysteveo said:
Thanks. I tried to flash the rom in adb but it said
writing zip...
then
failed <remote: not allowed>
Do you know what I can do next?
It was this firmware: 14.06.2013 Update: added 1.54.0000 from Base 2.17 Modified - red warning removed.
Click to expand...
Click to collapse
Oh, you flashed only the hboot patched and rom won't boot...
I mean you have to flash the rom from recovery
Guich said:
Oh, you flashed only the hboot patched and rom won't boot...
I mean you have to flash the rom from recovery
Click to expand...
Click to collapse
How do I do that? When I am in recovery and I select restore, there is nothing there.
I have a backup saved but it doesn't seem to be showing up.
i take it you've got s-off,goto htc1guru.com,look for ruu zip for flashing via fastboot,it will reset your phone to fully stock,guides on how to do it are on the site also
Sent from my S-Off 801n M7_UL
steelmaggot said:
i take it you've got s-off,goto htc1guru.com,look for ruu zip for flashing via fastboot,it will reset your phone to fully stock,guides on how to do it are on the site also
Sent from my S-Off 801n M7_UL
Click to expand...
Click to collapse
Okay, is there no way of getting a viperone zip file from my pc to install on to the phone?
You need to sideload the rom via adb. Then you'll be able to flash it from recovery.
Sent from my HTC One using Tapatalk
Evil-Dragon said:
You need to sideload the rom via adb. Then you'll be able to flash it from recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks, have tried but it can't find the file when I type the command in cmd.and it says that there is no such file or directory. I think I may have to go down the RUU route.

How do I fix my phone?

I successfully had Cyanogenmod installed, but now when I turn my phone on it stays stuck at the loading screen and goes back and forth to the HTC start up (the screen before the Cyanogen loading screen). I tried reverting back to stock using the RUU but it fails every. single. time. and there's nothing I can find that will help me at least get my phone back working.
Any help? My carrier is T-Mobile
moneyhbags said:
I successfully had Cyanogenmod installed, but now when I turn my phone on it stays stuck at the loading screen and goes back and forth to the HTC start up (the screen before the Cyanogen loading screen). I tried reverting back to stock using the RUU but it fails every. single. time. and there's nothing I can find that will help me at least get my phone back working.
Any help? My carrier is T-Mobile
Click to expand...
Click to collapse
Sounds like possibly you need to flash the boot.img on it. I think , a senior member will correct me, but if your S-On and rooted, you should do that , S-Off don't require the boot.img.
leesumm said:
Sounds like possibly you need to flash the boot.img on it. I think , a senior member will correct me, but if your S-On and rooted, you should do that , S-Off don't require the boot.img.
Click to expand...
Click to collapse
I don't know what S-On or S-Off means, but it's been like 20 minutes and it's now stuck at the HTC quietly brilliant screen.
I did do a back-up before I rooted it. I tried re-installing Cyanogenmod but the installer says my phone is unrecognizable.
edit: still stuck at Cyanogen loading screen =(
moneyhbags said:
I don't know what S-On or S-Off means, but it's been like 20 minutes and it's now stuck at the HTC quietly brilliant screen.
I did do a back-up before I rooted it. I tried re-installing Cyanogenmod but the installer says my phone is unrecognizable.
edit: still stuck at Cyanogen loading screen =(
Click to expand...
Click to collapse
S-ON or off means security is on or off, If you haven't done the mod to S-Off , your still stock S-On. To see for sure though , in the bootloader mode at the top it will say Tampered first line , then the second should say something like M7 ??? PVT ship. S-On
What recovery are you using? CWM or TWRP . Do you know or use ADB?
I just reread your OP and you said you RUU'd. why? I think too with S-On you have to relock the bootloader to RUU then unlock after boot. You can use the same unlock.bin code that you used to unlock the first time if you still have it too . Best if you done the root and everything else , do some reading on S-Off procedure and do that .
leesumm said:
S-ON or off means security is on or off, If you haven't done the mod to S-Off , your still stock S-On. To see for sure though , in the bootloader mode at the top it will say Tampered first line , then the second should say something like M7 ??? PVT ship. S-On
What recovery are you using? CWM or TWRP . Do you know or use ADB?
Click to expand...
Click to collapse
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
moneyhbags said:
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
Click to expand...
Click to collapse
I have had better luck with TWRP the latest one which is I think 2.6.3.
leesumm said:
I have had better luck with TWRP the latest one which is I think 2.6.3.
Click to expand...
Click to collapse
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
moneyhbags said:
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
Click to expand...
Click to collapse
I had the same problem like you... I have installed first twrp 2.6.3.3 then root the VIPER ROM, so I finelly got into the phone... Then I have flashed again vith ARHD 41.0 ROM and my phone is working perfect But I had the same problem as you... this is becouse of the S-ON and you stuck in boot-loop
moneyhbags said:
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
Click to expand...
Click to collapse
IF you can get to recovery, do you have a backup that is working ? If not you may have to unzip the CM rom, look for the boot.img , put that into the adb folder then run adb with fastboot flash boot.img , then reboot and it should go. If you have a back up of the Cm rom you might be able to go to recovery and do a restore from the backup there. And another thing you might do. Not sure if it will mess it up but/ fastboot erase cache then boot
peca_slo said:
I had the same problem like you... I have installed first twrp 2.6.3.3 then root the VIPER ROM, so I finelly got into the phone... Then I have flashed again vith ARHD 41.0 ROM and my phone is working perfect But I had the same problem as you... this is becouse of the S-ON and you stuck in boot-loop
Click to expand...
Click to collapse
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
moneyhbags said:
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
Click to expand...
Click to collapse
Good glad to know it works again.. Now do some reading on S-Off sounds like you have some idea of ADB so it really isn't that hard and it will make flashing easier in the future. You might even consider a full GPE conversion. I did it and like the Kit Kat but running Elegancia and once in a while revert back to the GPE with Xposed and Gravity Box KK for a mod. Super good battery.
moneyhbags said:
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
Click to expand...
Click to collapse
boot to recovery
clear cache and delvik
reboot to bootloader
fastboot USB and type
fastboot erase cache
now see if your phone will bootup
If no, find a different rom to flash
and here is a recovery flashable version of TWRP, flash it the same you do a rom and reboot to recovery to see it
moneyhbags said:
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
Click to expand...
Click to collapse
whoops looks like i got here late ..

Can't return to stock ?

I tried to return to stock using mike1986 instructions. ie, download stock Rom and put on sd and download stock recovery for fastboot flash.
Problem was, when I tried to fastboot flash the recovery I got a message that "appeared" to be sayin the recovery was to big in size.
Does that make any sense to anyone, if so, can anyone suggest anything ?
Thanks
Edit, I'm s-on
Sent from my HTC One using XDA Free mobile app
10rdan said:
I tried to return to stock using mike1986 instructions. ie, download stock Rom and put on sd and download stock recovery for fastboot flash.
Problem was, when I tried to fastboot flash the recovery I
Does that make any sense to anyone, if so, can anyone suggest anything ?
Thanks
Edit, I'm s-on
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
I was having problems before had encrypted ruu instead of decrypted,not sure if that helps but fixed my problem to return to stock.make sure you have wright ruu for carrier
10rdan said:
I tried to return to stock using mike1986 instructions. ie, download stock Rom and put on sd and download stock recovery for fastboot flash.
Problem was, when I tried to fastboot flash the recovery I got a message that "appeared" to be sayin the recovery was to big in size.
Does that make any sense to anyone, if so, can anyone suggest anything ?
Thanks
Edit, I'm s-on
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
First off, Post a fastboot getvar all ( minus your imei no and serial no ).
Is your bootloader unlocked?
post links to recovery you were trying to flash and how you were trying to flash it?
bored_stupid said:
First off, Post a fastboot getvar all ( minus your imei no and serial no ).
Is your bootloader unlocked?
post links to recovery you were trying to flash and how you were trying to flash it?
Click to expand...
Click to collapse
Was trying to flash stock, 4.19.401.11, recovery via fastboot command after flashing stock Rom via twrp. Wouldn't flash, question is why ?
Handset is "found" with "adb device", just wouldn't flash recovery.
Sent from my HTC One using XDA Free mobile app
10rdan said:
Was trying to flash stock, 4.19.401.11, recovery via fastboot command after flashing stock Rom via twrp. Wouldn't flash, question is why ?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Without a fastboot getvar all and a screenshot of your bootloader, and how you tried to flash it, i cant say
bored_stupid said:
Without a fastboot getvar all and a screenshot of your bootloader, and how you tried to flash it, i cant say
Click to expand...
Click to collapse
I've gone back to, backed up, ARHD62 so can't give you what you're asking for. Thanks anyway.
Reason I wanted to go back to stock was to get latest firmware when it's released then re unlock bootloader etc and flash ARHD71. NOT s-off.
Sent from my HTC One using XDA Free mobile app
10rdan said:
I've gone back to, backed up, ARHD62 so can't give you what you're asking for. Thanks anyway.
Reason I wanted to go back to stock was to get latest firmware when it's released then re unlock bootloader etc and flash ARHD71. NOT s-off.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
BTW, a getvar can be gotten no matter what ROM you are on... it would help identify your device, and if you do want to stay S-On, perhaps find a signed firmware.zip for your phone.

Where did I go wrong?

Okay, so I have an HK m8 on sprint, FW 1.54.654.13.
I was originally on Viper 1.8.0, but wanted to upgrade to 2.0.0, so I went back to my stock backup, with the aforementioned software version.
After restoring that backup I realized I needed to also flash a stock recovery in order to take the OTA. So I flashed the 'Stock Recovery From 1.54.651.8 OTA' over adb from this thread: http://forum.xda-developers.com/showthread.php?t=2736048
So, since flashing that recovery my phone seems to not have a recovery anymore; infact, it constantly reboots after about 1 minute of being booted to system. When I boot into recovery, I get a symbol of a phone with an "!" in a triangle over it.
Where did I go wrong? What recovery should I be using? I can re-flash TWRP, but it seems I still get the bootloop, even though it does actually boot into system (which I've never seen happen from a bootloop). It's been like this for 12+ hours, and no amount of searching has helped me out thus far, so I'm hoping someone here could help me out a little.
xLoveHateLegend said:
Okay, so I have an HK m8 on sprint, FW 1.54.654.13.
I was originally on Viper 1.8.0, but wanted to upgrade to 2.0.0, so I went back to my stock backup, with the aforementioned software version.
After restoring that backup I realized I needed to also flash a stock recovery in order to take the OTA. So I flashed the 'Stock Recovery From 1.54.651.8 OTA' over adb from this thread: http://forum.xda-developers.com/showthread.php?t=2736048
So, since flashing that recovery my phone seems to not have a recovery anymore; infact, it constantly reboots after about 1 minute of being booted to system. When I boot into recovery, I get a symbol of a phone with an "!" in a triangle over it.
Where did I go wrong? What recovery should I be using? I can re-flash TWRP, but it seems I still get the bootloop, even though it does actually boot into system (which I've never seen happen from a bootloop). It's been like this for 12+ hours, and no amount of searching has helped me out thus far, so I'm hoping someone here could help me out a little.
Click to expand...
Click to collapse
When I boot into recovery, I get a symbol of a phone with an "!" in a triangle over it.
Click to expand...
Click to collapse
This is stock recovery
You could pull the stock recovery from the HK firmware...hopefully that will get you back to normal.
Worse comes to worse run the RUU.
I do not have the recovery.img in my backup. I'm also not S-off, so I think the only way I can upgrade my firmware is through OTA from what I understand, correct? If I could just flash the proper stock recovery I think I would be fine from there?
xLoveHateLegend said:
I do not have the recovery.img in my backup. I'm also not S-off, so I think the only way I can upgrade my firmware is through OTA from what I understand, correct? If I could just flash the proper stock recovery I think I would be fine from there?
Click to expand...
Click to collapse
You can flash the full firmware while being s-on.
Alright, thanks! Can I go ahead and RUU 2.22.401.4 directly, or should I just RUU to my current stock firmware and just OTA from there?
Sent from my 831C using XDA Free mobile app
xLoveHateLegend said:
Alright, thanks! Can I go ahead and RUU 2.22.401.4 directly, or should I just RUU to my current stock firmware and just OTA from there?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
2.22.401.4 is not for Sprint.
I would go with the current HK RUU and start fresh.
BD619 said:
2.22.401.4 is not for Sprint.
I would go with the current HK RUU and start fresh.
Click to expand...
Click to collapse
Damn. Alright, well from what I can see 2.16.654.4 is the latest for Sprint. After downloading O.M.J.'s RUU, would I be good to go straight to viper 2.0.0?
Sent from my 831C using XDA Free mobile app
xLoveHateLegend said:
Damn. Alright, well from what I can see 2.16.654.4 is the latest for Sprint. After downloading O.M.J.'s RUU, would I be good to go straight to viper 2.0.0?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
After you install TWRP recovery, yes.
For future reference Viper does OTA's which are not the same as Sprint OTA's...download the Viper OTA and flash in twrp.
Magnum_Enforcer said:
After you install TWRP recovery, yes.
Click to expand...
Click to collapse
Yes of course, thank you.
BD619 said:
For future reference Viper does OTA's which are not the same as Sprint OTA's...download the Viper OTA and flash in twrp.
Click to expand...
Click to collapse
Yes, I am aware. But on 1.8.0 I did not get an OTA. Maybe because I'll get it after I upgrade my FW. So after RUUing then reinstalling TWRP, if I restore my viper 1.8.0 backup, I can just OTA to 2.0.0?
xLoveHateLegend said:
Yes of course, thank you.
Yes, I am aware. But on 1.8.0 I did not get an OTA. Maybe because I'll get it after I upgrade my FW. So after RUUing then reinstalling TWRP, if I restore my viper 1.8.0 backup, I can just OTA to 2.0.0?
Click to expand...
Click to collapse
Should be able to...
But if you are going to RUU why not just download the full rom and clean flash.
BD619 said:
Should be able to...
But if you are going to RUU why not just download the full rom and clean flash.
Click to expand...
Click to collapse
I tried flashing the full Rom per your suggestion, but after flashing the 2.0.0 Rom, it's like my phone has no OS and can only boot to bootloader or recovery, not system at all.
I also tried extracting the latest hk ruu to the root of my external SD card and running it through bootloader to no avail.
I feel like I'm missing a vital part of information here. I've never really ruu'd before so I'm new to that but I'm pretty stumped on this whole thing.
xLoveHateLegend said:
I tried flashing the full Rom per your suggestion, but after flashing the 2.0.0 Rom, it's like my phone has no OS and can only boot to bootloader or recovery, not system at all.
I also tried extracting the latest hk ruu to the root of my external SD card and running it through bootloader to no avail.
I feel like I'm missing a vital part of information here. I've never really ruu'd before so I'm new to that but I'm pretty stumped on this whole thing.
Click to expand...
Click to collapse
get the drivers for your phone + adb, rename the firmware update to firmware.zip, put it in /sdk/platform-tools
put the phone in fastboot, make sure it says fastboot USB and type fastboot devices in terminal to confirm it's connected.
then type in terminal Fastboot oem rebootRUU (capitalization matters.)
your screen will go black with a greyish HTC logo, then type in fastboot flash zip firmware.zip
once it's done doing it's thing type fastboot reboot
this method is pretty much failproof
EDIT: also, if you're flashing ONLY the sprint 2.0.0 update, you'll have to be on capt's twrp 2.7.0.7, otherwise you'll have to flash the full rom, boot into it, reboot into 2.7.1.0, and dirty flash the sprint viper ROM. Hope that helps, cheers >;3
yorisou said:
get the drivers for your phone + adb, rename the firmware update to firmware.zip, put it in /sdk/platform-tools
put the phone in fastboot, make sure it says fastboot USB and type fastboot devices in terminal to confirm it's connected.
then type in terminal Fastboot oem rebootRUU (capitalization matters.)
your screen will go black with a greyish HTC logo, then type in fastboot flash zip firmware.zip
once it's done doing it's thing type fastboot reboot
this method is pretty much failproof
EDIT: also, if you're flashing ONLY the sprint 2.0.0 update, you'll have to be on capt's twrp 2.7.0.7, otherwise you'll have to flash the full rom, boot into it, reboot into 2.7.1.0, and dirty flash the sprint viper ROM. Hope that helps, cheers >;3
Click to expand...
Click to collapse
Thanks for the reply! From my understanding, you need to be S-Off for that method, which I am not.
The method I attempted to use is this one, from O.M.J's thread here http://forum.xda-developers.com/showthread.php?t=2729173
using 7zip, extract 0P6BIMG.zip to ext sd card
-boot into bootloader
-make sure*hboot*is highlighted, press power button
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
The problem is, it scans my external SD card just fine but never asks if I want to start the update, nor do I get the option to press volume up etc... I am on captains twrp 2.7.0.7, as I've seen many other users confirm success with this recovery.
Also, I don't see just an update, it seems the Sprint version of the Rom I downloaded is the full rom. I actually did get it to boot once and got this (see screenshot), but it was a dirty flash.
Sent from my 831C using XDA Free mobile app
xLoveHateLegend said:
Thanks for the reply! From my understanding, you need to be S-Off for that method, which I am not.
The method I attempted to use is this one, from O.M.J's thread here http://forum.xda-developers.com/showthread.php?t=2729173
using 7zip, extract 0P6BIMG.zip to ext sd card
-boot into bootloader
-make sure*hboot*is highlighted, press power button
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
The problem is, it scans my external SD card just fine but never asks if I want to start the update, nor do I get the option to press volume up etc... I am on captains twrp 2.7.0.7, as I've seen many other users confirm success with this recovery.
Also, I don't see just an update, it seems the Sprint version of the Rom I downloaded is the full rom. I actually did get it to boot once and got this (see screenshot), but it was a dirty flash.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Did you re-lock your bootloader?
xLoveHateLegend said:
Thanks for the reply! From my understanding, you need to be S-Off for that method, which I am not.
The method I attempted to use is this one, from O.M.J's thread here http://forum.xda-developers.com/showthread.php?t=2729173
using 7zip, extract 0P6BIMG.zip to ext sd card
-boot into bootloader
-make sure*hboot*is highlighted, press power button
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
The problem is, it scans my external SD card just fine but never asks if I want to start the update, nor do I get the option to press volume up etc... I am on captains twrp 2.7.0.7, as I've seen many other users confirm success with this recovery.
Also, I don't see just an update, it seems the Sprint version of the Rom I downloaded is the full rom. I actually did get it to boot once and got this (see screenshot), but it was a dirty flash.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
http://venomroms.com/htc-one-m8/
download the full one and the sprint one, flash the first, reboot all the way (doubt you have to finish the automatic setup) then reboot into recovery and dirty flash the sprint one without wiping anything. It'll connect to the CDMA network instead of the GSM one with no problems, you don't even need to be on 2.7.0.7
And if it isn't working in HBOOT just go into recovery and adb sideload it, you shouldn't need to be s-off to do that. Enter adb sideload and just type in a terminal adb sideload (filename)
EDIT: idk why but that picture made me lol irl, KEEP CALM AND KANG AWAY
Alright giving that a shot now, thanks
That message is hilarious to me now, but it wasn't at the time xD
Edit: is it safe to dirty flash the first one, coming from 1.8.0? Also no, I haven't relocked my boot loader.
xLoveHateLegend said:
Alright giving that a shot now, thanks
That message is hilarious to me now, but it wasn't at the time xD
Edit: is it safe to dirty flash the first one, coming from 1.8.0? Also no, I haven't relocked my boot loader.
Click to expand...
Click to collapse
RUU won't run unless you re-lock the bootloader since you are s-on
BD619 said:
RUU won't run unless you re-lock the bootloader since you are s-on
Click to expand...
Click to collapse
Ahhh, okay makes sense now. My m7 was s-off and that was the first and last time I ever did a RUU. If I re-lock the boot loader, do I have to go through htcdev again to unlock once more, or will having it locked again not effect root?
Sent from my 831C using XDA Free mobile app
xLoveHateLegend said:
Ahhh, okay makes sense now. My m7 was s-off and that was the first and last time I ever did a RUU. If I re-lock the boot loader, do I have to go through htcdev again to unlock once more, or will having it locked again not effect root?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
fastboot oem relock
should do it

Categories

Resources