Hi!
I would like to seek helps with getting my Xiaomi Mi Play's bootloader unlocked and installed twrp and rooted. I have not found any guide or leads for getting twrp for this device as it only came out a few weeks or months back. Thank you!
hello!! when the twrp comes out for mi play?
Bump! It's a budget phone that would really benefit from a few Android rooted tricks
yes, twrp would be good to get rid of google apps. bloatware
any news ?
There Is no custom recovery about this device
Do you know who develops the twrp software?
peppinx80 said:
hello!! when the twrp comes out for mi play?
Click to expand...
Click to collapse
I almost ranted about the good old days!! WHOA! jeez cool guy theres like 6 folks considering making that for you. I told em you are upset. So not too much longer ..
trace_back2019 said:
Hi!
I would like to seek helps with getting my Xiaomi Mi Play's bootloader unlocked and installed twrp and rooted. I have not found any guide or leads for getting twrp for this device as it only came out a few weeks or months back. Thank you!
Click to expand...
Click to collapse
Hi, you can unlock bootloader directly with xiaomi tools.. You need to register to xiaomi website
hello everyone ,is anyone heard any news if someone is working in a development of an stock android rom for mi play,im not very happy with mui..
i could only install global rom. no 1mei repair or twrp magisk flash.
I Agree
I got mine rooted through using the guides on this site. Then i screwed up and tried to install a twrp ,,and well had to go back to stock. Now the phone is friendly to work on once you get the bootloader unlocked.
On a good note ive noticed a few folks working on it and i am too although this isnt my forte. So when it happens you better believe myself or someone on the ball will make a tutorial. Have you unlocked the bootloader yet?
tosunkaya said:
i could only install global rom. no 1mei repair or twrp magisk flash.
Click to expand...
Click to collapse
At least you could switch to global! Where did you find the ROM?
global rom
sinemora said:
At least you could switch to global! Where did you find the ROM?
Click to expand...
Click to collapse
Here is one source.
http://c.mi.com/thread-2199072-1-1.html
Hi all, my idea is to port stock recovery to twrp. To do so I need:
1) create a ported twrp;
2) unlock bootloader;
3) try the ported recovery without flashing it with " fastboot boot ported-twrp.img"
4) If all is ok flash IT.
1) Ive downloaded the Mi play global stock rom for fastboot and then I've ported the stock recovery with Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek to twrp but I've received that DM_Verity is active and i have to patch the boot with Magisk but I do not know what exactly do with Magisk. Do you have any suggestion?
Any update about this. I am rooting for an update for this mobile device
UPDATED 03 12 21 : I build a TWRP recovery for Xiaomi Mi play.
Unofficial TWRP Recovery 3.5.2_9-0
on https://github.com/gokur20/twrp_xiaomi_lotus_-Mi-Play-/releases you can the TWRP compiled for our Xiaomi Mi Play. It works with fw_lotus_miui_MIPLAYGlobal_V11.0.10.0.OFIMIXM_1600406463_8.1 and my be with other versions. Instructions: in...
forum.xda-developers.com
You can flash Gapps with It.
OUTDATED: No good news about flashing TWRP but I reached to install Lineageos 16 GSI with GAPPS without using any Recovery (lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img).
Our Smartphone seems to be compatible with GSI Aonly VNDKLITE. (I could not find any other like roms).
Steps with usb cable:
1- Reboot in fastboot mode
2- erase system, cache and userdata partition
fastboot erase system
fastboot erase cache
fastboot erase userdata
3- flash lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img in system, original cache.img, original userdata.img and original vbmeta.img disabling encryption and verity.
fastboot flash system lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4 - reboot
fastboot reboot
5 - To install the GAPPS without TWRP, we have to download gapps (Android 9) and do some work on the package to prepare to directly copy via adb the Core Apks and the permission in the right folder of the system partition. before we have to enable developer mode and in Developer option the root access over adb. Essentially you have to unzip the gapps package, unzip the packages inside the Core folder (I used lunzip with ubuntu) extract the apks and the xml files (permission), remount the system partition in rw , copy them in the right folders (you can take a look to gapps-remove.txt to have an idea, /system/priv-app/ /system/app/ /system/etc/permissions/, /system/etc/default-permissions/, /system/etc/default-permissions/) give the right permissions to apks (644) and reboot the system. Here is my script, in my example I have already divided the files in different folders on the PC.
#!/bin/bash
echo "Assicurati di aver abilitato ADB root in Opzioni Sviluppatore"
echo "Lo Script copierà gli APKs in /system/priv-app ed imposterà i permessi a 644 \n"
read -p "Premi un tasto per continuare.."
sudo adb root
sudo adb remount
sudo adb push ./priv-app/*.apk /system/priv-app/
sudo adb push ./app/*.apk /system/app/
sudo adb push ./xml/etc_permissions/*.xml /system/etc/permissions/
sudo adb shell mkdir /system/etc/default-permissions/
sudo adb push ./xml/etc_default-permissions/*.xml /system/etc/default-permissions/
sudo adb push ./xml/etc_sysconfig/*.xml /system/etc/sysconfig/
sudo adb shell chmod 644 /system/priv-app/AndroidMigratePrebuilt.apk
sudo adb shell chmod 644 /system/priv-app/CarrierSetup.apk
sudo adb shell chmod 644 /system/priv-app/ConfigUpdater.apk
sudo adb shell chmod 644 /system/priv-app/GoogleBackupTransport.apk
sudo adb shell chmod 644 /system/app/GoogleContactsSyncAdapter.apk
sudo adb shell chmod 644 /system/priv-app/GoogleExtServices.apk
sudo adb shell chmod 644 /system/priv-app/GoogleExtShared.apk
sudo adb shell chmod 644 /system/priv-app/GoogleFeedback.apk
sudo adb shell chmod 644 /system/priv-app/GoogleOneTimeInitializer.apk
sudo adb shell chmod 644 /system/priv-app/GooglePartnerSetup.apk
sudo adb shell chmod 644 /system/priv-app/GoogleRestore.apk
sudo adb shell chmod 644 /system/priv-app/GoogleServicesFramework.apk
sudo adb shell chmod 644 /system/priv-app/Phonesky.apk
sudo adb shell chmod 644 /system/priv-app/PrebuiltGmsCorePi.apk
sudo adb shell chmod 644 /system/priv-app/SetupWizard.apk
echo "Finito, ora il telefono verrà riavviato, esamina il file di log per eventuali errori /n"
read -p "Premi un tasto per continuare.."
sudo adb reboot
gokur20 said:
No good news about flashing TWRP but I reached to install Lineageos 16 GSI with GAPPS without using any Recovery (lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img).
Our Smartphone seems to be compatible with GSI Aonly VNDKLITE. (I could not find any other like roms).
Steps with usb cable:
1- Reboot in fastboot mode
2- erase system, cache and userdata partition
fastboot erase system
fastboot erase cache
fastboot erase userdata
3- flash lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img in system, original cache.img, original userdata.img and original vbmeta.img disabling encryption and verity.
fastboot flash system lineage-16.0-20191017-UNOFFICIAL-treble_arm64_avN.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4 - reboot
fastboot reboot
5 - To install the GAPPS without TWRP, we have to download gapps (Android 9) and do some work on the package to prepare to directly copy via adb the Core Apks and the permission in the right folder of the system partition. before we have to enable developer mode and in Developer option the root access over adb. Essentially you have to unzip the gapps package, unzip the packages inside the Core folder (I used lunzip with ubuntu) extract the apks and the xml files (permission), remount the system partition in rw , copy them in the right folders (you can take a look to gapps-remove.txt to have an idea, /system/priv-app/ /system/app/ /system/etc/permissions/, /system/etc/default-permissions/, /system/etc/default-permissions/) give the right permissions to apks (644) and reboot the system. Here is my script, in my example I have already divided the files in different folders on the PC.
#!/bin/bash
echo "Assicurati di aver abilitato ADB root in Opzioni Sviluppatore"
echo "Lo Script copierà gli APKs in /system/priv-app ed imposterà i permessi a 644 \n"
read -p "Premi un tasto per continuare.."
sudo adb root
sudo adb remount
sudo adb push ./priv-app/*.apk /system/priv-app/
sudo adb push ./app/*.apk /system/app/
sudo adb push ./xml/etc_permissions/*.xml /system/etc/permissions/
sudo adb shell mkdir /system/etc/default-permissions/
sudo adb push ./xml/etc_default-permissions/*.xml /system/etc/default-permissions/
sudo adb push ./xml/etc_sysconfig/*.xml /system/etc/sysconfig/
sudo adb shell chmod 644 /system/priv-app/AndroidMigratePrebuilt.apk
sudo adb shell chmod 644 /system/priv-app/CarrierSetup.apk
sudo adb shell chmod 644 /system/priv-app/ConfigUpdater.apk
sudo adb shell chmod 644 /system/priv-app/GoogleBackupTransport.apk
sudo adb shell chmod 644 /system/app/GoogleContactsSyncAdapter.apk
sudo adb shell chmod 644 /system/priv-app/GoogleExtServices.apk
sudo adb shell chmod 644 /system/priv-app/GoogleExtShared.apk
sudo adb shell chmod 644 /system/priv-app/GoogleFeedback.apk
sudo adb shell chmod 644 /system/priv-app/GoogleOneTimeInitializer.apk
sudo adb shell chmod 644 /system/priv-app/GooglePartnerSetup.apk
sudo adb shell chmod 644 /system/priv-app/GoogleRestore.apk
sudo adb shell chmod 644 /system/priv-app/GoogleServicesFramework.apk
sudo adb shell chmod 644 /system/priv-app/Phonesky.apk
sudo adb shell chmod 644 /system/priv-app/PrebuiltGmsCorePi.apk
sudo adb shell chmod 644 /system/priv-app/SetupWizard.apk
echo "Finito, ora il telefono verrà riavviato, esamina il file di log per eventuali errori /n"
read -p "Premi un tasto per continuare.."
sudo adb reboot
Click to expand...
Click to collapse
I downloaded the official rom from stockrom.net (it didn't have data.img and cache.img), so I continued the other steps, when I finished my device was still in bootloop, I flashed the stock rom's boot.img to try to fix it, but now my device is in black screen, the logo doesn't appear and I can't even go back to fastboot anymore, do you know how to solve it?
felipeelive said:
I downloaded the official rom from stockrom.net (it didn't have data.img and cache.img), so I continued the other steps, when I finished my device was still in bootloop, I flashed the stock rom's boot.img to try to fix it, but now my device is in black screen, the logo doesn't appear and I can't even go back to fastboot anymore, do you know how to solve it?
Click to expand...
Click to collapse
You can always fix It.
I had the same problem even without vibration. I followed this:
NB. in few word you have to block reboot with this tool and then use MT Flash tool to flash again the stock ROM.
Related
On the stock ROM, I can almost fully flash my Fascinate to Cricket (everything works but Market and applications using data, everything works with my Droid on the same plan, including Market and applications). I think the last piece is causing Market/Apps to not work. I need to do the following
cd c:\android\tools <enter>
adb shell <enter>
mkdir /data/opt/ <enter>
exit <enter>
adb remount <enter>
adb push c:\android\tools\u2nl /system/bin/u2nl <enter>
adb push c:\android\tools\autostart.sh /data/opt/autostart.sh <enter>
Now:
adb shell <enter>
chmod 0755 /system/bin/u2nl <enter>
chmod 0755 /data/opt/autostart.sh <enter>
adb reboot <enter>
Install Autostart from the Market or download it form the bottom of this post and install it. Reboot the phone (sometimes it will take more than 1 reboot) and give the Superuser Permission box a few seconds to pop up. Autostart will be looking for permission. Grant it.
Click to expand...
Click to collapse
The problem is I can't run the mkdir /data/opt/ command because the file system is locked. If I flash to a new ROM, then I can make the directory, but data stops working, and Cyanogen doesn't have a modem mode.
What would be the best Rom to use? Does anyone know which ones have modem-mode available? Or is there a way to unlock the filesystem so I can make that directory?
Hi guys .. i am using htc hero(t-mobile g2 touch)..i tried flashing clockworkmod recovery using adb,rom manager and terminal emulator..here is what i got
adb--cannot stat 'recovery-clockwork-2.5.0.7-hero.img': no such file or directory
for terminal emulator--error no such file or directory
for rom manager--unable to contact server
please help ..is there other way or did i make mistake??
thanks in advance
I'm a noob but did you by chance forget to Root your device?
Is it a .zip or .img file?
I'll give you a simple tutorial
1. Right-Click platform-tools and click Open CMD from here.
2. To be sure the device is detected do
adb devices
Click to expand...
Click to collapse
2.1 (optional) If no device is detected follow this tutorial.
3. extract the zip file to platform-tools and put the .img file in the same folder.
4. type the following commands:
adb push recovery-clockwork-2.5.0.7-hero.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery-clockwork-2.5.0.7-hero.img
adb shell chmod 777 /data/local/flash_image
adb shell rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
adb reboot
Click to expand...
Click to collapse
5. the device will reboot wait until it is on the homescreen again.
6. then type the following command:
adb shell /data/local/flash_image recovery /data/local/recovery-clockwork-2.5.0.7-hero.img
Click to expand...
Click to collapse
7. and you are done
Hi guys
I've imported the SH-06D from Japan and the phone is running great, however I'd like to remove some system apps etc to help speed up the phone (it's still on 2.3.5) and obviously tweak it as well.
I know there is an existing thread on the SH-01D (predecessor to the SH-06D) but I'm wondering if anyone has successfully rooted the SH-06D and if so, is there an (easy) process to do this?
Another reason I want to root, is to install the UI from the upcoming Evangelion Nerv edition of the SH-06D that is due to be released in a few days.
ICS for the SH-06D is just around the corner (due to be released in July) but I'd realy appreciate any help, assistance or tips in rooting the phone as it is now.
Cheers! :fingers-crossed:
Anyone?
:-(
here is a link to root the sh-06d :
http://itsuki.ddo.jp/gadget/index.php?SH-06D
THANK YOU!
Have you tried this method and does it work? Can you assist me in following those directions?
Cheers
interfreak said:
THANK YOU!
Have you tried this method and does it work? Can you assist me in following those directions?
Cheers
Click to expand...
Click to collapse
i haven't tried since i don't have this phone.
i can try to help you if you want.
testnumero said:
i haven't tried since i don't have this phone.
i can try to help you if you want.
Click to expand...
Click to collapse
Thanks mate!
I'm fumbling through the process now - it's a little hard when you are using google translate lol!
OK, I've run through all the steps but..
When I get to the end of the process:
C:\Users\interfreak\Desktop
$ su
su
su: permission denied
:-(
interfreak said:
OK, I've run through all the steps but..
When I get to the end of the process:
C:\Users\interfreak\Desktop
$ su
su
su: permission denied
:-(
Click to expand...
Click to collapse
i don't know what is the problem, try to do steps again.
Tried, same result. :-(
interfreak said:
Tried, same result. :-(
Click to expand...
Click to collapse
i'll ask to translate it
Thanks mate!!! :highfive:
I want to know untill now has SH-06D been rooted?
I wish someone could dump ROM or launcher from SH-06 NERV version:fingers-crossed:
I'm working on the translation for root on Sharp Aquos SH-06D.
Please give me one or two more days!
That is highly impossible, having full root in J Phone are hard enough. Unlocking the bootloader is a wet dream for almost everyone who likes J phone
lightout said:
I want to know untill now has SH-06D been rooted?
I wish someone could dump ROM or launcher from SH-06 NERV version:fingers-crossed:
Click to expand...
Click to collapse
I'm trying to hard reset my SH-06D, but I can't do it via settings-privacy. I can select to wipe, but nothing happens.
Any suggestions?
I got the Nerv edition
Hey man, how did the rooting go? I ordered the Nerv edition of this phone, and I want to root it (mainly to pair my sixaxis controller for psx emulation) but wanted to consult with you first as a precaution.
Here is the a rough translation of the root guide found here:
http://itsuki.ddo.jp/gadget/index.php?SH-06D
Big thanks to testnumero for the help!
Please don't ask me directly for help. I don't own this phone.
A quick look at root
• With root you can freeze preinstalled bloatware and backup application settings and game save data.
• 3D content from /system can be played on other devices and 3DTVs.
Unresponsive apps can be frozen which will help the device run smoother and have a longer battery life.
Applications which are frozen disappear from your drawer making the device look cleaner and keeping your mind at ease.
• The process is similar to the one used for SH-01D.
• If an update patch is released or the Android 4.0 summer update is released then this guide will no longer be of help.
(Make sure your device is the following: Android Ver. 2.3.5 Build No. 01.00.03)
• If your device becomes a paperweight I won’t be held responsible.
• Follow this guide at your own risk.
↑
Preparations – Before you begin
• Install Android SDK and SHARP ADB USB drivers and make to use ADB.
• 「Settings」→「Applications」→「Development」→「USB Debugging」 checked.
• SH-06D and micro USB cable to connect to your PC
↑
Required Files
• Download "shdisphook" from the following link and extract.
http://goo.gl/Bs6Iq
• Download shsdgetroot-omap4.zip from the following link and extract.
http://www1.axfc.net/uploader/File/so/78144
• Download shbootgetroot-su.lzh from the following link and extract.
http://www.mediafire.com/?6i0n32jlwbxe8cp
• Keep all extracted files in the same folder.
↑
Creating files
• Create a file named "shdisphook.bat" in the folder with the extracted files.
Copy and paste the following and save.
adb push onload.sh /data/local/
adb push libsdservice_jni.so /data/local/
adb push shdisphook /data/local/
adb shell chmod 755 /data/local/onload.sh
adb shell chmod 755 /data/local/shdisphook
adb reboot
adb wait-for-device shell /data/local/shdisphook
pause
• Create a file named "oncmd.sh" and put the following in the description.
(Save the line break as LF)
chmod 777 /cache
chmod 666 /cache/recovery
• Replace the contents of the file "installfile.cmd" with the following and save.
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/mount -o rw,remount -t rootfs rootfs /"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 777 /sbin"
adb push su /sbin
adb push busybox /sbin
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chown 0.0 /sbin/su"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chown 0.0 /sbin/busybox"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 6755 /sbin/su"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 755 /sbin/busybox"
adb shell /data/local/shsdgetroot-omap4 -c "/sbin/busybox --install -s /sbin"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 755 /sbin"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/mount -o ro,remount -t rootfs rootfs /"
adb push Superuser.apk /data/local/
adb shell /system/bin/pm install -t -f -r /data/local/Superuser.apk
adb shell /system/bin/rm /data/local/Superuser.apk
exit /b
↑
Step 1
• Open command prompt to the folder with the extracted files and navigate to "shdisphook".
Execute "shdisphook.bat". (You can also just double click on the .bat file)
• The device will reboot so just wait for the [Press any key to continue] message to appear.
If more than a few minutes have passed and nothing has appeared then, force close and execute "shdisphook.bat" again.
(When you fail your PC will reboot or your SH-06D WiFi will start. There is a high rate of success when you immediately unlock the lock screen for your device when it goes to sleep.)
↑
Step 2
• Open command prompt and send oncmd.sh to SH-06D to change permissions
adb push oncmd.sh /data/local/oncmd.sh
adb shell chmod 755 /data/local/oncmd.sh
• 「Settings」→「microSD and device storage」→「Unmount microSD」 This will execute the file "oncmd.sh" , which was sent to the device earlier.
(Cancel the message for 「Unmount microSD」)
• Enter the following commands.
adb shell mv /cache/recovery /cache/recovery_
adb shell ln -s /dev/shsd /cache/recovery
• Execute the following adb shell ls -l /cache and if you see the following message you have succeed.
drwxrwx--- root root 2011-11-11 03:39 lost+found
drw-rw-rw- system cache 2012-01-24 10:48 recovery_
lrwxrwxrwx shell shell 2012-03-02 13:24 recovery -> /dev/shsd
• Next execute adb shell ls -l /dev/shsd you should get the following message if you were successful.
crw-rw-rw- system cache 231, 0 2012-04-23 02:01 shsd
↑
Step 3
• Execute adb push shsdgetroot-omap4 /data/local
• Execute adb shell /system/bin/chmod 755 /data/local/shsdgetroot-omap4
• Execute adb shell /data/local/shsdgetroot-omap4 -v -m -u
• The “# “mark will appear there will be no response. Close command prompt for now.
• Execute installfile.cmd
• Check if you have root with the following adb shell→su
↑
After you reboot
• After you reboot you will lose root rights so execute shdisphook.bat→Cancel Unmount microSD →execute installfile.cmd and you should have root again.
The reason why you cannot do a clean wipe or nothing happen is because the recovery section has been move out into another location, causing it to not loading the recovery correctly.
Check with SH-01d part, I have asked similar question there and I revert the recovery in order to wipe the phone..
You need to rearrange the following section like on the sh-01d when you hit this part:
(Following is Original command that you relocated the recovery for root)
adb shell mv /cache/recovery /cache/recovery_
adb shell ln -s /dev/shsd /cache/recovery
And replace with the revert command found on sh-01d thread. You will need to redo all the steps from step 1 to step 2 and STOP AFTER YOU REVERT the RECOVERY.
You should be able to do a full wipe with no issue then. DO NOT POWER DOWN or RESET!!! You will have to REDO it again as it REQUIRES SHDSIHOOK to input shell command.
Hope it helps
waiting!!!!!!!!!!
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.