I rooted my op7t and i am on official oxygen os 10 with latest twrp 3.7.0 and magisk installed. It is having this error i don't know why. Someone kindly explain and help.
I flashed twrp using fastboot flash recovery recovery.img and tried flashing in both boot as well using :
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
Related
Hi guys
My Find7 using LVM and Paranoid ROM had rebooting issues (long time issues). I tried to 'fix file system' and it threw an 'encryption failed ' screen on ROM boot. That happened a few tims so I went into TWRP and attempted NANDROID restore.
That failed with error 225. I cannot after removing LVM install ColorOS 1.2.1i or 1.2.7.i . TWRP says it cannot mount '/data'. ColorOS stock recovery fails too.
Now I can't reflash through Fastboot TWRP
I think I recall fixing this by flashing Clockwork but I can't find a version for the Find 7.
Any help?
Thanks so much!
okay as soon as I published, I had moved through mass mounting coloros 1.2.7i using coloros stock recovery
I flashed and it worked.
Hours of failure prior to this.
Thanks, myself.
For anyone who can't flash recovery and is stuck do this
install fastboot. Google it.
download colorOS 1.2.7i and extract the zip to say the folder FIX
download this oppo find7 stock recovery to FIX http://s000.tinyupload.com/index.php?file_id=00219433653419942379 or use TWRP in its place (change the recovery.img name to whatever your twrp file is called.)
hold shift + right click (windows) in FIX and click open command prompt here
copy each line below and right click and paste line by line
Fastboot oem unlock
flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash LOGO logo.bin
fastboot flash reserve4 reserve4.img
I did the follwoing:
fastboot -i 0x2970 erase recovery
fastboot -i 0x2970 flash recovery /Users/xxxx/Desktop/androidtools1/cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NN-crackling-recovery.img
fastboot reboot
all went well- terminal reported ok
then reboot into recovery mode to install the cm13.zip file - failed!
device does not boot into recovery. I get black screen and dead device.
device comes back to life after battery is out and in again.
so no recovery mode menu.
any ideas what to do next?
wisdomlight said:
I did the follwoing:
fastboot -i 0x2970 erase recovery
fastboot -i 0x2970 flash recovery /Users/xxxx/Desktop/androidtools1/cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NN-crackling-recovery.img
fastboot reboot
all went well- terminal reported ok
then reboot into recovery mode to install the cm13.zip file - failed!
device does not boot into recovery. I get black screen and dead device.
device comes back to life after battery is out and in again.
so no recovery mode menu.
any ideas what to do next?
Click to expand...
Click to collapse
normally I just do
Code:
fastboot flash recovery <recovery-image-file>
Also how do you attempt to boot recovery?
- VolDn+Pwr ?
- adb reboot recovery ?
What if you flash stock recovery or twrp?
do you actually write <recovery-image-file> ??
I thought the actual .img file needs flashing. ??
either way - VolDn+Pwr and adb. = black screen dead device.
I thought cm-13.img is stock recovery. I downloaded it from cyanogen
twrp needs rooted device. I am trying to instal the OTA update from 12.1 to 13.0 and it doesn't work. and i was advised to un-root my device.
so now i have a un-rooted device but with no recovery.
arrrghhh
wisdomlight said:
do you actually write <recovery-image-file> ??
I thought the actual .img file needs flashing. ??
either way - VolDn+Pwr and adb. = black screen dead device.
I thought cm-13.img is stock recovery. I downloaded it from cyanogen
twrp needs rooted device. I am trying to instal the OTA update from 12.1 to 13.0 and it doesn't work. and i was advised to un-root my device.
so now i have a un-rooted device but with no recovery.
arrrghhh
Click to expand...
Click to collapse
if you unpack cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip from cyngn.com you may try to flash stock COS 13.0 as follows:
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
recovery partitions are different in Android O that means from fastboot
fastboot flash recovery <filename>.img changed to fastboot flash recovery_ramdisk <filename>.img (i had installed twrp with help of this code in my honor 7x)
i want to know is there any change for boot image partition.
fastboot flash boot boot.img not working in my case.
device: honor x BND-AL10
stock boot image from Update.APP (OREO built)
help me on this! i need to flash boot.img into my device
babu.123 said:
recovery partitions are different in Android O that means from fastboot
fastboot flash recovery <filename>.img changed to fastboot flash recovery_ramdisk <filename>.img (i had installed twrp with help of this code in my honor 7x)
i want to know is there any change for boot image partition.
fastboot flash boot boot.img not working in my case.
device: honor x BND-AL10
stock boot image from Update.APP (OREO built)
help me on this! i need to flash boot.img into my device
Click to expand...
Click to collapse
It changed to ramdisk so fastboot flash ramdisk that's the new boot
I followed this thread to install lineage OS on my MI A2 lite:
https://www.getdroidtips.com/lineage-os-16-xiaomi-mi-a2-lite/
IIRC, on this phone there is no recovery partition:
fastboot flash recovery twrp.img gives the error Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
I flashed TWRP to boot (fastboot flash boot twrp.img) instead of only starting it (fastboot boot twrp.img)
then I followed the procedure thinking that I was on the recovery partition and tried to install lineage os in boot (where twrp was)
now I can only enter the fastboot mode
fastboot boot twrp.img gives a black screen with device unable to boot error - mdtp image is corrupted
fastboot flash boot twrp.img gives the error Writing 'boot' FAILED (remote: 'partition table doesn't exist')
fastboot getvar current-slot gives current-slot: INVALID
the problem seems to be similar to this one:
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
though mdtp_a and mdtp_b are there but they are not active and I am not sure what image I should flash there.
How should I proceed?
baudoux said:
I followed this thread to install lineage OS on my MI A2 lite:
https://www.getdroidtips.com/lineage-os-16-xiaomi-mi-a2-lite/
IIRC, on this phone there is no recovery partition:
fastboot flash recovery twrp.img gives the error Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
I flashed TWRP to boot (fastboot flash boot twrp.img) instead of only starting it (fastboot boot twrp.img)
then I followed the procedure thinking that I was on the recovery partition and tried to install lineage os in boot (where twrp was)
now I can only enter the fastboot mode
fastboot boot twrp.img gives a black screen with device unable to boot error - mdtp image is corrupted
fastboot flash boot twrp.img gives the error Writing 'boot' FAILED (remote: 'partition table doesn't exist')
fastboot getvar current-slot gives current-slot: INVALID
the problem seems to be similar to this one:
https://forum.xda-developers.com/mi-a2-lite/help/device-unable-to-boot-error-mdtp-image-t3926962
though mdtp_a and mdtp_b are there but they are not active and I am not sure what image I should flash there.
How should I proceed?
Click to expand...
Click to collapse
How did you think to flash LineageOs in boot where TWRP used to be?
Anyway if you didn´t complete this disastrous attempt you could solve it restoring mdtp partition that is a kind of gpt for other devices.
Flash it in both slot using fastboot. Then you´ll can know which partition is active, if the system yet still alive you´ll can boot on it or boot temporarily to TWRP to do your stuff but if not then you´ll need to restore one or more partitions flashing again the whole stock rom through MiFlash tool.
SubwayChamp said:
How did you think to flash LineageOs in boot where TWRP used to be?
Click to expand...
Click to collapse
this was a typo, and I got lost in the process
SubwayChamp said:
Flash it in both slots using fastboot.
Click to expand...
Click to collapse
you mean flash LINEAGE OS playload.bin or TWRP.img in mdtp_a and mdtp_b?
baudoux said:
this was a typo, and I got lost in the process
you mean flash LINEAGE OS playload.bin or TWRP.img in mdtp_a and mdtp_b?
Click to expand...
Click to collapse
Sorry for delay, yes, in both partitionn you have to flash mdtp, is to restore the table partition.
And about LOS I think you need to read a bit more or you'll have a thermonuclear reaction some day (just kidding) Custom roms come in form of zip and contain scripts that are prepared for developers to can unpack and flash files in the right place so don't worry about it.
First restore your partitions and the next is a ready-to-go.
SubwayChamp said:
yes, in both partitionn you have to flash mdtp, is to restore the table partition.
First restore your partitions and the next is a ready-to-go.
Click to expand...
Click to collapse
I guess you mean fastboot flash mdtp_a mdtp.img and fastboot flash mdtp_b mdtp.img
I cannot find the mdtp.img file
baudoux said:
I guess you mean fastboot flash mdtp_a mdtp.img and fastboot flash mdtp_b mdtp.img
I cannot find the mdtp.img file
Click to expand...
Click to collapse
You´ll find it inside the stock rom.
SOLVED
flashing mtdp_a and mtdp_b did not help, I hat to flash the stock rom again and start the process from scratch
other problems showed up:
I had to downgrade twrp to 3.3.0 to avoid error 7 while flashing LINEAGE OS
and then upgrade it again to 3.3.1 fo avoid error 64 while flashing GAPPS
Hi
I wanted to install pixelexperience (plus) on my xz2c dual sim.
i flashed the oem as stated there
fastboot flash oem_a SW_binaries_for_Xperia_Android_(blahblah) fastboot flash oem_b SW_binaries_for_Xperia_Android_(blahblah)
and fastboot flash oem_b SW_binaries_for_Xperia_Android_(blahblah) fastboot flash oem_b SW_binaries_for_Xperia_Android_(blahblah)
it did not boot, so tried some things with recovery but recovery now is gone and fastboot boot recovery.img won t boot and fastboot flash recovery i get the message partition not found
reflashed several times with flashtool to 52.1.A.3.49 no luck with recovery partition.
I have never seen this error on my xperia-s, what am i missing
anyone know how to get back twrp so i can at least root with magisk again?