Related
I tried flashing magisk via twrp but everytime it used to stuck at flashing boot image for hours ..then I manually flashed the patched boot image of magisk....it showed me success but no root was there... after that I flashed my original boot IMG and then tried flashing SuperSU with twrp but this time too same case stucked at flashing boot image .and no further improvement
Note I am on viper os ROM and have tried to root with both f2fs and ext4 but no results... pls help
I don't use this ROM at my phone, but as you can see in this Video from "Tio Hetfield"
the root method from LineageOS does also work.
Simply download the suitable file for your Phone and flash it.
https://download.lineageos.org/extras
If your Rom is based on Android 7.1 download the file for LineageOS 14.1 the processor architecture of the Lenovo P2 is "arm64"
To activate root after flashing unlock the Developer settings and activate root in the new menu entry.
This is only for root access, not the magisk framework
Repair system partition and also ensure data it ext4. This fixed it for me.
Solution for being stuck at "flashing boot image"
Ishann15 said:
I tried flashing magisk via twrp but everytime it used to stuck at flashing boot image for hours ..
Click to expand...
Click to collapse
I had the same problem, but found a solution!!!
I restarted the Phone by pressing the power button for 20 or so seconds.
Then again thanged into TWRP Recovery mode and there I installed the new beta SuperSU file SR1-SuperSU-v2.82-SR1-20170608224931.zip
That one just worked!
I was trying to root my zenfone 4 max (ZC554KL), and I found out that apparently I had to downgrade to another firmware, since I wasn't able to use the flash-all script that came with it, I tried to do it by imitating the script manually, by trying to do that, I screwed things up and soft bricked my phone. I also cannot get into recovery. I have flashed both TWRP and stock recovery img, but I am unable to get into recovery, it just goes back to the unlocked bootloader menu. I have tried flashing the firmware again by converting the system dat files to img, but I still cannot boot into system. I have zero idea on what do now. Please help me.
/* *** Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM/KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will laugh at you.
* BOOM! goes the dynamite
*/
I have a Moto E5 plus XT1924-5 (rhannah) in my possession. It is the only device in which this guide has been tested. I should serve for the rest of the rhannah and others moto e5 without problems.
My cust LATAM and the compilation version is OPP27.91-25. Do not make the fast route if you do not have exactly the same device with that same compilation number or if you do not know exactly what you are doing.
The guide is divided into parts. First how to backup everything. Then how to root with magisk (for that there is fast and slow way)
What do you need.
- 1 Moto e5 Plus
- 1 Micro Sd card (minimum 4gb)
- Usb Cable
- Adb and fastboot drivers installed
-. Read the complete guide before to understand what they are doing (5 minutes, no bricks)
- 1 Brain.
- Comprehensive reading
FIRST STAGE (COMMON). BACKUP OF EVERYTHING.
Our phone have its own TWRP, works relatively well, except that it does not allow decrypting and therefore mounting the data partition and internal storage.
The steps.
1.- You open the bootloader. Look at any guide to open bootloader in Motorola, it has not science and is common for all motorala phones
2.- Download the Moto e5 play (james) TWRP (https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323)
3.- We put the phone in fastboot. For this, we activate the USB debugging and with the connected phone we write in a CMD "adb reboot-bootloader"
4.- In fastboot we write in our CMD "fastboot boot twrp_james.img". This will start our phone in TWRP without permanently flashing the recovery (for no reason to flash it)
5.- The recovery will take something to start and it will ask us for our key to decrypt data. We need to press cancel as the recovery will fail even with the correct key. DONT MOUNT SYSTEM WITH RW PERMISSION
6.- Go to the backup section, we choose as our destination SD and we backup
ALL except data and cache.
7.- Restart the cell phone and we put our backup in one or more safe place (the misfortunes happen)
With this we already have a backup of boot and system so we will not have problems if we make mistakes later
SECOND STAGE (THE DIFFICULT ROUTE) Patching our own boot.img for magisk
1.- In android we download and install he last magisk manager APK (available in my google drive account https://drive.google.com/open?id=1XD7Q7NXmchTNsSJ-oqt2TOXO8osroVJp)
2.- We open it, we go to setting and in "Update Channel" we activate the beta channel of updates (THE DEVICE WILL ENTER IN BOOTLOOP WITHOUT WITHOUT THIS STEP)
3.- In the main screen of magisk we are going to install, we accept to install the version of magisk 16.7 or superior (by no reason a lower one) and we go to "Patch boot image file", we select the file boot.emmc.win of our backup and We wait for you to patch our boot. (sdcard/TWRP/ Backups /ZL5223F3V8 / DATE /)
4.- Magisk will generate a patched boot in /internalstorage/MagiskManager/patched_boot.img
5.- Copy patched_boot.img to our computer, put the phone in fastboot mode and flash the patched_boot.img with the command fastboot flash boot patched_boot.img, and later restart the phone.
Ready!. Magisk perfectly installed our phone. In my case, safety.net passes without problems.
Second stage. (The easy way). SAFE ONLY in the variants indicated
0- Open bootloader
1.- Make the backups (iam not responsable of this)
2.- put the phone in fastboot mode
3.- Flash my boot.img patched for magisk "fastboot flash boot patched_boot.img"
Moto e5 plus XT1924-5 OPP27.91-25
https://drive.google.com/file/d/1XHtV1rI1cDPQCAw8otuBRxeSzNBzKWQn/view?usp=sharing
Moto e5 plus XT-1924-8 (Thanks Arslan_Rulex)
http://www.mediafire.com/file/zu9mefxd397nr1f/patched_boot.img/file
Moto e5 plus XT1924-7 (MetroPCS) (Thanks theUsualSuspexx)
https://drive.google.com/open?id=1UzP5NEBLD3_ex_zU2EoijVFs1uiGBEMI
Backups TWRP
Moto e5 plus rhannah xt1924-5 (OPP27.91-25.) Include twrp backup of rooted boot partition with system partition, and untouched boot partition (separated)
https://drive.google.com/open?id=1Vu0CvgBc0QeSxWOLyRgcMykvJ9ckgQy_
I hope you send yours, since there is only one fastboot image for this phone.
Thanks a lot, now im root in my e5 plus OPP27.91-41, via THE DIFFICULT ROUTE. the easy route give me a softbrick, :highfive:
folken2003 said:
Thanks a lot, now im root in my e5 plus OPP27.91-41, via THE DIFFICULT ROUTE. the easy route give me a softbrick, :highfive:
Click to expand...
Click to collapse
What rom are you using bike friend e5?
Rodneyy said:
What rom are you using bike friend e5?
Click to expand...
Click to collapse
the stock rom
In case I want to download and install an OTA update, is it possible to undo this by uninstalling Magisk (and its modules, Exposed, etc.) and reinstall the old boot.img via TWRP? Or would that brick the device?
Hinterecke said:
In case I want to download and install an OTA update, is it possible to undo this by uninstalling Magisk (and its modules, Exposed, etc.) and reinstall the old boot.img via TWRP? Or would that brick the device?
Click to expand...
Click to collapse
In theory, reinstalling your unmodified stock boot image will remove all traces of systemless root. On OTA installations with most Moto devices, the update.zip performs a number of checksums in order to verify that certain partitions are unaltered. Your /recovery, /boot, /system, /oem, and /vendor partitions are typically included in these checksums. Even if these partitions have never been altered, an OTA will nevertheless fail if any of the aforementioned partitions have ever been mounted as r/w, even if they were not altered or modified. So, if you've ever mounted any of these partitions as r/w via TWRP, your OTA will fail, but the likelihood of a brick is extremely slim. The best way to prepare your device for an OTA is to flash a full factory firmware package via fastboot or RSD Lite. RELOCKING THE BOOTLOADER IS NEVER NECESSARY ON A MOTO DEVICE FOR INSTALLING AN OTA UPDATE.
Alternatively, you may use a UTF-8 encoding capable file editor to remove checksums from your captured OTA package. Then, you can flash it with TWRP even on a rooted device.
So to fully answer your question, you would want to install stock recovery and boot image via fastboot, not TWRP, since the OTA will fail with a custom recovery. The OTA will need to be installed via stock recovery, not TWRP.
I used @avilav 's rooting method he described over here and didn't install TWRP because it would be useless, I actually read the big warning, so still on stock recovery.
Don't have the factory firmware for my rhannah XT-1924-1 (reteu) either so flashing that is not much of an option. Maybe I should just leave it this way cause most MOTO updates, for the cheaper devices, are mostly just security updates, no new features, software, etc.
MotoJunkie01 said:
In theory, reinstalling your unmodified stock boot image will remove all traces of systemless root. On OTA installations with most Moto devices, the update.zip performs a number of checksums in order to verify that certain partitions are unaltered. Your /recovery, /boot, /system, /oem, and /vendor partitions are typically included in these checksums. Even if these partitions have never been altered, an OTA will nevertheless fail if any of the aforementioned partitions have ever been mounted as r/w, even if they were not altered or modified. So, if you've ever mounted any of these partitions as r/w via TWRP, your OTA will fail, but the likelihood of a brick is extremely slim. The best way to prepare your device for an OTA is to flash a full factory firmware package via fastboot or RSD Lite. RELOCKING THE BOOTLOADER IS NEVER NECESSARY ON A MOTO DEVICE FOR INSTALLING AN OTA UPDATE.
Alternatively, you may use a UTF-8 encoding capable file editor to remove checksums from your captured OTA package. Then, you can flash it with TWRP even on a rooted device.
So to fully answer your question, you would want to install stock recovery and boot image via fastboot, not TWRP, since the OTA will fail with a custom recovery. The OTA will need to be installed via stock recovery, not TWRP.
Click to expand...
Click to collapse
+1 .If you never mount system rw before backup you should not have problems. It is not necessary to do it with this way of rooting, and in theory if you make a backup system-image you should not have problems , since that is a bit-by-bit backup
help me
folken2003 said:
Thanks a lot, now im root in my e5 plus OPP27.91-41, via THE DIFFICULT ROUTE. the easy route give me a softbrick, :highfive:
Click to expand...
Click to collapse
como lo hiciste?
mickeynews said:
como lo hiciste?
Click to expand...
Click to collapse
RTFM
I have the Boost Mobile (Sprint) version which shows as XT1924-8 in the Hardware tab in settings. It has the Snapdragon 435 1.4Ghz octacore w/ 3GB ram 32GB rom. I was able to follow these steps to unlock the bootloader, fastboot into TWRP, did a backup, install magisk manager, patch the boot image and then flash it via fastboot. I might try to get unltd tethering working but for now WOOOOOO-HOOOOOO, this was a rush!
reaper-death said:
I have the Boost Mobile (Sprint) version which shows as XT1924-8 in the Hardware tab in settings. It has the Snapdragon 435 1.4Ghz octacore w/ 3GB ram 32GB rom. I was able to follow these steps to unlock the bootloader, fastboot into TWRP, did a backup, install magisk manager, patch the boot image and then flash it via fastboot. I might try to get unltd tethering working but for now WOOOOOO-HOOOOOO, this was a rush!
Click to expand...
Click to collapse
That's excellent news. You are encouraged to start a rooting tutorial thread for the xt1924-8. By the way, upload me a system image and boot image from a TWRP backup of your device and I'll compile a TWRP flashable stock ROM for the device.
MotoJunkie01 said:
That's excellent news. You are encouraged to start a rooting tutorial thread for the xt1924-8. By the way, upload me a system image and boot image from a TWRP backup of your device and I'll compile a TWRP flashable stock ROM for the device.
Click to expand...
Click to collapse
Sure, I'm uploading the files to mediafire and should be up in a little while.
As for the tutorial basically I did ALMOST everything. I didn't flash twrp and I didn't flash noverity. I did get stuck with no boot when I flashed the patched boot img but figured it out (update channel wasn't set to beta). To fix that boot issue I restarted back to the bootloader then booted twrp and then restored just my boot image from the backup. Then I did the magisk patching and then flashed it and this time I got root.
reaper-death said:
Sure, I'm uploading the files to mediafire and should be up in a little while.
As for the tutorial basically I did ALMOST everything. I didn't flash twrp and I didn't flash noverity. I did get stuck with no boot when I flashed the patched boot img but figured it out (update channel wasn't set to beta). To fix that boot issue I restarted back to the bootloader then booted twrp and then restored just my boot image from the backup. Then I did the magisk patching and then flashed it and this time I got root.
Click to expand...
Click to collapse
Ok. Got it. You basically followed standard protocol based on the tutorial for other variants.
Cool. Once you get me the files I should be able to cook up the ROM and post sometime tomorrow. Thanks for your efforts and your feedback. This will help other members with your variant.
Ok, here is the link:
http://www.mediafire.com/?6862xg60zi8ai
Edit: I also was able to pull the stock recovery img using the XDA TWRP app in android.
c̶a̶n̶ ̶s̶o̶m̶e̶o̶n̶e̶ ̶p̶l̶e̶a̶s̶e̶ ̶u̶p̶l̶o̶a̶d̶ ̶t̶h̶e̶ ̶m̶e̶t̶r̶o̶p̶c̶s̶ ̶o̶r̶ ̶t̶ ̶m̶o̶b̶i̶l̶e̶ ̶T̶W̶R̶P̶ ̶b̶a̶c̶k̶u̶p̶?̶ ̶t̶h̶a̶n̶k̶s̶
hi how do you install the twrp backup you posted
seantello97 said:
hi how do you install the twrp backup you posted
Click to expand...
Click to collapse
Just like any twrp backup. Put it in your twrp/backups/*your phone's serial number*/*put backup here*
Stuck in bootloader
Hi thanks for that. I flashed Magisk on my e5 plus and rebooted but it takes me to bootloader every time. any ideas?
Hi the boot.img isn't showing up where i put it
Hello, I was searching for a root for my "new" Samsung J3 Prime (SM-J327W) that I got from my sister. I did the OEM Unlock and in ODIN Mode, it says that it's also "FRP LOCK : OFF". So far, CF-Auto-Root didn't work and all TWRP images, that I found, wouldn't even download on the device . I tried images for the "T", "P" and "U" variants also. The "P" one, lead to bootloop (I recovered stock rom since I got it). So is there any root for this device? It's on the latest versions of firmware and Android available for it.
Did you find anything for the J327W yet? I can only find ROMs for the 320, 327P and 330. I've been having very erratic battery life for over a year. It started after a factory android update. Sometimes my battery life will drop from 70% down to less than 5% in a minute. I've done a factory reset, cleared the cache and replaced the battery but nothing has helped. Trying to put a new ROM OS on this POS is my last hope.
shane_c said:
Did you find anything for the J327W yet? I can only find ROMs for the 320, 327P and 330. I've been having very erratic battery life for over a year. It started after a factory android update. Sometimes my battery life will drop from 70% down to less than 5% in a minute. I've done a factory reset, cleared the cache and replaced the battery but nothing has helped. Trying to put a new ROM OS on this POS is my last hope.
Click to expand...
Click to collapse
I think you'll need a battery replacement at this point... I did build a TWRP ROM myself for my popeltecan (code name of J327W in Canada apparently) but, according to a TWRP Builder Developer, my device might have some kernel issues with TWRP so I can share my ROM but I am not sure it will work on your device. Do you have your stock ROM in case?
Here is a GDrive link to my recoveries, there's the stock and the twrp one but be aware that you need all the ROM if there is a problem with the twrp (that means stock : BL, AP, CP and CSC). But you can use the stock recovery to build a device tree.
https://drive.google.com/open?id=1dNZGaNvCtd5kinHNfnr8MV5Z6o2_GOj4
MikasuX14 said:
I think you'll need a battery replacement at this point... I did build a TWRP ROM myself for my popeltecan (code name of J327W in Canada apparently) but, according to a TWRP Builder Developer, my device might have some kernel issues with TWRP so I can share my ROM but I am not sure it will work on your device. Do you have your stock ROM in case?
Click to expand...
Click to collapse
Replaced the battery about 3 months ago but it made no difference. I have some vacation time coming up so will have a little more free time to look into things.
shane_c said:
Replaced the battery about 3 months ago but it made no difference. I have some vacation time coming up so will have a little more free time to look into things.
Click to expand...
Click to collapse
Maybe a factory reset would be a good idea to try. If you want to try my twrp recovery build, you'll be wiping your data anyway. I highly suggest you to get the full stock rom since even just getting back the stock recovery could end up with a weird sort of corruption (like duplicated or unknown options inside the Settings app, or at least I experienced that). I am not responsible if it breaks anything, you were warned to get your precautions such as getting the stock rom.
MikasuX14 said:
Hello, I was searching for a root for my "new" Samsung J3 Prime (SM-J327W) that I got from my sister. I did the OEM Unlock and in ODIN Mode, it says that it's also "FRP LOCK : OFF". So far, CF-Auto-Root didn't work and all TWRP images, that I found, wouldn't even download on the device . I tried images for the "T", "P" and "U" variants also. The "P" one, lead to bootloop (I recovered stock rom since I got it). So is there any root for this device? It's on the latest versions of firmware and Android available for it.
Click to expand...
Click to collapse
hi if your still looking. i looked into it and the j327u twrp does work on j327w. i had the same problem trying to gain SU access with the other image files for j327w i had to use magisk zip and install it from twrp menu. had to format data and mount system in twrp.
twrp j327u does work but i could not get supersu or magisk to work, my build is J327WVLS4BSK1 with 8.1.0 oreo. i'm not sure there's a way to get past dm-verity using the boot patch by asphyx in the TWRP threads or the universal dm-verity workaround by zackptg5.
i first flashed twrp j327u using odin, ran up against dm-verity when running supersu. both MikasuX14 and another twrp j327w version i found would also flash and load, but the touchscreen wouldn't register my input. cfar didn't work either
sfirmware (website) has workable firmware for rev 4 j327w builds in case you need to recover your phone from soft brick - i could get my build's firmware to flash using the patched odin 13.3.3 version found on this site
bytwigorlimerick said:
twrp j327u does work but i could not get supersu or magisk to work, my build is J327WVLS4BSK1 with 8.1.0 oreo. i'm not sure there's a way to get past dm-verity using the boot patch by asphyx in the TWRP threads or the universal dm-verity workaround by zackptg5.
i first flashed twrp j327u using odin, ran up against dm-verity when running supersu. both MikasuX14 and another twrp j327w version i found would also flash and load, but the touchscreen wouldn't register my input. cfar didn't work either
sfirmware (website) has workable firmware for rev 4 j327w builds in case you need to recover your phone from soft brick - i could get my build's firmware to flash using the patched odin 13.3.3 version found on this site
Click to expand...
Click to collapse
heres what i did. i soft bricked, bootlooped and had to flash firmware from sfirmware a few times to get it to work
i used a twrp for j327u i found on a another similar thread on this topic. i flashed it with odin.
once inside twrp menu i went to wipe menu, i hit format, then back to mount menu, checked boxes data/system (previously data or system wouldnt check off before formatting data).once data and system were mounted i then
plugged phone back into computer while in twrp menu. the phone showed up as J327u cut/paste the latest magisk .exe into the internal storage of j327u (on computer) . i then on twrp menu found and installed magisk exe finally got it to properly install magisk i then in reboot menu hit system and reboot.
the phone restarted after awhile like it was factory reset but once i set up the phone magisk apk was already installed and root access was available. hope this helps.
so i've been busy for a long while before looking back into this. I will try again with the J327U rom. Right now, i struggle to find stock roms of the J327W because i flashed a not working twrp apparently and it locks my boot.
The J327U TWRP didn't work for me. Though, twrp itself works but i cannot get the system to boot and i cannot get to root it, no matter what i tried, i ended up in boot loop.
I managed to root this phone without TWRP. I used Linux tools to do this so I'm not sure if it could work on Windows.
Requirements:
Stock ROM for your phone (I used samfirm.js to pull it from the Samsung servers but downloading from sammobile.com works too)
A way to extract zip files
A way to extract tar files
Heimdall flasher (https://www.glassechidna.com.au/heimdall/)
Magisk Manager APK
An Internet connection on your phone
A compatible USB connector for your phone
Of course, a SM-J327W running the stock Android firmware
Obligatory warning: This WILL void the warranty of your phone and permanently trigger the warranty void flag. It also WILL cause a factory reset, so back up all your data first.
Bear with me, because there are a lot of steps. This will take around 15 to 30 minutes.
You will need to download and extract a stock ROM for your phone. Make sure that you download a ROM for the SM-J327W and not another model. Also make sure to download the latest version available.
Stock ROMs usually come in a zip file containing a few tar.md5 files. You will only need to extract the one that starts with "AP" for this procedure.
Step 1: Extract the tar.md5 file that starts with "AP" from your stock rom.
Step 2: Open the tar.md5 file in an archive manager. You may need to remove ".md5" from the end of the file.
Step 3: Extract the boot image (boot.img) from the AP file.
Step 4: Upload the boot image and the Magisk Manager APK to your phone. You can use ADB to transfer the files. For example:
adb push boot.img /storage/emulated/0
adb push Magisk-v22.0.apk /storage/emulated/0
Step 5: Open the files app on your phone. Navigate to the internal storage and tap on the Magisk APK file to install it. You may be prompted to allow installation from unknown sources.
Step 6: Open the Magisk app. It should say that Magisk isn't installed and it shoulld say "Yes" beside "Ramdisk". Tap the cogwheel icon in the top-right corner.
Step 7: Due to a bug in Magisk, you need to install version 21 instead of the latest version (v22). Set the update channel to "Custom Channel".
Step 8: When prompted, enter the following URL: "https://raw.githubusercontent.com/t...d863d3a15c6a2276b1061a280ece80ed7/stable.json" (Without the quotes.)
Step 9: Now it's time to patch the boot.img file. Tap the button to install Magisk and select the option to patch a file. When prompted, navigate to the internal storage and select the boot.img file that you transferred previously.
Step 10: Magisk will patch the file and tell you where it saved the patched file. Transfer the patched file to your computer. You can use ADB for this, for example:
adb pull /storage/emulated/0/Download/magisk_patched_XXXXX.img
Remember to replace the Xs with the the random characters that Magisk added to the file name.
Step 11: Reboot your phone into Download mode. You can shut it down and then hold the power, home, and volume down buttons at the same time to enter Download mode or use ADB: "adb reboot bootloader"
Step 12: A warning may show about the dangers of installing a custom OS. Press the volume up key to continue.
Step 13: The screen should now show "Downloading... Do not turn off target." If your phone isn't already plugged into your computer, plug it in now.
Step 14: Use Heimdall flasher to flash the patched boot image. For example:
heimdall flash --BOOT magisk_patched_XXXXX.img
Again, replace the Xs with the random characters that Magisk added to the file name.
Step 15: After a few seconds, Heimdall should report that the flash succeeded and your phone will reboot. It may take longer than usual. Leave it to do its thing and DO NOT pull out the battery.
Step 16: Your phone will show a notice that unauthorized changes have been detected and will prompt you to factory reset it. Press the button to perform the factory reset.
Step 17: Set up your phone as if it was new. It's not rooted yet, but you're really close if you got so far.
Step 18: Once you reach the home screen, upload the Magisk Manager APK to your phone again and install it like before.
Step 19: Open Magisk Manager. It will show that Magisk is installed and may prompt you to reboot to complete installation. Do not update Magisk to v22 or you will lose root access and you will have to flash the patched image again.
In the (very unlikely) case that your phone doesn't boot after flashing the patched boot.img, you can simply flash the original boot image and it should be fixed.
CONGRATULATIONS! You just rooted your SM-J327W successfully.
I also managed to port TWRP to this phone with the touchscreen working using the kernel from a recovery image for the SM-J327P found here: https://forum.xda-developers.com/t/...-1-samsung-galaxy-j3-emerge-sm-j327p.3573607/. All the partitions are mapped correctly. Due to a bug (presumably with the kernel), the data partition can unfortunately only be mounted read-only. However, this shouldn't affect being able to flash zips on your phone and you can insert an SD card to write backups onto. In the future, I may port CWM recovery to this phone using the stock kernel to be able to mount the data partition read-write.
You can find my custom recovery attached to this reply.
Follow up: It seems that the bug that causes Magisk to fail is fixed in the latest version (v22.1.) As a result, steps 6-8 in my previous post are unnecessary.
MikasuX14 said:
Here is a GDrive link to my recoveries, there's the stock and the twrp one but be aware that you need all the ROM if there is a problem with the twrp (that means stock : BL, AP, CP and CSC). But you can use the stock recovery to build a device tree.
https://drive.google.com/open?id=1dNZGaNvCtd5kinHNfnr8MV5Z6o2_GOj4
Click to expand...
Click to collapse
link is dead do you have twrp for j327w?
Hello Guys
I was on a custom Android 12 rom. For some odd reason, my phone rebooted. Now i cant get into TWRP Recovery.
I can fastboot, but TWRP is for Android 11, and my Rom is Android 12.
What can i do to either flash stock Rom via CMD, or what can i do to get into TWRP?
Note i cant boot into my rom either
is there any way i can get into TWRP with an Android 12 Custom Rom?
TWRP is a GUI based recovery, a menu presented to you once you boot device into recovery mode, where you can select some actions from, it isn't part of Android OS itself, it doesn't depend on Android OS's version, AFAIK.
Sounds to me like you need to flash back to stock rom then use the xiaomi flash tool to set everything back to stock and restart the root process.
At this point I would advise against rooting android 12 as it is brand new and the root process is very unstable. Therefore I recommend only stock until twrp and magisk catch up.
shivadow said:
Sounds to me like you need to flash back to stock rom then use the xiaomi flash tool to set everything back to stock and restart the root process.
At this point I would advise against rooting android 12 as it is brand new and the root process is very unstable. Therefore I recommend only stock until twrp and magisk catch up.
Click to expand...
Click to collapse
okay so i managed to get into TWRP via fastboot. I have the stock OOS 11..
please tell me if i have the process right
Boot into TWRP
swipe to factory reset
wipe data/cache/davlik
Hit install and flash Stock OOS11
Flash latest TWRP
if that is correct cool
But after flashing latest Twrp, i cant boot back into twrp recovery. I again have to boot via fastboot.
I have flashed the TWRP boot image, but still nothing