Database Users

[Q] Stuck at boot animation after flashing 5.1

I was using 5.0.1, with stock bootloader, stock recovery, actually stock everything except SuperSU added.
I downloaded the 5.1 image from Google, and tried flashing it:
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.06.img
fastboot reboot-bootloader
fastboot update image-occam-lmy47o.zip
Got some missing sig errors, and "failed to allocate xxxxxxxxx bytes" error. Thus after searching for more information I ended up unpacking image-occam-lmy47o.zip and running:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
Then rebooted. The result is an endless boot animation, regardless of anything I try. Tried restoring my TWRP backup, reflashing 5.1, reflashing 5.0.1, always the same. Last logcat line at boot:
E/kickstart( 233): Sahara protocol completed
Then it's just stuck there. For minutes. For tens of minutes. Looks like forever. Anyone else ever seen this problem, and happens to have a solution? (Preferably without losing my data)
Edit: After a few hours I restored the original (or so I hope) state, by wiping, then flashing 5.0.1, then restoring my backup. But now I don't dare to try flashing 5.1 again. Still would love to hear ideas from who might have seen this problem and knows a solution.

After you've flashed the factory image boot into the stock recovery and do a factory reset.
Sent from my Nexus 9 using XDA Free mobile app

IVBela said:
I was using 5.0.1, with stock bootloader, stock recovery, actually stock everything except SuperSU added.
I downloaded the 5.1 image from Google, and tried flashing it:
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.06.img
fastboot reboot-bootloader
fastboot update image-occam-lmy47o.zip
Got some missing sig errors, and "failed to allocate xxxxxxxxx bytes" error. Thus after searching for more information I ended up unpacking image-occam-lmy47o.zip and running:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
Then rebooted. The result is an endless boot animation, regardless of anything I try. Tried restoring my TWRP backup, reflashing 5.1, reflashing 5.0.1, always the same. Last logcat line at boot:
E/kickstart( 233): Sahara protocol completed
Then it's just stuck there. For minutes. For tens of minutes. Looks like forever. Anyone else ever seen this problem, and happens to have a solution? (Preferably without losing my data)
Edit: After a few hours I restored the original (or so I hope) state, by wiping, then flashing 5.0.1, then restoring my backup. But now I don't dare to try flashing 5.1 again. Still would love to hear ideas from who might have seen this problem and knows a solution.
Click to expand...
Click to collapse
You only really need to flash the following (unless there is a new bootloader and radio):
fastboot flash boot boot.img
fastboot flash recovery recovery.img (if you are running custom recovery you can skip flashing this)
fastboot flash system system.img

metpage said:
You only really need to flash the following (unless there is a new bootloader and radio):
fastboot flash boot boot.img
fastboot flash recovery recovery.img (if you are running custom recovery you can skip flashing this)
fastboot flash system system.img
Click to expand...
Click to collapse
There was a new radio, but that worked (I accidentally booted normally after flashing it). The rest is the same that I did, except the cache, guess next time I'll try doing it without flashing that one. Do I not have to wipe the cache partition either? (And no custom recovery here, I boot TWRP from my PC via fastboot.)
Edit: Who understands this.... I tried it again tonight, flashed radio, then fastboot update image-occam-lmy47o.zip worked, no error this time, no unpacking, nothing. Just a successful update this time.
Guess that wipe was needed, maybe something was already corrupted before I tried flashing the first time.
Case closed.

MX4 bootloop brick after trying to update I firmware on A phone

SOLVED:
Hi,
I just bricked my MX4 after trying to update system image from 4.5.6 to 4.5.7 using this guide:
Extract I version update.zip
use sdat2img to create system image
dd system image to system partition on live phone and reboot.
I used the same procedure successfully before, x-updating 4.5.4A ti I then updating to 4.5.6I.
After updating to 4.5.7, the phone goes into an infinite loop of Meizu splash screen, Flyme balloon, reboot.
I can enter fastboot and official recovery, but can't flash any partition from fastboot.
The bootloader is still locked.
Does anyone have any advice for unbricking?
Update:
The bootloop suddenly froze up for long enough for me to use adb to push an update.zip to the "sdcard" root. Have now flashed 4.2.8A from recovery and booted the phone.
As I had to clear all data I will unlock bootloader before trying anything else.

Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me

bobslesbricoleurs said:
Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me
Click to expand...
Click to collapse
Hi,
I managed to push 4.2.8.2 to sdcard then do a normal recovery reflash.
Have now successfully unlocked using the .apk method.
Now I need to find out if I can use that unlocked bootloader to flash recent "I" firmwares, or if I can only flash the unfinished cyanogen (would like to wait 'til that's a bit more polished before using it.
Anyway. Happy to have my phone back!

Maybe that newest 4.5.7I need a new kernel so you'll need to update to 4.5.7A before flashing system.img or you can flash directly 4.5.7I but you'll need to use fastboot flash boot boot.img
If a rom/firmware needs a specific kernel it'll bootloop if you don't flash it

Can I flash 4.5.7 I now that I have unlocked bootloader and custom recovery? If I understand the unlock threads correctly, I think I will relock the bootloader, or even brick if I try to flash the complete update.zip. Can I flash system and boot partitions using fastboot?

Fully BRICKED.
Now I FULLY bricked it (no more recovery).
Had successfully upgraded to 4.5.7 "I" and was installing super su for full root, before disabling update, but had forgotten that I still had official 4.2.8 rom as update.zip on "sdcard" root.
rebooted to TWRP recovery for full su install and recovery found the update.zip and flashed it.
Result: Bootloop, No recovery, locked fastboot, no possibility to flash anything.
Aaargh!

Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)

Fixed with large hammer! Goodbye Meizu!
Learnincurve said:
Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)
Click to expand...
Click to collapse
Fixed with large hammer! Goodbye Meizu!

fastboot boot recovery.img isn't a command at all... It's fastboot flash recovery C:/path/to/recovery.img

Bricked Nexus 4, send help. Flashed wrong version of twrp.

I used the WonderHowTo site incorrectly to flash a nexus 5 version of twrp unto my nexus 4.
My device at this point booted to a blank screen. It could still boot the boot loader at this point.
To "fix" this I found the correct version of twrp for my device and proceeded to flash that unto my device.
This has appeared to work since I can access twrp on my device but it is only thing I can access on the phone. When I attempt to boot to system through twrp I am sent back into twrp.
I have attempted to use the wugfresh root tool kit to unroot and return to stock using both soft bricked and phone is still working normally options with no success.
It can still boot to the boot loader currently.
I have logs from the toolkit if these can shed more light on my issue.
Is there anyway I can return my device to stock? Thanks for any response

Flash factory image
https://developers.google.com/android/nexus/images#occam

attempted
attempted to flash stock and got the following error message
error: neither -p product specified nor ANDROID_PRODUCT_OUT set

Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.

codebam said:
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
Click to expand...
Click to collapse
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.

MrTalk said:
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
Click to expand...
Click to collapse
Okay adb push a cyanogenmod zip from here and flash it in recovery. It should automatically install a working boot image. You should also flash the latest bootloader in the factory image with "fastboot flash bootloader bootloader.img" if you're using an outdated bootloader.

used the advice
I pushed the zip file using cmd and it appears to have been successful since I was given the summary of data transferred and how long it took once the process was finished.
I can't find the zip file in twrp to attempt to flash it.. Is there any reason the file name would change inside the device once it has been pushed?
Is there a way to flash the zip in question without pushing it unto the device?

[HELP] Recovery Bricked and can't reflash

Hello,
I've decided to install the Beta version of Oxygenos 3.0. Since my phone came from the OnePlus support, I've unlocked the oem, installed TWRP and flashed the Oxygen zip.
However, a day later I've spotted important touchscreen issues (I can't use the touchscreen sometimes).
To see if it is a software problem, I've decided to go to the recovery to reflash a backup. When I try to go to recovery mode, nothing Happen! (Just the oneplus logo ).
So, i've decided to reinstall TWRP by flashing it with fastboot.
"fastboot flash recovery recovery.img" -> OK
"fastboot boot recovery.img"
downloading 'boot.img' ...
OKAY [0.702s]
booting...
FAILED (remote: dtb not found)
Click to expand...
Click to collapse
I've tried to install the stock recovery but I've the same error.
PLEEEASE HELP. I've waited a week to receive my phone because it had a problem but it's broke again :crying:
Note: I can go in Android normally (but with the touchscreen problem)

http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.

This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.

AndroidBeginNinja said:
http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 try this.
Click to expand...
Click to collapse
Thank you,
I've done this and I had a working recovery, (bootloop if I try to boot up normaly but it's not a problem I just have to flash a rom)
Trey22200 said:
This happened to me too except I would not boot into the OS or recovery. I ended up going into fast boot and formatting the System, recovery and data partitions. Here is what I typed.
fastboot format system
fastboot format recovery
fastboot format data
I am not sure if you have to format the data but I did.
After that I flashed TWRP
fastboot flash recovery recovery.img
Then I booted into recovery and was able to restore.
Click to expand...
Click to collapse
I've tested your manipulation and it worked well too.
For those having the same problem OR want to install Oxygen OS the CLEAN WAY, read this post before: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
It is very important to read the faq before flashing and doing **** like me.

http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713 flash this first before you flash oos3

HELP! Stuck in fastboot!! (bricked?)

Dear everyone,
I am stuck in fastboot. I installed the greek TWRP, and cleaned my data by typing ''yes''.
I connected my phone to my PC to put a ROM zip on it, but it only glitched out (it showed multiple storages in Windows)
I restarted my phone, and it won't boot in recovery. When I try to boot to recovery via adb, it just shows
PS C:\adb> fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.616s]
booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
I am really scared now that my phone is hard bricked. Not sure why though.
Flashing a fastboot ROM wont work either, it just says flash done instantly.
I have done this so many times on my other Xiaomi phones I had without any problems.
And also, is it possible to turn the phone off for now? Because I dont want to have the fastboot screen burned in.
Regards

Jordytjes said:
Dear everyone,
I am stuck in fastboot. I installed the greek TWRP, and cleaned my data by typing ''yes''.
I connected my phone to my PC to put a ROM zip on it, but it only glitched out (it showed multiple storages in Windows)
I restarted my phone, and it won't boot in recovery. When I try to boot to recovery via adb, it just shows
PS C:\adb> fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.616s]
booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
I am really scared now that my phone is hard bricked. Not sure why though.
Flashing a fastboot ROM wont work either, it just says flash done instantly.
I have done this so many times on my other Xiaomi phones I had without any problems.
And also, is it possible to turn the phone off for now? Because I dont want to have the fastboot screen burned in.
Regards
Click to expand...
Click to collapse
Did you try flashing the fixed russian twrp? When I flashed the greek twrp on my phone and rebooted through adb it didn't reboot so I rebooted manually and it rebooted into stock recovery. I rebooted into fastbood and flashed the fixed twrp and it worked. If you can get into fastbood you have a chance of reflashing twrp or flashing stock rom so I don't think its bricked yet

Aserar said:
Did you try flashing the fixed russian twrp? When I flashed the greek twrp on my phone and rebooted through adb it didn't reboot so I rebooted manually and it rebooted into stock recovery. I rebooted into fastbood and flashed the fixed twrp and it worked. If you can get into fastbood you have a chance of reflashing twrp or flashing stock rom so I don't think its bricked yet
Click to expand...
Click to collapse
You are my hero! Thank you so much!

this is soft brick, try to flash another twrp as the above user mentioned.