Is there a step I'm missing when trying to root? my steps were.
- Upgrade to PIE using Odin
- Flash TWRP
- Boot in TWRP and allow modifications
- Flash DM_Verity patch
- Wipe data
- Boot in TWRP and flash Magisk without allow modifications
- System won't start
Related
Hello, I'm interested in few things about Moto G5.
1st question: Will be possible for developers to make Oreo ROMs fully functional after release of official Oreo by Motorola? I mean fixing camera, USB tethering etc.
2nd question: If I'd like to try official Oreo after its release with 4G working, is this the correct order? I'd preffer to install it as OTA update. Now, I'm running LineageOS 14.1 with 4G working fine.
- flash TWRP 64bit (currently using TWRP 32bit)
- backup EFS partition
- put phone into bootloader mode to lock bootloader (flash OEM, boot and system only - requirement to lock BL)
- boot into system
- put phone into bootloader mode to flash full Nougat stock ROM
- boot into system and install Oreo OTA update
- once again, put phone into bootloader mode to unlock bootloader
- flash TWRP 64bit
- flash no-verity-opt zip file
- restore EFS partition
- perform a factory reset
- reboot into system
Or would be better to wait for fastboot flashable ROM and use this order?
- flash TWRP 64bit (currently using TWRP 32bit)
- backup EFS partition
- put phone into bootloader mode
- flash Oreo stock ROM with fastboot comands (including erase modemst1; modemst2) and boot it up
- once again, put phone into bootloader mode
- flash TWRP 64bit
- flash no-verity-opt zip file
- restore EFS partition
- perform a factory reset
- reboot into system
I know, the best option would be waiting for TWRP install zip/backup, but... I'm such an impatient person.
3rd question: There's an performance limitation, if battery gets lower or equal to 10%. Is there any possibility of keeping full performance even with low battery?
so, i make this thread to share my tips when using vince. i assume you already unlock bootloader, root, have pc/laptop, already install usb driver for redmi 5 plus, and have common sense
this thread is based on my opinion and experience while using vince
Clean Flash to Flash Custom Rom
you can use this method with clean flash method. for me, this is best to do if you want to flash to different android rom version.
steps :
- backup your file (ROM, gapps, etc) to pc or SD Card (external storage)
- reboot phone to fastboot mode, and plug phone with usb to pc
- open xiaomi flash tool, on bottom right, choose clean all (not clean and lock)
- use select button and select the extracted archive of downloaded fastboot images folder
- press refresh button, and your vince should be detected
- press flash, and wait patiently
- after the xiaomi flash tool done flashing, your vince will reboot twice, on second reboot, you go to fastboot mode again.
- use the recovery flasher the file is on bottom of this post (just execute the bat file)
- your phone will reboot to recovery, format data, then wipe all
- flash last updated firmware
- flash the desired rom
if you want to flash to different custom rom, but its same android version, you can just
- wipe all
- flash last updated firmware
- flash desired rom
cause flash to fastboot rom is overkill
Common way to flash custom rom
this is how im flash custom rom. well its not a best choice, but its okay for using my vince as daily driver
ordered step
- clean flash (dirty flash its okay, but im rarely dirtyflash)
- flash last updated firmware
- flash rom
- flash opengapps nano
- flash magisk (lastest stable)
- flash custom kernel (some rom dont have lastest kernel)
Easy way to flash recovery
so i make a simple bat to flash recovery if you are from fastboot rom.
how to use
- reboot to fastboot mode
- plug phone to pc
- double click the bat file and follow the instruction there
Xiaomi flash Tool
https://www.xiaomiflash.com/
Recovery Flasher
TWRP 3.3.0-0 UNOFFICIAL V2
by @rama982
https://drive.google.com/open?id=1gl_S6BRDEViBpFbd_Edhvzc07jZWF-cb
Last updated weekly fastboot image
version: 9.6.20
http://bigota.d.miui.com/9.6.20/vince_images_9.6.20_20190620.0000.00_8.1_cn_60ef80a26a.tgz
Last updated firmware
version: 9.10.10
https://drive.google.com/open?id=1gl_S6BRDEViBpFbd_Edhvzc07jZWF-cb
sorry if this thread have grammatical error. any feedback welcomed :highfive:
Must Have An Unlocked Bootloader To Do This!
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install magisk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2
I Do Not Recommend Mixing Bit 5 With Higher Firmware!!!!
Unless Using Bit Safe Firmware That Is Patched
Downloads
SM-N970U/U1/W- Model
USERDATA_AIO_N970_FORCE_WIPE_10_10_21.tar.md5 --Use on android 10 or 11
This will force a wipe of data no mater what.
Full Odin 3.1.1 Bit1 Safe Firmware
N970USQS7FUH3_BIT5_SAFE.7z
This are odin files and will safely update all image files too bit 7 and keep bit 5 bootloaders. Unfortunately this will wipe data this is beyond my control as it seems to be a side affect of mixing firmware it causes data not to mount and therefore my AIO will format it. This is full firmware with USERDATA_AIO. This will put you on U firmware. Before flashing I recommend removing your google account and make sure in download mode you are not frp locked
If above USERDATA_AIO_N970_FORCE_WIPE_08_30_21.tar.md5 is newer than the one in this zip use the newer one from above
Odin3_v3.14.1_3B_PatcheD.zip
Files For SM-N975 Found Here
TWRP Recovery Provide by @afaneh92
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions For Newly Unlocked Devices
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load file USERDATA_SLOT_*9**U_**.tar.md5 you must choose one of the FORCE_WIPE files and load in the USERSDATA slot of odin and flash file
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Install Instructions For Updating Firmware On Phone Already Unlocked
1. Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above
2. Use patched 3.14 odin and load stock firmware in appropriate slots use regular CSC file in the CSC slot and load file one of the USERDATA_SLOT_*9**U_**.tar.md5 in the USERSDATA slot of odin and flash firmware. Do not use the User Data file that comes with firmware.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not
Install Instructions If Updating Images With TWRP
1. When done flashing images in TWRP Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above.
2. Use patched 3.14 odin and load file USERDATA_AIO_*9**_NO_WIPE_NO_BL.tar.md5 in the USERSDATA slot of odin and flash file.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not.
4. Alternatively to using USERDATA_AIO_*9**_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_21_4_N10U_US_Series_Android_R.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
Fix Safetynet
Bluetooth is patched for pairing to survive reboots
Samsung Health working
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
@elliwigy
@klabit87
@Krog18
@me2151
@stang5litre
@Raymonf for modified odin
@rayan-refoua for boot animation
@TheMadScientist
@afaneh92
@kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
@JDBarlow for test S20 stuff
Info For Bootloader Unlocks Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Hey can you help me with this process. I am not entirely to sure if my s10e varient is capable of root/unlocking bootloader.
Here's the steps on how to fix it, because Samsung's treble implementation is kinda crap.
(note: might not work for everyone, steps must be done correctly)
These steps assumes that you have your phone bootloader unlocked, rooted,flashed with a custom Recovery, and encryption removed.
Method 1 (easy, no need to download large flash files)
- Go to your custom recovery and then wipe
- Flash the boot.img file given below (note: Flash only on A71 4G. I am not responsible if your device bricked because you flashed this img on A71 5G or other devices. EVEN IF IT IS SIMILAR, IT WON'T WORK!)
- Reboot to recovery (important)
- Your device might boot to a stock recovery as of now. Don't panic if it does. Power off then boot to download mode
- Select "reboot to download"
- Use Odin to flash twrp-3.6.2_11-3_afaneh92-a71.tar (AP slot) that is given below.
- When the device reboots, immediately boot into the custom recovery by pressing volume up + power button.
- Flash Multidisabler, file given below
- Flash your GSI of choice (select install image then flash as system image)
- Flash any fix zips that need to be flashed (if there are any)
- Wipe again just to make sure
- Reboot
Bugs: This TWRP build's encryption/decryption not fully working. Make sure your device storage is already decrypted, as formatting data will not decrypt your device storage.
Method 2 (hard, but almost guaranteed will work)
Thank you @Zainullahk1234 for this fix
install Stock ROM (4 files, search on Samfw or Sammobile for the flash firmware for the A71. I recommend to flash the latest binary, as flashing older builds will not work sometimes) boot into the stock rom and then change date to 3 months from now
check for updates, make sure you're connected to the internet for this
boot into download mode
flash twrp 3.6.2 (file given above) and vbmeta tar file
boot into twrp
do format data
flash multidisabler
flash GSI ROM
flash GSI Fixes (if there are any)
do factory reset
reboot
if it boots you into fastboot again, shutdown then reboot to recovery, flash twrp 3.6.2 via Odin and try another factory reset and reboot (In twrp)
Credits: @ShaDisNX255 for the stock boot.img, extracted from RayOS
@afaneh92 for the TWRP recovery.
Thread - https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a71-snapdragon.4350893/
@ianmacd for the multidisabler
TigerLake said:
Here's the steps on how to fix it, because Samsung's treble implementation is kinda crap.
(note: might not work for everyone, steps must be done correctly)
These steps assumes that you have your phone bootloader unlocked, rooted,flashed with a custom Recovery, and encryption removed.
- Go to your custom recovery and then wipe
- Flash the boot.img file given below.
- Reboot to recovery (important)
- Your device might boot to a stock recovery as of now. Don't panic if it does. Power off then boot to download mode
- Select "reboot to download"
- Use Odin to flash twrp-3.6.2_11-3_afaneh92-a71.tar (AP slot) that is given below.
- When the device reboots, immediately boot into the custom recovery by pressing volume up + power button.
- Flash Multidisabler, file given below
- Flash your GSI of choice (select install image then flash as system image)
- Flash any fix zips that need to be flashed (if there are any)
- Wipe again just to make sure
- Reboot
Bugs: This TWRP build's encryption/decryption not fully working. Make sure your device storage is already decrypted, as formatting data will not decrypt your device storage.
Credits: @ShaDisNX255 for the stock boot.img, extracted from RayOS
@afaneh92 for the TWRP recovery.
@ianmacd for the multidisabler
Click to expand...
Click to collapse
It was simple if you linked my twrp thread, and please drop the image and direct link to my host.
afaneh92 said:
It was simple if you linked my twrp thread, and please drop the image and direct link to my host.
Click to expand...
Click to collapse
Okay, I'll link your TWRP thread.
afaneh92 said:
It was simple if you linked my twrp thread, and please drop the image and direct link to my host.
Click to expand...
Click to collapse
Also btw, TWRP 3.7 caused my phone to not boot, so I reflashed twrp 3.6.2 and this build is what I put here.
TigerLake said:
Also btw, TWRP 3.7 caused my phone to not boot, so I reflashed twrp 3.6.2 and this build is what I put here.
Click to expand...
Click to collapse
Thanks, will try to fix it soon
Hello, I want to update my device to Android 12 or 13. This is my device:
xiaomi redmi note 8 pro (begonia)
Miui Global Stable 12.5.7.0 (RGGEUXM)
Android Version: 11 RP1A.200720.011
Bootloader: unlocked
I flashed twrp with BRP3.5.2v3.1. Device is rooted, SafetyNet check in magisk failed.
How do I update to Android 12 or 13 and where do I get the images from or do I have to build them?
Will I still have root access after update?
What are you talking about?
For root:
- Unlocked Bootloader
- Working rom
- By TWRP method: Working TWRP. Flash Magisk.apk
- By Fastboot method: Take boot.img. Patch boot.img. Flash patched boot.img
- Patch vbmeta if you are using Miui. Custom rom don't need this
For pass Safetynet (Magisk v25.2)
- Enable Zygisk
- Enable Enforce Denylist
- Flash Safetynet fix 2.4.0
- Configure Denylist:
+ Google Play Store
+ Google Play Services
- Reboot
- Setting>Apps
- Clear data + storage of 2 Google stuff above
- Check if it show devide certified or not.
Some old rom need to change many props to make rom work. I will not write details here. You can search on YouTube. But i recommend to use new roms to prevent that.
Kirasu2080 said:
For root:
- Working rom
Click to expand...
Click to collapse
What means a working rom?
Kirasu2080 said:
- By TWRP method: Working TWRP. Flash Magisk.apk
Click to expand...
Click to collapse
You wrote in https://forum.xda-developers.com/t/soft-brick-bootloop-after-twrp-flash.4570389/ that twrp-3.3.1-0-begonia.img supports Android 9 only. If I want to use TWRP for A11, I should find an unofficial one by searching "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1).
How do I know, which twrp is fitting my device? Does 'working' in this case mean, the software is penetrate the system to access recovery mode or something else?
Kirasu2080 said:
- By Fastboot method: Take boot.img. Patch boot.img. Flash patched boot.img
Click to expand...
Click to collapse
Is it the same patching as mentioned here https://topjohnwu.github.io/Magisk/install.html?
Patching Images
Copy the boot/init_boot/recovery image to your device
Press the Install button in the Magisk card
If you are patching a recovery image, check the “Recovery Mode” option
If your device does NOT have a separate vbmeta partition, check the “Patch vbmeta in boot image” option
Choose “Select and Patch a File” in method, and select the boot/init_boot/recovery image
Start the installation, and copy the patched image to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Flash the patched boot/init_boot/recovery image to your device;
for most devices, reboot into fastboot mode and flash with command:
fastboot flash boot[_x] /path/to/magisk_patched_[random_strings].img or
fastboot flash init_boot[_x] /path/to/magisk_patched.img_[random_strings] or
fastboot flash recovery /path/to/magisk_patched.img_[random_strings],
where [_x] should be _a or _b or empty depending on your device
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img (note that it may wipe your data)
Reboot and launch Magisk app (you will see a stub Magisk app if you have wipped your data; use it to bootstrap to a complete Magisk app), and you will see a prompt asking for environment fix; click and wait for the reboot
Voila!
Click to expand...
Click to collapse
Kirasu2080 said:
- Patch vbmeta if you are using Miui. Custom rom don't need this
Click to expand...
Click to collapse
What exactly is vbmeta for? For preventing to remove the custom recovery loader? Or do I mistake it with avb close 2.0?
Kirasu2080 said:
Some old rom need to change many props to make rom work.
Click to expand...
Click to collapse
What is an old rom? By date or by software?
liltechie said:
What means a working rom?
You wrote in https://forum.xda-developers.com/t/soft-brick-bootloop-after-twrp-flash.4570389/ that twrp-3.3.1-0-begonia.img supports Android 9 only. If I want to use TWRP for A11, I should find an unofficial one by searching "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1).
How do I know, which twrp is fitting my device? Does 'working' in this case mean, the software is penetrate the system to access recovery mode or something else?
Is it the same patching as mentioned here https://topjohnwu.github.io/Magisk/install.html?
What exactly is vbmeta for? For preventing to remove the custom recovery loader? Or do I mistake it with avb close 2.0?
What is an old rom? By date or by software?
Click to expand...
Click to collapse
Working rom/TWRP mean rom/TWRP that you can boot on your phone.
Ex: Official TWRP can't boot with your Miui rom. So it's not working TWRP.
For knowing which is suitable TWRP, you need to know all about unofficial TWRP and it's changelog.
Fastboot method: it's working with almost device that don't have TWRP.
Patch vbmeta or avb close 2.0 with do same purpose. You can read about vbmeta in Official TWRP flash guide
Old rom is by date. Google update many stuff but old rom can't catch up.