Database Info

Stock GT-I9020A: Won't boot, can't unlock bootloader

Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!

Same issue
stevz34 said:
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Click to expand...
Click to collapse
I have the same problem wit an I9020T for australia and would appreciate any advice available as well.

Send to samsung service

stevz34 said:
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Click to expand...
Click to collapse
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...

Dark_Eyes_ said:
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Click to expand...
Click to collapse
Tried this but as said fastboot is not recognised by my pc. Have installed almost all the drivers I can find to no avail. Must be something else to try.

Spanner127 said:
Tried this but as said fastboot is not recognised by my pc. Have installed almost all the drivers I can find to no avail. Must be something else to try.
Click to expand...
Click to collapse
Well, you should be able to flash official Google images in stock recovery too... Have you tried that?

Dark_Eyes_ said:
Well, you should be able to flash official Google images in stock recovery too... Have you tried that?
Click to expand...
Click to collapse
mY COMPUTER ONLY RECOGNISES abd IN SIDELOAD MODE. tHE FASTBOOT ANYTHING IS NOT RECOGNISED SO i CANNOT UPDATE OR FIX anything. Thanks for trying.

Can you try doing all the stuff you did in some another PC.
Worth a try.

Dark_Eyes_ said:
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Click to expand...
Click to collapse
Tried as suggested, received the following output:
C:\Users\Steven\Downloads\sojua-jzo54k>flash-all
sending 'bootloader' (1536 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.203s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.543s]
writing 'radio'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.543s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKA3
Baseband Version.....: I9020UCKF1
Serial Number........: 33311A4C1F8500EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'I9020XXKA3'.
Update requires 'I9020XXLC2'.
finished. total time: 0.016s
Press any key to exit...
It would seem that I can't flash anything, including official firmware, if the bootloader is locked?
On the plus side, the phone responds fine to the fastboot commands and seems to transfer the images to it just fine, just still no luck getting the darn bootloader unlocked

stevz34 said:
Tried as suggested, received the following output:
C:\Users\Steven\Downloads\sojua-jzo54k>flash-all
sending 'bootloader' (1536 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.203s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.543s]
writing 'radio'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.543s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKA3
Baseband Version.....: I9020UCKF1
Serial Number........: 33311A4C1F8500EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'I9020XXKA3'.
Update requires 'I9020XXLC2'.
finished. total time: 0.016s
Press any key to exit...
It would seem that I can't flash anything, including official firmware, if the bootloader is locked?
On the plus side, the phone responds fine to the fastboot commands and seems to transfer the images to it just fine, just still no luck getting the darn bootloader unlocked
Click to expand...
Click to collapse
Normally it is possible to flash official ota from Google even if the bootloader is locked. What version did you have prior to your problems? Try flashing the ota package that came just after your version as it seems that the package your are trying with cannot be flashed over the version that you have right now!

Dark_Eyes_ said:
Normally it is possible to flash official ota from Google even if the bootloader is locked. What version did you have prior to your problems? Try flashing the ota package that came just after your version as it seems that the package your are trying with cannot be flashed over the version that you have right now!
Click to expand...
Click to collapse
Currently the phone has 2.3.6. I tried flashing 4.0.4, which was the next one, and it failed with the same error, indicating I need to unlock my bootloader. Also tried flashing the 2.3.6 firmware, received the same error. I'm starting to think I should probably give up on this phone.
Any more suggestions?

stevz34 said:
Currently the phone has 2.3.6. I tried flashing 4.0.4, which was the next one, and it failed with the same error, indicating I need to unlock my bootloader. Also tried flashing the 2.3.6 firmware, received the same error. I'm starting to think I should probably give up on this phone.
Any more suggestions?
Click to expand...
Click to collapse
Did you try the OTA update from Google? That's weird cause I flashed it back then and I was on stock 2.3.6 with locked bootloader and stock recovery and it worked. Have you don't anything particular with your phone or is it pure stock 2.3.6? Start there
http://forum.xda-developers.com/showthread.php?t=1063664

Dark_Eyes_ said:
Did you try the OTA update from Google? That's weird cause I flashed it back then and I was on stock 2.3.6 with locked bootloader and stock recovery and it worked. Have you don't anything particular with your phone or is it pure stock 2.3.6? Start there
http://forum.xda-developers.com/showthread.php?t=1063664
Click to expand...
Click to collapse
Thanks for posting that link. Still no luck though. I tried the 2.3.6 (GRK39C) -> 2.3.6 (GRK39F) OTA file and the 2.3.6 (GRK39F) -> 4.0.4 one as I am not sure which version of 2.3.6 that I have. Basically I am trying to use fastboot to apply the OTA update using fastboot -w update filename.zip however it is failing with the following message:
C:\Users\Steven\Downloads>fastboot -w update d1be8195481a.signed-sojua-GRK39F-fr
om-GRK39C.d1be8195.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Steven\Downloads>
The OTA updates indicate they can be flashed using stock recovery. However when I enter the recovery on the phone and select update from sdcard, I get the message indicating that it cannot mount /sdcard. Is there another way I should be doing this?

stevz34 said:
Thanks for posting that link. Still no luck though. I tried the 2.3.6 (GRK39C) -> 2.3.6 (GRK39F) OTA file and the 2.3.6 (GRK39F) -> 4.0.4 one as I am not sure which version of 2.3.6 that I have. Basically I am trying to use fastboot to apply the OTA update using fastboot -w update filename.zip however it is failing with the following message:
C:\Users\Steven\Downloads>fastboot -w update d1be8195481a.signed-sojua-GRK39F-fr
om-GRK39C.d1be8195.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Steven\Downloads>
The OTA updates indicate they can be flashed using stock recovery. However when I enter the recovery on the phone and select update from sdcard, I get the message indicating that it cannot mount /sdcard. Is there another way I should be doing this?
Click to expand...
Click to collapse
You have to rename the file to update.zip and place it on /sdcard. It will install it automatically. Stock recovery won't install custom zip file so that's why you need to do that. Let me know if it works...

[Q] [SOLVED] Cannot Flash Recovery/Root

Hey all,
I bought a Factor Refurbished TF700t with the intention of getting CROM-i flashed on it. I was able to get it unlocked with no issue, however, whenever I try to flash twrp to it, I get this.
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6948 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
and sometimes this
PS E:\Program Files (x86)\Minimal ADB and Fastboot> fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.009s
I am running the naked USB drivers, usb debugging is enabled and rooting with motochopper does not work. I also downgraded to the 10.6.1.14.8 build. It should be noted that I was on 10.6.1.14.10 build when I did the unlocking, but that didn't seem to effect anything. Lastly, fastboot does see the device as I get this output:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot devices
015d2d43004bfc01 fastboot
My fear is this may be an issue with the factory referb I got, but hopfully that's not the case! If anyone can help me, it would be greatly appreciated!
Edit: Solved! The answer was to do it in Linux. Grab a distro of Mint and get to it! =D

Highsight said:
Hey all,
I bought a Factor Refurbished TF700t with the intention of getting CROM-i flashed on it. I was able to get it unlocked with no issue, however, whenever I try to flash twrp to it, I get this.
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6948 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
and sometimes this
PS E:\Program Files (x86)\Minimal ADB and Fastboot> fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.009s
I am running the naked USB drivers, usb debugging is enabled and rooting with motochopper does not work. I also downgraded to the 10.6.1.14.8 build. It should be noted that I was on 10.6.1.14.10 build when I did the unlocking, but that didn't seem to effect anything. Lastly, fastboot does see the device as I get this output:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot devices
015d2d43004bfc01 fastboot
My fear is this may be an issue with the factory referb I got, but hopfully that's not the case! If anyone can help me, it would be greatly appreciated!
Click to expand...
Click to collapse
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:

LetMeKnow said:
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:
Click to expand...
Click to collapse
Yeah - and also: which TWRP version are you trying to flash?

LetMeKnow said:
It looks like that you have a bad download. Check the md5 to ensure that it is not corrupted..:fingers-crossed:
Click to expand...
Click to collapse
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
berndblb said:
Yeah - and also: which TWRP version are you trying to flash?
Click to expand...
Click to collapse
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.

Highsight said:
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.
Click to expand...
Click to collapse
Try a different USB port...
Try to wait to plug your device into your PC until your tablet is already in fastboot...
Let me know if this helps... Thx lj

lj50036 said:
Try a different USB port...
Try to wait to plug your device into your PC until your tablet is already in fastboot...
Let me know if this helps... Thx lj
Click to expand...
Click to collapse
Still no luck. I've been at this for a couple days now. I've tried different cords (one from my dad who also has a TF700 and also my old TF100 cords) and different USB ports, same result for all of them. I read somewhere about USB 3.0 possibly causing problems, is this true? I tried my USB 2.0 ports, but the result seemed the same.

Try "fastboot flash staging twrp.blob", maybe this works better. If not, it can't break anything.

_that said:
Try "fastboot flash staging twrp.blob", maybe this works better. If not, it can't break anything.
Click to expand...
Click to collapse
Same result:
PS C:\Program Files (x86)\Android Studio\sdk\platform-tools> fastboot flash staging twrp.blob
sending 'staging' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.007s

OK, then I can only think of "try a different operating system (Linux)" or "try a different computer".

Highsight said:
Can confirm, the hash is correct. Confirmed using the MD5 Check Util.
Click to expand...
Click to collapse
So your file is good..
Highsight said:
I've tried multiple different ones with the same result sadly, but mostly I've tried 2.7.0.0.
Click to expand...
Click to collapse
I just flashed twrp v2.7 yesterday and went fast and done.. So the v2.7 is working on the tf700. I think that this might be causing the problem.
Copy your fastboot folder and put it here c:\platform_tools> fastboot -i 0x0B05 flash recovery twrp.blob. I think that android is a unix/linux base so they don't like special characters which means no "space".
Please try that and report back for other users have the same issue, thanks..

LetMeKnow said:
So your file is good..
I just flashed twrp v2.7 yesterday and went fast and done.. So the v2.7 is working on the tf700. I think that this might be causing the problem.
Copy your fastboot folder and put it here c:\platform_tools> fastboot -i 0x0B05 flash recovery twrp.blob. I think that android is a unix/linux base so they don't like special characters which means no "space".
Please try that and report back for other users have the same issue, thanks..
Click to expand...
Click to collapse
Same results...
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.018s
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
C:\platform-tools>
I'm going to try sterilizing my drivers and installing the naked ones again.

I just have to ask.. Your bootloader is unlocked yes ???

Highsight said:
Same results...
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.018s
C:\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
(bootloader) Received Data of Bad Length.
sending 'recovery' (6292 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.000s
C:\platform-tools>
I'm going to try sterilizing my drivers and installing the naked ones again.
Click to expand...
Click to collapse
I am sorry for a stupid question but do you see "the device is unlocked" in the upper left corner?
Update: Oops, I am slower than you, @lj50036.

lj50036 said:
I just have to ask.. Your bootloader is unlocked yes ???
Click to expand...
Click to collapse
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"

LetMeKnow said:
I am sorry for a stupid question but do you see "the device is unlocked" in the upper left corner?
Click to expand...
Click to collapse
Beat you too It.. @LetMeKnow
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Highsight said:
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"
Click to expand...
Click to collapse
Yes I agree with @_that.... New OS 'Linux' Thats what I would try...

lj50036 said:
Beat you too It.. @LetMeKnow
---------- Post added at 11:25 AM ---------- Previous post was at 11:23 AM ----------
Yes I agree with @_that.... New OS 'Linux' Thats what I would try...
Click to expand...
Click to collapse
Lemme see what I can do about setting up a dual-boot for my computer and trying on that. To be honest I'm not great with Linux, especially when it comes to drivers, but I'll see what I can do...

Highsight said:
Lemme see what I can do about setting up a dual-boot for my computer and trying on that. To be honest I'm not great with Linux, especially when it comes to drivers, but I'll see what I can do...
Click to expand...
Click to collapse
O there are no drivers....:good: At least not for your android devices...
I would recommend Mint 16... Here is a link
Mint Download Page
Go for cinnamon desktop....
Shoot me a email if you need any help at all... There is an option to shoot me an email on my user page.....

lj50036 said:
O there are no driver....:good:
I would recommend Mint 16... Here is a link
Mint Download Page
Click to expand...
Click to collapse
Well that's pretty sweet. I assume a live USB will do?

Highsight said:
Supposdly.
Whenever I boot the device it says right on the top left "Device is Unlocked".
When going into the bootloader it says the following on the top left.
"Key driver not found... booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.8-20130514" A03
Starting Fastboot USB download protocol"
Click to expand...
Click to collapse
Everything is looking good and you said that your device is communicating with the fastboot command "fastboot devices" with a return of your device serial number. I don't know why that it refuses to write to your recovery partition. Maybe there are some bad blocks in your partition but you just reinstall the stock firmware. I am sorry that I don't have a clue what is going on...

Highsight said:
Well that's pretty sweet. I assume a live USB will do?
Click to expand...
Click to collapse
It will but I would install it native to a hard drive, as we are talking about a 400 dollar tablet.. Your call :fingers-crossed:

Honor 8 - Can't Factory Reset

So I've pretty much hit a wall. I have unlocked bootoader, and everytime I try to enter into factory resetting via volume + power button, it'll boot into "your device is booting now..." and it'll stay there. Same thing if I try to do it via the settings.
Whenever I try to install custom recovery or anything, I get this message.
C:\adb>fastboot flash recovery TWRP-CN.img
target reported max download size of 471859200 bytes
sending 'recovery' (29218 KB)...
OKAY [ 0.789s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.804s
I've tried all sorts of twrp files. My phone has locked me out of changing anything from adb commands it seems. How do I fix this?
My FRP is also locked, if that matters. I've tried to delete all accounts from my phone, as well as the "find my phone" option.
I'm on Anroid 7, EMUI 5.
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot devices
73QDU16B22001173 fastboot
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (remote: Command not allowed)
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot format cache
FAILED (remote: Command not allowed)
OEM is greyed out in the developer settings, I can't activate it or decative.

Try the unlock command again for the bootloader. This worked for me even when it was unlocked before

TomboIa said:
Try the unlock command again for the bootloader. This worked for me even when it was unlocked before
Click to expand...
Click to collapse
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock 1031871703372236
...
FAILED (remote: Command not allowed)
finished. total time: 0.020s
Same thing. It doesn't allow me.

Zebieok said:
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock 1031871703372236
...
FAILED (remote: Command not allowed)
finished. total time: 0.020s
Same thing. It doesn't allow me.
Click to expand...
Click to collapse
Dont share your unlock key here, and are you sure that was your bootloader unlock keys.
Frp lock means your bootloader is locked.

FRP lock is a security action, for remove them you must boot a device and remove all google accounts.
Unfortunately this casw happened to me, when i want factory reset my phone, his dead and i cant boot it again just fastboot work but FRP LOCK activate and i cant flash any thing, give error command not allowed, in last i have to go to repair services, and they do this with hard box (maybe chimera or sigma.. Or other).
If you can boot your device you can do any thing, but if your device get bootloop go to services center.

Trying to boot to twrp

Everytime I try to boot twrp i get this message.
PS C:\adb> fastboot boot twrp-3.3.1-4-guacamole.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.324s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.331s
I am bootloader unlocked so I dont know why I am getting that message. Any help would be appreciated. Thanks

Try "fastboot flash boot [img name]".

The correct command is
Fastboot boot [drag and drop the img]

phenomenalblaze said:
Everytime I try to boot twrp i get this message.
PS C:\adb> fastboot boot twrp-3.3.1-4-guacamole.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.324s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.331s
I am bootloader unlocked so I dont know why I am getting that message. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Are you on Beta1, if so, you can't boot into recovery that way, you need to flash recovery using Magisk first.

No I'm not. I'm on 9.5.11

phenomenalblaze said:
No I'm not. I'm on 9.5.11
Click to expand...
Click to collapse
If you have root, try flashing the recovery installer with Magisk

smo69 said:
Try "fastboot flash boot [img name]".
Click to expand...
Click to collapse
This command is useless it won't work. Download the latest oxygen OS zip(full rom package not the incremental one), place it in your internal storage and update it via the local updater.
After the update is complete you can boot to fastboot and then the command will work i.e. fastboot boot imagefilename.img
Hope this helps

fastboot boot TWRP.img is not rebooting into TWRP

This is a Pixel 3 (just to be clear). I have unlocked my bootloader successfully. I have installed the latest factory images (not OTA). I have re-allowed USB debugging. Downloaded the latest TWRP (twrp-3.3.0-0-blueline.img), and the zip (twrp-pixel3-installer-blueline-3.3.0-0.zip) placed the zip on the phone in the downloads folder. I reboot to bootloader. I open Win 10 command prompt (ADB and Fastboot is in PATH). Change directory to where TWRP img is saved. I type "fastboot boot twrp-3.3.0-0-blueline.img" I see:
Sending 'boot.img' (65536 KB) OKAY [ 0.286s]
Booting OKAY [ 3.407s]
Finished. Total time: 4.618s
My phone reboots but boots into system, not into TWRP.
I assume it is a NOOB mistake... I have looked at https://twrp.me/google/googlepixel3.html, and https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622, and https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Not sure what to do next as I would like to root. Any input would be appreciated.

Android 10 has no TWRP support for Pixel.

So how do I root the first time? Load an old factory image and then fastboot the TWRP image? Everything seems to say the same instructions, which I have tried to follow.

a_wolfie said:
So how do I root the first time? Load an old factory image and then fastboot the TWRP image? Everything seems to say the same instructions, which I have tried to follow.
Click to expand...
Click to collapse
Read the guide. Nothing to do with TWRP. https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359

fastboot oem unlock
...
FAILED (remote: unknown cmd.)
finished. total time: 0.007s
Have anxone a idia

QuentinAP said:
fastboot oem unlock
...
FAILED (remote: unknown cmd.)
finished. total time: 0.007s
Have anxone a idia
Click to expand...
Click to collapse
Did you enable "OEM unlocking" in settings? If "OEM unlocking" is grayed out, you probably have a Verizon or other variant that cannot be boot loader unlocked.

Oem is unlock

QuentinAP said:
Oem is unlock
Click to expand...
Click to collapse
Make sure you are using the latest Android Platform Tools from https://developer.android.com/studio/releases/platform-tools
Try different USB cables and different USB ports, or even a different computer. USB 2.0 ports seem to work better than 3.0 ports. Don't use any USB hubs or adapters.

Ich habe die neueste Version

Why are you trying to run "fastboot oem unlock"? That is only for older Pixel 2 XLs. What are you trying to do?
QuentinAP said:
fastboot oem unlock
...
FAILED (remote: unknown cmd.)
finished. total time: 0.007s
Have anxone a idia
Click to expand...
Click to collapse

Android 11 flashen custom rom
i have a gigaset gs 195

QuentinAP said:
Android 11 flashen custom rom
i have a gigaset gs 195
Click to expand...
Click to collapse
Sorry, I know nothing about that phone. This is a Pixel 3 forum. Try to find a forum for that phone or for the custom rom. Good luck.