Database Info

Bootloop! Unable to flash stock rom or lock bootloader (Help)

Hi. I can't get passed the google splash screen on a Nexus 5 D821 and could use some help.
Here are the facts:
* The owner of the device told me it bricked after an update.
* The Bootloader is unlocked. When i tried to lock i got the following message:
Code:
fastboot oem lock
...
OKAY [ 0.041s]
finished. total time: 0.041s
But it wasnt persistent. When given reboot comand the phone switched OFF instead. I turned it on to bootloader again and it was still unlocked.
* I tried flashing stock rom LRX22c manually after a failed attempt with the flash-all script. I got the following error for bootloader, radio, boot and recovery:
Code:
FAILED (remote: flash write failure)
* I tried erasing cache and flashing userdata but the after over 60 minutes waiting i came to the conclusion that i wasnt going anywhere and just rebooted the phone.
*The only thing im actually able to flash without an error message is system.img:
Code:
fastboot flash system ~/Downloads/hammerhead-lrx22c/image-hammerhead-lrx22c/system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.127s]
sending 'system' (981472 KB)...
OKAY [ 30.934s]
writing 'system'...
OKAY [ 62.705s]
finished. total time: 93.767s
* I tried booting TWRP, but i was unable to mount the file system (perhaps because i wasnt able to flash it. i used "fastboot boot twrp.img").
Are phones technically able to get to splash screen or bootloader with a damaged NAND or EEMC chip? Im starting to consider the possibility of a hardbrick. Why would i be able to write system.img if that was the case though? Any help is welcome
===============================================
alright so im pretty sure its a hard brick. The emmc is dead. its a shame :/ guess ill just try to sell it for parts. I would delete this thread because its pretty useless, but i have created my account a few days ago, and i ddont know how to.

You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk

Ben36 said:
You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried all of the imgs in their respective order. they all failed. i got the error
Code:
FAILED (remote: flash write failure)
. system.img was the only .img i was able to write, and i was wondering why. Also, when i try fastboot reboot the phone switches off. It doesnt reboot.

Nexus 5 and Android 6.0 Fastboot Issue

Hi all
I finally received my Nexus 5 back from LG, which said that they replaced the battery and other parts to address my issue (the original thread can be found at the link below).
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-various-issues-t3212261
This being said, I now want to flash Android 6.0 on my Nexus 5 and start fresh. This is the tutorial that I'm following, and that I followed when flashing Android 6.0 on my Nexus 5 prior to sending it to LG.
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
However it looks like it's not working anymore. On Step 8, the fastboot erase boot command returns me the following:
Code:
c:\adb>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
Anyone knows what that means? I used the ADB Installer 1.3, like I did back then, and even reinstalled it just in case, but to no avail.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
If anyone knows what's happening and can assist me, I would be really grateful! If you need more information, let me know.
Thank you!

Aura. said:
Hi all
I finally received my Nexus 5 back from LG, which said that they replaced the battery and other parts to address my issue (the original thread can be found at the link below).
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-various-issues-t3212261
This being said, I now want to flash Android 6.0 on my Nexus 5 and start fresh. This is the tutorial that I'm following, and that I followed when flashing Android 6.0 on my Nexus 5 prior to sending it to LG.
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
However it looks like it's not working anymore. On Step 8, the fastboot erase boot command returns me the following:
Code:
c:\adb>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
Anyone knows what that means? I used the ADB Installer 1.3, like I did back then, and even reinstalled it just in case, but to no avail.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
If anyone knows what's happening and can assist me, I would be really grateful! If you need more information, let me know.
Thank you!
Click to expand...
Click to collapse
Is your bootloader unlock? That is the first thing that comes to mind when ADB fails to write.
Sent from my SAMSUNG-SM-N910A using Tapatalk

It is, here's the output of the fastboot oem unlock command.
Code:
c:\adb>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
Also I can see on my phone LOCK STATE - unlocked

Alright so I restarted my phone in fastboot mode, and the command went through. Weird, now I'm at the step where I need to flash system, recovery, boot, cache, etc. manually, but I keep on getting this message:
Code:
c:\adb>fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.578s]
sending 'system' (1019257 KB)...
FAILED (command write failed (Too many links))
finished. total time: 0.625s
Restarted multiple times, also changed USB port (from USB 3.0 to USB 2.0) but the error persists. Any ideas?

Issue most likely solved. Changed my USB cable for a 2.0 one (I was using the 3.0 that came with the Nexus 5, but it started to be a bit loose), plugged it in a USB 2.0 port, and all the commands went through successfully. If I see that my Nexus behaves weirdly, I'll fastboot it again using the same setup to make sure that everything goes through properly.
This being said, issue solved, you can close this thread if you wish

Asus ME301T cannot flash using fastboot

Hi all,
I'm trying to get an Asus ME301T running again. It would hang on startup so I tried to flash the stock ROM again. I've tried for three days now without success.
I'm using Ubuntu 15.10 with ADB and Fastboot from PPA and set Android rules and stuff. Using this same setup, I could flash TWRP to my old HTC One X.
The following works:
sudo fastboot devices //shows my device id
sudo fastboot reboot
sudo fastboot erase system, userdata, boot, cache
The following seems to freeze the device, as the RCK/Android/wipe data screen stops blinking:
sudo fastboot erase recovery, misc
sudo -i 0x0b05 flash system blob //blob file of stock ROM, hangs on line "writing 'system' " and makes the device screen stop blinking
erasing 'system'...
OKAY [ 0.193s]
sending 'system' (10257 KB)...
OKAY [143.739s]
writing 'system'...
The same thing happens when I try to flash TWRP to the recovery partition.
I think the device has not been unlocked using the unlock APK file from Asus, but I cannot do that, as I cannot start Android. Is there another way?
Any help would be really appreciated!

How much time You gace fastboot to write the system? For me (tf300t) i took about 15 minutes.
Sent using XT1562 - stock 6.0 (retasia DualSim)

Waited more than an hour and finally got a failed message.
ch3mn3y said:
How much time You gace fastboot to write the system? For me (tf300t) i took about 15 minutes.
Sent using XT1562 - stock 6.0 (retasia DualSim)
Click to expand...
Click to collapse

Try this or Transformerforums
http://forum.xda-developers.com/showthread.php?t=2307313

Pixel 3a - stuck on BootLoader with: error boot prepar

Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked

DarthLuch said:
Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked
Click to expand...
Click to collapse
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.

adm1jtg said:
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.
Click to expand...
Click to collapse
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!

DarthLuch said:
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!
Click to expand...
Click to collapse
If 21 worked but 22 didn't... Going from my faltering memory that means your not on March security, your on feb or earlier. 22 only worked on March, i am running it myself.

I got stuck here, too... I used the flash tool (flash.android.com) and it put me back to stock after about a 20 minute progress bar crawl

I have the same problem can someone help me?

YYa solucionaste ?

Sony Xperia XZ1 Compact stucked after booting TWRP

Hey guys.
I'm having trouble to come forward booting my device with TWRP on my Sony Xperia XZ1 Compact (G8441) using a MacOSX.
Additional info to the phone:
version-baseband:1307-7511_47.2.A.11.228
version-bootloader:1306-5035_X_Boot_MSM8998_LA2.0_P_114
Steps I did:
Unlocking the bootloader (worked)
Flashing with TWRP from Androidfilehost (here) with:
Code:
./fastboot flash recovery TWRP.img
I've used Android 9.0 twrp-3.3.1-0-lilac-pie-5.img as TWRP.img
It gives me:
Code:
./fastboot flash recovery TWRP.imgSending 'recovery' (34548 KB) OKAY [ 0.750s]
Writing 'recovery' OKAY [ 0.262s]
Finished. Total time: 1.016s
Booting with TWRP:
Code:
./fastboot boot TWRP.img
Sending 'boot.img' (34548 KB) OKAY [ 0.749s]
Booting OKAY [ 5.742s]
After step #3 the phone gets stuck on the Splash screen showing "SONY" (blue LED light on)
Rebooting into normal mode using Volume-Up + Power also gives me a similar outcome leaving the phone stuck on the "XPERIA" screen.
I've read somewhere in this forum that a possible solution could be to format the cache and user data which gives me:
Code:
./fastboot format cache
/Applications/Android/./mke2fs failed with status 1
fastboot: error: Cannot generate image for cache
And a similar one for user data.
Does anyone of you have a clue what I did wrong and what I need to do next to solve it? Every constructive comment is much appreciated.
Best
EDIT:
I could get it running and were able to install lineage-17.1-20201217-UNOFFICIAL-v1.7-lilac from here (androidfilehost.com - modpunk).
It was working to get into TWRP through unplugging the USB cable. Restarting the phone and directly after it restarts pressing volume up and plugging in the USB again.

Wondering why you try to boot into TWRP when it has already been successfully installed?
Code:
fastboot boot <TWRP.IMG>
is used if TWRP isn't already installed yet.
You should run
Code:
adb devices
adb reboot recovery
instead.