[SOLVED] Unable to manually install nexus 7 (2012) wifi ADB driver - Nexus 7 Q&A, Help & Troubleshooting

Hi All,
I did a bit of searching and I haven't come across anyone in my situation, but I'm sure it's happened before. I dusted my nexus 7 (2012) wifi model off that I haven't used in a couple years and I was reading up on re-flashing stock and un-rooting. I'd used the NRT previously so I went back to that. I plugged the tablet into one of my USB3 slots and ran through the manual driver installation. Tested ADB and Fastboot and they both functioned.
I didn't care for retaining any data, I just wanted to upgrade to the newest from 4.2.1 which the tablet was running. When running the 'flash stock + unroot' to version 5.1.1 through the NRT, it ran into an error after wiping the partitions whereas it seemed to be an issue with USB3. The specific error:
"data transfer failure (too many open files in system)"
At this point it had wiped the device, but was unable to load anything back on. After looking into the issue, it appears that it was a result of having the device plugged into USB3... I've since plugged the device into USB2, however, I'm unable to get the drivers to recognize in Windows 8.1... I uninstalled the unrecognized device drivers for the USB2 device, rebooted, and attempted a clean install of both the default Google and Universal drivers (in separate install attempts). Neither of which appear to allow NRT to provide ADB access. The manual installation method was what I used for the USB3 ports, but AFAIK the ADB portion requires you to plug the device in with USB debugging enabled and install the drivers on that device. Since I can't load into anything other than the bootloader, I don't believe I can perform this step.
Am I SOL or is there potentially something I can do to breathe life back into this device? Any recommendations would be appreciated!
Thanks,
Nate

Turns out this was stupid easy using Linux (Ubuntu)... Thanks to Zesty01 for building the below thread:
http://forum.xda-developers.com/showthread.php?t=2647106
--
I had the image already downloaded from NRT toolkit so I just had to copy it over.
$ sudo apt-get update && sudo apt-get install -y android-tools-adb android-tools-fastboot
$ rsync -av --progress /complete/image-nakasi-lmy47v/ nexus7/
$ cd nexus7/
$ ls -la
total 764688
drwxr-x--- 2 derp derp 4096 Sep 5 10:48 .
drwxr-x--- 12 derp derp 4096 Sep 5 10:48 ..
-rw-r----- 1 derp derp 54 Apr 7 2015 android-info.txt
-rw-r----- 1 derp derp 5308416 Dec 31 2008 boot.img
-rw-r----- 1 derp derp 5875712 Dec 31 2008 recovery.img
-rw-r----- 1 derp derp 665042344 Dec 31 2008 system.img
-rw-r----- 1 derp derp 106792476 Dec 31 2008 userdata.img
$ sudo fastboot devices
015d18ad5c14161a fastboot
$ sudo fastboot flash system system.img
erasing 'system'...
OKAY [ 0.127s]
sending 'system' (649455 KB)...
OKAY [ 76.742s]
writing 'system'...
OKAY [ 32.124s]
finished. total time: 108.992s
$ sudo fastboot flash recovery recovery.img
sending 'recovery' (5738 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.362s]
finished. total time: 1.051s
$ sudo fastboot flash boot boot.img
sending 'boot' (5184 KB)...
OKAY [ 0.641s]
writing 'boot'...
OKAY [ 0.342s]
finished. total time: 0.983s
$ sudo fastboot -w
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
erasing 'userdata'...
OKAY [ 1.015s]
sending 'userdata' (137526 KB)...
OKAY [ 16.503s]
writing 'userdata'...
OKAY [ 8.402s]
erasing 'cache'...
OKAY [ 0.119s]
sending 'cache' (9052 KB)...
OKAY [ 1.101s]
writing 'cache'...
OKAY [ 0.636s]
finished. total time: 27.776s
$ sudo fastboot reboot
rebooting...
finished. total time: 0.120s
After about 10 minutes of the system loading, it's back up and accessible! Hope this helps someone else!
Nate

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] N7 stuck at google screen, flash write failure, (Hardware replacement advice)

Yesterday, I was using my Nexus 7 tablet and it suddenly restarted itself. Since then it's been stuck at the Google screen every time I try to start the tablet.
Some info on my tablet:
- Running Kitkat 4.4.2 unrooted (did not update to 4.4.3 or 4.4.4)
- Can enter fastboot mode
- Cannot enter recovery mode (just gets stuck at google screen when I enter it)
- My warranty has ran out
I've tried to flash the device but I get this error:
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.745s
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 'tos.sig'
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 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...: FLO-04.02
Baseband Version.....: none
Serial Number........: 05848e98
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.000s]
sending 'boot' (7014 KB)...
OKAY [ 0.234s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.153s
Press any key to exit...
I trawled through every thread I can find on this forum about this error, most of the time people just send it back to RMA for repairs. (however, my warranty has ran out)
Has anyone had this error and fixed it?
If this is a hardware problem and I want to fix this myself, what hardware do I need to buy? Is a new motherboard enough?

[Q] Nexus 4 bricked ? Please help to understand – Please !

Was on : LSv3.2 ROM / AK.355 AOSP kernal / All of a sudden phone rebooted and ended up in Bootloop
Phone Boots to Boot loader and Recovery just fine , TWRP showing 0MB as storage space. And getting following logs when I try to do MOUNT or FORMAT operation.
E: Cannot munt storage /Data/system etc
And same issue in fresh FAASHING, I get the following message
E: FAILED (remote: flash write failure)
Does this mean my Flash Memory is gone and need to change Motherboard fix issue ? Please let me understand the issue, Any help is deeply appreciated.
RA
Hey.. No relax.. Your software is messed up.. Do this--->>>
1. download the nexus factory image from Google developers
2. download wugfresh toolkit
3. Go to "flash stock+unroot" and tick device is softbricked
4. navigate to the factory image you have downloaded
5. let the toolkit finish,
PS:- DO NOT INTERRUPT THE FLASHING PROCESS
The device should boot up
Sent from my Nexus 4 using XDA Free mobile app
I tried it first; it didn't work (Nexus Root Toolkit by WugFresh) gave same message :crying:. I tried flashing standalone using fastboot commands that also gives same error. Copied the full log from NRT
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
sending 'radio' (45537 KB)...
OKAY [ 1.453s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.469s
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 '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........: 003a98544753509d
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot' (6366 KB)...
OKAY [ 0.219s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.328s
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...
Oh... yup... flash memory is bad
Sent from my Nexus 4 using XDA Free mobile app
Thanks @ arkangel72.
Any other opinion from anyone ? Please let me know
RA
I browsed the net.. You have to take your phone to LG.. You have a hardware failure
Sent from my Nexus 4 using XDA Free mobile app
Thanks Sir - I have replace the logic board and phone back to work. (Got a Phone whose screen was damaged and swapped the boards) I have followed YouTube video on Nexus 4 fixes to conduct the board replacement, Pretty easy and straight forward.
RA

Nexus 7 2012 Wi-Fi stucked at bootloader

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

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