Basically I was an ***** and flashed a oneplus3t rom onto a oneplus3, I thought it was a oneplus3t as I have 2 and used the wrong one (DumbDumb).
I have downloaded the MSM tool and got it to boot now, however upon boot it is looping with several things failing.
Boot failed (Red text)
Boot_aging failed (Red text)
Cache Failed (Red text)
System Failed (Red text)
Recovery Failed (Red text)
MD5 Checksum Failed. (Red text)
I am able to get it into fast boot but that's it, no recovery, just fast boot or bootloop with errors shown above.
I have managed to fix the Cache fail by flashing the .img in adb cmd
Tried to flash all the others but not having any luck.
I had 8.1 nitrogen which is oreo based rom installed.
Anyone have any suggestions, I've been trying to fix it all day yesterday but no joy.
Hope someone can help.
I'm recieving the following error upon boot.
boot Failed
boot _aging Failed
recovery Failed
md5 checksum Failed
System said failed and Cache, I have flashed them in ADB alongside all the other ones, but they are still showing as failed.
Any help? I had nitrogen 8.1 installed, if I can find the .img files maybe I can flash them but I dont know, I tried flashing the files from all in one tool, only cache and recovery are fixed, the rest are still red.
Related
First of, I'm running Cyanogenmod 12.1 on my Z2.
On the install it vanished my TWRP Recovery, so I decided to reflash it using their app - this was unsucessfull. I thought I would flash it the next day using adb, so I didn't mind.
However in the next hours I needed to reboot the phone - resulting in the Sony logo and nothing more. So I bootet into the CM recovery and tried to reflash the CyanDelta zip - this failed and resulted in "footer is wrong - signature verification failed - Installation aborted". The next thing I tried was flashing a zip by adb recovery sideload - this failed as well and resulted in "protocol fault (no status)".
This was when I tried to boot into the bootloader using the recovery menu entry. The screen got black, the LED lighted up blue and nothing happened forever. The same thing occours when I try to boot into the bootloader by hardware keys (hold VolUp and insert MicroUSB cable).
So, in short:
I can't boot android
I can't install zips by CM recovery
I can't boot into the bootloader [EDIT: I can.]
I can't install nandroid backups since the CM recovery doesn't offer that
Any idea?
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
the_crevis said:
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
Click to expand...
Click to collapse
Ah, I feel dumb now. I might be damaged from the informational Nexus bootloader.
So, I tried to flash a new recovery - fastboot flash twrp-2.8.6.0-sirius.img - which succeded, but it still boots the CM Recovery. Buh.
Seems like something is overriding the recovery on boot. So lets erase everything:
Code:
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot flash twrp-2.8.6.0-sirius.img
Aaaand - still CM Recovery.
I also tried to flash a stock image as you suggested, however:
Code:
fastboot flash system system.sin
sending 'system' (1800183 KB)...
FAILED (remote: data too large)
finished. total time: 0.002s
No worries, I came from a nexus 4 and it confused me as well at first. Try exacting http://forum.xda-developers.com/xperia-z2/development/kernel-m5-kernel-t2858912 and flashing the boot image via fastboot. That should give you a working recovery.
As I said, flashing a recovery by fastboot results in the CM Recovery.
I just tried to wipe my device using the CM Recovery, it told me it was unable to mount /data - my guess? The filesystem is ****ed up.
EDIT: I got it. Seems like TWRP needs some custom stuff to work (which is provided by CM). Flashing philz worked fine and allowed me to sideload a proper ROM. Everything fine now
I tried to update my device with the newest ROM (Dirty Unicorns) and somehow bricked it. ...
The device just stuck in the flashing process for over 10 hours. After TWRP and Fastboot were still working, I tried a lot of things to revive the system, but everything I tried went wrong.
First I tried to flash the factory image. The strange thing: that seamed to work well (with Wugfresh toolkit), but the device still stuck in a bootloop.
Everything I try in the recovery mode ends by TWRP with "E: Unable to mount '/system'" (in red letters). So I tried to flash the factory image again and wiped the device in the newly flashed Revovery completely.
No change: "Updating partition details... E: Unable to mount '/system'".
- ABD sideload doesn't work. I tried to flash system.img. No success.
- Bootloader is unlocked. V3.44.1.0123
- Newest TWRP (twrp-2.8.7.0-flounder.img)
Here are the best Android-experts worldwide! So can someone please help me?
Thanks in advance!!
Regards,
Frank
Gleichzwei said:
I tried to update my device with the newest ROM (Dirty Unicorns) and somehow bricked it. ...
The device just stuck in the flashing process for over 10 hours. After TWRP and Fastboot were still working, I tried a lot of things to revive the system, but everything I tried went wrong.
First I tried to flash the factory image. The strange thing: that seamed to work well (with Wugfresh toolkit), but the device still stuck in a bootloop.
Everything I try in the recovery mode ends by TWRP with "E: Unable to mount '/system'" (in red letters). So I tried to flash the factory image again and wiped the device in the newly flashed Revovery completely.
No change: "Updating partition details... E: Unable to mount '/system'".
- ABD sideload doesn't work. I tried to flash system.img. No success.
- Bootloader is unlocked. V3.44.1.0123
- Newest TWRP (twrp-2.8.7.0-flounder.img)
Here are the best Android-experts worldwide! So can someone please help me?
Thanks in advance!!
Regards,
Frank
Click to expand...
Click to collapse
Boot to bootloader, and enter the following commands:
fastboot format cache
fastboot format userdata (NOTE THAT THIS WILL WIPE THE CONTENTS OF YOUR SDCARD)
fastboot reboot
has anyone ever got FAILED (remote: image update error) after writing the image..... it wont seem to flash my stock image? It erased everything just fine then it flashes bootloader fine then all the rest it just says that failed part after writing each img... then when it reboot it jump back to my bootloader as if not flashing a thing
just reset my whole windows 10, reinstalled adb and wugfresh (didnt help)
Just tried to flash wugresh recovery twrp 3.0.2 and when it reboots devices it goes right back to fastboot mode
nm my vmware was f'd up i had to do it on mac
djranoia said:
has anyone ever got FAILED (remote: image update error) after writing the image..... it wont seem to flash my stock image? It erased everything just fine then it flashes bootloader fine then all the rest it just says that failed part after writing each img... then when it reboot it jump back to my bootloader as if not flashing a thing
just reset my whole windows 10, reinstalled adb and wugfresh (didnt help)
Just tried to flash wugresh recovery twrp 3.0.2 and when it reboots devices it goes right back to fastboot mode
nm my vmware was f'd up i had to do it on mac
Click to expand...
Click to collapse
You don't use ADB to flash factory images. You use fastboot. Boot to bootloader, then fastboot flash [partition name] [file name]
cam30era said:
You don't use ADB to flash factory images. You use fastboot. Boot to bootloader, then fastboot flash [partition name] [file name]
Click to expand...
Click to collapse
Thanks I kept digging in the Internet and found that out then I flashed . /fastboot flash on my mac my windows virtual box was messed up after a restore to my mac and downloading a restore over timecapsule
As a general FYI, the System Image needs to be in the root directory of your adb/fastboot.
I could flash everything else in the Factory image from CD ../desktop, except the System Image portion. Kept getting errors on that one file.
Hi guys, I really need your help!
I have a Vernee Apollo Lite and it's stuck in bootloop......
Can't enter in recovery mode (Tried flashing TWRP multiple times via fastboot with a Mac)
I'm also stuck with no OS, originally I got TWRP working and wanted to flash a custom rom (MadOS Oreo 8.1 AOSP)
but I messed up and wiped everything (the partitions).
Tried to flash it anyways but gave me Error 7 so I tried other roms but other problems occured and failed each time, I tried flashing another recovery.img file (TWRP) in recovery mode and rebooted but then it didn't load anymore so all I have right now is fastboot working.
Tried flashing a stock rom via fastboot but kept giving me "remote: partition table doesn't exist"
I wonder if I could use the flash-all command with the stock images but some are missing in the the stock rom file but probably it will still give me the same error (partition table doesn't exist)... oh and I also tried flashing custom roms with fastboot but no success.
VERY IMPORTANT TO KNOW THAT I ONLY HAVE A MAC By the way I checked each files and compatibility isn't the problem.
Thanks in advanced:good::good::good::good:
Hello,
After installing a xiaomi.eu rom via twrp, I cleared the cache, rebooted the system and then the screen went black and it is stuck in there. Any suggestions on how to resolve this issue? Thanks.
EDIT: Using fastboot, I was trying to reinstall twrp but i got the following message: FAILED (remote: Failed to load/authenticate boot image: 00000050)