model: BND-L21(c432)
bootloader unlocked
FRP unlocked
My phone was running omnirom beta 5 for 2 months, was rooted with magisk (patched_boot flashed in ramdisk_recovery partition)
The bluetooth wasn't working so I wanted to install phhusson aosp 9
So I flashed emui 8 stock recovery then tried to flash phhusson aosp 9 as a system image in fastboot
Now, when the phone boot, it shut down instantly then boot into erecovery without the ability to factory reset or wipe cache (the only thing I can do is "reboot", "shutdown" and "download latest version and erecovery")
What's working and what's not:
access to erecovery (with ability to wipe cache and factory reset) when the phone is powered off then I press power & vol +
can't access twrp (even if the flash on recovery_ramdisk succeed with fastboot )
access to fastboot mode
access to erecovery (without the ability to wipe, only "download latest and erecovery) when the phone try to boot
access to dload installation
Here's my tries to fix the issue:
after installing emui 9 through fastboot: honor boot animation for 30-40s then bootloop
after installing emui 5 or 8 through fastboot: boot into error mode which displays this: (I can't flash ramdisk or boot (error: partition length get error))
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Click to expand...
Click to collapse
dload installation don't work, even with service rom
tried installing phhusson aosp 9 and omnirom beta 5: boot into rescue mode error
huawei multi tool failed
hwoat failed (I can't reboot into twrp)
erecovery "download latest version and erecovery" failed
My thoughts are that my BOOT is broken, but since I can't flash a new one, I don't know what to do.
AlexLebul said:
model: BND-L21(c432)
bootloader unlocked
FRP unlocked
My phone was running omnirom beta 5 for 2 months, was rooted with magisk (patched_boot flashed in ramdisk_recovery partition)
The bluetooth wasn't working so I wanted to install phhusson aosp 9
So I flashed emui 8 stock recovery then tried to flash phhusson aosp 9 as a system image in fastboot
Now, when the phone boot, it shut down instantly then boot into erecovery without the ability to factory reset or wipe cache (the only thing I can do is "reboot", "shutdown" and "download latest version and erecovery")
What's working and what's not:
access to erecovery (with ability to wipe cache and factory reset) when the phone is powered off then I press power & vol +
can't access twrp (even if the flash on recovery_ramdisk succeed with fastboot )
access to fastboot mode
access to erecovery (without the ability to wipe, only "download latest and erecovery) when the phone try to boot
access to dload installation
Here's my tries to fix the issue:
after installing emui 9 through fastboot: honor boot animation for 30-40s then bootloop
after installing emui 5 or 8 through fastboot: boot into error mode which displays this: (I can't flash ramdisk or boot (error: partition length get error))
dload installation don't work, even with service rom
tried installing phhusson aosp 9 and omnirom beta 5: boot into rescue mode error
huawei multi tool failed
hwoat failed (I can't reboot into twrp)
erecovery "download latest version and erecovery" failed
My thoughts are that my BOOT is broken, but since I can't flash a new one, I don't know what to do.
Click to expand...
Click to collapse
I had the same error "error: partition length get error" with my BND-L24. What I did, I found the stock rom from the firmware finder application. Unloaded the boot.img and flashed it without any issues.
I used the guide in the OpenKirin webpage to find the correct rom (you can check the info of your phone using fastboot commands or download multitool and read the phone info there) and to extract the .img files (go to Openkirin webpage and press support for the guides).
Good luck!
i, I have an issue with my phone and would need your help in recovering it back to life.
I have rebranded mate SE to Indian version few months back. so far so good. I have unlocked bootloader and started playing with it by downgrading etc.
the current situation is the phone is bricked with a android pie erecovery and no boot. tried using all the roms visiting various threads here with no luck (including service rom, multi-tool flashing etc)
multi-tool says Orio version 8.0.0.375. I am not able to flash any Oreo images since multitool says partition mismatch (boot, recovery etc) but when I flash 9.0.XX versions or Nougat versions, system is flashed successfully, yet, boot loops and back to latest erecovery.
don't have twrp (despite multitool flashing is successful) all I get is phone boots only to erecovery (latest)
unable to flash any stock recovery or kernels - as multitools says, partition mismatch.
I tried above method of boot.img flashing but multitool says partition error. tried various boot.img (EMUI 5 / 8 / 9) with no luck.
any help? suggestions?
I had a similar issue the last two days. The only thing that worked was rebooting to fastboot. I tried to get back to Oreo but used a method, that bricked my phone since it flashed an older kernel.img. I got it back running by detecting the version of the bootloader with Multitool and fastboot-flashing recovery, kernel and system that have been aligned with that version.
Be aware: You will have two recovery partitions:
- Huawei has renamed the partitions from "recovery"/"recovery2" to "recovery_ramdisk"/""erecovery_ramdisk"
- unlocking the bootloader does only let you flash recovery_ramdisk
- if you boot into recovery (Pwr & Vol+), the image from erecovery_ramdisk gets loaded
- To boot into recovery you are able to flash, it requires three buttons to be pressed (Pwr & Vol+ & Vol-)
- To flash erecovery_ramdisk, you have to flash TWRP into recovery_ramdisk and from there you can install an image into erecovery_ramdisk.
After having flashed back everything to 9.1.0.162, it was possible to format damaged /data and to setup the device via erecovery and WIFI.
Related
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.
Solved. Just install as described in https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
(before that I restored recovery, sys and boot from backup)
Still TWRP doesn't work... but who cares
Hi,
I tried to root my Moto Z2 Play but I somehow failed.
I can still boot into fastboot and boot twrp from there. but that's all that works.
I tried booting into recovery from twrp which was booted via
Code:
fastboot boot twrp.img
but this results in "no command".
Everything else just shows "your device has been unlocked and can't been trusted". Cannot turn off phone.
I followed this guide
https://devsjournal.com/how-to-root-moto-z2-play.html
but the downloads linked were down, so I tried to replace with more official looking downloads (see below)
I did these steps:
- unlock bootloader - I think this succeeded
- temporary boot twrp from fastboot
- wipe dalvik, data and cache
- backup everything except what I wiped
- other than the guide said, I did not install anything as I didn't have the files on the SD card
- I accidentally rebooted and the device started encrypting again
- I booted fastboot and flashed twrp-3.2.3-0-albus.img (by Junior Passos) into recovery
- I tried around with booting and finally was in TWRP again
- wiped again because of encryption (twrp said is was able to decrypt with standard password?)
- installed universal-dm-verity-forceencrypt https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
- installed Magisk 20.4 from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- after that booting did not work any more
- installed https://www.themefoxx.com/dm-verity-forced-encryption-disabler/ version 6.0 (guide mentioned version 5.1 from a different download) in the hopes this would solve the problem, but no.
Any idea how to recover? how to successfully root and TWRP?
Which partitions did the install-zips modify, so which backups should I restore?
thanks
Hi all,
I tried rooting my Oneplus 7T (Android 11) but it failed horribly. I started by unlocking my bootloader, then "fastboot boot twrp.img" and it worked. I was in TWRP when I tried flashing Magisk and TWRP, and somehow my OS is gone.
Now, whenever I reboot, it says "No OS installed" and boots back to TWRP. I tried to sideload a stock ROM but failed as well. I did adb push stock rom and tried to install it but it gave the same error. As of now I am clueless on what to do. I already wiped my system and formatted my phone (I already backup everything).
Error code when trying to sideload ROM (both stock and custom):
Failed to mount '/system_root' (permission denied)
Failed to mount '/vendor' (permission denied)
Devices on super may not mount until rebooting recovery.
To flash additional zips, please reboot recovery to switch to the updated slot.
As you can see, I am an idiot.
Please help.
Msmtool to unbrick
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
U must flash twrp and not boot twrp:
fastboot flash recovery twrp.img (rename img file to twrp.img and put in same adb folder)
HOLY COW IT WORKED, I managed to reinstall the OS.
Thank you very much HueyT, you certainly saved my day.
So...if I want to root my Oneplus 7T, I need to flash instead of boot TWRP?
Yes, op7t won't like boot TWRP as it has a dedicated recovery partition (both a and b slots-but when u don't specify TWRP goes into both slots)
twrp-3-5-1_11-hotdog-20210821-oos11-test.img | by lossyx for OnePlus 7T Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Is best TWRP for oos11 as allow data backup in twrp
im having a similar issue as OP... with device super message. I flashed the OOS firmware, then TWRP and then the custom rom whichever that may be.
However i have a feeling i am doing something wrong here. The only rom i can boot into is Syberia Android 12. However, after that i cant enter recovery again, and get stuck on the TWRP splash screen.
is there any reason why i cant boot into any custom android 11 roms?
Find Device storage Corupted. Your device is unsafe now. This messgae keeps popping now and then anyway to fix it. Using Stock MIUI 12 13.0.10. Device is Mi 11x (Aliothin).
tried recloking and full flash of firmware erasing everything still no hope.
Any fix
Hi,
Read my post,
CTS doesn't pass even with locked bootloader.
I have poco f3 and i installed a custom ROM on it but then i wanted to use MIUI but when i locked bootloader i got device memory corrupted issue which someone suggested me to fix by flashing persist img and i did that but another problem arise...
forum.xda-developers.com
I hope it helps.
Thanks @johnr64.
Followed these steps using OrangeFox Recovery. TWRP had persmission issues.
1. Boot to OrangeFox Recovery ( Command below only works if booted to OrangeFox Recovery, if you dont have recovery installed just use fastboot command : Fastboot boot ornagefoxrecovery.img)
2. Go to 3 dot menu at bottom and choose terminal
3. type: dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
4. After its finished reboot to the system, finished and fixed.
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.