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.
Related
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.
I was trying out the Android L preview, and decided that I've had my fun and wanted to go back to the ROM I was using. I booted into recovery, and noticed that the stock recovery had been flashed. So, I downloadeed the lasted TWRP and flashed it through fastboot. When I tried to boot into recovery again, it froze at the Google screen. Since I already had everything backed up, I decided to just flash the stock image and try again. This is where the real trouble begins. The flash failed (output below), and now I can't boot into android as well as recovery. I tried a few different images (all from the official site, all marked razor), as well as the Nexus Root Toolkit, and all give me the same error(s).
So, how bad did I mess up?
Code:
C:\Android\razor-ktu84p>fastboot flash bootloader bootloader-flo-flo-04.02.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.135s]
writing 'bootloader'...
FAILED (remote: Signature mismatched!!!)
finished. total time: 1.024s
C:\Android\razor-ktu84p>fastboot -w update image-razor-ktu84p.zip
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: 13052653568
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3186683
Block groups: 98
Reserved block group size: 783
Created filesystem with 11/798112 inodes and 90699/3186683 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........: 09f8f0db
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.006s]
sending 'boot' (7050 KB)...
OKAY [ 0.234s]
writing 'boot'...
OKAY [ 0.308s]
sending 'recovery' (7598 KB)...
OKAY [ 0.256s]
writing 'recovery'...
OKAY [ 0.340s]
erasing 'system'...
OKAY [ 0.126s]
sending 'system' (736772 KB)...
OKAY [ 23.632s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 25.676s
That error is usually due to an incompatible fastboot, first try doing a: fastboot erase system
...then try to flash system.img manually again.
Make sure you have the newest fastboot, one that is new as Android L bootloader.
NOTE: DO NOT erase bootloader! This will hardbrick you.
BTW, this is one of the reasons why I use multirom!
mdamaged said:
That error is usually due to an incompatible fastboot, first try doing a: fastboot erase system
...then try to flash system.img manually again.
Make sure you have the newest fastboot, one that is new as Android L bootloader.
NOTE: DO NOT erase bootloader! This will hardbrick you.
BTW, this is one of the reasons why I use multirom!
Click to expand...
Click to collapse
The only img file I have is the bootloader. Is what what you mean?
Also, that seems like a tool I should really have.
StormConjurer said:
The only img file I have is the bootloader. Is what what you mean?
Also, that seems like a tool I should really have.
Click to expand...
Click to collapse
I assume you have the factory image for your old rom, in that package there is a zip file, if you extract it, you will find, among others, a img file named system.img. This is one of the files that is failing to flash.
The bootloader image is failing to flash because it is older than the one that is on there now (the Android L one), so fastboot does not recognize that new Android L bootloader because it expects one of the pre-L bootloaders, so you may have to grab the developers SDK and use that fastboot so it will recognize the newer bootloader.
mdamaged said:
I assume you have the factory image for your old rom, in that package there is a zip file, if you extract it, you will find, among others, a img file named system.img. This is one of the files that is failing to flash.
The bootloader image is failing to flash because it is older than the one that is on there now (the Android L one), so fastboot does not recognize that new Android L bootloader because it expects one of the pre-L bootloaders, so you may have to grab the developers SDK and use that fastboot so it will recognize the newer bootloader.
Click to expand...
Click to collapse
I installed the SDK platform for Android L through the SDK manager, but I'm still getting the exact same error.
I suppose it's also worth mentioning that even if I try to flash the L preview, I still get the same error.
StormConjurer said:
I installed the SDK platform for Android L through the SDK manager, but I'm still getting the exact same error.
I suppose it's also worth mentioning that even if I try to flash the L preview, I still get the same error.
Click to expand...
Click to collapse
Well, have you tried this? http://forum.xda-developers.com/showthread.php?t=2381582
Read the whole OP, you can and should obviously skip the relocking of the bootloader.
Try the Recovery_Nexus7.bat first, if that fails then goto the Dead_Nexus7.bat.
It probably will get you nowhere, but it's worth a shot, obviously if it works, it will wipe everything and put it back to factory.
I solved this simply... By using Nexus Root Toolkit and using Flash Stock and Unroot. Went back to 4.4.4, but you can flash back to any version this way. It will download the ROM you want and flash it with you I having to do basically nothing.
If you are in a boot loop, there's an option for that right under the flash stock and unroot option.
Sorry for the absence. Had a busy few days.
mdamaged said:
Well, have you tried this? http://forum.xda-developers.com/showthread.php?t=2381582
Read the whole OP, you can and should obviously skip the relocking of the bootloader.
Try the Recovery_Nexus7.bat first, if that fails then goto the Dead_Nexus7.bat.
It probably will get you nowhere, but it's worth a shot, obviously if it works, it will wipe everything and put it back to factory.
Click to expand...
Click to collapse
Nope, same results as before.
mhannigan said:
I solved this simply... By using Nexus Root Toolkit and using Flash Stock and Unroot. Went back to 4.4.4, but you can flash back to any version this way. It will download the ROM you want and flash it with you I having to do basically nothing.
If you are in a boot loop, there's an option for that right under the flash stock and unroot option.
Click to expand...
Click to collapse
Like I said in the first post, Nexus Root Toolkit is one of the methods I tried. There's an option to force flash, but I've been trying to avoid that, since it warns of hard bricking the device. I'm quickly running out of options though.
Update: Tried again with force mode turned on. No change in the results.
Hey, I haven't rooted my phone in years, and thought I'd try it to goof around with some stuff. When thinking of backing it up, I thought I had everything off of it that I cared about, only to realize afterwards that I don't have my recent videos of my child backed up.
1. I allowed for unlocking in dev options
2. Boot into fastboot mode
3. Flashed recovery TWRP 3.0.2 bullhead
4. Boot into recovery
TWRP asked me for my pattern to unlock my phone. I gave it the correct pattern, and it keeps saying that it's wrong and can't unencrypt. I gave up on flashing superSU since I couldn't boot, and now my phone won't boot.
I've tried flashing an older TWRP on (2.8.7.2) to try to get things back up and running, but no. Any help would be appreciated!
spierce7 said:
1. I allowed for unlocking in dev options
2. Boot into fastboot mode
Click to expand...
Click to collapse
Did you forget to list a step you did like
fastboot oem unlock
That step usually warns you that it is wiping your user data.
If you want to get it to boot, I would do
fastboot erase user
fastboot format user
fastboot erase cache
fastboot format cache
Although I wouldn't do that until you are sure what happened in case there is a remote chance your stuff is still there.
sfhub said:
Did you forget to list a step you did like
fastboot oem unlock
Click to expand...
Click to collapse
I ran
Code:
fastboot flashing unlock
In TWRP, in the backup option it still shows that I have several 26 GB in my data partition. I'm having a hard time finding it's location in the adb shell though so I can pull the files.
So that will get my device booting again? What if I wanted to get it booting again rooted?
spierce7 said:
I ran
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
And you don't recall it warning you on the phone that your user data would be erased, forcing you to accept the prompt on the phone?
spierce7 said:
In TWRP, in the backup option it still shows that I have several 26 GB in my data partition. I'm having a hard time finding it's location in the adb shell though so I can pull the files.
So that will get my device booting again? What if I wanted to get it booting again rooted?
Click to expand...
Click to collapse
If TWRP says you have 26GB in your data partition available, then your data partition is probably empty.
I can't tell you 100% that will get you booting because I'm unsure of your exact problem.
I can tell you that one reason for the boot hang is if your user partition is erased but not formatted properly. What I suggested would fix that potential problem.
It doesn't seem like you'll lose any additional data you haven't already lost from the fastboot flashing unlock so it is worth a try.
I think the videos you were trying to retrieve are gone though from the fastboot flashing unlock forced factory reset.
BTW are you working with Android N or Marshmallow (6.0.1)? TWRP decryption doesn't work with Android N.
sfhub said:
And you don't recall it warning you on the phone that your user data would be erased, forcing you to accept the prompt on the phone?
Click to expand...
Click to collapse
Honestly I don't remember at this point. If you're saying that it happens, then it must have happened, and I must be an idiot.
sfhub said:
If TWRP says you have 26GB in your data partition available, then your data partition is probably empty.
Click to expand...
Click to collapse
On the backup screen it says by data partition is 26019MB. I was interpreting that it was saying thats' how much data I have to back up. I guess your right, that it's not confirming that the data is there.
sfhub said:
BTW are you working with Android N or Marshmallow (6.0.1)? TWRP decryption doesn't work with Android N
Click to expand...
Click to collapse
Stock Android 6.0.1
sfhub said:
fastboot erase user
fastboot format user
fastboot erase cache
fastboot format cache
Click to expand...
Click to collapse
I gave up and decided the data probably wasn't there.
I'm trying to get my phone working again as root. I'm seeing 2 messages: a orange one that says my data might be corrupt, that's more of a warning, and a red one after running the super user script provided by twrp. I see the red one every time I try to boot.
After that I ran the commands you gave me. Here are the results:
Code:
spierce7-mbp:~ spierce7$ fastboot erase user
erasing 'user'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.020s
spierce7-mbp:~ spierce7$ fastboot format user
Formatting is not supported for file system with type ''.
spierce7-mbp:~ spierce7$ fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.076s]
finished. total time: 0.076s
spierce7-mbp:~ spierce7$ fastboot format cache
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.063s]
sending 'cache' (5688 KB)...
OKAY [ 0.232s]
writing 'cache'...
OKAY [ 0.061s]
finished. total time: 0.355s
Two questions:
1. How do I get my phone working again?
2. How do I get my phone rooted properly so that this all wasn't for nothing?
There is no partition labeled "user", type "userdata" instead.
przemcio510 said:
There is no partition labeled "user", type "userdata" instead.
Click to expand...
Click to collapse
Code:
spierce7-mbp:~ spierce7$ fastboot format userdata
Creating filesystem with parameters:
Size: 27283927040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6661115
Block groups: 204
Reserved block group size: 1024
Created filesystem with 11/1667904 inodes and 148720/6661115 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.426s]
sending 'userdata' (138993 KB)...
OKAY [ 3.819s]
writing 'userdata'...
OKAY [ 1.333s]
finished. total time: 5.578s
Good call.
So I'm still seeing the red "Your phone is corrupted", however my phone tries to boot again, however it still seems to be stuck on the boot animation. Not sure where to go from here.
Flash stock boot and vendor images, then in TWRP flash latest SuperSU.
przemcio510 said:
Flash stock boot and vendor images, then in TWRP flash latest SuperSU.
Click to expand...
Click to collapse
How do I do that? Where do I get the stock boot and vendor images from?
You can get latest image from here: https://dl.google.com/dl/android/aosp/bullhead-mtc19z-factory-9f649f91.tgz (this is stock Google firmware labeled MTC19Z from July)
After downloading, extract the archive, and run flash-all.bat (this script will flash all of the images for you, including data wipe, which can be disabled by removing -w parameter from the script).
Then, flash TWRP, boot into it and from there flash SuperSU zip.
przemcio510 said:
You can get latest image from here: https://dl.google.com/dl/android/aosp/bullhead-mtc19z-factory-9f649f91.tgz (this is stock Google firmware labeled MTC19Z from July)
After downloading, extract the archive, and run flash-all.bat (this script will flash all of the images for you, including data wipe, which can be disabled by removing -w parameter from the script).
Then, flash TWRP, boot into it and from there flash SuperSU zip.
Click to expand...
Click to collapse
I was able to boot into my phone following your instructions. Thank you very much. I'll try rooting my phone again after all the apps are restored.
It also seems that the auto backup on Google's "Photos" app saved all my pictures and videos. Thank you very much for your help. I really appreciate it
przemcio510 said:
There is no partition labeled "user", type "userdata" instead.
Click to expand...
Click to collapse
Thanks for correcting. Going by memory but it isn't what it used to be.
Thanks everyone . I was able to get phone back in working order with root.
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.
I'm not new to flashing the images... But Jesus Christ there's a lot going on with the pixel... There's not just a system, vendor, boot, recovery, and cache IMG now... There's a ****load and I'm not sure how to flash them... And when I run the flash all.bat I keep getting an error during the flash and it just pauses... Same goes for the skipsoft tool. Anyone know how to flash these?
Drivers. Search on how to verify your drivers are up to date and installed.
Am I able to flash the images separately though? I do I have to use the flash all script?
swapavi said:
Am I able to flash the images separately though? I do I have to use the flash all script?
Click to expand...
Click to collapse
Not usually.
And some dev's hate the bat due to Windows being stupid sometimes.
Many folks will flash individual files one at a time.
I however, am unfamiliar with the Pixel XL partition setup too, so I would totally wait for a higher level dev to come along and answer before I do anything.
I actually posted a similar question in the factory images thread over on the development sub forum for Pixel XL.
I am also having issue flashing the marlin-nde63p using the flash-all.bat with the 128GB Pixel XL phone from google. It keeps erroring out with the following [FAILED (remote: partition [boota] doesn't exist)]. Anyone know how to fix this?
C:\pixelxl\marlin-nde63p>
C:\pixelxl\marlin-nde63p>flash-all
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.823s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.046s]
finished. total time: 1.877s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.018s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.349s]
writing 'radioa'...
OKAY [ 0.895s]
finished. total time: 2.251s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.018s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........:XXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.047s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boota' (26481 KB)...
OKAY [ 0.689s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.156s
Press any key to exit...
Ok I literally just did this because I messed up my pixel xl 128gb after rooting it today.
First off I had my luck with minimum adb and fastboot, install it and go to your computer and find where its downloaded. (Ex. Mine was in C:> programs x86> minimal adb and fastboot folder). After you have located, find you image you just downloaded from Google and extract the files there should be 6 (I am a Verizon user and used the H update from the Google site). Copy all those 6 extracted files into that folder you located earlier (minimal adb and fastboot) and just click on the flash-all file you just dropped in there an sit back and let it do its thing
jscharf10 said:
Ok I literally just did this because I messed up my pixel xl 128gb after rooting it today.
First off I had my luck with minimum adb and fastboot, install it and go to your computer and find where its downloaded. (Ex. Mine was in C:> programs x86> minimal adb and fastboot folder). After you have located, find you image you just downloaded from Google and extract the files there should be 6 (I am a Verizon user and used the H update from the Google site). Copy all those 6 extracted files into that folder you located earlier (minimal adb and fastboot) and just click on the flash-all file you just dropped in there an sit back and let it do its thing
Click to expand...
Click to collapse
------------------------------
hi all semi-noob here... pls excuse any silly comments i make
background - i have twrp installed on my vzn pixel xl... bootloader is unlocked
so i copied all the 6 extracted files into the minimal adb and fastboot folder
i ran the flash-all file
cmd window popped up and just says "< waiting for any device >"
my phone is plugged into my pc via usb cable
question - what mode do i need to be in to flash the factory image?
@peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
[/COLOR @peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
jscharf10 said:
@peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
[/COLOR @peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
Click to expand...
Click to collapse
thx jscharf
Use The Unified Android Toolkit
swapavi said:
I'm not new to flashing the images... But Jesus Christ there's a lot going on with the pixel... There's not just a system, vendor, boot, recovery, and cache IMG now... There's a ****load and I'm not sure how to flash them... And when I run the flash all.bat I keep getting an error during the flash and it just pauses... Same goes for the skipsoft tool. Anyone know how to flash these?
Click to expand...
Click to collapse
I had the exact same issue that you are having, another user on here recommended that I use the Unified Android Toolkit to flash the factory image. It works perfectly, and also has a bunch of other useful features (some will be more useful as the community figures out this system partition thing).
The toolkit is great and no necessary features must be paid for. This will solve your error issue. Best of luck!
Find the toolkit here: https://skipsoft.net/