Database Users

Archos 101 one-click-root for firmware 2.0.71 using Archangel

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

Question: Is it safe to log into gmail after rooting?

Hello!
So I recently rooted my Samsung Galaxy S5 (SM-G900i)
I flashed the kltedd .tar.md5 file through odin (downloaded the .tar.md5 file through Chainfire's CF Auto Root Website)
Everything worked, after going through the whole process my phone rebooted and everything seems normal.
All my data has been preserved and it all works fine.
The only problem is to check that my phone actually has root access I need to download one of those root-checker apps from the play store, but I need to sign into my Gmail account to get to the play store in the first place.
I just wanted to know if it is safe to log into my gmail account on a rooted device - is it possible in any way shape or form that I might have a sneaky keylogger or some spy-ware that could potentially see my Gmail password?
Any help would be appreciated
Sincerely, a noob to XDA Forums.

If you have rooted then there should be a SuperSU app or similar, and when you enter it it should tell you somewhere if root is working fine.
There's an easy way to check for root, which doesn't involve any app, but you need to be able to connect the phone to a PC and you will need USB drivers, and to get your hands on adb.exe (or android-tools-adb package on Linux). Assuming you've done that:
* Enable developer options. (Settings > About Phone, tap Build number 10 times, you will get a popup telling you that Settings > Developer options has appeared.)
* Enable "USB debugging mode".
* Connect via USB to the PC.
* Run `adb devices`.
* You will be asked if you want to accept the debug connection, and possible if you want to enable MTP, say "yes" to both.
* Run `adb shell`.
* Once inside the shell you can type "su[ENTER]". The terminal should freeze and you should get a popup from your SuperSU app asking if you want to grant root access to ADB. If you don't get a popup and "su" fails in the terminal, you don't have root. If you don't get a popup but you get a "#" prompt in the terminal, you have root, but you don't have a root controller app, which is not good (anybody can get root).
Another even simpler method would be to use a terminal app... provided you already have one installed. Most custom ROMs do, stock ROMs don't. Then you just use the same "su[ENTER]" stuff in the terminal.

also, you can bypass the whole thing of logging into your gmail acct and go directly into your phones main screen, go into menu, settings, about phone and tap on the build number until you see the message stating that you are now a developer, back up one step, go into developer options, check the box to allow the installation of third party apps and just download the root checker apk from elsewhere. Sounds compllicated, but its easier than CLI stuff for the uninitiated
---------- Post added at 08:45 AM ---------- Previous post was at 08:45 AM ----------
also also, ive never heard of anyone getting a keylogger after merely rooting their phones

It's technically possible if you get your "root app" from random websites. It's a golden opportunity for a hacker, you're practically begging them "please exploit my phone, I'm gonna help by running your app and bypassing all safety measures".

security should be fine as long as you dont lose your device or download apps from unsafe sites.
as for whether it is rooted or not, already answered above.
Good to see another aussie here.
I'm still a bit of a noob too but happy to help with any endevours regarding phone, especially model specific ones (I have G900I too).

wirespot said:
It's technically possible if you get your "root app" from random websites. It's a golden opportunity for a hacker, you're practically begging them "please exploit my phone, I'm gonna help by running your app and bypassing all safety measures".
Click to expand...
Click to collapse
really mate!?
i have my rooted S5 with my 3 gmail accounts logged in
and i didnt have any secuirty issue at all in past and now

Motorola 'Factory Mode'

Hello,
I very recently had to remove the FRP lock on a client's Motorola G4 Plus because he had forgot his email and password (EXTREMELY common with old people getting smartphones). I have some experience with dirtycow, Samsung modem commands injection (using Realterm) and other bypass methods. Dirtycow was not working since this phone had security update from December 2016 so I had to use an online service with remote USB support. This service required me to enter Motorola's "Factory Mode" from the boot menu.
My question is: does anyone has experience with this special mode? Is there some literature regarding special commands, COM port settings or else when in this mode, or is everything kept private by the people who provide the service? Any basic information on what it does/how it works?
For what its worth, here's how the process went:
-Connected remotely with USB Redirector
-Booted into bootloader and activated "Factory Mode". Phone boots into OS but seems to operate in a special mode.
-Technician does something. I reboot into bootloader and boot again in factory mode.
-Technician somehow is able to enable ADB in 2nd "Factory Mode" boot. (this was not possible when I had access to Settings menu through "Talkback hack")
-Reboot again in normal mode and FRP seems to be removed. Setup has been bypassed, phone boots directly to Google Now Launcher.
What did he do? What does this "Factory mode" unlocks that permits him to enable ADB and completely bypass the Setup and Google Account verification? Did he erase the PERSIST partition? Did he inject app data from an already finished Setup?
Anyways, I am currently looking into it and will open another thread when I have more information.
Thank you!

If the technician used ADB it's likely you can Google whatever command he could have used. My guess is that he either wiped a file that concerns the Setup and Google Account Verification. Maybe he completely removed GApps remotely using ADB?
Sent from my Moto G (4) using Tapatalk

ironman38102 said:
If the technician used ADB it's likely you can Google whatever command he could have used. My guess is that he either wiped a file that concerns the Setup and Google Account Verification. Maybe he completely removed GApps remotely using ADB?
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
But these Apps are system apps, which would require ROOT to uninstall... Phone did not seemed rooted and bootloader was still locked after the procedure. I would think that finding a way of disabling the Setup/Google Services apps, and then re-enabling them, you would still be stuck when trying to add a Google Account afterwards since it will check for the PERSIST/FRP lock partition. Can the PERSIST partition be wiped through ADB without ROOT? Even then, how was ADB enabled in the first place? Some special AT command?

daveribss said:
But these Apps are system apps, which would require ROOT to uninstall... Phone did not seemed rooted and bootloader was still locked after the procedure. I would think that finding a way of disabling the Setup/Google Services apps, and then re-enabling them, you would still be stuck when trying to add a Google Account afterwards since it will check for the PERSIST/FRP lock partition. Can the PERSIST partition be wiped through ADB without ROOT? Even then, how was ADB enabled in the first place? Some special AT command?
Click to expand...
Click to collapse
Actually now that I think about it, you're right you can't remove GApps without root and you can't wipe Persist partition without root. I suppose he enabled ADB because that Factory Mode maybe has some special sort of commands, but even then what use is ADB when you don't have root?
Sent from my Moto G (4) using Tapatalk

This is the command that he uses in adb:
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1

sachingodishela said:
This is the command that he uses in adb:
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
Click to expand...
Click to collapse
does anyone know the command to use in Factory Mode to enable ADB?

daveribss said:
But these Apps are system apps, which would require ROOT to uninstall... Phone did not seemed rooted and bootloader was still locked after the procedure. I would think that finding a way of disabling the Setup/Google Services apps, and then re-enabling them, you would still be stuck when trying to add a Google Account afterwards since it will check for the PERSIST/FRP lock partition. Can the PERSIST partition be wiped through ADB without ROOT? Even then, how was ADB enabled in the first place? Some special AT command?
Click to expand...
Click to collapse
Just to shed some light, adb does allow you to remove system apps or for that fact google apps without root

A tad late to the party but I'll give you a hint on the ADB enabling thing for Moto's.
Before he got ADB he probably set the device into 'factory' mode. This mode lets you send bytes to a certain TCP port via USB that sets system props. One of them is ADB enable.
There's similar tools on Youtube for repair and FRP removal like motoservice.exe
I myself reversed this years back and even found a few bytes that weren't used in the app but able to inject to change device properties.
Anyway, read this wanted to share. Motorola still has this mode, but now some devices won't let you boot factory mode.

Booting in factory mode exposes CQATest. They are using it to run shell commands, in this case to enable adb.

Inaccessible Note 4 [BROKEN DIGITIZER] - How to recover data?

Need some help, got a broken note 4 here and I want to access my files that are still stored inside it. I tried the Vysor Application to see the display but the problem is I forgot the passcode of my phone because i haven't touched that phone for over a month now.
My phone is running custom Note 7 port rom (Ditto Note 7) and I have TWRP installed as a recovery option for my phone. I tried using the adb shell comand su to my phone to remove the gesture.key but it seems that I haven't accept permissions for the adb on my device.
How do I clear the passcode of my phone? or can I clear the settings and data (without internal storage) using TWRP?
Need replies ASAP please

There's probably a few dozen (at least) threads on recovering data on XDA
Did you try the forum search?
I did and amazingly this turned up very quickly
https://forum.xda-developers.com/showthread.php?t=2339530
If that doesn't nail it, try a search yourself, it's free, and easy
Another option is to go to Find my phone/android device manager website, sign in, and unlock the phone, and then connect it to PC and copy as normal....
p.s. the denied on su is most likely because you do not have apps not apps AND adb option enabled in your superuser app under developer settings

stylemessiah said:
There's probably a few dozen (at least) threads on recovering data on XDA
Did you try the forum search?
I did and amazingly this turned up very quickly
https://forum.xda-developers.com/showthread.php?t=2339530
If that doesn't nail it, try a search yourself, it's free, and easy
Another option is to go to Find my phone/android device manager website, sign in, and unlock the phone, and then connect it to PC and copy as normal....
p.s. the denied on su is most likely because you do not have apps not apps AND adb option enabled in your superuser app under developer settings
Click to expand...
Click to collapse
Okay thanks for the reply I'll try the link above

Microphone permissions resetting after reboot on HD8 7.3.1.6

Hello. It's driving me crazy: microphone access permissions for Google Meet, Microsoft Teams, Facebook Messenger keep reverting to disabled state after reboot. I tried setting them from adb (e.g. pm grant com.google.android.apps.meetings android.permission.RECORD_AUDIO) but it behaves the same. I do not have profiles enabled, I already wiped cache from recovery, I do not know what to try next. Storage and Camera permissions remain, just the Microphone is stubborn. Please help, thank you.

Update to 7.3.1.7 (a quick bug-fix release), then go through ALL of the tablet settings and toggle every one of them back and forth one time to end up on the correct setting, even if it looks like it is already on the correct setting (sometimes it isn't).

Just received 7.3.1.7 and the problem is still there after restart. Do you have the same version and for you is the microphone permission working fine for either of the sideloaded apps?

I'm having same problem. It seems to be happening only with sideloaded apps.

Actually I take that back, I just tried facebook app downloaded from Amazon appstore and it's also happening.

Restart your Fire tablet and view logs on your Fire tablet using ADB
Code:
//Enter ADB shell
adb shell
//Start logcat
logcat
and you can see the suspected app that revokes microphone permission.