Hello, so I have a question about my Virgin Mobile HTC DESIRE 510. I rooted it awhile back with TWRP and I went to advanced wipe where my Recovery Rom stuff was and when I went to reboot it, it said NO OS INSTALLED so I looked around on here and downloaded a stock Rom for it and it worked but it will not let me install system updates it just takes me straight to TWRP and that's all. I was wondering if there was a way to just unroot it and install updates?
Related
hey guys i just gotta a new software update on my htc one and i just realized that you cannot update your device if rooted because each time i try and install the new update it just boots into recovery which im not sure if thats suppose to happen or not. Anyways i tried this app called voodoo ota rootkeeper but each time i push protect root it just restarts my phone instead of giving me the option to temporarily un-root. Is there any other way how i can update my phone Thanks.
i am kinda confused what you are trying to achieve, you are rooted on a stock rom, but you want to update the ota, is that correct? my guess is that you have changed some system or other files (or changed kernel, or put a custom recovery) if anything of the previous is true, you'd have to go back to complete stock and then install the ota... or just get a custom rom there are 4.2 out there you know.
When you unlock the bootloader, some HTC apps are automatically deleted. If you're trying to install an official OTA, it will check for those apps and abort the install if they're not there. The only way to install it will be to get those apps back, or restore from an NAND backup that has them.
Or, alternatively, use one of the custom ROMs from either these forums or the HTC One International forums. They're way better anyway, and are running on Android 4.2.2.
yeah all i wanna do is upgrade to 4.2 so i gusse the best thing to do is just install a custom rom then and sorry sorta new to all this stuff
If all you want is 4.2 then you would need to flash either trickdroid or arhd latest version, I don't think 4.2 is even officially released yet as an ota anyway
Sent from my HTC One using xda app-developers app
alright thanks. but what is OTA exactly I just downloaded this app (voodoo OTA rootkeeper) from the google play store which was suppose to let me temporarily un-root my phone so i could update to the new software
Hi,
I own a Moto X DE for few days. It runs Kit Kat, and is unlocked and rooted with TWRP. Today, I've got a notification about an OS update. But when I try to update my system, the phone reboots on the TWRP menu, and no way to update.
Any idea about this?
Thanks.
I have a the T Mobile (Same as Dev). Had it rooted and bootloader unlocked. I didn't really care for saving data tbh. So what I did was return to stock.
Already had the 4.4 in my fastboot folder. So I booted into recovery and wiped everything.
Then went back to download mode and fastbooted the T-Mobile 4.4 version. Ran phone setup, check for update and installed. Took about 10 minutes max.
Though of course this is one way out of a few. The stickies in this section have the various ways. Find one which better suits you.
Do note you should not take OTA with root and a custom recovery
Sent from my XT1053 using Tapatalk
Thanks, should have read a bit before asking. Sorry, and thanks again for the help.
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.
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?
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