So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas on how to fix this?
Thanks in advance
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas on how to fix this?
Thanks in advance
Click to expand...
Click to collapse
You may need to try and flash oxygen OS recovery via adb and then format all your phone , flash oxygen OS and start again from scratch but that's just an educated guess , I'd wait for more responses first just in case someone knows a better method....
Xceeder said:
You may need to try and flash oxygen OS recovery via adb and then format all your phone , flash oxygen OS and start again from scratch but that's just an educated guess , I'd wait for more responses first just in case someone knows a better method....
Click to expand...
Click to collapse
I would say: Jump into fastboot with adb,
make sure you have an img of your old rom, and magisk both in a zip file on your phone
flash the recovery file
install rom
boot
reroot
Related
Hey guys, I went to root my Note 3 this morning and have run into some trouble. I used Odin to push TWRP, and TWRP to install my SU.zip. upon rebooting from TWRP the phone was acting a little strange, I downloaded Root checker but it was never able to verify root priveledges, it said the system was running slow. So I rebooted the phone. On boot up it now goes into Kernel Panic Upload mode with the following:
Kernel Panic!
KRAIT INFO
PC is at adreno_init+0x130/0x2d4
LRis at adreno_init+0x130/0x2d4
Panic caller : die+0x1d8/0x240
Panic Msg : Fatal exception
Thread : SurfaceFlinger:458
Speed_bin : 0x1
Wait...
Done!
Thankfully I can still get into recovery mode, however whether flashing a new rom or restoring my back up, I still am not able to boot because of the Panic Mode. I've tride installing 2 different ROMS and got this message last I tried:
Creating Symlink...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sd/Liquid-Kitkat-v3.0-NIGHTLY-hltetmo.zip'
Error flashing zip 'external_sd/
updating partition details...
Failed
I'm at work right now so I don't have access to Odin at the moment but was thinking I would try to push a stock back when I have a chance. Do you guys have any ideas?
macfable said:
Hey guys, I went to root my Note 3 this morning and have run into some trouble. I used Odin to push TWRP, and TWRP to install my SU.zip. upon rebooting from TWRP the phone was acting a little strange, I downloaded Root checker but it was never able to verify root priveledges, it said the system was running slow. So I rebooted the phone. On boot up it now goes into Kernel Panic Upload mode with the following:
Kernel Panic!
KRAIT INFO
PC is at adreno_init+0x130/0x2d4
LRis at adreno_init+0x130/0x2d4
Panic caller : die+0x1d8/0x240
Panic Msg : Fatal exception
Thread : SurfaceFlinger:458
Speed_bin : 0x1
Wait...
Done!
Thankfully I can still get into recovery mode, however whether flashing a new rom or restoring my back up, I still am not able to boot because of the Panic Mode. I've tride installing 2 different ROMS and got this message last I tried:
Creating Symlink...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sd/Liquid-Kitkat-v3.0-NIGHTLY-hltetmo.zip'
Error flashing zip 'external_sd/
updating partition details...
Failed
I'm at work right now so I don't have access to Odin at the moment but was thinking I would try to push a stock back when I have a chance. Do you guys have any ideas?
Click to expand...
Click to collapse
Well not that it matters that much but thought i'd post that going back to stock via odin worked in case any one else runs into this issue.
Hello Guys!
I was kinda hyped when I saw on Dec 31st that there's a new Softwareupdate available. Although I have a rooted device with a custom recovery (latest TWRP), previous OTAs always worked well. So I downloaded the OTA, and tapped "install" when it was finished. But this time it rebooted into recovery mode, and TWRP just did nothing. So, assuming it was because of the rooted device, I completely unrooted it and flashed the stock recovery and tried it again. This time there was actually smth. but an error saying "Update failed" appeared. Kinda pissed I downloaded the OTA update to my PC and tried to do it via adb sideload, same error "Installation failed" on the phone and cmd said
Code:
error: protocol fault (no status)
.
After that I copied the .zip to my phone, flashed TWRP again made a nandroid backup, wiped dalvik, chache & CO (no factory reset) and installed the zip. Again: Error. I don't remember the exact code, but it was smth. with "error reading zip" or so, but the file isn't damaged.
So I have the question: What am I doing wrong? Do I have to lock OEM again?
I am looking forward to your answers.
Sincerely, Firnien
PS: I updated adb to the latest version as well and tried, still not working
You should try this : https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Start with flashin twrp -28 then follow step by step.
Nobody07 said:
You should try this : https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Start with flashin twrp -28 then follow step by step.
Click to expand...
Click to collapse
Thanks, I'll try it
Hi,
I tried to unroot my oneplus 3 with
the guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock method from the oneplus forum
Everything works fine till the install from the sideload mode.
I get the error cannot read ota.zip (downloaded the newest oxigenos 4.0.2 file from the official Oneplus Site
I thought maybe the zip is corrupt, but i tried 3 other OTA from Oneplus with the same result.
im' currious in the zip the file system.patch.dat is size 0 and crc32 is also 00000000. Is this normal or should this be different?
I just checked whats happens when i unpack everything from the zip to my computer and then zip it again (i know this will not work but at least something happened), i got following message:
loading: ota.zip * daemon not running. starting it now on port 5037*
*daemen startet successfully *
Total xfer:0.00x
Any suggestions what may the problem could be?
Meitlibei said:
Hi,
I tried to unroot my oneplus 3 with
the guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock method from the oneplus forum
Everything works fine till the install from the sideload mode.
I get the error cannot read ota.zip (downloaded the newest oxigenos 4.0.2 file from the official Oneplus Site
I thought maybe the zip is corrupt, but i tried 3 other OTA from Oneplus with the same result.
im' currious in the zip the file system.patch.dat is size 0 and crc32 is also 00000000. Is this normal or should this be different?
I just checked whats happens when i unpack everything from the zip to my computer and then zip it again (i know this will not work but at least something happened), i got following message:
loading: ota.zip * daemon not running. starting it now on port 5037*
*daemen startet successfully *
Total xfer:0.00x
Any suggestions what may the problem could be?
Click to expand...
Click to collapse
I couldn't get nougat to sideload. I pushed it to internal storage, then used 'upgrade from internal'.
You need to wipe and reset system settings in stock recovery. Then all should work fine.
This is the problem with the adb drivers installed on the PC or MAC OS. I had the exact same problem. tried every adb software available on the net , but nothing worked. So I factory reseted Windows OS and installed adb drivers. Voila sideload started working as expected. The every same file which was giving error.
Please do not reset Windows. The issue is not with Windows, but your device. You need to have stock recovery installed. Reboot to recovery. Select English. Select Wipe Data and Cache, then choose Reset System Settings. Reboot to recovery again and side load. This has always worked for me. There is no need to reset Windows, just simply reset your internal storage/partitions to factory specs.
After installing TWRP and booting to my rom when I try to reboot to recovery again I get this message:
invalid boot image size
failed to validate recovery image
I'm using TWRP 64 bit
This thread is quite old (around 2 years old). But nevertheless, I am sharing my experience so that it may help someone facing similar problem. I have a Moto G 1st Gen Falcon which was running Lineage OS 14.1 based on Android 7.1.2. I was planning to update it to Android 10 based Unofficial Lineage OS. I downloaded latest TWRP zip to update existing TWRP. I rebooted into TWRP and flashed the zip. It installed perfectly. Then to check it attempted to reboot into recovery. But it instead went to fastboot mode with the error "Invalid boot image size! failed to validate recovery image Boot failed". I tried botting into recovery but was not working. I tried flashing through adb a different file but it was not working. Then what worked was booting into recovery using the command Fastboot boot recovery recovery.img. After that I was able to flash Android 10 and now everything is working perfectly.
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.