Help. I got an error today while trying to power on. It was something along the lines of validation failed. Cannot boot.
Then i tried installing the stock rom with the help of fastboot. It was going well. It even had success. But then I ran the command fastboot reboot and the phone doesn't turn on. Stays on black screen. Tried charging. No luck. I don't get any visual confirmation. Can I do anything to fix this phone?
Good. Via ADB the command adb devices or fastboot devices returns something? And the computer even recognizes him? It could be the same case that happened to me.
A year ago his screen turned bran and I sent in an assistance (it was updated in android stock 6.0, until it happened)... Only with the ROM it had, the system did not recognize the new screen (which was changed). Result: They downgraded the android (returned to 5.0) and now I'm breaking to solve an error, i can not even flash any twrp .... The message is
sending 'partition' (32 KB)...
OKAY [ 0.135s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.732s
Same issue here. I've been attemting to run stock firmware on mine. But I've been getting the same error. Idk if it's fixable and my recovery boot is corrupted.
Related
Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?
romka7 said:
Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?
Click to expand...
Click to collapse
If I remember right, it's actually EXT4 and android uses FUSE to make it look like a FAT32 partition to a connected machine.
I would have suggested RUU, but it seems like that's not an option for you. Good luck with your phone, man.
If worst comes to worst just go to att and say it broke randomly, I don't think they can tell it's rooted if you messed it up that badly
Sent from my One X using xda premium
Did you try just running the RUU ?
Ok, I beat it to death.... got it working. Somewhere in my trial and error process I ended up flashing to CWM recovery, which did nothing new for me, then I pushed TWRP again but the 2.1.8, was on 2.2 when the problem started.... all of the sudden ADB started working, not sure what happened on the newer version. I still did not see my SDcard, but I was able to push a version of cleanrom to the system partition. The install did not go, but the the process it formated the sdcard to the proper format.... or it restored some setting. I was then able to mount SD in TWRP and installed newest version of CleanRom.. All good now.... its all a learning process I guess
Hello everyone,
today I had very unpleasant surprise with my nexus 5. Let me tell the whole story from the beginning.
At first, I've never played with my nexus in any way (custom roms, root, etc.), it's all default from the beginning.
Few days ago I upgraded to 5.1 using android default upgrader. Next day I did a factory reset (from the settings menu) and then I encrypted the device. Since the flow of turning on the encrypted Android sucks, I did the factory reset again. Then I installed all the apps etc. and I was happily using the phone for 2 days until today's evening. I plugged my nexus into charging, it had 5% battery and was turned on. An hour or two later, I've noticed that the phone restarted and stucked on "Google" screen.
I tried booting several times. Then I googled how to boot into recovery mode. I hold volume and power buttons for a while, from the screen I chose "Recovery mode" and hit the power button again. Unfortunately I am getting the black screen...
Please, help me to make it working again, I found a lot of Google screen loop problems on the web as well as black screen recovery mode but happening not together and not with stock android.
I would like to have stock 5.1 back, possibly to backup some data before erasing.
Thanks,
alatar
alatar- said:
Hello everyone,
today I had very unpleasant surprise with my nexus 5. Let me tell the whole story from the beginning.
At first, I've never played with my nexus in any way (custom roms, root, etc.), it's all default from the beginning.
Few days ago I upgraded to 5.1 using android default upgrader. Next day I did a factory reset (from the settings menu) and then I encrypted the device. Since the flow of turning on the encrypted Android sucks, I did the factory reset again. Then I installed all the apps etc. and I was happily using the phone for 2 days until today's evening. I plugged my nexus into charging, it had 5% battery and was turned on. An hour or two later, I've noticed that the phone restarted and stucked on "Google" screen.
I tried booting several times. Then I googled how to boot into recovery mode. I hold volume and power buttons for a while, from the screen I chose "Recovery mode" and hit the power button again. Unfortunately I am getting the black screen...
Please, help me to make it working again, I found a lot of Google screen loop problems on the web as well as black screen recovery mode but happening not together and not with stock android.
I would like to have stock 5.1 back, possibly to backup some data before erasing.
Thanks,
alatar
Click to expand...
Click to collapse
Well you have two options:
Reflash stock rom with fastboot http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Or
Reflash stock rom with LG flashtool http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Both method will wipe your phone.
Use fastboot to reflash stock rom, but you may need to wipe data too. I've had this randomly happen before, luckily for me tho I had twrp and a backup, but even after re-installing the rom it'd still not load, i assume data had just got corrupted somehow unluckily, wiped data and all was fine and has been ever since
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Thank you @bitdomo and @Ben36.
So I tried reflashing with fastboot. I connected n5 to my notebook (running Ubuntu 14.04) and I turned on the device into fastboot mode. I ended up with "FAILED (remote: flash write failure)".
Here is what I did:
Code:
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot devices
[I]XXXXXXXXXXXX[/I] fastboot
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot oem unlock
...
OKAY [ 48.373s]
finished. total time: 48.374s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.292s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.472s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.476s
I wanted to try with another cable and usb port but I didn't manage n5 to be recognized in fastboot lately (fastboot devices list is empty, lsusb is blind as well). I did a lot of attempts both on linux and windows 8 but it worked only twice on linux.
I will try again later. Perhaps you have some advise for this problem?
PS What is strange, after few minutes I plug n5 intro charging , it starts booting by itself... What the hell?
PS2 The phone keeps restarting whole the time... The battery seemed empty so I was charging it. It starts charging, after a minute it starts booting and then after 3 minutes it goes off. All over again and again.
alatar- said:
Thank you @bitdomo and @Ben36.
So I tried reflashing with fastboot. I connected n5 to my notebook (running Ubuntu 14.04) and I turned on the device into fastboot mode. I ended up with "FAILED (remote: flash write failure)".
Here is what I did:
Code:
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot devices
[I]XXXXXXXXXXXX[/I] fastboot
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot oem unlock
...
OKAY [ 48.373s]
finished. total time: 48.374s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.292s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.472s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.476s
I wanted to try with another cable and usb port but I didn't manage n5 to be recognized in fastboot lately (fastboot devices list is empty, lsusb is blind as well). I did a lot of attempts both on linux and windows 8 but it worked only twice on linux.
I will try again later. Perhaps you have some advise for this problem?
PS What is strange, after few minutes I plug n5 intro charging , it starts booting by itself... What the hell?
Click to expand...
Click to collapse
That error message you get means that the emmc of the phone is fauilty.
Do you have warranty?
bitdomo said:
That error message you get means that the emmc of the phone is fauilty.
Do you have warranty?
Click to expand...
Click to collapse
Yes, I do. I have the phone just since few months. Are you sure about that? Cannot it be a failure of my usb port or poor cable quality?
alatar- said:
Yes, I do. I have the phone just since few months. Are you sure about that? Cannot it be a failure of my usb port or poor cable quality?
Click to expand...
Click to collapse
I am sure about that, there plenty of other people having the same problem. Only solution is to buy a new motherboard.
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
So for the past week, my phone has been bricked. Bricked by flashing the wrong firmware, so now not able to access the whole phone, and making matters worse by flashing the wrong recovery for the phone. The phone being an Honor 8, FRD-L14, 64GB.
I'm not able to use dload to rollback anything, or use that option at all, since the recovery isn't eRecovery, and doesn't even have any recovery in itself.
The problem is that I'm able to boot into "download mode" my phones unlocked, and when I type in "fastboot oem get-bootinfo", the response is:
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.010s
But when trying to flash anything through fastboot in the cmd, like the command "fastboot flash recovery recovery.img" to flash a recovery on the phone, the response would then be:
target reported max download size of 471859200 bytes
sending 'recovery' (29378 KB)...
OKAY [ 0.803s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.814s
My phone is unlocked, and on the download mode screen, is shows:
PHONE Unlocked
FRP Unlock
My drivers are installed, as well as the device being shown in fastboot when typing in the command "fastboot devices"
I haven't been able to do a single thing to the phone, and have searched up a countless amount of hours to find the fix for the phone, if anyone can, please look into the problem and assist me, thanks .
Kc4k12 said:
So for the past week, my phone has been bricked. Bricked by flashing the wrong firmware, so now not able to access the whole phone, and making matters worse by flashing the wrong recovery for the phone. The phone being an Honor 8, FRD-L14, 64GB.
I'm not able to use dload to rollback anything, or use that option at all, since the recovery isn't eRecovery, and doesn't even have any recovery in itself.
The problem is that I'm able to boot into "download mode" my phones unlocked, and when I type in "fastboot oem get-bootinfo", the response is:
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.010s
But when trying to flash anything through fastboot in the cmd, like the command "fastboot flash recovery recovery.img" to flash a recovery on the phone, the response would then be:
target reported max download size of 471859200 bytes
sending 'recovery' (29378 KB)...
OKAY [ 0.803s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.814s
My phone is unlocked, and on the download mode screen, is shows:
PHONE Unlocked
FRP Unlock
My drivers are installed, as well as the device being shown in fastboot when typing in the command "fastboot devices"
I haven't been able to do a single thing to the phone, and have searched up a countless amount of hours to find the fix for the phone, if anyone can, please look into the problem and assist me, thanks .
Click to expand...
Click to collapse
You're in a tough situation my friend, what do you get when you try the dload method? In my opinion this is the only thing you can do. However i heard about a thing called "DC Unlocker" . It can flash a clean ROM and other good stuff for bricked Huawei phones, but you have to pay, and i don't know what the prices are. Hope you'll make it
My moto g (xt1032) was running smoothly on Lollipop 5.1, Magisk rooted, until some apps kept crashing so I decided to reboot the phone (Used to fix the issue) but after booting the screen went blank, nothing showing, the only thing that shows was "Turn off" when i hold the power button, so I decided to boot into TWRP (Bootloader was Unlocked) and flash a 5.1 ROM that I used to successfully flash and work, but as soon as it finished and i press reboot, the screen goes black, no boot logo or anything, it only boots on the "Locked" bootloader.
Now the bootloader is showing version 41.1A . I tried to flash the firmware stock image that I used to flash before(GPE 5.1), i keep getting the same errors:
sending 'partition' (32 KB)...
OKAY [ 5.050s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.389s
I tried other 5.1 stock retail firmwares, same thing. anyone can help?