Thanks to @kryz who managed to generalize the Dirty Cow exploit, XT1528 now has a way to get temporary root : link Notice that the /system will still be read-only, but at least full access to /data is available. Given the state of XT1528, this looks like a pretty good progress!
Steps to get temp root (in Lollipop):
0) uninstall SuperSu apk if you have it installed, see thisfor the reason to uninstall
1) install Croowt.apk, use the 2nd option in the menu : "Get root"
2) install SuperSu apk from the playstore (don't update the binary)
3) install RootChecker apk from the playstore
4) enjoy temporary root (until hard reboot)
I've tested this on 5.0.2, but should probably work on 5.1.1 as well (as long as it was not patched since the end of Oct). Here is the output of Root Checker (where everything looks nice and green !) :
Device: XT1528 (MOTO E Verizon prepaid)
Android Version: 5.0.2
Additional - SELinux
Status: NOT enforcing
Status stored in /sys/fs/selinux/enforce
SuperSu works (untill hard reboot) !!!
@9acca9, @dreyeth, @Whoareyou, @bendrexl, @docna, @caspar347, @Dishe, @hp79
This is great!
Thank you @kryz
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
jcpowell said:
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
Click to expand...
Click to collapse
This looks like the old Kingroot behavior - temp root which is highly unstable. Once after a Kingroot attempt I had to factory reset the device due to the "junk" left behind, at least here it's all nice and clean ! I wonder if forcing a soft reboot right after root may help to make it more stable ... Or perhaps something else is going on ?
No idea if anyone is looking into unlocking this phone's bootloader still but hopefully this leads to it. Happened with my Droid Turbo. The initial process was use Kingroot for temp root and sunshine to unlock.
Tried sunshine and after second test it gives an error. Won't even try
jcpowell said:
Tried sunshine and after second test it gives an error. Won't even try
Click to expand...
Click to collapse
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
bibikalka said:
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
Click to expand...
Click to collapse
There is a bug if you have SuperSU is installed before get the root, the restore init function will not work properly.
So the instructions in this post should be changed, and clarify that is required uninstall it.
Also ive fixed another bug related to clean the state of the system, the apk is updated in the main post.
Really after the restore clean the phone should be in a clean state, but if supersu is installed i don't know why is denying the access to the app.
Can you check this issue please?
@kryz I'm actually finding it more unstable with the updated app.
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Idk, as soon as I attempt to use my phone after root it freezes and reboots. If I let it sit it'll last an hour at least, lol
jcpowell said:
@kryz I'm actually finding it more unstable with the updated app.
Click to expand...
Click to collapse
Let's see what's going on
-Are you using the apk or adb script?
-If you use the apk and don't restore init what happens?
-If you restore init is laggy or reboot?
-Can you try the adb script and tell me if you also get a reboot?
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Regards,
---------- Post added at 01:33 AM ---------- Previous post was at 01:16 AM ----------
fenlon said:
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Click to expand...
Click to collapse
First about the sdcard, i will look after that bug that i know what's happening,please don't remove/mount/umount for now.
Do you have a computer to do some checks?
You say that with the new version there is not reboot but laggy, can you check if there is some process eating the cpu with top:
Code:
/data/local/tmp/busybox top
I suspect there is the last process restauring init that is eating the cpu, check for this or ;
Code:
ps | grep dirtycow
If that is the case kill it and we will know if is the responsible of that lag.
In other hand can you attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Guessing that you are using the apk, what happen if you don't restore init?
Is laggy or just unstable, don't start wifi/bluetooth you can't change settings are like locked.
Have you tried the script adb version, can you try and tell me if you have the same issue?
Best regards,
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
jcpowell said:
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
Click to expand...
Click to collapse
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
kryz said:
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
Click to expand...
Click to collapse
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
jcpowell said:
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
Click to expand...
Click to collapse
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
kryz said:
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
Click to expand...
Click to collapse
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
jcpowell said:
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
Click to expand...
Click to collapse
If it reboots just checking permissions the problem is the fsck_msdos process not the shellcode in init, i saw in the files that you attach all is ok.
I've updated the apk in the main post, now it will release the sdcard, please check that version in the same way, first before get root, click "check perm" wait to see the results and work with the phone to see if reboots again for a while.
If all is working with "check perm" and you don't get reboot, try get root, is very probably that now doesn't reboot.
I think with the adb script will work because it overwrites run-as, anyways ive updated the apk for release the sdcard check process and it'll return ok status.
The instructions for the rar and adb.
First you need adb installation in your computer, i mean connectivity with the device via adb.exe.
When you have adb working you need to put all the content of the rar in the path /data/local/tmp/.
So extract the rar in your computer in a folder and with adb push copy all the files to that folder:
(in the folder of the rar contents)
Code:
adb push * /data/local/tmp/
Then get a shell with adb:
Code:
adb shell
Execute the script to exploit it:
Code:
cd /data/local/tmp
./exploit.sh
Wait the logs and if all is ok execute:
Code:
run-as -s2
Wait 5 seconds and:
Code:
su
If all is ok you will have a root shell, this method is more stable even doesn't clean the init you can do it in the app, but test all before.
That last apk causes me immediate reboot. Maybe it was not the fsck_msdos cause I was able to do a check and not get a reboot with the debug apk you gave me. I am trying the adb method but I think I am messing up some steps. Will let you know when I get through it.
@kryz I should have some time tomorrow to test the shell commands. Thank you again for taking your time to do this.
Related
The problem: After installing AOSP 1.6, I noticed protected apps weren't showing in Market, including some I had bought in 1.5. I restored my 1.5 backup and found the same thing. Instructions on this thread (http://forum.xda-developers.com/showthread.php?t=605028) were able to get my apps back in 1.5, but upon reflashing 1.6 I was back to square one.
Update:
----------
I started fresh to test things out, trying both AOSP 1.6 and gbhil's modded AOSP 1.6. I wiped, then flashed and booted, then flashed gbits and booted, then setup my google creds, then rebooted and flashed superuser, then installed busybox then rebooted.
That's my baseline. From that point, I observed:
- Market showed a limited amount of apps. One time My Downloads had all my apps, but upon trying to install one I got a "Download unsuccessful" error. I'm assuming when the download was initiated my fingerprint was sent out, and then Market filtered My Downloads to reflect that unofficial fingerprint. Meaning, most apps were missing again.
- I updated build.prop with the fingerprint from stock 1.5 (see below for instructions). I downloaded a random app (Twidroid Free) so it'd send out my "new" fingerprint, and thus remove the filter limiting my apps. Soon after all apps were appearing again. Be patient here, sometimes it doesn't update instantly. One gave a download error, but trying to install it again solved it.
- Just to test, I edited my build.prop back to whatever was default with the 1.6 rom I was using, then rebooted. My Downloads still showed everything, but as soon as I installed any random app, that unofficial fingerprint was sent out and my apps were limited again.
I don't know enough about Market to know the repercussions of what I did - does it think I have 1.5, so will it be showing me only 1.5 compatible apps? Either way, I'd rather have access to all 1.5 apps than only some 1.6 apps. And aren't most (not all, but most) 1.5 apps backwards compatible with 1.6 anyway? So the only real downside is 1.6+ apps will be hidden. If someone has the fingerprint for an "official" 1.6 device, they could change their fingerprint to that and conceivably have the best of both worlds (protected apps AND 1.6+ apps).
How To Change Your Build Fingerprint:
--------------------------------------------
1. Connect your phone.
2. Pull /system/build.prop | For Mac users: ./adb pull /system/build.prop ./
3. Using your favorite editor, find the line that starts with ro.build.fingerprint and put a # in front of it.
4. On a new line, put: ro.build.fingerprint=sprint/htc_heroc/heroc/heroc:1.5/CUPCAKE/85027:user/release-keys
5. Save the file.
6. Remount the filesystem as read/write | For Mac users: ./adb remount
7. Log into the phone | For Mac users: ./adb shell
8. Exit the shell by typing: exit
9. Now push the file back. | For Mac users: ./adb push ./build.prop /system/build.prop
10. Reboot | For Mac users: ./adb reboot
11. Go to Market, and install something to send out the new fingerprint.
12. Within a few minutes you should see all apps. If not, try rebooting. If still not, try clearing Market's cache (Settings->Applications->Market->Clear Cache)
--------------------------------------------
Hope this helps someone.
-TM
This affects the MoDaCo rom I installed, and the AOSP 1.6 rom I was playing around with. Things like WeatherBug Elite, and tons of other stuff are hidden from the Market. In the case of MoDaCo, which I installed overtop my existing 1.5 stock (after backing up of course) the apps ran fine since they were grandfathered in from the stock rom, but still weren't listed in the marketplace. I'd really appreciate any help, as these speedy roms are useless if I can't run any of my apps on them.
search is king
this should help you
Link here
This reply isn't valid anymore and may be deleted.
Can you please post the code for this. I'm having a hard time getting this to work. Thanks
dathryl said:
Can you please post the code for this. I'm having a hard time getting this to work. Thanks
Click to expand...
Click to collapse
Code for what? What problems are you having?
Newbie question, how do you "pull" the file. I'm on shell but don't know what to input in order to edit the file.
PRGUY85 said:
Newbie question, how do you "pull" the file. I'm on shell but don't know what to input in order to edit the file.
Click to expand...
Click to collapse
You need to have ADB installed (which you do if you've rooted your phone, as ADB is required to do so). So you'd need to go into a command prompt (Windows) or Terminal (Mac), navigate to your adb/tools directory (that has adb.exe in it) and type "adb pull fileonyourphone fileonyourcomputer". Obviously replace fileonyourcomputer with the actual paths and filenames of what you're pushing/pulling. When you push the file back to the Hero, you swap the syntax, so it'd be "adb push fileonyourcomputer fileonyourphone".
OK, sorry again for noobness...
He says adb remount as read write, how do I do that?
He says log in to the phone...how do I do that on the shell?
So just to be sure, this fix will allow me to download the apps that I just can't find on the market that my friends with stock Heros can, right?
Someone recommended a new twitter client (twicca) but I couldn't open it on the market and I'm assuming it's because I'm running AOSP 1.6.
Thanks.
I just did this, and it seemed to work, but when Weatherbug Elite was downloading the phone went into the "Android" boot screen and just looped it over and over. After a battery pull it still won't boot up, and it keeps getting stuck at the boot screen. Is there anyway to fix this?
sure is nice to have sufbs back.
thanks for this.
Thanks, worked like a charm.
I jumped the gun installed the original and the latest 2.1 leaks, so I am not rooted. I just recently learned how to use the ADB push feature in the tools of the Android SDK to install a custom boot animation and I'm stoked at how awesome it works.
I was wondering what all you can use the ADB push feature for on a NON-rooted Eris. Any help is greatly appreciated.
Thanks devs for all your hard work!
Adding custom boot images.
Thanks jcase! I was seriously hoping that there was there would be other things that I could use it for. Oh well, guess I'll just wait until the Official OTA 2.1 is released, then wait until you genius devs crack it open and get it rooted. Thanks again!
You can make a script to quickly install apps in mass.
#!/bin/sh
echo "Installing apps..."
./adb install apps/app1.apk
echo "app1 Installed."
./adb install apps/app2.apk
echo "app2 Installed."
./adb install apps/app3.apk
echo "app3 Installed."
./adb install apps/app4.apk
echo "app4 Installed."
./adb install apps/app5.apk
echo "app5 Installed."
echo "done"
how do i install ADB on my computer. I downloaded SDk and in the tools when i click or ADB or Emulator it opens and instantly disappears. im running windows 7.
interscion said:
how do i install ADB on my computer. I downloaded SDk and in the tools when i click or ADB or Emulator it opens and instantly disappears. im running windows 7.
Click to expand...
Click to collapse
....
EDIT: check your inbox interscion, I sent you a message in order to keep this thread uncluttered and on subject.
Android22 said:
....
EDIT: check your inbox interscion, I sent you a message in order to keep this thread uncluttered and on subject.
Click to expand...
Click to collapse
would you send me one too i have sdk setup and when i click adb a screen pops up and disapears ,,, help!! please please
trhanks
PM
Jimmie's 2.1 Eris said:
would you send me one too i have sdk setup and when i click adb a screen pops up and disapears ,,, help!! please please
trhanks
Click to expand...
Click to collapse
Sent, check your inbox...
I know this is an old thread, but I just got a replacement eris and i'm trying to avoid signing into the market before I root (for a completely clean install, probably doesn't matter, I'm just funny like that), in which case, I want to install 1-click root before I do anything. So, if someone could point me in the right direction to do an adb install on an un-rooted eris, that would be great.
demmo86rt said:
I know this is an old thread, but I just got a replacement eris and i'm trying to avoid signing into the market before I root (for a completely clean install, probably doesn't matter, I'm just funny like that), in which case, I want to install 1-click root before I do anything. So, if someone could point me in the right direction to do an adb install on an un-rooted eris, that would be great.
Click to expand...
Click to collapse
No need to bypass activation, skip account setup, Settings->Applications->Unknown sources, Settings->Applications->Development->USB Debugging.
Then this plus this:
Code:
adb install erisone010.apk
You are making unnecessary work for yourself - if you want a Nandroid backup of the factory ROM in a near virginal state, root the phone with OneClick (so that a custom recovery gets installed) - NOT including insallation of the engtools (or rootme, whatever it is called), and then perform a factory reset afterwards. (That will clear accounts & account data from the phone, and you can then boot to the recovery to make a backup of the virginal ROM).
bftb0 said:
No need to bypass activation, skip account setup, Settings->Applications->Unknown sources, Settings->Applications->Development->USB Debugging.
Then this plus this:
Code:
adb install erisone010.apk
You are making unnecessary work for yourself - if you want a Nandroid backup of the factory ROM in a near virginal state, root the phone with OneClick (so that a custom recovery gets installed) - NOT including insallation of the engtools (or rootme, whatever it is called), and then perform a factory reset afterwards. (That will clear accounts & account data from the phone, and you can then boot to the recovery to make a backup of the virginal ROM).
Click to expand...
Click to collapse
That's basically what I ended up doing (got impatient and didn't wait for a reply), except I did sign in to the market and picked up 1-click that way. Thanks for your reply though, to my question asked in an attempt to feed my OCD tendencies.
Sent from my FroyoEris using XDA App
Download rar file with apk:
dump.ru/file/5037798
or
depositfiles.com/files/7sh8g638s
rar password: cea69e0419
sha1sum of apk: 80ff2925e12b8d3f2e9c0cabd5b294e6556b2e3f
Archangel one-click-root from the Archaism Team
This will give you temporary or permanent root on your Archos 101 - firmware 2.0.71
Archos are kind enough to provide a SDE firmware which can allow root access,
but involves some significant changes to the system and they say that they will
invalidate your warranty if you install it. This is a bit frightening for new owners.
Archangel solves this with a painless one-click-root which you can uninstall at any time.
It does not use the SDE developer firmware.
This was specifically designed for the Archos 101 with firmware 2.0.71 - it may work on
other Archos devices or firmwares, but has not been tested and is not recommended for them.
If you find this application useful, please donate to those great forums who have given
the android root community so much. Encourage them to keep up their great work. We are
fans of C-Skills Blog, XDA Developers and Modaco Forum.
When installed, this app will use approx 10mb of storage space. Don't run it if you don't
have that much spare.
Usage Instructions:
1) Make sure you have 10mb of space available on the internal storage
2) Make sure you are connected on Wifi
3) Run the Archangel app
4) Click to install SuperUser application
5) Click to get root!
6) Check everything is working correctly, try an app which needs root
7) Once you have root you can tick the "Permanent" root option to always have root.
8) Party Hard!
To turn off root, either just reboot, or turn off permanent root and reboot if you had
enabled it.
To uninstall, just uninstall like any other app. You may also want to use the menu item
to clean up before you uninstall.
You can create a script in /sdcard/sdcard/extraroot.sh and this will be executed as root
whenver you reboot, so you can use this to do any additional root functions you want.
Enjoy!
does this work?
anyone try yet?
I have A70 so i'm not sure if this will work for me
ohh a video demo would be nice
I think this is a scam "Permanent" root is not possible because the filesystem is a read-only filesystem. But I can be wrong.
I'll download this and try to inspect it.
I hope this works, I really want to get Titanium Backup working.
Well I haven't tried yet, but did a quick analysis on the APK:
Permissions on the APK does not seem to be too fishy:
Storage: modify/delete SD card contents
System tools: view and change WIFI state
and automatically start at boot
APK contains superuser, su and ls binaries.
It Works
jsperri: I saw the same as you when I looked at it.
I did install it and it seems to be working. I was able to go su from the terminal and backup an app with Titanium Backup.
I can also confirm that if permanent root is checked this will still work after reboot. When I was looking at the app it looked like it plugged into the launcher process. So perhaps it is just starting just after android is loaded.
Although I have not verified, I suspect that /system is still read only because of squashfs.
What bothers me is first the dates within the apk are 29/2/2008 for all files.
Then the binaries su is a gzipped binary superuser is a gzipped superuser.apk BUT ls is not compressed.
Why do they need ls the ls of the ROM should work fine. I suspect a trojan but i'm not sure. I could be paranoid but a rar with passwords come on......
xdaAlan said:
jsperri: I saw the same as you when I looked at it.
I did install it and it seems to be working. I was able to go su from the terminal and backup an app with Titanium Backup.
I can also confirm that if permanent root is checked this will still work after reboot. When I was looking at the app it looked like it plugged into the launcher process. So perhaps it is just starting just after android is loaded.
Although I have not verified, I suspect that /system is still read only because of squashfs.
Click to expand...
Click to collapse
So xdaAlan your first post and you claim it works and what proof you can give us? screenshots maybe.....
I agree with extreme caution on files coming from the "wild" (my apologies to archaism1).
Permissions on the APK seems to be reasonably OK.
Like wdl1908 I was also puzzled about the files dates and the presence of ls binary.
Well, I'll run this Archangel beast on a resetted tablet and report here the results with proofs
The ls binary is definitely fishy I reexamined the rar file and the file dates for the readme.txt and the apk are 18/8/2009 whats up with that.......
jsperri said:
I agree with extreme caution on files coming from the "wild" (my apologies to archaism1).
Permissions on the APK seems to be reasonably OK.
Like wdl1908 I was also puzzled about the files dates and the presence of ls binary.
Well, I'll run this Archangel beast on a resetted tablet and report here the results with proofs
Click to expand...
Click to collapse
Thxs jsperri I don't have a spare unit and don't really want to reset my unit.
Does not seem to be doing much on my A32 test machine.
Just tested on my 70H, no root either ;(
What the application does is:
- install superuser apk
- does something while it says "please wait"
(ps on adb shell shows a
Code:
/tmp/ls 0x62c7a315 0x260de680
so ls may well be part of the exploit)
There is a checkbox "Permanent root" that probably just starts Archangel program on boot
(this is just my guess, based on the APK permission, and the fact there is little chance that the squashfs gets written)
Well, I'm pausing my investigation here, waiting for others feedback, hopefully positive.
There is a screenshot of the application here along with a comment from a user saying it worked on an Archos 70 IT.
hi,
i haven't been very careful about trojan risks, but i installed it on my 70it and it works!
how can i know if a trojan is instaled?
toutiwai said:
hi,
i haven't been very careful about trojan risks, but i installed it on my 70it and it works!
how can i know if a trojan is instaled?
Click to expand...
Click to collapse
Was WIFI enabled ?
How long does it take after the button says "Please wait" ?
What's next step on screen ?
Regarding the trojan risk, it's hard to say, you'd eventually want to run tcpdump to log for internet traffic on the tablet when the program is running. Also check if there are programs left (appart from Superuser) after uninstalling Archangel.
note: after install, i didn't asked to be "permanent root", but it launches "archangel" at startup anyway (but no root if i don't ask for)
wifi enabled: yes, enabled AND connected, if not it can't get "root"
how long? if wifi connected, say... 15-25 sec...
next step: nothing, the button "install root" changes in "i'm root" or something like this...
note: i had "superuser" already installed (but not rooted) before installing archangel, so it didn't asked me to install superuser
i'll try to be more precise next time if important...
archaism1,
Can you please give us some details on Archangel program, how the exploit works, why is Wifi necessary ? It would be great to trust this new tool, but it's difficult without having more details on a program coming from a dump archive and not a very well know author...
archaism1 said:
....
Archangel one-click-root from the Archaism Team
This will give you temporary or permanent root on your Archos 101 - firmware 2.0.71
Archos are kind enough to provide a SDE firmware which can allow root access,
but involves some significant changes to the system and they say that they will
invalidate your warranty if you install it. This is a bit frightening for new owners.
Archangel solves this with a painless one-click-root which you can uninstall at any time. It does not use the SDE developer firmware.
...
Click to expand...
Click to collapse
Will this work on my archos 43 Internet tablet ? Anyone brave to test and report.
http://www.appbrain.com/app/root-checker/com.joeykrim.rootcheck
anyone tried root-checker after trying this "1-click-root"? to check that it does what it claims?
I'd love to believe this, but i'm naturally sceptical.
i just tried (archos 70IT), and "rootchek" says it's ok
well at least that is promising , thanks
This does not work with Droid X System Version .621.
(Information on this post was taken from Pete's website: http://www.psouza4.com/Bionic/)
NOTE: If you were rooted on the original OTA and took the update to .602 and lost root, read the 'Droid X' notes under the how-to.
-----------------------------------------------------------------------------
How to: One Click Root for Windows 7/Vista
1. Your phone must be connected via USB data cable to your computer and be recognized.
2. If your phone is connected, but not recognized, you may need to install one of these software drivers:
-Windows universal 32-bit Motorola drivers version 5.2.0
-Windows universal 64-bit Motorola drivers version 5.2.0
3. Download this one-click root package: PetesMotorolaRootTools_v1.08.zip
4. Extract the contents of the one-click root package to a new folder on your computer.
5. Make sure USB Debugging is enabled on your device. This should be under Settings -> Applications -> Development -> USB Debugging.
6. From the new folder on your computer, double-click on Pete's_Motrola_Root_Tools.exe to begin the root process.
7. Click 'Root My Phone'.
-----------------------------------------------------------------------------
Droid X Note:
Droid X Notes
Your phone may need to be in either charging mode or PC mode or you may need to toggle it a number of times for the device to recognized correctly.
If you are trying to root from the OTA Gingerbread update and you were previously rooted, you will probably experience problems with this root method because of the pre-existence of busybox and superuser.apk. For that reason, you may need to attempt both the script method (for Windows XP users) and program executable method (Windows Vista/7 users). If you are still having problems, please follow these instructions:
Open a Command Prompt in the folder where you extracted the one-click root package (see instructions for rooting). If you are using Windows 7, you can just use Shift+Right-Click on the folder you extracted the package and choose to "Open a command prompt here". For other operating systems or versions of Windows, you may require some DOS experience or need to Google how to change directories.
In the command prompt, type the following command:
adb shell
Click to expand...
Click to collapse
If you receive any kind of error, then you may not be in the folder where you extracted ADB.exe or you may need to reboot your computer, your phone, or check the connection. You should receive an ADB prompt ending with either a # or a $.
If the line ends with a $, then run the one-click exploit for Windows XP (even if you have Windows Vista or 7) and only complete step 1.
When you have adb shell ending with a #, type the following commands:
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
Click to expand...
Click to collapse
Ignore any messages that warn you about the file not being found/missing. We're removing old copies of su/superuser which are causing this one-click root method to fail.
(credit: KevlarGibs)
Additionally, during the parts of the one-click root that reboot your phone, your phone will most likely reboot into recovery instead of into the standard Android lock screen. If this is the case, simply unplug the cable and reboot the phone manually. When you are finished rebooting, plug the phone back in again. Some people have had to reboot their PC too.
Finally, some users have mentioned that the root isn't taking affect right away for all apps. Eventually, after several reboots, the phone finally takes root. We're not sure why this is (I don't have a Droid X -- I'm just re-posting this information for brevity).
-----------------------------------------------------------------------------
Please try the Windows Vista/7 method first! It will work better for most Windows XP users.
Only use this method if the other has not worked yet.
http://www.mediafire.com/?pj5lk8u2s0zhqo8
----------------------------------------------------------------------------
Nothing you see here is my work. All credit goes to Pete and everyone he's credited. I simply created this thread on XDA using Pete's information.
Reserved for future information.
Awesome
Great tool, thanks so much!
Confirmed OTA
Works fine!!!
Awesome! Works perfectly!
Nice, I may give it a go (may sbf to 602 for a clean start)
D.
I SBF'd to .602 on my DX and the root was successful but I can't get my phone to boot into CWM Recovery. I tried following the special DX instructions but can't get the ADB Shell to show anything but a $.
Whats next for me to try to get this working?
Hi I'm trying to unroot my x2 and it keeps saying Error: you are missing adb.exe, which was packaged with this program. The adb.exe is in the same folder as all of the other files i extracted to my restore folder. Any ideas?
I will try this at thanksgiving for my dad's X
It was rooted froyo and got the ota GB and wont root. Hopefully this works
choonami said:
I SBF'd to .602 on my DX and the root was successful but I can't get my phone to boot into CWM Recovery. I tried following the special DX instructions but can't get the ADB Shell to show anything but a $.
Whats next for me to try to get this working?
Click to expand...
Click to collapse
Your preinstall is full. With Root Explorer go to preinstall/app/ and delete something (NFS). Reflash Clockwork mod. Then try again.
Sent from my PC36100 using XDA Premium App
I have just updated from 602 to 605 ota official.
Did run the process as guided above, but nothing seemed to happen on my droidX, and I cant see any super user. and did try to instal CWM to my device, its said the device has not rooted.
Any one got the same issue?
Greatdane said:
I have just updated from 602 to 605 ota official.
Did run the process as guided above, but nothing seemed to happen on my droidX, and I cant see any super user. and did try to instal CWM to my device, its said the device has not rooted.
Any one got the same issue?
Click to expand...
Click to collapse
Were you previously rooted on .602? If so, you may need to follow the Droid X notes.
Sent from my DROIDX using XDA App
This worked perfectly on my Droid X....thanks for making it so easy!!
Finally worked up the cajones to use Pete's Tools and rooted my DX. *whew*
Doing a complete TiBu right now. Couple quick questions.......
1. Is CWM installed? If so, how does one access. If not, ROM Manager perhaps?
2. Renamed blurupdater_VZW.apk to .bak to block updates
3. Any "landmines" I should NOT uninstall?
Sorry if I sound noobish but this is my only phone number and am proceeding cautiously.
Thanks
skeeterpro said:
Finally worked up the cajones to use Pete's Tools and rooted my DX. *whew*
Doing a complete TiBu right now. Couple quick questions.......
1. Is CWM installed? If so, how does one access. If not, ROM Manager perhaps?
2. Renamed blurupdater_VZW.apk to .bak to block updates
3. Any "landmines" I should NOT uninstall?
Sorry if I sound noobish but this is my only phone number and am proceeding cautiously.
Thanks
Click to expand...
Click to collapse
First of all, let me reassure you that anything you do to your phone can be reversed with a simple SBF. ^_^
Install ClockworkMod Recovery through Droid 2 Bootstrapper, then use ROM Manager to update it to the latest version.
There is plenty of things that you can remove that will cause issues =P It's pretty much trial and error, there are lists you can look up that will tell you what can and can't be removed, but regardless, always make a backup in CWM.
Sent from my DROIDX using XDA App
Thanks again.
Droid 2 Bootstrapper via Android Market will do it, one presumes?
skeeterpro said:
Thanks again.
Droid 2 Bootstrapper via Android Market will do it, one presumes?
Click to expand...
Click to collapse
You are correct.
Sent from my DROIDX using XDA App
I amaze myself sometimes. lol
Has anyone flashed working CWM via ROM Manager?
Can't say I have interest in flashing ROMs. Just want CWM for nandroid system backups actually.
STRANGE!
DroidX, 2.3.3, original Moto ROM, LauncherPro+
First time I did Pete's it worked perfectly.
After .605 OTA it had a problem, so I re-Peted.
Each time Pete tried to reboot the phone, I had to pull the battery. Eventually, the process finished and I had a rooted Droid. It's fast, stable, has fine battery life. TitaniumPro, QuickBoot, and other root-only tools work properly. Various things ask for Superuser permission, and I give it, and they work properly.
But the SUPERUSER app has disappeared. When I go to Market, it says "Installed". It doesn't appear on my app list, and was never frozen. It's there, but invisible.
Everything else works, so should I just leave it alone?
noguru said:
DroidX, 2.3.3, original Moto ROM, LauncherPro+
First time I did Pete's it worked perfectly.
After .605 OTA it had a problem, so I re-Peted.
Each time Pete tried to reboot the phone, I had to pull the battery. Eventually, the process finished and I had a rooted Droid. It's fast, stable, has fine battery life. TitaniumPro, QuickBoot, and other root-only tools work properly. Various things ask for Superuser permission, and I give it, and they work properly.
But the SUPERUSER app has disappeared. When I go to Market, it says "Installed". It doesn't appear on my app list, and was never frozen. It's there, but invisible.
Everything else works, so should I just leave it alone?
Click to expand...
Click to collapse
You should be able to find Superuser by using the search key. It's not really important to have, it just manages the superuser permissions. I think of it as a background app.
Sent from my DROIDX using XDA App
I want to root my A7+ WITHOUT installing someone elses custom rom. I just want it rooted long enough that I can push GAPPS onto it. Is there any special trick with Elocity A7+ ??
Will I only be able to do this with earlier versions from Elocity?
The reason I want to do it this way is twofold.
1) I want EVERTHING to keep working.
2) I don't want Superuser snoops.
I can work with ./adb shell on this Linux or it would be even better for someone to show me how to COMPILE the newly released source from Elocity.
Thank you all !!
Dan
as shown in this thread http://forum.xda-developers.com/showthread.php?t=1431967 you could use Z4root.apk
It allows for temporary root
Cheers !
Yes Thanks . I did Z4Root PERMANENT. Did my thing and then turned off root .
I remembered just before coming back to post here. I never used ./adb shell push this time. Couldn't get RW with ./adb so I just copied from GAPPS folder to /system/app/ using Root Explorer.
First time I copied TOO MUCH AND IT WAS IN ENDLESS LOOP.
I repaired and then copied the important stuff...Installed Gmail and then rebooted.
All is well after reboot. But I had to go through Wizard again. Now running everything !!
Dan
another thing that i find funny about this new setup is that bluetooth and foursquare only run when while im rooted????
if i turn off root they dont work
So as I said in my last post, BLUETOOTH only works while rooted. (after having rooted once) So, I wanted to use BLUETOOTH with a new keyboard. I removed Z4root, but left Superuser running in the background. Well , once again, everything seemed to run great for a week, but then things went south. I was getting a reboot loop type thing, about 5 times before it would finally boot up.
I'm not sure, but is suspect this leaves you wide open to a virus or other malicious garbage. So now I'm back to factory with no Gmail or Youtube but I'm finding workarounds.
Dan