Related
Hi, I downloaded UPDATE-SuperSU-v1.25.zip and saved it to my SD card. Rebooted into PhilZ recovery and installed it successfully. Rebooted and root checker basic says i dont have root access. is there something I'm missing?
DJRepresent said:
Hi, I downloaded UPDATE-SuperSU-v1.25.zip and saved it to my SD card. Rebooted into PhilZ recovery and installed it successfully. Rebooted and root checker basic says i dont have root access. is there something I'm missing?
Click to expand...
Click to collapse
SuperSU v1.25 is pretty old. Have you tried v1.93?
I don't know the process under PhilZ at all. You didn't mention which image you are using. TouchWiz? One of the custom images?
Magamo said:
SuperSU v1.25 is pretty old. Have you tried v1.93?
I don't know the process under PhilZ at all. You didn't mention which image you are using. TouchWiz? One of the custom images?
Click to expand...
Click to collapse
Where can I download 1.93?
I'm actually using one of the Team Apexqtmo ROMs from earlier this week.
DJRepresent said:
Where can I download 1.93?
I'm actually using one of the Team Apexqtmo ROMs from earlier this week.
Click to expand...
Click to collapse
In fact, looks like it was just updated to v1.94
http://forum.xda-developers.com/showthread.php?t=1538053
There's a download link in the OP of this thread, (Marked as the CWM/TWRP/Mobile ODIN version)
Magamo said:
In fact, looks like it was just updated to v1.94
http://forum.xda-developers.com/showthread.php?t=1538053
There's a download link in the OP of this thread, (Marked as the CWM/TWRP/Mobile ODIN version)
Click to expand...
Click to collapse
Installed it, but it didn't work. I used an app called Root Checker Basic and it says, "Sorry! This device does not have proper root access."
Any other ideas? Here's my device's information:
CyanogenMod Version: cm-11-20140329-NIGHTLY
Android Vers: 4.4.2
Edit: Weird, the SuperSU app didn't give me a "Not Rooted" error upon opening up. Anyways, can I overclock my phone now? What app can I use?
DJRepresent said:
Installed it, but it didn't work. I used an app called Root Checker Basic and it says, "Sorry! This device does not have proper root access."
Any other ideas? Here's my device's information:
CyanogenMod Version: cm-11-20140329-NIGHTLY
Android Vers: 4.4.2
Edit: Weird, the SuperSU app didn't give me a "Not Rooted" error upon opening up. Anyways, can I overclock my phone now? What app can I use?
Click to expand...
Click to collapse
Make certain that you set up SuperSU properly, and allow it to respect CyanogenMod's root access settings.
Magamo said:
Make certain that you set up SuperSU properly, and allow it to respect CyanogenMod's root access settings.
Click to expand...
Click to collapse
Yeah, it's already set to "respect." Not sure about the other settings, though. How do I overclock this piece?
I have a bad feeling that installing the old version first may have screwed up your new installation. If your root apps still fail to get permission, try going through the supersu settings to clean up for reinstallation, and go through the installation procedure again. Overclocking as you think of it is a function of the kernel, and I do not know of any custom kernels for the apexqtmo that allow for it. Besides, overclocking will give you no real performance benefit on the apexqtmo, and in fact will cause instability, and overheating, which will cause the phone to trip over into thermal protection mode much faster, which means it will automatically throttle back. (Which is precisely why the stock CM and HypnoToad kernels do not allow for frequency scaling in an upward direction from stock CPU speeds
I'm no expert, but maybe something just messed up. try flashing a rom so you can just start over.
Magamo said:
I have a bad feeling that installing the old version first may have screwed up your new installation. If your root apps still fail to get permission, try going through the supersu settings to clean up for reinstallation, and go through the installation procedure again. Overclocking as you think of it is a function of the kernel, and I do not know of any custom kernels for the apexqtmo that allow for it. Besides, overclocking will give you no real performance benefit on the apexqtmo, and in fact will cause instability, and overheating, which will cause the phone to trip over into thermal protection mode much faster, which means it will automatically throttle back. (Which is precisely why the stock CM and HypnoToad kernels do not allow for frequency scaling in an upward direction from stock CPU speeds
Click to expand...
Click to collapse
OK, thanks, I'll avoid doing it then.
Evening. I had previous installed WeakSauce and SuperSU on my Verizon HTC One M8.
today, I applied S-off, and flashed ClockwordMod Recovery Unofficial.
I installed Root from inside CWM.
However, I still cannot apply host files in CWM. This suggests that I don't necessarily have full root, so perhaps I missed a vital step somewhere.
Little help? That's all i want is proper ad blocking. otherwise, this phone runs just fine with Nova Launcher
thanks,
I always throw my Awaway apk into system/app. Not sure if that actually does anything, but it seems to apply more often than not. I've always had issues with adaway sometimes not applying, so you are not alone.
Myk Robinson said:
Evening. I had previous installed WeakSauce and SuperSU on my Verizon HTC One M8.
today, I applied S-off, and flashed ClockwordMod Recovery Unofficial.
I installed Root from inside CWM.
However, I still cannot apply host files in CWM. This suggests that I don't necessarily have full root, so perhaps I missed a vital step somewhere.
Little help? That's all i want is proper ad blocking. otherwise, this phone runs just fine with Nova Launcher
thanks,
Click to expand...
Click to collapse
Unfortunately, while booted into Android, the stock kernal prevents system partition write access. You'll need to disable it.
EDIT: I stand corrected.
MultiDev said:
Unfortunately, while booted into Android, the stock kernal prevents system partition write access. You'll need to disable it.
Click to expand...
Click to collapse
This. The modified kernel it's being worked on still but I believe it can be found in development
Sent from my HTC6525LVW using Tapatalk
Clarification
MultiDev, if I am understanding, you mean just disable AdAway because it wont work yet until a custom kernel or kernel mod is installed?
Myk Robinson said:
Evening. I had previous installed WeakSauce and SuperSU on my Verizon HTC One M8.
today, I applied S-off, and flashed ClockwordMod Recovery Unofficial.
I installed Root from inside CWM.
However, I still cannot apply host files in CWM. This suggests that I don't necessarily have full root, so perhaps I missed a vital step somewhere.
Little help? That's all i want is proper ad blocking. otherwise, this phone runs just fine with Nova Launcher
thanks,
Click to expand...
Click to collapse
download and flash this in recovery: http://download.chainfire.eu/345/SuperSU/
then open it so it can update (use recovery method when asked to update)
then run adaway
Got it
kwkw480 said:
download and flash this in recovery: http://download.chainfire.eu/345/SuperSU/
then open it so it can update (use recovery method when asked to update)
then run adaway
Click to expand...
Click to collapse
Thanks, it successfully applied after that. Apparently I missed step one in some previous instructions where it said to flash the SuperSU binary.
Last question. I assume at this point, I can uninstall WeakSauce since we have permanent proper root?
I gotta say, this was pretty easy in Linux Mint 16....
Myk Robinson said:
Thanks, it successfully applied after that. Apparently I missed step one in some previous instructions where it said to flash the SuperSU binary.
Last question. I assume at this point, I can uninstall WeakSauce since we have permanent proper root?
I gotta say, this was pretty easy in Linux Mint 16....
Click to expand...
Click to collapse
Yes, uninstall weak sauce
MultiDev said:
Unfortunately, while booted into Android, the stock kernal prevents system partition write access. You'll need to disable it.
Click to expand...
Click to collapse
S-Off'd and rooted through flashable zip. Installed adaway as a system app, and it's running fine here. Nothing else changed or added.
M8, nuff said.
Thank you
Thank you all for replying. Nice to have such a fast response.
All this because I missed the first line of the instructions...
If Verizon customer service was as good as the fine folks on this forum....
mchief298 said:
S-Off'd and rooted through flashable zip. Installed adaway as a system app, and it's running fine here. Nothing else changed or added.
M8, nuff said.
Click to expand...
Click to collapse
Yeah, I was wrong about that. The system partition is writable after S-off.
mchief298 said:
S-Off'd and rooted through flashable zip. Installed adaway as a system app, and it's running fine here. Nothing else changed or added.
M8, nuff said.
Click to expand...
Click to collapse
I also have s-off, uninstalled weak sauce, then flashed through CWM supersu.zip for full root, reboot. Downloaded latest AdAway apk found here on xda forum. I then ran apk file from my download folder, hit install. Open AdAway, click on Download fiels and apply add blocking. Now it just gets stuck on Applying... with the circle going around and around for over 15 minutes straight now! Yes i gave root access when asked. Is this normal?
Nevermind. Closed app, then reopened and it did the download thing like normal. Now says successful and applied hosts sources: 4/4.
So i'm good to go now? Does this need reboot like prompted?
deeznuts said:
I also have s-off, uninstalled weak sauce, then flashed through CWM supersu.zip for full root, reboot. Downloaded latest AdAway apk found here on xda forum. I then ran apk file from my download folder, hit install. Open AdAway, click on Download fiels and apply add blocking. Now it just gets stuck on Applying... with the circle going around and around for over 15 minutes straight now! Yes i gave root access when asked. Is this normal?
Nevermind. Closed app, then reopened and it did the download thing like normal. Now says successful and applied hosts sources: 4/4.
So i'm good to go now? Does this need reboot like prompted?
Click to expand...
Click to collapse
You don't NEED to, but it is recommended.
M8, nuff said.
This is the one app causing me problems. Adfree works problem free, but AdAway likes to keep getting stuck on "Applying...". I've got it to succeed once or twice by force closing and re-trying, but it's not reliable. I'm S-off, CWM recovery, SuperSU, and the modded kernel with RW permissions. What gives? :?
EDIT: Even tried installing Adaway as system app, problem still persists...???
EDIT2: Finally got it working. Noticed in the OP in the xda thread that there is a modded version to fix problem. All good
deeznuts said:
I also have s-off, uninstalled weak sauce, then flashed through CWM supersu.zip for full root, reboot. Downloaded latest AdAway apk found here on xda forum. I then ran apk file from my download folder, hit install. Open AdAway, click on Download fiels and apply add blocking. Now it just gets stuck on Applying... with the circle going around and around for over 15 minutes straight now! Yes i gave root access when asked. Is this normal?
Nevermind. Closed app, then reopened and it did the download thing like normal. Now says successful and applied hosts sources: 4/4.
So i'm good to go now? Does this need reboot like prompted?
Click to expand...
Click to collapse
Don't need to reboot. I never have and it works fine.
123421342 said:
Don't need to reboot. I never have and it works fine.
Click to expand...
Click to collapse
Thank you
I had to install the unsecure boot image in order for AdAway to work properly. Otherwise it just hangs on applying host files.
From what I understand, just because you're s-off still doesn't mean you have full write access. The stock kernel has the write protection modules built in.
Flashing the unsecure boot image fixed all issues I was having and I'm pretty sure if you're still having problems, flashing that will help
-HTC One m8-
I'm not disputing whether or not s-off provides full write access. But, I was able to install AdAway with full functionality without installing the unsecure stock kernel. It takes a while to download all the data and install it though (maybe 5 minutes or so?). Then, I rebooted and it's working very well. No more ads!
i just rooted my 1+1 and it worked for a day... i used tutorial from xda so with toolbox
after i finished with rooting i flashed TWRP and things were going little strange there
so when i flash TWRP it worked when i reboot my phone and i went in TWRP flash some app reboot 1+1
after that i used titanium backup to restore (apps + data) from my old phone and it worked
today i wanted goto in titanium backup again, and it said that phone is not rooted, i thought i just need reinstall SU, and turn off device and boot it in recovery (volume down + power) and TWRP is not there anymore it is booting some other recovery, when i try install same file UpdateSU2.0.2 i cant, cant check sum or something like that
any ideas why do i lose my root privileges and how do i fix it?
Did you uncheck the 'update cm recovery' option in Developer Options before flashing TWRP? Some advice: ditch the toolkit, they're more trouble than they're worth, plus it's really easy to do things manually, and the experience is crucial for when something goes wrong in future.
Transmitted via Bacon
timmaaa said:
Did you uncheck the 'update cm recovery' option in Developer Options before flashing TWRP? Some advice: ditch the toolkit, they're more trouble than they're worth, plus it's really easy to do things manually, and the experience is crucial for when something goes wrong in future.
Transmitted via Bacon
Click to expand...
Click to collapse
no, i followed video from xda, thought it will be easier
also there are no drivers on that video so not sure did i use right one (can you link me one that works?)
ps is every SuperSU same or i need special for every device, since in that video guide is 2.0.2 versions and latest is 2.1.4
Night5talker said:
no, i followed video from xda, thought it will be easier
also there are no drivers on that video so not sure did i use right one (can you link me one that works?)
ps is every SuperSU same or i need special for every device, since in that video guide is 2.0.2 versions and latest is 2.1.4
Click to expand...
Click to collapse
Check my guide thread in my signature, there's a link to drivers in that. SuperSU isn't dependant on device, it's universal. There have been updates since that video was produced.
Transmitted via Bacon
Night5talker said:
no, i followed video from xda, thought it will be easier
also there are no drivers on that video so not sure did i use right one (can you link me one that works?)
ps is every SuperSU same or i need special for every device, since in that video guide is 2.0.2 versions and latest is 2.1.4
Click to expand...
Click to collapse
future reference the general section of all xda threads will have the best and safest ways to root stickied. Always check there and do as much reading as possible before trying anything
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Andyw2100 said:
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Click to expand...
Click to collapse
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Andyw2100 said:
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Click to expand...
Click to collapse
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
berndblb said:
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
Click to expand...
Click to collapse
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Andyw2100 said:
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it. Though you should already have this on your computer or SD Card.
Edit: I believe there is an even easier way, just have never done it/tried it so I don't wanna lie and act like I know what to do.
The Stig 04 said:
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it.
Click to expand...
Click to collapse
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Thanks to both of you.
I don't believe I removed any bloatware, so I think the OTA update should work.
How do I flash the stock recovery in fastboot?
Again, many thanks!
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
berndblb said:
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Click to expand...
Click to collapse
Sorry I thought fastboot and ADB was kinda that same thing seeing as it was refereed to as "fastboot/adb directory"? If not my bad! Also this is the method I always use to take OTA's and have never ever had a problem.
Andyw2100 said:
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
Click to expand...
Click to collapse
Put the recovery image into the same folder with your fastboot.exe
Open a command prompt from that folder (shift + right click > open cmd window here)
check connection with
Code:
fastboot devices
if successful
Code:
fastboot flash recovery <name of recovery>.img
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
mumbles202 said:
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
No. You will lose root after the ota so it doesn't matter but you can always get it back as long as you are S-OFF by flashing a custom recovery like TWRP and then flashing SuperSu.
Well, I have run into a snag right off the bat.
While the command "ADB Devices" sees the phone, "Fastboot Devices" does not.
Any ideas as to how to rectify this?
Thanks!
I did some googling, and this problem I solved on my own.
I had to use adb to get into fastboot USB mode or something with adb reboot bootloader, and then fastboot devices worked.
I'm now continuing on.
Well, so much for this being easy.
I believe I successfully flashed my stock recovery.
But apparently I no longer have the OTA update ready to install, as at some point I tried to run it again just to get TWRP up, and now it's not showing as available. And when I try to check for updates in Settings/Software update/Check new I get an error message that says Download Unsuccessful. We were not able to download this update.
For now I guess I'll wait and see if Verizon tries to send me the update again, or if it works if I check for it myself some other time. (Or if anyone here has any suggestions.)
Also, I still seem to have root access. I thought that I wouldn't, since I believe I have replaced TWRP with the stock recovery.
I'm also now getting a constant error message about Google Play Services having stopped. And my wi-fi doesn't seem to be connecting properly.
I'm really wondering just what the heck I've done.
Well, for anyone still following my saga...
Things are somewhat better, but not totally resolved.
I kept checking, and eventually I was able to download the OTA update to 4.4.4. I did, I updated, and all went smoothly. I then was able to flash TWRP and then install Super SU and I have root access again. So on that front, all is well.
The problems that remain, though, are that I still am having issues with Google Play Services quitting and my Wi Fi not connecting. Could these things be related somehow? I've tried clearing the cache and then actually all data from Google Play services, but that has not helped. I have deleted my networks, and then tried reconnecting to them, but that also has not helped. It shows my networks in range as "saved" or "disabled" but won't connect to any of them.
Any ideas for me?
Thanks.
And thanks for the help in getting the 4.4.4 OTA update. At least that worked!
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Andyw2100 said:
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Click to expand...
Click to collapse
Not sure why I stopped receiving notifications from your thread. But at least you got your phone in working order! lol
Thanks to some questions and awnsers I was able to create the
rooted boot.img for our HTC Bolt devices.
This was tested on the HTC Bolt Software 1.17.651.11 Android N 7
How To: (downloads at bottom of page)
Connect Device to computer
Insure that usb debugging is on as well as OEM unlock is checked.
The device must be Boot-loader unlocked to do this!
place both the patched_boot.img and the magisk_cache.img in the same directory your fastboot files are setup at ( c:/android/sdk/fastboot or wherever you have it)
Boot the phone into Download mode. ( Power + VOL down)
Open up terminal on the computer and run both these commands:
fastboot devices
fastboot flash boot patched_boot.img
fastboot flash cache magisk_cache.img
followed by fastboot reboot
you'll need to head over to :
http://forum.xda-developers.com/htc-10/development/root-magisk-autoroot-magisk-phhs-t3507505
Grab the manager.apk and the super user apk to complete the setup.
Give these guys a thanks also for getting this going, gonna build a rom with debloat next and see if the twrp will flash it with this boot.img behind it.
shall see
Thanks to:
@OMJ Everything!
@topjohnwu magisk
@Captain_Throwback -twrp,root
@Chainfire - root
Downloads
Patched boot.img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528674
Cache img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528673
***********DevDigitel Custom Images************
Secure Boot Img: https://www.androidfilehost.com/?fid=457095661767122602
Unsecure Boot Img: https://www.androidfilehost.com/?fid=745425885120693359
Flashable ZIPS:
SuperSU:
https://www.androidfilehost.com/?fid=673368273298916495
Radio Fix Zip/FP Scanner Fix : https://www.androidfilehost.com/?fid=673368273298916521
Device will bootloop once, and when done will install su. Please be patient
Nice!
suprised that it went so smoothly, su being systemless is a little buggy here and there with Android N, but otherwise i was able to navigate the internals, remove the bloat, make some build prop edits and theyve stuck. so far so good.
Went ahead and tried to use flashify and flash the twrp image from other post. Flashed and was able to make a backup to sd only. I didn't flash or try to restore it yet but I did have to relock and restore 3x with the stock ruu after removing too much system and trying to flash xposed
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
S off
urbster1 said:
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
Click to expand...
Click to collapse
Not sure.. Probably gonna be some time with Android N.
I was able to change carrier types in Ui.
Got vzw 1x 3g 4G icons
Hot-spot mod
And a few other things working.
No radios to flash.. No kernels and I don't dev kernels.
So I don't need s-off really.. It's more so just having to re-lock
To go back to stock.
I just ordered a Bolt, can't wait to play
Screen shots
OMJ said:
I just ordered a Bolt, can't wait to play
Click to expand...
Click to collapse
Yey can't wait! It didn't want to be the only one working
On it!
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
Use the other supported devices section at bottom.
Just follow the steps on htc dev.
Save the unlock.bin file HTC will email you. You need it Every time you need to lock/unlock. Without s-off (removing the 2nd lock that protects the radios)
* the phone has to be re-locked to be restored with the stock htc software "ruu's"
Htc ruu is a 1 click style restore program...similar to odin that Will run on the PC and restore phone to stock.
It also comes in a update.zip format that can be flashed with the stock Signed recovery only via sd card slot.
Twrp is currently working on bolt / but has limitations because Its not 100%
More screenshots
Random stuff that can be unlocked hidden in the phone.
urbster1 said:
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
Click to expand...
Click to collapse
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
OMJ said:
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
Click to expand...
Click to collapse
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
jcase said:
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
Click to expand...
Click to collapse
@jcase let me know if you need any more partitions, or anything else dumped... Worse case I can send you mine.
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Team DevDigitel said:
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Click to expand...
Click to collapse
I actually just switched to this method after s-off, due to safetynet failing after detecting a unlocked bootloader...magisk can hide the detection
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Team DevDigitel said:
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Click to expand...
Click to collapse
yep...AP is my only goal
there's a kernel patch to bypass detection but I don't know squat about kernel modding