Hi Everyone,
I was able to maintain root when I did my upgrade to the leaked .206 ICS build. I pushed the n95 offsets file as part of the mempodroid package to find out what the required offsets for the mempodroid exploit would be and the following is the output:
Code:
[email protected]_maserati:/data/local/root # ls -l
ls -l
-rwxr-xr-x root root 10276 2012-06-08 09:13 mempodroid
-rwxr-xr-x root root 5403 2012-06-08 09:13 n95-offsets
-rwxr-xr-x root root 2162 2012-06-08 09:13 n95-offsets.c
[email protected]_maserati:/data/local/root # ./n95-offsets
./n95-offsets
n95-offsets by Nesquick95
Gets requiered offsets for mempodroid exploit
./mempodroid 0x8003 0xad33 sh
1|[email protected]_maserati:/data/local/root # ./mempodroid 0x8003 0xad33 sh
./mempodroid 0x8003 0xad33 sh
obviously the most important part is :
Code:
./mempodroid 0x8003 0xad33 sh
Does this help at all with regarding the root method?
edit:
Nope, I don't think this helps since the mempodroid exploit was probably patched in this version of the kernel that we have.
Can someone check if this program works? I can't since I'm already rooted...
I'm interested if it works on the leak: http://www.unlockroot.com
Sent from my XT894 running ICS
danifunker said:
Can someone check if this program works? I can't since I'm already rooted...
I'm interested if it works on the leak:
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Mempodroid does not work but if you'll send or post a copy of n95-offsets I'll see if it's the same on my phone. I'm assuming mempodroid pokes some bits somewhere in /system/bin/sh or elsewhere... to gain root?
Droid3Util used this offset: mempodroid 0xd6c4 0xad33 and It doesn't work.
siggmatic said:
Mempodroid does not work but if you'll send or post a copy of n95-offsets I'll see if it's the same on my phone. I'm assuming mempodroid pokes some bits somewhere in /system/bin/sh or elsewhere... to gain root?
Droid3Util used this offset: mempodroid 0xd6c4 0xad33 and It doesn't work.
Click to expand...
Click to collapse
They patched the mempodroid exploit in the kernel version of linux which is why it doesn't work... How about other rooting methods from other devices? Has anybody tried the new method from the asus transformerpad 300? http://forum.xda-developers.com/showthread.php?t=1704209
Funny you mention this. I just tried this method out and...
It worked!
I'm using the .208 leaked kernel. Screwed up my phone last night dicking around with my customized version of Hashcode's Safestrap and testing the non-safe flashing functions. Pretty much resigned myself to being rootless until djrbliss released his method, then I saw the same thread you mentioned earlier this afternoon.
This is gonna be big.
Awesome!
Great news! I will upgrade to .208 tomorrow. I have noticed a couple bugs on .206, I will see if they have been worked out after the upgrade
Sent from my A100 using Tapatalk 2
Related
First of all, Linux and OS X come with sqlite3 by default. Windows users will need to download the executable. With that said, here is how you can enable sideloading the old-fashioned way.
Code:
[[email protected] ~]$ adb shell
$ su
# busybox cp /data/data/com.android.providers.settings/databases/settings.db /data/data/com.android.providers.settings/databases/settings.db.bak
# chown system.system /data/data/com.android.providers.settings/databases/settings.db
# ls -l /data/data/com.android.providers.settings/databases/settings.db*
# busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard
# exit
$ exit
[[email protected] ~]$ adb pull /sdcard/settings.db
sqlite3 settings.db
sqlite> SELECT * FROM secure WHERE name="install_non_market_apps";
3|install_non_market_apps|0
sqlite> UPDATE secure SET value=1 WHERE name="install_non_market_apps";
sqlite> SELECT * FROM secure WHERE name="install_non_market_apps";
3|install_non_market_apps|1
sqlite> .quit
[[email protected] ~]$ adb push settings.db /sdcard/
[[email protected] ~]$ adb shell
$ su
# busybox cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
# chown system.system /data/data/com.android.providers.settings/databases/settings.db
# ls -l /data/data/com.android.providers.settings/databases/settings.db*
# exit
$ exit
[[email protected] ~]$ adb reboot
You should be all set.
thank god for super one click
Script?
Sent from my MB860 using XDA Premium App
lsxrx7 said:
thank god for super one click
Click to expand...
Click to collapse
1) Great if you use Wind'oh!s which I refuse to do.
2) I like to know how things work.
I think this work on only rooted devices. If that case we have one already which will root it and also side load apps.
You got the phone gdanko?! Cool
I'll do it this way for kicks when I get my phone lol
gdanko said:
1) Great if you use Wind'oh!s which I refuse to do.
2) I like to know how things work.
Click to expand...
Click to collapse
Yes, it's always great to know how things work.
But it looks like SuperOneClick is not just confined to Windows.
It is compatible with:
Windows Vista
Windows 7
Ubuntu Hardy (8.04 LTS)
Ubuntu Jaunty (9.04)
Ubuntu Karmic (9.10)
Ubuntu Lucid (10.04 LTS)
Ubuntu Maverick (10.10)
Debian Lenny (5.0)
Debian Squeeze (testing)
Debian Sid (unstable)
Debian Experimental
SuperOneClick uses Mono on Linux platforms, so most any of the modern ones should work. I used it on my openSUSE box and it worked just fine for allowing non-market installs.
Can anyone do this a little more nood friendly? And/or does this require root?
phro321 said:
Can anyone do this a little more nood friendly? And/or does this require root?
Click to expand...
Click to collapse
Yeah, you basically want to get out of this thread and head here:
http://forum.xda-developers.com/showthread.php?t=960336
Follow briefmobile's tutorial. And yes, it requires root.
If I am not mistaken gdanko doesnt use any of those operating systems. He uses a mac...
Maybe his old school ways will help uncover some mysterious portal into the Atrix that will allow cracking the bootloader...
I just finished running superoneclick. I wanted to double check that my phone is now allowing unknown sources, but i dont see the checkbox where it should be. Is this normal? Thanks!
__redfox__ said:
I just finished running superoneclick. I wanted to double check that my phone is now allowing unknown sources, but i dont see the checkbox where it should be. Is this normal? Thanks!
Click to expand...
Click to collapse
I guess the check box is not added, but superoneclick did do its job. The phone is communicating with the laptop as expected.
__redfox__ said:
I guess the check box is not added, but superoneclick did do its job. The phone is communicating with the laptop as expected.
Click to expand...
Click to collapse
Follow this to add the check box: http://forum.xda-developers.com/showthread.php?t=972760
agentdr8 said:
SuperOneClick uses Mono on Linux platforms, so most any of the modern ones should work. I used it on my openSUSE box and it worked just fine for allowing non-market installs.
Click to expand...
Click to collapse
Fails on Ubuntu 64. And installing mono and a host of other things for something so trivial is pointless.
Thank you, I needed this sideloading hack since I've already updated/rooted my phone and couldn't use Gladatrix or aRoot without having to reflash 1.26
------------
edit: Actually it got my phone stuck in bootloader with my configuration (1.57 update and rooted). SBF flashing now..
marlasinger said:
Thank you, I needed this sideloading hack since I've already updated/rooted my phone and couldn't use Gladatrix or aRoot without having to reflash 1.26
------------
edit: Actually it got my phone stuck in bootloader with my configuration (1.57 update and rooted). SBF flashing now..
Click to expand...
Click to collapse
Hey How did you root your 1.57?
Spoofy said:
Hey How did you root your 1.57?
Click to expand...
Click to collapse
Go to the GladRoot thread linked in my signature below. Please use the search function in the future.
Ririal said:
Go to the GladRoot thread linked in my signature below. Please use the search function in the future.
Click to expand...
Click to collapse
Lose the attitude buddy.
Don't tell me to search, as I have been googling and searching this forum for over a week and found nothing but SuperOneClick which also required me to downgrade.
I probably missed it due to "Last edited by Ririal; 23rd April 2011 at 01:40 AM. Reason: Updates"
Unfortunately this is still not what I am looking for as I am on 1.57 and am still required to downgrade.
Please have some respect.
EDIT: I'ts also not in the sticky thread
EDIT #2: I just found [HOWTO] Easy Root 1.5.7 using GingerBreak which popped up on the 23rd. WOHOOO, no need to downgrade and risk Wifi issues.
Spoofy said:
Lose the attitude buddy.
Don't tell me to search, as I have been googling and searching this forum for over a week and found nothing but SuperOneClick which also required me to downgrade.
I probably missed it due to "Last edited by Ririal; 23rd April 2011 at 01:40 AM. Reason: Updates"
Unfortunately this is still not what I am looking for as I am on 1.57 and am still required to downgrade.
Please have some respect.
EDIT: I'ts also not in the sticky thread
Click to expand...
Click to collapse
It has nothing to do with respect, and I don't have an attitude. Relax, guy.
All the information is readily available, all you need to do is look for it. There's several threads on the first page of the development forum (which you found as you're posting in it) that contain the information you need. One of the threads is even clearly labeled: "[HOWTO] Easy Root 1.5.7 using GingerBreak"
So sorry, I get a little short with people who ask questions that are already answered. Don't take it personally. Here's the breakdown:
There's currently 2 methods of root, one is GladRoot, which requires you to downgrade first. The other is GingerBreak, which formats your phone data. Pick your poison.
HTML:
The new update blocks the current ways of attaining root for the device. However, if you have root before you update, it is possible to retain this during the upgrade.
Script is online!
A newer version is available here:
http://forum.xda-developers.com/showthread.php?p=12540398#post12540398
Yeah... I'll just wait for you
Thanks for this! been holding out on the update ever since I found out you lose root during the beta testings
if this works i guess it's time to get my desktop back up and running so i can flash back and use this. damn power supplies dying on me.
ill wait for ur auto script
will this b possible btw neone?
Flash the 1.5.7 sbf -> run gblur custom rom -> run the root scrip
No Gingerblur needs root to push its files, also if you need a host I can host
Scripts are online!
Run beforeupdate.bat, update, then run afterupdate.bat.
Haven't tried it yet but wanted to say thanks and great work!
--EDIT -- BELIEVE THIS IS FIXED--
you didn't package the bin folder with psneuter.. :X
In reference to "adb.exe push movesu.sh /data/local/tmp > NUL 2>&1"
movesu.sh is now backup.sh, yes?
Also busybox "mv /system/xbin/su /system/bin/frozenfish" clobbers the copy from system/bin, if there is a difference, i thought it was generally a symlink to /system/bin.
Other than that, good idea in renaming the binary file, I probably won't use frozenfish in case Motorola targets that now..
Sounds sweet! If I already updated can I flash back to old then re root? Then run script then update?
Sent from my MB860 using XDA App
Update: Yes You Can ! just finished..
Whoops - I based it from adeo without making the proper changes. Corrected one should be live in a few minutes.
all good take your time..
so far the only corrections were the movesu.sh in beforeupdate.bat
and the missing /bin folder :X .. well technically you just need psneuter in there.. and just change the /bin/psneuter.. to /psneuter saves you time lol
The new version is up. It depends on su being installed on the system. You'll also need to OK a request by Superuser for root before it will run on beforeupdate.bat.
curious as the previous workaround used webtop to retain root through LXterminal... with root on here, will we be able to re-apply the Webtop mod?
by the way, good work
"movesu.sh" is called but doesn't exist.
shawnbuck said:
The new version is up. It depends on su being installed on the system. You'll also need to OK a request by Superuser for root before it will run on beforeupdate.bat.
Click to expand...
Click to collapse
Do you have the su that does not require Superuser.apk installed?
Let me boot into my windows partition and I'll give it a try. Let me make sure I have the steps right:
Run beforeupdate.bat
Get OTA from system update
Run afterupdate.bat
Anything I'm missing? I'm rooted using aRoot fyi.
I think
adb.exe push movesu.sh /data/local/tmp > NUL 2>&1
is a typo and it should say backupsu
dLo GSR said:
curious as the previous workaround used webtop to retain root through LXterminal... with root on here, will we be able to re-apply the Webtop mod?
by the way, good work
Click to expand...
Click to collapse
Root here is a normal root, anything you could do before you'll be able to continue doing.
eval- said:
I think
adb.exe push movesu.sh /data/local/tmp > NUL 2>&1
is a typo and it should say backupsu
Click to expand...
Click to collapse
Thats right - I corrected that and added a new version.
OrangesOfCourse said:
Let me boot into my windows partition and I'll give it a try. Let me make sure I have the steps right:
Run beforeupdate.bat
Get OTA from system update
Run afterupdate.bat
Anything I'm missing? I'm rooted using aRoot fyi.
Click to expand...
Click to collapse
Exactly right. I'll clarify the directions in the OP.
lpsi2000 said:
Do you have the su that does not require Superuser.apk installed?
Click to expand...
Click to collapse
This doesn't come bundled with a copy of su, it uses the one already installed in the system.
will this work on flash sbf?
Hello.
I am having trouble rooting my LG P990.
Android 2.2.2
Kernel 2.6.32.9
Build FRG83G
LGE Version LGP990-V10b
I have tried SuperOneClick 1.7 and the latest version (1.9.1).
Failed after trying to install Busybox.
I have also tried Z4root 1.3
I have also tried the method explained on Cyanogenmod Wiki
http://wiki.cyanogenmod.com/index.php?title=LG_Optimus_2X:_Rooting
and have gotten stuck at the command
/data/local/busybox cp /data/local/su /system/xbin/su
I am returned this error:
can't stat '/system/xbin/su': Not a directory
So yes. I have checked other threads. Does anyone have any good ideas on what I should do next to get this phone "permanently" rooted?
vitaminxero said:
Hello.
I am having trouble rooting my LG P990.
Android 2.2.2
Kernel 2.6.32.9
Build FRG83G
LGE Version LGP990-V10b
I have tried SuperOneClick 1.7 and the latest version (1.9.1).
Failed after trying to install Busybox.
I have also tried Z4root 1.3
I have also tried the method explained on Cyanogenmod Wiki
http://wiki.cyanogenmod.com/index.php?title=LG_Optimus_2X:_Rooting
and have gotten stuck at the command
/data/local/busybox cp /data/local/su /system/xbin/su
I am returned this error:
can't stat '/system/xbin/su': Not a directory
So yes. I have checked other threads. Does anyone have any good ideas on what I should do next to get this phone "permanently" rooted?
Click to expand...
Click to collapse
Try installing Pauls clockwork. No preroot required, it uses psneuter to create root. After that push busybox and superuser.
Sent from my LG-P990 using XDA Premium App
SuperOneClick also uses the psneuter exploit, so if one works, they all should.
I use SOC v1.9.1 yesterday on my phone (as I briefly reverted to stock for some testing), and it worked first time.
Rusty! said:
SuperOneClick also uses the psneuter exploit, so if one works, they all should.
I use SOC v1.9.1 yesterday on my phone (as I briefly reverted to stock for some testing), and it worked first time.
Click to expand...
Click to collapse
Well, he does not state that the exploit dont work..
I have never had problems with soc either..
Sent from my LG-P990 using XDA Premium App
reidar.ostrem said:
Well, he does not state that the exploit dont work..
I have never had problems with soc either..
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
PSneuter roots successfully but the entire thing fails when i cannot seem to install busybox
Checking for busybox
Copying busybox (/system/xbin/)...
cp: can't stat '/system/xbin/busybox': Not a directory
OK
chmod busybox (/system/xbin/)...
Unable to chmod /system/xbin/busybox: Not a directory
OK
Installing busybox (/system/xbin/)...
/system/xbin/busybox: not found
FAILED
vitaminxero said:
PSneuter roots successfully but the entire thing fails when i cannot seem to install busybox
Checking for busybox
Copying busybox (/system/xbin/)...
cp: can't stat '/system/xbin/busybox': Not a directory
OK
chmod busybox (/system/xbin/)...
Unable to chmod /system/xbin/busybox: Not a directory
OK
Installing busybox (/system/xbin/)...
/system/xbin/busybox: not found
FAILED
Click to expand...
Click to collapse
Well, have you tried installing busybox any other way? If you are not comfortable with adb, i think you can install busybox from titanium and see if titanium gets root at the same time ...
Skipped the whole thing and used CWM. =P
Used Paul's CWM. Replaced the .img with one for cyanogen.
Followed the rest of the steps here: http://wiki.cyanogenmod.com/index.php?title=LG_Optimus_2X:_Recovery_and_CyanogenMod
Now running CM7.1Nightly10
vitaminxero said:
Skipped the whole thing and used CWM. =P
Used Paul's CWM. Replaced the .img with one for cyanogen.
Followed the rest of the steps here: http://wiki.cyanogenmod.com/index.php?title=LG_Optimus_2X:_Recovery_and_CyanogenMod
Now running CM7.1Nightly10
Click to expand...
Click to collapse
Good to hear ! Glad it worked out for you.
Sorry in advance if I'm missing something simple but I'm at my wits' end here...
For a while now I've been slowly researching and learning how a possible root exploit could work, and finally I managed to come up with an attack plan and set up a build toolchain, only to find that I can't even run a simple Hello World!
Now I'm only a bit familiar with linux environments and even less so with android ones, but I'm pretty sure something's not right here. Trying to run anything I put on the phone just spits back "not found". Also, any command that actually can't be found gives me "permission denied", from my searching online I couldn't find out whether this is the correct behavior.
Code:
$ ./hello
./hello
./hello: not found
$ hello
hello
hello: permission denied
$ ls -l
ls -l
drwxrwxrwx shell shell 2011-08-09 21:21 bin
drwxrwx--x mot_tcmd shell 2011-06-29 08:50 12m
-rwxrwxrwx shell shell 5585 2011-08-09 21:10 hello
drwxrwx--x mot_tcmd shell 2011-06-29 16:38 tmp
(Had to strip down the commands for the overzealous spam filter, this is running from /data/local)
From what I've seen in the other threads in this forum people have been able to run busybox and such from this location, so does anyone have a clue what's going on here?
Alternately, if there's anyone that's very familiar with native-code android development or the android kernel, particularly regarding network capabilities, please let me know here or via PM/e-mail so maybe I can figure out if my exploit is even possible.
/data/local ? I didn't realize adb had access there. I run busybox from /tmp there's about 2mb of space there for us to use.
Good luck to you.
Well, I went and found a prebuilt busybox and that works, so I'm assuming there's something wrong with the binaries I'm making.
Right now I'm using the Code Sourcery GNU/Linux ARM toolchain as recommended by various sources online, since it seemed like the easiest option for someone with minimal experience with the GNU build tools. But unless I can get it working, seems like my only other option (without learning all the details of GNU development) is some "agcc" script somebody made a few years ago, which may not even work anymore, and would require me to do a full build of the android source in a linux VM.
So, anyone have any insights or experience on building native binaries fairly painlessly?
Try changing the permissions of the file.
chmod 755 /data/local/filename
Sent from my ADR6400L using Tapatalk
im pretty sure u are building a binary for another arch than arm...
I claim no credit for this but after the 893 OTA you wont have root and you will have to go this way to get it back.
Original post I robbed this from [HERE]
You will need adb to do this. You can get the download here depending on your operating system. ADB
Download the follow file: it contains the exploit, su, Superuser
Download exploit -->Exploit.zip
1) Unzip contents of folder to your Desktop
2) open a command terminal and navigate to the folder (cd Desktop/Exploit)
3) type the following commands
---> adb push zerg /data/local
---> adb push su /data/local
---> adb push Superuser.apk /data/local
---> adb shell
---> cd /data/local
---> chmod 777 zerg
---> ./zerg
4) Wait for the root to be gained
5) type the following commands
---> adb shell (only type this if you are no longer in [email protected])
---> mount -o rw,remount /dev/null /system
---> cat /data/local/su > /system/bin/su
---> cat /data/local/Superuser.apk > /system/app/Superuser.apk
---> chmod 4755 /system/bin/su
---> chmod 4755 /system/app/Superuser.apk
---> reboot
This is from P3Droid.
Click to expand...
Click to collapse
Worked like a charm. Thanks!
want to do this for my brother, you just connect the phone to the computer with usb debugging mode enabled right?
Fyi if you correctly root and forever root prior to the ota you will retain root. The update does not remove root if it was forever rooted.
Sent from my DROID BIONIC using XDA App
I used this method on a used Bionic I bought that has 5.7.893. It worked perfectly.
Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.
charlie310 said:
Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.
Click to expand...
Click to collapse
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.
you forgot last step....then update and youll still have forever root
I restored and forever rooted my bionic, then did OTA, and still have root. I was on rooted stock previously, but restored because I wasn't able to get or pull the OTA update due to "error try again later".
Sent from my DROID BIONIC using Tapatalk
Terror_1 said:
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.
Click to expand...
Click to collapse
Let's think about this logically:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
Or, D/L and install ADB, D/L and install Java SE, and D/L & unzip the Exploit Zip and type in 15 command lines to root your phone.
It's pretty obvious what is considered easier and requires less unnecessary software.
BTW, if you are flashing a ROM, then option 1 is always the best way to go since you don't have to D/L the OTA update since most ROMs have the update built in (and you already have the updated radio).
getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!
charlie310 said:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
It's pretty obvious what is considered easier and requires less unnecessary software.
Click to expand...
Click to collapse
You forget that some of us already have all the prerequisites. I personally can't say if your method works or not. It failed several times for me, so I gave up and zerg worked.
luke1333 said:
getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!
Click to expand...
Click to collapse
I am partial to doing things manually myself but I guess 43v3r does it too.
I personally had no luck with it.
Sent from my DROID BIONIC using XDA App
what version could you not root?
Does zerg work on 5.9.901 ?
luke1333 said:
what version could you not root?
Click to expand...
Click to collapse
893 43v3r doesn't work on, if you restore the 886 then root you should be fine. Just doing the update then trying to gain root isn't going to work.
kris7778 said:
Does zerg work on 5.9.901 ?
Click to expand...
Click to collapse
I don't know for sure but I am pretty confident that it would.
THANKS!
Flawless victory!
Binarality!
Has anyone rooted a previously unrooted device running version 5.9.901? Who's process?
This method worked for me, but I notice that my 3g service was weak and my 4g was gone. Even if i restarted the phone I couldn't get my 4g to work. This was after the 4g issue with VW braking it. Has anyone else had this problem?
1 click method
is there any 1 click method out there that can be used to do this ,,i used 4ever root a couple of time to restore my phone after screwing it up .. but now even that wont work .. so yeah i have the update but no root ...no matter how i try to do it before or after ..
and i unfortunately do not know how to connect to adb to push anything to my phone .. im not that technical with it ....dont have a clue .ive tried but not easy for me that is thanking you in advance Robb
One question, if I update and then for any reason I can't get root can I go back to stock rom you know the one before ota and start over? ???
Sorry for my english lol
Sent from my DROID BIONIC using XDA App