Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh
I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.
Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.
Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards
I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.
Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps
mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.
Now the phone is unable to boot to system, I have no idea what I could do to fix it as there is no way to use adb or fastboot command…
I remember that the stock rom version is S11a, it have some problems when I tried to root it, and failed to flash recovery even I've got the root permission (response "write error: no space left")
------↑solved by using LG flashtool↑------
Now I am facing the problem that unable to install TWRP recovery using dd, it responds “ write error: No space left on device” I’ve reinstall the LG drivers, reboot the phone, reboot the computer, unroot and root again, but the problem still occurs.
----- update ------
solved by using flashify, and TWRP version 3.3.1 instead of latest 3.6.1, so that it won’t have “secure boot error” warning, and boot to recovery successfully.
But there is a new problem now, when I tried to sideload MindTheGapps after installed LOS 18.1 successfully, it warns me “could not mount /mnt/system! Aborting”. This is the third phone that having this warning for me, and I still couldn’t figure out which step goes wrong.
Nothing goes wrong after flashed to lineage recovery, installed MindTheGapps now.
--update--
I also tried to flash lineage recovery from TWRP on my D855, it also works, I installed MindTheGapps and everything works fine. So this is the problem of TWRP? Or reinstall the recovery is the solution? Maybe I would have a test later.
Hello,
I have a strange problem with Galaxy A5 2017 after installing twrp + lineage 18.1. I will explain the problem in sub points.
1) in January on stock software I installed (according to instructions from XDA forum) root, twrp (via ODIN) and bypass with memory decryption. Then I installed Lineage 18.1, Gapps, Magisk and debloater on it to remove unnecessary apps.
2) The phone worked fine until mid-April. Some update was installed and the phone died.
3) The phone wouldn't boot up after the update and only the TWRP logo was looping (logo kept flashing).
4) the phone couldn't boot up, but after I found the only way to get the system to boot up was to enter command "adb reboot bootloader" from windows console. The system booted, but after another reboot unfortunately it was the same thing - the TWRP logo was looping.
5) I managed to upload Lineage Recovery via ODIN, but unfortunately this didn't change anything. Phone was booting to recovery only (but it was working). I tried to update via ADB Sideload from recovery - also without success. Interestingly, the only way to fix it was to fully format with the system partition from recovery and re-upload the system. This worked, and Lineage booted into the android interface, but on the next reboot I unfortunately only had the Lineage loading logo visible for 10-15 minutes - then a reboot into recovery. I had to repeat the formatting and re-upload the system.
6) Interestingly, when I used the combination - lineage recovery, full format, twrp 3.6.1 (via ODIN) - TWRP booted normally and I could install LineageOS. The system would only boot once, and after the next reboot the TWRP logo would loop again.
7) The last problem I noticed is that if I load Lineage system, gaaps package and magiska via TWRP or Lineage Recovery, the system will never boot - either it will loop the logo (if using Lineage Recovery) or the phone will not load the system, it will reset and loop the TWRP logo indefinitely (if using TWRP recovery).
Does anyone know a solution how to restore the phone? Will it still work or for example NAND memory is dead and nothing can be done? Best regards
Hi!
I was about to end this tutorial to root my MI 9 se (https://forum.xda-developers.com/t/...er-flashing-recovery-rooting-process.4286597/) and when I restart after install Magisk, I get a boot loop. Since then I tried this so far:
-Run uninstall.zip (from magisk apk). Resulting on "Updater process ended with error: 1"
-Install a previous versions (23 and 25). After install each version, I rebooted without success. Trying the uninstall.zip of each version result in the same previous error.
-Flash a boot.img. Doesn't seems to work
-Try the Magisk Manager tool. Running mm says that No magisk is installed, althought installing any verision of Magisk doesnt seems to fail (just the uninstall.zip part)
Since the begginning i had to figure some things by myself because adb not recognizes the device. Fastboot in other hand works perfectly (My computer only detects the device when on fastboot, no the other way. Seems to be something related to encryption by Xiaomi)
Some thoughts?
Thanks!
UPDATE: I had to go back to Stock MIUI through MiFlash Utility. After that, y tried another method with Lineage OS UNOFFICIAL, from this same forum, but I reached the same point, with a TWRP recovery bootLoop. I tried version 3.6 and 3.7 of TWRP and the result was the same.
UPDATE 2: Tried SHRP Recovery, but once flashed, pressing volume up + power button wont boot into recovery, just fastboot again (same behaviour as volume down + power). Its so strange but, well, another one more to the bag of problems.. In this try, I was able to boot again normally if just power on the device normally.