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.
Related
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Do what everyone should be doing... use Rezo's tool to root and install CWM. Then use CWM to flash your ROM. Simple.
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Is your bootloader unlocked? It must be to do that
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Boot your device on HBOOT, and select FASTBOOT and then connect with PC. (USB Debugging must be enabled)
Follow the instructions here to Flash ROM :
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
It's done now.
My phone stuck while using so as usual I pulled out the battery and it was his end. From then on bootanimation glitched and the phone restarted all over again. Sth like a bootloop but with complete phone restart. Then I tried to full wipe but with no luck, recovery hung and rebooted the phone. Even now restoring/zip installing etc suddenly restarts the phone. I also tried to flash new recovery/rom via fastboot as well as via Nexus Root Toolkit but everytime I got 'too many links error'
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2308 KB)...
OKAY [ 0.227s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.404s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.005s
sending 'radio' (12288 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.005s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.004s
archive does not contain 'boot.sig'
error: out of memory
Click to expand...
Click to collapse
I used two different cables that I use for every flashing so far, and different usb slots... I have no idea what else I can do.
Sth has changed, I tried to flash TWRP instead of CWM via fastboot and again, got 'too many links' error BUT it flashed the new recovery anyway . So now I have TWRP, managed to flash cm 10.2.1+gapps. I have a recovery log for sb to analyze. Could you check if my emmc is corrupted telling ftom this log?
i9250 recovery log http://pastebin.com/4Yx0ZwJK
Thanks
EDIT/
A second ago it booted to system in a normal way, then a sudden restart and the phone is stuck while boot animation, like a catch 22...
i can only get to fastboot mode. My nexus Bootloader version - FLO- 04.04, and it's unlocked. I've tried to use Wug tool kit but got stuck at "erasing cache". See log below. I've tried different cables and different USB ports. Any tips or guidance is greatly appreciate. Thanks
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.139s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.742s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
sending 'boot' (7448 KB)...
OKAY [ 0.245s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.166s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
erasing 'cache'...
i have the same problem
the nand flash is broken, change your mainboard and you will be happy again
i will never buy a asus device
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
matthew.bridell said:
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
Click to expand...
Click to collapse
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
CyberpodS2 said:
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
Click to expand...
Click to collapse
flash the zip? Would I just use fastboot flash image-taimen-opm1.171019.018.zip ?
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
CyberpodS2 said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
I was able to install Lineage-15.1-20180219 and boot into it. Tried to restore from that point and it now when I run flash-all it now says
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.006s
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
error: cannot load system.img from flash
Press any key to exit...
matthew.bridell said:
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
Click to expand...
Click to collapse
You need to update your platform-tools.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
just tried the zip and no luck
C:\Users\matth\Downloads>cd "platform-tools-latest-windows (2)"
C:\Users\matth\Downloads\platform-tools-latest-windows (2)>cd platform-tools
C:\Users\matth\Downloads\platform-tools-latest-windows (2)\platform-tools>flash-all
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.005s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.221s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
I do now have default Recover but don't know why it won't work.
I feel dumb. I got it to work with using a usb-a to usb-c cord. was trying to use the usb-c to usb-c cord thanks for all the help.
So, I was trying to install the twrp, but when I do put out the comand for the flash recovery I get this section:
sending 'recovery' (44474 KB)...
OKAY [ 1.537s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 1.585s
I did try to just boot it already and got this:
downloading 'boot.img'...
OKAY [ 1.216s]
booting...
FAILED (remote failure)
finished. total time: 1.400s
Can anyone help?