I successfully had Cyanogenmod installed, but now when I turn my phone on it stays stuck at the loading screen and goes back and forth to the HTC start up (the screen before the Cyanogen loading screen). I tried reverting back to stock using the RUU but it fails every. single. time. and there's nothing I can find that will help me at least get my phone back working.
Any help? My carrier is T-Mobile
moneyhbags said:
I successfully had Cyanogenmod installed, but now when I turn my phone on it stays stuck at the loading screen and goes back and forth to the HTC start up (the screen before the Cyanogen loading screen). I tried reverting back to stock using the RUU but it fails every. single. time. and there's nothing I can find that will help me at least get my phone back working.
Any help? My carrier is T-Mobile
Click to expand...
Click to collapse
Sounds like possibly you need to flash the boot.img on it. I think , a senior member will correct me, but if your S-On and rooted, you should do that , S-Off don't require the boot.img.
leesumm said:
Sounds like possibly you need to flash the boot.img on it. I think , a senior member will correct me, but if your S-On and rooted, you should do that , S-Off don't require the boot.img.
Click to expand...
Click to collapse
I don't know what S-On or S-Off means, but it's been like 20 minutes and it's now stuck at the HTC quietly brilliant screen.
I did do a back-up before I rooted it. I tried re-installing Cyanogenmod but the installer says my phone is unrecognizable.
edit: still stuck at Cyanogen loading screen =(
moneyhbags said:
I don't know what S-On or S-Off means, but it's been like 20 minutes and it's now stuck at the HTC quietly brilliant screen.
I did do a back-up before I rooted it. I tried re-installing Cyanogenmod but the installer says my phone is unrecognizable.
edit: still stuck at Cyanogen loading screen =(
Click to expand...
Click to collapse
S-ON or off means security is on or off, If you haven't done the mod to S-Off , your still stock S-On. To see for sure though , in the bootloader mode at the top it will say Tampered first line , then the second should say something like M7 ??? PVT ship. S-On
What recovery are you using? CWM or TWRP . Do you know or use ADB?
I just reread your OP and you said you RUU'd. why? I think too with S-On you have to relock the bootloader to RUU then unlock after boot. You can use the same unlock.bin code that you used to unlock the first time if you still have it too . Best if you done the root and everything else , do some reading on S-Off procedure and do that .
leesumm said:
S-ON or off means security is on or off, If you haven't done the mod to S-Off , your still stock S-On. To see for sure though , in the bootloader mode at the top it will say Tampered first line , then the second should say something like M7 ??? PVT ship. S-On
What recovery are you using? CWM or TWRP . Do you know or use ADB?
Click to expand...
Click to collapse
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
moneyhbags said:
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
Click to expand...
Click to collapse
I have had better luck with TWRP the latest one which is I think 2.6.3.
leesumm said:
I have had better luck with TWRP the latest one which is I think 2.6.3.
Click to expand...
Click to collapse
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
moneyhbags said:
Just checked, it's Tampered, Unlocked, M7, and S-On.
I used CWM for recovery and I have ADB.
Click to expand...
Click to collapse
I had the same problem like you... I have installed first twrp 2.6.3.3 then root the VIPER ROM, so I finelly got into the phone... Then I have flashed again vith ARHD 41.0 ROM and my phone is working perfect But I had the same problem as you... this is becouse of the S-ON and you stuck in boot-loop
moneyhbags said:
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
Click to expand...
Click to collapse
IF you can get to recovery, do you have a backup that is working ? If not you may have to unzip the CM rom, look for the boot.img , put that into the adb folder then run adb with fastboot flash boot.img , then reboot and it should go. If you have a back up of the Cm rom you might be able to go to recovery and do a restore from the backup there. And another thing you might do. Not sure if it will mess it up but/ fastboot erase cache then boot
peca_slo said:
I had the same problem like you... I have installed first twrp 2.6.3.3 then root the VIPER ROM, so I finelly got into the phone... Then I have flashed again vith ARHD 41.0 ROM and my phone is working perfect But I had the same problem as you... this is becouse of the S-ON and you stuck in boot-loop
Click to expand...
Click to collapse
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
moneyhbags said:
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
Click to expand...
Click to collapse
Good glad to know it works again.. Now do some reading on S-Off sounds like you have some idea of ADB so it really isn't that hard and it will make flashing easier in the future. You might even consider a full GPE conversion. I did it and like the Kit Kat but running Elegancia and once in a while revert back to the GPE with Xposed and Gravity Box KK for a mod. Super good battery.
moneyhbags said:
Yeah well I'll switch to that once I figure out how to get my phone to at least start working...
any help?
Click to expand...
Click to collapse
boot to recovery
clear cache and delvik
reboot to bootloader
fastboot USB and type
fastboot erase cache
now see if your phone will bootup
If no, find a different rom to flash
and here is a recovery flashable version of TWRP, flash it the same you do a rom and reboot to recovery to see it
moneyhbags said:
I just fixed it. I downloaded the stock T-Mobile recovery.img for HTC One, then opened the command line used fastboot uploaded the recovery.img then used that to recover and it just magically reinstalled the Cyanogenmod.
Click to expand...
Click to collapse
whoops looks like i got here late ..
Related
so i was stuck for a long time with a crappy rom that kept getting my calls stuck,so today i finally switched it to cooldroid revolution and it got stuck on boot so i tried to maybe switch some kernels and nothing worked so i tried other roms as well like Nik's Project X and paranoidandroid
and nothing works im stuck like that without a phone all day. can someone please find a answer?
Noamzoro said:
so i was stuck for a long time with a crappy rom that kept getting my calls stuck,so today i finally switched it to cooldroid revolution and it got stuck on boot so i tried to maybe switch some kernels and nothing worked so i tried other roms as well like Nik's Project X and paranoidandroid
and nothing works im stuck like that without a phone all day. can someone please find a answer?
Click to expand...
Click to collapse
What HBOOT version are you running and are you S-OFF or S-ON. You didn't give enough information to give you a straight answer.
Off hand, I would say that you are using an unlocked HBOOT, so you probably just need to manually flash the boot.img file from the last ROM you tried to install.
tpbklake said:
What HBOOT version are you running and are you S-OFF or S-ON. You didn't give enough information to give you a straight answer.
Off hand, I would say that you are using an unlocked HBOOT, so you probably just need to manually flash the boot.img file from the last ROM you tried to install.
Click to expand...
Click to collapse
im using 1.16.0000 Hboot and S-On
Noamzoro said:
im using 1.16.0000 Hboot and S-On
Click to expand...
Click to collapse
follow the steps.
1. extract boot.img from zip file
2. go to adb tools ..if you dont know what adb is google it....
3. fire up adb ...
4.put your phone in fastboot mode ..(boot in hboot by powering down your phone and press vol-down and power togethr while switching on)
5. connect to your pc
6. type fastboot flash boot boot.img
7. reboot your phone
8. done...
and yes important stuff only falsh the boot.img file of the rom installed on your device..dont flash any other boot.ing
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..
Hey guys,
This will be an interesting first post... I do have to say I apologize for making a thread regarding this, but I really feel like I'm stuck and would really benefit from some direct help. I've been searching non-stop for the last 2 days, and currently have more than 20 hours infront of my computer trying to figure out why I cannot restore this HTC One.
Details;
Tampered
Unlocked
M7_UL pvt ship S-ON RH
Hboot 1.55
Radio-4a.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.22.631.1
eMMC-boot 2048mb
Sep17/2013
ROGERS CANADA NETWORK
-Currently cannot get any further than HBOOT and TWRP 2.6
-Ends up in boot loop
-Recognized on Fastboot, and device manager, but cannot access via My Computer
-Phone had a garbage ROM, and I ended up wiping my entire phone. Every single file.
-If I could somehow get an install onto it I could try to get it going through TWRP?
-I've downloaded several gigs of roms that I've tried, and cant seem to get them to work.
-Phone is essentially bricked and non-functional. There is a way to save it I think??
-ABD device not found, have SDK, fully updated drivers all around... nothing.
I just want the phone back to factory... but ROGERS RUU files are .zip and not .exe
Very difficult to figure out a solution...
Please help guys,
Sorry I could not get it on my own. New to phones but not new to computers and troubleshooting.
I'll leave this tab open and constantly check whilst I look for more answers on my issue.
Thank you!
-Spence
I would try sideloading a rom through TWRP. If I remember correctly, you need the latest ADB which comes bundled with this:
http://developer.android.com/sdk/index.html
I think having the latest ADB binaries may also help your PC detect your phone. Once you have that downloaded, you can sideload a rom. More info on that here:
http://teamw.in/ADBSideload
Finally got it to recognize the device on ADB
However it says unauthorized, because I assume I couldnt activate debugging.
Still cant because it's bricked!
Drivers are all up to date to the best of my knowledge
Double and triple checked?
I will try to do something through TWRP... I dont have a lot of experience with it, I know I was fighting with it for a couple hours today, trying to get through all the errors - or to detect my computer properly.
ADB Sideload Complete
Failed
Unable to mount across the board.
-Spencer
UPDATE:
Sideload seems to be working. Still getting errors for being unauthorized I think..
12:33am
Via CWM I was able to get Android Revolution HD to install, and actually went through the entire install process...
At the end it said some files were unable to be installed, and then put me back in the bootloader/cwm cycle...
I just want to get the phone stable enough to use, so that I can revert it back to stock!
-Spence
Lets just say that the phone is completely non-functional.
What would be the step by step process of addressing such a problem?
As if the phone were not working at all...?
Can't seem to get it going, no matter how hard I try!
20 hours in!
Bawshawg said:
Lets just say that the phone is completely non-functional.
What would be the step by step process of addressing such a problem?
As if the phone were not working at all...?
Can't seem to get it going, no matter how hard I try!
Flash the last TWRP (2.6.3.4)
Flash ARHD 51
Fastboot erase cache
Erase davil'k cache
20 hours in!
Click to expand...
Click to collapse
Flash the last TWRP (2.6.3.4)
Flash ARHD 51
Fastboot erase cache
Erase davil'k cache
Uxepro said:
Flash the last TWRP (2.6.3.4)
Flash ARHD 51
Fastboot erase cache
Erase davil'k cache
Click to expand...
Click to collapse
Followed by what though?
If I'm basically just starting from the hardware up?
Nothing seems to be going in my favour! :S
Bawshawg said:
Lets just say that the phone is completely non-functional.
What would be the step by step process of addressing such a problem?
As if the phone were not working at all...?
Can't seem to get it going, no matter how hard I try!
20 hours in!
Click to expand...
Click to collapse
Uxepro said:
Flash the last TWRP (2.6.3.4)
Flash ARHD 51
Fastboot erase cache
Erase davil'k cache
Click to expand...
Click to collapse
ARHD 51 will not help as it still requires s-off
I'm going to recommend these instructions posted by @SaHiLzZ
Download Canadian 1.55 HBOOT recovery: http://goo.gl/2Kntxz
Download TWRP 2.6.3.3: http://techerrata.com/file/twrp2/m7/...2.6.3.3-m7.img
Make sure you're in the bootloader go into fastboot and make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery_stock_155hboot_htc_one_m7.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running <<< Important!
Phone will go out and start bootlooping. Now power off and go back to bootloader mode:
Go into fastboot
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into custom recovery and you should be good to proceed.
Click to expand...
Click to collapse
Sideload should work after this
Android revolution 51 does not require S-off...
Unless you want to upgrade the firmware
Uxepro said:
Android revolution 51 does not require S-off...
Unless you want to upgrade the firmware
Click to expand...
Click to collapse
please don't confuse things ... ARHD 51 will not boot / s-on
http://forum.xda-developers.com/showpost.php?p=50085331&postcount=185
http://forum.xda-developers.com/showpost.php?p=50084310&postcount=174
try Sideloading this one >> http://xda7.androidrevolution.nl/db_mirror/ROMs/HTC_One/Android_Revolution_HD-One_31.6.zip
clsA said:
please don't confuse things ... ARHD 51 will not boot / s-on
http://forum.xda-developers.com/showpost.php?p=50085331&postcount=185
http://forum.xda-developers.com/showpost.php?p=50084310&postcount=174
Click to expand...
Click to collapse
It's an uncommon thing. It can happen, but it does not require s-off.
"You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF"
Uxepro said:
It's an uncommon thing. It can happen, but it does not require s-off.
"You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF"
Click to expand...
Click to collapse
Dude he just posted he flashed it and it won't boot .. what don't you understand ?
clsA said:
Dude he just posted he flashed it and it won't boot .. what don't you understand ?
Click to expand...
Click to collapse
It doesn't boot because he used twrp 2.6, instead of 2.6.3.3 or didn't erase cache
I was S-on and everything was fine with flashing arhd 51.
No way a rom requires s-off to be flashed, unless an upgrade of hboot is mandatory.
Folks!
Somehow, I ended up getting the HTC Guru reset to work....
After literally 24 hours of messing with this thing.
So now I am running 4.3
and in the near future will try to completely restore back to all Rogers Canada software and update to their Kitkat OTA???
Or should I just wait a bit for someone to release one that works correctly?
Thank you for the help!
-Spence
Bawshawg said:
Folks!
Somehow, I ended up getting the HTC Guru reset to work....
After literally 24 hours of messing with this thing.
So now I am running 4.3
and in the near future will try to completely restore back to all Rogers Canada software and update to their Kitkat OTA???
Or should I just wait a bit for someone to release one that works correctly?
Thank you for the help!
-Spence
Click to expand...
Click to collapse
Just upgrade your TWRP, and flash the 4.4.2 rom you want
If you can Soff, then you will be able to run RUU for dev edition kitkat, or do the google edition conversion. That will give you an upgrade path in future by OTA
sent from my mobile device
My friend's phone is stuck in bootloop and I believe it's soft bricked.
It's a stock brand new HTC One M7.
It was updating one day and he said it might have got corrupted because it just shut down and when it booted back up it was stuck at the HTC Screen and wouldn't do anything.
Over the last week I have been trying to unbrick it.
It's LOCKED and S-ON Sprint HTC One M7.
I did a factory reset, wiped cache, dalvic cache, reboot. I tried putting in fastboot and flashing RUU on it but it kept failing because the RUU I had was a lower version of the image than the current one on the phone and I read online that I can only flash backwards if it's S-OFF.
Any help?
Thanks!
technocrat7 said:
My friend's phone is stuck in bootloop and I believe it's soft bricked.
It's a stock brand new HTC One M7.
It was updating one day and he said it might have got corrupted because it just shut down and when it booted back up it was stuck at the HTC Screen and wouldn't do anything.
Over the last week I have been trying to unbrick it.
It's LOCKED and S-ON Sprint HTC One M7.
I did a factory reset, wiped cache, dalvic cache, reboot. I tried putting in fastboot and flashing RUU on it but it kept failing because the RUU I had was a lower version of the image than the current one on the phone and I read online that I can only flash backwards if it's S-OFF.
Any help?
Thanks!
Click to expand...
Click to collapse
if the phone is new (never tampered with) and still under warranty, send it back for repair or replacement
s-off and run the ruu
unlock bootloader, flash a custom recovery and flash a rom or a nandroid backup
post in the sprint htc one forum for more detailed info
So the first step is S-OFF because I don't think k the warranty is on it.
And then custom recovery and what was the part with a custom nandroid backup? Can I run someone else's nandroid?
And if I put S-OFF on it, I can flash an older version of RUU right?
Sent from my HTC One_M8 using XDA Free mobile app
I'm pretty sure that in order to S-off you will need to be booted up first? The good news is that you can flash the full factory RUU with a s-on boot loader locked device so you may need to figure out how to do that first. Do you have an adb/fastboot environment set up? If so you are practically there. On a side note, I have seen no less than 3 m7s fail and softbrick on the first attempt at applying an ota, but it was always after S-off and a conversion to fully stock gpe (these were gsm models). I figured it was just because of the mods but who knows. Anyway, if you can locate and install a fully stock sprint RUU you should be back to where you were before the ota at which point you can proceed with whatever else you want to do.
technocrat7 said:
So the first step is S-OFF because I don't think k the warranty is on it.
And then custom recovery and what was the part with a custom nandroid backup? Can I run someone else's nandroid?
And if I put S-OFF on it, I can flash an older version of RUU right?
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
sorry for the confusion, this was not steps to follow (1-2-3-4) but either 1 or 2 or 3 or 4
if you go for option 2, yes you can flash older ruu.
for option 3, yes you can flash someone else nandroid, but it must be for your phone variant (sprint) and the ideal nandroid backup should be the same OS version.
---------- Post added at 02:34 PM ---------- Previous post was at 02:29 PM ----------
dougeedug said:
I'm pretty sure that in order to S-off you will need to be booted up first?
Click to expand...
Click to collapse
Right, you need a booted rom to s-off. (at least for the M7_UL dont know for the srpint variant)
The good news is that you can flash the full factory RUU with a s-on boot loader locked device so you may need to figure out how to do that first.
Click to expand...
Click to collapse
Not exactly, you can only flash ruu with a s-on device (and locked/relocked bootloader) if the ruu is same of higher version. In that case the OP need to find another ruu (if any available)
Yeah, I have a 4.2 image when loading RUU, therefore I'm not able to use an RUU.
So what else do I need to do?
And I do have an adb and fastboot environment set up, yes.
Should I instead just S-OFF It, put a custom bootloader on it and then flash a custom recovery?
Yes if you can achieve s-off you can put any RUU you want on it and that will rule out software issues.
Okay so I unlocked it.
However I looked online how to do S-OFF and all the articles I found said the phone has to be on an functional to enable USB debugging mode and to run the appropriate programs to make it S-OFF.
Is there any other way to do it?
Now that you are bootloader unlocked, flash a custom recovery and from there a rom. That should get you back to life so you can proceed however you wish.
I have a custom recovery.
TWRP 2.6.0.0 or something. And I loaded into it and my phone got stuck and the touch wouldn't work. It says "slide to unlock" and sliding doesn't work.
What do I do now? I can't even reboot the light keeps flashing and I even tried under a bright light and still nothing.
I'm letting the battery die to restart. When u do restart it, what do I do about the bad bootloader? Can I just put another one on there? I want Philz now after that terrible experience.
technocrat7 said:
I have a custom recovery.
TWRP 2.6.0.0 or something. .
Click to expand...
Click to collapse
This is very alarming! Be double sure you are flashing exactly what you need. The CWM you would need is 6.0.4.8 found on this page. I'm not sure what TWRP version is suitable as I don't use it. I don't dislike it. I have used it and it has worked.
Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!
technocrat7 said:
Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!
Click to expand...
Click to collapse
We will have to see what it does after you let it die. The way your phone is acting is not good. Unfortunately, we must keep in mind that it may be a hardware fault causing all of this from the start. If it will still charge offline, then you'll get a chance to see if you can power it up into the bootloader and get fastbootUSB.
technocrat7 said:
Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!
Click to expand...
Click to collapse
why are you waiting for it to die ? if you want to get out of recovery and tough isn't working, just hold down the power button and the volume down until the lights on the bottom flash 10 to 15 times, when it goes off, release the power button but continue to hold the volume down, you are now in the bootloader, or should be.
and yes, if you flash another recovery it will overwrite the one that's on there, unfortunately, most rom's require TWRP
---------- Post added at 03:28 AM ---------- Previous post was at 03:22 AM ----------
I also just noticed you have the Sprint M7, you cant use the normal recoveries or rom's, they wont work, you need to use the ones built for your phone, which is different to the normal gsm version.
I would try twrp 2.6.3.3 or this http://mdmower.cmphys.com/twrp-m7spr/ a newer custom compiled twrp so your os version dont get wiped on bootloader.
Dang, being with Sprint complicates things?
So will that one be safe to put on my phone? And that means I can't get Philz huh?
technocrat7 said:
Dang, being with Sprint complicates things?
So will that one be safe to put on my phone? And that means I can't get Philz huh?
Click to expand...
Click to collapse
No it doesn't complicate things, it's the same procedure, it's like with anything, you just have to make sure you get the right files. Your phone is cdma not gsm.
---------- Post added at 04:28 AM ---------- Previous post was at 04:17 AM ----------
http://forum.xda-developers.com/sprint-htc-one?nocache=1&z=1858146956656128
You can find all of those right files there
Okay thank you!
It is unlocked, rooted and had a custom recovery on it!
Now the last thing I need help with is, getting S-OFF because I still can't boot up the phone.
So now I just need to get S-OFF and then flash a custom ROM image on there and flash a custom image on it or something.
All I see when it boots up is the HTC screen.
technocrat7 said:
Okay thank you!
It is unlocked, rooted and had a custom recovery on it!
Now the last thing I need help with is, getting S-OFF because I still can't boot up the phone.
So now I just need to get S-OFF and then flash a custom ROM image on there and flash a custom image on it or something.
All I see when it boots up is the HTC screen.
Click to expand...
Click to collapse
You need a working Rom on it to go s-off, all s-off tools are run from an android booted phone, so download a Rom of your choice, in your case a sense Rom, make sure you get it from the link I supplied earlier for your particular phone, move it to the same folder where your adb and fastboot are on your computer, boot your phone into recovery (main screen only, no sub menus) and plug it into your computer, the type
adb push NAME_OF_ROM.zip /sdcard/
Takes a while so be patient, the command window will let you know when it's done.
Unplug your phone and in recovery select install, select your Rom from the list and follow the instructions
Seanie280672 said:
You need a working Rom on it to go s-off, all s-off tools are run from an android booted phone, so download a Rom of your choice, in your case a sense Rom, make sure you get it from the link I supplied earlier for your particular phone, move it to the same folder where your adb and fastboot are on your computer, boot your phone into recovery (main screen only, no sub menus) and plug it into your computer, the type
adb push NAME_OF_ROM.zip /sdcard/
Takes a while so be patient, the command window will let you know when it's done.
Unplug your phone and in recovery select install, select your Rom from the list and follow the instructions
Click to expand...
Click to collapse
So there's a slight problem.
"ADB Devices" doesn't show anything, it says "Devices not found"
The reason I would say is because it does not have USB Debugging enabled.
And I can't get into the phone to enable it because i'm not at that point yet.
Is there anything else I can do besides "adb push" to get the file on there?
Fastboot stuff works fine.
I went to the link you provided and found CynogenMod 11 I wanted to put on there.
After looking inside of the ZIP I downloaded there's a .img file inside called "boot.img" can I do anything with that?
Thanks!
Long story short usually first thing I do is root and rom my phones, but I recently got an HTC One off of swappa and loved it, didnt see a reason to root. I figured I would give dual-booting via multiboot a shot, so I HTC Dev unlocked it, rooted it, installed elemental kernel, and flashed CM11. Well CM11 wouldnt boot and I tinkered so I just figured I would cut my losses, so I followed the instructions to remove it which wiped my SD card. I was on linux, and couldn't get fastboot usb, just fastboot ac. So I hopped on a friends computer, Win8.1 and downloaded a special set of drivers and whatnot, got ADB and fastboot running. TWRP wasnt working very well, it wouldnt let me use ADB so I fastboot installed CWM. I managed to push cyanogenmod to it, but kept getting an error that wouldnt let me install it. So I figured next thing to do would be RUU it, and I got my version number and matched the CID and all that, it failed with an error 12. Both .exe and .zip give me the same error. Well not its 3am and I've been at it for 5 hours now, I dont know what to do. It seems like everything I try to do fails. Please give me some advice.
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.27.3218.14
OS-
eMMC-boot 2048MB
flapflip22 said:
Long story short usually first thing I do is root and rom my phones, but I recently got an HTC One off of swappa and loved it, didnt see a reason to root. I figured I would give dual-booting via multiboot a shot, so I HTC Dev unlocked it, rooted it, installed elemental kernel, and flashed CM11. Well CM11 wouldnt boot and I tinkered so I just figured I would cut my losses, so I followed the instructions to remove it which wiped my SD card. I was on linux, and couldn't get fastboot usb, just fastboot ac. So I hopped on a friends computer, Win8.1 and downloaded a special set of drivers and whatnot, got ADB and fastboot running. TWRP wasnt working very well, it wouldnt let me use ADB so I fastboot installed CWM. I managed to push cyanogenmod to it, but kept getting an error that wouldnt let me install it. So I figured next thing to do would be RUU it, and I got my version number and matched the CID and all that, it failed with an error 12. Both .exe and .zip give me the same error. Well not its 3am and I've been at it for 5 hours now, I dont know what to do. It seems like everything I try to do fails. Please give me some advice.
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.27.3218.14
OS-
eMMC-boot 2048MB
Click to expand...
Click to collapse
Your problems started at trying to install cm11 with elementalx kernel, that's a sense kernel and cm is not a sense Rom, so unlock your bootloader again and flash twrp 2.6.3.3 to your phone, push a sense Rom of your choice to the phone and flash it, I'm guessing the ruu isn't working as you can't back flash with s-on and you already have the newest os / firmware on your phone according to your hboot version
Seanie280672 said:
Your problems started at trying to install cm11 with elementalx kernel, that's a sense kernel and cm is not a sense Rom, so unlock your bootloader again and flash twrp 2.6.3.3 to your phone, push a sense Rom of your choice to the phone and flash it, I'm guessing the ruu isn't working as you can't back flash with s-on and you already have the newest os / firmware on your phone according to your hboot version
Click to expand...
Click to collapse
Will give this a try, thanks
and dont forget, 4.4+ sense roms (i.e arhd) must be flashed using twrp 2.6.3.3 or 2.6.3.4 and newest CM11 roms must be flashed using twrp 2.7.1.1 because of the new fstab layout introduced May, 2014
alray said:
and dont forget, 4.4+ sense roms (i.e arhd) must be flashed using twrp 2.6.3.3 or 2.6.3.4 and newest CM11 roms must be flashed using twrp 2.7.1.1 because of the new fstab layout introduced May, 2014
Click to expand...
Click to collapse
Noted, just flased 2.6.3.3 and adb pushing a sense 6 rom. Kinda funny, 2.6.3.3 connects to adb on linux but no other recovery would. Granted it wont let me side-load but as long as I can push files I'm good. Just tested it by pushing a random zip file, all is good. Just gonna wait for it to finish downloading, adb push it and try to flash it. If all goes as well as I hope it should work. I'll let you guys know if I need more help.
Thank you so much.
flapflip22 said:
Noted, just flased 2.6.3.3 and adb pushing a sense 6 rom. Kinda funny, 2.6.3.3 connects to adb on linux but no other recovery would. Granted it wont let me side-load but as long as I can push files I'm good. Just tested it by pushing a random zip file, all is good. Just gonna wait for it to finish downloading, adb push it and try to flash it. If all goes as well as I hope it should work. I'll let you guys know if I need more help.
Thank you so much.
Click to expand...
Click to collapse
if you cant sideload its probably because you are using an outdated version of adb. latest version of adb is 1.0.31. however, you'll be fine using adb push.
alray said:
if you cant sideload its probably because you are using an outdated version of adb. latest version of adb is 1.0.31. however, you'll be fine using adb push.
Click to expand...
Click to collapse
Alright, managed to adb push to files to my phone but now it just says "updating partition details..." then "error flashing zip /sdcard/myrom.zip" and FAILED at the bottom. What next?
flapflip22 said:
Alright, managed to adb push to files to my phone but now it just says "updating partition details..." then "error flashing zip /sdcard/myrom.zip" and FAILED at the bottom. What next?
Click to expand...
Click to collapse
you might want to wipe everything + format data then push the rom again and install it. Also check MD5 of the rom
alray said:
you might want to wipe everything + format data then push the rom again and install it. Also check MD5 of the rom
Click to expand...
Click to collapse
It worked! Followed your instructions, then I used a CM 10.2 rom and a JB kernel and it worked just fine. Next I'm gonna s-off and superCID it so I wont have to go through any of this again, and then flash the ROM and kernel I want. Probably not gonna tinker anymore until later when the newest HTC sense release comes out.
flapflip22 said:
It worked! Followed your instructions, then I used a CM 10.2 rom and a JB kernel and it worked just fine. Next I'm gonna s-off and superCID it so I wont have to go through any of this again, and then flash the ROM and kernel I want. Probably not gonna tinker anymore until later when the newest HTC sense release comes out.
Click to expand...
Click to collapse
:good: happy flashing