Nexus 7 2012 Wi-Fi stucked at bootloader - Nexus 7 Q&A, Help & Troubleshooting

Hi all, I'm really a newbie and hope you can help me with my Nexus 7 2012 wi-fi.
I tried to downgrade to 4.4.4 ( becasuse from 5.0 the tablet was unusable) following the instructions I found on gottabemobile.
I unlocked the device and everything seemed ok but when I try to write the new image with flash-all.bat I get the following errors, like the computer can't communicate with the device.
Code:
...
OKAY [ 0.000s]
finished. total time: 0.000s
erasing 'boot'...
FAILED (remote: (Timeout))
finished. total time: 2.044s
erasing 'cache'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
erasing 'recovery'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
erasing 'system'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
erasing 'userdata'...
FAILED (remote: (Timeout))
finished. total time: 2.028s
sending 'bootloader' (2100 KB)...
FAILED (remote: (Timeout))
finished. total time: 2.028s
rebooting into bootloader...
FAILED (remote: (Nv3pBadReceiveLength))
finished. total time: 1.014s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 14569963520
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3557120
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/889440 inodes and 97309/3557120 blocks
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d2856b1400802
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4994 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.179s
If I try a fastboot devices I can see the serial number of the tablet but it is stucked in fastboot mode.
The bootloader is v. 4.23, product name is grouper, the image I'm using is image-nakasi-ktu84p (nakasi-ktu84p-factory-2c6e4d6f.tgz)
In computer management I see Android Device > Android Bootloader Interface
What did I do wrong? Have I bricked the device or it can be saved? Thanks in advance for any help.

Did you try with a different USB cable / a different USB port? Because it looks really as a communication problem.
Nevertheless be sure not to flash one of the factory images which contain a defective bootloader! Normally I am unpacking the factory image and flash boot.img and system.img manually by fastboot, i.e.:
- fastboot flash boot boot.img
- fastboot flash system system.img

Thanks for your help AndDiSa: I changed cable and port and flashed the images one by one and it worked!
Just one question: is Android 4.3 faster that 4.4 on the Nexus 7? Will I miss something big if I downgrade to 4.3?

You should probably even try 6.x

Related

Can't flash my system

Hey,
one day my phone suddenly stopped working properly so i rebooted it. But instead of rebooting it had a bootloop.
I erased the whole phone and tried to flash the stock image but I get the following errors:
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.109s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.125s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.782s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.798s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
Creating filesystem with parameters:
Size: 14129561600
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3449600
Block groups: 106
Reserved block group size: 847
Created filesystem with 11/863264 inodes and 95427/3449600 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.03
Serial Number........: XXXXXXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot' (6366 KB)...
OKAY [ 0.250s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.343s
Press any key to exit...
Now I can not boot the phone or even open recovery mode...
What should I do? Is my Phone bricked? Can I repair it?
Hope you guys will help me.
Thank you for every hint
Seems like bad eMMC. RMA if the phone's under 2 years.
DrFredPhD said:
Seems like bad eMMC. RMA if the phone's under 2 years.
Click to expand...
Click to collapse
Is it for me possible to change the eMMC?
If yes where can I buy one ?
Forget about it. eMMC is a BGA part, you need professional tools or a lot of luck to change one at home successfully. If you could get a new motherboard it would be better, but I don't recommend it as a new motherboard would come blank or clone IMEI and you have no way of changing it to original one, and a used motherboard may have other problems/barred IMEI.
DrFredPhD said:
Forget about it. eMMC is a BGA part, you need professional tools or a lot of luck to change one at home successfully. If you could get a new motherboard it would be better, but I don't recommend it as a new motherboard would come blank or clone IMEI and you have no way of changing it to original one, and a used motherboard may have other problems/barred IMEI.
Click to expand...
Click to collapse
So what should I do now?
My phone is older than 2 years...
You could try follow this guide, but I don't think it will help (it's mainly for people who don't have working bootloader mode). http://forum.xda-developers.com/showthread.php?t=2347060
Failing that, new phone time. Moto G has similar specs at a good price.

[Q] Bricked Nexus 10 - Wrong Bootloader Version?

Hi There,
I've had a bricked Nexus 10 for 2 years now. Been trying WugFresh toolkit for a while & also tried manually flashing.
I realized in the code that it says that I have the wrong bootloader version:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.024s]
finished. total time: 0.028s
erasing 'recovery'...
OKAY [ 0.024s]
finished. total time: 0.024s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.024s]
finished. total time: 0.024s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.024s]
finished. total time: 0.024s
sending 'bootloader' (1280 KB)...
OKAY [ 0.184s]
writing 'bootloader'...
OKAY [ 0.148s]
finished. total time: 0.340s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.008s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 blocks
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB03G6VJ
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ12'.
Update requires 'MANTAMF01'.
finished. total time: 0.024s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
---
"Device version-bootloader is 'MANTALJ12'.
Update requires 'MANTAMF01'."
Anyone what the next steps are? Some help would be greatly appreciated :good:
Thanks!!
Hi,
I'll suggest you flashing a stock ROM from zero here. It seems the version you're trying to install is incompatible with the bootloader version. To do as such, follow the instructions in the 3rd post of this thread: http://forum.xda-developers.com/showthread.php?t=2670400
Good luck,
~Lord
XxLordxX said:
Hi,
I'll suggest you flashing a stock ROM from zero here. It seems the version you're trying to install is incompatible with the bootloader version. To do as such, follow the instructions in the 3rd post of this thread: http://forum.xda-developers.com/showthread.php?t=2670400
Good luck,
~Lord
Click to expand...
Click to collapse
Hi Lord,
I appreciate the reply . As per your suggestion I tried the code in post 3:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Brian Wu>cd downloads
C:\Users\Brian Wu\Downloads>cd fastboot
C:\Users\Brian Wu\Downloads\fastboot>fastboot devices
R32CB03G6VJ fastboot
C:\Users\Brian Wu\Downloads\fastboot>fastboot oem unlock
...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Users\Brian Wu\Downloads\fastboot>fastboot erase system -w
erasing 'system'...
OKAY [ 0.016s]
erasing 'userdata'...
OKAY [ 0.016s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 blocks
sending 'userdata' (139141 KB)...
writing 'userdata'...
OKAY [ 19.061s]
erasing 'cache'...
OKAY [ 0.020s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
sending 'cache' (10372 KB)...
writing 'cache'...
OKAY [ 1.434s]
finished. total time: 20.548s
C:\Users\Brian Wu\Downloads\fastboot>fastboot erase boot
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Brian Wu\Downloads\fastboot>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash bootloader bootloader-manta-
mantamf01.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.163s]
writing 'bootloader'...
OKAY [ 0.140s]
finished. total time: 0.305s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash system system.img
sending 'system' (522703 KB)...
OKAY [ 65.681s]
writing 'system'...
OKAY [ 4.249s]
finished. total time: 69.931s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash userdata userdata.img
sending 'userdata' (137478 KB)...
OKAY [ 17.284s]
writing 'userdata'...
OKAY [ 0.588s]
finished. total time: 17.874s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash cache cache.img
sending 'cache' (10372 KB)...
OKAY [ 1.308s]
writing 'cache'...
OKAY [ 0.090s]
finished. total time: 1.399s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash boot boot.img
sending 'boot' (4608 KB)...
OKAY [ 0.584s]
writing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.604s
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash recovery recovery.ig
error: cannot load 'recovery.ig'
C:\Users\Brian Wu\Downloads\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (5108 KB)...
OKAY [ 0.645s]
writing 'recovery'...
OKAY [ 0.021s]
finished. total time: 0.666s
C:\Users\Brian Wu\Downloads\fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Users\Brian Wu\Downloads\fastboot>
---
However when it rebooted, I'm still bricked. Any ideas?
I was also able to flash the file with the correct bootloader version:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.020s
erasing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.021s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.100s]
finished. total time: 0.270s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 blocks
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB03G6VJ
--------------------------------------------
checking product...
OKAY [ 0.014s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4608 KB)...
OKAY [ 0.585s]
writing 'boot'...
OKAY [ 0.019s]
sending 'recovery' (5108 KB)...
OKAY [ 0.647s]
writing 'recovery'...
OKAY [ 0.021s]
erasing 'system'...
OKAY [ 0.020s]
sending 'system' (522703 KB)...
OKAY [ 66.031s]
writing 'system'...
OKAY [ 4.249s]
erasing 'userdata'...
OKAY [ 0.020s]
sending 'userdata' (139141 KB)...
OKAY [ 17.548s]
writing 'userdata'...
OKAY [ 1.086s]
erasing 'cache'...
OKAY [ 0.019s]
sending 'cache' (10372 KB)...
OKAY [ 1.313s]
writing 'cache'...
OKAY [ 0.089s]
rebooting...
finished. total time: 91.692s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
---
but still stuck on the Google logo with the lock symbol.
Hi,
Well, it is looking a problem far more complicated than I expected at first. You are clearly writing the partitions, but for some reason it is not booting in Android. Can you start recovery? If you can we can try issuing some commands via adb to your tablet.
~Lord
Hi Lord,
Really appreciate the follow up.
I can go to recovery or flashboot custom recovery via wugfresh. Do you happen to know which thread has the instructions for the sideload?
Thanks
I was able to get to stock recovery menu to do an adb sideload via wugfresh tools, but once it aborts installation everytime. Any ways around this?

[Q] Boot loop, unable to write to 'system'

Hi,
I've been trying to put Nethunter on my nexus and seems to have bricked the device.
My main issue is being unable to write to 'Bootloader' and' 'System'. See below for the problem I'm having.
I've tried a number of different images and variations on the steps but nothing seems to work. Any help would be great! Thanks
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.031s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.062s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.031s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.062s]
finished. total time: 0.062s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.016s]
finished. total time: 1.031s
sending 'bootloader' (2100 KB)...
OKAY [ 0.469s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.625s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d24bc7d10080f
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.031s]
sending 'boot' (5184 KB)...
OKAY [ 1.062s]
writing 'boot'...
OKAY [ 0.188s]
sending 'recovery' (5738 KB)...
OKAY [ 1.188s]
writing 'recovery'...
OKAY [ 0.203s]
erasing 'system'...
OKAY [ 0.047s]
sending 'system' (649455 KB)...
OKAY [131.703s]
writing 'system'...
FAILED (remote: (BadParameter))
finished. total time: 144.578s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Hi, if you restart do you have the same apps and system there was before? Or is all erased as it should be according to your erase actions in fastboot?
If all works the same as it was it seems you have the same problem as us. There is unfortunately still no solution for this problem. If it is only a bootloader writing problem I also can't help you out, sorry.
See http://forum.xda-developers.com/showthread.php?t=2588911
There is nothing. It gets stuck on the google logo and never gets past that stage so I assume it's been completely wiped.

Can't update bootloader from LJ12 to MF01...

Hey all,
My nexus 10 randomly started bootlooping a while back (i was on some custom firmware on something like 4.2, but never bothered to update because I rarely used it). Today I decided to take the plunge and try and restore this thing to stock firmware, so I tried to install the stock firmware on the google site for 5.1.1... and it didn't work. This was the log:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
erasing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.020s
erasing 'recovery'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.019s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.021s
sending 'bootloader' (1280 KB)...
OKAY [ 0.163s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.294s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 14273216512
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3484672
Block groups: 107
Reserved block group size: 855
Created filesystem with 11/871408 inodes and 96018/3484672 blocks
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB053T9E
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ12'.
Update requires 'MANTAMF01'.
finished. total time: 0.018s
Press any key to exit...
Apparently, despite writing the MF01 bootloader to the tablet, it didn't take. I tried to do this manually with fastboot, but this also didn't hold - my tablet still defiantly displays its bootloader version as MANTALJ12.
Is there anything I can do to beat the new version into its head? Did I mess something up? Or am I just SOL?
Thanks in advance...

Did I hard bricked my tablet?

Hi,
My Nexus 7 2012 tablet was running very slow with Lollypop 5.1.1, so I tried to downgrade it to Kitkat 4.4.4.
I first installed Clockworkmod 7 and then tried to flash the image. I did it on a Mac Terminal. I had to add ./ in some of the files as I got a fastboot not found error but still kept on showing errors. I finally made the huge mistake of trying to reboot and the tablet hasnĀ“t load from that moment, not even the battery signal. The computer doesn't recognize it either. I have tried several button combinations to start the tablet but nothing works. All I get is a black screen.
Once I got here, could you tell me, is this a hard brick? Is there a solution? Do I have to say goodbye to my tablet? Any help will be very much appreciated.
Thanks in advance.
In case this clears the process, here's what the Terminal showed:
Last login: Sun Jul 3 16:45:48 on ttys000
jurgen:~ admin$ cd /JURGEN/desktop/kitkat
-bash: cd: /JURGEN/desktop/kitkat: No such file or directory
jurgen:~ admin$ cd desktop/kitkat
jurgen:kitkat admin$ ./flash-all.sh
./flash-all.sh: line 17: fastboot: command not found
./flash-all.sh: line 18: fastboot: command not found
./flash-all.sh: line 19: fastboot: command not found
./flash-all.sh: line 20: fastboot: command not found
./flash-all.sh: line 21: fastboot: command not found
./flash-all.sh: line 22: fastboot: command not found
./flash-all.sh: line 23: fastboot: command not found
./flash-all.sh: line 24: fastboot: command not found
./flash-all.sh: line 26: fastboot: command not found
./flash-all.sh: line 27: fastboot: command not found
./flash-all.sh: line 29: fastboot: command not found
jurgen:kitkat admin$ ./flash-all.sh
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.143s]
finished. total time: 0.143s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.126s]
finished. total time: 0.126s
erasing 'recovery'...
OKAY [ 0.025s]
finished. total time: 0.025s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.627s]
finished. total time: 0.627s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 10.666s]
finished. total time: 10.666s
sending 'bootloader' (2100 KB)...
OKAY [ 0.275s]
writing 'bootloader'...
OKAY [ 1.224s]
finished. total time: 1.499s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
./flash-all.sh: line 25: ./sleep: No such file or directory
ERROR: Unable to create a plug-in (e00002be)
< waiting for device >
sending 'radio' (16384 KB)...
OKAY [ 2.036s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.059s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
./flash-all.sh: line 28: ./sleep: No such file or directory
ERROR: Unable to create a plug-in (e00002be)
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
Creating filesystem with parameters:
Size: 30080499712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7343872
Block groups: 225
Reserved block group size: 1024
Created filesystem with 11/1836000 inodes and 159268/7343872 blocks
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d25648b5c1a14
--------------------------------------------
checking product...
FAILED
Device product is 'grouper'.
Update requires 'tilapia'.
finished. total time: 0.123s
jurgen:kitkat admin$ ./flash-all.sh
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.017s]
finished. total time: 0.017s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.083s]
finished. total time: 0.083s
erasing 'recovery'...
OKAY [ 0.017s]
finished. total time: 0.017s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.109s]
finished. total time: 0.109s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 4.938s]
finished. total time: 4.938s
sending 'bootloader' (2100 KB)...
OKAY [ 0.276s]
writing 'bootloader'...
OKAY [ 1.207s]
finished. total time: 1.483s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
./flash-all.sh: line 25: ./sleep: No such file or directory
< waiting for device >
sending 'radio' (16384 KB)...
OKAY [ 2.019s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.034s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
./flash-all.sh: line 28: ./sleep: No such file or directory
ERROR: Unable to create a plug-in (e00002be)
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
Creating filesystem with parameters:
Size: 30080499712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7343872
Block groups: 225
Reserved block group size: 1024
Created filesystem with 11/1836000 inodes and 159268/7343872 blocks
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d25648b5c1a14
--------------------------------------------
checking product...
FAILED
Device product is 'grouper'.
Update requires 'tilapia'.
finished. total time: 0.113s
jurgen:kitkat admin$ ./flash-all.sh
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.017s]
finished. total time: 0.017s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.083s]
finished. total time: 0.083s
erasing 'recovery'...
OKAY [ 0.017s]
finished. total time: 0.017s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.109s]
finished. total time: 0.109s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 4.938s]
finished. total time: 4.938s
sending 'bootloader' (2100 KB)...
OKAY [ 0.276s]
writing 'bootloader'...
OKAY [ 1.213s]
finished. total time: 1.489s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
./flash-all.sh: line 25: ./sleep: No such file or directory
< waiting for device >
sending 'radio' (16384 KB)...
OKAY [ 2.027s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.045s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
./flash-all.sh: line 28: ./sleep: No such file or directory
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
Creating filesystem with parameters:
Size: 30080499712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7343872
Block groups: 225
Reserved block group size: 1024
Created filesystem with 11/1836000 inodes and 159268/7343872 blocks
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d25648b5c1a14
--------------------------------------------
checking product...
FAILED
Device product is 'grouper'.
Update requires 'tilapia'.
finished. total time: 0.112s
jurgen:kitkat admin$
hi! did you have soved your problem yet? the problem here is that the script erased everything in your device, and by the output you pasted it seems that it flashed bootloader correctly, so you should be able to boot into bootloader mode. have you tried doing a battery pull? also, have your device enough battery to boot? the process failed because the image you tried to flash was a 3G/tilapia version and you have a WiFi/grouper device (it says that in the terminal).
try to do a battery pull, and try to boot into bootloader, if you can you could flash everything back from here, this is of course if you haven't got rid of your device already. hope this helps, and please post your results
HectorFabianC said:
hi! did you have soved your problem yet? the problem here is that the script erased everything in your device, and by the output you pasted it seems that it flashed bootloader correctly, so you should be able to boot into bootloader mode. have you tried doing a battery pull? also, have your device enough battery to boot? the process failed because the image you tried to flash was a 3G/tilapia version and you have a WiFi/grouper device (it says that in the terminal).
try to do a battery pull, and try to boot into bootloader, if you can you could flash everything back from here, this is of course if you haven't got rid of your device already. hope this helps, and please post your results
Click to expand...
Click to collapse
Hi,
Thanks for your response.
I finally bought another mother board and installed it.

Categories

Resources