I soft bricked my Sprint HTC One M7 and can't get a new ROM working. I'll start by saying I am probably in over my head and never should have done this to begin with. On the bright side, this is a backup device essentially being used as a toy. I have spent hours trying different things and searching the forums without finding any threads with the same issue. My apologies in advance if there is a thread I could have read but I could not find one. So, on to what I have done and the current issues I am having.
I'm not sure all of this background is necessary but it can't hurt. I successfully unlocked the phone, loaded TWRP, and I thought, rooted the phone, all using the guide on htconeroot.com. I attempted to run a program that requires root access and it said "no root access". I then used fastboot to load SuperSU 2.46 and it all went south. After I loaded SuperSU 2.46, the phone hung on the HTC One load screen.
At this point, I decided I would just Flash a new ROM to the phone. After spending hours trying to get adb to recognize the phone (a whole different story), I finally managed to get adb sideload to work and flashed the most recent version of Android Revolution. I went through the entire install process and got a message saying the install was successful. However, when the phone rebooted, as it was loading it switched to say recovery at the top and loaded into TWRP. I noticed the message icon at the bottom, center of the screen and tapped it. It switched to a gray screen which said "updating partition details..." at the bottom. It just hangs on that screen. I wiped cache with no luck and had same result when I re-flashed.
I tried Viper ROM 8.0 and had the exact same issue as Revolution.
I attempted Bad Boyz 1.4 which got a little further but still wouldn't load. I tried Bad Boyz 1.2 to see if their ROM with Sense 5.0 would work. That version said install successful and rebooted. I got really excited when it showed updating Android and started counting through app updates. It got to the unlock screen with the time and HTC default background picture. When I pull up the lock to unlock the phone, I get error messages that messages stopped unexpectedly and HTC Sense stopped unexpectedly. It then sits on a white screen with the green HTC logo for ~10 seconds and then reboots. If I let it go without trying to unlock it, it still reboots after 20-30 seconds, caught in an unending boot loop.
I am at a loss at this point. Do I try a few other ROMs until I find one that works? Am I doing something wrong? I should add that the guide I used said nothing about a Nandroid backup so I don't have one ?, and I really don't want to go back to stock anyway.
Thanks in advance for any help.
Bucknut816 said:
I soft bricked my Sprint HTC One M7 and can't get a new ROM working. I'll start by saying I am probably in over my head and never should have done this to begin with. On the bright side, this is a backup device essentially being used as a toy. I have spent hours trying different things and searching the forums without finding any threads with the same issue. My apologies in advance if there is a thread I could have read but I could not find one. So, on to what I have done and the current issues I am having.
I'm not sure all of this background is necessary but it can't hurt. I successfully unlocked the phone, loaded TWRP, and I thought, rooted the phone, all using the guide on htconeroot.com. I attempted to run a program that requires root access and it said "no root access". I then used fastboot to load SuperSU 2.46 and it all went south. After I loaded SuperSU 2.46, the phone hung on the HTC One load screen.
At this point, I decided I would just Flash a new ROM to the phone. After spending hours trying to get adb to recognize the phone (a whole different story), I finally managed to get adb sideload to work and flashed the most recent version of Android Revolution. I went through the entire install process and got a message saying the install was successful. However, when the phone rebooted, as it was loading it switched to say recovery at the top and loaded into TWRP. I noticed the message icon at the bottom, center of the screen and tapped it. It switched to a gray screen which said "updating partition details..." at the bottom. It just hangs on that screen. I wiped cache with no luck and had same result when I re-flashed.
I tried Viper ROM 8.0 and had the exact same issue as Revolution.
I attempted Bad Boyz 1.4 which got a little further but still wouldn't load. I tried Bad Boyz 1.2 to see if their ROM with Sense 5.0 would work. That version said install successful and rebooted. I got really excited when it showed updating Android and started counting through app updates. It got to the unlock screen with the time and HTC default background picture. When I pull up the lock to unlock the phone, I get error messages that messages stopped unexpectedly and HTC Sense stopped unexpectedly. It then sits on a white screen with the green HTC logo for ~10 seconds and then reboots. If I let it go without trying to unlock it, it still reboots after 20-30 seconds, caught in an unending boot loop.
I am at a loss at this point. Do I try a few other ROMs until I find one that works? Am I doing something wrong? I should add that the guide I used said nothing about a Nandroid backup so I don't have one ?, and I really don't want to go back to stock anyway.
Thanks in advance for any help.
Click to expand...
Click to collapse
You have a CDMA Sprint htc one (M7WLS variant) ARHD is a rom for GSM htc one (M7_UL or M7_U variants). You can only flash custom recovery, custom roms, kernels ect that are made for the Sprint HTC One (M7WLS).
So you can flash twrp for sprint, then flash a sprint custom rom
or
return to your stock rom using a sprint RUU.
You can find the sprint roms in the "Sprint HTC One" section of xda. TWRP recovery for sprint can be found on their website, the filename should ends with "wls.img"
If your phone was running on android lollipop then using a lower version than supersu2.46 is what caused the bootloop. Thats why you shouldn't follow outdated guides from 2013 like the one at htconeroot.com
We can help you flashing the custom recovery/rom or the RUU, its up to you.
Thanks for the quick reply. I probably should have realized the CDMA vs GSM issue. I used to sell Sprint phones 20 years ago.
I would rather go with a custom ROM on the phone without all of the bloatware/sprint garbage.
I understand the issue with ARHD but what about Bad Boyz? I am using their Sprint ROM v 1.2 from the Sprint M7 section with no luck. It loads Android all the way to the lock screen with the time, status bar, and sense skyscraper wallpaper but then crashes. I tried 1.4 first and it got to the unlock screen but no status bar or sense background (skyscraper wallpaper).
You mention TWRP for Sprint. Is there a specific Sprint version and if I used a different version would it have gotten that far? Should I install a different version of TWRP and try flashing Bad Boyz again?
Bucknut816 said:
Thanks for the quick reply. I probably should have realized the CDMA vs GSM issue. I used to sell Sprint phones 20 years ago.
I would rather go with a custom ROM on the phone without all of the bloatware/sprint garbage.
I understand the issue with ARHD but what about Bad Boyz? I am using their Sprint ROM v 1.2 from the Sprint M7 section with no luck. It loads Android all the way to the lock screen with the time, status bar, and sense skyscraper wallpaper but then crashes. I tried 1.4 first and it got to the unlock screen but no status bar or sense background (skyscraper wallpaper).
You mention TWRP for Sprint. Is there a specific Sprint version and if I used a different version would it have gotten that far? Should I install a different version of TWRP and try flashing Bad Boyz again?
Click to expand...
Click to collapse
If there is a specific version of twrp mentioned in bad boyz thread, use that one. Otherwise any recent version should work but yes it must absolutely be a sprint twrp recovery.
Here are all the sprint version: https://dl.twrp.me/m7wls/
The M7_UL have different partition layout than the Sprint version (see both links below). The kernel (/boot partition), the OS (/system partition) and the radio (/radio) are not located at the same place on the memory. If flashing a M7_UL rom a Sprint phone you'll end up with the OS flashed on the Kernel partition, the Kernel flashed on the radio partition etc... This should be easily fixed by re-flashing a custom rom (if the rom does include its own kernel and radio to overwirte the bad flash). In the worst case, you'll have to flash a RUU to fix everything and then relfash sprint twrp and a sprint custom rom
http://forum.xda-developers.com/showthread.php?t=2317621
http://forum.xda-developers.com/showthread.php?t=2236254
Thanks for all the help. I was able to work on it again last night. I updated TWRP and was able to get viper ROM loaded and working...mostly. I had to delete HTCSetupwiz.apk to get out of the hands-free activation loop. The only problem is, the home key does not work. I get the haptic response from it but it doesn't do anything.
I tried Viper 8.0 and 9.0 and had same issue. I tried to switch to Bad Boyz and adb was hanging at ~7%. I am feeling much more comfortable with all of this and I think I can fix the loading issue with Bad Boyz. I just tired of fiddling with it last night. Before I do that, any idea how to get the home key working with Viper?
Would it be best to flash the ruu and start over just to make sure there are no lingering problems from screwing up the partitions?
Thanks again for all the help.
alray said:
If there is a specific version of twrp mentioned in bad boyz thread, use that one. Otherwise any recent version should work but yes it must absolutely be a sprint twrp recovery.
Here are all the sprint version: https://dl.twrp.me/m7wls/
Click to expand...
Click to collapse
Sorry to bug in... yeah I know, no need to tell me, people have been telling me plenty enough of their kind thoughts..., but the universal builds http://android.cmphys.com/twrp-m7/
should work on M7_U, M7_UL, M7_WLS, M7_WLV
they use "by-name" partitions, etc
maybe even the official builds, as mdmower is the maintainer, but unsure, since I haven't checked.
Obviously, still doesn't allow you flash a ROM not meant for your particular device, especially that many installer-scripts still use hardcoded mmcbkls, which would seriously break things
hmm, that reminds me.... have to check on something else too
Related
i have previously unlocked bootloader and rooted my device using the Hasoons all in one tool kit and then had been using ard 12.1.
I then fancied trying the latest GE 4.3 release (stock) which i downloaded and flashed and all seemed fine however when i went to check root was still there i have the icon but get a message saying that there is no su binary installed. I have tried to use the toolkit again to go back the root procedure in the hope i can re-install what ever is missing however for some reason now the tool kit comes up with an error message in the box saying waiting for device or device not recognized.
I have tried to sort the problem but now feel i am just going round and around in circles and really dont have the knowledge to put it right as im quite new to the flashing and modding side and dont fully understand all the terminology, im sure its probably something really simple to fix for those who know how so would really appreciate some advice.
My overall aim would be to be running the stock rom (or might even try the new arhd 4.3 ge) with root so that i can then use the volume + to wake mod as i find this really usefull as my power button is quite depressed and hard to use.
hpsauce37 said:
i have previously unlocked bootloader and rooted my device using the Hasoons all in one tool kit and then had been using ard 12.1.
I then fancied trying the latest GE 4.3 release (stock) which i downloaded and flashed and all seemed fine however when i went to check root was still there i have the icon but get a message saying that there is no su binary installed. I have tried to use the toolkit again to go back the root procedure in the hope i can re-install what ever is missing however for some reason now the tool kit comes up with an error message in the box saying waiting for device or device not recognized.
I have tried to sort the problem but now feel i am just going round and around in circles and really dont have the knowledge to put it right as im quite new to the flashing and modding side and dont fully understand all the terminology, im sure its probably something really simple to fix for those who know how so would really appreciate some advice.
My overall aim would be to be running the stock rom (or might even try the new arhd 4.3 ge) with root so that i can then use the volume + to wake mod as i find this really usefull as my power button is quite depressed and hard to use.
Click to expand...
Click to collapse
hello you are in need of the new 4.3 superuser.zip
http://download.clockworkmod.com/test/superuser-4.3-beta3.zip
if you are using CWM, when it asks to fix su upon reboot, select NO
Wow thank you!!!!!
You have no clue, or maybe you do, how lost I got trying to root my HTC One. This is all new to me, but this forum has helped massively. I found that the supersu zip I had was the older version when I already had 4.3 uploaded before rooting. This community rocks!
why do my gapps processes keep crashing?
NM forgot to full wipe
So I have the same issue - my only question is that I am running 4.4 now. Does this super user file still work or is there a 4.4 version?
Just use "SuperSu" if you face any root acces issues
Sent from my loved HTC One S using (most time buggy) Tapatalk
HHEELLPPP
Hi there, Im new to the rooting world, I have a htc one m7 from sprint trying to sim unlock it, as far as I know I unlocked the bootloader, tampered it, and rooted, but no access to super user so I can sim unlock it. I downloaded and installed this App that you mention, but still keeps saying no binary updated, and with this 4.3 version says there was an error installing superuser. Please help, I dont know what to do.
I was having this same issue on my Note 2 (4.3). I seem to have found a way to restore root that may help you as well.
I think this issue may be caused by the SU app & binary updates. Uninstalling the updates has restored root for me.
Go to:
Settings > More > Application Manager > All > SuperSU > Uninstall updates
(menu options may be slightly different on other devices)
This will roll back SuperSU and hopefully restore your root access.
Let me know if this helps.
Any updates on this? I'm trying to get root on an HTC One M7 that I just purchased and I'm running into the same error.
Thanks!
I've seen several discussions about this around the web, but none of the solutions I've read have helped me.
I have the Sprint HTC One M8 with custom ROM (ViperOneM8). The phone is activated and works fully, yet on reboot I always get the 'Hands Free Activation' wizard. If I hit Activate and then Done it goes away and I can use my phone normally, but every reboot brings it back up again.
Ideas?
I'll add that I have custom recovery (TWRP), rooted, custom ROM, and S-Off.
Htc m8 and sprint
aprwx said:
I've seen several discussions about this around the web, but none of the solutions I've read have helped me.
I have the Sprint HTC One M8 with custom ROM (ViperOneM8). The phone is activated and works fully, yet on reboot I always get the 'Hands Free Activation' wizard. If I hit Activate and then Done it goes away and I can use my phone normally, but every reboot brings it back up again.
Ideas?
Click to expand...
Click to collapse
Sorry I have the same issue with mine and finally ive called htc for a swap out phone to see if its a software defect. htc said that if it still occures it may bee an issue with sprint...
Are you running stock, or did you install a custom rom?
Sent from my Sprint HTC One M8
... I ask because when I first bought the phone it activated fine (with delay because it was the same day that the Galaxy S5 was released and Sprint had a delay activating phones that day)....but then I installed a custom ROM and am having this problem now with the custom ROM.
Thought I'd post here to help others who stumble on this thread....
This removed Hands Free Activation for me on Sprint's HTC One M8:
j to the 4n said:
Re: Hands Free Activation ... http://forum.xda-developers.com/showpost.php?p=50392144&postcount=2287
Click to expand...
Click to collapse
This worked for me, but a couple notes:
- I wasn't able to do the command line or Root Explorer. Both methods gave me errors, seemingly that I didn't have permissions to rename or delete the file. Why would that be? I went into TWRP and 'Fixed Permissions' but that didn't help. -- found it interesting that boot up is a LOT slower now that I fixed permissions.
- I ended up going into TWRP, mounting system and then going into TWRP's file manager to rename the file. Now Hands Free Activation no longer comes up (Thank you!), but I also note that neither PRL Update or Update Profile do anything now. Not a huge deal because before they just errored out anyway, but I would think it would be important to be able to do PRL/Profile updates.
aprwx said:
Thought I'd post here to help others who stumble on this thread....
This removed Hands Free Activation for me on Sprint's HTC One M8:
This worked for me, but a couple notes:
- I wasn't able to do the command line or Root Explorer. Both methods gave me errors, seemingly that I didn't have permissions to rename or delete the file. Why would that be? I went into TWRP and 'Fixed Permissions' but that didn't help. -- found it interesting that boot up is a LOT slower now that I fixed permissions.
- I ended up going into TWRP, mounting system and then going into TWRP's file manager to rename the file. Now Hands Free Activation no longer comes up (Thank you!), but I also note that neither PRL Update or Update Profile do anything now. Not a huge deal because before they just errored out anyway, but I would think it would be important to be able to do PRL/Profile updates.
Click to expand...
Click to collapse
Thanks for the heads up about this. I just changed the .apk to .bak with root explorer, noted the path and file name so I can change it back to update the pir and prl. Mine didn't usually error out.
aprwx said:
I've seen several discussions about this around the web, but none of the solutions I've read have helped me.
I have the Sprint HTC One M8 with custom ROM (ViperOneM8). The phone is activated and works fully, yet on reboot I always get the 'Hands Free Activation' wizard. If I hit Activate and then Done it goes away and I can use my phone normally, but every reboot brings it back up again.
Ideas?
Click to expand...
Click to collapse
I'd find another ROM.
I think you are always safest to stay with Sprint "Native" ROMs on a Sprint Phone. Mainly because the developer usually doesn't have a Sprint Phone to fully flesh it out on a regular day to day basis. There are subtle differences between all the carriers. You also end up with a Build of Android that exactly matches the corresponding build of Firmware.
Once you do get back on a native ROM you *MIGHT* have to do a ##72786# (full wipe) to get things back in order.
What I think are related issues lead me to a fix that was common to several problems I was having:
http://forum.xda-developers.com/sprint-htc-one-m8/general/fix-data-issues-t2819915
simply freeze vDM
My Verizon HTC One M7 is rooted and S-off. I have custom recovery Team Win 2.7 installed. I have back-ups so I'm not concerned about my phone being softbricked. The problem is that every time I install a rom with Aroma installer, it never works and puts me into a bootloop. Is it a problem with my custom recovery? Or is it my phone? Aroma goes through the whole process of installing and says it was successful, but still doesn't boot. The only rom I have been able to successfully flash is [ROM]Google Edition HTCOneVZW[KitKat] by JoelZ9614. All other roms like Skydragon, Viper, and Android revolution do not work. Any suggestions?
You have a Verizon phone, which is a CDMA device, not GSM, like most of the ROMs here, thus causing a bootloop. Look for ROMs, which have Verizon support or look around in the Verzion HTC one forums: http://forum.xda-developers.com/verizon-htc-one/development
That is weird. I could have swore I was looking in the Verizon development. Oops. Well I'm more new to Xda than I am to phones. Thanks I'll have to check out those roms.
So I was running a 4.4.x ROM and it was working great...then my company bought me a wifi-only tablet and that's pretty much useless for me without some tethering, and for whatever reason FoxFi didn't work with my ROM. I searched Google for days, tried mods and all sorts of Xposed stuff, but nothing worked. So I gave up and figured I'd try a new ROM. No reason not to switch to Lollipop, while I was at it - especially because the ROMs currently supported are all 5.0. So I flash a stock 5.0 firmware and tried a ROM - tethering didn't work. Tried another. Same deal. So fine - if i'm going to have no tethering capabilities, I'd rather have it with my old ROM and Nandroid backup.
Using Odin, I flashed the stock firmware that I've been flashing for a year now. It has worked every time in the past. But this time, Odin worked, and passed, and everything looked great - but when I booted up the phone, it starts to boot up, gives me the unlocked lock picture screen, then starts to load the Samsung image, stops mid-way through, and ... NOTHING. Screen goes blank and it hangs forever. I re-flashed with Odin a dozen times...nothing. Wiped data, wiped cache...nothing. I'm out of ideas and apparently Google hasn't seen this before, as far as I can find.
The image is where it stops loading the Samsung logo and then it just goes black.
Please. Help.
isellmidgets said:
So I was running a 4.4.x ROM and it was working great...then my company bought me a wifi-only tablet and that's pretty much useless for me without some tethering, and for whatever reason FoxFi didn't work with my ROM. I searched Google for days, tried mods and all sorts of Xposed stuff, but nothing worked. So I gave up and figured I'd try a new ROM. No reason not to switch to Lollipop, while I was at it - especially because the ROMs currently supported are all 5.0. So I flash a stock 5.0 firmware and tried a ROM - tethering didn't work. Tried another. Same deal. So fine - if i'm going to have no tethering capabilities, I'd rather have it with my old ROM and Nandroid backup.
Using Odin, I flashed the stock firmware that I've been flashing for a year now. It has worked every time in the past. But this time, Odin worked, and passed, and everything looked great - but when I booted up the phone, it starts to boot up, gives me the unlocked lock picture screen, then starts to load the Samsung image, stops mid-way through, and ... NOTHING. Screen goes blank and it hangs forever. I re-flashed with Odin a dozen times...nothing. Wiped data, wiped cache...nothing. I'm out of ideas and apparently Google hasn't seen this before, as far as I can find.
The image is where it stops loading the Samsung logo and then it just goes black.
Please. Help.
Click to expand...
Click to collapse
I'm not saying you file that you are using is messed up but I've been using the NCE downgrade file in this thread
http://forum.xda-developers.com/showthread.php?t=3076803. It's in the OP, step 5 in the notes section. Worth a shot.
Ok, first off, let me say what a idiot I am! I've been unlocked, s-off, and rooted since the day I got this phone and for the most part been running BadBoyz Rom. It had gotten a little bogged down and I thought I would go ahead and put a fresh flash of this ROM on the phone a couple days ago, I was tired and somehow erased everything on the phone and couldn't get ADB Sideload to copy anything onto it and I was out of time and a little panicky so I went to the the Sprint store and talked to a tech who didn't hassle me at all about it and he was able to load a stock ROM for me, in the process he also updated the Hboot of my phone (at a minimum). Currently it has hboot of 1.61, Radio 1.01.20.1225, DSP 3.51.202740718, OS 6.23.651.7. Phone is still unlocked and S-Off so I flashed twrp recovery and then tried to flash supersu. When I tried to flash the supersu I got a message about the cache? Could'nt mount cache or something like that but then it appeared to work? So, when I restarted phone and checked for Root, it tole me the same old binaries not loaded, this is a problem message? Started with Twrp 2.84 now I have 2.87 thinking that was the problem but it's not I don't think. Also tried a few different versions of supersu too. Help!!!
I read advice somewhere on the forum about just flashing a rom since you have twrp? I almost did that but twrp gave me a warning that this might not be compatible so I stopped. Could this work?