Related
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
Hey guys in this tutorial i will show you how to root the Samsung Galaxy Exhibit from Metro PCS, model SGH-T599N.
The phone comes Stock with Android Jelly Bean 4.1 Jelly Bean. This will also work on 4.1.2 Jelly Bean.
So lets get started.
There is a tutorial video at the bottom of the page
WARNING:
THIS WILL MOST LIKELY VOID YOUR WARRANTY.
YOU DO THIS AT YOUR OWN RISK, THERE IS A CHANCE YOU COULD BRICK YOUR PHONE.
What you will need:
1) A Samsung Galaxy Exhibit SGH-T599N
(To check your model number, go to Settings / About Device / Model Number)
2) A PC running Windows (XP, Vista, 7, 8 or 8.1)
3) A Usb Cable
4) Rooting program called VROOT
Step 1:
You need to download the VROOT rooting program.
https://www.dropbox.com/s/f85okpyc1u33zgt/Galaxy_Exhibit_Root.zip
Once the link is downloaded, extract the zip. You will get a .exe file called VRoot_1.7.3.4863_english_cid1005_7337ba1e_89.exe
Run the VRoot_1.7.3.4863_english_cid1005_7337ba1e_89.exe You will be greeted with the VROOT Setup Screen.
Click the Next button. You will be taken to the screen where you can chose where the installer, installs the program. You can chose a directory or use the default. Use the default.
Click the Next button. The next screen will ask you if you want the program to be put in your Start Menu, this is up to you.
Click the Next Button. The next the screen will ask if you want to place a Shortcut on your desktop, again this is up to you.
Click the Next Button. The program will now install it self. It should only take a couple of seconds. once the installer is done you will see the Setup Complete screen. Make sure the Launch VROOT box has a check in it and click the Finish Button.
The VROOT program will open. You will see a screen saying Device is connecting. After a moment the program will install daemon.
Step: 2
For the program to recognize you phone, you will need to turn on Usb Debugging on, on your phone. To do this on your phone go to Settings / Developers Options
Scroll down to the Debugging Section. Look for USB debugging and click on it.
A warning will pop up saying Allow USB debugging, select OK
After you turn on Usb Debugging a second warning should pop up on your phone asking if you wanna allow Usb debugging between your computer and phone. Check the always allow and then OK. Checking Always makes it so you do not have see that warning everything. Your computer and phone will allow debugging connect every time you connect in that mode.
Step 3
Now back on your PC you should see VROOT trying to connect to your phone. Once it connects you should see your phones model number on the screen. T599N
VROOT will now check to see if your phone already has root permission. VROOT will tell you, you do not have root.
The green root button in the bottom right corner should now be available. Press the Root button.
You will see the Rooting now screen. This should only take a moment to complete.
When VROOT is done, you will see a screen saying Success, your T599N is rooted. Rebooting.
You can now click complete, you are done with the VROOT program.
Step 4
You Exhibit will now reboot back into the Android OS
Once you are back at your home screen, open the app drawer in the bottom right hand corner to show all your phone apps. Scroll all the way to the right. You should now have two new apps installed on your phone. Superuser and one that is in Chinese. The one in Chinese was installed when VROOT told you it was installing daemon. You will no longer need that app.
The Superuser app is the one we want. This app regulates which app you grant root permission to. Just open the app. Make sure it does no tell you, you do not have root permission.
Now my suggestion here is to get a different app to do the same thing. The one you should use is SuperSU by Chainfire from the Play Store. Go to the Play Store and in the search look for SuperSU. There are 2 verions, a free one and a paid one. The free on works just fine.
Install this version. You will now have a app that looks like a Superman symbol with a # inside of it. Open the app. Make sure SuperSU does not tell you, you do not have root.
Now anytime a app requests root, a warning will pop up from SuperSU asking if you want to allow that app root access.
You have the option to Deny or Grant that app root. You can also check the Ask again box. If you check this box and Grant a app root, after some time SuperSU will pop up again asking the same thing. If you chose to Grant a app root without checking the box, that app will have full root access anytime you use it.
If you Deny it then the app will not have root access and not work the way it was ment to.
And that's it guys. You now have root access on your Metro PCS Samsung Galaxy Exhibit SGH-T599N
Video Tutorial
https://www.youtube.com/watch?v=SzUpbP55k30
Checkout my blogger page for these instructions with lots of pictures.
Checkout my Youtube page also
If this helped in any way please leave a comment of say thanks.
Can anybody here confirm that this method works? My mothers phone is in need of rooting and I want to make sure this won't brick her phone.
Same question
any verification this will work? Thanks in advance.
dadlovsyall said:
any verification this will work? Thanks in advance.
Click to expand...
Click to collapse
I can verify that this rooting method works. 100%. It's simple and easy to do. I'd recommend it.
Rooted my wifes t599n , metro pcs, stock rom. Worked perfect exept now i can't remove he chinese superuser app, i can disable, but new superuser will not install over it.
Never mind, got it.
sent from my lgms323 towelrooted waiting on cstom rom
brentwago said:
Rooted my wifes t599n , metro pcs, stock rom. Worked perfect exept now i can't remove he chinese superuser app, i can disable, but new superuser will not install over it.
Never mind, got it.
sent from my lgms323 towelrooted waiting on cstom rom
Click to expand...
Click to collapse
How did you get it?
jeankeeRD said:
How did you get it?
Click to expand...
Click to collapse
Found it in one of the cleaner apps on there, don't remember which one tho, sorry I went through like 6 of them that day.
sent from my lgms323 towelrooted waiting on custom rom
brentwago said:
Found it in one of the cleaner apps on there, don't remember which one tho, sorry I went through like 6 of them that day.
sent from my lgms323 towelrooted waiting on custom rom
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2843809
still working, EXE auto-updated, then i followed simple instructions, and the device rebooted with root.
vroot does install its own Super User Permission Management app, and a System Cleaner app (which are both actually useful), and some other junk (i uninstalled this). all their apps seem to have links to their other apps/appstore, but as long as you ignore them the apps themselves seem to be harmless enough.
Download the latest tools from the AFH link near end of post. It includes the changes in the attached "jobs" zip. You only need "jobs" if you downloaded the tools before May 11
EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
UPDATE May 17: Install Other Launcher and Install Kingroot tools may not complete if Windows username has spaces. I'll fix in next update. Until then, if your username has spaces, use this fix.
Here are tools for the 2014 Fire HD 6 and 7. A little late, I know, but some of you who still troll the forums may find them handy. Download the tools from AFH link, extract and run RUNME.bat.
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
Tested working on OS 5.1.2.1 and below, except:
- Current Kingroot can't root 5.1.2.1. You need to downgrade. See "ROOT OS 5.1.2", below.
- OS 4: Only OTA blocking is implemented in the Block/Unblock jobs. [5/13/16 UPDATE: Also, Play Store isn't working on OS 4.
.. I probably won't fix it unless there's some demand. Try the video guide here. OS 4 users, also see post #11 for useful info about custom launchers.]
THE TOOLS
Install Play Store
Install Nova Launcher to /priv-app [root]
Install Other Launcher to /priv-app [root]
Uninstall priv-app Launchers [root]
Install Apps
Block/Unblock: OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH [root]
Root Checker
Device Info
Root Tools
Install Kingroot ~ Root ~ Block OTA
Replace Kingroot with SuperSU [root]
DESCRIPTIONS
Before running a job, look here for any tips and instructions. This info is also in the readme.txt in the zip
INSTALL PLAY STORE - Like it says. Works on both rooted and unrooted OS 5. Not for OS 4. EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
INSTALL NOVA LAUNCHER - Installs Nova to /system/priv-app so widgets work. If you just rooted, make this your first custom launcher. You can replace it or add a different one later.
INSTALL OTHER LAUNCHER Installs the launcher app in user_launcher folder to priv-app. Get the apk for the launcher you want (from apkmirror.com for example) and put it into the folder and run the job. EDIT 5/16/2016: Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.)
HOW TO INSTALL GOOGLE NOW (also in Readme.txt):
It's much easier to install Google Now if Amazon is blocked, and you need a custom launcher to do that.
1. If you don't have a custom launcher installed, use Install Nova tool (installs Nova and blocks Amazon)
If you have a custom launcher, block Amazon so your custom launcher is running.
2. Get Google Now (small) from apkmirror.com, e.g., put into user_launcher folder and run Install Other Launcher job.
You'll boot to your "other" launcher
3. Run Google Now in app drawer and:
If prompted to Update Google App (Get it from Google Play), do it.
If prompted that other launcher is default, tap link to go to Amazon Settings. In Apps & Games>Manage all Applications: Swipe to All, scroll to your other launcher, tap it and see if "Launch by Default" is on. If yes, Clear Defaults. If no, go to your launcher settings and see if you can turn off default there.
Some launchers don't give up their default easily. If pressing home key doesn't show "Select Home App" after doing the above, run Block/Unblock tool and switch to Amazon. Then block Amazon again. After restart, press home key and you'll get "Select Home App" and be able to choose Google Now.
UNINSTALL LAUNCHERS - Uninstalls and deletes everything associated with a launcher installed to /priv-app. If multiple, prompts you to choose the one to uninstall.
INSTALL APPS - Installs all the apps in the user_apps folder. Put the apks into the folder and run the job. Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.) Don't install a launcher with this; use one of the launcher tools.
BLOCK/UNBLOCK - OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH
Except for OTA, these work only on rooted OS 5. OTA does a soft block on unrooted OS 4, hard block on rooted.
OTA: Disables update packages and renames DeviceSoftwareOTA.apk for a "hard" block. Unblock reverses it.
ADS: Blocks/unblocks the lockscreen ads.
AMAZON LAUNCHER: Block disables the stock launcher (Amazon UI) and the Appstore, which forces the home key to use your custom launcher. Unblock switches you to Amazon. Checks for custom launcher before disabling Amazon. Black screen with multiple custom launchers: If you haven't set a default launcher, disabling Amazon will boot to black screen. (System doesn't know which launcher to use.) Press home key (circle at bottom) for launcher choices. TIP: To easily switch between your launcher and Amazon, use @bibikalka's guide here to set up "one-tap switching" from launcher home screen.
APPSTORE: Blocks the appstore so in-app links take you to the Play Store (instead of throwing that stupid Appstore prompt). Amazon complains bitterly if you run this from Amazon UI, so use it at your custom launcher or just use the Amazon launcher block.
AMAZON SEARCH: If you have Google Search installed, blocking Amazon Search makes your launcher search bar use Google instead of Amazon shopping.
DEVICE INFO - Just some specs that I find interesting. Lazy man's way to find out which tablet is plugged in, OS it's running, whether rooted . . .
INSTALL KINGROOT, ROOT, BLOCK OTA - Installs Kingroot, prompts you through rooting and blocks OTA updates.
- Installs kingroot v.4.8.5 by default.
- You can skip installation if Kingroot already installed
- You can install a later version if available: Check for new versions here: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
ROOTING AND UPDATES: An update file can download while you're rooting. The Kingroot tool prevents it from installing as soon as you press Enter to tell the tool you're rooted. Then it looks for any downloaded file and if it finds one it tells you where it is and prompts you to delete.
Amazon says that updates install when the the device is not being used, but be aware that on OS 5 there's some risk. To minimize the risk, never leave the tablet idle while rooting. Just keep running Kingroot until root is successful and then press Enter to block installation of any download. (These instructions are in the tool.) To eliminate all risk, you can downgrade and root OS 4.5.3. On OS 4 the tool blocks update installation before rooting. (There's no way to do this on OS 5.) From OS 4.5.3, you upgrade with root in TWRP per bibikalka's root Tut.
True story: Kingroot once rebooted 5 times and told me "Root Failed" 3 times before finally succeeding. An update had downloaded to /cache, but the kingroot tool successfully blocked installation and found the file, which I deleted. So, although it's possible you could get upgraded, as long as you keep the tablet busy trying to root and then press Enter as soon as you're rooted, it's very unlikely.
REPLACE KINGROOT WITH SUPERSU - Installs W0lfDroid's sh script and prompts you through using it to replace Kingroot.
I reviewed and tested the script and it does (only) what it says: Removes all Kingroot (except Purify app, which tool uninstalls) and installs SuperSU. The tool uses SuperSU v. 2.4.6 for OS 5 (known working on OS 5.1.2) and SuperSU v. 2.4.9 for OS 4 (because 2.4.6 didn't seem to work).
FULL DISCLOSURE: I lost root one time after running this on OS 4. I think the problem was SuperSU 2.4.6 and that's why I changed it. I've tested many times and this only happened once, but you should know it happened. AFAIK W0lfDroid script is still the best free tool for the job.
ERRORS: Script was written to remove Kingroot from multiple android versions, so it tries to remove Kingroot files that don't exist on Lollipop. THIS PRODUCES LOTS OF ERRORS. THAT'S OK. I left in all commands so it will work on OS 4, too.
USE THIS SOON AFTER ROOTING. W0lfDroid's script should work fine even with root apps installed, but all I know for sure is it runs quick and easy on a "fresh" system.
ADB Sideload
There's an adb-sideload job in the jobs folder. I didn't put it on the menu because it uses commands that may not run on some systems. Also, if you know what you're doing, it's probably faster to manually sideload an update. If someone wants to try it, put the update bin file into adb_sideload folder and run sideload.bat.WINDOWS TESTING: Script was tested on English-language versions of Win 7 Pro and Home. Some testing on Win 10. (Thanks @SpaceBananas!) There's nothing that can hurt your tablet, but there may be kinks to work out based on Windows version. Hope a tester will work with me to help make the tools accessible to everyone. Thanks!
ADB DRIVERS REQUIRED: Try the guide in first link below. If problems, try the second.
Guide: http://forum.xda-developers.com/fir...ivers-fire-t3189000/post62561840#post62561840
Other options: http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
ROOT OS 5.1.2
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
ROOT GUIDE: Follow this guide to use Kingroot and the root tools to set up your tablet.
At this time, Kingroot can only root OS 5.1.2 (February 2016) and below.
You can downgrade OS 5.1.2.1 (March 2016) to 5.1.2 and root, as explained in Root Guide, but this is an exception!
In general, never downgrade in order to use Kingroot. It's the fastest way to a brick!
You may be able to safely downgrade a higher OS to OS 4.5.3, root, and then upgrade in TWRP per @bibikalka's root Tut. Before trying this on an OS later than 5.1.2.1, make sure the tutorial says it's safe.
DOWNLOAD THE TOOLS FROM AFH ➔ . FireHD_TOOLS v 1.2
Update as of 5/11/16
➔ If you got the tools before the update, just replace the jobs folder in FIREHD_TOOLS with the one in attached "jobs_v1.x.zip"
Change Log
5/11/2016 - v1.2: Updated sideload.bat. (Missed the Find/Findstr fixes.)
5/10/2016 - v1.1: Fixed "No such file or directory" and "Permission denied" errors for users with *nix Find command installed
.
Nice Work!
@DoLooper - Magnum Opus, no less !
Why version 0.1 ??? The first release - solid 1.0 !!!
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Updated again <sigh>. Sideload tool didn't get updated in v1.1. Apologies to those who downloaded the jobs zip.
DoLooper said:
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Click to expand...
Click to collapse
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Thanks again!
notorious.dds said:
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Click to expand...
Click to collapse
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
DoLooper said:
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
Click to expand...
Click to collapse
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
notorious.dds said:
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
Click to expand...
Click to collapse
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work? This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
BTW, how come you want to stay on OS 4?
DoLooper said:
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work?
Click to expand...
Click to collapse
Nope.
DoLooper said:
This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
Click to expand...
Click to collapse
I think I tried that to no avail, but I can't remember exactly which module I used.
DoLooper said:
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
Click to expand...
Click to collapse
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
DoLooper said:
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
Click to expand...
Click to collapse
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
DoLooper said:
BTW, how come you want to stay on OS 4?
Click to expand...
Click to collapse
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
notorious.dds said:
. . .
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Sorry to hear about the brick. Good thing Amazon is patient with us.
Yes, wallpaper works fine on OS 5. [For others who read this, on OS 4 the only way to get wallpaper is with Xposed (installed in TWRP) and the kindleBG module in the link I posted above. And BTW, although the tools don't block OS 4 Amazon launcher ATM, it can be done manually. Commands are here.]
Thanks for your input. Play store didn't work for me either this time, despite earlier success. Everything else except the launcher block (and other non-OTA blocks) does work, so for now I'm just going to edit post and see if there's any other interest in play store on OS 4. (I trust you'll get OS 5 on replacement or will want to update to it.)
As to TWRP: Once tablet is set up, booting TWRP isn't needed much except for upgrading. and bibikalka gives us lots of options for doing it.
Let us know if anything comes of UART port tests. You'd be the hero of the community!
Workaround for Windows username with spaces
The Install Other Launcher and Install Kingroot jobs may not complete if your Windows username has spaces in it. I'll fix this in next update. Meanwhile here's the workaround:
1. Right-click RUNME.bat and choose Edit. [file opens in Notepad]
2. Add a blank line under :: Set paths and run menu.
3. Type: SET "username=abc"
4. Make sure this section of RUNME looks like below and then save and close Notepad
Code:
:: Set paths and run menu.
SET "username=abc"
SET "main=%CD%\"
SET "jobsdir=%main%jobs\"
[remaining code]
This changes the username only for the tools. The rest of Windows continues to use the real username.
I'm getting ready to update. Please let me know if you found any problems.
Used the tool on my Fire HD 6 (4th Gen) running a Rooted OS 5.1.2.1 to install a new launcher and block OTA's, ads, fire launcher, appstore, and Amazon search. Everything worked without issue! Thanks for the awesome and simple to use tool! Tablet is now almost pure Android. Great work!!!
Sidenote: Used bibikalka's TUT (http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950) on my Fire HD 6 that was currently running Fire OS 4.5.3 with TWRP Recovery to obtain a Rooted Fire OS 5.1.2.1..
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
wallywallywally said:
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
Click to expand...
Click to collapse
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
sd_shadow said:
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
wallywallywally said:
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
Click to expand...
Click to collapse
yes
Sent from my KFFOWI using XDA Labs
Confirmed, this procedure worked for Fire (5th generation), however the amazon update file is different (see a few posts back)
I just got a fire HD 6 (4th Gen) with the 4.5.2 OS.
Everything I see talks about 4.5.3 and later. I have not turned on wifi, so basically in a holding pattern for now. I want to root/twrp and maybe a custom rom.
Can some give me advice on the best path to take? Should I upgrade then root? Or root then upgrade? Any advice is appreciated.
Hi,
I just bought a new unit with Allwinner R16 with Android 6.0.1 - all is working i have just few questions.
Here is the info with the versions:
MCU: 5.3.19-3-20-047101-170224
System version: V7.3.1_20161221.185302_ACX13
My Questions:
1. I tried to install AutoMate and i can't make it work with One Touch and tablet talk (can't call from the App)
2. How can i add widget to control the brightness ?
3. How can i add widget to direct dial from screen and not from Bluetooth ?
4. Reboot widget to the system ? how to reboot it ?
5. How to root it ?
Hardware info attached
Hi,you can root the unit using kingoroot APK but it not succeed in every unit.
My unit have a touch asset option in the desktop drop menu which give you widget for brightness and vol.control.
I have reboot APK you can install it .
Can you do dump of partition 11 ( flashable files) or ask your seller for a link to download your unit firmware. Thanks.
i couldn't root the device, do you have idea how can i do it?
The asset option thanks it worked.
root
Hi Alikro
I just know how to attach files to my reply,found attached kingoroot apk and reboot apk.
for kingoroot,copy apk to usb and attach it to your unit, install apk using apk install app or from file explorer. run the kingoroot with wifi enabled and follow instruction. may rooting succeed and somtetimes failed, if failed there is a trick done in my unit of 20161229-tw2 version, 2017 version will crash.
after you got failed screen ,he will give you option of reroot ,use it and black screen will appear then use reset button[small hole in the screen side] to reboot. unistall kingoroot and reset again then reinstall kingoroot and run it, if you are luky your kingoroot tell you that root accesed. then you can use any supersu from google play and if it work and given file explorer root permession,then unistall kingoroot and its supersu app and reboot.
for reboot apk ,give you option of reboot to system or flash mode option.
I hope that my notes is usefull.
I got these steps from 4PDA forum, may be a little different than my way but try it.
About getting root on the A6. That's 100% Working Instructions:
(at least I always work)
1. Install KingoRoot and chainfire SuperSU from google play
2. Connect the Internet, run KingoRoot, press the button: One Click Root.
3. As a result, after a 90% progress will see the message: ROOT FAILED - Error code: 0x1B3AB4 . SU also may rebooted (restarted).
4. In the same window click the button: Give IT another shot
5. Next, press the button again: One Click Root, again came to 90% and the same error, restart the superSU.
6. At this stage, a new SuperUser app, delete it!
7. Run SuperSU, click New User (new member), exit the application and go again. It will now be prompted to update the Super SU binary. Click "continue" and press the "Normal" button. After a successful update, SuperSU prompted to restart.
Root received!
This is a guide to debloat the KIW-AL10 and make stock Chinese usable.
First download Minimal adb and fastboot from here and install it.
Download HISuite and use that to install huawei drivers
Next Make sure developer options by hitting build number 7 times then open developer options and make sure usb debugging is activated in the developer options.
Plug phone into computer and install drivers, any unknown device will be adb so right click and select choose driver from list then select android devices then adb interface, always choose the older driver version for this phone.
One you have that installed you need to unlock your bootloader a great guide is here
Once you have unlocked the bootloader download install twrp using minimal adb and fastboot
First reboot into fastboot..
First check the device is present. using the command :adb devices
then boot into bootloader using the command : adb reboot-bootloader
if that doesn't work turn off device then switching on quickly hold down the volume down button while inserting the cable into the device
The device should then have a white screen with a robot and say unlocked in green writing
find the recovery image you downloaded and if its a different name rename it twrp.img so you know which one it is, files everywhere can get quite messy !
Now right click on the minimal adb link on the desktop and click open file location..
Now put the twrp.img file into the folder with the minimal adb files and close the window.
now flash the recovery using the command: fastboot flash recovery twrp.img
Voila if everything is sucessful your phone now has twrp recovery !
Next use the following command: adb reboot recovery, if that doesnt work force a shutdown by holding the power button then let the phone boot while holding down the volume up button, it should boot into recovery.
Next MAKE A BACKUP THIS IS VERY IMPORTANT AND WHEN ITS DONE COPY IT TO A SAFE DRIVE DO NOT KEEP IT JUST ON YOU SD CARD IN CASE YOUR CARD DIES ! BECAUSE OF THE NATURE OF THIS PHONE AND THE FACT THAT YOU CANT FLASH NON VOLTE ROMS ON THIS PHONE THIS IS YOUR ONLY WAY OF RESTORING THE PHONE SO GUARD IT LIKE YOUR LIFE DEPENDS ON IT !
Now get a cup of coffee and have a break its not good to rush things
Now to root your phone..
Finish your coffee.
Download supersu from here
Put the zip onto your phones sd card and boot into recovery, select install and select the supersu zip and let it install, once done reboot the phone, it may reboot a few times thats normal dont panic, once the phone has finished booting check you have the su app installed, if so now we can do the rest of the stuff.
Next download google play store from here and install it
After opening the play store and signing in you will probably be told to update google services, let it do it then reboot the phone
Next using the play store download root explorer
Next stage is to make the dialer English. and remove yellow pages.
Using root explorer navigate to /cust/alltelecom/cn/prop
hard press on the file local.prop and select open in text editor using the 3 dots on the top right
Look for the following lines of code ro.product.locale.region=CN or similar
Change this to ro.product.locale.region=GB (or whatever your location is such make sure the country code is in CAPS )
Save the file
Now navigate to /system and open build.prop in text editor and change the following lines of code so they end in County matching code not cn
Example
ro.product.locale.region=GB (or whatever your location is such )
ro.product.locale.language=en (or whatever your location is such )
ro.product.locale.region=GB
Go slow there is lots of lines there but you will see them if you take your time
select save and exit from root explorer then reboot.. viola the chinese and yellow pages is gone !
After reboot you may get a baidu warning about location tracking, dont panic we will kill that bugger next !
Next install system app safe remover from the play store https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_GB I always use this as its simple and keeps a backup of the removed app (just in case of problems)
Use that to remove all the chinse apps from the system including hivoice or it will interfere with google assistant, they are self explanatory
as they are all in chinese !
Next remove hi app
hi care
huawei id
network location (this is the one causing the nag screen dont worry work it will still work.
then reboot phone, there should be no more warnings about baidu location.
Now to get services google working.
You my have notice that despite installing a google account you contacts havent synced. we will fix that now..
To get google contacts to sync you need to install google contacts sync adaptor 6.0.1 from here
After you have installed it open up system apps and check it permision contacts is allowed, also open the battery setting and check it runs at boot and while screen is off, if there are no options for that ignore that bit and exit.
while you are there check google play services permission are all on especially contacts then reboot
Now install the google app from the app store
next install google assistant from the play store
now install google photos from the play store
Next install google chrome from play store
next install google calendar from the play store
next install google plus from the play store
next install google maps from the play store
next install youtube from the play store
Next install gboard from the play store
Then when all is done reboot the phone
After reboot check all the permissions of the apps and make sure all the google apps run at boot and keep running after screen off or they wont sync etc then reboot again.
Change horrible huawei keyboard to gboard in language settings
Open the google app and setup google and check your contacts have synced. set up the rest of your settings
Get a decent launcher as the huawei one sucks I use nova launcher prime its worth every penny but the free one is still good
Open settings app and click advanced, here you can change default launcher and select default app setting then select assistance and voice input, selectassist app as google select use text from screen and select use screenshot
I think that pretty much it, the rest you should be able to do yourself, have fun and good luck, any questions just ask.
I wrote this guide as there is very little info on the AL10,
Happy modding !
Very useful
Very useful post, my first venture into phone modding, enabled me to use my KIW-AL10 with Google functionality and to avoid the worst excesses of the stock Chinese software. Thanks!
Ed_shred said:
Very useful post, my first venture into phone modding, enabled me to use my KIW-AL10 with Google functionality and to avoid the worst excesses of the stock Chinese software. Thanks!
Click to expand...
Click to collapse
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
swukjay said:
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
Click to expand...
Click to collapse
So, the phone worked ok for a month, but then started restarting itself all the time. I deleted loads of apps, but it didn't solve the problem. Now, I decided to try to solve the problem by installing a custom ROM, so first step was to wipe the phone with TWRP. After wiping, I no longer had root access, and now installing SuperSU doesn't work, I can install the .zip through TWRP recovery, but I still don't have root access afterwards, according to Root Checker. Any ideas? Thanks!
Ed_shred said:
So, the phone worked ok for a month, but then started restarting itself all the time. I deleted loads of apps, but it didn't solve the problem. Now, I decided to try to solve the problem by installing a custom ROM, so first step was to wipe the phone with TWRP. After wiping, I no longer had root access, and now installing SuperSU doesn't work, I can install the .zip through TWRP recovery, but I still don't have root access afterwards, according to Root Checker. Any ideas? Thanks!
Click to expand...
Click to collapse
Repeated the process, ticked a few boxes in SuperSU, seems to be solved for now, thanks...
swukjay said:
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
Click to expand...
Click to collapse
OK, so I have tried quite a few times to install Lineage OS 14.1 and Viper, with both they get stuck in a bootloop. Trying to install Lineage with this guide https://wiki.lineageos.org/devices/kiwi/install, the 'format data' stage is not successful. I get a message saying ' E:Unable to wipe '/data' - unknown file system 'auto Unable to format to remove encryption '.
I'm not totally committed to a custom ROM, but I'd like this phone to work. Any ideas, either how to troubleshoot the ROM flashing issue, or to get the phone stable with the stock de-Chinesed stock ROM? Thanks!