Related
Hey Guys,
I have a redmi 3s prime and i tried to install lineage os on it, during the process i accidentaly flashed twrp over both the recovery and the boot. Now i cannot get into the recovery (and fastboot) unless i flash it over boot before rebooting my phone. After that i AM able to flash an new rom but it seems to always have wifi issues.
atm i am trying to flash the xiaomi developers global rom to see if it makes any difference. My main goal is to flash TWRP and a curstom rom (linage or resurrectionremix).
Can anyone help me?
Thanks alot!
Update #1
The flashing of the global developer rom worked and the wifi seems to work aswell, i will try to boot into fastboot and recovery.
Update #2
Its seems i am able to boot into fastboot and recovery again
Update #3
Following a tutorial for flashing TWRP and a custom rom but cant se2 anyone help me here?:
Code:
>>> Check then next step to root :
- launch minimal adb tool (previously installed)
- type : adb devices (to list phone connected) it will appear "unauthorized"
- on the phone : accept the computer
- re type : adb devices
it has changed in "authorized"
- type : adb reboot bootloader
it will go in fastboot mode (the same that power + vol down)
- type : fastboot devices
your phone will appear as in adb mode (unless the bad signed driver is choosen in win10 ; i won't repeat it again)
- type (optional) : fastboot oem device-info (to verify if bootloader is locked or unlocked)
now, we go to root
- type : fastboot boot twrp.img (if it is your renamed twrp copied in the minimal adb folder)
link for TWRP guide at the end if needed
!!! it will boot temporary in this recovery but it will keep your original recovery !!!
> allow to modify system (don't keep the "read only" if you want to root or flash recovery later)
go to settings to set date, hours, language, set custom options...
My optional advices :
- save your EFS & persist partitions or all whole partitions (except cache) to make a backup
- export this backup in computer or SD card in case of future problem
(EFS, persist are usefull to save and restore your IMEI in particular)
- you can flash directly TWRP with fastboot command : fastboot flash recovery twrp.img
>>> Root :
Now flash DM-verity patch, then superSU.zip to root and accept to wipe dalvik/cache after, finally reboot !
Device is rooted ! and you have kept the original recovery.
the reboot is quite long like rom update (because of cache rebuild)
sometimes, parts of theme are lost after rooting : just restore your theme
some devices don't need DM-verity patch as explained upper
superSU app shows "systemless root" from android 6+, it is normal, read below
>>> Change the Recovery by TWRP (optional) :
Now you are rooted, you have 2 methods :
- Install one TWRP app with googleplay and flash recovery through app on rooted device.
New official app in development (flash/backup .img & .tar)
- OR reboot in fastboot mode (with TWRP app method or power+vol- method or adb reboot recovery method)
in fastboot mode, and type commands :
fastboot devices
fastboot flash recovery twrp.img
(be sure your twrp.img is unlocked and correctly copied/renamed in minimal adb folder)
Now, long press power to turn OFF phone
power + vol+ (release power at vibration) to enter in TWRP or by TWRP app or Updater app or under Windows with minimal adb reboot recovery command
Note for devices with DM-verity : flashing TWRP needs to have patched system with DM-verity patch before because you will modify system most of time - generally, you don't need to patch again because you have ever done it in previous steps - in case of bootloop : go to fastboot mode, boot in TWRP with command and patch it.
Chainfire has recently modified superSU for android 6+ devices with DM-verity to install root without modify the system : it's called "systemless root". When you flash superSU.zip, it detects automatically android version, cleans old files and installs with appropriate method. Maybe no need to patch boot in this case with DM patch.
Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode
REQUIREMENTS -
1 - Setup adb and fastboot on your PC.
2- Stock boot image (boot.img) of your device (extract file from factory image android P)
3 - Last Magisk Manager (v 5.8.3)
4 - Active Internet connection
5 - Active mind and patience.
6 - Devices must is unlock bl.
This Boot-Image is for boot android P PPR1.180610.009:
https://drive.google.com/open?id=166pE9aMk-jqns3JM74enFhsaDY6-c3yJ
Magisk Manager
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
==================================================
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta
7- Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
CREDITS
@topjohnwu (Magisk)
Sadly goes into a bootloop for me - no idea why though
This worked for me. I had magisk installed and took the pie update. No more root. D/l the factory image and extracted the boot image to the files folder...pissmeoff they changed the name of the icon... and magisk patched the image and saved it in its folder. Found the file, moved it to the laptop then flashed it.
reawo said:
Sadly goes into a bootloop for me - no idea why though
Click to expand...
Click to collapse
I think you made a mistake.
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
reawo said:
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
Click to expand...
Click to collapse
I think you use my file(boot.img) for patch_boot.img from magisk manager.
I think you must check your build number devices.
You must use file boot.img from your factory image for root.
9.0.0 (PPR1.180610.009, Aug 2018) >This is version for my devices
9.0.0 (PPR1.180610.011, Aug 2018, Telstra) >?
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
reawo said:
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
Click to expand...
Click to collapse
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
newyesor said:
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
Click to expand...
Click to collapse
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
I receive also a bootloop and I didnt make any mistake. I also used this method pre Pie, I read that alot of users have problems with rooting Pie atm, even with TWRP
reawo said:
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
Click to expand...
Click to collapse
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
newyesor said:
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
Click to expand...
Click to collapse
I downloaded all the latest adb and fastboot. Never touched kernel or did custom recovery, always used the magisk method since i am on a pixel device. i also got the issue that my pc doesnt recognize my pixel from time to time, you think i should do a complete wipe?
I don't sure.
You are use platfrom-tool from sdk lastversion?(for flash via fastboot mode)
@reawo
I think you should flash factory image new again and factory reset your devices.
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta ,and close this app.****
7- Open app again and Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching (This process is not failed)***
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
Will work on the verizon variant (bootloader locked)?
sabi95190 said:
Will work on the verizon variant (bootloader locked)?
Click to expand...
Click to collapse
Nope. If it were that easy for bootloader locked Verizon phones, it would have been done months ago.
What happens if you lock the bootloader after all of this?
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
You'll wipe the phone, lose root, and be stock.
DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
TonikJDK said:
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
Click to expand...
Click to collapse
"Borderline"???? More like certifiably insane! ?
I realize this may be quite hard to answer but hopefully someone has some idea
I'm really tempted by the new galaxy tab a 8 with s pen (sm-p200/sm-p205). It's the perfect size for quick note taking
Thing is, I really want root and custom roms for it, does anyone have any thoughts as to how likely these are to eventuate? It shares the same chipset (exynos 7885) as the 2018 Galaxy A8 phone which has been rooted
Is this device likely to get root or custom rom support?
It seems we have magisk root here :
https://blog.gsm-social.com/2019/07/p205-u1-9-and-magisk/
But I don't understand Arabic. Can anyone check this site?
Could someone update on any feedback if they managed to get the P200/205 rooted?
Thanks a lot for the info
I've actually try this method on my P205 (China/ Hong Kong version) but could not make it work. It's possible that maybe works on an international version of the P205 or on the P200. Has anyone else tried this method with any success?
http://androidbiits.com/root-samsung-galaxy-tab-a-sm-p205-wisdom-easily/
VeEuzUKY said:
I've actually try this method on my P205 (China/ Hong Kong version) but could not make it work. It's possible that maybe works on an international version of the P205 or on the P200. Has anyone else tried this method with any success?
http://androidbiits.com/root-samsung-galaxy-tab-a-sm-p205-wisdom-easily/
Click to expand...
Click to collapse
Hi,
successfuly rooted mine. It is the malaysian version of the tab. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the keycombination for booting from the recovery partition. ( Vol Up + Power).
Use the tutorial from the readme on the magisk github page
Link: https://topjohnwu.github.io/Magisk/install.html
flushb
flushback666 said:
Hi,
successfuly rooted mine. It is the malaysian version of the tab. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the keycombination for booting from the recovery partition. ( Vol Up + Power).
Use the tutorial from the readme on the magisk github page
Link: https://topjohnwu.github.io/Magisk/install.html
flushb
Click to expand...
Click to collapse
Thanks a lot for the info! I'm on a Hong Kong/Chinese Global ROM (stock of course). What version of Android are you running in your rooted device now and do you have the WiFi or LTE version?
Thanks again
VeEuzUKY said:
Thanks a lot for the info! I'm on a Hong Kong/Chinese Global ROM (stock of course). What version of Android are you running in your rooted device now and do you have the WiFi or LTE version?
Thanks again
Click to expand...
Click to collapse
Hi,
i have the LTE Version SM-P205. As it arrived it had an old firmware so I first updated to the current stock Firmware P205DXU2ASH2 with the normal Samsung Update.
I downloaded the correspondending firmware files again for magisk patching with samfirm tool or if you or prefer from the usual samsung firmware download pages.
As i have a CSC from malaysia i took the XME CSC Firmware. From there on you can just fellow the magisk tutorial. Hopefully someone compiles a twrp recovery as firmware sources are available. So now i am on stock rooted firmware P205DXU2ASH2 .
I am using the LTE Version here in germany without any problems.
flushb
Download Mode Key Combo is VOL - + Vol +
flushback666 said:
Hi,
successfuly rooted mine. It is the malaysian version of the tab. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the keycombination for booting from the recovery partition. ( Vol Up + Power).
Use the tutorial from the readme on the magisk github page
Link: https://topjohnwu.github.io/Magisk/install.html
flushb
Click to expand...
Click to collapse
flushback666 said:
Hi,
i have the LTE Version SM-P205. As it arrived it had an old firmware so I first updated to the current stock Firmware P205DXU2ASH2 with the normal Samsung Update.
I downloaded the correspondending firmware files again for magisk patching with samfirm tool or if you or prefer from the usual samsung firmware download pages.
As i have a CSC from malaysia i took the XME CSC Firmware. From there on you can just fellow the magisk tutorial. Hopefully someone compiles a twrp recovery as firmware sources are available. So now i am on stock rooted firmware P205DXU2ASH2 .
I am using the LTE Version here in germany without any problems.
flushb
Download Mode Key Combo is VOL - + Vol +
Click to expand...
Click to collapse
Thanks again for the info. I will try follow the same steps and attempt to root again. I've had endless Samsung devices and this is the first time I am having problems trying to get one rooted.. Then again this is a much different process than the usual and we don't have Recovery yet. Given the limited sales and interest in this Tab (which is really a shame), probably there won't be too much development around it. This is actually the best price/features Tab Samsung makes now and the perfect form factor/size. If only the hardware was a bit faster and the camera a bit bigger.. but hey, can't have everything, haha
Thanks again for sharing the info, much appreciated
VeEuzUKY said:
Thanks again for the info. I will try follow the same steps and attempt to root again. I've had endless Samsung devices and this is the first time I am having problems trying to get one rooted.. Then again this is a much different process than the usual and we don't have Recovery yet. Given the limited sales and interest in this Tab (which is really a shame), probably there won't be too much development around it. This is actually the best price/features Tab Samsung makes now and the perfect form factor/size. If only the hardware was a bit faster and the camera a bit bigger.. but hey, can't have everything, haha
Thanks again for sharing the info, much appreciated
Click to expand...
Click to collapse
Hi,
no problem if you have questions just ask.
Attached screenshoot from root check
flushb
flushback666 said:
Hi,
no problem if you have questions just ask.
Attached screenshoot from root check
flushb
Click to expand...
Click to collapse
You know, I have received lots of PM regarding root as no one seems to be successful at it. You should start a new thread, call it something like "SM-P205 ROOT ACHIEVED" and post a step-by-step guide on how you did it. Not many people are following this thread here and news of root for this Tab will make thousands of people very happy worldwide.
If you have the time, you should do it. The whole community here appreciation is guaranteed
Thanks again
VeEuzUKY said:
You know, I have received lots of PM regarding root as no one seems to be successful at it. You should start a new thread, call it something like "SM-P205 ROOT ACHIEVED" and post a step-by-step guide on how you did it. Not many people are following this thread here and news of root for this Tab will make thousands of people very happy worldwide.
If you have the time, you should do it. The whole community here appreciation is guaranteed
Thanks again
Click to expand...
Click to collapse
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb
flushback666 said:
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb
Click to expand...
Click to collapse
Very cool, and I'll contribute to the thread with my feedback as much as I can myself too. Thanks again
flushback666 said:
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb
Click to expand...
Click to collapse
yes, please when you have time, do a tutorial. thanks a lot!!!
VeEuzUKY said:
Very cool, and I'll contribute to the thread with my feedback as much as I can myself too. Thanks again
Click to expand...
Click to collapse
Done!
Samsung Galaxy Tab A 8.0 (2019) with S Pen (SM-P205) ROOT ACHIEVED / Howto
flushb
flushback666 said:
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb
Click to expand...
Click to collapse
flushback666 said:
Done!
Samsung Galaxy Tab A 8.0 (2019) with S Pen (SM-P205) ROOT ACHIEVED / Howto
flushb
Click to expand...
Click to collapse
Awesome, I'll check it out now
Just bought the wifi variant of this tablet here in Germany too.....Seems to be a good 8" alternative. Looking forward to installing twrp and a Lineage ROM. Any news for that?
samsung unlockBL downgraderoot AutoBootCharge autoSd3HrIdle Charge to 65%
It is sharing of experience only without any liability or warranty.
Why: I use the tab very rarely but in critical requirement, I am getting it in discharged condition when i needed. Good news is that , in off condition it consumes around 1% per 10 days. I did not want to root it, but this tab at least shoud have have scheduled shutdown like other makes. The battery protect mode does not function properly. However thanks to Samsung for leaving the facility to unlock the Bootloader, rooting etc for advanced users (I feel definitely it has the capability to lock fully like apple )
Pre requirements
1. Samsung Tab A 2019 P200 (I have no experience on other models) charged more than 50%
2. Usb cable
3. Samsung USB Drivers
4. Windows 10 PC with UPS
5. Firmware suitable to your phone / region
6. Odin3-v3.14.4
7. 7Z ZS
8. Magisk Manager
9. Root explorer
I. Unlocking Bootloader
Normally I wouldn’t provide instructions for this, but since things had changed drastically from previous Samsung devices, and there are some caveats, I figure this would be helpful.
The following worked for me
• Installed Samsung USB driver on PC
• Allow bootloader unlocking in Developer options → OEM unlocking
• Disconnect the USB cable
• Power off the device
• Press and hold Volume Up & Down keys
• Insert USB cable
• Long press Volume up key
• Press Volume up ( yes) to unlock BootLoader
Just when you think the bootloader is unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
• Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
• Enable developer options, and confirm that the OEM unlocking option exists and grayed out! (yes it happened in my case) The VaultKeeper service will unleash the bootloader after it confirms that the user has the OEM unlocking option enabled.
• Your bootloader now accepts unofficial images in download mode.
II. Downgrade Flash instructions
1. Extract (unzip) the Samsung firmware file. Recommended using 7-Zip ZS
2) Install Samsung USB driver on PC if already not installed
3. , Extract Odin ZIP file Odin Tool 3.14.4 Downloaded, Open Odin execute file
4.) Remove Samsung . Google etc accounts from Tab
5. Reboot Samsung phone in Download Mode (hold Power + Volume Up buttons, it will booted to Recovery, select reboot to bootloader, Downloading screen will come then plug-in cable)
6. Connect you Samsung phone and wait until you get a blue symbol with com port no in Odin
7. Add the 1 file Samsung firmware to AP/PDA or 4 files Samsung firmware (AP/BL/CP/CSC) to it's slots (for P205 it will be 5 files)
8. Make sure re-partition is NOT ticked at Options at Odin
9. Click the START button, sit back and wait few minutes
Downgrading BootLoader-Theory
Downgrading BootLoader is Not possible unless you modify the BL….. .tar.md5 by removing the .bin files in it, then tar it up and flash in odin (- NOT TRIED).
The secure bootloader (sboot.bin) won't allow the downgrade of itself. you can't downgrade because the bootloader is protected by Rollback Prevention, So apparently I can only install firmware files which come with the same Bootloader.
We need to know what your current "Build Number" is on the phone. You also can't downgrade to other bootloaders that are lower then your current one, so if you're on bootloader 5 you need to use the Oreo bootloader 5 version firmware or it will not work. (Bootloader # is the 5th spot from the right.
Rollback Prevention (RP)
Rollback Prevention blocks the device from loading or flashing an approved but old version of boot components. Old versions of software may contain known vulnerabilities that attackers can exploit. Rollback prevention checks the version of the bootloader and kernel during both boot and updates, and blocks these processes from continuing if versions are unacceptably old. The lowest acceptable version of the bootloader is stored in secure hardware fuses when the device is flashed, and the lowest acceptable version of the kernel is stored in the bootloader itself. Whenever a vendor-applied update occurs, the lowest acceptable version can be incremented in the fuses. Because this value is kept in fuses, it cannot be decremented even through physical tampering. Rollback Prevention fuses are set at manufacturing time in the Samsung factory to prevent old firmware versions from overwriting newer ones.
Present version on device: P200ZHU2ASK2 (Settings>About Tabet>Software information>Build No XXXX XXXXXXX P200ZHU2ASK2, Service Provider SW ver ………….TGY// i.e Hongkong) , tried and failed is : P200ZHU1ASG1 , but now downgraded (bootloader is same version) P200ZHU2ASH2.
III. Rooting
Notes Installing Magisk
• Your device is non-A/B and uses system-as-root, so Magisk will be installed to the recovery partition of your device.
• Installing Magisk WILL trip KNOX (void Warranty)
• Installing Magisk for the first time REQUIRES a full data wipe, backup before continue
• You have to have your bootloader unlocked before following the instructions
Instructions on Rooting
1. Unzip the firmware P200ZHU2ASH2 on PC and copy the AP tar file to your Phone. It is normally named as AP_P200ZHU2ASH2_CL16717766_QB25581052_REV01_user_low_ship_meta_OS9.tar.md5
2. Install the latest Magisk Manager
3. In Magisk Manager: Install → Install > select and patch file> browse to location of file > tap and hold to select >open e.g AP tar file> working version / build is MagiskManager-v7.5.1.apk) (internet connection will make install button visible )
4. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
5. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
It will be copied to PC at C:\Users\......\AppData\Local\VirtualStore\Program Files (x86)\Minimal ADB and Fastboot
6. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options !
7. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
8. We now want to boot into the stock recovery to factory reset our device.
9. Disconnect the phone.
10. Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key (Power + Volume Up) to boot to recovery continue pressing the volume up button until you see the stock recovery screen (Not patched recovery , as it has Factory data reset, try again, view recovery logs only) as we need it.
11. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
12. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key (Power + Volume Up) to recovery. After seeing the bootloader warning screen (first screen), release all buttons so it can boot to the system.
13. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
14. After the device is booted up, done the usual initial setup. The following steps will need an internet connection.
15. I have manually installed the APK , downloaded in step 2 and continued to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
16. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
17. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the key combination for booting from the recovery partition. ( Vol Up + Power) but in my case it is always booting to Magisk.
Theory: Since some devices no longer use ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
After installing Magisk in recovery:
• (Powering up normally) → (System with NO Magisk) or if required reboot phone once OS is loaded
• (OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
• (OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
In my case (for my version of firmware) once magisk system is booted as above , every time it is loading magiskpatched system if shutdown is used (while charger is not connected ), but if we use reboot it is rebooting to Stock system- further, if we shutdown while charger is connected it is will shutting down and start charging with charging animation (means if we press power button it will boot to stock system) great advantage as stock (partially rooted?) also can be booted when required.
Additional Info
• Magisk actually patches 3 partitions on your device:
o vbmeta: replace with empty vbmeta image to disable partition verification
o boot: remove the signature of the image to prevent soft bricks
o recovery: this is where Magisk is actually installed
• Never, ever try to restore either of the 3 images mentioned back to stock! You can easily brick your device by doing so, and the only way out is to do full Odin restore following with factory reset. Just don’t do it.
• If you want to upgrade your device, never flash the stock AP tar file with the reasons mentioned above. Always pre-patch the firmware before flashing in Odin.
• If you don’t need to patch the full firmware, you can manually create a tar file with at least vbmeta.img, boot.img, and recovery.img to let Magisk Manager patch your images in the proper way.
Release Keys ( P&V+) for System with Magisk
Keep pressing volume up for Actual recovery
IV. Splash screen and warning screen change
1. Download the correct firmware of your Samsung
2. Unzip the firmware files with an extractor (winrar, etc)
3. Open the BL file WITH 7-ZIP EXTRACTOR (example) BL
4. BL_P200ZHU2ASH2_CL16717766_QB25581052_REV01_user_low_ship.tar.md5
5. Extract the param.bin.lz4 file WITH 7-ZIP EXTRACTOR
6. Open the param.bin.lz4 file WITH 7-ZIP EXTRACTOR and extract the param.bin file
7. Extract param.bin WITH 7-ZIP EXTRACTOR. All images are extracted in a folder.
8. edit logo.jpg and svb_orange.jpg or any other file suitably
9. select all files(not folder) and right click and select 7-Zip ZS Add archive > select archive format tar>ok to get param.bin.tar
10. Close 7-zip ZS, now change the name of above file from param.bin.tar to param.bin.
11. Right click on above param.bin select 7zip ZS > add archive…> select select archive format tar>ok to get param.bin.tar again
12. Change its name to BL_param.bin_only_to_change_logo (just to remind it is BL) Now we have the param.tar file ready for ODIN.
13. Open ODIN 3.13.3, start your phone in download mode, load the param.bin.tar file in the BL section and click on start.
Note: At the end of the flashing with ODIN the phone restarts showing the modified image, but it starts in recovery mode, you just have to accept restarting the phone, and it will start normally without losing data or the configuration of your Samsung Tab A P200
V. Auto Boot Charger connected once charged to more than 5 %
1. This is a bonus, if magisk is in effective condition, it will auto boot when charger is connected.
i.e. If it boots on auto when charger is connected that means that the sytem is magisk patched
(no need to edit lpm, however if we modify lpm, phone will hang at power symbol screen in non-magisk mode –to reset it, remove charger connection , press power+VolUp+VolDown simultaneously still phone restarts )
VI. Auto shutdown on 3 hours idle
1. Install Automate app
2. Import file
“Boot to on and Auto Shutdown by 3hr idle (reset by Foreground GMusicFMusicPAmp or Charge or 11 min on) V8.flo”
3. At automate settings select Run on System start up
3. Start flow
VII. Auto stop charging at preset max and restart charging preset min shutdown phone at preset battery low
1. Install latest AccA 1.0.23 app from github and connect to internet
(older beta app was changing battery % with every booting , showing fast draining without any actual drain etc, if charger is connected instead of rising battery level , it is showing as decreasing , i.e. battery sync , ghost effect issues)
Or
If above does not work uninstall AccA and connect to internet , open magisk manager >options>downloads>search for acc >install Advanced Charging Controller 2019.7.21-r1 (201907211) > install > rebotot)
Or if above is also not working properly please use battery charge limit v1.1.1 from play store (it will not have all options of AccA.
2. Configure as required like max charge 65 , re charging start level at 35 % shutdown at 5 % etc by editing config.txt file at root>data>adb>acc-data> capacity= 5, 101, 35-65 (101 not to stop intermittently between 35-65 % charging) and save
Now one can connect phone always to power source without wearing out Battery.
It my experince only and thanks and regards to all who contributed on respective sections / fields.
hi,
thx for the comprehensive instruction.
I have successfully rooting my sm-p205
I have 2 questions if u pls help me :
1. I want root my sm-p205 because I want to use tincore keymapper. but although now I have successfully rooted it, it seems that I have to set the selinux to permissive.
I have tried all I've found, from using selinuxmodechanger, selinuxswitch, or even using terminal with su 0 setenforce 0, and all not working. that selinux still enforcing.
can u pls help me how to change the selinux ?
2. if I couldnt change the selinux, than it's no use for me to still on root. Is there anyway to go back to original stock firmware and unroot ? because I read on the last instruction of magisk that I may not flash it again with usual ap file that it may make it brick ?
thx
Any custom ROM available for this tablet? I can't find one anywhere. Thanks
Nubia Red Magic 5G and 5S Roms and Root support Thread
Second post for TWRP and Magisk installation. Mirror for all roms and tools at end of post
Latest Official Rom updates
Android 11
US/Asia - V8.70 Nubia Link MD%: will update soon
EU - V7.70 Nubia Link MD5: will update soon
China - V9.50 Nubia Link MD5: 361AC13CA52AB83C239783FBAB088CEA
Android 10
US/Asia - V8.12 Nubia Link MD5: 6e930fc2431b3daeae2d94145926a6c1
EU - V7.15 Nubia Link MD5: bb9e3153716851e87f196ae6b4f44a2e
China - V6.23 Nubia Link MD5: BD447840ACA4D48F9443B94D2EAD890F
Change Log - 8.70 / 7.70 Android 11
- Security Patch October 2022
- Game Space enhancements
- Game space Gyro sensitivity menu
- game space touch sample rate improvement
- Fixed: corner of screen non-touchable in some cases
- Fixed: issue where game would fail to close
- Fixed: location of caller display
-Fixed: screen tearing when using 144hz
-
Bugs -
in Testing
- Always on display notification not showing
- memory leak in nubia launcher (requires forced close often to stop phone from lagging)
- small window mode for telegram and discord have wrong zoom/ aspect levels.
_____________________________________________________________________________________________________________
UNBRICK TOOL for 5S - Courtesy of @johnny886
Use this tool, with directions on the thread to restore your device to USA/Asia 8.07
you can then install TWRP and after flash any region rom after creating a somewhat universal unbrick tool for those in different regions.
Follow directions on the thread. but here is a link to the Thread. A Mirror for the tool is in my Personal Mirror at the bottom of this thread post.
Link to Thread
Confirmed working with 5G devices - but its recommended to update as soon as you unbrick.
_____________________________________________________________________________________________________________
For unlocked bootloader
Fix your fingerprint sensor.
here Link
--------------------------------
Update Instructions.
Note
for Android 11 do not flash through TWRP you will softbrick.
____________________________________________________________________
For Stock devices without root
- disable security. No pin, no face unlock, no finger print, no pattern. remove all security.
-download zip file
-go to system update tap three dots and select local update
-Navigate to update.zip and select.
-your phone will reboot and install new rom
- you phone will reboot once more and you will be greeted with your lock screen
- setup Phone with security options as before flash.
For devices with "LOCKED bootloader" Root / TWRP (not tested on A11)
- take backup of vbmeta and recovery partitions in TWRP
- change the name of both files to vbmeta.img and recovery.img
(VBmeta is often 64kb big and Recovery is often 90+mb big.)
- copy and paste these new img files into the update zip.
- flash through TWRP
- go back to main menu, select advanced, then select option
"disable replace TWRP" to keep TWRP as your recovery.
for devices with "Unlocked bootloader" (not tested on A11)
-make full backup
-download zip
-install zip through TWRP
-reboot
__________________________________________________________________________________
Custom Roms and Kernels
Kernel
Mattofthedead's Redmagic 5S kernel for LOS and Stock roms LINK
Roms
Rom Builder Ra's Custom Roms - Please post any bugs or issues in the related threads.
Pixel Experience Plus
Ressurection Remix
NOTE : to boot any Custom rom on the 5S device. Flash the Rom following the directions. then flash Matts LOS kernel Version 3
__________________________________________________________________________________
------------------------------
Old roms
Android 11
V8.65 Nubia Link MD5: 3d52e18c66366d3d23744184425d3926
V8.64 Nubia Link MD5: a7e61f5e2f7c377a6850cf6ac3a62aa7
V7.65 Nubia Link MD5: 746dad5b6145dfba1108355095a6ad46
V7.64 Nubia Link MD5: 55371ee8e5728aee2bc7df5b3a7d6585
V9.42 Nubia Link MD5: D492B92DD83B366508CDD74DE7D152A3
V9.40 Nubia Link MD5: D28F26289A9B75F771EF4F623F0BB367
V8.57 Nubia Link MD5: 266819d4b09c2c52aadb39e948dc84bc
V8.59 Nubia Link MD5: d7e32b7a3e833adc57fcf734aa47f5a3
V7.57 Nubia Link MD5: 81ee71869f660a28b631d871ffb59524
V7.60 Nubia Link MD5:
V9.26 Nubia Link MD5: 8997375CD97D8F7F261F21121FC8EFAA
Android 10
v6.18 Link MD5: 9AC5EA5F64835C1995E4A81D4973FB71
V6.13 Link MD5: F38ED2D7CB58252D308B29D1D4517DB9
V7.07 Link MD5: ffc3fdaf4afc522aa3a084d9275f2cb6
V7.14 Link MD5: 0f879160fbf8b556de5303207b93d0d1
V8.07 Link MD5: b30dab221be73292c5da7884afc0363f
V8.11 Link MD5: 85d9366a3017112cb68d66041e725ce6
________________________________________________________
Personal Mirror - Located in Eastern Canada
________________________________________________________
TWRP and root guide for 5S and 5G on Android 10 only - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked during and after process is complete.
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put an installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file found at the end of this post
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted. (CD = Change Directory)
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable replace TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Reboot to system for the first time and complete the initial setup. this is to create the user space partitions data/media ( preferably do not make a pin or pattern at this stage)
13. once in the rom, connect to PC and copy over the Magisk zip to the internal memory. then reboot holding Volume up
14. once back into TWRP (if you created a pin during setup TWRP will ask you for your pin to access data) go into install and flash the Magisk.zip you moved in step 13 then reboot. once back into the rom, you will see a Magisk app, tap it and allow to update, the APK will install latest version of the manager.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have an update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini - zip updated with Magisk 21.4 zip
MD5 for ADBfastbootmini.zip: 0ad97a9ae1539b26ef78c849b169e807
I'm working on a process that will update to Android 11, through TWRP and root, without losing data. Much like a stock update.
I will update the thread once my tests are complete.
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
josehdx said:
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
Click to expand...
Click to collapse
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Patrick Morgan said:
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Click to expand...
Click to collapse
Thanks
Working fine after full data partition wipe.
I have an additioal question regarding further updates, and i would not want to open a new topic. so, after flashing the zip, i "lost" TWRP but i already have root access. I wonder if is possible to flash upcoming updates with the default recovery built in on the phone, if not, i would assume i need to install TWRP again.in any case, will side loading update make any problem with the current system? i hope my question and context is clear
As these are official ROMs, they will replace the recovery and remove root from the phone.
If you do not have root, flashing these zips from the system menu local update should work. But if you have root or TWRP it's better to flash through TWRP.
You could just flash TWRP again after flash, but I personally modify the zip and add the recovery to it to save me going into fastboot after each update.
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Darkvenum79 said:
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Click to expand...
Click to collapse
I've spoken with another EU rom user, that has the same issue before. it seems it was an error in the stock rom.
reinstalling 7.07 from the links above should fix your problem.
both 7.07 (the EU rom) and 8.07 (the US rom) are exactly the same. the only difference is the languages from what I can tell.
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
No it wont.
There is a specific step by step that is required to get it functioning again. And it only survives until your next full wipe, which i assume you will do more often flashing non official roms.
I can grab the steps and edit this post for you.
Edit -
Prep.
have a black / very dark brown leather. (belt, wallet, etc)
a soft gel plaster / Bandaid
(something skin textured and in a pink / light beige colour) texture and colour are important.
First step is clear data in the infingerprint app in app info and remove permissionfor data memory - (you need to show system apps to find it)
- digit in call phone code:
*#9959#
(android 11 use Activity launcher (playstore) to enter fingerprint menu)
- uncheck performance checkbox , check only calibration checkbox
Steps -
1. Press start then wait.
2.Press next and with plaster / bandaid press on circle
3.Press next and use wallet / belt ( the display becomes black for black calibration)
4.Press next and use gel plaster / bandaid again but pinch it in so only the part with your finger touches the circle.
If you are lucky see success alert in green color
In system app in setting In-Display-Fingerprint allow access to data memory then reboot device.
Enjoy your Finger Print once more!
P.S. = do this procedure in a very dark room to improve the chances of it succeeding.
Thanks to qtr1st (Salem) and mikekrunk (Mike) for the steps and information.
josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Patrick Morgan said:
TWRP and root guide for 5S - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked after process is complete.
Pretty short step by step to get twrp and Magisk if you want, on your phone. (Red Magic 5S)
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put a installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file attached or mirrored
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted.
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have a update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
where is the link of twrp.img
sansha1211 said:
where is the link of twrp.img
Click to expand...
Click to collapse
Patrick Morgan said:
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
that file called Link ADBmini has all you need
Is it ok to flash Eu rom to my NA/asia rom?
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
reboot to bootloader by... power off device -> press and hold volume down and power button until you see the logo -> connect device to your computer then do the steps 7 to 12
also once you are in TWRP make sure you ... this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
if you have not removed your pin before flashing any of the roms. it asks you for YOUR own pin that you made when you setup the phone. so use your own pin.
the process of rooting your device, clears a security partition. (the VBmeta partiton)
this deletes the encryption you had on your phone. so the devices partitions are unaccessable and need to be wiped before you can boot to system.
you need to clear data. all data. then check in TWRP file browser if your data partition is clear. .. if you see folders with random letters its not been formatted correctly.
so, in the wipe menu on TWRP you should go into advanced and change the partition type to ext4 then back to f2fs to clear the partition of data.
once your phone is clear you should be able to wipe cache and davik then reboot to system for it to start like a factory reset.
sansha1211 said:
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
where is the link of twrp.img
Click to expand...
Click to collapse
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
fastboot flashing lock
josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
via cmd -- fastboot flashing lock
After i reboot in TWRP and disable replace TWRP, i install magisk from a USB otg, and then i wipe all data, then i reboot system but it keeps opening TWRP in every reboot, i had to install Stock Rom to have my phone back but without root, what im doing wrong?? thanks
Edit: now it worked, tried a few times and worked don't know what failed
Hi Guys, This morning I was attending a video conference on my Mi 9T, after the conferenece the battery was at 9%, so I turned off the phone (not having a power bank with me at the moment).
Then I went back to my office and connected Mi 9T to a charger, then head off to lunch. When I came back the phone is in fastboot. I tried turning off/on, reboot into system from recovery, and fastboot reboot command using PC. But it always goes back to fastboot. Is there anything else I can do except to flash?
ps. about 10 days ago I have the bootloader unlocked, orangefox reocvery installed (there were errors when trying to install twrp) and rooted (using magisk manager), rom is original stock rom
sparktrix said:
Hi Guys, This morning I was attending a video conference on my Mi 9T, after the conferenece the battery was at 9%, so I turned off the phone (not having a power bank with me at the moment).
Then I went back to my office and connected Mi 9T to a charger, then head off to lunch. When I came back the phone is in fastboot. I tried turning off/on, reboot into system from recovery, and fastboot reboot command using PC. But it always goes back to fastboot. Is there anything else I can do except to flash?
ps. about 10 days ago I have the bootloader unlocked, orangefox reocvery installed (there were errors when trying to install twrp) and rooted (using magisk manager)
Click to expand...
Click to collapse
Official twrp-3.5.2_9-0-davinci should work (you didn't mention your ROM full name and version)
Anyway, you can try without Magisk. Flash the original (not patched by Magisk) boot.img from Fastboot
Btw, that's one reason I prefer installing the Magisk by patching and flashing - in that case you would likely have on your PC the original boot img.
Otherwise, you now have to know exactly what was your stock ROM, download it (to PC) from xiaomiupdater, extract boot.img and flash it
zgfg said:
Official twrp-3.5.2_9-0-davinci should work (you didn't mention your ROM full name and version)
Anyway, you can try without Magisk. Flash the original (not patched by Magisk) boot.img from Fastboot
Btw, that's one reason I prefer installing the Magisk by patching and flashing - in that case you would likely have on your PC the original boot img.
Otherwise, you now have to know exactly what was your stock ROM, download it (to PC) from xiaomiupdater, extract boot.img and flash it
Click to expand...
Click to collapse
I didn't flash the rom, so it is still the original stock.
thanks for the tip boot.img, I will try that
The phone is back to life, thanks to @zgfg
what I have done:
1. download the rom from https://xiaomifirmwareupdater.com/
2. extract boot.img from the rom
3. install and run XiaomiTool V2 to ensure latest usb driver https://www.xiaomitool.com/
4. connect the phone to PC via USB, make sure it is connected by command : fastboot devices
5. flash the boot.img by command: fastboot flash boot boot.img
after that the phone rebooted to system, while the widgets were loading, it crashed and reboot, then it's all back to normal
sparktrix said:
The phone is back to life, thanks to @zgfg
what I have done:
1. download the rom from https://xiaomifirmwareupdater.com/
2. extract boot.img from the rom
3. install and run XiaomiTool V2 to ensure latest usb driver https://www.xiaomitool.com/
4. connect the phone to PC via USB, make sure it is connected by command : fastboot devices
5. flash the boot.img by command: fastboot flash boot boot.img
after that the phone rebooted to system, while the widgets were loading, it crashed and reboot, then it's all back to normal
Click to expand...
Click to collapse
Your phone boots without Magisk but bootloops with Magisk.
It is a common case due to a problem with some Magisk module (Magisk loads all modules when booting)
Do you remember which Magisk modules you had installed?
I'm not using OF but I think it has the interface where you can manage (hence also list) the Magisk modules
Telling you this because you can disable module(s) and try again with Magisk - but let's see first did you have modules installed and which of them
zgfg said:
Your phone boots without Magisk but bootloops with Magisk.
It is a common case due to a problem with some Magisk module (Magisk loads all modules when booting)
Do you remember which Magisk modules you had installed?
I'm not using OF but I think it has the interface where you can manage (hence also list) the Magisk modules
Telling you this because you can disable module(s) and try again with Magisk - but let's see first did you have modules installed and which of them
Click to expand...
Click to collapse
it was working with root (magisk manager) for about 10 days, in that duration there were no issues at all. only after sunday morning i truned it off it's stucked in bootloop.
btw, the first boot.img i flashed was not the correct version but enabled me to boot into system (although sluggish and reboots randomly) to see the exact version, after flashing the correct boot.img it's like nothing has happened.
i'm trying to install magisk with patch method now, will report if there is to be any issues.