Hi
This seems similar to others but thought i'd post for help incase there is something different.
Device hung, then rebooted but wouldn't get past google screen. Can get into bootloader.
When recovery mode selected get :-
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
Using NRT, tried Back to stock/Unroot and got :-
sending 'bootloader' (3911 KB)...
OKAY [ 0.133s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.702s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 0586533c
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
Then followed instructions and set NRT to force write, and repeated the process.
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.701s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
erasing 'cache'...
And it's been like this for over an hour ..... ermmmm
Any ideas?
filking said:
Hi
This seems similar to others but thought i'd post for help incase there is something different.
Device hung, then rebooted but wouldn't get past google screen. Can get into bootloader.
When recovery mode selected get :-
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
Using NRT, tried Back to stock/Unroot and got :-
sending 'bootloader' (3911 KB)...
OKAY [ 0.133s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.702s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 0586533c
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
Then followed instructions and set NRT to force write, and repeated the process.
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.701s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
sending 'boot' (7018 KB)...
OKAY [ 0.235s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.136s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
erasing 'cache'...
And it's been like this for over an hour ..... ermmmm
Any ideas?
Click to expand...
Click to collapse
That looks bad, try a different USB port, if possible a different cable and even a different PC, don't use a usb hub or usb3 port, if none of that helps, it's probably a bad EMMC, see this thread and see if it is.
Haven't got another computer but tried a different usb 2 port and now looks worse.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'boot' (7018 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'cache' (4664 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'recovery' (7564 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
sending 'system' (717936 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'userdata' (136890 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
rebooting...
finished. total time: 0.549s
Any more suggestions?
filking said:
Haven't got another computer but tried a different usb 2 port and now looks worse.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'boot' (7018 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'cache' (4664 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'recovery' (7564 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
sending 'system' (717936 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
sending 'userdata' (136890 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
rebooting...
finished. total time: 0.549s
Any more suggestions?
Click to expand...
Click to collapse
Did you try the thread I linked and do what it said to test if you eMMC is fried? If it is, only a hardware repair will fix it.
Hi,
I tried that link. I go through the recovery mode and get the android system recovery and the :
e:cant mount /cache
......
etc.
I issue the adb shell command and get
adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Any more hints?
filking said:
Any more hints?
Click to expand...
Click to collapse
Mate, there is obviously some connection problem between your PC and your device. The most likely of all: it is a USB driver related problem. I'm trying to help last few days to another forum mate @PieceofSlice who has almost identic problem. He is on 04.01 bootloader and uses Windows 7 PC.
Please take my advice and don't try to flash bootloader anymore until you are 100% sure that the fastboot connection works perfectly fine. If your bootloader gets erased and the new one doesn't get flashed, the Tab is hard-bricked and only JTAG service will can revive it. As long as your bootloader is OK, you will get your tab working again, don't worry.
Actually it would be worth it to install Linux besides Windows and execute fastboot directly from there. Linux needs no drivers and always works. IDK if Ubuntu could also work if you run it in a Virtual Machine in Windows.
tetakpatalked from P5110
Thanks for your reply.
Actually, the more I think about it, the more I think it is the connection socket on the tablet that is faulty, rather than the link/pc.
I've had occasions when moving the cable near the socket, (which appears a tad loose), has caused the tablet to stop charging then start again.
This tablet is a replacement for a broken N7 (2012) that I got from a retail shop in the UK. As they gave me a new receipt, this tab is covered under year warranty. If I take it into the shop, they will refund and replace, no problem.
My last question is, how can I ensure that all info is wiped. (pretty sure it already is), but as the stock/unroot failed, it prob didn't actually overwrite anything.
ta
Just one crucial question: is your bootloader locked?
If it is, you can give it back. They will unbrick it the way that they will totally wipe whole internal memory before they flash a factory image.
tetakpatalked from P5110
It is unlocked.
Not sure this retail shop will know what to look for when I return it, turn it on, and it doesn't boot. That in my mind is broken and they will prob see it that way.
If they do spot it, or refuse.. I will take it away, rethink, and return to another branch, lots locally.
Unless, NRT will let me remove the lock... maybe....
filking said:
It is unlocked.....
Click to expand...
Click to collapse
Try to execute in the bootloader mode "fastboot oem lock"
tetakpatalked from P5110
OK, all guys with fastboot conectivity problems, it really makes me sad to read about your issues and I hate to hear about bootloops and desperate forum mates!
Therefore, I think this will be solution for most of you: I will post here a new guide within less than 24 hours how to install ADB and fastboot in Ubuntu/Linux OS. If you already have installed Ubuntu OS, it takes only 2 min to install ADB and fastboot.... and IT WORKS THERE!
Linux is in general much better than Windows for flashing Android devices. And it needs no stupid, nasty drivers so the things can't go so easy wrong.
Use this time and already install Ubuntu aside your Windows. In most of cases it works flawlessly. You will have dual boot possibility. Please check WWW how to do it, it costs bit of time but it is really easy afterwards.
tetakpatalked from Nexus 7
That sounds like a very good plan and thanks for helping us poor unfortunate N7 sufferers.
PS: Tried to lock tablet and it said it was successful, and nothing happened. Rebooted, and still unlocked.
filking said:
That sounds like a very good plan and thanks for helping us poor unfortunate N7 sufferers.
PS: Tried to lock tablet and it said it was successful, and nothing happened. Rebooted, and still unlocked.
Click to expand...
Click to collapse
Yep, connection problems....in very most of cases it is related to unproperly working drivers = as I said: not Windows but "Loose-dows"
tetakpatalked from Nexus 7
filking said:
That sounds like a very good plan and thanks for helping us poor unfortunate N7 sufferers.
PS: Tried to lock tablet and it said it was successful, and nothing happened. Rebooted, and still unlocked.
Click to expand...
Click to collapse
Mate, here is my promissed thread:
http://forum.xda-developers.com/showthread.php?t=2726287
If Ubuntu won't flash successfully, we have a hardware related problem and it has to be fixed in the service.
tetakpatalked from Nexus 7
Looking now..
Thanks a lot.
It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
billownz said:
It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
Click to expand...
Click to collapse
What have you been trying to flash as "bootloader" ? If you want to flash a recovery you should do
fastboot flash recovery recovery-destination-here-or-name-if-you-are-aleady-in-the-same-file.img
But I'd suggest you downloading the factory image from Google's page and doing a fresh complete install
PS don't use toolkits they are much more complicated and can mess things up
billownz said:
It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
Click to expand...
Click to collapse
I had the very same issue occur to me 18 hours out of the box on a 2013 refurb. Had to RMA to Asus. It was a hardware issue. On the repair slip they said they had to replace the board.
You might talk to them and see what a repair out of warranty would cost. There is a member here who works for Asus Customer Service, who perhaps might be able to give you some guidance. I cannot find his name at the moment, but will update with it when I do.
Update:
His name is @[email protected] and he posted here with his info: http://forum.xda-developers.com/nexus-7/help/asus-answers-t2846136
Happened the same 2me with my first nexus... I was on cm, two random reboots and that's it, couldn't flash anything, luckily i managed to relock the bootloader and erase the recovery partition (twrp)... Another user couldn't relock the bootloader so he ended up buying a motherboard on ebay
I realize this has been discussed ad nauseam and after searching through all the posts on it I am a little confused about what my options are. My Nexus 7 2013 mobile is stuck on the Google logo. Here's what I have done..
First, I tried to simply wipe the cache partition to no avail.
Second, using the WugFresh Nexus toolkit I tried to unroot and flash stock to no avail. It would get to the point of flashing I would get remote failure error messages when trying to flash the radio etc,
Basically, all I have at this point, is the Google screen and access to fastboot and it's options and the Nexus is recognized by my computer through fastboot.
What are my options now?
Should I relock the bootloader and request Google repair it?
Or should I try to flash 4.4.4 manually through fastboot without a toolkit. If so, can you refresh my memory on how to do this?
I would appreciate any help you could provide. Thanks!
Try flashing 4.4.4 manually in fastboot. There are instructions on the page where you download the firmware. Did you flash 5.0 on a LTE model?
I did not flash 5.0. It froze during usage and I restarted it and then it suddenly would not boot past the Google logo. I did nothing to it.
I downloaded the factory image for 4.4.4 and followed instructions and ran the flash-all.bat and here is what the command prompt returns:
< waiting for device >
sending 'bootloader' (3911 KB)...
OKAY [ 0.152s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.709s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'radio' (76038 KB)...
OKAY [ 3.034s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 174.608s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
Is it time to relock the bootloader and hope Google will repair it?
Hey there,
as the title of the threat already indicates, my HTC One X got bricked.
As this usually happens when trying to flash some custom roms or recoverys, in my case it is the result of an official HTC update for android.
I can boot into Fastboot, and via cmd "fastboot devices" does show me the connected phone.
Now my approach for solving this matter was to flash the clockwork mod and then boot into recovery.
From there i wanted to pull data from the phone via adb commands.
The only problem is that my phone is locked. I cannot unlock it at the moment without wiping all data (which obviously would miss the whole data recovery point).
When i try tp flash the CWM in fastboot i get:
sending 'recovery' (8100 KB)...
FAILED (unknown status code)
finished. total time: 0.933s
I also tried to directly boot a recovery via fastboot boot recovery.img.
This resulted in
downloading 'boot.img'...
FAILED (unknown status code)
finished. total time: 0.933s
Well now I am seriously frustrated and dont know how to get my data.
Any help is very much appreciated.
Cheers
Josef
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
joe1000 said:
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
Click to expand...
Click to collapse
You must to unlock the device qith locked you can't do anything but if you unlock it is possible to wipe all data on the SD card
well but thats exactly the problem...
Hi all,
I'm trying to unroot and relock my Pixel 2 XL because I need to send it in for warranty for an issue with the phone's microphone.
when I try to run the flash-all command in adb I get errors during each step. Could somebody help me figure out what's going on?
Here is what adb is kicking back at me:
Code:
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot devices
712KPRW1212070 fastboot
C:\platform-tools>flash-all
Sending 'bootloader' (36336 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.045s
rebooting into bootloader FAILED (Write to device failed (Too many links))
Finished. Total time: 0.040s
Sending 'radio' (60388 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.045s
rebooting into bootloader FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.035s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
fastboot: error: requirements not met!
Press any key to exit...
Chelseablue said:
Hi all,
I'm trying to unroot and relock my Pixel 2 XL because I need to send it in for warranty for an issue with the phone's microphone.
when I try to run the flash-all command in adb I get errors during each step. Could somebody help me figure out what's going on?
Here is what adb is kicking back at me:
Code:
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot devices
712KPRW1212070 fastboot
C:\platform-tools>flash-all
Sending 'bootloader' (36336 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.045s
rebooting into bootloader FAILED (Write to device failed (Too many links))
Finished. Total time: 0.040s
Sending 'radio' (60388 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.045s
rebooting into bootloader FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.035s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
By the way, I am flashing image 9.0.0 (PQ1A.181205.002, Dec 2018)
I tried flashing the most recent one and got the same errors so I tried an older image.
Chelseablue said:
Hi all,
I'm trying to unroot and relock my Pixel 2 XL because I need to send it in for warranty for an issue with the phone's microphone.
when I try to run the flash-all command in adb I get errors during each step. Could somebody help me figure out what's going on?
Here is what adb is kicking back at me:
By the way, I am flashing image 9.0.0 (PQ1A.181205.002, Dec 2018)
I tried flashing the most recent one and got the same errors so I tried an older image.
Click to expand...
Click to collapse
What version of platform-tools are you using?
And, if your already on stock rom, just do a factory reset and send it back. An unlocked bootloader doesn't void your warranty.
Badger50 said:
What version of platform-tools are you using?
And, if your already on stock rom, just do a factory reset and send it back. An unlocked bootloader doesn't void your warranty.
Click to expand...
Click to collapse
I'm running r28.0.1. Really? I thought it had to have the bootloader locked for warranty. If that's the case, it would save me the time...
Chelseablue said:
I'm running r28.0.1. Really? I thought it had to have the bootloader locked for warranty. If that's the case, it would save me the time...
Click to expand...
Click to collapse
Just reset it and send it in. Many have done so including myself with the 6p. Question, have you tried a different cable, and are using the command...fastboot flashing lock....?
And, have you run the magisk uninstaller zip to fully get rid of root?