Ok so I got my XT1080 few days or whatever and it had the first 4.4 ota, you know the one with the transparent status bar but still that blue jelly bean hue on the status bar etc.... So not thinking of it I just decided to see if there was another ota and there was so I got it and now I want root.... Here's what I want to know please.. Without telling me to go read 30 pages on another post can someone just tell me
Is there root for me
If so do I have to have boot loader unlocked, I've had phones with locked boot loaders and still flashed Roms
Can I flash Roms on this device with a locked boot loader via twrp
I mainly read that you have to downgrade to a certain version use jcase method it something? I got lost in that bounty post..
Yes there is!
Note
This little guide assumes you know how to install adb and use basic command-line tools.
First, flash your phone back to a older version with rsdlite. (instructions: http://forum.xda-developers.com/showpost.php?p=53141176&postcount=6)
Second, use jcase's pie exploit. (instructions: http://forum.xda-developers.com/mot...-x-pie-motorola-devices-t2771623/post53128101)
Third, use motowpnomo, but executing "adb shell /data/local/atvc/root.sh" in a separate cmd window every time the device reboots (instructions for motowpnomo: http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113 as for the command, just spam it till it goes through)
Forth, install your superuser application (and safestrap if you want custom rom functionality)
Fifth, profit!
Note that you do have read/write access to system and root access, but still a locked bootloader.
bluebloomers said:
Yes there is!
Note
This little guide assumes you know how to install adb and use basic command-line tools.
First, flash your phone back to a older version with rsdlite. (instructions: http://forum.xda-developers.com/showpost.php?p=53141176&postcount=6)
Second, use jcase's pie exploit. (instructions: http://forum.xda-developers.com/mot...-x-pie-motorola-devices-t2771623/post53128101)
Third, use motowpnomo, but executing "adb shell /data/local/atvc/root.sh" in a separate cmd window every time the device reboots (instructions for motowpnomo: http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113 as for the command, just spam it till it goes through)
Forth, install your superuser application (and safestrap if you want custom rom functionality)
Fifth, profit!
Note that you do have read/write access to system and root access, but still a locked bootloader.
Click to expand...
Click to collapse
Wow I love you!
alright my inner noob is going crazy. i see a zillion threads on how you need to roll back to 4.2.2 rom. my question is do i need to roll back if im on 4.4 stock?
i must have downloaded every tool and rom needed by this point. a step by step would be awesome. lots of tutorials available but im seeing they are mostly off of the x which i do understand is practically a sibling to the ultra and maxx.
any info or step by step would be awesome. lastly if i dont need to roll back to an earlier version that would be super. thanks!!!
kdm212 said:
alright my inner noob is going crazy. i see a zillion threads on how you need to roll back to 4.2.2 rom. my question is do i need to roll back if im on 4.4 stock?
i must have downloaded every tool and rom needed by this point. a step by step would be awesome. lots of tutorials available but im seeing they are mostly off of the x which i do understand is practically a sibling to the ultra and maxx.
any info or step by step would be awesome. lastly if i dont need to roll back to an earlier version that would be super. thanks!!!
Click to expand...
Click to collapse
What build of 4.4 are you one? 19.5.3 or 19.6.3?
Topsnake said:
What build of 4.4 are you one? 19.5.3 or 19.6.3?
Click to expand...
Click to collapse
19.5.3 it should be made known i plan on using the phone with t-mobile and the outside hope that i can have a fully functional phone with lte...
Well that makes things more difficult, TMobile has an LTE to Voice/text handoff issue present in 19.5.3 and 19.6.3. I hear its corrected in 4.4.4. Do you have an unlocked boot loader?
Topsnake said:
Well that makes things more difficult, TMobile has an LTE to Voice/text handoff issue present in 19.5.3 and 19.6.3. I hear its corrected in 4.4.4. Do you have an unlocked boot loader?
Click to expand...
Click to collapse
Boot loader is not unlocked. However if I do the update I won't be able to get root. Correct?
Correct. You are on the correct version to begin root. With Jcase's pie and run wp off. You can keep that when you update to 19.6.3 however when you update to 4.4.4 youll lose root (unless you preserve it) but you definitely lose wp off
Topsnake said:
Correct. You are on the correct version to begin root. With Jcase's pie and run wp off. You can keep that when you update to 19.6.3 however when you update to 4.4.4 youll lose root (unless you preserve it) but you definitely lose wp off
Click to expand...
Click to collapse
Alright but I won't be able to take advantage of lte I imagine. Right? Can you point me the right direction with a link? So am I correct with root, recovery, rom? Or am I missing some stuff in there? I appreciate the responses!
kdm212 said:
Alright but I won't be able to take advantage of lte I imagine. Right? Can you point me the right direction with a link? So am I correct with root, recovery, rom? Or am I missing some stuff in there? I appreciate the responses!
Click to expand...
Click to collapse
Link to what specifically? You dont need to downgrade on your version
Topsnake said:
Link to what specifically? You dont need to downgrade on your version
Click to expand...
Click to collapse
Ok to which version? After the downgrade root, recovery, rom? Unlock the boot loader in any of those steps?
kdm212 said:
Ok to which version? After the downgrade root, recovery, rom? Unlock the boot loader in any of those steps?
Click to expand...
Click to collapse
You don't need to downgrade of you are on 19.5.3. You just need to run motopie then motowpnomo.
You can't unlock the bootloader unless you have a code or a developer edition.
No recovery or rom needed.
Root-wp off- Root survival mode in supersu- update to 19.6.3 then stay there unless you want to update to 4.4.4 to address the tmobile lte issue
Then the sequence would be Root-wp off- Supersu survival-update to 19.6.3- supersu survival-update 4.4.4
Topsnake said:
You don't need to downgrade of you are on 19.5.3. You just need to run motopie then motowpnomo.
You can't unlock the bootloader unless you have a code or a developer edition.
No recovery or rom needed.
Root-wp off- Root survival mode in supersu- update to 19.6.3 then stay there unless you want to update to 4.4.4 to address the tmobile lte issue
Then the sequence would be Root-wp off- Supersu survival-update to 19.6.3- supersu survival-update 4.4.4
Click to expand...
Click to collapse
Alright cool, I will start hunting around for all of these tools and threads. Thank you sir!
kdm212 said:
Alright cool, I will start hunting around for all of these tools and threads. Thank you sir!
Click to expand...
Click to collapse
No problem
any tips on keeping root after reboots? also, is there a major difference from 19.5.3 to 19.6.3?
kdm212 said:
any tips on keeping root after reboots? also, is there a major difference from 19.5.3 to 19.6.3?
Click to expand...
Click to collapse
Run motowpnomo to gain wp off then safe strap can install su to system
Ok my buddy has a regular Droid Maxx and after seeing my Droid Maxx DE with Xposed Framework he wants to root his. Looking into it is a bit more work than mine. I have never used adb so I was hoping someone could help me out with this.
TheDroidURLookinFor said:
Ok my buddy has a regular Droid Maxx and after seeing my Droid Maxx DE with Xposed Framework he wants to root his. Looking into it is a bit more work than mine. I have never used adb so I was hoping someone could help me out with this.
Click to expand...
Click to collapse
What version is it on?
Topsnake said:
What version is it on?
Click to expand...
Click to collapse
19.5.3
Related
XT1080M Dev Ed currently running 4.4 / 19.6.3 rooted with native tether exploit.
If anyone is willing to spare a few minutes and point me in the right direction, I want to be rooted with native tether exploit on 4.4.4 ideally without having to backup then restore all my data and apps, however, I'm willing to do that if it gets me the most stable setup to start over from scratch instead of some patch upgrade path.
Any help greatly appreciated -- I have been searching threads almost three hours but am not quite sure the best path and I am seeing conflicting info or am not understanding some info correclty.
Thanks for your time..!
reyxlp said:
XT1080M Dev Ed currently running 4.4 / 19.6.3 rooted with native tether exploit.
If anyone is willing to spare a few minutes and point me in the right direction, I want to be rooted with native tether exploit on 4.4.4 ideally without having to backup then restore all my data and apps, however, I'm willing to do that if it gets me the most stable setup to start over from scratch instead of some patch upgrade path.
Any help greatly appreciated -- I have been searching threads almost three hours but am not quite sure the best path and I am seeing conflicting info or am not understanding some info correclty.
Thanks for your time..!
Click to expand...
Click to collapse
The smartest thing would be to wait for this: http://forum.xda-developers.com/droid-ultra/general/request-help-exploit-moto-bl-bootloader-t2829042
Then you can update to ANY android version with no fear of losing root.
samwathegreat said:
The smartest thing would be to wait for this: http://forum.xda-developers.com/droid-ultra/general/request-help-exploit-moto-bl-bootloader-t2829042
Then you can update to ANY android version with no fear of losing root.
Click to expand...
Click to collapse
Thanks for the quick reply!
I'm on a Dev Ed with unlocked BL so I thought I didn't have to worry about losing root or not being able to regain it if I lost it?
Or is there no root method available yet for 4.4.4, even for unlocked BL Dev Ed phones?
reyxlp said:
Thanks for the quick reply!
I'm on a Dev Ed with unlocked BL so I thought I didn't have to worry about losing root or not being able to regain it if I lost it?
Or is there no root method available yet for 4.4.4, even for unlocked BL Dev Ed phones?
Click to expand...
Click to collapse
AH! Ok didn't realize you were on an unlocked DEV edition. This is EASY!
Download the entire 4.4.4 SBF for your specific device.
Two ways of doing it:
1. RSD Lite: Extract the SBF, find the XML file. Edit it with Notepad. Find the line "getvar max-download-size" and erase that entire line. Find the line "erase userdata" and erase that entire line. Flash the SBF with RSD Lite (DON'T SELECT THE ZIP! Select the XML file you modified).
You will be updated to 4.4.4 without losing your data/apps.
2. Manual method: Extract the SBF and follow the instructions for manual flashing. SKIP THE COMMAND "fastboot erase userdata".
You will be updated to 4.4.4 without losing your data/apps.
Easy peasy! Full instructions are here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Also there are links to all tools you will need and the firmware files themselves. **BE SURE TO DELETE / SKIP THE ERASE USERDATA COMMAND - otherwise EVERYTHING will be erased. This is NOT included in the linked guide - the guide assumes you WANT to erase everything**
Afterwards, you can re-flash TWRP and re-root. This WILL cause you to lose root (because su is stored in /system) and you will also need to reinstall Xposed if you are using that. But all apps / settings / files will be intact.
samwathegreat said:
AH! Ok didn't realize you were on an unlocked DEV edition. This is EASY!
Download the entire 4.4.4 SBF for your carrier.
Two ways of doing it:
1. RSD Lite: Extract the SBF, find the XML file. Edit it with Notepad. Find the line "getvar max-download-size" and erase that entire line. Find the line "erase userdata" and erase that entire line. Flash the SBF with RSD Lite (DON'T SELECT THE ZIP! Select the XML file you modified).
You will be updated to 4.4.4 without losing your data/apps.
2. Manual method: Extract the SBF and follow the instructions for manual flashing. SKIP THE COMMAND "fastboot erase userdata".
You will be updated to 4.4.4 without losing your data/apps.
Easy peasy! Full instructions are here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Also there are links to all tools you will need and the firmware files themselves. **BE SURE TO DELETE / SKIP THE ERASE USERDATA COMMAND - otherwise EVERYTHING will be erased. This is NOT included in the linked guide - the guide assumes you WANT to erase everything**
Afterwards, you can re-flash TWRP and re-root. This WILL cause you to lose root (because su is stored in /system) and you will also need to reinstall Xposed if you are using that. But all apps / settings / files will be intact.
Click to expand...
Click to collapse
Do I need to restore to stock before doing any of this?
Also:
I currently have the native tether hack going (19.6.3 version) and I don't want to lose it. Do you know if it will survive either of these processes? Or do you know if there a native tether hack already available for 4.4.4 that I can fall back on in case upgrading kills my existing hack?
Thanks again for the help...
reyxlp said:
Do I need to restore to stock before doing any of this?
Also:
I currently have the native tether hack going (19.6.3 version) and I don't want to lose it. Do you know if it will survive either of these processes? Or do you know if there a native tether hack already available for 4.4.4 that I can fall back on in case upgrading kills my existing hack?
Thanks again for the help...
Click to expand...
Click to collapse
This WILL return you to stock -- stock 4.4.4. No reason to flash 4.4 first....this will take you STRAIGHT to 4.4.4.
Yes, the native tether will be lost. You can use THIS instead: http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
It works like a dream to enable native tether and bypass the entitlement. Just install it afterwards (after you have flashed twrp and re-rooted), and it will enable native tether for you. Click the "apply on reboot" and it will enable tether after every reboot - no system modifications made
samwathegreat said:
This WILL return you to stock -- stock 4.4.4. No reason to flash 4.4 first....this will take you STRAIGHT to 4.4.4.
Yes, the native tether will be lost. You can use THIS instead: http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
It works like a dream to enable native tether and bypass the entitlement. Just install it afterwards (after you have flashed twrp and re-rooted), and it will enable native tether for you. Click the "apply on reboot" and it will enable tether after every reboot - no system modifications made
Click to expand...
Click to collapse
Ah, yes, sorry I missed that, re: returning to stock.
Thanks for all the help!
reyxlp said:
Ah, yes, sorry I missed that, re: returning to stock.
Thanks for all the help!
Click to expand...
Click to collapse
Seeing as you have a XT1080 make sure you flash the 1080 software. Not the Moto X FXZ. Looks like @samwathegreat linked to moto X thread.
Next run my port, guaranteed you'll like it better and comes pre-built with hotspot. Also comes with google dialer/gmail email client/T-Mobile fix etc. All the goodies from the X ported the the Maxx. Link below. Also both the stock XT1080 4.4.4
If you decide to run my port, you dont need to update to 4.4.4 first. You can simply flash my port and be on 4.4.4. Doing it this way will enable you to downgrade to 4.4 19.6.3 if you later choose. If you update to 4.4.4 21.11.21, you cannot downgrade later.
My port below.
http://forum.xda-developers.com/showthread.php?t=2828366
If you choose to use stock XT1080 4.4.4 you can use the tether bypass linked below as well. Same endpoint as the one samwa linked, just doesnt need to be reset each boot and is now twrp flashable.
Link
http://forum.xda-developers.com/showthread.php?t=2811810
Topsnake said:
Seeing as you have a XT1080 make sure you flash the 1080 software. Not the Moto X FXZ. Looks like @samwathegreat linked to moto X thread.
Click to expand...
Click to collapse
I linked him to the guide in the Moto X thread because it is much more concise than anything in the Ultra section. The instructions are identical. In my second reply, I stated to use the correct 4.4.4 firmware for *his device*.
Granted....in hindsight (considering some of the "spoon-feed me" attitudes we see all too often on XDA), I probably should have been more specific. The point is though, that the procedure is identical....
samwathegreat said:
I linked him to the guide in the Moto X thread because it is much more concise than anything in the Ultra section. The instructions are identical. In my second reply, I stated to use the correct 4.4.4 firmware for *his device*.
Granted....in hindsight (considering some of the "spoon-feed me" attitudes we see all too often on XDA), I probably should have been more specific. The point is though, that the procedure is identical....
Click to expand...
Click to collapse
Agreed. You know we can no longer assume anything here.
samwathegreat said:
This WILL return you to stock -- stock 4.4.4. No reason to flash 4.4 first....this will take you STRAIGHT to 4.4.4.
Yes, the native tether will be lost. You can use THIS instead: http://forum.xda-developers.com/moto-x/themes-apps/app-hotspot-entitlement-bypass-v1-1-5-9-t2705152
It works like a dream to enable native tether and bypass the entitlement. Just install it afterwards (after you have flashed twrp and re-rooted), and it will enable native tether for you. Click the "apply on reboot" and it will enable tether after every reboot - no system modifications made
Click to expand...
Click to collapse
I am on a Droid Maxx (Not DE) running 4.4.4 on 21.11.21. Locked bootloader, but Rooted ever since JB 4.2.2, followed by SlapMyMoto/MotoWpNoMo and SuperSU survival....I have always updated with OTAs, ever since 4.2........ 21.11.21 turned Wp back on, so I have been using the referenced entitlement bypass v1.2 for tether.
Will the entitlement bypass app continue to work if I take the 23.3.24 OTA
@iKrYpToNiTe -any thoughts?
Thanks in advance for any help. Greatly appreciated.
Donated to @jcase ( sent as friend instead of donate)
Donated to @Topsnake ( pp Confirmation: 98U78263NX3684739)
I think you will lose root if you proceed with the latest OTA.
Sounds like you might be one of those for whom the Sunshine app will work.
Worth a try, you'll be unlocked and never have to worry about losing root again.
Sent from my XT1080 using XDA Free mobile app
If your on 4.2.2 just unlock with sunshine. Best 25 bucks you will ever spend.
sent from "my kungfu is stronger then yours" XT1080
bigv5150 said:
If your on 4.2.2 just unlock with sunshine. Best 25 bucks you will ever spend.
sent from "my kungfu is stronger then yours" XT1080
Click to expand...
Click to collapse
I second that 100%, I love my Maxx now.
kenryan said:
Sounds like you might be one of those for whom the Sunshine app will work.
Worth a try, you'll be unlocked and never have to worry about losing root again.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the idea......and Sunshine worked on my Droid Maxx running 4.4.4 on 21.11.21.
So I went with sunshine, and BINGO! worked on Maxx.
After unfreezing bloat, and undoing previous mods to the /system/ folder, I then took the 23.3.24 OTA and all is good. Entitlement Bypass v1.2, still works (Now that I have an unlocked BL and write protection is back off, there are other options for tether, but I love the fact that entitlement bypass doesnt change system folder, making it that much easier to revert to stock and take OTAs).
From what I can see, even if I still had the locked BL and WP on, taking the 23.3.24 OTA would have still been ok, by keeping root with SuperSU survival, and bypass entitlement still would work. The update went flawless. But like I said, I wanted more options if this had not been the case, so thats why I "sunshined".
-Droide Maxx 4.4.4, 23.3.24 with Root and Unlocked BL......Rooted (RockMyMoto done back on 12.15.1.5, SlapMyMoto on 19.5.3), Unlocked BL (Sunshine ran on 21.11.21), Stock ROM & Stock Recovery
sunshine and 24.3.7
have you taken 24.3.7 OTA without issue? I'm same -- xt1080 after sunshine and counting on entitlement bypass. can you confirm no problems after taking OTA?
kdavidb said:
have you taken 24.3.7 OTA without issue? I'm same -- xt1080 after sunshine and counting on entitlement bypass. can you confirm no problems after taking OTA?
Click to expand...
Click to collapse
I did and entitlement bypass works fine.
sent from "my kungfu is stronger then yours" XT1080
bigv5150 said:
I did and entitlement bypass works fine.
sent from "my kungfu is stronger then yours" XT1080
Click to expand...
Click to collapse
thanks much. I had the same result -- no changes to root or bootloader.
anyone know of a convenient "safe to remove" bloatware list?
So I have a new shield tablet on the way, in the mail. I'm not sure yet if it will be sent to me on Lollipop or KitKat. It is the 32 gig, LTE variant.
If it is on KitKat, is it best to root it on KK and stay there or should I take the OTA up to Lollipop and then root it from there? Is the best bet to root and stay stock or should I look at some of the roms available? Have people found that the tablet handles emulators well like Reicast, FPSE and more?
If you want root your best bet is to unlock the bootloader. This can be done on kitkat or lollipop.
Sent from my SHIELD Tablet using Tapatalk
T-Keith said:
If you want root your best bet is to unlock the bootloader. This can be done on kitkat or lollipop.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
Is it done via the typical fastboot and then oem unlock?
Edit- http://forum.xda-developers.com/showthread.php?t=2399737
Yup. Typical bootloader unlock. Is there a preferred recovery most people like for the tablet? I know for one of my old phones (Rezound), you could use a few but devs preferred usually 1 out of the many. CWM is the way to go for us?
Lollipop root is independent of having root on KitKat or not. As of right now the only way to root is to unlock the bootloader, flash a temporary/permanent custom recovery and then flash the SuperSU. Being that the bootloader wipes the device I recommend doing it before you dig too into the tablet and load it up. Follow this guide and you should be golden ponyboy http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
Or if the tablet already has Lollipop on it then follow these instructions. http://forum.xda-developers.com/showpost.php?p=56888108&postcount=23
The LTE version will come with kk. They haven't pushed lollipop to the LTE version yet as it's pending carrier certification. I rooted and flashed recovery all without unlocking the bootloader. I followed the lollipop root instructions in the dev section. First you root kk, install recovery, flash the ota zip, flash the su zip, flash the rooted boot image then reflash custom recovery if you want. Im now running lollipop rooted with clockwork installed and my bootloader is still locked(follow the locked bootloader root instructions in that thread)
http://forum.xda-developers.com/showthread.php?t=2945044
[ROOT] Root for SHIELD Tablet 2.0 (Lollipop)
graffixnyc said:
The LTE version will come with kk. They haven't pushed lollipop to the LTE version yet as it's pending carrier certification. I rooted and flashed recovery all without unlocking the bootloader. I followed the lollipop root instructions in the dev section. First you root kk, install recovery, flash the ota zip, flash the su zip, flash the rooted boot image then reflash custom recovery if you want. Im now running lollipop rooted with clockwork installed and my bootloader is still locked(follow the locked bootloader root instructions in that thread)
http://forum.xda-developers.com/showthread.php?t=2945044
[ROOT] Root for SHIELD Tablet 2.0 (Lollipop)
Click to expand...
Click to collapse
So you took yours up to Lollipop manually because the LTE version doesn't have the carrier approval yet?
Does lollipop introduce any headaches or anything to be aware of in comparison to KK? The tablet did get cleared for Grid correct?
NapalmDawn said:
So you took yours up to Lollipop manually because the LTE version doesn't have the carrier approval yet?
Does lollipop introduce any headaches or anything to be aware of in comparison to KK? The tablet did get cleared for Grid correct?
Click to expand...
Click to collapse
Yeah I flashed it manually. Honesty, I can't tell you if it brings problems compared to KK.. haha I got the tablet yesterday and as soon as I powered it on I started updating and rooing it so I was only in KK for a few minutes so the only experience I really have with the tablet is on lollipop
NapalmDawn said:
Is it done via the typical fastboot and then oem unlock?
Edit- http://forum.xda-developers.com/showthread.php?t=2399737
Yup. Typical bootloader unlock. Is there a preferred recovery most people like for the tablet? I know for one of my old phones (Rezound), you could use a few but devs preferred usually 1 out of the many. CWM is the way to go for us?
Click to expand...
Click to collapse
I really prefer Philz. I love TWRP but I don't think there's a working TWRP recovery for the Shield tablet yet.
graffixnyc said:
Yeah I flashed it manually. Honesty, I can't tell you if it brings problems compared to KK.. haha I got the tablet yesterday and as soon as I powered it on I started updating and rooing it so I was only in KK for a few minutes so the only experience I really have with the tablet is on lollipop
Click to expand...
Click to collapse
I will plan to do the same. I'm going to unlock/root it before I do any work on it so I don't lose anything during the wipes. Does the tablet handle emulators well like FPS and Reicast? My guess is their performance would be phenomenal on this device.
Just of the lollipop update not too major a problem, battery life seems a little bit worse for me....but I have a question what is that star icon beside my WiFi bar? Idk how to take a screenshot sorry I just got the tablet
butch87402 said:
Just of the lollipop update not too major a problem, battery life seems a little bit worse for me....but I have a question what is that star icon beside my WiFi bar? Idk how to take a screenshot sorry I just got the tablet
Click to expand...
Click to collapse
Star means that you put the tablet into Priority mode - only notifications that you deem as priority will alert you.
Hi everyone,
I am new to android mods. I just bought a used vzw M8 running 4.4.4. I unlocked and got S off using sunshine. Rooted with WS2, and verified. Installed SuperSU. Stock otherwise. I have installed the SDK on my laptop. I can't get any devices to show up when i use the adb devices command.
I am trying to figure out how to disable the OTA for Lollipop. Does anyone know if the OTA will re-lock or bypass my root? Can you help me disable if it is an issue?
Eventually, I'd like to go to a different (cleaned up) ROM and 5.X, but i need to make sure the evil red monster doesn't mess up my work first. I have spent several hours searching the forums, and have made some progress. If there are any detailed posts to point me to, I'd appreciate any and all help.
Thank you,
Dustin
Did you install the HTC drivers? If not install HTC sync manager (I think that's the name) and it'll install them for u then u can uninstall HTC sync manager and you should get adb to recognize your device. Ota will not relock your device. It will take off root tho. But you can just flash custom recovery and flash su in there. I'd suggest since your s off to flash dottats s off 5.0.1 ruu over in the development section once you get adb working. It is also pre rooted and will get up and running on lollipop.
Save the Manuals!!!
dustinoob said:
Hi everyone,
I am new to android mods. I just bought a used vzw M8 running 4.4.4. I unlocked and got S off using sunshine. Rooted with WS2, and verified. Installed SuperSU. Stock otherwise. I have installed the SDK on my laptop. I can't get any devices to show up when i use the adb devices command.
I am trying to figure out how to disable the OTA for Lollipop. Does anyone know if the OTA will re-lock or bypass my root? Can you help me disable if it is an issue?
Eventually, I'd like to go to a different (cleaned up) ROM and 5.X, but i need to make sure the evil red monster doesn't mess up my work first. I have spent several hours searching the forums, and have made some progress. If there are any detailed posts to point me to, I'd appreciate any and all help.
Thank you,
Dustin
Click to expand...
Click to collapse
Check this thread out for blocking the OTA http://forum.xda-developers.com/verizon-htc-one-m8/help/block-ota-updates-t2871520 It is also my understanding that just being rooted will cause the OTA to fail. I may be wrong about that, however.
MotoTurbo said:
Did you install the HTC drivers? If not install HTC sync manager (I think that's the name) and it'll install them for u then u can uninstall HTC sync manager and you should get adb to recognize your device. Ota will not relock your device. It will take off root tho. But you can just flash custom recovery and flash su in there. I'd suggest since your s off to flash dottats s off 5.0.1 ruu over in the development section once you get adb working. It is also pre rooted and will get up and running on lollipop.
Save the Manuals!!!
Click to expand...
Click to collapse
I did install the drivers exactly the way you suggest. My computer recognizes the phone as a drive. I just can't get it to show up on ADB. Thank you for the suggestion on the ruu. I may just let the OTA come though today to get rid of the message. Then, run the ruu when I figure this out more.
BladeRunner said:
Check this thread out for blocking the OTA http://forum.xda-developers.com/verizon-htc-one-m8/help/block-ota-updates-t2871520 It is also my understanding that just being rooted will cause the OTA to fail. I may be wrong about that, however.
Click to expand...
Click to collapse
Thank you. I've been looking at that post mainly. Hopefully I'll figure out what they're talking about once I get into the phone on ADB.
dustinoob said:
Thank you. I've been looking at that post mainly. Hopefully I'll figure out what they're talking about once I get into the phone on ADB.
Click to expand...
Click to collapse
Maybe try dottats HTC fastboot exe. Its in the main ruu thread in general section. Its in 2nd or 3rd post I believe And check adb there, might be the sdk
Save the Manuals!!!
---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------
Here's the link to post
http://forum.xda-developers.com/showthread.php?p=56890497
Save the Manuals!!!
Makes me want to brick mine too sometimes.
dustinoob said:
Thank you. I've been looking at that post mainly. Hopefully I'll figure out what they're talking about once I get into the phone on ADB.
Click to expand...
Click to collapse
Somethings just can't be explained. Check this out. I have to use my 6 year old laptop with AMD Phenom II x4 because my desktop Intel i5-3570 cant send sh1t to my phone. It's always something. After trying to figure it out for hours, I gave into the PC Gods. I'm sure Dottat could solve it in 2 mins or less.
I only post to let you know others share your frustration. Honestly, if I didn't have an unlimited data plan, I might not even bother with modding anymore. I will follow your post, waiting for a solution too.
dustinoob said:
Thank you. I've been looking at that post mainly. Hopefully I'll figure out what they're talking about once I get into the phone on ADB.
Click to expand...
Click to collapse
To use adb/htc_fastboot with the copy i have on the thread you were already linked all you need to do is unzip the file. You don't install adb/htc_fastboot... You just unzip and use. So long as your drivers are installed correctly.
Help with root, new to HTC
Hi,
I have been on Samsung since ....well forever...lol. Can someone point me to the noob thread to unlock and root? I heard of this Sunshine thing...does that do it all?
Thanks...and sorry for the noobness.
handymanxda said:
Hi,
I have been on Samsung since ....well forever...lol. Can someone point me to the noob thread to unlock and root? I heard of this Sunshine thing...does that do it all?
Thanks...and sorry for the noobness.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=51395737
Save the Manuals!!!
dottat said:
To use adb/htc_fastboot with the copy i have on the thread you were already linked all you need to do is unzip the file. You don't install adb/htc_fastboot... You just unzip and use. So long as your drivers are installed correctly.
Click to expand...
Click to collapse
Thank you, dottat. I have installed and re-installed the driver. My computer can see my phone, and pull it up as a disk drive. I can open the SDK and ADB. In the CMD window, when I type "adb devices", it starts the daemon successfully. Then, under list of devices, it is blank. Any ideas? Could i have downloaded the wrong SDK/ADB package and need to get yours? I'm really green with this software and Linux in general, so I may be missing something. I'm hoping I can get comms worked out and load your RUU file soon. Can I go ahead and take the 5.0 OTA without worry? I have root, s off, and BL unlock. SuperSU fails to update.
THANK YOU!!!
Do you have Android Debugging checked under developer settings?
Save the Manuals!!!
MotoTurbo said:
Do you have Android Debugging checked under developer settings?
Save the Manuals!!!
Click to expand...
Click to collapse
That was it!! Thank you!
dustinoob said:
That was it!! Thank you!
Click to expand...
Click to collapse
Yes! Yeah just remembered that this morning haha. Glad you got it working
Save the Manuals!!!
MotoTurbo said:
http://forum.xda-developers.com/showthread.php?p=51395737
Save the Manuals!!!
Click to expand...
Click to collapse
Thanks! Looks like a lot of work...it's because Verizon locked things down? So am I right in saying I need to use Sunshine to get S-Off then do that Bootloader Unlock? Or do I need to unlock the bootloader?
handymanxda said:
Thanks! Looks like a lot of work...it's because Verizon locked things down? So am I right in saying I need to use Sunshine to get S-Off then do that Bootloader Unlock? Or do I need to unlock the bootloader?
Click to expand...
Click to collapse
What Android version you running?
On 4.4.3 and over sunshine will s off and unlock bootloader together, but its a 50/50 chance. I personally used firewater and weaksauce but I was on 4.4.2 when I did it but VZW closed that exploit in 4.4.3.
Save the Manuals!!!
MotoTurbo said:
What Android version you running?
On 4.4.3 and over sunshine will s off and unlock bootloader together, but its a 50/50 chance. I personally used firewater and weaksauce but I was on 4.4.2 when I did it but VZW closed that exploit in 4.4.3.
Save the Manuals!!!
Click to expand...
Click to collapse
It is 4.4.3. Firewater chugged and spit...LOL...will try Sunshine and see if that unlocks the bootloader as well. Thanks!
Just wondering if anyone has any insight on SU6-7.7 on the Droid line? Whether or not anyone know or hear anything about downgrading to a different SU version? I have the firmware file for the latest SU6-7.7 in case anyone wants it.
https://drive.google.com/open?id=0B7hPMTc_G5VPMFVqZmdMSXJEbjA
It would be nice if Motorola/Lenovo would let us do what we want with a phone they no longer "support".
Thanks, I was looking for this.
RichardCA said:
Thanks, I was looking for this.
Click to expand...
Click to collapse
Sure thing! Let me know if you need anything else!
SalmanJohnson2011 said:
Sure thing! Let me know if you need anything else!
Click to expand...
Click to collapse
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?
RichardCA said:
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?
Click to expand...
Click to collapse
I believe that you can replace the stock boot logo with an unlocked or locked bootloader. There are a quite a few logos to choose from. When you pick one, you fastboot the image.
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
Not sure at the moment. XD I'll reply back to this post or PM you if I do. Thanks again! If you have any more info, please let me know!
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
When you flashed it to your mini/ultra, where you on SU6-7.7?
SalmanJohnson2011 said:
When you flashed it to your mini/ultra, where you on SU6-7.7?
Click to expand...
Click to collapse
I jumped around a lot. I was playing with marshmallow and lollipop builds and needed to revert back. But I was on the Motorola stock SU4.21 when I flashed it.
I used the process on this page, and got zero errors:
http://forum.xda-developers.com/showthread.php?t=2580060
Help please!!!
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:
edgar1994 said:
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:
Click to expand...
Click to collapse
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.
Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.
ashal said:
Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.
Click to expand...
Click to collapse
Nope. I've tried and it doesn't work.
SalmanJohnson2011 said:
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.
Click to expand...
Click to collapse
Man this really sucks i hope someone finds a way around this :crying:
edgar1994 said:
Man this really sucks i hope someone finds a way around this :crying:
Click to expand...
Click to collapse
I Agreed dude. I'm with you! I don't know why I keep getting Verizon phones. XD Regardless of what I learned. Haha
SalmanJohnson2011 said:
Nope. I've tried and it doesn't work.
Click to expand...
Click to collapse
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.
ashal said:
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.
Click to expand...
Click to collapse
For me, I tried going down one update at a time and it still doesn't work.
it says devoloper phones only
can I flash to my ultra even tho its not a dev phone??
RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.
root successful
Davey126 said:
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.
Click to expand...
Click to collapse
Dear i have successfully rooted mine droid mini su6-7.7 with kingo root (not global) v3.4 successfully now i have superuser app in system directory
---------- Post added at 05:42 AM ---------- Previous post was at 05:20 AM ----------
Dear friends i have successfully root mini droid mini su6-7.7 with kingo root v3.4 (not kingo root global). actually i was trying to flash su4.21 over su6-7.7 with RSD lite v6.1 but failed with max get var and after that tried to flash with RSD lite 5.1 again failed without any error. after all of there method i thought of giving a try to kingo root. i downloaded 2 apps kingo root globalv4.9.7 and kingo root v3.4, kingo root global failed to root but.... kingo root v3.4 succeeded to roo. now i have superuser app in system driectory.
but problem is that after removing system app (amazon) when i restarted the phone all the apps came back and superuser app gone. i don't know why so my request to look into this method .
i have tested this method and worked 100% and i have no intention of making fun of me. i have both the apps but don't know how to upload here
Thanks
I know root is achieved with a tot file for the G5 but will there be a one script method like for the g3? I haven't rooted my phone yet because I dont want to risk bricking my phone.
RicardoSal24 said:
I know root is achieved with a tot file for the G5 but will there be a one script method like for the g3? I haven't rooted my phone yet because I dont want to risk bricking my phone.
Click to expand...
Click to collapse
there won't be a script for this as there are no instructions for the bootloader to flash any file. The reason they are using the TOT method is because we have no other way to write to the device. ADB is enabled but the actual command needed to copy everything over was left out.
fatapia said:
there won't be a script for this as there are no instructions for the bootloader to flash any file. The reason they are using the TOT method is because we have no other way to write to the device. ADB is enabled but the actual command needed to copy everything over was left out.
Click to expand...
Click to collapse
Is rooting the phone ASAP worth the time or is it best to wait awhile after a software update?
RicardoSal24 said:
Is rooting the phone ASAP worth the time or is it best to wait awhile after a software update?
Click to expand...
Click to collapse
if you haven't taken that 10d update I would just root now. Not sure if you've seen the thread where they are discussing the possibility of using the TOT method with the new 10d file, but once you update it trips something (qfuse I believe, Autoprime is the one who discovered this AFAIK) that prevents you from using the existing TOT on the forum and from downgrading.
once you root, you can update to 10d and as long as you flash supersu you will still have access to TWRP and root on the latest update. I recommend waiting updating to 10d even after rooting until they iron out all the issues though.
edit: have you done the OEM unlock through dev options yet? it will wipe your phone in the process FYI so make sure you have everything backed up.
Come on. It wasn't that hard to root it. Just follow the directions. Easy!
How do I know if I have the 10d update? I unlocked the bootloader, rooted it, then thought I had a quality control issue with the pain on the frame. So I flashed stock and locked the bootloader to prepare for a warranty exchange. Turns out the paint wasn't bubbling. It was the protective plastic adhesive I had never taken off. I'm stupid, I know, lol. Now I want to root again but I don't know about the 10d update.
rebelde80 said:
How do I know if I have the 10d update? I unlocked the bootloader, rooted it, then thought I had a quality control issue with the pain on the frame. So I flashed stock and locked the bootloader to prepare for a warranty exchange. Turns out the paint wasn't bubbling. It was the protective plastic adhesive I had never taken off. I'm stupid, I know, lol. Now I want to root again but I don't know about the 10d update.
Click to expand...
Click to collapse
about phone/software version
fatapia said:
if you haven't taken that 10d update I would just root now. Not sure if you've seen the thread where they are discussing the possibility of using the TOT method with the new 10d file, but once you update it trips something (qfuse I believe, Autoprime is the one who discovered this AFAIK) that prevents you from using the existing TOT on the forum and from downgrading.
once you root, you can update to 10d and as long as you flash supersu you will still have access to TWRP and root on the latest update. I recommend waiting updating to 10d even after rooting until they iron out all the issues though.
edit: have you done the OEM unlock through dev options yet? it will wipe your phone in the process FYI so make sure you have everything backed up.
Click to expand...
Click to collapse
I've had an understanding that updating android versions while being rooted may cause the phone to be bricked
i have software version 10a that is rootable right thats not 10d or are they similar.
RicardoSal24 said:
I've had an understanding that updating android versions while being rooted may cause the phone to be bricked
Click to expand...
Click to collapse
that may have been true at some point especially with OEM FW, but as far as custom I rooted then updated for my GS4, G3, and v10. Just because it worked for me doesn't mean it will for anyone else. I had the variants that once they were rooted you held on to it like dear life
fatapia said:
that may have been true at some point especially with OEM FW, but as far as custom I rooted then updated for my GS4, G3, and v10. Just because it worked for me doesn't mean it will for anyone else. I had the variants that once they were rooted you held on to it like dear life
Click to expand...
Click to collapse
So then its best to wait until something is done with the update?
RicardoSal24 said:
So then its best to wait until something is done with the update?
Click to expand...
Click to collapse
from what I've read the method is established now and there is "zero" risk as long as you follow the instructions, I haven't updated because I haven't experienced the issues others are having
fatapia said:
from what I've read the method is established now and there is "zero" risk as long as you follow the instructions, I haven't updated because I haven't experienced the issues others are having
Click to expand...
Click to collapse
I think I'll play it safe until its 100% or wait for a new android version with a root method
RicardoSal24 said:
I think I'll play it safe until its 100% or wait for a new android version with a root method
Click to expand...
Click to collapse
it's never 100% safe, hence the quotation marks. there's always a risk of something going wrong such as a power outage, or bad file download. As long as you verify the md5sum of your files you shouldn't have a problem with rooting, the only problems I've seen are people trying to use the wrong files on their device. up to you tho man, good luck with which ever you decide
This root method (compared to my old EVO 3D which needed juopunutbear and a wire)....ez pz.
lordodin912 said:
This root method (compared to my old EVO 3D which needed juopunutbear and a wire)....ez pz.
Click to expand...
Click to collapse
That sounds like fun, if you ask me. What was the wire for, if you don't mind me asking? Bypassing a fuse?
xanderin said:
That sounds like fun, if you ask me. What was the wire for, if you don't mind me asking? Bypassing a fuse?
Click to expand...
Click to collapse
It was needed for s-off, so not tech for root (if i remember correctly) but for being able to flash custom roms and such. Theres youtube videos about it.