hi guys!
recently, i got a phone,i want to root it,but not success. this is the information of my phone: 1. not root,2.access bootloader,3.can use adb and fastboot .
i want to try this method:
(1). backup system partition,i copyed the whole file in /system/ to the /sdcard/system/, using RE file manager.
(2). add root file and root it
sudo cp su /sdcard/system/bin/
sudo cp busybox /sdcard/system/xbin/
sudo cp Superuser.apk /sdcard/system/app/
sudo chown root:root /sdcard/system/bin/su
sudo chmod 4755 /sdcard/system/bin/su
sudo chown root:root /sdcard/system/xbin/busybox
sudo chmod 4755 /sdcard/system/xbin/busybox
sudo chown root:root /mnt/system/app/Superuser.apk
sudo chmod 644 /sdcard/system/app/Superuser.apk
(3).make system image
sudo ./mkyaffs2image /sdcard/system/ $HOME/system.img
(4).fastboot flash it
fastboot flash system system.img
i doubt with this method,this method can root my phone???? help help
Related
Hello guys.
I'm with the Docomo Galaxy tab LTE SC-01D.
I've been trying but I can't root it nor install the CWM.
I've tried flashing the CWM 4.0.0.4 with Odin but when I try to get into recovery mode, the tablet gets stuck in the Samsung screen.
Since it's a japanese tablet, is it different to root and install CWM?
Thanks.
_ImPoSsIbLe_ said:
Hello guys.
I'm with the Docomo Galaxy tab LTE SC-01D.
I've been trying but I can't root it nor install the CWM.
I've tried flashing the CWM 4.0.0.4 with Odin but when I try to get into recovery mode, the tablet gets stuck in the Samsung screen.
Since it's a japanese tablet, is it different to root and install CWM?
Thanks.
Click to expand...
Click to collapse
Do you have any linux experience?
If yes you can do this:
mv system.img.ext4 ext4_utils
cd ext4_utils
sudo apt-get install zlib1g-dev
make
./simg2img system.img.ext4 system.img
mkdir system
sudo mount -o loop system.img system
cd ..
sudo mv su ext4_utils/system/bin
sudo mv Superuser.apk ext4_utils/system/app
cd ext4_utils/system/bin
sudo chown root.root su
sudo chmod 4755 su
cd ../app
sudo chown root.root Superuser.apk
sudo chmod 644 Superuser.apk
cd ../..
sudo ./mkuserimg.sh -s ./system ../system.img.ext4 ext4 system 687M
cd ..
tar --format=ustar -cf rootimage.tar system.img.ext4
md5sum -t rootimage.tar >> rootimage.tar
mv rootimage.tar rootimage.tar.md5
(by muneho)
If you are able to do this please be so kind to share your .tar file you make at the end so everybody can do all this a bit easier. Thanks
ps. you need to download ext4_utils, su and Superuser.apk on your linux.. then flash the final file to your phone with odin.
hi,
I have iball Slide i6012 and its brick.
Since there is no firmware for this device,I downloaded Ice Fusion v0.2.zip which is a working custom rom for this device.
My tablet can only be flash from Livesuit because other method are not possible because it stuck in the first 'Iball' logo(adb, memory card not detected).
Is it possible to make livesuit Flashable image file from this zip file?
Can anyone give me instructions?
anyone willing to help?
anyone? ???
kcisrael said:
hi,
I have iball Slide i6012 and its brick.
Since there is no firmware for this device,I downloaded Ice Fusion v0.2.zip which is a working custom rom for this device.
My tablet can only be flash from Livesuit because other method are not possible because it stuck in the first 'Iball' logo(adb, memory card not detected).
Is it possible to make livesuit Flashable image file from this zip file?
Can anyone give me instructions?
Click to expand...
Click to collapse
Found this on:
https://www.miniand.com/wiki/Allwinner/Unpacking+and+building+LiveSuit+images
---------- Post added at 10:37 PM ---------- Previous post was at 10:29 PM ----------
kcisrael said:
hi,
I have iball Slide i6012 and its brick.
Since there is no firmware for this device,I downloaded Ice Fusion v0.2.zip which is a working custom rom for this device.
My tablet can only be flash from Livesuit because other method are not possible because it stuck in the first 'Iball' logo(adb, memory card not detected).
Is it possible to make livesuit Flashable image file from this zip file?
Can anyone give me instructions?
Click to expand...
Click to collapse
Converting a ZIP ROM to a system.img
This is basically for Rockchip ROMs.
OK so first lets understand the difference.
system.img is nothing more than a image file that is formatted EXT4 and mounted in Linux.
You make the image file using DD and then format it EXT4 (or EXT3 for older devices).
Then you mount it in Linux and copy all your stuff into it.
Now this is EASY when you mount an existing system.img and copy it into a new system.img Why? Because that original system.img has all the symbolic links and permissions already set!
However, if you get a update that is a ZIP file this is not the case. Or if you get a CWM backup and untar it, you can loose the symlinks and permissions.
So one day I got a ROM that was only supplied as a zip. It used what is called a edify script to install it which that script copies all the files into system then does all the file permissions and setup up the needed symlinks.
The commands in the script do not map in Linux! Thus I had to convert them. Let me tell you this was somewhat a pain and special thanks to 900Supersport and Petrus for helping me understand and convert.
So here is how you do it.
First create a directory to unzip or un-tar all the files into. I called mine system_orig
Then this is my script to build a system.img The harder part is getting the IMG file size correct. You have to watch out making it too big as the parameter file defines how big system can be. If yours is bigger than what the parameter file allows, you will need to adjust the parameter file. I believe most parameter files today allow up to 500megs.
#create the system dir
mkdir system2
# create the system image using DD. Set size here:
dd if=/dev/zero of=system.img count=471000000
#format the image you just created. This is EXT4 but you can use anything the kernel allows as defined in init.rc
sudo /sbin/mkfs.ext4 -q system.img
#Now mount it in Linux
sudo mount -o loop system.img system2
# Now copy everything from your unzipped folder into the new image.
sudo cp -r system_orig/* system2
#OK lets create all the symbolic links
#make symlinks
sudo ln -s Roboto-Bold.ttf system2/fonts/DroidSans-Bold.ttf
sudo ln -s Roboto-Regular.ttf system2/fonts/DroidSans.ttf
sudo ln -s mksh system2/bin/sh
sudo ln -s toolbox system2/bin/cat
sudo ln -s toolbox system2/bin/chmod
sudo ln -s toolbox system2/bin/chown
sudo ln -s toolbox system2/bin/cmp
sudo ln -s toolbox system2/bin/date
sudo ln -s toolbox system2/bin/dd
sudo ln -s toolbox system2/bin/df
sudo ln -s toolbox system2/bin/dmesg
sudo ln -s toolbox system2/bin/getevent
sudo ln -s toolbox system2/bin/getprop
sudo ln -s toolbox system2/bin/hd
sudo ln -s toolbox system2/bin/id
sudo ln -s toolbox system2/bin/ifconfig
sudo ln -s toolbox system2/bin/iftop
sudo ln -s toolbox system2/bin/insmod
sudo ln -s toolbox system2/bin/ioctl
sudo ln -s toolbox system2/bin/ionice
sudo ln -s toolbox system2/bin/kill
sudo ln -s toolbox system2/bin/ln
sudo ln -s toolbox system2/bin/log
sudo ln -s toolbox system2/bin/ls
sudo ln -s toolbox system2/bin/lsmod
sudo ln -s toolbox system2/bin/lsof
sudo ln -s toolbox system2/bin/md5
sudo ln -s toolbox system2/bin/mkdir
sudo ln -s toolbox system2/bin/mount
sudo ln -s toolbox system2/bin/mv
sudo ln -s toolbox system2/bin/nandread
sudo ln -s toolbox system2/bin/netstat
sudo ln -s toolbox system2/bin/newfs_msdos
sudo ln -s toolbox system2/bin/notify
sudo ln -s toolbox system2/bin/printenv
sudo ln -s toolbox system2/bin/ps
sudo ln -s toolbox system2/bin/r
sudo ln -s toolbox system2/bin/reboot
sudo ln -s toolbox system2/bin/renice
sudo ln -s toolbox system2/bin/rm
sudo ln -s toolbox system2/bin/rmdir
sudo ln -s toolbox system2/bin/rmmod
sudo ln -s toolbox system2/bin/route
sudo ln -s toolbox system2/bin/schedtop
sudo ln -s toolbox system2/bin/sendevent
sudo ln -s toolbox system2/bin/setconsole
sudo ln -s toolbox system2/bin/setprop
sudo ln -s toolbox system2/bin/sleep
sudo ln -s toolbox system2/bin/smd
sudo ln -s toolbox system2/bin/start
sudo ln -s toolbox system2/bin/stop
sudo ln -s toolbox system2/bin/sync
sudo ln -s toolbox system2/bin/top
sudo ln -s toolbox system2/bin/touch
sudo ln -s toolbox system2/bin/umount
sudo ln -s toolbox system2/bin/uptime
sudo ln -s toolbox system2/bin/vmstat
sudo ln -s toolbox system2/bin/watchprops
sudo ln -s toolbox system2/bin/wipe
#OK now lets set all the permissions
sudo chown -R 0:0 system2
sudo chmod -R 0755 system2
sudo find system2 -type d -exec chmod 0755 {} \;
sudo find system2 -type f -exec chmod 0644 {} \;
sudo chown -R 0:2000 system2/bin
sudo chmod 0755 system2/bin
sudo find system2/bin -type d -exec chmod 0755 {} \;
sudo find system2/bin -type f -exec chmod 0755 {} \;
sudo chown 0:3003 system2/bin/netcfg
sudo chmod 2750 system2/bin/netcfg
sudo chown 0:3004 system2/bin/ping
sudo chmod 2755 system2/bin/ping
sudo chown 0:2000 system2/bin/run-as
sudo chmod 6755 system2/bin/run-as
sudo chown -R 1002:1002 system2/etc/bluetooth
sudo chmod 0755 system2/etc/bluetooth
sudo find system2/etc/bluetooth -type d -exec chmod 0755 {} \;
sudo find system2/etc/bluetooth -type f -exec chmod 0440 {} \;
sudo chown 0:0 system2/etc/bluetooth
sudo chmod 0755 system2/etc/bluetooth
sudo chown 1000:1000 system2/etc/bluetooth/auto_pairing.conf
sudo chmod 0640 system2/etc/bluetooth/auto_pairing.conf
sudo chown 3002:3002 system2/etc/bluetooth/blacklist.conf
sudo chmod 0444 system2/etc/bluetooth/blacklist.conf
sudo chown 1002:1002 system2/etc/dbus.conf
sudo chmod 0440 system2/etc/dbus.conf
sudo chown 1014:2000 system2/etc/dhcpcd/dhcpcd-run-hooks
sudo chmod 0550 system2/etc/dhcpcd/dhcpcd-run-hooks
sudo chown 0:2000 system2/etc/init.goldfish.sh
sudo chmod 0550 system2/etc/init.goldfish.sh
sudo chown 0:0 system2/etc/install-recovery.sh
sudo chmod 0544 system2/etc/install-recovery.sh
sudo chown -R 0:0 system2/etc/ppp
sudo chmod -R 0755 system2/etc/ppp
sudo find system2/etc/ppp -type d -exec chmod 0755 {} \;
sudo find system2/etc/ppp -type f -exec chmod 0555 {} \;
sudo chown -R 0:2000 system2/vendor
sudo chmod -R 0755 system2/vendor
sudo find system2/vendor -type d -exec chmod 0755 {} \;
sudo find system2/vendor -type f -exec chmod 0644 {} \;
sudo chown -R 0:2000 system2/xbin
sudo chmod -R 0755 system2/xbin
sudo find system2/xbin -type d -exec chmod 0755 {} \;
sudo find system2/xbin -type f -exec chmod 0755 {} \;
sudo chown 0:0 system2/xbin/librank
sudo chmod 06755 system2/xbin/librank
sudo chown 0:0 system2/xbin/procmem
sudo chmod 06755 system2/xbin/procmem
sudo chown 0:0 system2/xbin/procrank
sudo chmod 06755 system2/xbin/procrank
sudo chown 0:0 system2/xbin/tcpdump
sudo chmod 06755 system2/xbin/tcpdump
# Note I added this to ROOT the new ROM. I simply copied in SU and Superuser and busybox.
# However if you want stock remove this area.
# Also note, some only put busybox and SU in /bin or /xbin. I usually do both.
sudo chown 0:0 system2/bin/su
sudo chmod 06755 system2/bin/su
sudo chown 0:0 system2/xbin/su
sudo chmod 06755 system2/xbin/su
sudo chown 0:0 system2/bin/busybox
sudo chmod 6755 system2/bin/busybox
sudo chown 0:0 system2/xbin/busybox
sudo chmod 6755 system2/xbin/busybox
sudo chown 0:0 system2/app/Superuser.apk
sudo chmod 6755 system2/app/Superuser.apk
# OK now lets unmount system.img
sudo umount system2
# for clean up I usually delete system2 folder.
sudo rm -f -R system2
That should do it!
FYI, you do not RKCRC system.img.
Hope this helps
Help
azithro said:
Found this on:
https://www.miniand.com/wiki/Allwinner/Unpacking+and+building+LiveSuit+images
---------- Post added at 10:37 PM ---------- Previous post was at 10:29 PM ----------
Converting a ZIP ROM to a system.img
This is basically for Rockchip ROMs.
OK so first lets understand the difference.
system.img is nothing more than a image file that is formatted EXT4 and mounted in Linux.
You make the image file using DD and then format it EXT4 (or EXT3 for older devices).
Then you mount it in Linux and copy all your stuff into it.
Now this is EASY when you mount an existing system.img and copy it into a new system.img Why? Because that original system.img has all the symbolic links and permissions already set!
However, if you get a update that is a ZIP file this is not the case. Or if you get a CWM backup and untar it, you can loose the symlinks and permissions.
So one day I got a ROM that was only supplied as a zip. It used what is called a edify script to install it which that script copies all the files into system then does all the file permissions and setup up the needed symlinks.
The commands in the script do not map in Linux! Thus I had to convert them. Let me tell you this was somewhat a pain and special thanks to 900Supersport and Petrus for helping me understand and convert.
So here is how you do it.
First create a directory to unzip or un-tar all the files into. I called mine system_orig
Then this is my script to build a system.img The harder part is getting the IMG file size correct. You have to watch out making it too big as the parameter file defines how big system can be. If yours is bigger than what the parameter file allows, you will need to adjust the parameter file. I believe most parameter files today allow up to 500megs.
#create the system dir
mkdir system2
# create the system image using DD. Set size here:
dd if=/dev/zero of=system.img count=471000000
#format the image you just created. This is EXT4 but you can use anything the kernel allows as defined in init.rc
sudo /sbin/mkfs.ext4 -q system.img
#Now mount it in Linux
sudo mount -o loop system.img system2
# Now copy everything from your unzipped folder into the new image.
sudo cp -r system_orig/* system2
#OK lets create all the symbolic links
#make symlinks
sudo ln -s Roboto-Bold.ttf system2/fonts/DroidSans-Bold.ttf
sudo ln -s Roboto-Regular.ttf system2/fonts/DroidSans.ttf
sudo ln -s mksh system2/bin/sh
sudo ln -s toolbox system2/bin/cat
sudo ln -s toolbox system2/bin/chmod
sudo ln -s toolbox system2/bin/chown
sudo ln -s toolbox system2/bin/cmp
sudo ln -s toolbox system2/bin/date
sudo ln -s toolbox system2/bin/dd
sudo ln -s toolbox system2/bin/df
sudo ln -s toolbox system2/bin/dmesg
sudo ln -s toolbox system2/bin/getevent
sudo ln -s toolbox system2/bin/getprop
sudo ln -s toolbox system2/bin/hd
sudo ln -s toolbox system2/bin/id
sudo ln -s toolbox system2/bin/ifconfig
sudo ln -s toolbox system2/bin/iftop
sudo ln -s toolbox system2/bin/insmod
sudo ln -s toolbox system2/bin/ioctl
sudo ln -s toolbox system2/bin/ionice
sudo ln -s toolbox system2/bin/kill
sudo ln -s toolbox system2/bin/ln
sudo ln -s toolbox system2/bin/log
sudo ln -s toolbox system2/bin/ls
sudo ln -s toolbox system2/bin/lsmod
sudo ln -s toolbox system2/bin/lsof
sudo ln -s toolbox system2/bin/md5
sudo ln -s toolbox system2/bin/mkdir
sudo ln -s toolbox system2/bin/mount
sudo ln -s toolbox system2/bin/mv
sudo ln -s toolbox system2/bin/nandread
sudo ln -s toolbox system2/bin/netstat
sudo ln -s toolbox system2/bin/newfs_msdos
sudo ln -s toolbox system2/bin/notify
sudo ln -s toolbox system2/bin/printenv
sudo ln -s toolbox system2/bin/ps
sudo ln -s toolbox system2/bin/r
sudo ln -s toolbox system2/bin/reboot
sudo ln -s toolbox system2/bin/renice
sudo ln -s toolbox system2/bin/rm
sudo ln -s toolbox system2/bin/rmdir
sudo ln -s toolbox system2/bin/rmmod
sudo ln -s toolbox system2/bin/route
sudo ln -s toolbox system2/bin/schedtop
sudo ln -s toolbox system2/bin/sendevent
sudo ln -s toolbox system2/bin/setconsole
sudo ln -s toolbox system2/bin/setprop
sudo ln -s toolbox system2/bin/sleep
sudo ln -s toolbox system2/bin/smd
sudo ln -s toolbox system2/bin/start
sudo ln -s toolbox system2/bin/stop
sudo ln -s toolbox system2/bin/sync
sudo ln -s toolbox system2/bin/top
sudo ln -s toolbox system2/bin/touch
sudo ln -s toolbox system2/bin/umount
sudo ln -s toolbox system2/bin/uptime
sudo ln -s toolbox system2/bin/vmstat
sudo ln -s toolbox system2/bin/watchprops
sudo ln -s toolbox system2/bin/wipe
#OK now lets set all the permissions
sudo chown -R 0:0 system2
sudo chmod -R 0755 system2
sudo find system2 -type d -exec chmod 0755 {} \;
sudo find system2 -type f -exec chmod 0644 {} \;
sudo chown -R 0:2000 system2/bin
sudo chmod 0755 system2/bin
sudo find system2/bin -type d -exec chmod 0755 {} \;
sudo find system2/bin -type f -exec chmod 0755 {} \;
sudo chown 0:3003 system2/bin/netcfg
sudo chmod 2750 system2/bin/netcfg
sudo chown 0:3004 system2/bin/ping
sudo chmod 2755 system2/bin/ping
sudo chown 0:2000 system2/bin/run-as
sudo chmod 6755 system2/bin/run-as
sudo chown -R 1002:1002 system2/etc/bluetooth
sudo chmod 0755 system2/etc/bluetooth
sudo find system2/etc/bluetooth -type d -exec chmod 0755 {} \;
sudo find system2/etc/bluetooth -type f -exec chmod 0440 {} \;
sudo chown 0:0 system2/etc/bluetooth
sudo chmod 0755 system2/etc/bluetooth
sudo chown 1000:1000 system2/etc/bluetooth/auto_pairing.conf
sudo chmod 0640 system2/etc/bluetooth/auto_pairing.conf
sudo chown 3002:3002 system2/etc/bluetooth/blacklist.conf
sudo chmod 0444 system2/etc/bluetooth/blacklist.conf
sudo chown 1002:1002 system2/etc/dbus.conf
sudo chmod 0440 system2/etc/dbus.conf
sudo chown 1014:2000 system2/etc/dhcpcd/dhcpcd-run-hooks
sudo chmod 0550 system2/etc/dhcpcd/dhcpcd-run-hooks
sudo chown 0:2000 system2/etc/init.goldfish.sh
sudo chmod 0550 system2/etc/init.goldfish.sh
sudo chown 0:0 system2/etc/install-recovery.sh
sudo chmod 0544 system2/etc/install-recovery.sh
sudo chown -R 0:0 system2/etc/ppp
sudo chmod -R 0755 system2/etc/ppp
sudo find system2/etc/ppp -type d -exec chmod 0755 {} \;
sudo find system2/etc/ppp -type f -exec chmod 0555 {} \;
sudo chown -R 0:2000 system2/vendor
sudo chmod -R 0755 system2/vendor
sudo find system2/vendor -type d -exec chmod 0755 {} \;
sudo find system2/vendor -type f -exec chmod 0644 {} \;
sudo chown -R 0:2000 system2/xbin
sudo chmod -R 0755 system2/xbin
sudo find system2/xbin -type d -exec chmod 0755 {} \;
sudo find system2/xbin -type f -exec chmod 0755 {} \;
sudo chown 0:0 system2/xbin/librank
sudo chmod 06755 system2/xbin/librank
sudo chown 0:0 system2/xbin/procmem
sudo chmod 06755 system2/xbin/procmem
sudo chown 0:0 system2/xbin/procrank
sudo chmod 06755 system2/xbin/procrank
sudo chown 0:0 system2/xbin/tcpdump
sudo chmod 06755 system2/xbin/tcpdump
# Note I added this to ROOT the new ROM. I simply copied in SU and Superuser and busybox.
# However if you want stock remove this area.
# Also note, some only put busybox and SU in /bin or /xbin. I usually do both.
sudo chown 0:0 system2/bin/su
sudo chmod 06755 system2/bin/su
sudo chown 0:0 system2/xbin/su
sudo chmod 06755 system2/xbin/su
sudo chown 0:0 system2/bin/busybox
sudo chmod 6755 system2/bin/busybox
sudo chown 0:0 system2/xbin/busybox
sudo chmod 6755 system2/xbin/busybox
sudo chown 0:0 system2/app/Superuser.apk
sudo chmod 6755 system2/app/Superuser.apk
# OK now lets unmount system.img
sudo umount system2
# for clean up I usually delete system2 folder.
sudo rm -f -R system2
That should do it!
FYI, you do not RKCRC system.img.
Hope this helps
Click to expand...
Click to collapse
Can you help me with this ?
http://forum.xda-developers.com/showthread.php?p=46541879#post46541879
My Kindle fire hdx 8.9 worked normally since I bought it. Yesterday I remove the signature to install google service, and the wrong was it can't restart and I reset it to the factory from recovery. Now it still rest on the colored "kindle fire". But it seems some processes have been loaded because the MTP devices can be found in PC and the adb mode seems work normally. I think some steps losed in the boot. Can I recover it by adb mode or other methods? Thank you.
I reset it to the factory from recovery.
Click to expand...
Click to collapse
very bad, you lost root, so no ideas.
But try:
Code:
adb shell
su
ONYXis said:
very bad, you lost root, so no ideas.
But try:
Code:
adb shell
su
Click to expand...
Click to collapse
Yes , the root tools can work. Input su and display "[email protected]:/#". It seems something different with the bricked in forum.
tianlie said:
Yes , the root tools can work. Input su and display "[email protected]:/#". It seems something different with the bricked in forum.
Click to expand...
Click to collapse
Good.
You need put back original files:
services.odex and any others that you changed
like this:
Code:
adb shell
su
mount -o remount /system
adb push services.odex /data/local/tmp
chmod 755 /data/local/tmp/services.odex
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
or simple
Code:
adb shell
su
mount -o remount /system
rm /system/framework/services.odex
adb push services.odex /system/framework/
chmod 755 /system/framework/services.odex
reboot
ONYXis said:
Good.
You need put back original files:
services.odex and any others that you changed
like this:
Code:
adb shell
su
mount -o remount /system
adb push services.odex /data/local/tmp
chmod 755 /data/local/tmp/services.odex
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
or simple
Code:
adb shell
su
mount -o remount /system
rm /system/framework/services.odex
adb push services.odex /system/framework/
chmod 755 /system/framework/services.odex
reboot
Click to expand...
Click to collapse
"adb push services.odex /data/local/tmp" This command give an error: device not found.
Does it need the file "services.odex"? Where?
Thanks a lot.
The complete response:
D:\win32>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount /system
mount -o remount /system
[email protected]:/ # rm /system/framework/services.odex
rm /system/framework/services.odex
[email protected]:/ # adb push services.odex /system/framework/
adb push services.odex /system/framework/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ # chmod 755 /system/framework/services.odex
chmod 755 /system/framework/services.odex
Unable to chmod /system/framework/services.odex: No such file or directory
10|[email protected]:/ # reboot
reboot
Sorry. Syntax error. I am at gym now. Ill help you when come home. What version of firmware do you use?
ONYXis said:
Sorry. Syntax error. I am at gym now. Ill help you when come home. What version of firmware do you use?
Click to expand...
Click to collapse
It should be 14.3.2.5. OK. I wait you.:good:
https://www.dropbox.com/s/tfd5htc9smt17nx/Desktop.zip?dl=0
Code:
adb push C:\Users\xxx\Desktop\services.odex /sdcard/services.odex
adb shell
su
mount -o remount /system
cp /sdcard/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
If it will not help - try to put back framework-res.apk.
ONYXis said:
https://www.dropbox.com/s/tfd5htc9smt17nx/Desktop.zip?dl=0
Code:
adb push C:\Users\xxx\Desktop\services.odex /sdcard/services.odex
adb shell
su
mount -o remount /system
cp /sdcard/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
If it will not help - try to put back framework-res.apk.
Click to expand...
Click to collapse
That's great! Kindle is upgrading... Select language, register, the desktop come back.
Thank you, ONYXis, you are my god!:good:
To others, don't think the factory set is best.
Thank you again.
I've tried KingRoot but it tells me the device isn't supported. Are there any ways to install a custom recovery like TWRP or CWM?
Extract the boot.img file from "UPDATE.APP", upload it here, and I'll root it manually for you.
mann1 said:
Extract the boot.img file from "UPDATE.APP", upload it here, and I'll root it manually for you.
Click to expand...
Click to collapse
I saw your post on another thread here so I got the tools to extract it, but my knowledge is limited at ro.secure=0 and bash. If you wouldn't mind sharing I'd love to know how it's done.
I've attached the file.
Well, first you need to download the following files:
1-Your rooted_boot img from here
2-Compressed folder mann1.zip from here
===
Now lets start,
1- Unzip the rooted img then flash it, (be careful it's not tested)
2- 2- Unzip the file "mann1.zip" to get folder "mann1" then copy it directly into your device internal storage NOT the SD card. Put the the whole folder not the files inside
3-If the rooted boot worked fine, restart your device in the normal mode (NOT the recovery nor bootloader), and type the following commands one by one:
Code:
adb devices
adb root
adb shell
Now you supposed to see your root like that
[email protected]:/ #
complete the commands in the adb shell:
mount -o remount,rw /system
mount -o remount,rw /etc
mkdir /system/bin/.ext
mkdir /etc/init.d
cat /sdcard/mann1/busybox > /system/bin/busybox
cat /sdcard/mann1/su > /system/xbin/su
cat /sdcard/mann1/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/mann1/su > /system/xbin/daemonsu
cat /sdcard/mann1/su > /system/xbin/sugote
cat /system/bin/sh > /system/xbin/sugote-mksh
cat /sdcard/mann1/supolicy > /system/xbin/supolicy
cat /sdcard/mann1/otasurvival.sh > /system/xbin/otasurvival.sh
cat /sdcard/mann1/libsupol.so > /system/lib/libsupol.so
cat /sdcard/mann1/su > /system/bin/.ext/.su
cat /sdcard/mann1/su > /etc/.installed_su_daemon
cat /sdcard/mann1/install-recovery.sh > /etc/install-recovery.sh
cat /sdcard/mann1/99SuperSUDaemon > /etc/init.d/99SuperSUDaemon
chown 0.0 /system/bin/busybox
chmod 0755 /system/bin/busybox
chown 0.0 /system/app/Superuser.apk
chmod 0755 /system/app/Superuser.apk
chown 0.0 /system/xbin/su
chmod 0755 /system/xbin/su
chown 0.0 /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chown 0.0 /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chown 0.0 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
chown 0.0 /system/xbin/supolicy
chmod 0755 /system/xbin/supolicy
chown 0.0 /system/xbin/otasurvival.sh
chmod 0755 /system/xbin/otasurvival.sh
chown 0.0 /system/lib/libsupol.so
chmod 0755 /system/lib/libsupol.so
chown 0.0 /system/bin/.ext/.su
chmod 0755 /system/bin/.ext/.su
chown 0.0 /etc/.installed_su_daemon
chmod 0755 /etc/.installed_su_daemon
chown 0.0 /etc/install-recovery.sh
chmod 0755 /etc/install-recovery.sh
chown 0.0 /etc/init.d/99SuperSUDaemon
chmod 0755 /etc/init.d/99SuperSUDaemon
daemonsu -d
reboot
I assumed you already know the adb and fastboot commands to flash the boot
If everything run smoothly,after restarting your device you will find SuperSU installed, and the device is rooted w/o custom recovery.
mann1 said:
Code:
adb devices
adb root
adb shell
Now you supposed to see your root like that
[email protected]:/ #
Click to expand...
Click to collapse
I just booted the image and tried to start adb as root which it does however adb shell drops me into a regular shell, I also tried to flash it but still, no dice.
Code:
[email protected]:~/Music/root$ adb root
restarting adbd as root
[email protected]:~/Music/root$ adb shell
[email protected]:/ $ exit
I have a feeling there may be a software block inside system.img to prevent adb starting a shell as root, any idea?
adamhighdefinition said:
I just booted the image and tried to start adb as root which it does however adb shell drops me into a regular shell, I also tried to flash it but still, no dice.
I have a feeling there may be a software block inside system.img to prevent adb starting a shell as root, any idea?
Click to expand...
Click to collapse
The method works fine under Windows, but I've never tried it out under Linux.
Try this new root_boot2.img HERE (be careful it's not tested)
Pls flash it, don't just boot it:
fastboot flash boot root_boot2.img
If you get error with "adb root", skip it and keep going till the "reboot"
Good luck
mann1 said:
The method works fine under Windows, but I've never tried it out under Linux.
Try this new root_boot2.img HERE (be careful it's not tested)
Pls flash it, don't just boot it:
fastboot flash boot root_boot2.img
If you get error with "adb root", skip it and keep going till the "reboot"
Good luck
Click to expand...
Click to collapse
Just tested it, it caused a bootloop though, I cleared the cache and it still looped. I'll flash the first one and test it on windows then I'll report back.
The first one does allow me to see the Logcat output for all of the system services in Android Studio though, so it is giving elevated permissions.
Yeah, same on windows. Drops me into a normal shell.
Well, try this one
mann1 said:
Well, try this one
Click to expand...
Click to collapse
Dude thank you! I was repacking custom systems all night last night trying to install it directly into the rom.
In your mann1 folder the su binary is out of date btw
adamhighdefinition said:
Dude thank you! I was repacking custom systems all night last night trying to install it directly into the rom.
In your mann1 folder the su binary is out of date btw
Click to expand...
Click to collapse
Yvw, then this last one worked fine with you.
Su binary is extracted from the most recent version of SuperSu.apk, but in all cases we just use it to get rooted then you can update the whole package via Google play.
mann1 said:
Yvw, then this last one worked fine with you.
Click to expand...
Click to collapse
Yeah, last one worked for the Mediapad T1 8.0 Pro T1-921L.
mann1 said:
Su binary is extracted from the most recent version of SuperSu.apk, but in all cases we just use it to get rooted then you can update the whole package via Google play..
Click to expand...
Click to collapse
Must just be supersu being weird then, thanks again.
This tutorial explains how to root the kernel of any device under Linux. Here
Good luck
Hi. First sorry for my English.
I can erase they prenormal state without wait the 7 days I a A+2019 (A605GN) with binary 3 in Oreo
Need tools: ADB driver's, combination fw for ur model, stock fw, Mixplorer (or an other root file explorer), SuperSu zip, RMM bypass zip, forced encryption disabled zip and Odin 3.13.
Optional TWRP image zip, magisk zip.
First go to download mode and flash the combination fw.
Reboot ur phone when startup go to settings, enable usb debugging.
Unzip the SuperSu zip and make a bat (in Windows) or sh (in Linux) with the following code in the root of SuperSu folder
Code:
adb root
adb remount
adb push common/Superuser.apk /system/app/SuperSU/SuperSU.apk
adb shell chmod 0644 /system/app/SuperSU/SuperSU.apk
adb shell chcon u:object_r:system_file:s0 /system/app/SuperSU/SuperSU.apk
adb push common/install-recovery.sh /system/etc/install-recovery.sh
adb shell chmod 0755 /system/etc/install-recovery.sh
adb shell chcon u:object_r:toolbox_exec:s0 /system/etc/install-recovery.sh
adb shell ln -s /system/etc/install-recovery.sh /system/bin/install-recovery.sh
adb push armv7/su /system/xbin/su
adb shell chmod 0755 /system/xbin/su
adb shell chcon u:object_r:system_file:s0 /system/xbin/su
adb push armv7/su /system/bin/.ext/.su
adb shell chmod 0755 /system/bin/.ext/.su
adb shell chcon u:object_r:system_file:s0 /system/bin/.ext/.su
adb push armv7/su /system/xbin/daemonsu
adb shell chmod 0755 /system/xbin/daemonsu
adb shell chcon u:object_r:system_file:s0 /system/xbin/daemonsu
adb push armv7/supolicy /system/xbin/supolicy
adb shell chmod 0755 /system/xbin/supolicy
adb shell chcon u:object_r:system_file:s0 /system/xbin/supolicy
adb push armv7/libsupol.so /system/lib/libsupol.so
adb shell chmod 0644 /system/lib/libsupol.so
adb shell chcon u:object_r:system_file:s0 /system/lib/libsupol.so
adb shell cp /system/bin/app_process /system/bin/app_process_original
adb shell chmod 0755 /system/bin/app_process_original
adb shell chcon u:object_r:zygote_exec:s0 /system/bin/app_process_original
adb shell cp /system/bin/app_process32 /system/bin/app_process32_original
adb shell chmod 0755 /system/bin/app_process32
adb shell chcon u:object_r:zygote_exec:s0 /system/bin/app_process32_original
adb shell rm -rf /system/bin/app_process32
adb shell rm -rf /system/bin/app_process
adb shell ln -s /system/xbin/daemonsu /system/bin/app_process32
adb shell ln -s /system/xbin/daemonsu /system/bin/app_process
adb shell "echo 1 > /system/etc/.installed_su_daemon"
adb shell /system/xbin/su --install
Open a terminal with ur phone connected and run
Adb root
Adb remount
Then run ur bat or sh file in the terminal if u don't underestandme search how to install SuperSu with ADB.
Reboot the phone.
Open SuperSu and install the binaries normally.
Open Mixplorer and go to root.
Then go to dev\block and open steady with de code Editor of Mixplorer.
The file only show symbols. In the star search prenormal and change to Normal. Search an other prenormal word and change to Normal. Save the file.
Reboot ur phone in recovery mode and then to bootloader.
And the prenormal state are gonne.
Open Odin and DISABLE AUTOREBOOT AND F. LOCK.
Flash the stock FW (all AP BL CSC CL)
When finish no reboot yet. In plug and plug the phone.
Flash TWRP.
Reboot ur phone in recovery mode and TWRP should open. ???
Then flash the encryption forced disabled. And Format data. (DONT WIPE, USE FORMAT DATA).
Reboot again in recovery mode.
Flash de rmm bypass zip.
Install magisk zip.
Reboot in system.
READY!!!!
U have a Normal State. TWRP and rooted phone. Enjoy.