Hi! The story goes like this:
A friend of mine gave me a bricked Galaxy Nexus to resurrect: the phone keeps playing the colors animations and never ends booting up, but I can enter fastboot and recovery modes.
Things I tried:
1) efrant guide to return to stock.
Here is the big problem: after doing the 'fastboot oem unlock', at the bottom it appears in red text 'LOCK STATE - UNLOCKED'. But then I do a 'fastboot reboot-bootloader' and it changes to LOCKED again, so I can't complete the steps because of this. I think this is what is causing all the troubles.
2) Flash JB package with Odin.
3) Flash ICS package with Odin.
This last two completed successfully, but the phone is having the same problem, there were no changes. The bootloader version is always PRIMEKK15.
Any hints? Maybe it's a hardware problem and there's no software solution? It's a shame, because I can access fastboot and recovery, but everything I tried doesn't seem to work.
Big thanks.
seems to me that the unlock token is not sticking somehow. have you tried relocking it right after you unlock it? for example, can you 'fastboot boot customrecovery.img' and enter cwm after you unlock?
sent from my i9250
bk201doesntexist said:
seems to me that the unlock token is not sticking somehow. have you tried relocking it right after you unlock it? for example, can you 'fastboot boot customrecovery.img' and enter cwm after you unlock?
sent from my i9250
Click to expand...
Click to collapse
Yes, if I do:
# fastboot oem unlock
# fastboot boot cwm-recovery.img
It enters CWM just fine. The problems seems to be that the changes are not persistent, or at least that's what it shows the info in the fastboot mode. Even after all the things I flashed, the bootloader never changed.
I will be trying to relock it right after unlocking it and I'll post the results.
Thanks.
envidia said:
Even after all the things I flashed, the bootloader never changed.
Thanks.
Click to expand...
Click to collapse
You can try to use the GALAXY NEXUS TOOLKIT V7.8. It has many helpful features for unlocking, rooting, flashing factory images, or separate radio\bootloader images. User-friendly GUI are included.
Feinar said:
You can try to use the GALAXY NEXUS TOOLKIT V7.8. It has many helpful features for unlocking, rooting, flashing factory images, or separate radio\bootloader images. User-friendly GUI are included.
Click to expand...
Click to collapse
He already knows how to use fastboot. There is no need for him to use a toolkit which does nothing different aside from hide the commands from you...
Guess he have his 10 posts now so he won't post for a while ^^
Feinar said:
You can try to use the GALAXY NEXUS TOOLKIT V7.8. It has many helpful features for unlocking, rooting, flashing factory images, or separate radio\bootloader images. User-friendly GUI are included.
Click to expand...
Click to collapse
And don't recommend toolkits to people asking for help, 3/4 of the time they are clueless, recommending it to them will just make them sink deeper in to a god knows how deep pool of sh*t. No offence to you though, just don't recommend toolkits next time
Thanks guys.
I'm reading that people recommend doing an OMAP flash, but only when the phone is completely dead. I can get to fastboot / Odin mode, is there anything that I should try before doing an OMAP flash?
envidia said:
Thanks guys.
I'm reading that people recommend doing an OMAP flash, but only when the phone is completely dead. I can get to fastboot / Odin mode, is there anything that I should try before doing an OMAP flash?
Click to expand...
Click to collapse
i think we already ran out of options. you could try omapflash... although i still think it's an issue with the unlock token/nand.
bk201doesntexist said:
have you tried relocking it right after you unlock it?
Click to expand...
Click to collapse
I've just tried that and it works as expected.
# fastboot oem unlock
*It says the bootloader is unlocked in the phone display*
# fastboot oem lock
*It says the bootloader is locked again in the phone display*
Then I tried flashing the ICL53F 4.0.2 stock image through fastboot, because it uses the bootloader that I have at the moment. It didn't work, it's still stuck at the animation colors. Look at the results, it all seems ok:
Code:
[B]# ./fastboot oem unlock[/B]
...
OKAY [ 10.102s]
[B]# ./fastboot -w update image-yakju-icl53f.zip[/B]
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: 0149C25E0200A00B
--------------------------------------------
checking product...
OKAY [ 0.007s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.008s]
sending 'boot' (4074 KB)...
OKAY [ 0.436s]
writing 'boot'...
OKAY [ 2.510s]
sending 'recovery' (4406 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 4.459s]
sending 'system' (317594 KB)...
OKAY [ 40.473s]
writing 'system'...
OKAY [1387.576s]
erasing 'userdata'...
OKAY [ 0.035s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [262.626s]
erasing 'cache'...
OKAY [ 0.007s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 15.788s]
rebooting...
finished. total time: 1714.590s
The only thing that caught my attention is the fact that the process lasted almost 29 minutes. I don't know if that's normal.
Follow the steps in my guide here (instead of using the fastboot update command), with the following exception: instead of doing step 10, replace that step with: fastboot erase userdata
efrant said:
Follow the steps in my guide here (instead of using the fastboot update command), with the following exception: instead of doing step 10, replace that step with: fastboot erase userdata
Click to expand...
Click to collapse
I did:
Code:
[B]# ./fastboot oem unlock[/B]
...
OKAY [ 9.623s]
finished. total time: 9.623s
[B]# ./fastboot flash bootloader bootloader-maguro-primekk15.img[/B]
sending 'bootloader' (2308 KB)...
OKAY [ 0.324s]
writing 'bootloader'...
OKAY [ 7.972s]
finished. total time: 8.296s
[B]# ./fastboot flash radio radio-maguro-i9250xxkk6.img[/B]
sending 'radio' (12288 KB)...
OKAY [ 1.739s]
writing 'radio'...
OKAY [ 4.395s]
finished. total time: 6.134s
[B]# ./fastboot flash system image-yakju-icl53f/system.img[/B]
sending 'system' (317594 KB)...
OKAY [ 43.399s]
writing 'system'...
OKAY [1387.456s]
finished. total time: 1430.855s
[B]# ./fastboot erase userdata[/B]
erasing 'userdata'...
OKAY [ 0.033s]
finished. total time: 0.033s
[B]# ./fastboot flash boot image-yakju-icl53f/boot.img[/B]
sending 'boot' (4074 KB)...
OKAY [ 0.568s]
writing 'boot'...
OKAY [ 4.384s]
finished. total time: 4.953s
[B]# ./fastboot flash recovery image-yakju-icl53f/recovery.img[/B]
sending 'recovery' (4406 KB)...
OKAY [ 0.620s]
writing 'recovery'...
OKAY [ 4.458s]
finished. total time: 5.079s
[B]# ./fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.007s]
finished. total time: 0.007s
[B]# ./fastboot reboot[/B]
rebooting...
finished. total time: 0.006s
It isn't working, same result as always.
I'm new to this Android world, so I have to ask: could CWM or similar custom recovery offer some additional method to try? Because I can boot CWM recovery, but I don't know if can do something from there.
Thank you guys.
can we get a logcat of the bootloop?
anyways, if you flash cwm, does it stick? it doesnt, i assume. be reminded that /system/recovery-from-boot.p needs to be renamed or removed, if exists.
imo, using cwm to flash a rom won't do much here, given the current situation.
sent from my i9250
bk201doesntexist said:
can we get a logcat of the bootloop?
anyways, if you flash cwm, does it stick? it doesnt, i assume. be reminded that /system/recovery-from-boot.p needs to be renamed or removed, if exists.
imo, using cwm to flash a rom won't do much here, given the current situation.
Click to expand...
Click to collapse
About the logcat, I've read that you have to use adb, but it never worked for me. When I do:
Code:
[B]# ./adb devices[/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
<empty space here>
I can boot the CWM recovery. If I flash it, it doesn't stick. I don't know how to delete /system/recovery-from-boot.p, do I need adb?
I tried the OMAP flash, then tried to unlock the bootloader and after the fastboot reboot-bootloader, it gets locked again.
I'm reading lots of threads with bricked Galaxy Nexus, but never one with this behavior.
Only thing I can suggest is try fast booting a different bootloader version to a newer one.
http://forum.xda-developers.com/showthread.php?t=1587498
Sent from my Galaxy Nexus
The Gingerbread Man said:
Only thing I can suggest is try fast booting a different bootloader version to a newer one.
http://forum.xda-developers.com/showthread.php?t=1587498
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
it seems it always stays on kk15
sent from my i9250
bk201doesntexist said:
it seems it always stays on kk15
sent from my i9250
Click to expand...
Click to collapse
OK then odd, the other thing I'd suggest is go to the Google factory image website https://developers.google.com/android/nexus/images then using mskips tool kit there is a feature to turn the .IMG into .tar (I think its .tar?) which can then be using in Odin mode instead. Flashing this way is different than fast boot and the Google factory images contain boot loader and radio and obviously a ROM.
Sent from my Galaxy Nexus
envidia said:
About the logcat, I've read that you have to use adb, but it never worked for me. When I do:
Code:
[B]# ./adb devices[/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
<empty space here>
Click to expand...
Click to collapse
That is because your ADB driver is not installed. It seems like you have the fastboot driver installed, but not the ADB driver.
envidia said:
I can boot the CWM recovery. If I flash it, it doesn't stick. I don't know how to delete /system/recovery-from-boot.p, do I need adb?
I tried the OMAP flash, then tried to unlock the bootloader and after the fastboot reboot-bootloader, it gets locked again.
I'm reading lots of threads with bricked Galaxy Nexus, but never one with this behavior.
Click to expand...
Click to collapse
Since you've already tried fastboot, odin and omapflash, I doubt anything else will work. The only other thing I can think of that could possibly work is for flash the bootloader using dd, but I doubt it. Most likely a hardware issue.
The Gingerbread Man said:
OK then odd, the other thing I'd suggest is go to the Google factory image website https://developers.google.com/android/nexus/images then using mskips tool kit there is a feature to turn the .IMG into .tar (I think its .tar?) which can then be using in Odin mode instead. Flashing this way is different than fast boot and the Google factory images contain boot loader and radio and obviously a ROM.
Click to expand...
Click to collapse
Thanks, The Gingerbread Man. I've already tried flashing stock images through Odin and there's no change at all.
efrant said:
That is because your ADB driver is not installed. It seems like you have the fastboot driver installed, but not the ADB driver.
Click to expand...
Click to collapse
I'm on Linux, I thought that if fastboot is working, adb should work as well. I'm trying adb with the phone in fastboot mode, should I try in Odin or recovery mode?
efrant said:
Since you've already tried fastboot, odin and omapflash, I doubt anything else will work. The only other thing I can think of that could possibly work is for flash the bootloader using dd, but I doubt it. Most likely a hardware issue.
Click to expand...
Click to collapse
Let's suppose the problem is the NAND flash memory, is it replaceable? Of course I'm not doing it myself, but I'm thinking if the phone has to be replaced by a new one, or can be repaired.
envidia said:
I'm on Linux, I thought that if fastboot is working, adb should work as well. I'm trying adb with the phone in fastboot mode, should I try in Odin or recovery mode?
Click to expand...
Click to collapse
Oops, forgot you were using linux (so no drivers required). But ADB should not work your device is booted in fastboot mode or odin mode. It will only work when you are booted into recovery or into Android.
envidia said:
Let's suppose the problem is the NAND flash memory, is it replaceable? Of course I'm not doing it myself, but I'm thinking if the phone has to be replaced by a new one, or can be repaired.
Click to expand...
Click to collapse
Not really. You would need to replace the motherboard as a whole.
Related
This is for Re-locking and Un-Rooting the US WIFI Xoom BUILD HWI69 ONLY
This is for use only on the Wifi-Only Xoom HWI69 build. Check your build number before you install!!!
Please note the following information does contain official Motorola images from a non Motorola source. The information in this thread has been tested, however I can not confirm that it will work for every situation. In no way will I or xda-developers.com be held accountable for any damage resulting from using this information. Use the following with extreme caution.
1. Download the necessary files from here:
http://www.android.net/forum/downloads.php?do=file&id=39
2. Unzip the files to the directory you will be running ADB from.
3. Enter the following commands into the command prompt
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
After the final reboot you should be back to stock, Locked and Un-Rooted.
note: If you are using Terminal on a mac your commands should include a ./ before every command like this:
./adb reboot bootloader
Xoom will then reboot into bootloader screen
./fastboot flash boot boot.img
./fastboot flash system system.img
./fastboot flash recovery recovery.img
./fastboot flash userdata userdata.img
./fastboot erase cache
./fastboot oem lock
Credits go to Steady Hawkin on xoomforums.com
first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Last login: Wed May 18 22:11:38 on ttys000
Hooligans:~ Hooligan$ ./adb reboot bootloder
-bash: ./adb: No such file or directory
Hooligans:~ Hooligan$ adb reboot bootloder
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse
HooliganBG said:
first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Click to expand...
Click to collapse
fixed build number, thanks for that! ya i just did it yesterday and worked no problem.
everytime i run commands in terminal on my mac i have to put the ./ or else it wont work, never worked for me just typing it in normally
I just tried this and it works great! Excellent work OP!
After unrooting and unlocking and My 3.1 updates kicked in right away..... I think I will be running stock for a while
I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?
Buddhahb said:
I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?
Click to expand...
Click to collapse
check your build number in settings>about phone, it has to be HWI69 in order for this to work
I have that model. I was just making sure it wouldn't be a problem that I hate flashed the 3.1 update
what format are these imgs in?
I am trying to unyaffs them but it is not the right format
Your trying to what?
The build number does not matter. All that matters is you flash official images for YOUR device. For example the US wifi images on a us wifi device. The same goes for the 3g. Just do not relock the bootloader with out those images flash onto the device.
In a year from now your device could be running ice cream sandwich with who knows what build number. Unlocked bootloader = flash back official images when ever you want.
Sent from my Xoom using Tapatalk
I am trying to get the data out (on my pc)
I lost all the default stuff that come with the xoom.
Does doing the ota to android 3.1 change build number from HWI69 to HMJ37?
worked nice thanks man... sad to say im taking this thing back today to get the less cool looking transformer for 200 dollars less... same thing just looks not as cool... supposedly screen display is better too... thanks again..
yes it does... ur wifi onnly us xoom should have been that to begin with before the ota...
Video for Noobs
Made a video using this Tutorial for anyone interested.
http://www.youtube.com/watch?v=pT8NF-_nLCo
Gave all credit to those it belongs to.
Tried this last night but used HMJ37 instead of HWI69 and got myself into a weird situation where it wouldn't boot (stuck on Dual Core screen). Had to power off and use vol+ to get to fast boot and unlock again.
Is HWI69 the only build that can be oem locked ?
-Matt
Thanks!
Worked perfectly, thank you for taking the time to post this useful thread.
Code:
c:\android-sdk-windows>adb reboot bootloader
* daemon not running. starting it now *
* daemon started successfully *
c:\android-sdk-windows>cd tools
c:\android-sdk-windows\tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 1.039s]
writing 'boot'... OKAY [ 2.139s]
finished. total time: 3.179s
c:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 27.063s]
writing 'system'... OKAY [ 14.166s]
finished. total time: 41.231s
c:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)... OKAY [ 1.427s]
writing 'recovery'... OKAY [ 2.038s]
finished. total time: 3.466s
c:\android-sdk-windows\tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 13.288s]
writing 'userdata'... OKAY [ 21.292s]
finished. total time: 34.582s
c:\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... OKAY [ 1.615s]
finished. total time: 1.616s
c:\android-sdk-windows\tools>fastboot oem lock
... INFO To continue, follow instructions on the d
evice's display...
OKAY [101.907s]
finished. total time: 101.908s
Hello,
i am just thinking i bricked my Galaxy Nexus.
But first i will describe what happened:
My device was running fine with 4.3 Cyanonogenmod Nighlty builds for a few days but yesterday in the car the device suddenly was stuck in a bootloop.
After arriving home i tried to fix that by removing the battery and give it a few minutes.
But my device was stuck in a bootloop after that.
I tried to reflash ROM and RADIO few times but nothing helped.
I was in TWRP Recovery and wanted to get CWM just to rescue some files via USB before flashing stock ROM.
So i got the toolkit and tried to flash a recovery and the script told me all worked, but there seems not to be any recovery on the device anymore.
When i boot into bootloader and select Recovery i am just getting the battery symbol and nothing more happens.
I flashed a stock ROM via toolkit without wiping userdata but this did not help, too.
Now i am stuck with a device that does not seem to have a recovery and does not boot behind the Google Logo.
Also the device only reacts to the power button anymore when on external power via USB wire, not on battery.
Any suggestions how to continue or just rescue my files from the "sdcard" ?
myxor said:
Hello,
i am just thinking i bricked my Galaxy Nexus.
But first i will describe what happened:
My device was running fine with 4.3 Cyanonogenmod Nighlty builds for a few days but yesterday in the car the device suddenly was stuck in a bootloop.
After arriving home i tried to fix that by removing the battery and give it a few minutes.
But my device was stuck in a bootloop after that.
I tried to reflash ROM and RADIO few times but nothing helped.
I was in TWRP Recovery and wanted to get CWM just to rescue some files via USB before flashing stock ROM.
So i got the toolkit and tried to flash a recovery and the script told me all worked, but there seems not to be any recovery on the device anymore.
When i boot into bootloader and select Recovery i am just getting the battery symbol and nothing more happens.
I flashed a stock ROM via toolkit without wiping userdata but this did not help, too.
Now i am stuck with a device that does not seem to have a recovery and does not boot behind the Google Logo.
Also the device only reacts to the power button anymore when on external power via USB wire, not on battery.
Any suggestions how to continue or just rescue my files from the "sdcard" ?
Click to expand...
Click to collapse
Drop the toolkit, learn how to do it proper or stop flashing stuff before you hurt your device.
beekay201 said:
Drop the toolkit, learn how to it proper or stop flashing stuff before you hurt your device.
Click to expand...
Click to collapse
I guess it's already to late
I just tried to install the CWM Recovery via fastboot
D:\gn\adt-bundle-windows-x86_64
sending 'recovery' (6214 KB)...
OKAY [ 0.631s]
writing 'recovery'...
OKAY [ 0.759s]
finished. total time: 1.392s
D:\gn\adt-bundle-windows-x86_64
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
But when i select Recovery from the bootloader menu i only get the charging battery icon.
Anything i can do?
I've never had a similar experience so but from reading several similar topics I will suggest that you flash a factory image. Not a STOCK ROM, but the actual factory image. It *should* re-lock the boot loader and default you to complete stock.Your files will be gone but assuming the files aren't overwritten you can still recover them per the instructions on this thread. As others have suggested, lay off the toolkit. Without it, you will be absolutely sure as to what is going on with your phone. Read, read, read, read before doing anything you're unfamiliar with.
iLeopard said:
I've never had a similar experience so but from reading several similar topics I will suggest that you flash a factory image. Not a STOCK ROM, but the actual factory image. It *should* re-lock the boot loader and default you to complete stock.Your files will be gone but assuming the files aren't overwritten you can still recover them per the instructions on this thread. As others have suggested, lay off the toolkit. Without it, you will be absolutely sure as to what is going on with your phone. Read, read, read, read before doing anything you're unfamiliar with.
Click to expand...
Click to collapse
Thank you for your advices but the results are not what i hoped for:
After flashing the factory image from https://developers.google.com/android/nexus/images#instructions with the following output:
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.236s]
writing 'bootloader'...
OKAY [ 0.605s]
finished. total time: 0.841s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.233s]
writing 'radio'...
OKAY [ 2.590s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: XXXXXXXXXXXXXXXX (censored by author)
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.007s]
sending 'boot' (4376 KB)...
OKAY [ 0.438s]
writing 'boot'...
OKAY [ 0.380s]
sending 'recovery' (4924 KB)...
OKAY [ 0.497s]
writing 'recovery'...
OKAY [ 0.761s]
erasing 'system'...
OKAY [ 0.013s]
sending 'system' (474180 KB)...
OKAY [ 46.800s]
writing 'system'...
OKAY [ 47.830s]
erasing 'userdata'...
OKAY [ 0.550s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [ 25.975s]
erasing 'cache'...
OKAY [ 0.015s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 3.136s]
rebooting...
finished. total time: 126.458s
Press any key to exit...
the device is stuck in the Google Logo now for about 10 Minutes and nothing is happening :crying:
Was this issued using flash-all.bat?
Sent from my Galaxy Nexus using xda app-developers app
myxor said:
Thank you for your advices but the results are not what i hoped for:
After flashing the factory image from https://developers.google.com/android/nexus/images#instructions with the following output:
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.236s]
writing 'bootloader'...
OKAY [ 0.605s]
finished. total time: 0.841s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.233s]
writing 'radio'...
OKAY [ 2.590s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: XXXXXXXXXXXXXXXX (censored by author)
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.007s]
sending 'boot' (4376 KB)...
OKAY [ 0.438s]
writing 'boot'...
OKAY [ 0.380s]
sending 'recovery' (4924 KB)...
OKAY [ 0.497s]
writing 'recovery'...
OKAY [ 0.761s]
erasing 'system'...
OKAY [ 0.013s]
sending 'system' (474180 KB)...
OKAY [ 46.800s]
writing 'system'...
OKAY [ 47.830s]
erasing 'userdata'...
OKAY [ 0.550s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [ 25.975s]
erasing 'cache'...
OKAY [ 0.015s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 3.136s]
rebooting...
finished. total time: 126.458s
Press any key to exit...
the device is stuck in the Google Logo now for about 10 Minutes and nothing is happening :crying:
Click to expand...
Click to collapse
4.3 first bootup times is much slower than previous versions. Let it boot until it reboots itself or something. If after 45min it still going at it, I think you have two options:
- my first suggestion is to return to the bootloader, and follow this thread's first post. No need to reflash bootloader or radio, as far as I can tell, nothing's wrong with those two. Erase, then format all the remaining partitions.
Code:
fastboot erase partition_name
fastboot format partition_name
Flash all the remaining partitions: boot, recovery (a custom recovery if you'd like, beware of 4.3 changes - not sure all the custom recoveries have updated accordingly, check dev section), system, userdata, cache.
Code:
fastboot flash partition /path/to/filename.img
- my second suggestion is that you search of a way to enable adbd, to see whats going on. That might require some extra steps, such as editing init.rc i believe.
Anyways, if you return to the bootloader, and try to
Code:
fastboot boot /path/to/cwm_or_twrp.img
What does it do? Can you use your custom recovery now?
beekay201 said:
4.3 first bootup times is much slower than previous versions. Let it boot until it reboots itself or something. If after 45min it still going at it, I think you have two options:
- my first suggestion is to return to the bootloader, and follow this thread's first post. No need to reflash bootloader or radio, as far as I can tell, nothing's wrong with those two. Erase, then format all the remaining partitions.
Code:
fastboot erase partition_name
fastboot format partition_name
Flash all the remaining partitions: boot, recovery (a custom recovery if you'd like, beware of 4.3 changes - not sure all the custom recoveries have updated accordingly, check dev section), system, userdata, cache.
Code:
fastboot flash partition /path/to/filename.img
- my second suggestion is that you search of a way to enable adbd, to see whats going on. That might require some extra steps, such as editing init.rc i believe.
Anyways, if you return to the bootloader, and try to
Code:
fastboot boot /path/to/cwm_or_twrp.img
What does it do? Can you use your custom recovery now?
Click to expand...
Click to collapse
I ran through the linked post and erased + formated all possible partitions.
Is it normal that o can not format some partitions like the recovery partition?
Code:
>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.009s
After that i flashed the partitions once by once per
Code:
fastboot flash partitions /path/file.img
with the files from the factory image.
Sadly no boot possible.
Then i tried to boot my recovery by
Code:
fastboot boot /path/to/cwm_or_twrp.img
but it happens the same as before:
after selecting to boot into recovery from fastboot mode the google logo appears for a few seconds then the screens goes black and returns with the battery charging symbol.
After turning the phone off and booting again into fastboot mode i can read in red letters: "FASTBOOT MODE - NO BOOT OR RECOVERY IMG".
This stays the same after flashing a recovery image via fastboot :crying:
myxor said:
I ran through the linked post and erased + formated all possible partitions.
Is it normal that o can not format some partitions like the recovery partition?
Code:
>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.009s
After that i flashed the partitions once by once per
Code:
fastboot flash partitions /path/file.img
with the files from the factory image.
Sadly no boot possible.
Then i tried to boot my recovery by
Code:
fastboot boot /path/to/cwm_or_twrp.img
but it happens the same as before:
after selecting to boot into recovery from fastboot mode the google logo appears for a few seconds then the screens goes black and returns with the battery charging symbol.
After turning the phone off and booting again into fastboot mode i can read in red letters: "FASTBOOT MODE - NO BOOT OR RECOVERY IMG".
This stays the same after flashing a recovery image via fastboot :crying:
Click to expand...
Click to collapse
Use omapflash to restore your bootloader. See this thread's post with useful links. http://forum.xda-developers.com/showthread.php?t=1812959
I sent in the device to the repair and got it back a few days ago.
Some "broken parts" were changed and i got a new battery.
Now my Galaxy Nexus works again like a charm
Don't really know what parts were broken but it seemed that it was a hardware failure.
Thanks to everyone who helped! :good:
I apologize for my n00b-ness. I went to Windows Phone (yeah, go ahead and laugh) for a little over a year, and am somewhat out of the rooting scene.
So I installed the TWRP 2.7.0.3 recovery based on the thread in this sub-forum here:
http://forum.xda-developers.com/showthread.php?t=2698134
Everything appears to have worked:
Code:
C:\android-sdk\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.247s]
finished. total time: 0.247s
C:\android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (12496 KB)...
OKAY [ 1.212s]
writing 'recovery'...
OKAY [ 0.763s]
finished. total time: 1.974s
C:\android-sdk\sdk\platform-tools>
I'm not sure what to do from here. When my phone boots, I hold power to reboot, and I don't see any "reboot into recovery" option like I've seen on past phones. Is there another way I should access recovery so that I can finish rooting my phone? Or should flashing TWRP have effectively rooted it?
Thanks for any help.
ChodeNode said:
I apologize for my n00b-ness. I went to Windows Phone (yeah, go ahead and laugh) for a little over a year, and am somewhat out of the rooting scene.
So I installed the TWRP 2.7.0.3 recovery based on the thread in this sub-forum here:
http://forum.xda-developers.com/showthread.php?t=2698134
Everything appears to have worked:
Code:
C:\android-sdk\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.247s]
finished. total time: 0.247s
C:\android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (12496 KB)...
OKAY [ 1.212s]
writing 'recovery'...
OKAY [ 0.763s]
finished. total time: 1.974s
C:\android-sdk\sdk\platform-tools>
I'm not sure what to do from here. When my phone boots, I hold power to reboot, and I don't see any "reboot into recovery" option like I've seen on past phones. Is there another way I should access recovery so that I can finish rooting my phone? Or should flashing TWRP have effectively rooted it?
Thanks for any help.
Click to expand...
Click to collapse
Press power restart when it goes off hold power volume down
Or download twrp app from play store
ChodeNode said:
I apologize for my n00b-ness. I went to Windows Phone (yeah, go ahead and laugh) for a little over a year, and am somewhat out of the rooting scene.
So I installed the TWRP 2.7.0.3 recovery based on the thread in this sub-forum here:
http://forum.xda-developers.com/showthread.php?t=2698134
Everything appears to have worked:
Code:
C:\android-sdk\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.247s]
finished. total time: 0.247s
C:\android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (12496 KB)...
OKAY [ 1.212s]
writing 'recovery'...
OKAY [ 0.763s]
finished. total time: 1.974s
C:\android-sdk\sdk\platform-tools>
I'm not sure what to do from here. When my phone boots, I hold power to reboot, and I don't see any "reboot into recovery" option like I've seen on past phones. Is there another way I should access recovery so that I can finish rooting my phone? Or should flashing TWRP have effectively rooted it?
Thanks for any help.
Click to expand...
Click to collapse
Why don't you use one of the toolboxes:
http://forum.xda-developers.com/showthread.php?t=2699065
b0gd4n said:
Why don't you use one of the toolboxes:
http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
Cause toolkits are lazy and it should be encouraged to do everything manually where possible so that you understand what's actually happening so you have the knowledge to fix any possible issues
Just my 2p...
It appears the issue was my n00bness. I assumed the hboot menu would be replaced with the recovery screen. Didn't see the recovery option there in the list. Of course I use that menu item and I'm good to go.
Yeah - I'm dumb.
Hey guys, I'd love anyone's opinion on this as this is the first time something like this has happened to be.
Was using the tablet and noticed that the WiFi wouldn't turn back on. Decided to restart. No more start up and stuck on Google logo indefinitely.
Can get into Bootloader
Computer recognizes the Nexus 7 but thats about it
Cannot get into recovery, frozen screen
Fastboot is unrecognizable
Cannot ADB anything
Tried to use Toolkit to flash OTA Google update to no avail
Code:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.652s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
sending 'radio' (76038 KB)...
OKAY [ 2.465s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 92.586s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.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-03.14
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 07927f06
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-03.14'.
Update requires 'FLO-04.02'.
finished. total time: 0.078s
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...
Is there anything that can be done or am I SOL?
The tablet is still under warranty but it was running custom ROM with an unlocked bootloader, so I'm totally screwed?
Hi mate. exactly the same happened to me few days ago, in fact I came here to open the same topic.
I tried flashing stock image using Nexus toolkit, see the progress but wouldn't load further the google logo. Tried loading the custom recovery, but when I do so from the tool fastboot on my Nexus freezes.
Tried flashing clockwork recovery and TWRP manually but it stays on stock bootloader screen and if I reboot it goes back to the stock bootloader screen (the one with laying android)
I was rooted with stock 4.4.3
@tecz0r, based on the screenshot and the log you posted, have you tried relocking and unlocking the bootloader? See if it helps.
Maverick-DBZ- said:
@tecz0r, based on the screenshot and the log you posted, have you tried relocking and unlocking the bootloader? See if it helps.
Click to expand...
Click to collapse
Just tried that, was able to lock back. Then tried selecting the recovery mode but that just restarted and then jut stayed with the google logo. Was then able to unlock again with a prompt on the device whether or not I would like to unlock but that did not help.
---------- Post added at 03:04 PM ---------- Previous post was at 02:09 PM ----------
Ok, so I was able to boot with TWPR but for some reason touch screen wouldn't work. When trying to boot with Philz or Clockwork bootloader just freezes
When you use the below command
Code:
fastboot devices
Does your device serial number show up? I'm pretty sure it does, since you're able to re-lock and unlock bootloader. I'm guessing you're using wugfresh toolkit on 64 bit windows.
Try to downgrade to JB 4.3, if this works, you can update to 4.4.3 via OTA.
https://developers.google.com/android/nexus/images#razorg
Download the JB 4.3 image above and extract all files to
C:\Program Files (x86)\WugFresh Development\data
Run the below commends manually in a dos prompt.
Code:
cd C:\Program Files (x86)\WugFresh Development\data
fastboot flash bootloader bootloader-deb-flo-03.14.img
fastboot reboot-bootloader
fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
fastboot reboot-bootloader
fastboot update image-razorg-JLS36C.zip
Then boot to recovery and factory reset.
Reboot tablet and hope for the best.
Maverick-DBZ- said:
When you use the below command
Code:
fastboot devices
Does your device serial number show up? I'm pretty sure it does, since you're able to re-lock and unlock bootloader. I'm guessing you're using wugfresh toolkit on 64 bit windows.
Try to downgrade to JB 4.3, if this works, you can update to 4.4.3 via OTA.
https://developers.google.com/android/nexus/images#razorg
Download the JB 4.3 image above and extract all files to
C:\Program Files (x86)\WugFresh Development\data
Run the below commends manually in a dos prompt.
Code:
cd C:\Program Files (x86)\WugFresh Development\data
fastboot flash bootloader bootloader-deb-flo-03.14.img
fastboot reboot-bootloader
fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
fastboot reboot-bootloader
fastboot update image-razorg-JLS36C.zip
Then boot to recovery and factory reset.
Reboot tablet and hope for the best.
Click to expand...
Click to collapse
Thanks for the tip. Happy to say that I was able to RELOCK the bootloader so atleast I have a better chance at Asus honoring the warranty.
Weird thing: couldn't get the bootloader UNLOCKED. It just hangs for about 15 minutes and then says FAILED.
At this point, I simply cannot get the bootloader to write anything or replace current bootloader. Never heard of this issue. No idea how it can be resolved without RMA.
Yeah, looks like it's gone. Good luck with the RMA.
Hey gang!
So I got it to work! yay. tried everything mentioned here, but no luck. Last thing I've tried was manually flashing 4.3. Nothing
Today a guy from the office took it apart and disconnected the battery. Connected it back and booya it's loading.
Surprisingly it loaded 4.3 so flashing was successful but something was preventing it from loading.
Nice to be back, I was kind of getting tired of using my phone for browsing internets from my couch
Interesting, reminds me of a similar problem with the nexus 4 called the red light of death.
Glad it's working fine again.
Greetings,
So I suppose I made the mistake of not locking the bootloader before flashing the factory NRD91D image. Current situation is that my Pixel C is reporting unlocked bootloader but I can't flash TWRP. Fastboot indicates a successful recovery flash but when booting into recovery it comes up with the sad little dead android and "No command".
My goal is to get rooted N, obviously. TWRP would be nice.
I think I read somewhere that I can:
1. Flash factory 6.0.1
2. Flash TWRP
3. Wipe everything
4. Root
5. Lock bootloader
6. Flash factory OTA to N using Flashfire with SuperSU Injection.
I've been trying adb fastboot and I sprung for skipsoft hoping it could magically bail me out but no luck.
Anybody else stuck in this situation? Does anybody have 7.0.0 rooted with TWRP? If so what steps did you use?
Thanks in advance for any help or advice.
I been using Skipsoft and its saying the device is unlocked. The bootloader screen says its unlocked at the bottom, but also says no recovery OS is corrupted. I've tried to lock it with oem lock/unlock as well as flashing unlock. The system does not report errors while unlocking/locking, but I'm unable to flash anything.
sending 'bootloader' (16384 KB)...
OKAY [ 0.423s]
writing 'bootloader'...
FAILED (remote: unsupported command)
or
$ fastboot boot twrp.img
creating boot image...
creating boot image - 13035520 bytes
downloading 'boot.img'...
OKAY [ 0.388s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.391s
This happens on my Mac and Windows machine (in case someone thinks its a driver issue)
type fastboot flashing/flash lock ( try flash or flashing)
wait that user data partition is regolar formatted
and now you are able of unlock and wait for userdata formatted
now you can flash rom
Alessandro999 said:
type fastboot flashing/flash lock ( try flash or flashing)
wait that user data partition is regolar formatted
and now you are able of unlock and wait for userdata formatted
now you can flash rom
Click to expand...
Click to collapse
Thank for replying.
Keep in mind When I click [Reboot into Android Recovery] it only reboots to the bootloader I've included a picture of that.
jatilq$ ./fastboot flashing lock
...
OKAY [ 3.963s]
finished. total time: 3.963s
jatilq$ ./fastboot flashing unlock
...
OKAY [ 2.306s]
finished. total time: 2.306s
jatilq$ ./fastboot boot twrp.img
< waiting for any device >
creating boot image...
creating boot image - 13035520 bytes
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.372s
jatilq$ ./fastboot oem lock
...
OKAY [ 23.284s]
finished. total time: 23.284s
jatilq$ ./fastboot oem unlock
...
OKAY [ 2.683s]
finished. total time: 2.683s
jatilq$ ./fastboot flash bootloader bootloader-dragon-google_smaug.7900.67.0.img
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.480s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.482s
It finishes about 5 min after 'archive does not contain system.sig
jatilq$ ./fastboot -w update image-ryu-n2g48b.zip
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 57825820672
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14117632
Block groups: 431
Reserved block group size: 1024
Created filesystem with 11/3530752 inodes and 267682/14117632 blocks
wiping cache...
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
--------------------------------------------
Bootloader Version...: Google_Smaug.7900.50.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking partition-size:system...
OKAY [ 0.016s]
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.029s
./fastboot flash boot recovery.img
target reported max download size of 268435456 bytes
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.001s
These are most of the commands I've tried. This is on my mac. The windows machine SKipSoft will say it's unlocked, but during flashing will throw back that it's locked (bootloader reports unlocked)
I included photos to show it does say it locks/unlocks.
I contacted Google and that was a disturbing experience. Both times you can tell support is reading from a script. They both promised someone from 2 tier would contact me, so far nothing. I'm willing to pay to have the thing repaired, but sadly you need the 2nd tier person to call you to even find out if that's possible.
ok but you must wait that after lock/unlock bootloader the userdata is formatted automaticcaly!
reboot into fastboot
type fastboot flashing/flash lock and waith that userdata is auto formatted
flash stock firmware
if you dont do this the error still persist due to damaged userdata partition
---------- Post added at 10:17 AM ---------- Previous post was at 10:07 AM ----------
i want help you .... i ve got this error last month and i fixed with this.... follow this tut:
- use a pc with windows 7 installed
-download google usb driver ( adb and fastboot) latest
reboot device into bootloader mode , connect it and open terminal and use fastboot flash/ flashing lock ( now pixel c will automatic format userdata partition corrupted)
after the process is ended( 5/10 minutes) you are able to back to stock ... dont try to flash tpwr , first i reccomend factory image 7.1.2 august for pixel c
after flash stock reboot configure the sofware , go on setting and if the device is already unlock reboot info fastboot and flash tpwr ( fastboot flash recovery recoveryname.img)
i reccoment latest stable tpwr
actually i have this and i have resurrection remix latest + f2fs data cache+ xceed foolowsi kernel with fsync off, zen scheduler
very smooth and fast
every time you lock/unlock bootloader you must wait that userdata is formatted by device ( this during 5/10 minutes usually)
I pasted the output before to show that I've done as you suggested several times. It says its unlocked after the lock/unlock process (look at my previous commands). Once you input those commands, you hit power to say yes and the device will reboot. The below process is from SkipSoft Android Toolkit to better explain the issue as explained in the title of this thread.
Are you ready to start? Type y[yes] or n[no]:y
Device mode detected: Fastboot Mode
Device Serial Number:
Device Bootloader State: Locked
When prompted, Press the Power button on the device to Unlock the Bootloader.
If it is already unlocked then this will just be skipped and your device will not
be wiped. After unlocking the device will reboot to recovery to erase the device.
Sending flashing unlock command to device..
Device bootloader is already unlocked so no data will be wiped
Rebooting back to Android..
rebooting...
finished. total time: -0.000s
Press any key to return to the Main Menu..
jatilq said:
erasing 'boot'...
FAILED (remote: unsupported command)
Click to expand...
Click to collapse
I had this issue and fixed it with fwtool
boot into recovery, then
Code:
adb shell
fwtool vbnv write dev_boot_fastboot_full_cap 1
jatilq said:
Thank for replying.
Keep in mind When I click [Reboot into Android Recovery] it only reboots to the bootloader I've included a picture of that.
jatilq$ ./fastboot flashing lock
...
OKAY [ 3.963s]
finished. total time: 3.963s
jatilq$ ./fastboot flashing unlock
...
OKAY [ 2.306s]
finished. total time: 2.306s
jatilq$ ./fastboot boot twrp.img
< waiting for any device >
creating boot image...
creating boot image - 13035520 bytes
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.372s
jatilq$ ./fastboot oem lock
...
OKAY [ 23.284s]
finished. total time: 23.284s
jatilq$ ./fastboot oem unlock
...
OKAY [ 2.683s]
finished. total time: 2.683s
jatilq$ ./fastboot flash bootloader bootloader-dragon-google_smaug.7900.67.0.img
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.480s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.482s
It finishes about 5 min after 'archive does not contain system.sig
jatilq$ ./fastboot -w update image-ryu-n2g48b.zip
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 57825820672
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14117632
Block groups: 431
Reserved block group size: 1024
Created filesystem with 11/3530752 inodes and 267682/14117632 blocks
wiping cache...
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
--------------------------------------------
Bootloader Version...: Google_Smaug.7900.50.0
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking partition-size:system...
OKAY [ 0.016s]
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.029s
./fastboot flash boot recovery.img
target reported max download size of 268435456 bytes
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.001s
These are most of the commands I've tried. This is on my mac. The windows machine SKipSoft will say it's unlocked, but during flashing will throw back that it's locked (bootloader reports unlocked)
I included photos to show it does say it locks/unlocks.
I contacted Google and that was a disturbing experience. Both times you can tell support is reading from a script. They both promised someone from 2 tier would contact me, so far nothing. I'm willing to pay to have the thing repaired, but sadly you need the 2nd tier person to call you to even find out if that's possible.
Click to expand...
Click to collapse
Hello,
I have the exact error that you show in the screenshots. I follow your steps and I´m stuck with the same problem. Finally you can solve the problem? I´m totally frustrated withg this tablet and need some help.
Thanks in advance.
Istvan_86 said:
Hello,
I have the exact error that you show in the screenshots. I follow your steps and I´m stuck with the same problem. Finally you can solve the problem? I´m totally frustrated withg this tablet and need some help.
Thanks in advance.
Click to expand...
Click to collapse
Unfortunately I jumped through many hoops with Google before then sent me a one time replacement. I sold the tablet and now I'm on a Samsung Galaxy Tab3.
jatilq said:
Unfortunately I jumped through many hoops with Google before then sent me a one time replacement. I sold the tablet and now I'm on a Samsung Galaxy Tab3.
Click to expand...
Click to collapse
Hello and thanks for your answer. So basically I must contact Google as you did?
I think that I'm totally done with this tablet......
Istvan_86 said:
Hello and thanks for your answer. So basically I must contact Google as you did?
I think that I'm totally done with this tablet......
Click to expand...
Click to collapse
As I said you will have to jump through many hoops. They will want you to email support, then you have to wait for a call back. Expect no one to be able to help you, even though they will keep bouncing you around. I'm not sure if its 100% guarantee they will send a replacement after a few contacts. If they do send you one, prepare to have them hold around $550 for the refurbished unit to be sent and the old one returned to them. I sold the new one as fast as I could on swappa, because of the lack of recovery options for the device and the messed up unlock/lock flag error that this thread is talking about.
Using fwtool command worked beautifully
xavierbutt said:
I had this issue and fixed it with fwtool
boot into recovery, then
Code:
adb shell
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
I had a situation where I locked and unlocked in fastboot and still had TWRP recovery installed so the OS protection kicked in and prevented me from booting up normally.
I booted into TWRP recovery where TWRP has built in root access.
I copied the fwtool to the SDcard while the tablet was booted up normally using the PC but, if you can't boot up, ADB push command from a PC would have also placed the fwtool onto the tablet sdcard (adb push fwtool /sdcard).
I used the command adb shell and thus was sitting on the sdcard root where the fwtool was placed. I issued the fwtool command directly from the sdcard location. I did not copy the fwtool to any place else.
adb shell
fwtool vbnv write dev_boot_fastboot_full_cap 1
The command was successful and, I was then able to have full flash access back.
Regards galearned
Thanks @galearned your instruction saved me! Because I didn't get adb to work I used the terminal of TWRP and it worked!
---------- Post added at 09:54 PM ---------- Previous post was at 09:54 PM ----------
Thanks @galearned your instruction saved me! Because I didn't get adb to work I used the terminal of TWRP and it worked!
Thanks @galearned greatful my pixel c is worked again
---------- Post added at 03:36 PM ---------- Previous post was at 03:36 PM ----------
Thanks @galearned greatful my pixel c is worked again
Sorry for the Resurrection. Can somebody explain how they fixed this, I have the same situation exactly. Access to TWRP and fastboot etc, but the dreaded FAILED (remote: unsupported command) stops me in my tracks. I can only lock and unlock the bootloader.