Any TWRP for Umidigi One Pro that is able to read the /data partition ?
Edit:Solved
Ghost505 said:
Any TWRP for Umidigi One Pro that is able to read the /data partition ?
Edit:Solved
Click to expand...
Click to collapse
What was the solution? I didn't even know we had a twrp!
http://community.umidigi.com/forum.php?mod=viewthread&tid=2962&extra=page=1
https://forum.xda-developers.com/android/development/twrp-umidigi-z2-z2-special-edition-t3842866
Best twrp found here : http://community.umidigi.com/forum.php?mod=viewthread&tid=17560&extra=page=1
Hey, What is your device Android version?
Android 8.1
For those with Umidigi One / One Pro or Z2
0. Install twrp from first link
---
(second link)
1. now we need to edit the fstab file
because its a MTK device your fstab file looks like fstab.mt6763 or simliar
2. Download Mixplorer from XDA Thread. ( this root explorer is the best because it set permission automaticly.)
3. open mixplorer and browse to root/system/vendor/etc/fstab.mt6763..
4 open that file and search for ( should be line 15)
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,forceencrypt=/dev/block/platform/bootdevice/by-name/metadata,
Click to expand...
Click to collapse
5. edit the file to this
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,encryptable=/dev/block/platform/bootdevice/by-name/userdata,
Click to expand...
Click to collapse
6.save and turn off the phone
---
7. Wipe Data from device and enter in the phone again and no more encryption so twrp will be able to access the data partition.
Ghost505 said:
http://community.umidigi.com/forum.php?mod=viewthread&tid=2962&extra=page=1
https://forum.xda-developers.com/android/development/twrp-umidigi-z2-z2-special-edition-t3842866
Click to expand...
Click to collapse
Thanks for the info, I'll give it a shot soon.
There's no item when I go to root in Mixplorer
Ghost505 said:
Android 8.1
For those with Umidigi One / One Pro or Z2
0. Install twrp from first link
---
(second link)
1. now we need to edit the fstab file
because its a MTK device your fstab file looks like fstab.mt6763 or simliar
2. Download Mixplorer from XDA Thread. ( this root explorer is the best because it set permission automaticly.)
3. open mixplorer and browse to root/system/vendor/etc/fstab.mt6763..
4 open that file and search for ( should be line 15)
5. edit the file to this
6.save and turn off the phone
---
7. Wipe Data from device and enter in the phone again and no more encryption so twrp will be able to access the data partition.
Click to expand...
Click to collapse
Blackchancellor said:
There's no item when I go to root in Mixplorer
Click to expand...
Click to collapse
This means that Mixplorer does not have root permissions to access root folder. Install magisk and try again, if it still does not work and you have root installed, clear data&cache for mixplorer app.
But I can't root the phone. I've tried all, but when I enter twrp it mounting data partition always fails. And TWRP also always only starts the first time after it's been flashed. Next time I start in recovery mode, I just see "No command".
Ghost505 said:
This means that Mixplorer does not have root permissions to access root folder. Install magisk and try again, if it still does not work and you have root installed, clear data&cache for mixplorer app.
Click to expand...
Click to collapse
Blackchancellor said:
But I can't root the phone. I've tried all, but when I enter twrp it mounting data partition always fails. And TWRP also always only starts the first time after it's been flashed. Next time I start in recovery mode, I just see "No command".
Click to expand...
Click to collapse
it is odd on why the recovery partition is being changed to default, do you have root ?
root tutorial
Install magisk manager 6.0.1 apk
Get the boot..img from rom section last update and put it inside phone
Use magisk manager install button to modify boot.img
Extract it to pc and mount it on boot partition in flash tools and only select that partition and click download with phone off
twrp after that link
It didn't work. When I press "install" and select the rom in the file manager, it says "flashing" and then it disapears. Nothing changes
Ghost505 said:
it is odd on why the recovery partition is being changed to default, do you have root ?
root tutorial
Install magisk manager 6.0.1 apk
Get the boot..img from rom section last update and put it inside phone
Use magisk manager install button to modify boot.img
Extract it to pc and mount it on boot partition in flash tools and only select that partition and click download with phone off
twrp after that link
Click to expand...
Click to collapse
Blackchancellor said:
It didn't work. When I press "install" and select the rom in the file manager, it says "flashing" and then it disapears. Nothing changes
Click to expand...
Click to collapse
Try SP_Flash_Tool to root with magisk first
But my main question has always been: hiw to root? I can't mount data partition after flasing twrp so I can't access my files in recovery mode and I can't install magisk
Ghost505 said:
it is odd on why the recovery partition is being changed to default, do you have root ?
root tutorial
Install magisk manager 6.0.1 apk
Get the boot..img from rom section last update and put it inside phone
Use magisk manager install button to modify boot.img
Extract it to pc and mount it on boot partition in flash tools and only select that partition and click download with phone off
twrp after that link
Click to expand...
Click to collapse
Ghost505 said:
Try SP_Flash_Tool to root with magisk first
Click to expand...
Click to collapse
Blackchancellor said:
But my main question has always been: hiw to root? I can't mount data partition after flasing twrp so I can't access my files in recovery mode and I can't install magisk
Click to expand...
Click to collapse
You do not need twrp to root the device, all you need is the sp flash tool and the boot.img from the rom. Also the magisk manager application installed normally.
OK. Could you please help me by explaining step to step how to root using SPFT? Thanks in andvance
Ghost505 said:
You do not need twrp to root the device, all you need is the sp flash tool and the boot.img from the rom. Also the magisk manager application installed normally.
Click to expand...
Click to collapse
Blackchancellor said:
OK. Could you please help me by explaining step to step how to root using SPFT? Thanks in andvance
Click to expand...
Click to collapse
1. install magisk manager apk
2. place boot.img in the downloads folder in the phone
3. press install in magisk manager apk and choose patch boot
4. get the new boot.img file created by magisk manager 6.0.1 and put it in pc and flash it using sp flash tool in boot partition
in here is the boot.img look in it with winrar
Thanks, but where to get this boot.img? Is it from the extracted rom (.rar) files.
Ghost505 said:
You do not need twrp to root the device, all you need is the sp flash tool and the boot.img from the rom. Also the magisk manager application installed normally.
Click to expand...
Click to collapse
Ghost505 said:
1. install magisk manager apk
2. place boot.img in the downloads folder in the phone
3. press install in magisk manager apk and choose patch boot
4. get the new boot.img file created by magisk manager 6.0.1 and put it in pc and flash it using sp flash tool in boot partition
Click to expand...
Click to collapse
It worked. Thanks!
Ghost505 said:
1. install magisk manager apk
2. place boot.img in the downloads folder in the phone
3. press install in magisk manager apk and choose patch boot
4. get the new boot.img file created by magisk manager 6.0.1 and put it in pc and flash it using sp flash tool in boot partition
in here is the boot.img look in it with winrar
Click to expand...
Click to collapse
Phone is now rooted and TWRP installed, but I still can't mount data partition.
Go in ROOT /vendor/etc/fstab.mt6763 with MIXPLORER
Should be on line 15 I think
edit:
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,forceencrypt=/dev/block/platform/bootdevice/by-name/metadata,
to:
/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,quota,formattable,resize,encryptable=/dev/block/platform/bootdevice/by-name/userdata,
save and restart phone and wipe data in twrp, everything will be erased, enter in phone after that and follow instructions like the first time you started the phone
Related
ROOT n unRoot, Mi 3W Stable Global-India KXDMIBH34.0 Changelog & Fastboot Download
Download
Recovery Rom: Mi 3 WCDMA Stable Version (Global) KXDMIBH34.0
http://bigota.d.miui.com/KXDMIBH34.0/miui_MI3WMI4WGlobal_KXDMIBH34.0_a6570e5f9c_4.4.zip
Fastboot Rom: Mi 3 WCDMA Stable Version (India) KXDMIBH34.0 (*applicable for India Rom only)
http://bigota.d.miui.com/KXDMIBH34.0/cancro_global_images_KXDMIBH34.0_4.4_in_c941119fcf.tgz
(first unzip with rar, then u have another file not recognized by windows, right click the extracted file ,open with winrar and extract again .. now follow the instruction, don't forget to press thanks)
Changelog
Messaging
Improved the security of Cloud Messaging
Check attachment for Rooting files
F.A.Q
1) To flash Recovery ROM, you just need to put the ROM file into your device's SD card root directory, and flash it in Recovery mode. Flashing Recovery ROM will not wipe your user data or the files in internal storage.
2) To flash Fastboot ROM, you'll need to connect your device to a computer, and use ROM flashing tools. You can choose different fastboot script to decide whether to wipe data or not
a. flash_all.bat（This file should be used in Windows operating system. It will flash all the files, and wipe all userdata and all files in internal storage)
b. flash_all_except_data_storage.bat （This file should be used in Windows operating system. It will flash the updated files, and will not wipe user data and files in internal storage)
c. flash_all_except_storage.bat （This file should be used in Windows operating system. It will flash the updated files, wipe user data, but will not delete files in internal storage）
d. flash_all.sh（This file should be used in Linux operating system. It will flash the updated files, and will not wipe user data and files in internal storage）
e. flash_all_except_data_storage.sh （This file should be used in Linux operating system. It will flash the updated files, and will not wipe user data and files in internal storage）
f. flash_all_except_storage.sh （This file should be used in Linux operating system. It will flash the updated files, wipe user data, but will not delete files in internal storage）
Source : MiUi Forum
Thanks for sharing. I do not find flash_all_except_storage.bat in Fastboot ROM India. Can you please attach here.
arulshoponline said:
Thanks for sharing. I do not find flash_all_except_storage.bat in Fastboot ROM India. Can you please attach here.
Click to expand...
Click to collapse
unzip the file unde rar with 7zip right click and select open with 7zip and you can see all
Thanks Brother
yatharthsims said:
Thanks Brother
Click to expand...
Click to collapse
Press the thanks button :Cheers:
imranaryan said:
Press the thanks button :Cheers:
Click to expand...
Click to collapse
Deleted.
imranaryan said:
unzip the file unde rar with 7zip right click and select open with 7zip and you can see all
Click to expand...
Click to collapse
Still not able to see
can we use this root to KXDCNBH34.0 (V5) ROM?
Key2run said:
can we use this root to KXDCNBH34.0 (V5) ROM?
Click to expand...
Click to collapse
yes
imranaryan said:
http://bigota.d.miui.com/KXDMIBH34.0/miui_MI3WMI4WGlobal_KXDMIBH34.0_a6570e5f9c_4.4.zip
Fastboot Rom: Mi 3 WCDMA Stable Version (India) KXDMIBH34.0 (*applicable for India Rom only)
http://bigota.d.miui.com/KXDMIBH34.0/cancro_global_images_KXDMIBH34.0_4.4_in_c941119fcf.tgz
(first unzip with rar, then u have another file not recognized by windows, right click the extracted file ,open with winrar and extract again .. now follow the instruction, don't forget to press thanks)
Click to expand...
Click to collapse
Please post the MD5 of the image and add it to your first post.
MD5 has been used in a wide variety of security applications, and is also commonly used to check the integrity of file, and verify download. You can download the md5 calculator app from below, only 249K.
http://www.winmd5.com/
naturist said:
Please post the MD5 of the image and add it to your first post.
MD5 has been used in a wide variety of security applications, and is also commonly used to check the integrity of file, and verify download. You can download the md5 calculator app from below, only 249K.
http://www.winmd5.com/
Click to expand...
Click to collapse
the link is directly from miui forum/website
Is there any method to root directly from phone without laptop or pc ..? I already have stock version 34 pre installed.
Sent from my GT-N7100
zabaknilesh said:
Is there any method to root directly from phone without laptop or pc ..? I already have stock version 34 pre installed.
Sent from my GT-N7100
Click to expand...
Click to collapse
just download the root file on your phone and flash through recovery, no need of pc
This guide is to help anyone who wants to use Android Pay but his XC phone is unlocked and rooted. It begins with an unlocked phone with a valid backup of the TA partition as well as an unrooted /system partition.
Prerequisites:
1. A backup of TA partition (https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236)
2. Unlocked bootloader
3. Working fastboot driver and command
4. Clean /system partition without any trace of su. Systemless root is fine because it will be overwritten by the new kernel. If needed, flash the stock system partition again.
5. TWRP image for XC (https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM)
6. Stock kernel image (Extract kernel.sin from official FTF)
7. Trim Area Proof Of Concept (https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893)
8. Tobias kernel repack tool (https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605)
9. Magisk v12.0 flashable zip, not Manager app (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Procedures:
1. Run TA PoC (DOUBLECLICKME.bat). You'll be asked to select your kernel image (kernel.sin) and TA backup (your TA backup file). Choose also to disable DM-Verity, Sony RIC but keep Force-encrypt (my data partition is encrypted, your choice). At the end a new file new_boot.img will be created.
2. Copy the new_boot.img in step 1 to Tobias tool folder. In the same folder, execute the following command. Again, disable Sony RIC, don't install TWRP, don't install DRM fix and don't install Busybox. At the end, another file boot.img will be created.
Code:
rootkernel.cmd new_boot.img boot.img
3. Power off your phone. Power on again while holding volume up rocker to enter fast boot mode. Execute the following command to flash the new boot image. Replace boot.img with your new image in step 2 with full path.
Code:
fastboot.exe flash boot [I]boot.img[/I]
4. Reboot your phone. No root or SuperSU app should be found.
5. Copy Magisk zip file into phone internal storage.
6. Dial *#*#7378423#*#*, followed by Service Test > Security to check if DRM is detected properly. At this point of time, your phone should be su free and DRM working properly.
7. Power off your phone. Power on again while holding volume up rocker to enter fast boot mode. Execute the following command to boot TWRP. Replace twrp.img with your TWRP image with full path.
Code:
fastboot.exe boot [I]TWRP.img[/I]
8. In TWRP, flash Magisk zip
9. Reboot your phone. Install Magisk Manager app (no long available in Play Store) (http://tiny.cc/latestmanager)
10. Run Magisk Manager and turn on Magisk Hide. You should see Magisk installed successfully and properly rooted with MagiskSU. Tap SafetyNet button to check if it can be passed.
11. (optional) Install Xposed using Magisk app, not official method. Xposed will break Safety Net again. But you can always disable it in Magisk Manager easily.
Remarks:
1. Trim Area Proof Of Concept is required to restore full DRM functionality so that Safety Net thinks the phone is still locked.
2. /system partition must be clean and free of any trace of previous su installation.
3. Magisk Manager app cannot be used to install Magisk because it requires root in the first place. Even with systemless root, after Magisk is installed this way, trace of su can be found in /vendor partition.
4. Tobias tool has to be used to repack the boot image because I found that if PoC image is used directly, phone will reboot unexpectedly after Magisk is installed.
This is the clearest guide I found so far for rooting x compact :good: (Your old guide also help me understand some of the concept)
I get most of the steps but want to confirm whether I understand it correctly
itandy said:
1. Run TA PoC (DOUBLECLICKME.bat). You'll be asked to select your kernel image (kernel.sin) and TA backup (your TA backup file). Choose also to disable DM-Verity, Sony RIC but keep Force-encrypt (my data partition is encrypted, your choice). At the end a new file new_boot.img will be created.
Click to expand...
Click to collapse
TA PoC modify the boot image and the modified boot image will mount the TA backup image during boot and "trick" the system/kernel into thinking that is the original TA Partition, and it is untouched.
itandy said:
2. Copy the new_boot.img in step 1 to Tobias tool folder. In the same folder, execute the following command. Again, disable Sony RIC, don't install TWRP, don't install DRM fix and don't install Busybox. At the end, another file boot.img will be created.
Click to expand...
Click to collapse
- Drm fix is not needed because of the trick in step 1. This step is only needed because of incompatibility of boot image generated from step 1 with magisk (mentioned in the remarks section.).
- TWRP is not needed because in this guide TWRP will be booted by fastboot through PC without actually installing it on the phone (Step 7)
- Busybox is now included in magisk I think?
itandy said:
6. Dial *#*#7378423#*#*, followed by Service Test > Security to check if DRM is detected properly. At this point of time, your phone should be su free and DRM working properly.
Click to expand...
Click to collapse
- This is to prove the TA PoC mount trick above is working. No kernel fix is done.
The advantage of this method instead of kernel drm fix is that you can have completely stock kernel/system and only have modified boot image (and some extra data in data partition). Can you theoretically update the system and exclude the boot and data partition and still have the root intact? Or is that not recommended as new update might have some change in the boot partition as well?
I still need to do more reading about magisk and why the manager need to be installed manually (and what does it do)
trewelu said:
This is the clearest guide I found so far for rooting x compact :good: (Your old guide also help me understand some of the concept)
I get most of the steps but want to confirm whether I understand it correctly
TA PoC modify the boot image and the modified boot image will mount the TA backup image during boot and "trick" the system/kernel into thinking that is the original TA Partition, and it is untouched.
- Drm fix is not needed because of the trick in step 1. This step is only needed because of incompatibility of boot image generated from step 1 with magisk (mentioned in the remarks section.).
- TWRP is not needed because in this guide TWRP will be booted by fastboot through PC without actually installing it on the phone (Step 7)
- Busybox is now included in magisk I think?
- This is to prove the TA PoC mount trick above is working. No kernel fix is done.
The advantage of this method instead of kernel drm fix is that you can have completely stock kernel/system and only have modified boot image (and some extra data in data partition). Can you theoretically update the system and exclude the boot and data partition and still have the root intact? Or is that not recommended as new update might have some change in the boot partition as well?
I still need to do more reading about magisk and why the manager need to be installed manually (and what does it do)
Click to expand...
Click to collapse
Your understanding is correct. As for busybox, I didn't install it because I don't use it. You can try and see if it affects Safety Net detection.
Yes, system partition can be updated without losing root.
trewelu said:
This is the clearest guide I found so far for rooting x compact :good: (Your old guide also help me understand some of the concept)
I get most of the steps but want to confirm whether I understand it correctly
TA PoC modify the boot image and the modified boot image will mount the TA backup image during boot and "trick" the system/kernel into thinking that is the original TA Partition, and it is untouched.
- Drm fix is not needed because of the trick in step 1. This step is only needed because of incompatibility of boot image generated from step 1 with magisk (mentioned in the remarks section.).
- TWRP is not needed because in this guide TWRP will be booted by fastboot through PC without actually installing it on the phone (Step 7)
- Busybox is now included in magisk I think?
- This is to prove the TA PoC mount trick above is working. No kernel fix is done.
The advantage of this method instead of kernel drm fix is that you can have completely stock kernel/system and only have modified boot image (and some extra data in data partition). Can you theoretically update the system and exclude the boot and data partition and still have the root intact? Or is that not recommended as new update might have some change in the boot partition as well?
I still need to do more reading about magisk and why the manager need to be installed manually (and what does it do)
Click to expand...
Click to collapse
Just found that you can actually enable busybox in Magisk Manager so you don't have to pack it into the boot image.
Sent from my F5321 using Tapatalk
Done the step above and gained root and pass safety check in magisk.
Is there a way to disable the bootloader unlocked message during boot? I don't mind the message but it delay booting process I
trewelu said:
Done the step above and gained root and pass safety check in magisk.
Is there a way to disable the bootloader unlocked message during boot? I don't mind the message but it delay booting process I
Click to expand...
Click to collapse
I'm not aware anyone is able to do that so far.
itandy said:
I'm not aware anyone is able to do that so far.
Click to expand...
Click to collapse
You would need to alter bootloader....
Remark for Android 7.0 Users
If you will use this guide on Nougat, you will need to DISABLE force-encrypt, because data partition is encrypted by default on Nougat. On top of that, you will need to first boot to TWRP, wipe DATA partition without decrypting / mounting it and then reboot system to re-create unencrypted data partition. Only then you can flash Magisk..
ondrejvaroscak said:
If you will use this guide on Nougat, you will need to DISABLE force-encrypt, because data partition is encrypted by default on Nougat. On top of that, you will need to first boot to TWRP, wipe DATA partition without decrypting / mounting it and then reboot system to re-create unencrypted data partition. Only then you can flash Magisk..
Click to expand...
Click to collapse
Just curious, I'm on MM and my data partition is encrypted. But I didn't have to decrypt it first before installing Magisk. Is there anything on Nougat that makes it different?
itandy said:
Just curious, I'm on MM and my data partition is encrypted. But I didn't have to decrypt it first before installing Magisk. Is there anything on Nougat that makes it different?
Click to expand...
Click to collapse
Yes, quite substantially .... the TWRP does NOT support /data decryption on Nougat. On MM it works, on Nougat there is no way, until someone compiles TWRP with support for Nougat encrypted /data. The workaround is to DISABLE force-encrypt, wipe /data to force re-create unencrypted /data, install anything you need and then encrypt in Settings/Security. Once you do it, there is no way to get into /data in recovery...
ondrejvaroscak said:
Yes, quite substantially .... the TWRP does NOT support /data decryption on Nougat. On MM it works, on Nougat there is no way, until someone compiles TWRP with support for Nougat encrypted /data. The workaround is to DISABLE force-encrypt, wipe /data to force re-create unencrypted /data, install anything you need and then encrypt in Settings/Security. Once you do it, there is no way to get into /data in recovery...
Click to expand...
Click to collapse
And why is data partition decryption support needed in TWRP in this case? Flashing Magisk requires modification on data partition?
itandy said:
And why is data partition decryption support needed in TWRP in this case? Flashing Magisk requires modification on data partition?
Click to expand...
Click to collapse
I don't think so. I just re-did the step (accidentally locked back my bootloader when trying to remove the unlocked message). On twrp, it ask for password which I don't even know as after BL unlock wipe, I haven't set my screen lock yet. I skip that part, mount the sd card and flash magisk. Magisk modify the boot image and I can have root and safety net working.
Ps: You might need to update the step, the magisk manager stub will force you to download the app from play store, but it is already pulled. I need to download the app directly from magisk thread and side load it.
Edit: I was wrong. Magisk do use /data for magisk.img, but it have workaround instalation in case it is inaccessible during flashing install script. See #15
trewelu said:
Ps: You might need to update the step, the magisk manager stub will force you to download the app from play store, but it is already pulled. I need to download the app directly from magisk thread and side load it.
Click to expand...
Click to collapse
Updated. Thanks!
itandy said:
And why is data partition decryption support needed in TWRP in this case? Flashing Magisk requires modification on data partition?
Click to expand...
Click to collapse
Magisk installs file magisk.img into /data. This file is than mounted as /magisk. I am not sure, how Magisk handles installation if /data is not accesible/mountable during flashing, did not try it.
ondrejvaroscak said:
Magisk installs file magisk.img into /data. This file is than mounted as /magisk. I am not sure, how Magisk handles installation if /data is not accesible/mountable during flashing, did not try it.
Click to expand...
Click to collapse
I'm not good with script, but here is my understanding,
In case of inaccessible data during flash, magisk will flash magisk.img temporarily in cache partition. During booting (after data is unencrypted), magisk check if the workaround image in cache exist and move it to data
scripts/flash_script.sh
Code:
if (is_mounted /data); then
IMG=/data/magisk.img
else
IMG=/cache/magisk.img
ui_print "- Data unavailable, use cache workaround"
fi
jni/daemon/bootstages.c
Code:
// Merge images
if (merge_img("/cache/magisk.img", MAINIMG))
goto unblock;
if (merge_img("/data/magisk_merge.img", MAINIMG))
goto unblock;
jni/magisk.h
Code:
#define MAINIMG "/data/magisk.img"
trewelu said:
I'm not good with script, but here is my understanding,
In case of inaccessible data during flash, magisk will flash magisk.img temporarily in cache partition. During booting (after data is unencrypted), magisk check if the workaround image in cache exist and move it to data
Click to expand...
Click to collapse
Cool, very clever. I did not make the effort to study in in depth, but expected some sort of solution to exist when users succesfully installed Magisk even when they can not mount /data in TWRP. This temporary /cache mount is just nice example of clever programming
Hey, I think I pseudo-bricked my device while following these steps. I used fastboot to boot into TWRP, without disabling encryption, on Nougat 7.1. I didn't notice the requirement to disable encryption in Post #8 until afterwards.
Now the device appears to be on (my computer detects an unknown device when I plug it in), but it doesn't show any LEDs or react to any buttons. Is my only recourse to wait till the battery dies in a few days and try again, or is there another way?
HAHA, I found if I hold EVERY button (power, vol up, vol dn, and camera), the phone restarts and I have access again. w00t!
Just wondering if somebody tried this with Nougat 7.1? I can't get TA_POC to work, security test displays error and sim card is not detected.
baz1 said:
Just wondering if somebody tried this with Nougat 7.1? I can't get TA_POC to work, security test displays error and sim card is not detected.
Click to expand...
Click to collapse
Yes this works with 7.1 the same as with 7.0. How did you perform the update to 7.1?
I followed the guide to perfection, and everything works perfectly...but...If I want to turn a user app into system apps, link2sd gives me this error: mount: '/dev/block/bootdevice/by-name/system'->'/system': Device or resource busy" and system app mover gives me this error : "could not remount /system".
is system read only? why? I've already tried to enable "rw" "ro" through the command line without success...
Can anyone help me?
p.s. I have granted root permissions to the applications mentioned above at their opening
I was new for rooting and choose the easiest way to root(kingoroot not kingroot) my samsung galaxy j1 ace...
and now i want to switch to supersu from kingo superuser...
as kingroot being more famous... i didnt found any tutorials too... some are using supersu me...
i have no idea what to do... i want to clear the remainants of kingo too...
help me...
A procedure is here:
https://forum.xda-developers.com/an...g/replace-kingoroot-supersu-manually-t3573361
My device stores applications in directories in /data/app, ex:
com.kingoapp.apk-1, com.kingouser.com-2, eu.chainfire.supersu-1,
with subdirectories, lib and oat...
Any help to transpose the procedure above into this environment?
pascal.malaise said:
A procedure is here:
https://forum.xda-developers.com/an...g/replace-kingoroot-supersu-manually-t3573361
My device stores applications in directories in /data/app, ex:
com.kingoapp.apk-1, com.kingouser.com-2, eu.chainfire.supersu-1,
with subdirectories, lib and oat...
Any help to transpose the procedure above into this environment?
Click to expand...
Click to collapse
can u suggest me something easy???... like with terminal....
Revert to stock rom and try the manual rooting using SuperSU. You'll need a compatible custom recovery to install supersu.
rolland.arriza said:
Revert to stock rom and try the manual rooting using SuperSU. You'll need a compatible custom recovery to install supersu.
Click to expand...
Click to collapse
terminal or supersu me will work?
http://www.ccnworldtech.com/2017/03/how-to-replace-kinguserkingo-superuser.html?m=1
will it work???
yashasvi.malik said:
can u suggest me something easy???... like with terminal....
Click to expand...
Click to collapse
plss help....
yashasvi.malik said:
terminal or supersu me will work?
Click to expand...
Click to collapse
Have you reverted to stock rom? You can just do a factory reset (root access should be removed too). Install the necessary drivers. Download a custom recovery for your device (TWRP maybe, search it here in the forum). Download the supersu flashable zip (this is an older version, just update after install). Also download the latest ADB drivers (awesome app). Then you root:
(1) Copy the supersu zip to your device storage. Copy/move the custom recovery to the root folder of your ADB.
(2) Open ADB:
Code:
adb reboot bootloader
wait for the device to go into fastboot, then:
Code:
fastboot boot "recovery.img"
(3) Navigate the new custom recovery and select "Install" and select the supersu zip file, then reboot.
(4) Check root access.
Goodluck
its my first time rootnig my phone (galaxy a5 - SM-A520F ) and all ive done so far is installed TWRP. I downloaded supersu.zip but the files i see in the android's file explorer are diffrent from those that the twrp explorer shows so i cant find the zip file in twrp. I dont have an sd card to move it on. What can i do?
anastbogia said:
its my first time rootnig my phone (galaxy a5 - SM-A520F ) and all ive done so far is installed TWRP. I downloaded supersu.zip but the files i see in the android's file explorer are diffrent from those that the twrp explorer shows so i cant find the zip file in twrp. I dont have an sd card to move it on. What can i do?
Click to expand...
Click to collapse
R U sure you selected zip and not img from twrp? Twrp might be looking only for img if that is so.
File manager in twrp is no different than standard file manager , only zips or img are visible.
jason_l367 said:
R U sure you selected zip and not img from twrp? Twrp might be looking only for img if that is so.
File manager in twrp is no different than standard file manager , only zips or img are visible.
Click to expand...
Click to collapse
From what i read online (but could be totaly wrong) twrp files are the system files whereas android file explorers are internal storage.
I figured out how to access my system files but its read only so I cant paste in zip
anastbogia said:
I figured out how to access my system files but its read only so I cant paste in zip
Click to expand...
Click to collapse
Need to "swipe to allow modifications" when you first time start TWRP
You'll be able to flash SuperSU then.
jason_l367 said:
Need to "swipe to allow modifications" when you first time start TWRP
You'll be able to flash SuperSU then.
Click to expand...
Click to collapse
My problem is that I cant modify the system files from android not from twrp
anastbogia said:
My problem is that I cant modify the system files from android not from twrp
Click to expand...
Click to collapse
Place the SuperSU zip file in 'Downloads' directory on your phone (there's no way it won't be visible in TWRP) do button combo ,enter twrp -swipe to allow modifications (so it's not 'read only') ,navigate to Downloads , select the 'supersu . zip ,swipe to install. There's literally no way it can fail.
jason_l367 said:
Place the SuperSU zip file in 'Downloads' directory on your phone (there's no way it won't be visible in TWRP) do button combo ,enter twrp -swipe to allow modifications (so it's not 'read only') ,navigate to Downloads , select the 'supersu . zip ,swipe to install. There's literally no way it can fail.
Click to expand...
Click to collapse
I cant mount data folder in TWRP without wiping first so the data is empty and i cant see no downloads
I got an sd card and now I can locate the file, I flashed it but it failed and my phone couldn't boot so I install the Samsung firmware with odin. Will wiping before flashing fix this?
anastbogia said:
I got an sd card and now I can locate the file, I flashed it but it failed and my phone couldn't boot so I install the Samsung firmware with odin. Will wiping before flashing fix this?
Click to expand...
Click to collapse
If it were my phone , upon booting to twrp I'd wipe system data and cache(s) formatt data and flash a rom /root!
Since you got twrp ur bootloader is unlocked so u should be good to flashmagisk or latest SuperSU without issue. I'm not an expert. Sorry for the delayed responses this oppo phones are crap.
jason_l367 said:
If it were my phone , upon booting to twrp I'd wipe system data and cache(s) formatt data and flash a rom /root!
Since you got twrp ur bootloader is unlocked so u should be good to flashmagisk or latest SuperSU without issue. I'm not an expert. Sorry for the delayed responses this oppo phones are crap.
Click to expand...
Click to collapse
I watched a tutorial and the guy in the vid doesnt wipe before flashing but after supersu is install he taps on the "wipe cache " or something like that. So I have to do that and will my data be erased?
anastbogia said:
I watched a tutorial and the guy in the vid doesnt wipe before flashing but after supersu is install he taps on the "wipe cache " or something like that. So I have to do that and will my data be erased?
Click to expand...
Click to collapse
You phone should be rooted if you have twrp and flash the root zip. You don't have to wipe cache
The device may reboot 1-2 times after you flash the root.zip but you should be ok.
This thread is now defunct. I have moved to iPhone. Sorry about this.
Take care everybody.
Regards,
Magnetox
Appreciate this! If I'm already unlocked, is it possible to remove the -w in the flash-all script before running for a rooted install without wiping user data?
Wi1son said:
Appreciate this! If I'm already unlocked, is it possible to remove the -w in the flash-all script before running for a rooted install without wiping user data?
Click to expand...
Click to collapse
I would leave it as is, but if you want to try it, go ahead (might brick).
Hi ! Thanks for it.
Just a question After flash the Rom when the phone reboot before copy magisk manager can restore my Google backup ?
And how I do when they had an update ?
Thanks
ggkameleon said:
Hi ! Thanks for it.
Just a question After flash the Rom when the phone reboot before copy magisk manager can restore my Google backup ?
And how I do when they had an update ?
Thanks
Click to expand...
Click to collapse
Yes that should be fine. Just restore normally. But don't forget magisk otherwise it won't have proper root.
Might be a silly question, but, does this stock image work with Google Fi?
Also, a little confused with some of the directions...
In step 1 it says "Download the appropriate rar package for your system and install."
Does this mean download my stock image from Google and install it with Magisk, or... ?
In step 9 it says, " Once in fastboot, and the bootloader, run "fastboot devices" from the "BRAMBLE" folder. "
Does this mean to run "fastboot devices" as a command inside the command prompt from the "BRAMBLE" folder or to open one of the tools inside the platform tools folder?
Also, in step 11, where do I find the "appropriate flash-all command on your operating system"?
These are just a bit confusing to me. Don't want to brick my phone, so any help is appreciated.
Thanks
SpecialKCF22 said:
Also, a little confused with some of the directions...
...
Thanks
Click to expand...
Click to collapse
Download the WinRAR package in the mega.nz folder for your OS.
Both, platform tools should be in that BRAMBLE folder. Example fastboot.exe should be in BRAMBLE.
You will find this in your BRAMBLE folder when you properly extract platform tools and the .rar into the BRAMBLE folder.
SpecialKCF22 said:
Might be a silly question, but, does this stock image work with Google Fi?
Click to expand...
Click to collapse
It's just stock with root, so if the Pixel 4a 5g works normally it will too.
Magnetox said:
Download the WinRAR package in the mega.nz folder for your OS.
Both, platform tools should be in that BRAMBLE folder. Example fastboot.exe should be in BRAMBLE.
You will find this in your BRAMBLE folder when you properly extract platform tools and the .rar into the BRAMBLE folder.
Click to expand...
Click to collapse
You're not very detailed and you didn't answer the questions. I'll pass on this method. Thanks
SpecialKCF22 said:
You're not very detailed and you didn't answer the questions. I'll pass on this method. Thanks
Click to expand...
Click to collapse
Feel free to PM
Magnetox said:
Yes that should be fine. Just restore normally. But don't forget magisk otherwise it won't have proper root.
Click to expand...
Click to collapse
So, will update delete the magisk app? Or what do you mean when write "don't forget magisk"?
Ryav said:
So, will update delete the magisk app? Or what do you mean when write "don't forget magisk"?
Click to expand...
Click to collapse
I mean don't forget to install it and assure you have proper root after.
Does this one works with Google pay. My rooted build of RD1A.200810.022.A4 doesn't pass the safety check on magisk manager. Thank you
imFonk said:
Does this one works with Google pay. My rooted build of RD1A.200810.022.A4 doesn't pass the safety check on magisk manager. Thank you
Click to expand...
Click to collapse
MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0
Thanks for this! FYI for anyone curious the newest Magisk 8.07 does work, you don't need to use the linked file.
dadozer said:
Thanks for this! FYI for anyone curious the newest Magisk 8.07 does work, you don't need to use the linked file.
Click to expand...
Click to collapse
Yes feel free to do this. The APK that is linked works fine as well and will update itself with your permission.
Magnetox said:
Hey everybody,
Here is the latest Android 11 January 2021 update rooted (I will keep it updated). It's all clean. It is the Google stock system image with root applied (comes with GAPPS). You can cleanly flash your device with this as long as your fastboot (bootloader) is working.
Download LINK:
File folder on MEGA
mega.nz
Steps:
1) Download the appropriate rar package for your system and install.
2) Download the appropriate platform-tools package for your operating system (this contains ADB and Fastboot) and extract it in a folder we'll call "BRAMBLE" (we will use this folder for the install).
3) Download the bramble-rq1a.210105.003.rar file (this is the stock rom). Extract it to the "BRAMBLE" folder. You will want to see all the files (ie. the flash-all.sh) all in the folder the same folder that contains the ADB and Fastboot tools.
4) Download MagiskManager-v8.0.4.apk, this will be used after the install and installed on the device.
5) Enable USB debugging and OEM unlocking (the bootloader unlock) in developer options (smash on build a bunch of times in a row real fast to enable developer options in about phone).
7) Navigate to the "BRAMBLE" folder with a terminal or command prompt (depending on your operating system) and run "adb devices" with root or administrator access in your terminal or command prompt on your computer (respectively there). Allow the USB debugging to connect to your computer forever on your phone, something should pop up. It should appear in the terminal or command prompt. If not you need to accept USB debugging on your phone (forever).
8) Put in the command "adb reboot bootloader" once your device appears.
9) Once in fastboot, and the bootloader, run "fastboot devices" from the "BRAMBLE" folder. This should return your device. If not, something is wrong and restart. Another way of reaching fastboot is restarting your phone and holding VOLUME DOWN.
10) Make sure your device is unlocked, run "fastboot flashing unlock".
11) In the "BRAMBLE" folder, run the appropriate flash-all command on your operating system. This will take a while and completely reflash the system with the Stock ROM with root. You will see the progress as it appears.
12) Once it's done, your phone will reboot. Just wait for it to start up and do as you normally would on a new flash.
13) Move the MagiskManager-v8.0.4.apk onto the phone, and install it. It will confirm you have partial root and ask you to apply something more and reboot. Do so.
14) When rebooted, your phone will be fully flashed and rooted. Feel free to download a root verification app, I recommend this one. It should be working fine. Grant root permission forever to it.
If you have any questions, feel free to ask. You can install the ElementalX kernel on this rom for Pixel 4a 5g. Download this. It's a great kernel tool and it will help you with full root access download and install the kernel. It's the kernel I'm using.
Regards,
Magnetox
Click to expand...
Click to collapse
i could not install magisk, the 13th step in your guide might not be complete.
i managed to root, and got to pass safety net, and google pay working.
i have to move the boot.img from the zip file included in the package you provided, move it to internal storage, patch it in magisk manager.
then i moved the patched boot.img to my pc, did adb reboot bootloader, then fastboot flash [patched boot.img] and then only i was fully rooted.
i also flash the safetynet-fix-v1.1.1.zip module in magisk to pass satefynet.
hope it could help out, i digged all night yesterday to get this done lol.
MegaJuif said:
i could not install magisk, the 13th step in your guide might not be complete.
i managed to root, and got to pass safety net, and google pay working.
i have to move the boot.img from the zip file included in the package you provided, move it to internal storage, patch it in magisk manager.
then i moved the patched boot.img to my pc, did adb reboot bootloader, then fastboot flash [patched boot.img] and then only i was fully rooted.
i also flash the safetynet-fix-v1.1.1.zip module in magisk to pass satefynet.
hope it could help out, i digged all night yesterday to get this done lol.
Click to expand...
Click to collapse
I updated it with the latest 8.0.7 magisk. Hope this fixes it. (Uploading now)
Upload complete! (Magisk 8.0.7)