Database Users

Bricked - help needed

OK, so I was trying to flash the Minimal Matte theme onto my N1, and I seem to have bricked the phone.
The phone now just sticks at the "X" logo when trying to boot.
I cannot access recovery - I get the exclamation mark.
I've tried download the Nexus One FRG83 system image from HTC and put it on the SD card and renamed it passimg.zip to try and get it up and running again - it did the update on the bootloader screen, but it hasn't helped.
Any ideas?

If your getting the exclamation mark, I would say the recovery has been lost somehow, and its on standard again.
Try re flashing recovery via fastboot, amon ra or clockwork, which ever one. Then re flashing whatever rom
Rellikzephyr
Sent from my Nexus One using Tapatalk

OK I've tried this and get the following
Code:
C:\AndroidSDK\tools>fastboot flash recovery d:\recovery.img
sending 'recovery' (2906 KB)... OKAY [ 0.415s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.813s
Any ideas?
ETA: I've tried several different recovery images to no avail.

tameracingdriver said:
OK I've tried this and get the following
Code:
C:\AndroidSDK\tools>fastboot flash recovery d:\recovery.img
sending 'recovery' (2906 KB)... OKAY [ 0.415s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.813s
Any ideas?
ETA: I've tried several different recovery images to no avail.
Click to expand...
Click to collapse
Did you unlock the bootloader?

Also, have you tried:
Code:
fastboot boot recovery.img

Try the nandroid back up in the recovery.

I've just unlocked the bootloader, and ran the command again and I can now get into recovery, and am now trying the CM6 ROM... so we'll see what happens...

And that has worked
Thanks very much for your help

tameracingdriver said:
And that has worked
Thanks very much for your help
Click to expand...
Click to collapse
Glad it worked out for ya ^_^

What size was the image that you've downloaded from HTC?
If it was ~5MB rather than ~90MB - you've downloaded an update, and not a full system image. That would explain why your phone wasn't working after applying it.

Jack_R1 said:
What size was the image that you've downloaded from HTC?
If it was ~5MB rather than ~90MB - you've downloaded an update, and not a full system image. That would explain why your phone wasn't working after applying it.
Click to expand...
Click to collapse
It was about 80ish Mb IIRC.

Hmm.. FRG83 Passimg.. Could you share it or a link to it?

Jack_R1 said:
Hmm.. FRG83 Passimg.. Could you share it or a link to it?
Click to expand...
Click to collapse
http://developer.htc.com/ 2nd link...
http://dl3.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip
That what you are looking for?

Yep Thanks. I'll try to see, why didn't this flash the system clean.

Possible Bricked Tablet - Please Help!

I think i may have bricked my nexus 10.. I was trying to install the chainfire3d application from the market, and when it rebooted, it wouldnt go past the X logo. waited for a long time, so i tried a hard reset, and still nothing. So i figured i would try using the toolkit to help fix. tried to relock, flash, and re-unlock, and it wouldnt work..after the step where you go into factory reset/wipe, it woudlnt go further. I cant get a custom recovery to install, it wont save the file. tried doing that step separately, and it seems to stick on sending the file over. this seems to be a common issue with anything i try.
The screen says:
"sending TWRP touch recovery..
sending 'recovery' (7246 KB) ...
and is just stuck there. this seems to happen in several places, with a few different things ive tried. When trying to flash the stock image, it will get stuck in similar places, perhaps not with the recovery step, but with a portion of the stock image. Been at this for a couple of hours... any help would be greatly appreciated!.
Also, as of now... it wont boot past the google logo. I can get it into fastboot by holding down the buttons, and I can get it into the stock recovery, but thats it. I don't even think adb is detecting the device. I have a feeling that may be a major roadblock to getting this thing fixed. Does anyone know how I can get the tablet to be detected by adb if i cant even get past the google logo screen at boot?
Update 1:
Still cant unbrick my device. any time i try to transfer or flash files to it... it stalls, and if i disconnect the device, i get this error:
FAILED (data transfer failure (too many links)).
Your Device will now boot into Android and detect ADB mode.
problem is, it doesnt reboot, and even if it did, it wouldnt be able to boot into android, since it wont go past the google logo when the device turns on. in fact, i cant even turn it off. only way to turn it off would be to wait for the battery to drain.
If this helps, here is what it says on the fastboot screen:
Device Information
Product Name: manta
Variant: wifi
H/W version : 8
Bootloader Version: MANTALJ12
Carrier Info: none
Serial Number: *********** (not going to publish that, lol)
LOCK STATE: Unlocked
Reboot Mode Flag: none.
anyone have any ideas at all how I can salvage this thing? Im kindof embarrassed honestly. Ive had 5 android devices prior to this one, and have rooted, flashed, and reflashed each of them countless times, and never, ever ran into this before. I could really use the help.
Quick note:
I just noticed that when i try to flash anything to the tablet, the following appears under the rest of the info i listed above.
FASTBOOT STATUS - DATA00713800 (this text is highlighted in light blue)
Update 2:
ok, so i tried to do the factory restore, and am running into the same wall as always. here is the text from the window, perhaps that may clue you into the problem:
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.tg
z
Extracting mantaray-jop40c-factory-0d641789.tar
Everything is Ok
Size: 329369600
Compressed: 326396069
Now extracting flashable Images
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.ta
r
Extracting mantaray-jop40c
Extracting mantaray-jop40c\image-mantaray-jop40c.zip
Extracting mantaray-jop40c\flash-base.sh
Extracting mantaray-jop40c\bootloader-manta-mantalj12.img
Extracting mantaray-jop40c\flash-all.sh
Extracting mantaray-jop40c\flash-all.bat
Everything is Ok
Folders: 1
Files: 5
Size: 329358105
Compressed: 329369600
Factory Images extracted. Starting Flash Process.
Now Flashing Bootloader Image..
sending 'bootloader' (1280 KB)... OKAY [ 0.232s]
writing 'bootloader'... OKAY [ 0.113s]
finished. total time: 0.345s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
Now Flashing Factory Image: Boot, Cache, Recovery, System and Userdata..
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.002s]
sending 'boot' (4606 KB)...
Its just stuck on that last part, sending 'boot' (4606 KB)...
and under all the info on the fastboot page, the following appeared while this was happening:
FASTBOOT STATUS - DATA0047f800 (this line is highlighted in light blue)

*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)

cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
can you link it?

cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
trying that....
so far so good... dont want to get my hopes up though... below is what ive got so far in the cmd screen:
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...

Its been about 30 minutes now... and its still stuck on "sending 'system' (528847 KB)..." in the cmd window.... not sure what that means... it did take about a minute for the recovery to get sent over, and its about 100x larger in size, so i guess i will leave it connected like this for the next hour or so... and hope that it is just going REALLY slowly. Got my fingers crossed...

Battery died while waiting.... this is the complete text of the CMD screen while i was waiting.. forgot that it doesnt charge while in fastboot. got it plugged into an outlet for faster charging while its off.... hopefully when its charged up, i can try again and ill continue to progress
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3941.094s
Press any key to exit...

Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.

jodvova said:
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
Click to expand...
Click to collapse
I cant get it to load a custom recovery! any advice on how to get that going?

ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.

ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
Dumb question, if using a desktop PC are you using the front or rear USB ports? I had a similar issue where it would just get stuck on the "sending system" message. Switched the USB from front port to back port on my linux box and it solved my problem.
Sent from my Nexus 10 using Tapatalk 2

jodvova said:
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
Click to expand...
Click to collapse
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.

ltracte said:
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
Click to expand...
Click to collapse
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.

jodvova said:
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
Click to expand...
Click to collapse
couldnt get the command to work via adb, so i tried it using terminal inside TWRP, and this what it spit back at me:
/dev/block/platform/dw_mmc.0/by-name/system: clean. 11/51296 files. 6651/204800 blocks
i have no idea what that means, nor what else to do....

Fixed it!!!!

ltracte said:
Fixed it!!!!
Click to expand...
Click to collapse
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.

mskip said:
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
Click to expand...
Click to collapse
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!

Whew! So glad you finally had success & thanks for sharing. I'm reading up, research, etc. I received my N10 yesterday. I'm getting ready to unlock/root today.
Sent from my Nexus 7 using Tapatalk 2

ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
Hmm, did you try the flash-all.bat file that comes with the factory image? It does those 3 commands, + erases all partitions automatically.

ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
That's exactly what I did. Just followed the factory image flashing instruction on google's page(where you download the image file for N10). Did you figure out why it wassnt able to transfer the first time?

nexus 4 will make me crazy

i have one received from customer , when i power on just hang on start-up log
to fix that i need just unlock boot loader flash the phone (using Nexus Root Toolkit1.8.6 )
but this one , root is done phone habe unlocked boot loader , when i try to flash i get this error
archive does not contain 'boot.sig'
PHP:
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2203 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
OKAY [ 0.318s]
finished. total time: 0.398s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
sending 'radio' (45537 KB)...
OKAY [ 1.503s]
writing 'radio'...
OKAY [ 2.578s]
finished. total time: 4.083s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
archive does not contain 'boot.sig'
error: out of memory
any help ^

Probably is not the problem about that "sign" error but next line, out of memory error. Check if there is any storage left. If there is,... What rom do you flash with?
Addition: i had a similar problem and i couldnt instal 4.4.4, i did first install 4.2 amd after that on 4.4.4 and it was successful.
I did it by this manual:
https://developers.google.com/android/nexus/images
Sent from my Nexus 4 using XDA Free mobile app

bojanz said:
Probably is not the problem about that "sign" error but next line, out of memory error. Check if there is any storage left. If there is,... What rom do you flash with?
Addition: i had a similar problem and i couldnt instal 4.4.4, i did first install 4.2 amd after that on 4.4.4 and it was successful.
I did it by this manual:
https://developers.google.com/android/nexus/images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
This ^ boot sig error is normal
Sent from my Nexus 5 using XDA Free mobile app

yes phone work with 4.2 as you say thx for help
but i have base band version unknown

hitibiti said:
yes phone work with 4.2 as you say thx for help
but i have base band version unknown
Click to expand...
Click to collapse
Fastboot flash the 4.2 cache image
Sent from my Nexus 5 using XDA Free mobile app

how can i do that ?
thx

hitibiti said:
how can i do that ?
thx
Click to expand...
Click to collapse
Download the factory image. Extract it. Inside is a zip, extract that too. In there you'll find the cache.img. boot into the bootloader and in a cmd window on the pc use
fastboot flash cache cache.img
If you don't have fastboot set up on the pc Google 15 second adb install xda
Sent from my Nexus 5 using XDA Free mobile app

Can't Flash TWRP

Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.

bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Your command is wrong, The command to use is: fastboot flash recovery twrp.the name of your file.img

Just like @jawmail said, you're flashing twrp on the bootloader """slot""
-fastboot flash recovery ***TWPR***.img
-fastboot reboot-bootloader
When your phone reboots, using your volume keys, search for "recovery" and using the power button, confirm it.
PROFIT

bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.

Haha. Thanks. Yeah I am really lucky. My phone is working now thanks. Just coming from the S6 Edge. Very different rooting method from that, so yeah I should be way more careful. Thanks for the awesome guide, btw Heisenberg. Running PureNexus with ExperimentalX kernel. Such an amazing combo.
Heisenberg said:
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Click to expand...
Click to collapse

Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?

Puck24 said:
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Click to expand...
Click to collapse
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P

Heisenberg said:
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Click to expand...
Click to collapse
guess it's a corrupted file?

Actually, I just tried flashing it one more time, rebooted to the bootloader with the phone, not with the command. Then I also used the phone to enter into recovery, not by issuing commands. And it works
Sent from my Nexus 6P using XDA Free mobile app

FAILED (remote: Permission denied!)

Hi guys,
I need some help, I'm rooted running on the stock rom.
I was running the 6.0 L and decided to update to 6.0.1 vie fastboot.
I followed this guide (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) section 10- and did the exact same thing.
Every thing was flashing fine till I reached system.img and this is what I get.
C:\SDK\android-sdk-windows\platform-tools\6.0.1>fastboot flash sysytem C:\SDK\android-sdk-windows\platform-tools\6.0.1\system.img
target reported max download size of 494927872 bytes
sending sparse 'sysytem' (463062 KB)...
OKAY [ 10.395s]
writing 'sysytem'...
FAILED (remote: Permission denied!)
finished. total time: 10.410s
I did not flash the recovery because it says it's optional. I proceeded with the vendor and rebooted the device. When the device starts I get a pop up saying : There's an internal problem with your device. Contact your manufacture for details.
In the setting im still on 6.0 L build but bootloader and radios are on the latest firmware.
any suggestions?
Thanks
I did some search and couldn't find a decent answer.

If this is copy/paste directly from Terminal, then you misspelled "system" in your initial command:
C:\SDK\android-sdk-windows\platform-tools\6.0.1>fastboot flash sysytem C:\SDK\android-sdk-windows\platform-tools\6.0.1\system.img
target reported max download size of 494927872 bytes
sending sparse 'sysytem' (463062 KB)...
OKAY [ 10.395s]
writing 'sysytem'...
FAILED (remote: Permission denied!)
finished. total time: 10.410s
Click to expand...
Click to collapse
Notice the bold, the command is looking for "sysytem" which does not exist. You'll be good to go, if the typo is removed.

SlimSnoopOS said:
If this is copy/paste directly from Terminal, then you misspelled "system" in your initial command:
Notice the bold, the command is looking for "sysytem" which does not exist. You'll be good to go, if the typo is removed.
Click to expand...
Click to collapse
:| facepalm...... thanks man, I should not flash things at 1 AM.
I assume I dont need to flash the BL and radios again? just wipe cache install boot, system and vendor?

mr.dj26 said:
:| facepalm...... thanks man, I should not flash things at 1 AM.
I assume I dont need to flash the BL and radios again? just wipe cache install boot, system and vendor?
Click to expand...
Click to collapse
Correct, as long as you flashed the proper bootloader and radio. Just keep it all matching and you should be set. I try to avoid doing phone tinkering at night lol just never feel like troubleshooting at that time if I mess up.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Correct, as long as you flashed the proper bootloader and radio. Just keep it all matching and you should be set. I try to avoid doing phone tinkering at night lol just never feel like troubleshooting at that time if I mess up.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
lol, ya i'm falling asleep so i'll do it tomorrow, thanks again and good night.