Develop Bugs

[Q] N7 LTE Dead. No Write on NAND. Permanent Brick?

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.

Teclast X70R - C7F9 - Tablet - Android 5.1.1 - Intel SoFIA Atom X3-C3230

Teclast X70R - It's different model than Teclast X70
Brand: Teclast
Type: Phablet
OS: Android 5.1.1
CPU Brand: Intel
CPU: SoFIA Atom X3-C3230
GPU: Mali-450MP
Core: Quad Core
RAM: 1GB
ROM: 8GB
Support Network: 2G, Built-in 3G, WiFi
WiFi: 802.11b/g/n wireless internet
Network type: GSM+WCDMA
Frequency: GSM 850/900/1800/1900MHz WCDMA 900/2100MHz
3G : Built in 3G (WCDMA)
GPS: Yes
Bluetooth: Yes
Screen type: IPS, Retina Screen, Capacitive (5-Point)
Screen size: 7 inch
Screen resolution: 1024 x 600 (WSVGA)
Camera type: Dual cameras (one front one back)
Back camera: 2.0MP
Front camera: 0.3MP
SIM Card Slot: Dual SIM, Dual Standby
TF Card Slot: Yes
Micro USB Slot: Yes
3.5mm Headphone Jack: Yes
Battery Capacity: 3000mAh
Battery / Run Time (up to): 3 hours video playing time
AC adapter: 100-240V 5V 2A
G-sensor: Supported
---
ROOT
I have bought recently Teclast X70R (C7F9).
but... I can't root it. I've tried many programs (iRoot, KingRoot, KingoRoot, OneClick Root, etc.)
Tablet is absent in system and it's sometimes seen as Rockchip Sofia C7F9.
I have proper drivers, but when I tried to root it by iRoot it has an unknow device in device manager called: 2 CDCa new and don't have drivers for it.
I've got is bootloader:
secure: NO
unlocked: YES
version-bootloader: 1538.400_M1S1
product: SF_3GR
Its of course C7F9. Any ideas?
Instructions to ROOT Teclast X70R (C7F9) »
.

Quick search & found that you have indeed started a new thread here... Since your bootloader is unlocked & unsecured, by right you can root it directly using my root script or using the method here, try & report it back on how it works out for you...

yuweng said:
Quick search & found that you have indeed started a new thread here... Since your bootloader is unlocked & unsecured, by right you can root it directly using my root script or using the method here, try & report it back on how it works out for you...
Click to expand...
Click to collapse
I'm little affraid to flash this device by other recovery or something similar. Some people said that it fits recovery from Chuvi Vi7, and maybe from Teclast X70 (not R). But I'm afraid to brick it.
I've tried your method, and connected through ADB WiFi (earlier also by regular USB). But... There is the same problem as ADB by USB. When I type:
adb root
it gives me comment:
"adbd cannot run as root in production builds"
and
adb disable-verity give comment
"disable-verity only works for userdebug builds"
and of course, adb remount:
remount of system failed: Permission denied
remount failed
I have X70R - model number X70 R(C7F9)
Baseband version: SF3GR_LPOP-MR1_REL_01.1530.02.07
Kernel: 3.14.0
Build number: V1.08_20151030
So it's newst version - some people have 1.06
And in fastboot getvar all, all I have:
c:\adbmini>fastboot getvar all
(bootloader) version-baseband: 24832
(bootloader) version-bootloader: 1538.400_M1S1
(bootloader) product: SF_3GR
(bootloader) secure: NO
(bootloader) unlocked: YES
(bootloader) off-mode-charge: 0
(bootloader) ========== parition type ==========
(bootloader) system parition type: ext4
(bootloader) userdata parition type: ext4
(bootloader) cache parition type: ext4
(bootloader) hypervisor parition type: raw
(bootloader) boot parition type: raw
(bootloader) recovery parition type: raw
(bootloader) splash parition type: raw
(bootloader) mvconfig parition type: raw
(bootloader) secvm parition type: raw
(bootloader) vrl parition type: raw
(bootloader) psi parition type: raw
(bootloader) slb parition type: raw
(bootloader) ucode_patch parition type: raw
(bootloader) ===================================
(bootloader) ========== parition size ==========
(bootloader) system parition size: 0x80000000
(bootloader) userdata parition size: 0x30700000
(bootloader) cache parition size: 0x1a900000
(bootloader) hypervisor parition size: 0x400000
(bootloader) boot parition size: 0x1000000
(bootloader) recovery parition size: 0x1000000
(bootloader) splash parition size: 0x1700000
(bootloader) mvconfig parition size: 0x100000
(bootloader) secvm parition size: 0xc00000
(bootloader) vrl parition size: 0x40000
(bootloader) psi parition size: 0x20000
(bootloader) slb parition size: 0x100000
(bootloader) ucode_patch parition size: 0x3000
(bootloader) ===================================
(bootloader) max-download-size: 0x3ec00000
@yuweng, you written that I can run your script in recovery - I need to boot it to recovery when starts tablet (VOL- + Power) - or to boot it there by command (i.e. adb reboot fastboot)?
Soory, but I also don't see/ didn't find your script. Can you provide it?

As pointed out, the name of the file is ROOT-x3-C3130-KK.7z is here... Try the attach recovery.img & see if it works... :fingers-crossed:
Code:
adb reboot fastboot
fastboot flash recovery recovery.img
adb reboot recovery
adb root
adb remount
Double-click the root.bat & it should root... If it works then manually install SuperSU...

Tried 2 times - one as normal, going to fastboot and flash recovery, and second, when tried to unlock it (again) and next flash recovery.
After normal flashing in fastboot:
c:\adbmini>fastboot flash recovery recovery.img
(bootloader) recovery partition type: raw
target reported max download size of 1052770304 bytes
sending 'recovery' (11844 KB)...
(bootloader) Ready to receive: 0x00b91000 size of data
FAILED (data transfer failure (Too many links))
finished. total time: 0.032s
Unlocking bootloader - results. Is it okay?
c:\adbmini>fastboot oem unlock confirm
...
(bootloader) Unlocking and rebooting into unlocked state
OKAY [ 0.006s]
finished. total time: 0.007s
and then tried flash recovery as above.

i've never seen that error before, quick search suggest you either have a bad contact, faulty USB port or cable & even driver problem, try different port or cable... Anyway, i've flash it on my X70, fastboot flash 100% successful...

OK, I have a problem some time ago with Android TV Box on my Windows 8.1. This OS didn't see it properly, so I connected it to my Windows 7 PC. Then, all was OK. I've flashed and now it's working. So going to Teclast X70R:
I connected it to Windows 7 PC, and... Flashing recovery was ok. Below is a whole process:
Code:
c:\adba>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789012345678901234567890 device
c:\adba>adb reboot fastboot
c:\adba>fastboot devices
0123456789012345 fastboot
c:\adba>fastboot flash recovery recovery.img
(bootloader) recovery partition type: raw
target reported max download size of 1052770304 bytes
sending 'recovery' (11844 KB)...
(bootloader) Ready to receive: 0x00b91000 size of data
OKAY [ 0.462s]
writing 'recovery'...
(bootloader) Flashing partition: recovery
OKAY [ 1.064s]
finished. total time: 1.530s
c:\adba>
but... I can't give command adb reboot recovery. It says: error: device not found
So I rebooted it manually, and in recovery there is no working adb command (it's normal I purpose). And any adb root or adb disable-verity are still as before.
What changed when I've flashed this recovery?
EDIT:
Quite far away. In recovery:
Code:
c:\adba>root.bat
c:\adba>adb remount
remount of system failed: Success
remount failed
c:\adba>adb install Superuser.apk
failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk': Permission de
nied
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\adba>adb install RootChecker.apk
failed to copy 'RootChecker.apk' to '/data/local/tmp/RootChecker.apk': Permissio
n denied
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\adba>adb push install-recovery.sh /system/etc
failed to copy 'install-recovery.sh' to '/system/etc': Permission denied
c:\adba>adb push su /system/xbin/daemonsu
failed to copy 'su' to '/system/xbin/daemonsu': Permission denied
c:\adba>adb push su /system/xbin/su
failed to copy 'su' to '/system/xbin/su': Permission denied
c:\adba>adb push su /system/xbin/sugote
failed to copy 'su' to '/system/xbin/sugote': Permission denied
c:\adba>adb push su /system/xbin/supolicy
failed to copy 'su' to '/system/xbin/supolicy': Permission denied
c:\adba>adb push supolicy /system/xbin
failed to copy 'supolicy' to '/system/xbin': Permission denied
c:\adba>adb push libsupol.so /system/lib
failed to copy 'libsupol.so' to '/system/lib': Permission denied
c:\adba>adb shell chmod 0755 /system/etc/install-recovery.sh
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\adba>adb shell chmod 0755 /system/xbin/su
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\adba>adb shell chmod 0755 /system/xbin/daemonsu
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\adba>adb shell chmod 0755 /system/xbin/sugote
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\adba>adb shell chmod 0755 /system/xbin/supolicy
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\adba>adb shell chmod 0644 /system/lib/libsupol.so
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\adba>adb reboot
c:\adba>
... failed: Success? What a strange error?
adb root - works in recovery, when typed, it "thinking" and show next line, so it works (I suppose). And next adb disable-verity shows as above - disable-verity only works for userdebug builds.
So what's next? @yuweng, you are my only hope 0 And remember, this is X70R not X70 - just in case 0

It has been explained at the X70 thread here & that should enable adb root & adb remount... Try below commands two times while at recovery...
Code:
adb root
adb shell mount -ro remount,rw /
Now double-click root.bat & hope it works... :fingers-crossed: if it doesn't then we'll have to take a deeper look at dm-verity...

yuweng said:
It has been explained at the X70 thread here & that should enable adb root & adb remount... Try below commands two times while at recovery...
Code:
adb root
adb shell mount -ro remount,rw /
Now double-click root.bat & hope it works... :fingers-crossed: if it doesn't then we'll have to take a deeper look at dm-verity...
Click to expand...
Click to collapse
adb root in recovery works ok, but when I type second command, I have error:
- exec '/system/bin/sh' failed no such file or directory (2) -
and also the same happened when I type: adb shell

its quite late over this side of the globe now so in the meantime, you can always look at the ref here...

yuweng said:
its quite late over this side of the globe now so in the meantime, you can always look at the ref here...
Click to expand...
Click to collapse
Tried, searched, but I have no knowledge and really don't want to make any mistake and brick device. I see you have this knowledge, so that's why I rely on you 0 Any other forums or persons don't guide me or someone to this far point (I think). So easy, I don't hurry you, I understand you 0 but I will be grateful if you, or someone will help to works this out.
Thank you.

The biggest problem with users nowadays is that they just don't feedback & then disappear, its really sad that most DEVs devoted their time/ experience while they don't get anything in return, just as TWRP Lead Developer Dees_Troy once said...
Dees_Troy said:
Occasionally there's a third method where we work with a remote tester who owns the device to get the device working in TWRP. This third method is not used very often because by and large, remote testers are epic failures. Remote testers often need tons of hand holding and line-by-line directions. Remote testers often fail to know how to get things like adb and fastboot working. Remote testers often fail to make themselves available when we need them and they disappear before we're able to finish verifying a completely working build. At this point, we usually only work with remote testers that we already know and have a relationship with so that we can ensure that we're not wasting our valuable time working with someone who doens't know what they're doing and will disappear before the job is done.
Click to expand...
Click to collapse
Fyi, Intel X3 devices are unbrickable... Since you said you have the newer version of C7F9 then its best that you upload the boot.bin directly from your device using this View attachment C7F9-ebl.fls.zip, use this driver, zip it & attach it to your reply then we'll try the unsecured-boot method... In case you don't have the View attachment FlashTool_E2_v146.zip
Step 1
Step 2 <= Take note : The Start Address is 0x1B000000 for your C7F9
Step 3 <= Click at the Start USB1 (here you see the Stop button), switch off your X70R & upload will proceed
Step 4 <= Zip the boot.bin & attach it to your reply
Try the attachment below & see if it works this time... :fingers-crossed:
Updates - For X3-C3230 device owners that doesn't have or can't find their factory firmware
Seems that it is possible to upload system.bin too with this View attachment X3-C3230-system-ebl.fls.zip <= The Start Address is 0x00000044 & lenght is 0x80000000, it will take quite awhile, refer to here on how-to create a fastboot flashable system.img
As for recovery, the previous same C7F9-ebl.fls.zip can also be use to upload the recovery.bin <= The Start Address is 0x0001C800 & lenght is 0x01000000 but require cleaning up the unused header, refer to here for more info...
Of course the easier way would be after gaining root access....
Code:
adb shell su -c "dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID[COLOR="Blue"]068[/COLOR] of=storage/sdcard1/system.img"
adb pull storage/sdcard1/system.img
adb shell su -c "dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID[COLOR="blue"]071[/COLOR] of=storage/sdcard1/boot.img"
adb pull storage/sdcard1/boot.img
adb shell su -c "dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID[COLOR="blue"]121[/COLOR] of=storage/sdcard1/recovery.img"
adb pull storage/sdcard1/recovery.img
With boot & system.img, you would be able to unbrick your X3 while the stock 3e recovery is for flashing update.zip factory firmware if it is available

yuweng said:
The biggest problem with users nowadays is that they just don't feedback & then disappear, its really sad that most DEVs devoted their time/ experience while they don't get anything in return, just as Lead TWRP Developer Dees_Troy once said...[/hide]Fyi, Intel X3 devices are unbrickable... Since you said you have the newer version of C7F9 then its best that you upload the boot.bin directly from your device using this View attachment 3597241, use this driver here View attachment 3509083, zip it & attach it to your reply then we'll try the unsecured-boot method... In case you don't have the View attachment 3597251
View attachment 3475319
View attachment 3475320 <= Take note : The Start Address is 0x1B000000 for your C7F9
View attachment 3475321 <= Click at the Start USB1 (here you see the Stop button), switch off your X70R & upload will proceed
View attachment 3475322 <= Zip the boot.bin & attach it to your reply
Try the attachment below & see if it works this time... :fingers-crossed:
Click to expand...
Click to collapse
I will do it later (but today) I have to go now. I have downloaded files from this post, but seems to be a problem with above description. You have written and linked attachements like "Attachment 3597241". I only see name and empty link. No link to a file. When clicked it gives me an info:
Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post.
So if you give ma proper links, to files I will do it with the instructions.
Anyway - for now I have 2 things.
1. I can work on it's root, I have a little bit knowledge about flashing ROMs, rooting device etc. Not big, but I will try to help. Not only for me, but there are many users with same device. It can help them also if we solve it. But I need clear instructions, because I don't want to brick device, or do something wrong.
I will not resign, I will not dissappear 0
2. With this 2 files as attachements, what I have to do - flash it as before? Or do it only when first part will be done (this with empty attachements links)?
unsecured-C7F9-recovery-V2.zip
C7F9-kernel-vi7-ramdisk.zip

Fixed download link, same post, as for the attachment is the same, extract it & use fastboot to install it, same adb commands...

yuweng said:
Fixed download link, same post, as for the attachment is the same, extract it & use fastboot to install it, same adb commands...
Click to expand...
Click to collapse
Done this 2 files. After flashing first: unsecured-C7F9-recovery-V2.zip
Here what happened - same as before. Recovery worked, options, navigation etc.
Code:
c:\adba>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0123456789012345678901234567890 device
c:\adba>adb reboot fastboot
c:\adba>fastboot devices
0123456789012345 fastboot
c:\adba>fastboot flash recovery recovery-02-unsecured-C7F9-recovery-V2.img
(bootloader) recovery partition type: raw
target reported max download size of 1052770304 bytes
sending 'recovery' (11844 KB)...
(bootloader) Ready to receive: 0x00b91000 size of data
OKAY [ 0.410s]
writing 'recovery'...
(bootloader) Flashing partition: recovery
OKAY [ 1.060s]
finished. total time: 1.480s
c:\adba>adb reboot recovery
error: device not found
c:\adba>adb root
error: device not found
c:\adba>fastboot devices
0123456789012345 fastboot
c:\adba>
After flashing second: C7F9-kernel-vi7-ramdisk.zip
Some new things here. adb root gives comment: adbd is already running as root
adb disable-verity: verity not enabled - ENG build
And cannot go to recovery - no options, no navigation, only "dead" Android robot with exclamation and Chineese info (which I don't understand) - see attachement.
And process:
Code:
c:\adba>adb reboot fastboot
c:\adba>fastboot devices
0123456789012345 fastboot
c:\adba>fastboot flash recovery recovery-03-C7F9-kernel-vi7-ramdisk.img
(bootloader) recovery partition type: raw
target reported max download size of 1052770304 bytes
sending 'recovery' (11992 KB)...
(bootloader) Ready to receive: 0x00bb6000 size of data
OKAY [ 0.420s]
writing 'recovery'...
(bootloader) Flashing partition: recovery
OKAY [ 1.070s]
finished. total time: 1.490s
c:\adba>adb root
error: device not found
c:\adba>fastboot reboot
rebooting...
finished. total time: -0.000s
c:\adba>adb reboot recovery
c:\adba>adb root
adbd is already running as root
c:\adba>adb remount
remount of system failed: Success
remount failed
c:\adba>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\adba>adb disable-verity
verity not enabled - ENG build
c:\adba>
Also - I've been today at market where is other tablet using the same configuration, but other company, other logo. Kiano:
model number: SlimTab7_3GR
Baseband version: CTE_MNT_SF_3GR_MRD_LPOP_MR1_1526.02
Kernel: 3.14.0 (as mine Teclast) and more info: [email protected] #1. Thu Jul 30 15:54:45 CST 2015
Build number: Sf3gr_mrd6_p2-userdebug 5.1.1. LMY47V eng.softteam.20150730.152121 release-keys
I know that is different model (looks same, parameters same, like Chuvi Vi7 or Vido T99), but on build number there is info "userdebug", and also it have in options: OEM unlocking. I don't have this option in my Teclast X70R.
Two questions:
If I flash first recovery, it will back to live as previous, instead of "dead" robot?
I've downloaded your files, but using this tool "FlashTool_E2" I don't see my tablet. Tried on 3 computers, and in stationary even tried connect on back USB ports, from motherboard. No connection. What I have to make it working - fastboot or other state?

Looks like i have to get my hands on it, install teamviewer & give me the user id/ password via pm...

yuweng said:
Looks like i have to get my hands on it, install teamviewer & give me the user id/ password via pm...
Click to expand...
Click to collapse
Here is this boot file (attachement)
I've found something here according error "... /bin/sh - no such file or directory (2)" Wipe? It will delete all?
http://forum.xda-developers.com/showthread.php?t=2177166
and also some informations. Maybe @yuweng you will understand more:
http://stackoverflow.com/questions/...hell-on-android-when-system-bin-sh-is-missing
.

Since you mentioned it, i presume you did format the data & cache when you unlock the bootloaders...
Code:
fastboot format userdata
fastboot format cache
[COLOR="Blue"]OR[/COLOR] carry out a factory reset from recovery
Fyi, uploaded boot.bin kernel from your device is identical to the C7F9 firmware from here ( for those who doesn't know, enter C7F9 credits to the Russian for the link )
Read this regarding the danger of using FlashTool, IMEI & unbricking... :good: Anyway, attach is the unsecured-boot, test it out & see if it works... :fingers-crossed: if this doesn't work then the last resort would be Pre-Rooted system.img but in my opinion, its really a waste of bandwidth to download a few hundreds of MB just for rooting it...

yuweng said:
Since you mentioned it, i presume you did format the data & cache when you unlock the bootloaders...
Code:
fastboot format userdata
fastboot format cache
[COLOR="Blue"]OR[/COLOR] carry out a factory reset from recovery
Fyi, uploaded boot.bin kernel from your device is identical to the C7F9 firmware from here ( for those who doesn't know, enter C7F9 credits to the Russian for the link )
Read this regarding the danger of using FlashTool, IMEI & unbricking... :good: Anyway, attach is the unsecured-boot, test it out & see if it works... :fingers-crossed: if this doesn't work then the last resort would be Pre-Rooted system.img but in my opinion, its really a waste of bandwidth to download a few hundreds of MB just for rooting it...
Click to expand...
Click to collapse
OK, what I have done:
Rebooted to fastboot
In fastboot unlocked bootloader
formatted userdata
formatted cache
flashed recovery-vi7-v2 - the same you have sent me yesterday through TV
rebooted
Nothing changed, only system is new, factory reset.
OEM unlock I've done like this:
Code:
c:\adba>adb reboot fastboot
c:\adba>fastboot oem unlock
...
(bootloader) Unlocking the bootloader means the following:
(bootloader) All user data will be deleted
(bootloader) Any securely stored data will be inaccessible
(bootloader) Warranty will be void
(bootloader) After unlocking you have to execute
(bootloader) > fastboot format userdata
(bootloader) > fastboot format cache
(bootloader) or carry out a factory reset from recovery
(bootloader) To confirm the unlock, please execute the command
(bootloader) > fastboot oem unlock confirm
OKAY [ 0.050s]
finished. total time: 0.050s
c:\adba>fastboot oem unlock confirm
...
(bootloader) Unlocking and rebooting into unlocked state
OKAY [ 0.000s]
finished. total time: 0.000s
c:\adba>fastboot devices
0123456789012345 fastboot
c:\adba>fastboot format userdata
(bootloader) userdata partition type: ext4
erasing 'userdata'...
(bootloader) Erasing partition: userdata
OKAY [ 1.600s]
formatting 'userdata' partition...
(bootloader) userdata partition type: ext4
(bootloader) userdata partition size: 0x30700000
Creating filesystem with parameters:
Size: 812646400
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 3100
Label:
Blocks: 198400
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/49616 inodes and 6446/198400 blocks
sending 'userdata' (14492 KB)...
(bootloader) Ready to receive: 0x00e27190 size of data
writing 'userdata'...
(bootloader) Flashing partition: userdata
(bootloader) Download Progress 20%
(bootloader) Download Progress 40%
(bootloader) Download Progress 60%
(bootloader) Download Progress 80%
OKAY [ 4.230s]
finished. total time: 5.850s
c:\adba>fastboot format cache
(bootloader) cache partition type: ext4
erasing 'cache'...
(bootloader) Erasing partition: cache
OKAY [ 0.230s]
formatting 'cache' partition...
(bootloader) cache partition type: ext4
(bootloader) cache partition size: 0x1a900000
Creating filesystem with parameters:
Size: 445644800
Block size: 4096
Blocks per group: 32768
Inodes per group: 6800
Inode size: 256
Journal blocks: 1700
Label:
Blocks: 108800
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27200 inodes and 3510/108800 blocks
sending 'cache' (8692 KB)...
(bootloader) Ready to receive: 0x0087d124 size of data
writing 'cache'...
(bootloader) Flashing partition: cache
(bootloader) Download Progress 20%
(bootloader) Download Progress 40%
(bootloader) Download Progress 60%
(bootloader) Download Progress 80%
OKAY [ 2.310s]
finished. total time: 2.540s
c:\adba>fastboot oem unlock confirm
...
FAILED (remote: Please run oem unlock first and read instructions)
finished. total time: 0.010s
c:\adba>fastboot flash recovery recovery-04-vi7ramdisk-recovery.img
(bootloader) recovery partition type: raw
target reported max download size of 1052770304 bytes
sending 'recovery' (11992 KB)...
(bootloader) Ready to receive: 0x00bb6000 size of data
OKAY [ 0.410s]
writing 'recovery'...
(bootloader) Flashing partition: recovery
OKAY [ 1.150s]
finished. total time: 1.570s
c:\adba>
All working (or not working) as before, so adb remount does nothing, adb shell gives error like it's not present - not such file or directory (in Android it works or either, it's seen).
What next - flash it unsecured boot? How to do it? Which app - FlashTool_E2 or something other like PhoneFlashToolLite_5.3.4.1 or else?
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite

Code:
fastboot flash boot boot.img
fastboot reboot
Wait for it to boot up then...
Code:
adb root
adb remount
adb shell mount -ro remount,rw /
Double-click root.bat

Installed TWRP, phone forever on boot animation. Need data from device

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.

After Android 7.0 update, stuck on BootScreen ; Bootloader Locked

Device : Nexus 5X
I am registered with Google beta program and have installed Andriod 7.0 OTA update this morning. After a few hours of usage, the phone by itself booted and stuck at google dots animation logo. I don't know why it happened and trying to figure out a solution since a few hours.
Here is what I have and What I did so far..
1. Bootloader is LOCKED and both usb debugging and oem unlock check box in developer options are NOT enabled. I can't boot the phone, so there is no way to enable them now.
2. I have tried using fastboot the following commands 'fastboot oem unlock' ; 'flashboot flashing unlock' ; fastboot format cache' with the following results.
fastboot oem unlock and fastboot flashing unlock : FAILED <remote: oem unlock is not allowed>
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'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.016s
3. With no good solution, I started looking for adb sideload options.
So I downloaded the recovery rom to adb sideload of this version 6.0.1 (MTC20F) from the website which is the latest release. ANY OTHER older versions are giving error saying Device requires bootloader-bullhead-bhz11e version and rom has a different version bootloader. So it failed to load any other previous rom releases.
Result : It did not work. It successfully installed, both in cmd promt and adb's Apply update from ADB' mode, I get no errors and installs successfully. On booting the phone, It is stuck on same google dots animation logo and phone heats up like insane. I left it there few hours since it takes more time for first booting with much patience and hope but its no good.
4. As some of the forum's advised, I have installed Nexus Toolkit ( which I although hate using). In the toolkit, Unlock bootloader would for some reason reboot my phone as soon as I click it and shows this message "Waiting for devices".
I have explained what I done now. I have pretty much run out my ideas and need you guys help.
The core problem that would solve this is to unlock the device which requires access to Developer's options which the phone won't boot. I only have access to TWRP for now.

Bootloader Reports Unlocked, Unable to Flash Custom Recovery/Re-Lock Bootloader

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.