Related
SOLVED - check post 35
..and I don't know how to solve it. So, I would really need and appreciate your help!
Device:
m7ul s-off, currently unlocked, running cm 10.1 nightly
The problem:
I experienced reboots and fc's on various aosp roms as pa, cm and pac. cm is running best so far, on pa i lost data connection from time to time.
I tryed everything. I flashed sense roms, I flashed stock, I did a nandroid restore of stock ruu, relocked my bootloader, flashed stock recovery and everything possible to fix my device.
If I was lucky, it booted, but it shut down after a few seconds and kept bootlooping.
I can't get it back to stock and that really worries me. I did everything as explained but nothing worked.
Now to what I did with my device:
unlocked, flashed cwm, perm root
flashed cm, but coming from the nexus4 i was looking forward for pa rom
flashed a pa dev build, which was made for m7tmo. this might be the point where my troubles started. build was a bit buggy so
flashed trickdroid 6.0.0, flashed some tweaks and had major issues as no status bar and frequent reboots
went back to cm and from then on I just flashed pa or cm roms (gave pac a try but had even more issues)
everything else is already explained (the problem).
If there is any further information I have to provide you, just tell me. I don't really know much about logcat, but I could upload a log if that would help. All I see is hundreds of errors with QC-DS-LIB, LocSvc, kickstart and others..
I spent days on trying to fix my phone. I'm also afraid of bricking it with all the **** I try... Maybe someone here can help me find a solution. Please
Do you have the appropriate radio for your ROM?
http://forum.xda-developers.com/showthread.php?t=2245615
That might be the root of all evil...
I did flash 1.29.401.12 WWE OTA - 4A.14.3250.13_10.33.1150.01L while running the stable pa rom. currently I'm on 4A.13.3221.27_10.31.1131.05L (I guess stock?)
edit: it's from RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
I am not sure but all the stuff you did it is likely that something got messed up.
Which recovery do you use? Please flash that again with
fastboot erase cache
fastboot flash recovery recovery.img (*recovery.img = the exact name of the recovery as it is in your platform-tools folder) followed by
fastboot erase cache
Use only the USB cable that came with the One, and don't use a USB 3.0 under Windows 8. Maybe try a different computer as well.
Flash a Sense ROM that is close to stock, and a matching radio based.
Before flashing a ROM.zip, wipe cache/factory reset and dalvik cache within the recovery first.
Hope you get it all sorted
hardstuffmuc said:
I am not sure but all the stuff you did it is likely that something got messed up.
Which recovery do you use? Please flash that again with
fastboot erase cache
fastboot flash recovery recovery.img (*recovery.img = the exact name of the recovery as it is in your platform-tools folder) followed by
fastboot erase cache
Use only the USB cable that came with the One, and don't use a USB 3.0 under Windows 8. Maybe try a different computer as well.
Flash a Sense ROM that is close to stock, and a matching radio based.
Before flashing a ROM.zip, wipe cache/factory reset and dalvik cache within the recovery first.
Hope you get it all sorted
Click to expand...
Click to collapse
Did exactly what you said, phone got stuck on boot (with beatsaudio) for over 10 mins (this actually happened every time i tried flashing arhd). rebooted, was able to do a first setup after 3 mins. downloaded catlog, havent had the errors mentioned above so far. running smooth for now. will post again if some crazy **** happens.
Thanks!
And again, after installing some apps I got reboots. The only difference to aosp is, that I have to do a reboot by holding the home button, hence this rom gets stuck on the bootlogo. The aosp roms rebootet after 15 secs.
Sent from my HTC One using xda app-developers app
George_Mn said:
And again, after installing some apps I got reboots. The only difference to aosp is, that I have to do a reboot by holding the home button, hence this rom gets stuck on the bootlogo. The aosp roms rebootet after 15 secs.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Download the RUU for your device. boot to fastboot and relock bootloader, then install ruu.exe from PC. That will fix you up. Nandroid restore of stock ruu is different. The ruu will replace all partitions.. U have something wrong somewhere that roms dont touch i bet. The ruu should do it. If s-off and supercid you dont even need your exact ruu. Any ruu will do.
nugzo said:
Download the RUU for your device. boot to fastboot and relock bootloader, then install ruu.exe from PC. That will fix you up. Nandroid restore of stock ruu is different. The ruu will replace all partitions.. U have something wrong somewhere that roms dont touch i bet. The ruu should do it. If s-off and supercid you dont even need your exact ruu. Any ruu will do.
Click to expand...
Click to collapse
I have actually tried that. I also think it does not depend on the rom I use. Since I can't remember wether I relocked my bootloader before trying the ruu.exe I will try again.
I was also thinking about flashing boot.img but i'm afraid of bricking.
Sent from my HTC One using xda app-developers app
George_Mn said:
I have actually tried that. I also think it does not depend on the rom I use. Since I can't remember wether I relocked my bootloader before trying the ruu.exe I will try again.
I was also thinking about flashing boot.img but i'm afraid of bricking.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Just do the ruu again, it should fix you up. Boot.img is no big deal, it gets flashed with all roms. If ruu doesnt work please let us know if it successfully installed or not. If it will be like first time you powered it on (minus the s-off, that will stay) if it installed correctly. It will install correct radio and boot.img.
Have you changed your MID? i think you should just installl the latest ruu for your CID and MID.
Also have you installed different hboot? like the modded one or the eng hboot? If so have you flashed the original back? The RUU will install the correct hboot.
Sorry top say but If completed ruu doesnt fix it, its broke. Nothing software can do.
nugzo said:
Just do the ruu again, it should fix you up. Boot.img is no big deal, it gets flashed with all roms. If ruu doesnt work please let us know if it successfully installed or not. If it will be like first time you powered it on (minus the s-off, that will stay) if it installed correctly. It will install correct radio and boot.img.
Have you changed your MID? i think you should just installl the latest ruu for your CID and MID.
Also have you installed different hboot? like the modded one or the eng hboot? If so have you flashed the original back? The RUU will install the correct hboot.
Sorry top say but If completed ruu doesnt fix it, its broke. Nothing software can do.
Click to expand...
Click to collapse
No I haven't, getvar says my cid is 102 and my mid pn0710000
I think I have installed different hboot but as you said ruu will revert...
guess thats the right one?: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
I could also try: RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13. 3227.06_10.27.1127.01_release_308001_signed_2_4.ex e
edit: omg just checked md5sum of the ruu I used earlier... there should be a tool automatically checking every md5sum. no wonder it bootlooped..
Stuck on bootscreen after installing the ruu.exe
no fastboot usb, no custom recovery
what can i do now?
George_Mn said:
Stuck on bootscreen after installing the ruu.exe
no fastboot usb, no custom recovery
what can i do now?
Click to expand...
Click to collapse
Still stuck? What happened, did pc say it finished successfully ? Takes a few minutes after ruu. Which ruu did u use?
nugzo said:
Still stuck? What happened, did pc say it finished successfully ? Takes a few minutes after ruu. Which ruu did u use?
Click to expand...
Click to collapse
I used RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
pc said it finished successfully
turned it off to not kill the battery
waited for over 10 minutes.
currently talking to htc support usa since the german support is asleep..
i can access the bootloader, thats all
George_Mn said:
I used RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
pc said it finished successfully
turned it off to not kill the battery
waited for over 10 minutes.
currently talking to htc support usa since the german support is asleep..
i can access the bootloader, thats all
Click to expand...
Click to collapse
If you wish you can unlock again, install custom recovery and then side load a rom. I'm afraid HTC will just have you try the ruu again. Or tell you it's broke.
How long did the ruu install take? Did it restart phone a few times? If it was me, I'd unlock again and install a custom rom. If that doesn't work I don't know what else to try..tried everything. Most likely Something wrong with the hardware
nugzo said:
If you wish you can unlock again, install custom recovery and then side load a rom.
Click to expand...
Click to collapse
I don't think so, my pc does not recognize my phone because usb debugging is not enabled.. any solution?
in stock recovery it says MounT SDCARD failed, so I will try fixing that by performing a few factory resets lol
George_Mn said:
I don't think so, my pc does not recognize my phone because usb debugging is not enabled.. any solution?
in stock recovery it says MounT SDCARD failed, so I will try fixing that by performing a few factory resets lol
Click to expand...
Click to collapse
When in fastboot it doesn't matter if debugging is enabled. It must say fastboot USB . If not select fastboot and press power
What hboot do you have now? Since you r s off I don't know if boot loader needs to be unlocked. If you can get to fastboot and be seen by pc,download twrp recovery and put it in your adb folder. Then "fastboot flash recovery filename.img" then u can side load.
nugzo said:
When in fastboot it doesn't matter if debugging is enabled. It must say fastboot USB . If not select fastboot and press power
What hboot do you have now? Since you r s off I don't know if boot loader needs to be unlocked. If you can get to fastboot and be seen by pc,download twrp recovery and put it in your adb folder. Then "fastboot flash recovery filename.img" then u can side load.
Click to expand...
Click to collapse
omg i'm such a stupid person... I was checking my usb ports and unplugged the cable, plugged it to my phone and yeah guess what there was no FASTBOOT USB there was just FASTBOOT ...
Okay so I can still get a rom on it that's really good news. But, there is still the other problem..
George_Mn said:
omg i'm such a stupid person... I was checking my usb ports and unplugged the cable, plugged it to my phone and yeah guess what there was no FASTBOOT USB there was just FASTBOOT ...
Okay so I can still get a rom on it that's really good news. But, there is still the other problem..
Click to expand...
Click to collapse
What's the other problem? I can help
George_Mn said:
omg i'm such a stupid person... I was checking my usb ports and unplugged the cable, plugged it to my phone and yeah guess what there was no FASTBOOT USB there was just FASTBOOT ...
Okay so I can still get a rom on it that's really good news. But, there is still the other problem..
Click to expand...
Click to collapse
What's the other prob.. We're knocking them out.. Hang in there
---------- Post added at 08:02 PM ---------- Previous post was at 07:51 PM ----------
MacHackz said:
What's the other problem? I can help
Click to expand...
Click to collapse
Mac does he have to unlock boot loader if he's s off? To flash recovery?
MacHackz said:
What's the other problem? I can help
Click to expand...
Click to collapse
Well I've been through this (ruu>stuck on boot>unlock>flash cwm>sideload rom) twice.
The problems are still reboots from time to time and app shut downs or fcs. It happens with every rom i tryed. on sense roms its stuck on bootscreen until i reboot with power button, on aosp it just reboots within 15 secs
I'll have to admit, I did the ruu on win8 with usb 3.0
When does it reboot? Sometimes upon installing apps, accessing play store, on landscape mode, on unlocking sim. Much to often to just live with it..
just sideloaded cm10.1, it's alive..
Hi there
I justed Unlocked my one and installed clockwork recovery.
I installed Revolution HD Google (no sense) rom.
But now my phone keeps rebooting, sometimes i see the screen where i need to enter my pincode or select language. But then its shuts down and powers up again.
I tried reinstalling it, wiping everything.
I got my phone on the charger too.. but tried it without charging it too
Does someone know a solution?
Thank you in advance!
Same
Bentaar said:
Hi there
I justed Unlocked my one and installed clockwork recovery.
I installed Revolution HD Google (no sense) rom.
But now my phone keeps rebooting, sometimes i see the screen where i need to enter my pincode or select language. But then its shuts down and powers up again.
I tried reinstalling it, wiping everything.
I got my phone on the charger too.. but tried it without charging it too
Does someone know a solution?
Thank you in advance!
Click to expand...
Click to collapse
Hello,
I have the same problem. Just did it now. I tried 3 times to reinstall it but I have the same problem every time. I would also be very thankful if somebody would be able to help.
I wanted to try to install a different ROM, but I've got no idea how to access the SD card to save different zip
Thank you
looks like same issue as my thread: http://forum.xda-developers.com/showthread.php?t=2549259
Bentaar said:
Hi there
I justed Unlocked my one and installed clockwork recovery.
I installed Revolution HD Google (no sense) rom.
But now my phone keeps rebooting, sometimes i see the screen where i need to enter my pincode or select language. But then its shuts down and powers up again.
I tried reinstalling it, wiping everything.
I got my phone on the charger too.. but tried it without charging it too
Does someone know a solution?
Thank you in advance!
Click to expand...
Click to collapse
are u guys s-on, by any chance? you know u have to be s-off for 4.4.
koolhoffi said:
Hello,
I have the same problem. Just did it now. I tried 3 times to reinstall it but I have the same problem every time. I would also be very thankful if somebody would be able to help.
I wanted to try to install a different ROM, but I've got no idea how to access the SD card to save different zip
Thank you
Click to expand...
Click to collapse
adb push, or adb sideload, or OTG.
nkk71 said:
are u guys s-on, by any chance? you know u have to be s-off for 4.4.
adb push, or adb sideload, or OTG.
Click to expand...
Click to collapse
Im on S-On. Did not know that. Should have read further....
Is there any chance to access the SD so that I can install a different ROM?
EDIT: I understand that these "adb push, or adb sideload, or OTG." are possibilities to access SD card?
nkk71 said:
are u guys s-on, by any chance? you know u have to be s-off for 4.4.
Click to expand...
Click to collapse
Indeed forgot to do S-off
Any possibility to do it through Fastboot?
Cause i cant get in the rom.
Bentaar said:
Indeed forgot to do S-off
Any possibility to do it through Fastboot?
Cause i cant get in the rom.
Click to expand...
Click to collapse
s-off using fastboot -> not as far as i know; reflash a compatible rom for rumrunner or revone (depending on your firmware), and get s-of.
nkk71 said:
s-off using fastboot -> not as far as i know; reflash a compatible rom for rumrunner or revone (depending on your firmware), and get s-of.
Click to expand...
Click to collapse
USB Debugging is off, How can i enter the phone storage without entering the rom?
So how to reflash? or how to push a rom towards the phone through fastboot? Sorry if i ask a lot, but I cant figure it out.
Bentaar said:
USB Debugging is off, How can i enter the phone storage without entering the rom?
So how to reflash? or how to push a rom towards the phone through fastboot? Sorry if i ask a lot, but I cant figure it out.
Click to expand...
Click to collapse
go to bootloader, select fastboot then
./fastboot flash recovery recovery.img //recovery.img is the custom recovery file you downloaded, either CWM TWRP.
./flash erase cache
reboot to recovery then you can do
adb push
b3rx said:
go to bootloader, select fastboot then
./fastboot flash recovery recovery.img //recovery.img is the custom recovery file you downloaded, either CWM TWRP.
./flash erase cache
reboot to recovery then you can do
adb push
Click to expand...
Click to collapse
I got CWM on it, so now im looking for a rom who doesnt need S-OFF
http://forum.xda-developers.com/showthread.php?t=2382691
This one doesnt need S-off right?
It says:
Error: device not found
if i try to push the rom, I dont have a connection with my pc. It says: FASTBOOT USB on my phone,
But if i send out: ADB Devices it comes out clear.
Bentaar said:
I got CWM on it, so now im looking for a rom who doesnt need S-OFF
http://forum.xda-developers.com/showthread.php?t=2382691
This one doesnt need S-off right?
It says:
Error: device not found
if i try to push the rom
Click to expand...
Click to collapse
go to install zip -> sideload
then do a ./adb sideload rom.zip
and yes that rom doesnt need s-off.
nkk71 said:
are u guys s-on, by any chance? you know u have to be s-off for 4.4.
adb push, or adb sideload, or OTG.
Click to expand...
Click to collapse
Hey, Just wanted to say thank you I was able to put a different Rom onto my phone and installed it successfully
b3rx said:
go to install zip -> sideload
then do a ./adb sideload rom.zip
and yes that rom doesnt need s-off.
Click to expand...
Click to collapse
I get the error: Device not found.
Reinstalled HTC Sync too. Same problem
Adb devices comes out empty
--
Tried it on another pc too now, same problem.
He doesnt see my device.
Fixed
I fixed it by mounting an usb stick with a rom to it and installing it through Recovery!
Thanks you all !!
I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab. Then when he tried to flash Cyanogenmod 10.2 it keeps failing. I asked him why he did this and he said his friend told him how cool Cyanogenmod is so naturally he want it to! (By the way my son is 13).
I know very little about this phone but I would like to get the phone back to the way it was before he messed with it as it cost me $650 to buy it. I started reading about RUU files but from what I can tell the RUU will not work with S-ON. And I can't seem to flash any ROM as it keeps failing. Any suggestions would be a big help!
Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck
Then make him use a flip phone for a week as punishment lol
I had the same. In my case I started ruu for another version (international), of course ruu failed to install but it did fix partitions, after that I was able to sideload rom. I will try to find my topic and provide You with my solution.
This is my BLS/ALS with HTC One, patient is alive and well now, only camera has pink tint...
http://forum.xda-developers.com/showthread.php?t=2322851
Try with CWM instead of TWRP... and finally pass some information about progress.
Thealshear said:
Don't worry this is fixable
First relock your bootloader
Then download a RUU.zip for GPe
boot into fastboot
and type this command (in your pc of course with adb) fastboot oem rebootRUU
A silver htc logo should show
copy the RUU you downloaded to your adb folder and rename to ruu.zip
and type this command fastboot flash zip ruu.zip
this command should be typed twice (ignore the error that shows up)
after the second time it's done
type fastboot reboot
should turn right up
Good luck
Click to expand...
Click to collapse
Will the ruu method work if the phone is S-ON? All of the XDA posts I read state that you need to be S-OFF?
Give it a shot the phone is already bricked what you got to lose
crixley said:
Then make him use a flip phone for a week as punishment lol
Click to expand...
Click to collapse
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk
woody970 said:
For now until I can fix the phone he is back to two cans and string!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You can run an ruu but it has to be newer..
See here:
http://forum.gsmhosting.com/vbb/f485/understanding-s-off-super-cid-s-read-b4-u-run-ruu-1505916/
crixley said:
You can run an ruu but it has to be newer..
Any idea where to download the RUU? The build number that was on the phone before all this started was KRT16S.H5 release-keys
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
woody970 said:
I am hoping someone can help with this, my son completely wiped his Google Edition HTC One. When I asked him what he did he stated that he flashed TWRP and did a full wipe checking all of the boxes under the advanced tab.
Click to expand...
Click to collapse
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk
Delgra said:
The good news are that the phone isn't bricked, imho. The bad ones are that you will have to play with ROMs recoveries and RUU's a bit in order to have a working phone back. First of all I would focus to succeed in flashing a ROM in order to boot your phone. Googling I found a user with your same error showed in the pic that solved the issue "checking the signature box then flash a ROM where he got the error then unchecked the same signature box and reflash with success". If this process doesn't work for you, I suggest to flash a different recovery such as CWM and try to flash the ROM through it. Anyway you'll need an unlocked bootloader for the entire process. Let me know if you succeed.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
when your son was flashing CM mod was he using the correct version? I don't recall but I tried flashing my ATT HTC one but I am running a WWE firmware so that made me have to flash the GSM version of CM mod. http://www.cmxlog.com/11/m7ul/ Try downloading the latest zip file there and than try mounting to his phone with the USB mount or if you have a USB OTG you can install it from a USB. It shouldn't matter if your S-ON or S-OFF for installing some roms it just helps you avoid taking extra steps to get the ROM to install.
When your flashing with TWRP make sure to do a advanced wipe and check everything that is on there. After you do a advanced wipe do a regular factory reset. I'm hoping that the new CM11 rom will flash for his phone. You can also use ADB sideload to send the zip files over to your phone if you cannot mount the phone. What ADB sideload does is open up a connection from your phones USB and lets you transfer zips over onto the internal SD card basically in DOS command.
I want to thank everyone for there guidance in this. After googling for a couple of days and a few failed attempts with the RUU command I was finally able to restore the phone. I was able to flash a nandroid backup using TWRp from another google edition HTC which brought the phone back to life. Then I flashed a stock recovery and OTA's became available to the phone. The once dead HTC is now back up and running stock 4.4 android. The only issue I with the phone now is that there is a popping sound after a notification comes in that I can't get rid of... Anyone have any ideas?
Sent from my Nexus 5 using Tapatalk
The popping noises seem to come after I updated to kit Kat I don't know but a lot of people might have that issue too.
Sent from my HTC One using Tapatalk
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
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
its the peanut said:
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
Also make sure you downloaded the rom made for your phone model!
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Can you please post the output of
Code:
fastboot getvar all
please remove your imei and serial number.
Depending on which variant of the M7 you have you probably just need a different version of recovery to install a CM rom. I think they prefer TWRP 2.7.x.x. Post the getvar and we can see what you have. then I can give you a better informed instruction. :good:
P.s also check the md5 of the rom zip you downloaded. Use this tool www.winmd5.com the correct md5 should be listed with the link you downloaded the rom from
failed to mount /dev/block/blah blah blah = needs "block:by-name" support which twrp 2.6.3.3 doesn't have
everything explained here
So update your recovery
and do what danny said above so he can confirm you have the right rom/recovery for your device.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Your getvar looks fine this rom should work fine with your device. Download this version of TWRP https://www.androidfilehost.com/?fid=23501681358561860 (2.7.1.2). dropthe file in your fastboot folder and flash it with fastboot.
Code:
fastboot flash recovery "name-of-recovery".img
fastboot erase cache
fastboot reboot-bootloader
Once thats done reflash the rom with the new version of TWRP. It should flash just fine :good:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Burky1996 said:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Click to expand...
Click to collapse
There are a number of ways to return to stock software. You can simply flash a stock rom through twrp or use a stock nandroid. look for rom that match your version main. 7.19.401.22
I think there is even an lollipop 7.19.401.22 RUU for your device but I'm not sure if it will work with s-on though because it's a zip but it certainly wouldnt hurt to try it though. You will need to relock your bootloader and flash it with fastboot.
I'll edit this post with links when I find them unless some one beats me to it
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Burky1996 said:
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Click to expand...
Click to collapse
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Burky1996 said:
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Click to expand...
Click to collapse
Okay try this. Download the OTA but select the option "Install Later" connect your m7 to your pc and browse your storage. In the download folder on your phone you should find the OTA in zip format. Copy it to your pc.
Now open the OTA zip on your pc. Inside you'll find another zip called "firmware.zip" extract it then open it. Inside you'll find a recovery.img. extract the recovery file and flash it with fastboot. Now reboot to android and continue to install the OTA. :fingers-crossed:
Sent from my SM-T230 using Tapatalk
im going to have to unlock the boot loader again and then do it
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
its still not working so i mite just install twrp and restore to cm12.1
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
could it be not working coz my hboot has changed to 1.51.
Burky1996 said:
could it be not working coz my hboot has changed to 1.51.
Click to expand...
Click to collapse
Your still stuck with this? Try starting the process over, but do not relock your bootloader at any point.
Wipe system data and cache partitions with TWRP Advanced wipe
Flash the Rom with twrp as a clean install.
Reboot and download the OTA. Choose install later, then copy the OTA to your pc. Extract the Stock Recovery and flash it with fastboot. Reboot and install the OTA.
But do not relock your boot loader. Because when you unlock the bootloader, it wipes the device including the data/preload folder. If the preload folder is not intact the OTA will fail
Sent from my M7 Running ARHD 92.x