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..
I am a newbie trying to root htc one(att) , after I installed the 4.2.2 it began to keep restarting,I tought it was because I didn't wipe my data before I flash a new ROM, so i enter the TWRP and wanna wipe data and try again.
But I selected all the options and wiped everything on the cellphone including the OS, so now I can enter the bootloader, and I can enter the recovery, but I can't find the "USB storage" in the computer , so how can I transfer the rom to the storage and flash again?
Thank you very much
Search on how to use sideload command
Sent from my HTC One using xda app-developers app
You know what ADB and Fastboot are I assume? if not, I'll explain more.
But you have to do the following:
- download a rom of your choice on your pc (or use one you already have on there)
- put it in your ADB folder (for example for me C:\Users\Thom\Downloads\One\adt-bundle-windows-x86_64-20130219\sdk\platform-tools)
- then open a command window in that folder (shift+right click on the folder, or in a cmd window use the cd command)
- use the command "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly.
Hi, thank you for the help. I followed your guide and successfully transfer the zip into the phone. But when I enter the recovery and try to install, it failed and says:
E: unable to mount /cache
E: unable to mount /data
E: unable to mount /system
E: unable to mount internal storage
I click the mount option in the recovery , there are 4 box (cache, data,system,USB-OTG), but I can't choose any of them.
Also at the bottom of the box it says that"Storage: Internal Storage (0MB)"
T_T
thom109 said:
You know what ADB and Fastboot are I assume? if not, I'll explain more.
But you have to do the following:
- download a rom of your choice on your pc (or use one you already have on there)
- put it in your ADB folder (for example for me C:\Users\Thom\Downloads\One\adt-bundle-windows-x86_64-20130219\sdk\platform-tools)
- then open a command window in that folder (shift+right click on the folder, or in a cmd window use the cd command)
- use the command "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly.
Click to expand...
Click to collapse
Hi, thank you for the help.
I'm trying to search more threads about the sideload and learn it.
But since I cant mount anything, I cant do sideload, trying to fix it :silly:
zeekabal said:
Search on how to use sideload command
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
JohnnyXCG said:
Hi, thank you for the help.
I'm trying to search more threads about the sideload and learn it.
But since I cant mount anything, I cant do sideload, trying to fix it :silly:
Click to expand...
Click to collapse
the other, and right now I think only, option is to flash a RUU.
Which One do you have? Europe, Asia, AT&T, Developer, etc? Once I now that I can point you in the right direction
thom109 said:
the other, and right now I think only, option is to flash a RUU.
Which One do you have? Europe, Asia, AT&T, Developer, etc? Once I now that I can point you in the right direction
Click to expand...
Click to collapse
My one is AT&T
Thank you
JohnnyXCG said:
My one is AT&T
Thank you
Click to expand...
Click to collapse
ok, I'll try to help.
I had the exact same problem yesterday (I was being a bit dumb and accidently pressed the wrong button ) and I managed to solve it.
Okay, here is the RUU. Download it, it may take a while.
http://bugsylawson.com/files/file/1847-ruu-m7-ul-jb-50-cingular-12650212exe/
So while it's downloading, start with preparing.
First of all, did you flash the new firmware already? If so, go back to the old one. I'm not sure if the AT&T has same firmware as the international, if it does I can give you a link because I still have it on my pc.
You can flash it with "fastboot oem rebootRUU" (case sensitive!)
then when you see a htc logo on your phone "fastboot flash zip firmware.zip" (replace firmware with actual file name)
THEN FLASH IT AGAIN, OTHERWISE IT WON'T WORK AND YOU'LL BE BRICKED
then if it says succesful, use "fastboot reboot". Then go back into bootloader.
then, flash stock recovery (http://forum.xda-developers.com/showthread.php?t=2158763)
after that, relock your device (command is "fastboot oem relock")
so after the RUU finished downloading, try to run it.
Any problems, I'll keep an eye on this thread
Thank you . I am now at the htc grey logo status.
Since I dont know what firmware is I am afraid to take the next step.
Whats the firmware you've talked about? Is it OS? like 4.2.2 OS zip file?
thom109 said:
ok, I'll try to help.
I had the exact same problem yesterday (I was being a bit dumb and accidently pressed the wrong button ) and I managed to solve it.
Okay, here is the RUU. Download it, it may take a while.
http://bugsylawson.com/files/file/1847-ruu-m7-ul-jb-50-cingular-12650212exe/
So while it's downloading, start with preparing.
First of all, did you flash the new firmware already? If so, go back to the old one. I'm not sure if the AT&T has same firmware as the international, if it does I can give you a link because I still have it on my pc.
You can flash it with "fastboot oem rebootRUU" (case sensitive!)
then when you see a htc logo on your phone "fastboot flash zip firmware.zip" (replace firmware with actual file name)
THEN FLASH IT AGAIN, OTHERWISE IT WON'T WORK AND YOU'LL BE BRICKED
then if it says succesful, use "fastboot reboot". Then go back into bootloader.
then, flash stock recovery (http://forum.xda-developers.com/showthread.php?t=2158763)
after that, relock your device (command is "fastboot oem relock")
so after the RUU finished downloading, try to run it.
Any problems, I'll keep an eye on this thread
Click to expand...
Click to collapse
JohnnyXCG said:
Thank you . I am now at the htc grey logo status.
Since I dont know what firmware is I am afraid to take the next step.
Whats the firmware you've talked about? Is it OS? like 4.2.2 OS zip file?
Click to expand...
Click to collapse
No, the firmware package for the HBoot, Radio, etc.
I assume you didn't flash it when going to 4.2.2?
Or did you take the official 4.2.2 update before?
No, I didn't flah firmware when going to 4.2.2.
When my phone is good, all I did is I just copied the 4.2.2 to the phone and install in the recovery status.
Then the 4.2.2 keeps restarting and then I deleted everything on the phone .
thom109 said:
No, the firmware package for the HBoot, Radio, etc.
I assume you didn't flash it when going to 4.2.2?
Or did you take the official 4.2.2 update before?
Click to expand...
Click to collapse
JohnnyXCG said:
No, I didn't flah firmware when going to 4.2.2.
When my phone is good, all I did is I just copied the 4.2.2 to the phone and install in the recovery status.
Then the 4.2.2 keeps restarting and then I deleted everything on the phone .
Click to expand...
Click to collapse
Okay, you still have 4.1.2 firmware then. In that case you can just reboot already and skip the first step
Thanks.
The second step, flash stock recovery, I downloaded the file and in the recovery folder there are many .imgs
Which one is the one I need?
and how do I do it? just shift+right click to cmd and fastboot flash recovery name.img?
thom109 said:
Okay, you still have 4.1.2 firmware then. In that case you can just reboot already and skip the first step
Click to expand...
Click to collapse
JohnnyXCG said:
Thanks.
The second step, flash stock recovery, I downloaded the file and in the recovery folder there are many .imgs
Which one is the one I need?
and how do I do it? just shift+right click to cmd and fastboot flash recovery name.img?
Click to expand...
Click to collapse
yep, that's exactly how. Gimme a sec, I'll download it too to see which one you need
http://forum.xda-developers.com/showthread.php?t=2362818
Sent from my HTC One using xda app-developers app
okay, I have been browsing a while, but I unfortunately have no idea which one you could use.
HOWEVER,
I did see someone say you don't need stock recovery. So, try to just relock it and then flash the RUU.
You can always unlock it again if it doesn't work, so there isn't much of a risk
---------- Post added at 09:53 PM ---------- Previous post was at 09:49 PM ----------
zeekabal said:
http://forum.xda-developers.com/showthread.php?t=2362818
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
the problem here isn't the firmware he flashed the 4.2.2 rom, which uses the storage a bit different.
The problem he has is caused by the fact he didn't clear SD directly after flashing (needed if you jump from custom rom 4.1.2 to 4.2.2)
it could have been easy, but he can't boot into his rom, everything is gone. If he could boot it would be waaaaaaay easier, would only require a few ADB commands
OK, now I run the RUU, the phone is in the grey htc status,.It says gonna take 10 mins, hope it will be fine :victory:
thom109 said:
okay, I have been browsing a while, but I unfortunately have no idea which one you could use.
HOWEVER,
I did see someone say you don't need stock recovery. So, try to just relock it and then flash the RUU.
You can always unlock it again if it doesn't work, so there isn't much of a risk
Click to expand...
Click to collapse
JohnnyXCG said:
OK, now I run the RUU, the phone is in the grey htc status,.It says gonna take 10 mins, hope it will be fine :victory:
Click to expand...
Click to collapse
okay, if your phone gets a green bar with silver htc logo, you're good and I'm very happy for you
Yeah, it finished and my phone is back to life...
Now I'll try to install 4.2.2 agian.
Thanks for spending so much time on me thom109, you're truly a great person !!
God bless you !:good::good::good::good::good::good::good::good::good::good::good::victory::victory::laugh::laugh:
thom109 said:
okay, if your phone gets a green bar with silver htc logo, you're good and I'm very happy for you
Click to expand...
Click to collapse
JohnnyXCG said:
Yeah, it finished and my phone is back to life...
Now I'll try to install 4.2.2 agian.
Thanks for spending so much time on me thom109, you're truly a great person !!
God bless you !:good::good::good::good::good::good::good::good::good::good::good::victory::victory::laugh::laugh:
Click to expand...
Click to collapse
no problem mate
good you're back.
before you flash 4.2.2, take the official OTA
or if you don't have it yet, first flash the 4.2.2 firmware (can be found in the ARHD thread) and then after the rom is done installing, wipe the sd card
Have fun with your One
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
TaintedCross said:
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
Click to expand...
Click to collapse
Get s-off and restore any RUU.. After restore, better get s-off before you update, you won't be able to get it after the update.
Sent from my iPod touch using Tapatalk
TaintedCross said:
I have an HTC One by T-Mobile, Our update was released Monday. I tried to update but when it rebooted it went to install and failed to install, I looked up some information that say usually the cause of the failed install for software system updates is because of an unlocked bootloader and custom recovery. So I've tried to restore to factory OEM settings but every time it fails to up restore to the factory update as well. I'm at a loss here and no Idea what to do. I can flash any custom roms I want and those seem to work and flash just fine but If I try anything else like reverting to OEM stock it doesn't work. Anyone have any Ideas?
Before anyone asks, I've tried doing a RRU restore from desktop and .Zip on my phone and neither work. Both fail.
Click to expand...
Click to collapse
you need to flash the stock recovery and lock your bootloader to be able to do the update.
[email protected] said:
you need to flash the stock recovery and lock your bootloader to be able to do the update.
Click to expand...
Click to collapse
I'm pretty sure you don't need to relock the bootloader for OTAs, you do however need 100% stock ROM and (a very close) stock recovery for that ROM.
nkk71 said:
I'm pretty sure you don't need to relock the bootloader for OTAs, you do however need 100% stock ROM and (a very close) stock recovery for that ROM.
Click to expand...
Click to collapse
i stand corrected.
a stock recovery will do
[email protected] said:
i stand corrected.
a stock recovery will do
Click to expand...
Click to collapse
Only for OTAs, to run a full RUU exe, I do think the bootloader has to be locked/relocked
nkk71 said:
Only for OTAs, to run a full RUU exe, I do think the bootloader has to be locked/relocked
Click to expand...
Click to collapse
Not going to matter anyway, I accidently wiped my whole OS. I've tried using adb Sideload but it wont detect my device.
TaintedCross said:
Not going to matter anyway, I accidently wiped my whole OS. I've tried using adb Sideload but it wont detect my device.
Click to expand...
Click to collapse
Restart your computer, also update to latest HTC drivers and adb sdk.
Alternate method, use an OTG cable with a USB stick with a ROM.ZIP on it, and mount "external sdcard" (or whatever it's called) in custom recovery.
nkk71 said:
Restart your computer, also update to latest HTC drivers and adb sdk.
Alternate method, use an OTG cable with a USB stick with a ROM.ZIP on it, and mount "external sdcard" (or whatever it's called) in custom recovery.
Click to expand...
Click to collapse
I have restarted like 20 times, still doesn't detect it. And I don't have an OTG cable
TaintedCross said:
I have restarted like 20 times, still doesn't detect it. And I don't have an OTG cable
Click to expand...
Click to collapse
Does fastboot work?
Sent from my HTC One using Tapatalk
nkk71 said:
Does fastboot work?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I can boot into fastboot on my phone but I've no idea what to do from there.
Edit: HELLS YEAH! I got it! lol had to relock bootloader using fastboot and then go back into fastboot on my phone and run the RUU.exe and it worked this time! SOOO freaking stoked and happy! I've been up for 7 hours straight trying to fix this!
Nice. Please update the thread and put SOLVED
Sent from my HTC One using xda app-developers app
Ok, I know I'm going to catch all kinds of hell probably for posting this. But, I'm stuck. This is the first question I have asked on this forum, and have literally spent days on end searching, and trying new things. What happened is I think I tried flashing a GSM rom (the new android revolution 30.0) onto my Sprint HTC One. I just got this phone two weeks ago, and unfortunately upgraded to the 4.3 with the 1.55 hboot. So, S-on. I was using slimbean as my dd, but wanted to give revolution a try. When I dl the rom, it stated for m7wls, so thought I was good. Well, went into a kind of bootloop where it would upgrade android like 41 out of 120, then it would restart. When it finally would boot up, I had about fifteen seconds before it would reboot again. I tried to wipe and restore, but same thing was happening. I read that the partitions may have been screwed up from the gsm to cdma so, I wiped data and everything. I was going to relock and flash an RUU. Then I find out that there isn't one yet for the 4.3. I tried the Guru reset, updating drivers, sideloading, flashing cwm from twrp, pushing and had a rom boot up once, but no service or gapps. In cmd fastboot, my phone is recognized. But, when I use adb, it can't find it.I can get into recovery, and I have the official android 4.3 stock rom on my laptop ready to flash, but just can't get it to the phone. I am a noob, so I am sorry for that, but we all were at one time or another. I researched, tried to learn as much as I could before I took the plunge. I've read thread upon thread here and in other forums trying to find a fix. Everything that I've tried from some of these posts just didn't work for me. I don't know what I'm doing wrong, and I am not sure what you guys would need from me as far as more info. But, I would be grateful if someone could steer me in the right direction. Thanks in advance, and again apologies if I'm not doing things right for you guys. Just trying to learn and do.
C:\Users\Guest\Desktop\Fastboot>fastboot devices
FA38DS904955 fastboot
C:\Users\Guest\Desktop\Fastboot>fastboot flash rom.zip Dev-3.22.1540.1-Stock-Roo
ted-DE-ODEX.zip
target reported max download size of 1526722560 bytes
sending 'rom.zip' (1061169 KB)...
OKAY [ 47.135s]
writing 'rom.zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 169.469s
This is what cmd tells me when I try to flash the rom.
Dev-3.22.1540.1-Stock-Rooted-DE-ODEX.zip
Click to expand...
Click to collapse
Is not a Sprint rom
bigdaddy619 said:
Is not a Sprint rom
Click to expand...
Click to collapse
Even when I tried to flash slimbean, same thing happens. Thank you for the reply though.
I downloaded super one rom to laptop, tried using adb sideloader, but it doesn't detect my device. I went into mounts and storage on cwm and tried mounting usb, but doesn't toggle. I really am in desperate need of directions. I would even pay if I could lol.
bbjay351 said:
Even when I tried to flash slimbean, same thing happens. Thank you for the reply though.
I downloaded super one rom to laptop, tried using adb sideloader, but it doesn't detect my device. I went into mounts and storage on cwm and tried mounting usb, but doesn't toggle. I really am in desperate need of directions. I would even pay if I could lol.
Click to expand...
Click to collapse
Installed universal usb drivers, got sideload working. But now after installing the rom it is in bootloop.
Installed slimbean, I can get into the rom, but only for a minute or two. I have no service at all. When I go into about phone phone status it shows unknown network, out of service, unknow phone number etc. How do I get that back up and running? And, how do I get it to stop rebooting after a few minutes? Thank you guys
Your partitions are borked from flashing a non Sprint Rom. To fix them
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456
Then side load your Rom and you should be golden.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
Your partitions are borked from flashing a non Sprint Rom. To fix them
if you are s-on, flash the 4.3 full firmware http://www.androidfilehost.com/?fid=23159073880933344
if you are s-off, flash the modified firmware http://www.androidfilehost.com/?fid=23159073880933456
Then side load your Rom and you should be golden.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Tried sideloading this and fails saying zip file is corrupt.
bbjay351 said:
Tried sideloading this and fails saying zip file is corrupt.
Click to expand...
Click to collapse
I hate to say it but use the Format Data option within TWRP to format your sdcard the try to sideload
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
bbjay351 said:
Tried sideloading this and fails saying zip file is corrupt.
Click to expand...
Click to collapse
Check PM
Get a signed download of the firmware and flash thru fastboot if nothing else.
Sent from my HTCONE using XDA Premium 4 mobile app
Big thanks
Just wanted to say thanks again to Bigdaddy619! Spent the time with me to walk me through. Learned a lot from him. And a thanks to all that replied. Love learning new stuff, even if it makes me pull my hair out lol
bbjay351 said:
Just wanted to say thanks again to Bigdaddy619! Spent the time with me to walk me through. Learned a lot from him. And a thanks to all that replied. Love learning new stuff, even if it makes me pull my hair out lol
Click to expand...
Click to collapse
Updated steps for below
So this is what we did:
1.We downloaded the s-on firmware zip from the link provided by @Konfuzion
2.Renamed it firmware.zip (put the firmware.zip into the folder you use to open your cmd window)
3.Booted to bootloader
4.Then used these commands
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot
He got an error so I had him re-lock his bootloader
5.Ran the commands again
Got another error
Code:
failed 90 hboot pre-update! please flush image again
press the UP Arrow on your keyboard and press enter to issue the command again.
6.He was able to unlock the bootloader again and re-flash TWRP and sideload or adb push a rom to his phone.
7. S-OFF using Rumrunner
8.Win lol
bigdaddy619 said:
So this is what we did:
1.We downloaded the s-on firmware zip from the link provided by @Konfuzion
2.Renamed it firmware.zip (put the firmware.zip into the folder you use to open your cmd window)
3.Booted to bootloader
4.Then used these commands
Code:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot
He got an error so I had him re-lock his bootloader (not sure if it was needed but...)
5.Ran the commands again
Got another error
Code:
failed 90 hboot pre-update! please flush image again
press the UP Arrow on your keyboard and press enter to issue the command again.
6.He was able to unlock the bootloader again and re-flash TWRP and sideload or adb push a rom to his phone.
7. S-OFF using Rumrunner
8.Win lol
Click to expand...
Click to collapse
Ok so I am in a similar position with one of my Sprint devices (I have 2 my kids and mine...) Anyway the device is s-off and had gone into TWRP and formated everything in anticipation of loading a new ROM that 4.3 based so wiped everything and then was going to push the rom with ADB... Problem I am having is that ADB doesn't see the device.
Now it shouldn't be a driver issue as I connected my other device to it with no problem and adb sees it fine.
@bigdaddy619.
I followed steps 1-4 except I used the zip for s-off and received no errors so I went back to twrp and attempted to sideload and still won't work.
Thanks for the assistance.
MG
EDIT: Well looks like it was a driver issue, odd since I wasn't having trouble connecting with my other Sprint HTC One but I changed to the Universal Windows ADB Driver listed here in this post. I also updated to the latest Android-SDK and was able to sideload... Thanks all for the info in this thread!
MG
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