While trying to root my Mi5, I accidentally misplaced the SuperSU zip into my main internal memory so now I can't install it through TWRP. My phone is now stuck on the Mi boot logo, but I still have access to fastboot and recovery. How can I fix this? Thank in advance.
Edit: nevermind I fixed it using adb sideload
Related
Hi
I recently installed twrp 3.1.0-0 through cmd. I saw a thread about twrp 3.2.1.0-0 so it was a zip file instead of img file so I went to twrp and flashed that zip after that whenever I reboot my phone to system in stays on mi logo forever. Then I flashed a rom .tgz file through mi flash tool. To check I went back to twrp using my pc cmd typing the command "fastboot boot twrp.img" . I was taken to twrp recovery. I did nothing and tried to boot back system again same thing stuck here forever. I had to go through the same flashing process to get my phone back.
you probably need to restart again by flashing a new rom and read carefully howto.
U Can just flash no-verity-opt-encrypt here https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Mahadi14 said:
Hi
I recently installed twrp 3.1.0-0 through cmd. I saw a thread about twrp 3.2.1.0-0 so it was a zip file instead of img file so I went to twrp and flashed that zip after that whenever I reboot my phone to system in stays on mi logo forever. Then I flashed a rom .tgz file through mi flash tool. To check I went back to twrp using my pc cmd typing the command "fastboot boot twrp.img" . I was taken to twrp recovery. I did nothing and tried to boot back system again same thing stuck here forever. I had to go through the same flashing process to get my phone back.
Click to expand...
Click to collapse
if stock recovery is replaced by TWRP then stock rom wont boot.
to boot you need to disable dm-verity in boot.img magisk does this while flashing.
so to boot just flash magisk or dm-verity disabler or lazy flasher
Hi,
I unlocked the bootloader on my Oneplus 3T, then flashed TWRP. Unfortunately I misread and tapped on the read-only bit, and since then I am not able to boot into TWRP after the first time.
These are my steps (which I am trying over and over)
- fastboot;
- flash TWRP with fastboot flash recovery recovery.img
- disconnect the phone and shutdown
- boot into recovery with power/vol-
- twrp boots; I reboot into system
- system boots; i shut down
- boot into recovery with power/vol-
- the default recovery loads instead of TWRP.
I tried ticking and unticking the checkbox for read only under Mount in TWRP; I tried restoring the full backup. Every time it keeps going into the default recovery
from TWRP, I can shut down and boot into recovery and I'll get TWRP. I can reboot into recovery and I'll get TWRP. But as soon as I reboot into system, TWRP is gone
any ideas?
https://forum.xda-developers.com/on...elp-thread-t3509641/post75240034#post75240034
eLcTrOn said:
https://forum.xda-developers.com/on...elp-thread-t3509641/post75240034#post75240034
Click to expand...
Click to collapse
hm, ok thanks; I must have missed that bit.
I flashed TWRP again, then installed SuperSU from it. It went fine, then it prompts me to reboot. upon reboot I am using root checker and it says it's not done. I reboot into recovery and I get the default one again...
edit: nevermind, I used another zip for supersu and it worked. now it boots into twrp, many thanks.
Wouldn't it be better to use Magisk?
przemcio510 said:
Wouldn't it be better to use Magisk?
Click to expand...
Click to collapse
I flashed FreedomOS with Magisk at the end.
I was trying to root my phone and had already unlocked by bootloader, flashed TWRP, and made a NANDroid backup. I had the Magisk zip from Magisk Manager on my SD card. I booted into TWRP using the commands
Code:
adb reboot bootloader
Code:
fastboot flash recovery twrp-3.2.3-0-ali.img
and
Code:
fastboot boot twrp-3.2.3-0-ali.img
Once in TWRP, I mounted the cache, vendor and micro SD card partitions. I unmounted them immediately afterwards and then installed the Magisk zip file. The reason that I mounted and unmounted the SD card was because, based on me trying random things, it was the only way for TWRP to show the zip file. Afterwards, I rebooted the system, the "Your device has been unlocked and can't be trusted" screen came up as normal, except that where it said "bad key" before, it said "N/A". The device did not move past this screen and instead stayed at that screen. I managed to turn it off by holding the power button for far longer than normal. I then booted my phone into TWRP and restored a previous backup. Is there a potential cause for this? Is there an alternative method of rooting that I'm not aware of?
did you install the no verity boot for your variant?
The only thing I installed was the zip. If it wasn't in the zip, then I didn't install it. How would I install that and where would I get it?
lucror said:
The only thing I installed was the zip. If it wasn't in the zip, then I didn't install it. How would I install that and where would I get it?
Click to expand...
Click to collapse
Check this thread
https://forum.xda-developers.com/mo...oot-magisk-installation-t3816569/post77074751
Will the fact that I have already tried to install Magisk affect the process? I did flash my TWRP backup, so would that have any bearing on the process? Sorry if these are basic questions, I haven't rooted a phone before and I'm trying to be very cautious.
lucror said:
Will the fact that I have already tried to install Magisk affect the process? I did flash my TWRP backup, so would that have any bearing on the process? Sorry if these are basic questions, I haven't rooted a phone before and I'm trying to be very cautious.
Click to expand...
Click to collapse
Nope, you're overwriting the boot image when flashing no-verity so Magisk would be gone anyways.
Okay. Thank you for your help everyone. I'll try that when I get the chance.
I followed the steps mentioned in the below link to root my Mi 5 phone and now my phone is stuck with Mi logo upon reboot to system.
rootmygalaxy.net/root-xiaomi-mi-5-install-twrp-recovery
Things I did:
1. Enabled USB debugging and OEM unlock option
2. Installed ADB v1.3
3. Unlocked bootloader using mi 5 flash unlock tool
4. Downloaded twrp-3.2.3-0-gemini and renamed as twrp.img
5. Installed twrp recovery via fastboot using the following commands
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img
6. Copied SuperSU-v2.82-201705271822 to phone's internal memory
7. Booted device into twrp recovery. Under wipe option, did a factory reset. Installed SuperSu successfully. Clicked 'swiped to wipe' under wipe cache\delvik.
8. Then rebooted to system from twrp main menu
After the above steps, my phone didn't reboot and got stuck in Mi logo. This is the first time I tried rooting my phone .
Could you please suggest some idea to recover my phone? Thanks in advance.
It's likely not a big deal at all. Look up putting your device to EDL mode and flashing stock image with xiaomiflash. If you choose the correct stock image, everything will be fine.
Hi,
I think I broke something while updating my system, I was going from old PixelExperience to a new one and while flashing it with TWRP, it broke TWRP, instead of booting to it through recovery it started booting to fastboot, but I decided to try to fix it and flash TWRP again. When I was doing that my device broke even more. Now I am stuck in fastboot, I am not able to boot into system or flash TWRP.
The only way I can access TWRP is if I do fastboot boot twrp.img from my folder on my PC, but after I get to TWRP and try to install PixelExperience again, rebooting to system boots me back to fastboot.
I HAVE SCREWED UP ROYALLY. Please help, I am out of ideas and don't know what to do...
Update: managed to flash OrangeFox recovery from the booted TWRP so thats some progress I guess?
Fixed, thank god for OrangeFox, it helped, idk how to close this thread but it is ok to close if any mods want to do that