[ROOT] [a10] Razmataz - ROOT your Allwinner a10 semiroot tablet right! - Android Software/Hacking General [Developers Only]

Follow this I've REMOVED the installer link as the problem is that tool i wrote has a risk of a perma brick!
-edit-
8:54 am August 27 2012
(me) iToast announces the Flare officially is rooted and no longer standing strong against our exploits!
if I can find my CWM files I'l post them for this tablet as well!
I don't take responsibility if you destroy your device!
Ok, download the files that are attached and make sure you have ADB
I personally get ADB from Super1click.
Extract the archive into your ADB folder
Open a ADB shell and you should see a '#' If you don't, you're screwed. if you do, just type these commands!
push app/Superuser.apk /system/app
push xbin/busybox /system/xbin
push xbin/su /system/xbin
chmod 664 /system/app/Superuser.apk
chmod 664 /system/xbin/busybox
chmod 664 /system/xbin/su
reboot
Enjoy root

reserved

last reserved

Thanks for your contribution .

john9 said:
Thanks for your contribution .
Click to expand...
Click to collapse
Ty

Hipstreet Flare
Hi seniors, can I use this to root my new hipstreet flare tablet? I want play store on my tablet.

band5 said:
Hi seniors, can I use this to root my new hipstreet flare tablet? I want play store on my tablet.
Click to expand...
Click to collapse
Yes, but I got a new method that fixes a problem that breaks it. il be posting that once i have it ready

successful rooting of Hipster Flare
I was able to root my Hipster Flare using your instructions
and Puppy Linux.
I dragged 3 files to my home folder /root
Superuser.apk
busybox
su
Java was installed and the adb application in Puppy linux
Type in terminal
Code:
adb push Superuser.apk /system/app
adb push busybox /system/xbin
adb push su /system/xbin
adb shell chmod 664 /system/app/Superuser.apk
adb shell chmod 664 /system/xbin/busybox
adb shell chmod 664 /system/xbin/su
adb shell reboot
_________________________________________

Related

Root acess in Kyros 8024

First, make this tutorial at your own risk, I'm not responsible for damage to the device. Well, let's go...
In links Add spaces please..
First install the drivers for the Android the link http : / / www . gamefront . com / files / 17282335 / PdaNetA245 . exe, download the version 1.7 on SuperoneClick link http : / / www . megaupload . com, connect your Kyros in debug mode, the folder will have 3 files superoneclick so "su-v1", "su-v2", "su -v3 ", rename the last file" su-v3 "to" su "only after you run the adb command under the folder where you extracted the superoneclick the cmd windows.
adb push su /etc/
adb push busybox /etc/
adb push psneuter /etc/
adb shell chmod 777 /etc/su
adb shell chmod 777 /etc/busybox
adb shell chmod 777 /etc/psneuter
adb shell
$/etc/psneuter
adb shell
#mount -o rw,remount/system
#cp /etc/su /system/bin/su
#cp /etc/busybox /system/bin/busybox
#cp /etc/su /system/xbin/su
#cp /etc/busybox /system/xbin/busybox
#chown 0:0 /system/bin/su
#chmod 6755 /system/bin/su
"ctrl+C"
adb install superuser.apk
reeboot your device, and.... root
I did on my device and got success...

[Q] Sharp Aquos Zeta sh02e Root

I recently purchased this device in hopes a root method would soon become available. Has anyone out there had any success? Even temporary root access would be greatly appreciated considering the amount of bloatware on this device. Thanks in advance
andyeternity said:
I recently purchased this device in hopes a root method would soon become available. Has anyone out there had any success? Even temporary root access would be greatly appreciated considering the amount of bloatware on this device. Thanks in advance
Click to expand...
Click to collapse
I really hope someone does something. I also bought one of this babies in Japan and I wish this can be tinkered with. There is an enormous potential within this phone that is locked down on DoCoMo's crappy bloatware and prohibitions. Can't use nothing: TV receiver, radio, pedometer, and all the other functions found on most Sharp phones alone.
I got some text and some files but I really don't know what to do with them or who created them. I just translated some text from Japanese and this seems like a way to get root in the device.
PLEASE. If this can be seen by someone with experience, could this be turned into an app that is useful for us non-devs? The file is attached at the bottom.
adb push sh02eunlock /data/rootkit
adb push acdbwritevalue /data/rootkit
adb push su /data/rootkit
adb shell chmod 777 /data/rootkit/
adb shell chmod 777 /data/rootkit/sh02eunlock
adb shell chmod 777 /data/rootkit/acdbwritevalue
adb shell chmod 777 /data/rootkit/su
adb shell
su
cd /data/rootkit/
./acdbwritevalue 0xc0e74998 0x80200000
./acdbwritevalue 0xc0e749a8 0x01000000
./sh02eunlock 0
cat /data/rootkit/su >cat /data/rootkit/su > /system/xbin/su
mount -o rw,remount /system /system
cat /data/rootkit/su > /system/xbin/su
chown root.root /system/xbin/su
chmod 06755 /system/xbin/su
cat /data/rootkit/sh02eunlock > /system/xbin/soff
chmod 755 /system/xbin/soff
mount -o ro,remount /system /system
chmod 755 /system/xbin/soff
sync;sync;sync
That's all I got. I really need to delete all this spy/statistics apps from the phone and without root it's impossible.

[Q] yarvik luna 474 rooting

Does anyone know how to root luna tab474 as the firmware on it is terrible, even the touch does not respond well and yarvik r not any help what so ever. My kids cant play half the games and it does not seem to support flash.
Its running android 4.0 and there seems to b lack of updates off yarvik
toiletroll said:
Does anyone know how to root luna tab474 as the firmware on it is terrible, even the touch does not respond well and yarvik r not any help what so ever. My kids cant play half the games and it does not seem to support flash.
Its running android 4.0 and there seems to b lack of updates off yarvik
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showpost.php?p=41229206&postcount=3
Tried that but no joy. Used bin4ry root and restore now have Su on it that's as far as I got so far
Sent from my HTC One S using xda app-developers app
Yarvik 474 root
The Yarvik 474 by default is "rooted", but technically is not . The busybox and the su don't work propoerly.
To make it work, we have to change them.
Preparation :
1.) download ADB,SU, Supersuser.apk ("www48.zippyshare.com/v/60795775/file.html")
2.) download busybox to the same directory ("busybox.net/downloads/binaries/latest/busybox-armv7l" )
2.b.) rename "busybox-armv7l" to "busybox".
Start the rooting:
1.) Connect your Yarvik 474 to your PC with USB "debug on"
2.) Open "DOS" terminal on your PC and type:
adb devices
adb remount
adb shell "mkdir /data/busybox"
adb push busybox /data/busybox/busybox
adb push busybox /system/sbin/busybox
adb push su /system/sbin/su
adb push Superuser.apk /system/app/
adb shell
chmod 644 /system/app/Superuser.apk
mv /bin/su /bin/su2
mv /bin/busybox /bin/busybox2
cd /data/busybox
chmod 04755 busybox
chown root.root busybox
./busybox --INSTALL /system/sbin
cd /system/sbin
chmod 04755 su
chmod 04755 busybox
chown root.root su
chown root.root busybox
cd /bin
ln /system/sbin/su su
ln /system/sbin/busybox busybox
3.) restart your tablet
You have a full rooted Yarvik 474!!!

[GUIDE][ROOT] Root almost any china android phone

Use any 1 of the following methods.
I have personally tried these on 2 of my china android phones.
1. Using linux {Recommended}Install Ubuntu or DebianEither
Install the android-sdk.
dl.google.com/android/adt/adt-bundle-linux-x86-20130717.zip <==x86
dl.google.com/android/adt/adt-bundle-linux-x86_64-20130717.zip <==x86_64
or
Just get the standalone adb and fastboot executables
texasice-cream-sandwich-mirror.googlecode.com/files/adb_fastboot.zip​Install ia32-libsRun this in a terminal
Code:
sudo apt-get install libc6-i386 lib32stdc++6 lib32gcc1 lib32ncurses5
Now download the files required for root and put it in the same folder as adbmir.cr/GDEPZT4V​After you finish installing the files,
Connect your device with debugging mode enabled
Run
Code:
cd path/to/adb
where "path/to/adb" is the directory of your adb file
Now run
Code:
sudo chmod a+x adb
sudo chmod a+x fastboot
>>Root
Code:
./adb devices
./adb push psneuter /data/local/tmp/
./adb push busybox /data/local/tmp/
./adb push su /data/local/tmp/
./adb push Superuser.apk /data/local/tmp/
./adb shell
Chmod and run the exploit under adb shell
Code:
cd /data/local/tmp/
chmod 755 psneuter
./psneuter
Now re-engage an adb shell to check if the exploit worked.
Code:
./adb kill-server
./adb devices
./adb shell
If you see a # sign, the exploit was was successful. Otherwise repeat from >>Root
Now run these on the same adb shell
Code:
cd /data/local/tmp
./busybox ash
mount -o remount,rw /dev/block/mtdblock0 /system
cp /data/local/tmp/su /system/xbin/su
chmod 6755 /system/xbin/su
chown 0.0 /system/xbin/su
cp /data/local/tmp/Superuser.apk /system/app/Superuser.apk
chmod 777 /system/app/Superuser.apk
cp /data/local/tmp/busybox /system/xbin/busybox
chmod 6755 /system/xbin/busybox
Now reboot your device and open up SuperSU. Let it update the binary.
Your device should be rooted. ​2. Use Windows + MoboroboMethod 1 {Recommended but hard}
Download Moborobo from
Code:
moborobo.com
This software can Install drivers for many china phones and other branded phones.
After installing Moborobo download the files required for root
Code:
mir.cr/GDEPZT4V
Extract the files to the installation directory of Moborobo.
Code:
C:\Program Files (x86)\Moborobo
Run a CMD window under that directory and type
Code:
xcopy AndroidInterface.exe adb.exe
Connect your device in debugging mode & Open up Moborobo, It will install the drivers.
Keep Moborobo open & Follow the instructions mentioned in >>Root
P.S- the linux commands begin with a "./" remove this in windows or else it won't work. Note: Wherever I mentioned a terminal, the windows equivalent to this would be cmd​Method 2 {Easier}
Download and Install Moborobo just like above and run this under a cmd on that folder
Code:
xcopy AndroidInterface.exe adb.exe
Also download UnlockRoot or SuperOneClick
To make sure the adb files are of the same version, Copy over
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
to UnlockRoot's tools directory or SOC's ADB directory
Connect your device in debugging mode and open up moborobo.
Now keep Moborobo open and Run UnlockRoot or SOC. ​Good Luck :good:
---Smo0thK, team BL4CKF1R3---
Click thanks if I helped you.
[/COLOR]
Hi there!
under method 2 in the end...I could not locate ROOT nowhere.....
>>Root
arena1 said:
Hi there!
under method 2 in the end...I could not locate ROOT nowhere.....
Click to expand...
Click to collapse
I said follow the instructions mentioned in ">>Root".
I named a step in Method one as ">>Root". So I meant you should repeat those steps.
Now download the files required for root and put it in the same folder as adb
mir.cr/GDEPZT4V
Click to expand...
Click to collapse
What files?
EDIT: managed to do all the steps using method 1 in windows but got this message with executing ./psneuter :
mnmap() failed. Invalid argument
I used windows to root
failed at adb shell psneuter command...
/system/bin/sh: psneuter: not found
how to proceed ?

[TUT] How-To Root Fire HD 7, 8, and 10 6th, 7th, and 8th generation

Edit: Someone pointed out the title is not completely accurate, so I changed it to be more descriptive and I will add a list of devices this root method will work with here
Edit2: Thanks to @Rortiz2 for the automated method! You can download it here! Simply extract the files and run MTK-SU.bat to install the SuperSU app and root your device. Once you reboot after the batch script has completed, simply open SuperSU, go to settings, and ensure that default root access for apps is set to grant.
Fire HD 8 8th gen (2018) (thanks @xyz`)
Fire HD 8 7th gen (2017)
Fire HD 8 6th gen (2016) (thanks @bibikalka)
Fire HD 10 7th gen (2017) (thanks @bibikalka)
Fire TV 2 2015 (mt8173-based) (thanks @el7145) -- up to firmware 5.2.6.9
Fire 7 9th gen (2019) (thanks @Michajin)
Before trying this root method, please read through this entire post: 5 and make sure it will work for your device!
Note: I did not create these methods, all credit goes to @diplomatic and @dutchthomas
I simply wanted to put it into a single forum post with easy instructions.
With that out of the way, lets get started.
Only use this for Fire OS 5.x.x.x, I haven't tested it with the latest version, but it should still work.
First, follow these instructions by diplomatic:
After you have verified that you have access to a root shell (The '[email protected]:/ $' will change to '[email protected]:/ #) you can follow these steps by dutchthomas:
1. Install SuperSu from Playstore (if you do not have the playstore installed, you can follow the guide by @Gilly10 here https://forum.xda-developers.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603)
2. Download SuperSu and unzip somewhere (download the .zip from here)
3. Inside the UPDATE-SuperSU-v2.79-20161211114519.zip there should be an arm64 folder. Copy that folder to your platform-tools folder
Most of this is just going to be copy paste commands
4. adb push arm64/su arm64/supolicy arm64/libsupol.so /data/local/tmp
5. adb shell
6. cd /data/local/tmp
7. ./mtk-su
8. The $ after [email protected] should change to a #, if it doesn't, close the terminal and start again from step 5.
9. mount -o remount -rw /system
10. cp /data/local/tmp/su /system/xbin/su
11. cp /data/local/tmp/su /system/xbin/daemonsu
12. cp /data/local/tmp/supolicy /system/xbin/
13. cp /data/local/tmp/libsupol.so /system/lib/
14. cp /data/local/tmp/libsupol.so /system/lib64/
15. chmod 0755 /system/xbin/su
16.
Code:
chcon u:object_r:system_file:s0 /system/xbin/su
17.
Code:
chcon u:object_r:system_file:s0 /system/xbin/su
18.
Code:
chcon u:object_r:system_file:s0 /system/xbin/daemonsu
19. daemonsu --auto-daemon
20. Back on your device, open the SuperSU app and allow it to update its binaries.
After updating the SuperSU binaries, reboot your device. Once you are back to your main screen, open SuperSU, go to settings, Then scroll down to Access. Click the [Grant] option for Default Access. You need to do this because for unknown reasons the Kindle Fire is unable to show the root access popup. Your device is now fully rooted!
https://forum.xda-developers.com/showpost.php?p=79441935&postcount=629
The original thread is here: https://forum.xda-developers.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595. The title of the current thread does not accurately reflect which tablets can rooted by this method. This information is in the first post of the original thread.
MontysEvilTwin said:
The original thread is here: https://forum.xda-developers.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595. The title of the current thread does not accurately reflect which tablets can rooted by this method. This information is in the first post of the original thread.
Click to expand...
Click to collapse
Thanks for the feedback, I updated the post to be more informative!
Rortiz2 said:
https://forum.xda-developers.com/showpost.php?p=79441935&postcount=629
Click to expand...
Click to collapse
Added a link and credit to you on my post, thanks for the script!
SirHappyCatIII said:
Added a link and credit to you on my post, thanks for the script!
Click to expand...
Click to collapse
Ok.
Correction
I now realize it was obvious, but it took me a while to realize there shouldn't be two identical commands.
Instruction #17 should be #18
And #18 should be
Code:
chmod 0755 /system/xbin/daemonsu
Thanks got my Fire HD 8 (6th Gen) running Fire OS 5.3.6.4 (626536720) rooted
deleted
Hi, i followed the steps for my Fire HD 8 8th gen (2018), FireOS 6.3.0.0.
I was able to obtain temporary root access using mtk-su. Prompt is now #.
Step 9 (9. mount -o remount -rw /system) returns this error.
mount: '/dev/block/dm-0'->'/system' : Device or resource busy.
I also tried " "mount -o rw,remount /system"
And it returns this error '/dev/block/dm-0' is read-only.
So I cannot proceed any further. Your help is greatly appreciated.
PS: Your step 1 says install SuperSu from PlayStore. But it seems there isn't a ChianFire SuperSu available in PlayStore. And how is this related to the rest of the steps?
mxj_xda said:
Hi, i followed the steps for my Fire HD 8 8th gen (2018), FireOS 6.3.0.0.
I was able to obtain temporary root access using mtk-su. Prompt is now #.
Step 9 (9. mount -o remount -rw /system) returns this error.
mount: '/dev/block/dm-0'->'/system' : Device or resource busy.
I also tried " "mount -o rw,remount /system"
And it returns this error '/dev/block/dm-0' is read-only.
So I cannot proceed any further. Your help is greatly appreciated.
PS: Your step 1 says install SuperSu from PlayStore. But it seems there isn't a ChianFire SuperSu available in PlayStore. And how is this related to the rest of the steps?
Click to expand...
Click to collapse
what are you looking to do? If you have root access then you can unlock... This thread is kind of old....
https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496
i get this error when i try and download the release 22 zip file
C:\Users\cod3w\AppData\Local\Temp\kKb_tka2.zip.part could not be saved, because the source file could not be read.
Try again later, or contact the server administrator.
Can this be used on the Fire HD 10 8TH GEN?
This guide should be updated. There's no more SuperSU on the Play store. I believe that it hasn't been updated for quite a while before it was taken down. There should be a more updated guide somewhere.
Hi.
I have a Fire HD 8 (6th Generation) ...OS 5.6.8.0 (626542120).
please i use which prosedure for root?
I get a question mark after the 1st command.
PS C:\adb> adb push arm64/su arm64/supolicy arm64/libsupol.so /data/local/tmp
[ ?] /data/local/tmp/libsupol.so
If i continue, it will fail with:
[email protected]:/data/local/tmp $ ./mtk-su
/system/bin/sh: ./mtk-su: not found
Will keep digging, i'm on a fire hd 8 6th gen on 5.3.6.4
I'm only using a very small adb pack, maybe it's that, but i am able to commuinicate.
Will keep at it.
PS: Thank you so much for making this guide, hopefully i can breath some life into this now quite slow tablet.
EDIT: MTK was missing from all folders?
Heres the whole list of commands, now fails on the last part, daemon
PS C:\adb> adb push arm64/su arm64/supolicy arm64/libsupol.so /data/local/tmp
[ ?] /data/local/tmp/libsupol.so
PS C:\adb> adb shell
[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ ./mtk-su
UID: 0 cap: 3fffffffff selinux: permissive
[email protected]:/data/local/tmp # mount -o remount -rw /system
[email protected]:/data/local/tmp # cp /data/local/tmp/su /system/xbin/su
[email protected]:/data/local/tmp # cp /data/local/tmp/su /system/xbin/daemonsu
[email protected]:/data/local/tmp # cp /data/local/tmp/supolicy /system/xbin/
[email protected]:/data/local/tmp # cp /data/local/tmp/libsupol.so /system/lib/
[email protected]:/data/local/tmp # cp /data/local/tmp/libsupol.so /system/lib64/
[email protected]:/data/local/tmp # chmod 0755 /system/xbin/su
[email protected]:/data/local/tmp # chcon ubject_r:system_file:s0 /system/xbin/su
[email protected]:/data/local/tmp # chcon ubject_r:system_file:s0 /system/xbin/su
[email protected]:/data/local/tmp #
hcon ubject_r:system_file:s0 /system/xbin/daemonsu <
[email protected]:/data/local/tmp # daemonsu --auto-daemon
/system/bin/sh: daemonsu: can't execute: Permission denied
126|[email protected]:/data/local/tmp #
Need to allow permissions i guess but not sure how.
Have tried the other mtk method in the thread mentioned in the OP and have this in powershell, different response to the adb push.
PS C:\adb> adb push .\mtk-su /data/local/tmp
[100%] /data/local/tmp/mtk-su
PS C:\adb> adb shell
[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 mtk-su
[email protected]:/data/local/tmp $ ./mtk-su
UID: 0 cap: 3fffffffff selinux: permissive
[email protected]:/data/local/tmp #
help
Ok so i managed to root using the mtk-su app from here:
Releases · JunioJsv/mtk-easy-su
Get bootless root access with few clicks. Contribute to JunioJsv/mtk-easy-su development by creating an account on GitHub.
github.com
Now i do have magisk and super su installed but there is no prompt from any root request, however it does say i am rooted according the supersu root checker, plus magisk safetynet fails, so i'm at a loss now.

Categories

Resources