[Q] Another N7 Wont boot but bootloader ok

filking · Apr 19, 2014

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?

mdamaged · Apr 19, 2014

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?

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.

filking · Apr 19, 2014

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?

mdamaged · Apr 19, 2014

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.

filking · Apr 20, 2014

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?

tetakpatak · Apr 20, 2014

filking said:
Any more hints?

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

filking · Apr 20, 2014

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

tetakpatak · Apr 20, 2014

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

filking · Apr 20, 2014

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....

tetakpatak · Apr 20, 2014

filking said:
It is unlocked.....

Try to execute in the bootloader mode "fastboot oem lock"

tetakpatalked from P5110

tetakpatak · Apr 20, 2014

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

filking · Apr 20, 2014

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.

tetakpatak · Apr 20, 2014

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.

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

tetakpatak · Apr 21, 2014

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.

Mate, here is my promissed thread:
http://xdaforums.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

filking · Apr 21, 2014

Looking now..

Thanks a lot.

Topics

Topics

[Q] Another N7 Wont boot but bootloader ok

filking

Senior Member

mdamaged

Senior Member

filking

Senior Member

mdamaged

Senior Member

filking

Senior Member

tetakpatak

Senior Member

filking

Senior Member

tetakpatak

Senior Member

filking

Senior Member

tetakpatak

Senior Member

tetakpatak

Senior Member

filking

Senior Member

tetakpatak

Senior Member

tetakpatak

Senior Member

filking

Senior Member

Similar threads

New posts