What is it:
Yet another implementation of the well-known miloj's root exploit for most Android ICS devices. It is said to be quirky as it operates on /system filesystem using debugfs. However, it definitely works on an XT910 running 672.180.41.XT910.NonEFIGSRetail.en.EU ICS official firmware without any ill effects.
Why yet another implementation:
I was sick and tired of cleaning up mess left by other implementations. This one will set minimal required permissions on the two files it dumps to /system partition. It will also remove all temporary files it is going to create during rooting process (i.e. no /data/local/12m/cmds et al.).
Requirements:
POSIX Bourne shell
ADB installed in PATH
Your Android device has to be ARM-based and be running on ICS up to 4.0.4
Please feel free to replace su binary and Superuser.apk app with your favorite ones. The ones packaged were taken from SuperSu 0.99 (4th Dec 2012) by Chainfire.
Does it work on the new JB kernel?
Olao99 said:
Does it work on the new JB kernel?
Click to expand...
Click to collapse
Unfortunately, no. I gave it a shot, and it was a no go. Slumming it with usb tethering until we're blessed with root.
Have you tried http://www.androidpolice.com/2012/1...trix-hd-all-rooted-courtesy-of-dan-rosenberg/ or http://www.oneclickroot.com/root-android/android-4-1-jelly-bean-root/? I can't test myself as I have an XT910 and I don't want to mess with XT912 leak.
Sent using a touch screen
Napisane na ekranie dotykowym
Could anyone implement a root script for windows please ? Vatazhka, thanks for sharing.
Vatazhka said:
Have you tried http://www.androidpolice.com/2012/1...trix-hd-all-rooted-courtesy-of-dan-rosenberg/ or http://www.oneclickroot.com/root-android/android-4-1-jelly-bean-root/? I can't test myself as I have an XT910 and I don't want to mess with XT912 leak.
Sent using a touch screen
Napisane na ekranie dotykowym
Click to expand...
Click to collapse
Unfortunately, neither of those work.
If there was a way to roll back to the ICS boot.img, the phone could be downgraded to ICS. Unfortunately, that's the only bit that fails when trying to flash back.
OP, why would you make a post for another way to root ICS at a point in time when a lot of people are looking for a JB Root?? At least clarify your thread title to state it is for ICS.
Semseddin said:
Could anyone implement a root script for windows please ? Vatazhka, thanks for sharing.
Click to expand...
Click to collapse
You can run it on Windows e.g. using Cygwin. You must have all drivers and ADB in place, and specifically ADB in PATH.
pastorbennett said:
Unfortunately, neither of those work.
If there was a way to roll back to the ICS boot.img, the phone could be downgraded to ICS. Unfortunately, that's the only bit that fails when trying to flash back.
Click to expand...
Click to collapse
It's a shame, but - on the other hand - also a good sign that Motorola fixes bugs in their ROMs. Technically, what is holding you back from downgrading is version number of the boot partition stored in the CDT. The bootloader won't allow you to flash a partition image with version lower than the one stored in the CDT.
85gallon said:
OP, why would you make a post for another way to root ICS at a point in time when a lot of people are looking for a JB Root?? At least clarify your thread title to state it is for ICS.
Click to expand...
Click to collapse
If you did bother reading OP (there is a reason I bother writing it, you know), you would have known it doesn't work on JB before downloading it. It is definitely fit for purpose, which is rooting ICS without leaving any residue and that's why I shared it. I'm happy to take any bug reports if it doesn't work as advertised.
Please note that some people found it useful and thanked me for sharing it - I'm glad it worked.
Added value of not including ICS reference in topic: People who are looking for a way to root JB leak obviously didn't bother to read OP in other threads, too - there's always time to learn.
Semseddin said:
Could anyone implement a root script for windows please ? Vatazhka, thanks for sharing.
Click to expand...
Click to collapse
You can also open the script file named "android-ics-root" in a text editor, and copy & paste the commands into the Windows command prompt.
Vatazhka said:
It's a shame, but - on the other hand - also a good sign that Motorola fixes bugs in their ROMs. Technically, what is holding you back from downgrading is version number of the boot partition stored in the CDT. The bootloader won't allow you to flash a partition image with version lower than the one stored in the CDT.
Click to expand...
Click to collapse
Thanks for the info, and for your work on this. I've got a follow-up question, though. What's the possibility of unpacking the ICS boot.img, modifying the version number, and then repacking the boot.img? I really am not that knowledgeable when it comes to Android hacking/programing, so I don't know if it's even possibile.
This is probably off-topic for the thread, but from the way it looks, the two possible ways for getting root on the RAZR running OTA JB would be to downgrade to ICS (with a boot.img that will work) and follow the guides out there for updating to JB while keeping root, and the other would be to figure out the root exploit. Of course, I have no idea how to do either, but I'm wondering if a downgrade would be an easier approach than discovering an exploit that will work.
As a side thought, does your root method register with the root checker build into recovery? It would be absolutely genius if it didn't.
pastorbennett said:
Thanks for the info, and for your work on this.
Click to expand...
Click to collapse
There was little work involved, to be honest - just a little clean up, that's all.
What's the possibility of unpacking the ICS boot.img, modifying the version number, and then repacking the boot.img? I really am not that knowledgeable when it comes to Android hacking/programing, so I don't know if it's even possibile.
Click to expand...
Click to collapse
Sorry, it's not possible. Boot partition is protected with a digital signature, so the bootloader will detect modified/corrupted image and refuse to flash it. There's also a runtime validation, so even if you managed to flash a modified image it wouldn't run.
This is probably off-topic for the thread, but from the way it looks, the two possible ways for getting root on the RAZR running OTA JB would be to downgrade to ICS (with a boot.img that will work) and follow the guides out there for updating to JB while keeping root, and the other would be to figure out the root exploit. Of course, I have no idea how to do either, but I'm wondering if a downgrade would be an easier approach than discovering an exploit that will work.
Click to expand...
Click to collapse
As I explained previously, downgrade of CDT is not possible. Digital signature is in place again.
As a side thought, does your root method register with the root checker build into recovery? It would be absolutely genius if it didn't.
Click to expand...
Click to collapse
It's currently unknown how the so-called root checker interacts with /xbin/qe. My script happily ignores both
Sent using a touch screen
Napisane na ekranie dotykowym
Related
Ok so today i was about to sit down and root
after trying to use the flash recovery method it seems my Hero is patched
my Q is ....
am i still able to root this badboy using other methods and if so, can someone post a decent guide or good tutorial to do so
Many Thanks
no takers then? any help would be appreciated
i don't get your question, you have rooted your phone and now you want to know how?
anyway, there is more than enough information on this, you just gotta read it!
No, he is saying that the firmware he is using is patched so the normal way to root the phone doesn't work, in other words, the exploit used to get root access was patched. He wants to know if there are any other ways to root it.
I'm new to Android, but I do believe there is an older firmware version or something along the lines of that that allows you to open a terminal and root it from there.
mrinehart93 said:
No, he is saying that the firmware he is using is patched so the normal way to root the phone doesn't work, in other words, the exploit used to get root access was patched. He wants to know if there are any other ways to root it.
I'm new to Android, but I do believe there is an older firmware version or something along the lines of that that allows you to open a terminal and root it from there.
Click to expand...
Click to collapse
thanks for re-explaining that for me, maybe i wasnt clear enough
but again i do thank you .... i guess ill just see how this thread goes
yeah it seems its patched and normal method will not work .... not too hot on ADB and thats why i was asking
cheers
the version of your rom could help
check modaco, there is a thread explaining some "gold card" stuff. i think that is the hardcore method if everything else fails. never looked at it though, got lucky with my hero and got an older rom
Yea I'm having this problem too...
I had a rooted Hero but then 'foolishly' installed the update to fix lag, and therefore losing my root.
I have even created a goldcard on my SD card and still the 'One Click Root' doesn't work...
Any other methods?
OGC313 said:
I have even created a goldcard on my SD card and still the 'One Click Root' doesn't work...
Click to expand...
Click to collapse
If you've got the goldcard, you need to downgrade your ROM before you can root.
Regards,
Dave
foxmeister said:
If you've got the goldcard, you need to downgrade your ROM before you can root.
Regards,
Dave
Click to expand...
Click to collapse
Oh I forgot to mention I did that... installed the 2.73? I think t-mobile uk original RUU and it still didn't work.
If you installed T-Mobiles 2.73, you've just reinstalled a ROM that can't be exploited!
Regards,
Dave
foxmeister said:
If you installed T-Mobiles 2.73, you've just reinstalled a ROM that can't be exploited!
Regards,
Dave
Click to expand...
Click to collapse
But there is no other tmobile RUU available, or at least I can't find it. The 1.76 one?
google is your friend:
http://www.megaupload.com/?d=XDXZYP7F
Is there currently any way to gain root access on JB for 672.180.41.XT910.Retail.en.EU?
If not, is anyone known to be working on it?
one more vote
Zenithise said:
Is there currently any way to gain root access on JB for 672.180.41.XT910.Retail.en.EU?
If not, is anyone known to be working on it?
Click to expand...
Click to collapse
I would also be very grateful!!
I unrooted because I was afraid that it would conflict with OTA (before the upgrade instructions were published).:crying:
.
Zenithise said:
Is there currently any way to gain root access on JB for 672.180.41.XT910.Retail.en.EU?
If not, is anyone known to be working on it?
Click to expand...
Click to collapse
I have tried a lot of root tool, but it still doesnt work. So all we have to do is wait for the developers to make a it
Hit the 'thanks' button if it helps
I just updated to EU retail and I'm in the same situation. None root tool worked
For XT910 devices there is currently no way to get root. It is only possible for XT912 devices.
To gain root access during JB update you should have protect root with Voodoo OTA Rootkeeper. That works.
AcidAngel21 said:
For XT910 devices there is currently no way to get root. It is only possible for XT912 devices.
To gain root access during JB update you should have protect root with Voodoo OTA Rootkeeper. That works.
Click to expand...
Click to collapse
That would have worked. We know that ...
Those who did not protect root, just hope that someone can help to gain root again.
Frup said:
That would have worked. We know that ...
Those who did not protect root, just hope that someone can help to gain root again.
Click to expand...
Click to collapse
Well. I've updated from nonEFIGSRetail.en.EU to Retail.en.EU using http://forum.xda-developers.com/showthread.php?t=2194825. Root did not survive this.
Maybe there is some more root user friendly process, but it is not easy to find the correct one.
AcidAngel21 said:
For XT910 devices there is currently no way to get root.
Click to expand...
Click to collapse
Damn! Now I can't restore all my apps and data using Titanium Backup. I did try the method from here:
http://forum.xda-developers.com/showthread.php?t=1710871
...and it did say success, but during the process it came up with "system/bin/sh su not found" and TB says it has no root access. It worked when I was on ICS, but now I am on JB 4.1.2 System Version 982.124.14.XT910.Retail.en.AU. Anybody with bright ideas on how to gain root access again would be much appreciated!
?
I'm on JB with my XT910 and it's rooted, in fact I used the method from the Eternity project (it's the easiest way from my viewpoint)...
yogi77 said:
?
I'm on JB with my XT910 and it's rooted, in fact I used the method from the Eternity project (it's the easiest way from my viewpoint)...
Click to expand...
Click to collapse
really ? do you have a link to this please.
Death Walker said:
really ? do you have a link to this please.
Click to expand...
Click to collapse
I rooted the ICS, installed BMM, flashed the Kernel and flashed Avatar Rom in 2nd slot, Liquid in 3rd slot
Another link
yogi77 said:
I rooted the ICS, installed BMM, flashed the Kernel and flashed Avatar Rom in 2nd slot, Liquid in 3rd slot
Another link
Click to expand...
Click to collapse
....this doesn't help any of us who are already on JB and need root as there is no way back to ICS!
mormopterus said:
....this doesn't help any of us who are already on JB and need root as there is no way back to ICS!
Click to expand...
Click to collapse
Actually, there is a way, but only if you aren't on the JB bootloader. When I wrote my comment, I thought, you just have to flash again (also with JB bootloader). In the meantime, I learned that it seems to be prevented to switch to a lower version.
Sorry for any confusion...
yogi77 said:
Actually, there is a way, but only if you aren't on the JB bootloader. When I wrote my comment, I thought, you just have to flash again (also with JB bootloader). In the meantime, I learned that it seems to be prevented to switch to a lower version.
Sorry for any confusion...
Click to expand...
Click to collapse
in the development section there is a thread on root for JB but you need to be on linux check it out
naifs_br10 said:
in the development section there is a thread on root for JB but you need to be on linux check it out
Click to expand...
Click to collapse
Thx for the hint. I (personally) don't need root, but it would be interesting to read. I'm on Gentoo, so should be ok. Could you post the link? I know, I'm lazy
Found it The exploit is an ELF, but it should be possible (in principle) to create a Windows binary also, shouldn't it?
yogi77 said:
Thx for the hint. I (personally) don't need root, but it would be interesting to read. I'm on Gentoo, so should be ok. Could you post the link? I know, I'm lazy
Found it The exploit is an ELF, but it should be possible (in principle) to create a Windows binary also, shouldn't it?
Click to expand...
Click to collapse
not sure but for now only for linux users apparently unless its developed/sourced out for windows
naifs_br10 said:
not sure but for now only for linux users apparently unless its developed/sourced out for windows
Click to expand...
Click to collapse
djrbliss said:
A Windows version of this exploit is not possible for technical reasons. Please don't waste anyone's time by asking about a Windows version.
Click to expand...
Click to collapse
anyone can do it they just need a live cd and its just a case of simple copy n paste in terminal and follow the instructions and they are done. they could even use a usb stick with say ubuntu installed on it.
i did this with a live cd on my laptop to see if it worked and it did, my main pc is ubuntu anyway but a friend was too scared to try it on his laptop with live cd so i did it to show him and he rooted his very quickly
A few of us purchased the Dev Edition and it appears there are some things where clarification is required concerning the three "R's":
1. Rooting: I understand this wonderful rooting exercise is successful: http://forum.xda-developers.com/showthread.php?t=2290798. I would think since the Dev Edition is unlocked, an owner would only utilize Step 3, and NOT the kernel exchange section. Correct?
2. ROMing: Since the ROMS were created using the Loki enabled system, does this affect ROMing the Dev Edition since it is already unlocked? What does a user need to do? Or, does it not matter? Do the Loki enabled ROMS work on a Dev Edition?
3. Recovery: Again, it appears TWRP and CWM are Loki adjusted, so does this affect recovery on the Dev Edition and restoring? Also, is there a Stock Factory Image which will NOT turn the phone back to a locked bootloader? Or, does the one which exists OK to use?
I only ask these questions since a few of us are somewhat confused.
Thanking you in advance!
markwebb said:
A few of us purchased the Dev Edition and it appears there are some things where clarification is required concerning the three "R's":
Click to expand...
Click to collapse
I've been thinking about buying the Verizon S4 Dev Edition phone, but have been hesitant due to not knowing how simple it would be to root. Is it as simple as just running MotoChopper? Or is there a better way?
Being that the bootloader on this phone is truly unlocked, can you install the current versions of CWM or TWRP that are LOKI enabled, and will it work on this phone? I haven't seen any compiled versions that were non-loki (standard).
Same question goes for kernels too.
The first batch of Dev phones sold out in less than 24 hours, so I'd expect some of the people that have them would start posting their experience with it here soon. At least, I hope so!
Root failed when just applying the Motochopper step! It says it installs correctly and then it reboots and SuperSu is installed and then I checked for an upgrade which it took. However, it says it cannot install binary, there is a problem and closes.
I uninstalled SuperSu and tried a few times to root again but it doesn't work.
My phone states:
Kernel Version: 3.4.0-562219 dated May 15th
Build Number: JDQ439.I545OYUAMDK
Baseband: I545OYUAMDK
Must be something we can do....
markwebb said:
Root failed when just applying the Motochopper step! It says it installs correctly and then it reboots and SuperSu is installed and then I checked for an upgrade which it took. However, it says it cannot install binary, there is a problem and closes.
I uninstalled SuperSu and tried a few times to root again but it doesn't work.
My phone states:
Kernel Version: 3.4.0-562219 dated May 15th
Build Number: JDQ439.I545OYUAMDK
Baseband: I545OYUAMDK
Must be something we can do....
Click to expand...
Click to collapse
I wonder if step 2 and 4 are still required? (swapping kernels)
Even though the bootloader is unlocked, the kernel may still have root blocked?
guyd said:
I wonder if step 2 and 4 are still required? (swapping kernels)
Even though the bootloader is unlocked, the kernel may still have root blocked?
Click to expand...
Click to collapse
It sounds like it. But wouldn't swapping kernels render the Dev Edition to a retail version? Kinda defeats the purpose, no? Or, am I missing something?
The question is: Does the Dev Edition have the same kernel as the Retail Edition? If so, then it would make sense to swap kernels. I think we need the devs to weigh in.
markwebb said:
It sounds like it. But wouldn't swapping kernels render the Dev Edition to a retail version? Kinda defeats the purpose, no? Or, am I missing something?
The question is: Does the Dev Edition have the same kernel as the Retail Edition? If so, then it would make sense to swap kernels. I think we need the devs to weigh in.
Click to expand...
Click to collapse
From what I've been able to gather, Samsung has put in place a SetUID restriction on the stock release kernel via CONFIG_SEC_RESTRICT_SETUID. Apparently the D2 prerelease kernel doesn't have this restriction in place. That seems to be why flashing that is required prior to using MotoChopper to gain root. What I can't figure out is why you can flash the release DK afterwards and still keep root?
On the T-Mobile and Sprint S4 they've been able to remove the SetUID restriction on their latest DL release kernel by recompiling the kernel source with the SetUID restriction commented out
Thanks for the thoughts and analysis. Hopefully someone will find an alternate
root method for the dev edition since it has been available for a week and it sold out in less than twenty four hours, somebody with know how must have purchased it and is tinkering as we speak.
I would hate to render it back to a retail version otherwise.
Sent from my SCH-I545 using xda app-developers app
markwebb said:
Thanks for the thoughts and analysis. Hopefully someone will find an alternate
root method for the dev edition since it has been available for a week and it sold out in less than twenty four hours, somebody with know how must have purchased it and is tinkering as we speak.
I would hate to render it back to a retail version otherwise.
Click to expand...
Click to collapse
I think I may have found a solution. With the Developer Edition we have an unlocked bootloader, so there is no need to use loki. I was looking for a non-loki patched (normal) recovery that could be flashed in Odin. I think I found one here http://forum.xda-developers.com/showthread.php?t=2322675. Look for the "Latest version can be found here" link, not the "loki patched" link. The filename is : Philz_touch_5.06.6-jfltevzw.tar.md5
If this works like it did in previous unlocked Samsung devices, then we should be able to flash the custom recovery in Odin, and then boot into recovery afterwards to flash SuperUser. From there, we're rooted.
If I had my dev edition S4, I'd test it out myself. But I'm still waiting for them to get back in stock!
Great..am somewhat game to try. Well report back. Thanks!!
Sent from my SCH-I545 using xda app-developers app
IT WORKED...somewhat!!! When it boots, I now get Samsung Custom and unlocked symbol and I am in Philz Touch Recovery backing up the image.
As expected, the backup image is 4GB+ (saved on external card of course).
However, I can't update binary for root.
You, sir, are a genius...thanks so much..almost there!
Not really rooted though. Can't update binary and when in Root Explorer I can explore most folders but Root checker says I am not rooted.
Now what do I do? LOL
markwebb said:
IT WORKED...somewhat!!! When it boots, I nLet me know how it goes ow get Samsung Custom and unlocked symbol and I am in Philz Touch Recovery backing up the image.
As expected, the backup image is 4GB+ (saved on external card of course).
However, I can't update binary for root.
You, sir, are a genius...thanks so much..almost there!
Click to expand...
Click to collapse
Did you flash SuperSU from recovery via the zip file? (from this thread) http://forum.xda-developers.com/showthread.php?t=1538053. Look for the UPDATE-SuperSU-v1.41.zip file in the download section.
This should give you root after flashing in recovery! If you can't get root in a root app after flashing this file, then the kernel is blocking root. You can thank Samsung for adding that in the DK kernel.
You can easily work around this by flashing a custom kernel!
Let me know how it goes.
guyd said:
Did you flash SuperSU from recovery via the zip file? (from this thread) http://forum.xda-developers.com/showthread.php?t=1538053. Look for the UPDATE-SuperSU-v1.41.zip file in the download section.
This should give you root after flashing in recovery! If you can't get root in a root app after flashing this file, then the kernel is blocking root. You can thank Samsung for adding that in the DK kernel.
You can easily work around this by flashing a custom kernel!
Let me know how it goes.
Click to expand...
Click to collapse
BINGO!!!!!!!!!!!! THANKS!!!!
Now we need a thread/tutorial started for the Dev Edition Owners on how to do this!!
markwebb said:
BINGO!!!!!!!!!!!! THANKS!!!!
Now we need a thread/tutorial started for the Dev Edition Owners on how to do this!!
Click to expand...
Click to collapse
Do you now have root with the stock DK kernel, or did you flash a custom kernel?
Root with stock kernel.
Sent from my SCH-I545 using xda app-developers app
markwebb said:
Root with stock kernel.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Now I know exactly what I need to do when I get mine!
Thanks for testing it out on your device
guyd said:
Now I know exactly what I need to do when I get mine!
Thanks for testing it out on your device
Click to expand...
Click to collapse
You are welcome. Now, the next question: Can we flash the ROM's which are Loki adjusted?
markwebb said:
You are welcome. Now, the next question: Can we flash the ROM's which are Loki adjusted?
Click to expand...
Click to collapse
Good question. From what I have seen thus far, the recovery is the piece that has to be Loki adjusted to allow it to be flashed on a locked bootloader. I don't think the ROM cares one way or the other. The only thing I still have questions about is the kernel. Is the kernel in the Developer Edition different than the carrier version?
guyd said:
Good question. The only thing I still have questions about is the kernel. Is the kernel in the Developer Edition different than the carrier version?
Click to expand...
Click to collapse
How do I/we find out? If you have any suggestions, let me know. I have gone this far and sweated.
markwebb said:
How do I/we find out? If you have any suggestions, let me know. I have gone this far and sweated.
Click to expand...
Click to collapse
If we could get an MD5 of the Developer DK kernel (boot.img), and compare it to the MD5 of a completely stock DK kernel (boot.img). Or maybe compare the kernel build numbers? I dunno, just throwing some ideas out.
Should i root XTZ or not?
I search few threads with rooting XTZ but seems every method has some issues, for example rebooting after mounting system / deleting app...
What's the best working method to root WITHOUT ANY issue?
E7ite said:
Should i root XTZ or not?
I search few threads with rooting XTZ but seems every method has some issues, for example rebooting after mounting system / deleting app...
What's the best working method to root WITHOUT ANY issue?
Click to expand...
Click to collapse
There is an effective solution to the mounting reboot issue with the app, adbd insecure. Follow the instructions in the root thread and you should be fine
Sent from my SGP312 using Tapatalk 4
to Root or Not to root?
E7ite said:
Should i root XTZ or not?
I search few threads with rooting XTZ but seems every method has some issues, for example rebooting after mounting system / deleting app...
What's the best working method to root WITHOUT ANY issue?
Click to expand...
Click to collapse
Should i root XTZ or not?
ask yourself a question, WHY should i root my XTZ...???
some of us want to root their devices but in reality they are not using the privilege of being rooted. it makes no sense.
rooting is safe provided you know how to backup and restore your firmware if anything goes wrong during/after the process.
and if you are rooted be careful with the app and files inside the /system. and be careful with the apps (for rooted devices that requires rooted devices) you'll installed.
:victory:
big ach said:
There is an effective solution to the mounting reboot issue with the app, adbd insecure. Follow the instructions in the root thread and you should be fine
Sent from my SGP312 using Tapatalk 4
Click to expand...
Click to collapse
Can you please specify? Post link or something please.
By the way mounting reboot issue appears on every method of rooting and every stock rom?
donedos said:
Should i root XTZ or not?
ask yourself a question, WHY should i root my XTZ...???
some of us want to root their devices but in reality they are not using the privilege of being rooted. it makes no sense.
rooting is safe provided you know how to backup and restore your firmware if anything goes wrong during/after the process.
and if you are rooted be careful with the app and files inside the /system. and be careful with the apps (for rooted devices that requires rooted devices) you'll installed.
:victory:
Click to expand...
Click to collapse
I need a root but if it makes device buggy and not working properly then i rather just don't do it. Im asking cause i've seen a lot of issues in threads with rooting methods.
E7ite said:
Can you please specify? Post link or something please.
By the way mounting reboot issue appears on every method of rooting and every stock rom?
I need a root but if it makes device buggy and not working properly then i rather just don't do it. Im asking cause i've seen a lot of issues in threads with rooting methods.
Click to expand...
Click to collapse
I don't know if the issue appears on every method of rooting and every stock rom but it definitely appeared for me, stock US wifi version 32 GB
Here is the solution to solve the rebooting when remounting issue: http://forum.xda-developers.com/showpost.php?p=42914126&postcount=23
After I applied this fix, root access works perfectly for me, and I even used Vodoo OTA Rootkeeper and my root survived the upgrade!
Good luck!
big ach said:
I don't know if the issue appears on every method of rooting and every stock rom but it definitely appeared for me, stock US wifi version 32 GB
Here is the solution to solve the rebooting when remounting issue: http://forum.xda-developers.com/showpost.php?p=42914126&postcount=23
After I applied this fix, root access works perfectly for me, and I even used Vodoo OTA Rootkeeper and my root survived the upgrade!
Good luck!
Click to expand...
Click to collapse
Thank you but any issues other than that?
E7ite said:
Thank you but any issues other than that?
Click to expand...
Click to collapse
Not that I know of. Everything is working very well for me after Root and applying that fix. But maybe others can chime in with their experience.
Sent from my DROID RAZR HD using Tapatalk 4
big ach said:
Not that I know of. Everything is working very well for me after Root and applying that fix. But maybe others can chime in with their experience.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
I bet there's something else.
By far i heard of: Mounting reboot, NFC bug, Unclock bootloader status...
BUMP
I dont know why all these comments leave you on the road to ruin... Cause not once did I see any one ask what model you have or what your current version of android you are running on it.
I have the US version SGP312 32GB WiFi only version build 10.3.1.C.0.136... (Android version 4.2.2) rooted and working fine with no hiccups.
Keep in mind I did update it first from the box.
Here is the link if you need it:
forum.xda-developers.com/showthread.php?t=2428830
For the record, I can confirm that my NFC works just fine after root. Just beamed a few videos from my phone to the tablet without a even a hiccup.
(FYI the NFC chip is located right under the Xperia logo on the back)
E7ite said:
Should i root XTZ or not?
I search few threads with rooting XTZ but seems every method has some issues, for example rebooting after mounting system / deleting app...
What's the best working method to root WITHOUT ANY issue?
Click to expand...
Click to collapse
No issues whatsoever with mine, rooted with the Chinese vroot.
Sent from my C5303 using Tapatalk 4
Has anyone successfully rooted this phone yet? I found root instructions by googling, but they were posted before the release of the phone so I don't trust them. For example:
http://guideroot.net/how-to-root-lenovo-phab-2-pro/
madmartian said:
Has anyone successfully rooted this phone yet? I found root instructions by googling, but they were posted before the release of the phone so I don't trust them. For example:
http://guideroot.net/how-to-root-lenovo-phab-2-pro/
Click to expand...
Click to collapse
I temp rooted mine with dirty cow, however it gained me very little. There are three main obstacles: 1) SELinux prevents most things from working, because each program runs within a tight security context, 2) using dirty cow causes the kernel to not save changes to the partition (it doesn't want to write a corrupted partition to disk), in other words a r/w /system is useless, even when you can finally write to it, 3) using dirty cow on the most attractive programs (from a permissions perspective) causes "little" problems like the screen going off.
I've been monitoring another XDA thread (sorry, link is at home) where they are working through these issues on another device. There are various approaches and workarounds, but they currently all involve way more risk than I can justify for a $500 phone.
AIUI, once you've got root, you need to be able to put selinux into permissive mode, but surely getting temp root is a start?
Can you not install systemless root?
If I got the dates right, the phone kernel should be affected by this bug. A proof of concept seemed to be promised by the reporter in the next few days. http://seclists.org/oss-sec/2016/q4/607
Will be interesting to see how it compares to dirty cow as far as access.
Tried KingoRoot - no luck
madmartian said:
Has anyone successfully rooted this phone yet? I found root instructions by googling, but they were posted before the release of the phone so I don't trust them. For example:
http://guideroot.net/how-to-root-lenovo-phab-2-pro/
Click to expand...
Click to collapse
Well, I tried KingoRoot by running the apk and it failed with an error at 90%. They say there is a version that can be run from Windows, but it appears to be no longer available. I emailed support. I will post again if I make any progress.
madmartian said:
Has anyone successfully rooted this phone yet? I found root instructions by googling, but they were posted before the release of the phone so I don't trust them. For example:
http://guideroot.net/how-to-root-lenovo-phab-2-pro/
Click to expand...
Click to collapse
DO NOT TRY "Rootkhp". IT CONTAINS VIRUSES AND OPENS UP A BUNCH OF WINDOWS, INCLUDING A FAKE ANTIVIRUS.
Thanks Windows Defender for NOT defending me!
calamari said:
I temp rooted mine with dirty cow, however it gained me very little.
Click to expand...
Click to collapse
Hi
what kernel version does the LP2Pro have? can you post a link to the binary so that others can try it out? thanks
speculatrix said:
Hi
what kernel version does the LP2Pro have? can you post a link to the binary so that others can try it out? thanks
Click to expand...
Click to collapse
https://github.com/timwr/CVE-2016-5195
Please note that the phone is 64-bit. This is source code that requires compilation and additional code to do anything useful. Prerequisites include the NDK and related build tools installed via Android Studio. I run Linux so it was relatively painless, but I imagine it might be more of a challenge under Windows.
calamari said:
https://github.com/timwr/CVE-2016-5195
Please note that the phone is 64-bit. This is source code that requires compilation and additional code to do anything useful. Prerequisites include the NDK and related build tools installed via Android Studio. I run Linux so it was relatively painless, but I imagine it might be more of a challenge under Windows.
Click to expand...
Click to collapse
thanks, I tried that out of curiosity on my phone and it worked (Lollipop, stock Sony Xperia Z Ultra ROM).
--edit-- It appears to give me a root shell, but it doesn't execute anything if I hit return, just hangs. but still, it proves my kernel is vulnerable ;-(
deleted. had a total brain fade and made this post in the wrong forum, sorry.
speculatrix said:
Is there someone with an AZf3U willing to trust me and try the dirtycow exploit?
I've uploaded the dirtycow exploit which I built using the Android Studio NDK to
http://www.zaurus.org.uk/download/CV...5195.built.tgz
there's two builds, one for for 32 and the other for 64 bit android
unpack and run on a linux box connected to the phone over ADB
the instructions on how to use it are here:
https://github.com/timwr/CVE-2016-5195
let me know if you need more help
Paul
Click to expand...
Click to collapse
Try posting this in the Zenfone 3 forum
doctahjeph said:
Try posting this in the Zenfone 3 forum
Click to expand...
Click to collapse
sorry about that. I had a total brain failure! thanks for letting me know, I copied my post over there.
speculatrix said:
sorry about that. I had a total brain failure! thanks for letting me know, I copied my post over there.
Click to expand...
Click to collapse
i can mess with adb commands and see what happens but fastboot isnt on this phone....i can tinker with it and see what happens with the phone. let me know what i can do !
Hi. I know this thread is about the Lenovo Phab2 Pro and I have the Lenovo Phab2 but maybe someone can help me. I tried what was suggested on this thread https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305 But it seems I screwed up and now the phone gets stuck in the Lenovo sign. I'd really appreciate some help since I just bought this phone 2 days ago and now I can't use it. I can access TWRP but it seems there's nothing in /system. I think maybe that's the problem. I'm no expert but since I had rooted and downgraded and upgraded firmware several times on my previous phone, a LG G3. I thought maybe I could do this. I shouldn't have If someone can help me I'd really appreciate. Thanks in advance.
I was able to fix this. Sorry to have bothered.
Hi,
I've been able to get proper root access on this phone. One new problem I am facing is that the tango camera and sensors doesn't seem to work. Normal camera works just fine.
Is this related to the rooting or can it be anything else entirely?
Edit: Never mind. I was able to fix it without having to remove the root. Apparently 'Tango Core' didn't have permissions to access camera. I am not sure how that got reset. So I gave access to it and now it works just fine.
Dominic.B said:
Hi,
I've been able to get proper root access on this phone. One new problem I am facing is that the tango camera and sensors doesn't seem to work. Normal camera works just fine.
Is this related to the rooting or can it be anything else entirely?
Edit: Never mind. I was able to fix it without having to remove the root. Apparently 'Tango Core' didn't have permissions to access camera. I am not sure how that got reset. So I gave access to it and now it works just fine.
Click to expand...
Click to collapse
Dominic, what method did you use to root the Lenovo Phab 2 Pro? Can you provide a link or instructions?
madmartian said:
Dominic, what method did you use to root the Lenovo Phab 2 Pro? Can you provide a link or instructions?
Click to expand...
Click to collapse
Hi. Check this
https://forum.xda-developers.com/showthread.php?p=72725120
Sent from my Lenovo PB2-690M using Tapatalk
Anyone root the PB2-690Y
Dominic.B said:
Hi. Check this
https://forum.xda-developers.com/showthread.php?p=72725120
Sent from my Lenovo PB2-690M using Tapatalk
Click to expand...
Click to collapse
Has anyone rooted the pb2-690y?