I think i may have bricked my nexus 10.. I was trying to install the chainfire3d application from the market, and when it rebooted, it wouldnt go past the X logo. waited for a long time, so i tried a hard reset, and still nothing. So i figured i would try using the toolkit to help fix. tried to relock, flash, and re-unlock, and it wouldnt work..after the step where you go into factory reset/wipe, it woudlnt go further. I cant get a custom recovery to install, it wont save the file. tried doing that step separately, and it seems to stick on sending the file over. this seems to be a common issue with anything i try.
The screen says:
"sending TWRP touch recovery..
sending 'recovery' (7246 KB) ...
and is just stuck there. this seems to happen in several places, with a few different things ive tried. When trying to flash the stock image, it will get stuck in similar places, perhaps not with the recovery step, but with a portion of the stock image. Been at this for a couple of hours... any help would be greatly appreciated!.
Also, as of now... it wont boot past the google logo. I can get it into fastboot by holding down the buttons, and I can get it into the stock recovery, but thats it. I don't even think adb is detecting the device. I have a feeling that may be a major roadblock to getting this thing fixed. Does anyone know how I can get the tablet to be detected by adb if i cant even get past the google logo screen at boot?
Update 1:
Still cant unbrick my device. any time i try to transfer or flash files to it... it stalls, and if i disconnect the device, i get this error:
FAILED (data transfer failure (too many links)).
Your Device will now boot into Android and detect ADB mode.
problem is, it doesnt reboot, and even if it did, it wouldnt be able to boot into android, since it wont go past the google logo when the device turns on. in fact, i cant even turn it off. only way to turn it off would be to wait for the battery to drain.
If this helps, here is what it says on the fastboot screen:
Device Information
Product Name: manta
Variant: wifi
H/W version : 8
Bootloader Version: MANTALJ12
Carrier Info: none
Serial Number: *********** (not going to publish that, lol)
LOCK STATE: Unlocked
Reboot Mode Flag: none.
anyone have any ideas at all how I can salvage this thing? Im kindof embarrassed honestly. Ive had 5 android devices prior to this one, and have rooted, flashed, and reflashed each of them countless times, and never, ever ran into this before. I could really use the help.
Quick note:
I just noticed that when i try to flash anything to the tablet, the following appears under the rest of the info i listed above.
FASTBOOT STATUS - DATA00713800 (this text is highlighted in light blue)
Update 2:
ok, so i tried to do the factory restore, and am running into the same wall as always. here is the text from the window, perhaps that may clue you into the problem:
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.tg
z
Extracting mantaray-jop40c-factory-0d641789.tar
Everything is Ok
Size: 329369600
Compressed: 326396069
Now extracting flashable Images
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.ta
r
Extracting mantaray-jop40c
Extracting mantaray-jop40c\image-mantaray-jop40c.zip
Extracting mantaray-jop40c\flash-base.sh
Extracting mantaray-jop40c\bootloader-manta-mantalj12.img
Extracting mantaray-jop40c\flash-all.sh
Extracting mantaray-jop40c\flash-all.bat
Everything is Ok
Folders: 1
Files: 5
Size: 329358105
Compressed: 329369600
Factory Images extracted. Starting Flash Process.
Now Flashing Bootloader Image..
sending 'bootloader' (1280 KB)... OKAY [ 0.232s]
writing 'bootloader'... OKAY [ 0.113s]
finished. total time: 0.345s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
Now Flashing Factory Image: Boot, Cache, Recovery, System and Userdata..
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.002s]
sending 'boot' (4606 KB)...
Its just stuck on that last part, sending 'boot' (4606 KB)...
and under all the info on the fastboot page, the following appeared while this was happening:
FASTBOOT STATUS - DATA0047f800 (this line is highlighted in light blue)
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
can you link it?
cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
trying that....
so far so good... dont want to get my hopes up though... below is what ive got so far in the cmd screen:
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
Its been about 30 minutes now... and its still stuck on "sending 'system' (528847 KB)..." in the cmd window.... not sure what that means... it did take about a minute for the recovery to get sent over, and its about 100x larger in size, so i guess i will leave it connected like this for the next hour or so... and hope that it is just going REALLY slowly. Got my fingers crossed...
Battery died while waiting.... this is the complete text of the CMD screen while i was waiting.. forgot that it doesnt charge while in fastboot. got it plugged into an outlet for faster charging while its off.... hopefully when its charged up, i can try again and ill continue to progress
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3941.094s
Press any key to exit...
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
jodvova said:
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
Click to expand...
Click to collapse
I cant get it to load a custom recovery! any advice on how to get that going?
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
Dumb question, if using a desktop PC are you using the front or rear USB ports? I had a similar issue where it would just get stuck on the "sending system" message. Switched the USB from front port to back port on my linux box and it solved my problem.
Sent from my Nexus 10 using Tapatalk 2
jodvova said:
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
Click to expand...
Click to collapse
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
ltracte said:
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
Click to expand...
Click to collapse
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
jodvova said:
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
Click to expand...
Click to collapse
couldnt get the command to work via adb, so i tried it using terminal inside TWRP, and this what it spit back at me:
/dev/block/platform/dw_mmc.0/by-name/system: clean. 11/51296 files. 6651/204800 blocks
i have no idea what that means, nor what else to do....
Fixed it!!!!
ltracte said:
Fixed it!!!!
Click to expand...
Click to collapse
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
mskip said:
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
Click to expand...
Click to collapse
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Whew! So glad you finally had success & thanks for sharing. I'm reading up, research, etc. I received my N10 yesterday. I'm getting ready to unlock/root today.
Sent from my Nexus 7 using Tapatalk 2
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
Hmm, did you try the flash-all.bat file that comes with the factory image? It does those 3 commands, + erases all partitions automatically.
ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
That's exactly what I did. Just followed the factory image flashing instruction on google's page(where you download the image file for N10). Did you figure out why it wassnt able to transfer the first time?
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
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........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
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...
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
rohanjoshi said:
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
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........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
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...
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
Click to expand...
Click to collapse
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
rohanjoshi said:
...
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
...
Click to expand...
Click to collapse
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.
GedBlake said:
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
woops, I'll get on that!
hello guys when i try to flash the bt my wifi n7 2012 with 4.4.2 (grouper-Nakasi) is in error and do not understand why ... can someone help me?
Code:
Microsoft Windows [Versione 6.1.7601]Copyright (c) 2009 Microsoft Corporation. Tutti i diritti riservati.
C:\Users\Francesco>cd C:\Users\Francesco\Desktop\Nuova cartella\nakasi-kot49h
C:\Users\Francesco\Desktop\Nuova cartella\nakasi-kot49h>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.522s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.758s
Code:
fastboot mode
product name - grouper
variant - grouper
hw versione - er3
bootloader version - 4.23
baseband version - n/a
serial number - xxxxxxxxxxx
singning - not defined yet
lock state - unlocked
forgive my english, but I translated with tranlate
sommoomnia said:
hello guys when i try to flash the bt my wifi n7 2012 with 4.4.2 (grouper-Nakasi) is in error and do not understand why ... can someone help me?
Code:
Microsoft Windows [Versione 6.1.7601]Copyright (c) 2009 Microsoft Corporation. Tutti i diritti riservati.
C:\Users\Francesco>cd C:\Users\Francesco\Desktop\Nuova cartella\nakasi-kot49h
C:\Users\Francesco\Desktop\Nuova cartella\nakasi-kot49h>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.522s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.758s
Code:
fastboot mode
product name - grouper
variant - grouper
hw versione - er3
bootloader version - 4.23
baseband version - n/a
serial number - xxxxxxxxxxx
singning - not defined yet
lock state - unlocked
forgive my english, but I translated with tranlate
Click to expand...
Click to collapse
Hi, sommoomnia...
There known issues fastboot flashing the v4.23 bootloader that ships with **some** versions of Factory Stock, and that are known to cause 'Invalid state/ signature mismatch' errors when fastboot flashed.
For further details, see here... and also here, [WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google.
However, the second half of your output above indicates your Nexus 7 has the v4.23 bootloader already installed... so I'm a little puzzled why you're attempting to flash it again.
Rgrds,
Ged.
GedBlake said:
Hi, sommoomnia...
There known issues fastboot flashing the v4.23 bootloader that ships with **some** versions of Factory Stock, and that are known to cause 'Invalid state/ signature mismatch' errors when fastboot flashed.
For further details, see here... and also here, [WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google.
However, the second half of your output above indicates your Nexus 7 has the v4.23 bootloader already installed... so I'm a little puzzled why you're attempting to flash it again.
Rgrds,
Ged.
Click to expand...
Click to collapse
Today I wanted to do a factory reset and I used to reflash the rom to be sure to start from clean rom and I found the error ....
Nexus 10 getting stuck at splashing screen..
Tried using flash-all.bat (Downloaded from Google developers site ) and
sending 'bootloader' (2203 KB)... OKAY
writing 'bootloader'... FAILED (remote: partition table update fail!)
rebooting into bootloader... OKAY
< waiting for device >
sending 'radio' (45537 KB)... OKAY
writing 'radio'... FAILED (remote: unknown partition...)
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: XXXXXXXXXXX
Baseband Version.....: no modem
Serial Number........: XXXXXXXXXXXX
--------------------------------------------
checking product... FAILED
Device product is '$$$$$$'.
Update requires 'mako'.
Press any key to exit...
Getting the above error ..Please help me what to do as i am unable to start the device.
This happened when i was rooting the nexus 5 ..
Hi,
It looks a bad issue... Probably something went wrong and you lost your partition table . Are you sure your bootloader is unlocked?
~Lord
sidvangala said:
Nexus 10 getting stuck at splashing screen..
Tried using flash-all.bat (Downloaded from Google developers site ) and
sending 'bootloader' (2203 KB)... OKAY
writing 'bootloader'... FAILED (remote: partition table update fail!)
rebooting into bootloader... OKAY
< waiting for device >
sending 'radio' (45537 KB)... OKAY
writing 'radio'... FAILED (remote: unknown partition...)
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: XXXXXXXXXXX
Baseband Version.....: no modem
Serial Number........: XXXXXXXXXXXX
--------------------------------------------
checking product... FAILED
Device product is '$$$$$$'.
Update requires 'mako'.
Press any key to exit...
Getting the above error ..Please help me what to do as i am unable to start the device.
This happened when i was rooting the nexus 5 ..
Click to expand...
Click to collapse
What is the mako all about is that not the code name for the nexus 4 ??
lj50036 nailed it, partition table isn't messed up, it just isn't the same for the mako, which is a good thing your bootloader still runs these checks or you were in for a brick
Be sure to download the manta firmware and try again
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
lj50036 nailed it, partition table isn't messed up, it just isn't the same for the mako, which is a good thing your bootloader still runs these checks or you were in for a brick
Be sure to download the manta firmware and try again
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What made me confused was about the Bootloader: XXXXXXXXX. It made me think that the partition table was messed up, but it probably is just mako... Download the new firmware and make sure it's manta.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1
I didn't see the mako when I first read it either, and you do get a similar message if the partition table were messed up. Actually in a sense it was as the manta and mako have different ones
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
I didn't see the mako when I first read it either, and you do get a similar message if the partition table were messed up. Actually in a sense it was as the manta and mako have different ones
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thx you a pat on the back for me....
I tried to install nakasi-lrx22g (should be Android 5), but the update process complains about boot loader version. So I tried to update the bootloader via "fastboot flash boot" with the enclosed boot loader image. This worked without error message:
fastboot flash boot ./bootloader-grouper-4.23.img
sending 'boot' (2100 KB)...
OKAY [ 0.270s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.385s
, but the boot loader remains 4.18:
FASTBOOT MODE
PRODUCT NAME - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.18
BASEBAND VERSION - N/A
SERIAL NUMBER - ...
SIGNING - not defined yet
LOCK STATE - unlocked
How could that happen? Is the partition write protected?
Addendum: Instead of installing the bootloader from the image I tried to install the one from that thread:
[Q] JWR66Y nakasi factory image bootloader problem
This also was unsuccessful, i.e. bootloader remained 4.18.
Addendum 2: Instead of directly installing the bootloader I replaced the one in the image with that from the mentioned thread, and now the update worked.
This is really (!) strange.
Ahkah said:
I tried to install nakasi-lrx22g (should be Android 5), but the update process complains about boot loader version. So I tried to update the bootloader via "fastboot flash boot" with the enclosed boot loader image. This worked without error message:
fastboot flash boot ./bootloader-grouper-4.23.img
sending 'boot' (2100 KB)...
OKAY [ 0.270s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.385s
, but the boot loader remains 4.18:
FASTBOOT MODE
PRODUCT NAME - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.18
BASEBAND VERSION - N/A
SERIAL NUMBER - ...
SIGNING - not defined yet
LOCK STATE - unlocked
How could that happen? Is the partition write protected?
Addendum: Instead of installing the bootloader from the image I tried to install the one from that thread:
[Q] JWR66Y nakasi factory image bootloader problem
This also was unsuccessful, i.e. bootloader remained 4.18.
Addendum 2: Instead of directly installing the bootloader I replaced the one in the image with that from the mentioned thread, and now the update worked.
This is really (!) strange.
Click to expand...
Click to collapse
Use the version from that post. And the command is fastboot flash bootloader not boot.
riggerman0421 said:
Use the version from that post. And the command is fastboot flash bootloader not boot.
Click to expand...
Click to collapse
So it was finally just a dumb typo. Thanks! And of course the questions remain why fastboot did not respond with an error message when I tried to install the bootloader using a wrong command and why Google's original package failed to be installed.
It didn't give am error because it was flashing an image file(bootloader) to a correctly named partition (boot). The error was yours, flashing the file to the wrong partition. Fastboot was following the instructions you gave it. As for the bootloader file not flashing, it has been broken for a while in the factory image. I guess Google isn't worried about fixing it.