All Your Root Questions Answered:
This thread is a work in progress. Ask your root questions, and I'll answer them in the OP. This way we can clean up the other thread.
Thank you @DmdStar, @somberfox, @CrashXXL, and everyone else I missed (which I will add to the OP)
Q: I followed all the directions and after I finished the root procedure, my device is stuck at the M logo? HALP.
A: You didn't follow all the directions, and now you're going to have to start over from step one. Flash SU6-7 in RSD Lite as mentioned in the directions, and follow the directions word-for-word. You're only wasting your own time, not ours.
Q: My phone is stuck at the black green and the root script isn't detecting my phone?
A: You're probably using a USB3.0 port which isn't supported. Move your phone to a USB2.0 port and install the Qualcomm drivers provided in the download.
Q: Why is it taking so long, I think it froze.
A: Just leave your phone alone and get a coffee. Make that three. It's a long process.
Q: Can I install blah-blah ROM?
A: NO! While this is a perma-root, you are unable to disable write-protection, therefore you can't use Safestrap.
Q: Now that I'm rooted, can I unlock my bootloader?
A: SU4-21 was the last system update that worked with Sunshine. Unless you can get in contact with the Chinese middleman, you're out of luck. Sorry.
Q: Why won't my changes to /system persist after a reboot?
A: Unfortunately, no one has managed to circumvent write protection on the device, therefore you can't do anything to /system and expect it to persist unless you do soft-reboots. Sorry.
Q: Can I delete system apps?
A: No, unless you edit the system.mbn and split it into 16mb chunk files. There's no way around this, sorry.
Q: Can I install your Busybox image?
A: I mean if you want a brick, go right ahead. No one's stopping you.
Q: Viper4Android?
A: Which needs Busybox. Again, feel free to proceed at your own risk.
Q: Can I downgrade to SU6-7 if I took the upgrade to SU6-7.2?
A: Yes, you can. There's no magic trick to downgrading to SU6-7, just flash it in RSD Lite.
Q: Can i have only root with SU6-7 and locked bootloader?
A: You can not unlock your bootloader past SU4-21.
Q: Wait, if we can downgrade to SU6-7, why not just downgrade to SU4-21 and unlock our bootloaders?
A: Because you can't. Debating about it on the forums won't magically make it work neither. Nor will complaining about Motorola locking down the devices. You bought an on-contract device that you knew was going to be locked and stock. They also had a developer edition MAXX for sale. If you didn't get it, blame yourself, not Motorola/Verizon.
Q: Can we take the OTA update without losing root?
A: Yes, but you will lose Xposed if you do.(Answered by @DmdStar)
Thanks for the faq @thenameisnigel
Sent from my XT1080 using Tapatalk
yeah thx
Nice one ! Thanks for Viper4Android information. What preset did you choose (battery saving, high/super quality) ?
Actually I don't see what stops you from deleting an app, although it's faster "frozing" it via Titanium for example (paid solution). I removed some files successfully (I should try with apps). Also, did you try installing another ROM ? I didn't take the time to try it but it might work with the python script. You just would have to replace almost all memory blocks, which would take 16+ hours (!!).
I've another question : did someone succeed in installing CF.Lumen ?
Thanks again for the faq
PS : agree with Artimunor just below my post, change colors please !
thenameisnigel said:
Q: Can I delete system apps?
A: No.
Click to expand...
Click to collapse
Wait... here you say it's impossible....
however in the other thread you replied to my post with this:
thenameisnigel said:
Yes
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
My original post:
Artimunor said:
Thats the reason i would like to know how to safely alter the image we upload to the phone, to add/remove apps from it.
Is it save to just mount the image on a linux system as a HD and alter the /system directory?
Click to expand...
Click to collapse
Whats the deal here?
I already started creating a linux environment for this, just did not had the time to complete it yet with my dayjob (already pretty sleep depraved)
P.S. that azure blue really hurts the eyes.
Artimunor said:
Wait... here you say it's impossible....
however in the other thread you replied to my post with this:
My original post:
Whats the deal here?
I already started creating a linux environment for this, just did not had the time to complete it yet with my dayjob (already pretty sleep depraved)
P.S. that azure blue really hurts the eyes.
Click to expand...
Click to collapse
It's possible if you edit the image like what you're doing. That answer was meant more for people who want to edit /system directly from the device. I'll clarify it.
Sent from my XT1080 using Tapatalk
can i have only root with SU7-6 and locked bootloader?
Deleted.
danger2u said:
can i have only root with SU7-6 and locked bootloader?
Click to expand...
Click to collapse
thenameisnigel said:
Q: Can i have only root with SU6-7 and locked bootloader?
A: You can not unlock your bootloader past SU4-21.
Click to expand...
Click to collapse
Sent from my XT1080 using Tapatalk
thenameisnigel said:
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
ok.
but can i have root with locked bootloader with the method that bricks the phone?
danger2u said:
ok.
but can i have root with locked bootloader with the method that bricks the phone?
Click to expand...
Click to collapse
Yes.
Sent from my XT1080 using Tapatalk
if i restart the phone,the root will remain ?
Busybox can be installed?
danger2u said:
if i restart the phone,the root will remain ?
Busybox can be installed?
Click to expand...
Click to collapse
Only if you put it in the image before you flash it to the phone it seems, if you do it afterwards it does not persist.
another question
can we take the OTA update without losing root?
danger2u said:
another question
can we take the OTA update without losing root?
Click to expand...
Click to collapse
Yes. But you will lose xposed if you installed it.
Sent from my XT1080 using Tapatalk
danger2u said:
another question
can we take the OTA update without losing root?
Click to expand...
Click to collapse
Didnt try it myself but from what ive gathered if you used the crashxxl method you will not loose root if you take the su6-7.2 OTA update.
Artimunor said:
Didnt try it myself but from what ive gathered if you used the crashxxl method you will not loose root if you take the su6-7.2 OTA update.
Click to expand...
Click to collapse
i updated
the root it s still here.
will see with Lollipop if ever will be out for Droid maxx
ps: don t update if u want xposed.
danger2u said:
take it the update
the root it s still here.
will see with Lollipop if ever will be out for Droid maxx
Click to expand...
Click to collapse
Dude why are you telling people to take the update when we already know that it'll break Xposed? If you're not here to help, don't post. Simple as that.
Sent from my XT1080 using Tapatalk
thenameisnigel said:
Dude why are you telling people to take the update when we already know that it'll break Xposed? If you're not here to help, don't post. Simple as that.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I take it the update
i don t tell anyone to update the Droid maxx.
are you referring to losing functionality of a baked in exposed? I am running the crash exploit, with non-baked exposed, on SU6-7.2
Related
So I posted a thread here asking for help (the phone was functional at this point) and one user suggested a root method to try out in the comments there http://forum.xda-developers.com/showthread.php?t=2379833
After running this root method my wifi is now dead. It's killing me! Someone please help me out here.
My phone model is a Japanese Softbank 201 M with the 4.1.2 update. It's not rooted but is unlocked. The phone is the developer edition if that helps any.
System version
9.3.102.201M.SBM.en.JP
Model No
201M
Android version
4.1.2
Baseband
SM_T_BP_1539.000.35.03P
Kernel Version
3.0.42-g721d60d
Build Number
9.8.2Q-34_SMJ-102
HBogard said:
So I posted a thread here asking for help (the phone was functional at this point) and one user suggested a root method to try out in the comments there http://forum.xda-developers.com/showthread.php?t=2379833
After running this root method my wifi is now dead. It's killing me! Someone please help me out here.
My phone model is a Japanese Softbank 201 M with the 4.1.2 update. It's not rooted but is unlocked. The phone is the developer edition if that helps any.
System version
9.3.102.201M.SBM.en.JP
Model No
201M
Android version
4.1.2
Baseband
SM_T_BP_1539.000.35.03P
Kernel Version
3.0.42-g721d60d
Build Number
9.8.2Q-34_SMJ-102
Click to expand...
Click to collapse
Ouch. Your WiFi is broken because he told you to flash a US VZW (XT-907) firmware.
Okay. First, you should try to find a 201M restore file. That will get your WiFi back. Next, since you've got a Dev edition, you can bootloader unlock and install a custom recovery, then flash a root zip
EDIT: Found it
http://sbf.droid-developers.org/scorpion_mini_xt902/list.php
Use one of those to restore your WiFi
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Ouch. Your WiFi is broken because he told you to flash a US VZW (XT-907) firmware.
Okay. First, you should try to find a 201M restore file. That will get your WiFi back. Next, since you've got a Dev edition, you can bootloader unlock and install a custom recovery, then flash a root zip
EDIT: Found it
http://sbf.droid-developers.org/scorpion_mini_xt902/list.php
Use one of those to restore your WiFi
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
While the link I gave him was unidentified as to warnings to non vzw users (now fixed) , the flashing of vzw sw comes in step 8 clearly he would have had to have pulled it from a xml himself if he even got that far. And if he did it would have been from reading the rzr op. As the bare motochopper has no vzw sw inside.
aviwdoowks said:
While the link I gave him was unidentified as to warnings to non vzw users (now fixed) , the flashing of vzw sw comes in step 8 clearly he would have had to have pulled it from a xml himself if he even got that far. And if he did it would have been from reading the rzr op. As the bare motochopper has no vzw sw inside.
Click to expand...
Click to collapse
Oh my bad. Thought you sent him to your other post... Still I suspect he got to step 8 and pulled the vz firmware.
OP: Download one of those restore files for the 201M and flash it. That should repair any damage done...
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Oh my bad. Thought you sent him to your other post... Still I suspect he got to step 8 and pulled the vz firmware.
OP: Download one of those restore files for the 201M and flash it. That should repair any damage done...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I didn't get the system img at all. I just wanted to flash the superuser files to /data which I thought would set me up to flash the whole thing with Rom manager.
Anyway, thank you for the help. I am downloading the firmware you linked to now. This guide tells me to edit the XML file and remove the getvar text from it, should this apply here as well? (Edit: Cant post outside links, but I think you get my point)
I'm going to use RSD 6.1.4 to restore the firmware. Any further instructions would be appreciated as I have never done this before.
HBogard said:
I didn't get the system img at all. I just wanted to flash the superuser files to /data which I thought would set me up to flash the whole thing with Rom manager.
Anyway, thank you for the help. I am downloading the firmware you linked to now. This guide tells me to edit the XML file and remove the getvar text from it, should this apply here as well? (Edit: Cant post outside links, but I think you get my point)
I'm going to use RSD 6.1.4 to restore the firmware. Any further instructions would be appreciated as I have never done this before.
Click to expand...
Click to collapse
Don't think you'll need to since it's designed for your device. You can try without the edit and do it if it doesn't work. I'll try to find a guide for RSDLite (been a while since I used it myself - fastboot is usually what I use now...
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Don't think you'll need to since it's designed for your device. You can try without the edit and do it if it doesn't work. I'll try to find a guide for RSDLite (been a while since I used it myself - fastboot is usually what I use now...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Dear sir,
I'd like you to buy a ticket to Karachi right now because I'd run all the way to the airport to KISS YOU until the police dragged me away.
The process worked. My wifi just turned back on. Thank you very much for the weekend stress relief!
I think I'm gonna give up on the idea of rooting this thing until there's a more reliable method available. Also, if anyone has the same issue then take note: I did remove the getvar commands when using RSD.
HBogard said:
.....
Click to expand...
Click to collapse
I am glad SC took care of you & I am sorry I lead you in that direction.
Please fill in some details for others?
How do you have a path to the newer sw? Is it your carriers ota? If you can obtain the same in the xml form there is an easy root using a modded ver w/ unlocked phone. The ota.zip could also be useful if you take it while you have root. It resides in /cache.
Thank you
aviwdoowks said:
I am glad SC took care of you & I am sorry I lead you in that direction.
Please fill in some details for others?
How do you have a path to the newer sw? Is it your carriers ota? If you can obtain the same in the xml form there is an easy root using a modded ver w/ unlocked phone. The ota.zip could also be useful if you take it while you have root. It resides in /cache.
Thank you
Click to expand...
Click to collapse
It wasn't your fault for trying to help, so it's ok. I'm glad a solution existed.
I'm more than willing to answer the questions, but I am a layman here so please explain some things for me: What do you mean by SW? I just installed the update by going into about phone -> system update on Wifi. The carriers here don't even support 3G, much less 4G (So now you know why Wifi was important for me).
The phone came unlocked day one when I bought it from a friend's friend. I don't know if he did it that way or if it comes unlocked because it is the developer edition.
I installed CW Recovery using Fastboot. I installed the incorrect superuser file using Motofail which wrote the superuser file but failed at all other steps. I was then unable to either access or remove this superuser apk file.
Since I am back on 4.0.4. now, what's the easy way to get root access and superuser permissions that you mention? I wish other XT902 owners would post here too, generating interest would really help in getting development support for this phone.
HBogard said:
Dear sir,
I'd like you to buy a ticket to Karachi right now because I'd run all the way to the airport to KISS YOU until the police dragged me away.
The process worked. My wifi just turned back on. Thank you very much for the weekend stress relief!
I think I'm gonna give up on the idea of rooting this thing until there's a more reliable method available. Also, if anyone has the same issue then take note: I did remove the getvar commands when using RSD.
Click to expand...
Click to collapse
Lol no problem, glad to know it worked. Getting root is actually really simple since you're unlocked. All you need to do is flash a custom recovery and flash a root .zip from there... No exploits required
I can try to write up a guide to that if you want
Sent from my XT907 using Tapatalk 4
sloosecannon said:
Lol no problem, glad to know it worked. Getting root is actually really simple since you're unlocked. All you need to do is flash a custom recovery and flash a root .zip from there... No exploits required
I can try to write up a guide to that if you want
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
I tried that, and while it did install superuser, it seemed to have no effect. I couldn't get permissions for any app and using ROM manager's functions would just freeze up that particular application. Any ideas?
HBogard said:
It.
Click to expand...
Click to collapse
Once you root on 404 you can grab your update.zip & copy it to your sd . Any rooting exploit would evolve from that Or the newest xml ver of the 404 you just flashed from rsd. You may be able to request it from your carrier.
---------- Post added at 01:21 PM ---------- Previous post was at 12:40 PM ----------
You can paste the mods from my vzw restore (no vzw software will be used) into the 404 xml & obtain root from a preinstalled cwmr! Then maintain root with voodoo for your ota.
I will help you just read the op. Link is in my signature.
HBogard said:
I tried that, and while it did install superuser, it seemed to have no effect. I couldn't get permissions for any app and using ROM manager's functions would just freeze up that particular application. Any ideas?
Click to expand...
Click to collapse
Hmm... Which zip did you use?
Sent from my XT907 using Tapatalk 4
sloosecannon said:
Hmm... Which zip did you use?
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
http://www.aosp.us/wp-content/files/Root.zip <- This one.
HBogard said:
http://www.aosp.us/wp-content/files/Root.zip <- This one.
Click to expand...
Click to collapse
I am making a xml to gain root. Which of the two xmls did you flash? & why.
the smj-165 must be newer.
aviwdoowks said:
I am making a xml to gain root. Which of the two xmls did you flash? & why.
the smj-165 must be newer.
Click to expand...
Click to collapse
7.7.1Q-164_SMJ-143_SCORPION_MINI_SBM_SIGNED_CFC
I used this one. Why? I saw them posted somewhere else as while while doing a little research on using RSD and saw that the mirrors on that other link mentioned JP in the file name - I have the Japanese softbank model so I figured this was the one specific to my phone. Turned out to be right.
HBogard said:
http://www.aosp.us/wp-content/files/Root.zip <- This one.
Click to expand...
Click to collapse
Try this. Which recovery are you using? ClockworkMod or TWRP?
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Try this. Which recovery are you using? ClockworkMod or TWRP?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I did use this one. It didn't work for me. Clockwork mod always gave an error for writing superuser.apk or something.
HBogard said:
I did use this one. It didn't work for me. Clockwork mod always gave an error for writing superuser.apk or something.
Click to expand...
Click to collapse
I'm an idiot and forgot the link...
http://forum.xda-developers.com/showthread.php?t=1538053
Sent from my Nexus 7 using Tapatalk 4
HBogard said:
7.7.1Q-164_SMJ-143_SCORPION_MINI_SBM_SIGNED_CFC
I used this one. Why? I saw them posted somewhere else as while while doing a little research on using RSD and saw that the mirrors on that other link mentioned JP in the file name - I have the Japanese softbank model so I figured this was the one specific to my phone. Turned out to be right.
Click to expand...
Click to collapse
Can you upload the xml only ~ 1kb
Hello,
I have a NEVER ROOTED Motorola Droid Razr M XT709
In the end all I want to do is use my SD card to store app stuff, just the data would be acceptable ( entire thing would be best ). I am figuring I need to root my device to be able to do this but before I did I wanted to make sure I was capable of rooting it and UNrooting it as well. Here is a link to a screen shot from my phone with it's basic specs displayed under Settings > About Phone : https://dl.dropboxusercontent.com/u/16564468/Screenshot_2013-11-23-09-44-00.png
So...
Can I move apps or app data to SD without rooting? If so, how? If not...
Can I root? If so, what would be the safest method?
Can I unroot? If so, what is the safest method?
Thanks!
-Reiz
I hit a button accidentally while playing a game and got an ota. Posted link to new stats after ota
https://www.dropbox.com/s/eo11d9gqkbbltss/2013-11-23 16.20.04.png
Sent from my XT907 using XDA Premium 4 mobile app
Unfortunately, I can't open your links at work, but I did see your first pic last night and on that version, you would have been able to root. If you took the latest update, then you can't root it.
RikRong said:
Unfortunately, I can't open your links at work, but I did see your first pic last night and on that version, you would have been able to root. If you took the latest update, then you can't root it.
Click to expand...
Click to collapse
Is there any way to roll back on the OTA?
Reizvoller said:
Is there any way to roll back on the OTA?
Click to expand...
Click to collapse
Not if your bootloader is locked.
RikRong said:
Not if your bootloader is locked.
Click to expand...
Click to collapse
So essentially, even if I did a 'hard reset' , I am still boned?
Reizvoller said:
So essentially, even if I did a 'hard reset' , I am still boned?
Click to expand...
Click to collapse
I would assume that you're talking about a factory reset? Yes, you are boned, it will only revert back to the latest OTA, which you just did.
UPDATED:
Please jump to the following thread for information on root/lollipop:
http://forum.xda-developers.com/shield-tablet/help/qa-root-shield-tablet-2-0-lollipop-t2945163
garyd9 said:
There's some misinformation going around concerning lollipop (android 5.0), root, and the SHIELD tablet. I'm posting this (redundant) information to (hopefully) clear things up and prevent someone from causing themselves a headache after the tablet updates...
nvidia has stuck very close to AOSP in their tablet firmware updates, so it's a reasonable assumption (at this point) that the new firmware will also be very close to AOSP.
If that comes to be, then "rooting" the tablet will be more difficult than in previous firmware updates. Most of the gory details can be found in this G+ article by @Chainfire : https://plus.google.com/113517319477420052449/posts/VxjfYJnZAXP
(BTW, as always, a huge thanks to Chainfire for his efforts. If you haven't already, paying for the upgrade to "SuperSU Pro" is well worth the price if for no other reason than to encourage Chainfire to continue work on that project.)
If you don't understand the details of that post from chainfire, I'll try to summarize it: Even if you manage to get a copy of the "su" binary on your system partition (which is essentially the goal of all the older root exploits), it won't matter much in Android 5.0. In Android 5.0, we'll ALSO need a part of the kernel image changed (the ramdisk) so that a part of "superSU" can run at a more permissive context.
Updating the kernel ramdisk shouldn't be too difficult (if its compressed with the kernel in a normal way) once we have the image to play with. As well, in order to put the newly modified kernel image in place, a person would have to unlock their bootloader (which can void your warranty.)
Actually, it's possible (once the image is released by nvidia) that @Chainfire will stick the image on his server in one of his very easy to use "CF-Auto-Root" bundles. (Hopefully, all the @ references I've made will get him to look at this thread and confirm what I've said. The honest truth is that I'm NOT familiar with SELinux, so I'd have to do a bit of experimenting to get this working.)
Take care
Gary
Click to expand...
Click to collapse
Have you found any specifics on what will need to be modified in the ramdisk? I haven't really done anything with the boot.img itself but I'd be interested to see what is going on with this.
Keithn said:
Have you found any specifics on what will need to be modified in the ramdisk? I haven't really done anything with the boot.img itself but I'd be interested to see what is going on with this.
Click to expand...
Click to collapse
That Google plus post I linked to describes the needed change.
Sent from my SHIELD Tablet using Tapatalk
Okay, thanks. I guess I didn't catch that.
Sent from my One M8
Root successful!
I just successfully got root. If I can make it permanent I will post the necessary files/instructions in the update thread.
SuperPichu said:
I just successfully got root. If I can make it permanent I will post the necessary files/instructions in the update thread.
Click to expand...
Click to collapse
With a modified recovery or stock ?
matyas69 said:
With a modified recovery or stock ?
Click to expand...
Click to collapse
CWM. The instructions are up in the lollipop update thread
SuperPichu said:
CWM. The instructions are up in the lollipop update thread
Click to expand...
Click to collapse
Is this root sticking?
whoamanwtf said:
Is this root sticking?
Click to expand...
Click to collapse
It seems to be. Only problem I have run into is that FX file explorer root mode doesn't seem to work, but ES does so I think it's an app compatibility with 5.0 thing rather than a problem with root.
SuperPichu said:
CWM. The instructions are up in the lollipop update thread
Click to expand...
Click to collapse
I'll wait root without custom recovery
SuperPichu said:
It seems to be. Only problem I have run into is that FX file explorer root mode doesn't seem to work, but ES does so I think it's an app compatibility with 5.0 thing rather than a problem with root.
Click to expand...
Click to collapse
Are you able to use FolderMount with it? and Titanium? Those are the reason I need root, and if those both work then I will wipe and unlock to get LP rooted
whoamanwtf said:
Are you able to use FolderMount with it? and Titanium? Those are the reason I need root, and if those both work then I will wipe and unlock to get LP rooted
Click to expand...
Click to collapse
Testing right now. How should I test these? i.e. What do you use them for?
SuperPichu said:
Testing right now. How should I test these? i.e. What do you use them for?
Click to expand...
Click to collapse
Awesome, I use FolderMount to link my obb files from the sd card to the main so that my largest game files are all on my sd card. I actually have the premium version so I just link my whole obb folder and data folder but I would guess linking any obb and then seeing if the game would load would test it. As for Titanium a backup/delete/restore of any app would test all of the features. Thanks for checking that out
whoamanwtf said:
Awesome, I use FolderMount to link my obb files from the sd card to the main so that my largest game files are all on my sd card. I actually have the premium version so I just link my whole obb folder and data folder but I would guess linking any obb and then seeing if the game would load would test it. As for Titanium a backup/delete/restore of any app would test all of the features. Thanks for checking that out
Click to expand...
Click to collapse
No problem.
Results
Folder Mount - Made a link from internal to external and the link seemed to be working correctly (files put in one showed up in the other)
Titanium - Backed-up, uninstalled, and restored Netflix successfully with no errors
Here's a link to the root instructions. http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
Please post any questions there.
Works for both locked and unlocked bootloaders now.
SuperPichu said:
Here's a link to the root instructions. http://forum.xda-developers.com/showpost.php?p=56854633&postcount=77
Works for both locked and unlocked bootloaders now.
Click to expand...
Click to collapse
You beat me too it lol. I just got home pulled the ota and modified the boot.img before I saw this.
Keithn said:
You beat me too it lol. I just got home pulled the ota and modified the boot.img before I saw this.
Click to expand...
Click to collapse
I was starting to wonder how I was the only person (or at least the first) to have that idea.
So I already installed the update for lollipop. Although I was rooted using towelroot, I never installed CWM or unlocked my bootloader. Is it too late to follow the instructions to unlock my bootloader at this point? Do I need to just wait for another root method?
onduck said:
So I already installed the update for lollipop. Although I was rooted using towelroot, I never installed CWM or unlocked my bootloader. Is it too late to follow the instructions to unlock my bootloader at this point? Do I need to just wait for another root method?
Click to expand...
Click to collapse
No if you unlock your bootloader you can follow my unlocked instruuctions.
onduck said:
Is it too late to follow the instructions to unlock my bootloader at this point?
Click to expand...
Click to collapse
no. Not too late.
Sent from my HTC One_M8
It appears that real soon we may have root for locked bootloader devices running Lollipop.
Read here for more info.
zoid_99 said:
It appears that real soon we may have root for locked bootloader devices running Lollipop.
Read here for more info.
Click to expand...
Click to collapse
One thing has nothing to do with the other.
Lollipop requires some changes to have root access and that was only possible with a modified kernel.
Now Chainfire managed to root the Lollipop without a custom kernel.
But installing ZIP file of root need a custom recovery , so still need to have the device with unlocked bootloader .
I've done the root Lollipop using this new root method of Chainfire.
Junior Passos said:
One thing has nothing to do with the other.
Lollipop requires some changes to have root access and that was only possible with a modified kernel.
Now Chainfire managed to root the Lollipop without a custom kernel.
But installing ZIP file of root need a custom recovery , so still need to have the device with unlocked bootloader .
I've done the root Lollipop using this new root method of Chainfire.
Click to expand...
Click to collapse
If you read the article it appears that there is no need to install a zip in a custom recovery to get root with this method.
" the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here"
zoid_99 said:
If you read the article it appears that there is no need to install a zip in a custom recovery to get root with this method.
" the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here"
Click to expand...
Click to collapse
Hmmm interesting.
Then the process should be with CF-Auto-Root .
I used one of those before when I first root in Lollipop.
But thought the command "mfastboot boot cf-auto-root.img" only work with unlocked bootloader and not the locked too.
Amazing.
Me excite!
You can only flash signed zips, so this only makes it easier because you dont need a device specific package for rooting
godutch said:
You can only flash signed zips, so this only makes it easier because you dont need a device specific package for rooting
Click to expand...
Click to collapse
Translated... Will it work on moto x vzw?
GatorsUF said:
Translated... Will it work on moto x vzw?
Click to expand...
Click to collapse
No.
cam30era said:
No.
Click to expand...
Click to collapse
OF course
This revelation means that Android 5.0 users*no longer need to run a modified kernel to gain root access via SuperSU (or other root solutions). While not a huge problem on Nexus devices with unlockable bootloaders, the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here, and we can present an exclusive explanation of the changes needed. At least for now (until/unless Google patch this), it is possible to gain root access and then install and use SuperSU on a stock Android 5.0 device, without any kernel ramdisk tweaking. The reason for this is the need for SuperSU to run a service as root, to allow for unconstrained root access on SELinux-protected devices.
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
neh4pres said:
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
Click to expand...
Click to collapse
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
neh4pres said:
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
Click to expand...
Click to collapse
Thanks Motorola -_-
Buy a nexus 6. That's what I did. Still have the moto x for my wife so I can play with it
Can't afford it right now. If I knew programming, you bet I would be working on it. God I hate Verizon, but been here so long it's my cheapest option.
matt99017d said:
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
Click to expand...
Click to collapse
Will the pure edition work on Verizon?
GrandMstrBud said:
Will the pure edition work on Verizon?
Click to expand...
Click to collapse
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
GreenMunky said:
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
Click to expand...
Click to collapse
LTE should work but what about CDMA side of it?
GreenMunky said:
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
Click to expand...
Click to collapse
GrandMstrBud said:
LTE should work but what about CDMA side of it?
Click to expand...
Click to collapse
No, CDMA will not work, nor 3G. So you will be confined only to LTE service and Google Voice (or similar).
matt99017d said:
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
Click to expand...
Click to collapse
Looks like your idea will not work and maybe that's the reason for this thread? Pure Edition won't work on VZW
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Unless you are on the totally stock system then I wouldn't lock your bootloader.
vjyrdy said:
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Click to expand...
Click to collapse
Technically i believe you could and would still be rooted, but I've always seen it advised NOT to lock your bootloader again until you are on 100% stock (right now your boot.img isn't stock since it's patched for root).
mrcooter said:
Technically i believe you could and would still be rooted, but I've always seen it advised NOT to lock your bootloader again until you are on 100% stock (right now your boot.img isn't stock since it's patched for root).
Click to expand...
Click to collapse
So you mean I would not be able to re-lock bootloader even if I had installed Nougat, isn't it?
thats because we are using tampered boot.img. Is it possible in-future we can use original boot.img ?
vjyrdy said:
Thanks for taking time to read my query.
I was wondering if I've to lock boot-loader after rooting ( I just rooted my Oero)
and before looking can I take everything backup on titanium backup and then restore everything after locking ?
I'm I still be rooted?
Regards
Click to expand...
Click to collapse
If you relock your bootloader with anything other than a factory image you will brick your device.
vjyrdy said:
So you mean I would not be able to re-lock bootloader even if I had installed Nougat, isn't it?
thats because we are using tampered boot.img. Is it possible in-future we can use original boot.img ?
Click to expand...
Click to collapse
If you modify your device, bottom line, you should leave it unlocked so you can fix things or go back to stock if needed, otherwise you could turn it into a paper weight. Even if root is done without modifying the boot.img, I would still keep it unlocked as there are usually still system changes.
mrcooter said:
If you modify your device, bottom line, you should leave it unlocked so you can fix things or go back to stock if needed, otherwise you could turn it into a paper weight. Even if root is done without modifying the boot.img, I would still keep it unlocked as there are usually still system changes.
Click to expand...
Click to collapse
This.
With a modified system or other partition, you risk a brick.
If anything goes wrong, once the bootloader is locked you can't fix it.
DO NOT LOCK THE BOOTLOADER ON ANY PHONE IF ROOTED!!!!!
See this thread:
https://forum.xda-developers.com/essential-phone/help/bricked-essential-phone-t3714809
When I boot my k20 plus I get "cannot verify corruption. Lock your boot loader" it sticks there until I press power. How do I get rid of that without locking bootloader?
zlost1 said:
When I boot my k20 plus I get "cannot verify corruption. Lock your boot loader" it sticks there until I press power. How do I get rid of that without locking bootloader?
Click to expand...
Click to collapse
K20+?? You are in the wrong thread sir. Please search for your phones XDA forum and ask in the rooting thread there. This is the essential ph-1 forum. Good luck!
Sent from my PH-1 using XDA Labs
swiftbones74 said:
K20+?? You are in the wrong thread sir. Please search for your phones XDA forum and ask in the rooting thread there. This is the essential ph-1 forum. Good luck!
Click to expand...
Click to collapse
Doesn't really matter what phone. If. It were a rocket with a string attached the question would have the. Same answer.
zlost1 said:
Doesn't really matter what phone. If. It were a rocket with a string attached the question would have the. Same answer.
Click to expand...
Click to collapse
This ain't the rocket and thread forum or the whatever dumb other thing forum so it really doesn't matter what the answer is.
Sent from my PH-1 using XDA Labs
I don't see anything about a phone type in the original question. Only that he asks about locking the boot loader.
zlost1 said:
I don't see anything about a phone type in the original question. Only that he asks about locking the boot loader.
Click to expand...
Click to collapse
Lol you are in the wrong thread genius. I don't know who "he" is but assume you are referring to the OP and in that case "He" doesn't need to mention anything about any specific phone because he is already posting in the right place. The question you asked about your k-whatever phone will most certainly be different for every phone. Good luck and who knows maybe a forum moderator can help you?
Sent from my PH-1 using XDA Labs
Also this. https://forum.xda-developers.com/lg-k20-plus/help
MOD EDIT
You are one trippy person ? if you really feel the need to post about your LG phone in the mata thread go right ahead buddy.
Sent from my PH-1 using XDA Labs
MOD EDIT
It's worth noting that the Essential PH-1 uses an A/B partition system so any advice given here would not be helpful in the slightest for devices that don't have the same file system. Quickly doing a search of your phone reveals it's not an A/B partitioned system so following advice here could potentially lead to you actually destroying your phone.
could you lock the BL once rooted if in fastboot mode it lists device tampering = false?
Wonderful reply
tech_head said:
This.
With a modified system or other partition, you risk a brick.
If anything goes wrong, once the bootloader is locked you can't fix it.
DO NOT LOCK THE BOOTLOADER ON ANY PHONE IF ROOTED!!!!!
See this thread:
https://forum.xda-developers.com/essential-phone/help/bricked-essential-phone-t3714809
Click to expand...
Click to collapse
Thanks, this reply should be pinned to the top of the thread. It is crucial information for our dear noobies
swiftbones74 said:
Lol you are in the wrong thread genius. I don't know who "he" is but assume you are referring to the OP and in that case "He" doesn't need to mention anything about any specific phone because he is already posting in the right place. The question you asked about your k-whatever phone will most certainly be different for every phone. Good luck and who knows maybe a forum moderator can help you?
Sent from my PH-1 using XDA Labs
Also this. https://forum.xda-developers.com/lg-k20-plus/help
Click to expand...
Click to collapse
Just an opinion, but...there are rules for posting in forums that Dev's, no matter how over worked and underpaid/appreciated should follow as well. Teach by example not proxy. Applaud the calm gentleman who responded with eloquent grammar and poise.
NaterTots said:
Unless you are on the totally stock system then I wouldn't lock your bootloader.
Click to expand...
Click to collapse
If you patched boot.img (Android 11 stock) with magisk and then lock bootloader... Will that be possible since it's stock rom or it altered because of the boot.img patch?
rossrosh007 said:
If you patched boot.img (Android 11 stock) with magisk and then lock bootloader... Will that be possible since it's stock rom or it altered because of the boot.img patch?
Click to expand...
Click to collapse
I don't know.