Database Info

Wipe data from bootloader menu, didn't brick my frend's device

Hi!
Yesterday my friend asked me to I helped him with unlock, recovery and Custom ROM. I didn't have enough time to help him, so he does it himself. He succesfull unlocked, install TWRP 2.4.3.0 and install CROMI 3.4.4. When he finished install CROMI he reboot system. After 5 minutes he rebooted to bootloader menu (Vol- & Pwr) and from 4 icons (RCK, USB, Wipe Data, Android Logo) he choosed Wipe Data. It dindn't brick his device! He has got this on the newest JB 4.1.1 bootloader.
It's amazing! Does anyone can confirm this information?
Maybe Asus fix bootloader bug? Nobody know.

Hazard17 said:
Hi!
Yesterday my friend asked me to I helped him with unlock, recovery and Custom ROM. I didn't have enough time to help him, so he does it himself. He succesfull unlocked, install TWRP 2.4.3.0 and install CROMI 3.4.4. When he finished install CROMI he reboot system. After 5 minutes he rebooted to bootloader menu (Vol- & Pwr) and from 4 icons (RCK, USB, Wipe Data, Android Logo) he choosed Wipe Data. It dindn't brick his device! He has got this on the newest JB 4.1.1 bootloader.
It's amazing! Does anyone can confirm this information?
Maybe Asus fix bootloader bug? Nobody know.
Click to expand...
Click to collapse
Doing it on the latest boot loader with the latest TWRP is fine. The problems occur on an older bootloader with newer recovery or new bootloader with old recovery. By old and new I mean ICS and JB respectively.
He did JB / JB :good:

Hi
I made the mistake of accidentally wiping data in the bootloader when attemping to upgrade my bootloader from 4.1 to 4.2 using the latest Asus Stock ROM. It completed the wipe and booted into a fresh Andriod (CM10.1 nightly) install. Thinking everying was ok i went back into the bootloader and selected recovery to flash the new Asus Rom...i flashed the ROM and after rebooting it hangs (have let it sit from 30 min to 2hrs on different flash attempts) at the ASUS logo with the spinning circle...if i reboot i still have bootloader access so i can get into recovery or fastboot
Is there anyway to save my tablet?
Thansk

moosehead11 said:
Hi
I made the mistake of accidentally wiping data in the bootloader when attemping to upgrade my bootloader from 4.1 to 4.2 using the latest Asus Stock ROM. It completed the wipe and booted into a fresh Andriod (CM10.1 nightly) install. Thinking everying was ok i went back into the bootloader and selected recovery to flash the new Asus Rom...i flashed the ROM and after rebooting it hangs (have let it sit from 30 min to 2hrs on different flash attempts) at the ASUS logo with the spinning circle...if i reboot i still have bootloader access so i can get into recovery or fastboot
Is there anyway to save my tablet?
Thansk
Click to expand...
Click to collapse
If you have the Asus spinning circle yes it is saveable That is just stuck booting the ROM.
So please list which bootloader and recovery you have with versions.
The easiest way to fix for the 10.6.1.14.8 bootloader and TWRP 2.4.40 and up is download my rom. Do a factory wipe from TWRP and flash it.

sbdags said:
If you have the Asus spinning circle yes it is saveable That is just stuck booting the ROM.
So please list which bootloader and recovery you have with versions.
The easiest way to fix for the 10.6.1.14.8 bootloader and TWRP 2.4.40 and up is download my rom. Do a factory wipe from TWRP and flash it.
Click to expand...
Click to collapse
I have the bootloader from the most recent firmware update WW_V10.6.1.15.3 (sorry don't have my tablet in front of me) and i have twrp 2.4.4-4.2 for my recovery

moosehead11 said:
I have the bootloader from the most recent firmware update WW_V10.6.1.15.3 (sorry don't have my tablet in front of me) and i have twrp 2.4.4-4.2 for my recovery
Click to expand...
Click to collapse
I think you need to upgrade TWRP to the 2.5.0 0 JB4.2 version (make sure you grab the JB4.2). Then it should be a case of factory wipe and flash a stock based 10.6.1.15.3 based rom to get you back up and running.

Bootloader is ww_epad-10.6.1.15.3-20130416 a03
I've tried with 2.5-4.2 with no luck same issue
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 07:02 PM ---------- Previous post was at 06:58 PM ----------
sbdags said:
If you have the Asus spinning circle yes it is saveable That is just stuck booting the ROM.
So please list which bootloader and recovery you have with versions.
The easiest way to fix for the 10.6.1.14.8 bootloader and TWRP 2.4.40 and up is download my rom. Do a factory wipe from TWRP and flash it.
Click to expand...
Click to collapse
What is your rom that you are refering to by the wY
Sent from my GT-I9000 using xda app-developers app

Cannot Flash anything!

Alright, so, my tablet decided to one day just cease stop working. The recovery for some reason can't flash anything now, is used to be able to flash a backup, but not anymore. It used to be able to boot past the animation, but not anymore. I cannot flash a ROM from recovery because it says that the file is bad (and please, don't tell me to check to see if the md5's are correct, they are, I've triple checked.) I've flashed CWM recovery and TWRP recovery, and TWRP cannot fix permissions, but CWM recovery can, but neither can flash a single ROM. I've tried sideloading a rom but i get this error from the CMD window
Code:
* failed to write data 'protocol fault (no status)' *
. I'm at my wits end here. The bootloader is perfectly fine, it works 100% but I can't flash a single thing from recovery. I've flashed non-corrupted recoveries, and still I cannot flash a thing.

You have flashed the latest TWRP via fastboot and it still wont flash roms? Also, what bootloader are you on?
Sent from my ASUS Transformer Pad TF700T Infinity using Tapatalk HD
Rom: CleanRom 3.4.4

Phultara said:
Alright, so, my tablet decided to one day just cease stop working. The recovery for some reason can't flash anything now, it used to be able to flash a backup, but not anymore. It used to be able to boot past the animation, but not anymore. I cannot flash a ROM from recovery because it says that the file is bad (and please, don't tell me to check to see if the md5's are correct, they are, I've triple checked.) I've flashed CWM recovery and TWRP recovery, and TWRP cannot fix permissions, but CWM recovery can, but neither can flash a single ROM. I've tried sideloading a rom but i get this error from the CMD window
Code:
* failed to write data 'protocol fault (no status)' *
. I'm at my wits end here. The bootloader is perfectly fine, it works 100% but I can't flash a single thing from recovery. I've flashed non-corrupted recoveries, and still I cannot flash a thing.
Click to expand...
Click to collapse
What tablet do you have?
From where did you download which recovery for which Asus tablet.
Sounds like the recovery version doesn't match the device.

Thats OK said:
What tablet do you have?
From where did you download which recovery for which Asus tablet.
Sounds like the recovery version doesn't match the device.
Click to expand...
Click to collapse
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.

Phultara said:
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Click to expand...
Click to collapse
Have you ever unlocked the bootloader? (If not: do so by searching on Asus' site for the Unlock Bootloader Tool v7) It's a simple apk which you install and then check and let it unlock.
Only then, you can start flashing!
If you already have unlocked, maybe you sent it in (?) Or flashed an official Asus rom (?), you might want to unlock it again.
Let us know if any of these answers above helped

Phultara said:
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Click to expand...
Click to collapse
If you have the 4 icons that indicates JB.
Sounds like the custom recovery is not installed if your on the RCK icon and press the up volume rocker and nothing happens.

adelancker said:
Have you ever unlocked the bootloader? (If not: do so by searching on Asus' site for the Unlock Bootloader Tool v7) It's a simple apk which you install and then check and let it unlock.
Only then, you can start flashing!
If you already have unlocked, maybe you sent it in (?) Or flashed an official Asus rom (?), you might want to unlock it again.
Let us know if any of these answers above helped
Click to expand...
Click to collapse
Unlocking it would require an OS to be installed, but none is installed because I was wiping to install a different ROM. I have unlocked it. In response to the boot loader, yes, it has 4 icons. So I guess it is the JB boot loader. When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.

Phultara said:
When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Click to expand...
Click to collapse
Can you get adb shell access to your recovery?
Which ZIP are you actually trying to flash? What is the exact error message from the recovery? Try running md5sum (inside the adb shell) on the file you want to flash. Check the output of "mount". Check if /cache/recovery/log contains interesting info.

Phultara said:
Unlocking it would require an OS to be installed, but none is installed because I was wiping to install a different ROM. I have unlocked it. In response to the boot loader, yes, it has 4 icons. So I guess it is the JB boot loader. When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Click to expand...
Click to collapse
AH sorry!
I only read the title and replied lol
Does adb do anything?
Or is adb not working either?

adelancker said:
AH sorry!
I only read the title and replied lol
Does adb do anything?
Or is adb not working either?
Click to expand...
Click to collapse
How would I go about connecting through ADB?

Phultara said:
How would I go about connecting through ADB?
Click to expand...
Click to collapse
* Connect your tablet to a computer with proper drivers and adb installed.
* Boot tablet to recovery.
* On computer, type "adb shell".

_that said:
* Connect your tablet to a computer with proper drivers and adb installed.
* Boot tablet to recovery.
* On computer, type "adb shell".
Click to expand...
Click to collapse
Alright, I'll have to try that when I get home in about 3-4 hours. I'll get back to you on that. Also, I noticed last night that when I was on fast boot, it would stay stuck as waiting for device on the cmd window. I'm not sure if it was my computer that didn't detect it or a new symptom. O hope its just a fluke!

Alright, here's the log from my recovery.

Phultara said:
Alright, here's the log from my recovery.
Click to expand...
Click to collapse
OK, I assumed that you're not using data2sd. 1. Make sure your microsdcard is good (reformat and recopy your backup or rom if needed),2. Boot into twrp and wipe cache, dalvik cache, factory reset, wipe system, wipe internal then finally the most important part, FORMAT SDCARD. Now reflash a new rom or try to restore from backup. I would try step#2 first. Good luck.
EDIT: format sdcard instead of wipe sdcard.

buhohitr said:
OK, I assumed that you're not using data2sd. 1. Make sure your microsdcard is good (reformat and recopy your backup or rom if needed),2. Boot into twrp and wipe cache, dalvik cache, factory reset, wipe system, wipe internal then finally the most important part, FORMAT SDCARD. Now reflash a new rom or try to restore from backup. I would try step#2 first. Good luck.
EDIT: format sdcard instead of wipe sdcard.
Click to expand...
Click to collapse
That did it!!! Thank you!!!! Looks like it was the SD that was the root of the issue! Thanks!!

[Q] Corupted ssd disc/mmcblk0boot0 + mmcblk0boot1?

Hi Team,
It seems that after 1 year of using TF700 64GB, ssd disc is corupted.
I had installed CWM+CM 10.2 stable, but system has lags and has a problem with booting (2 sucess from 5 times?). I try to make new installation via CWM (+factory reset/wipe dalvik cache).First problem was with mounting \System, \Cache...factory reset was unsuccessful...its possible that i used factory reset in menu after going to recovery menu too...
Recovery mode CWM is still functional, i can change recovery via fastboot to TWRP without problems, but there is bootloop....
Android system doesnt want startup...
Im looking for dump of bootpartitions mmcblk0boot0 + mmcblk0boot1 (images of these partitions http://forum.xda-developers.com/showthread.php?t=2274333) - or any advices to resolve my problem.
Unfortunately, i can not dump these 2 partitions from non rooted tablet and i havent any unlocked/rooted....
Thanks in advance for any helpful reply!

rxd1978 said:
Recovery mode CWM is still functional, i can change recovery via fastboot to TWRP without problems, but there is bootloop....
Android system doesnt want startup...
Click to expand...
Click to collapse
I sounds as if you are on the wrong bootloader. For CM 10.2 you have to be on a 10.6.1.14.4 or later bootloader. What's your version?
And the quoted sentence leaves me scratching my head: Which recovery do you have installed: CWM or TWRP? You can't have both..... Also post which version.
You probably have to
- flash bootloader and recovery in fastboot
- at least wipe, maybe format your /data partition in recovery
- flash the rom

berndblb said:
I sounds as if you are on the wrong bootloader. For CM 10.2 you have to be on a 10.6.1.14.4 or later bootloader. What's your version?
And the quoted sentence leaves me scratching my head: Which recovery do you have installed: CWM or TWRP? You can't have both..... Also post which version.
You probably have to
- flash bootloader and recovery in fastboot
- at least wipe, maybe format your /data partition in recovery
- flash the rom
Click to expand...
Click to collapse
Now i using TWRP. Before this bootloop/android starting problem i had CWM. TWRP i flashed later via faastboot.
Tablet worked with CM 10.2 without problems a few days, so i suppose that bootloader version was correct...
My friend, which helping me resolve this said, that from ADB console this 2 partitions are unreadable...
therefore advised me to obtain images this hidden bootpartitions from the same type of TF700...
thx!

Not sure what or why your friend is suggesting, but I'd try formatting data from inside twrp first.
You still haven't said what versions you are using so we are guessing when trying to help you.

sbdags said:
Not sure what or why your friend is suggesting, but I'd try formatting data from inside twrp first.
You still haven't said what versions you are using so we are guessing when trying to help you.
Click to expand...
Click to collapse
TWRP 2.6.3.1., bootloader is 10.6.1.14.10 i think

rxd1978 said:
TWRP 2.6.3.1., bootloader is 10.6.1.14.10 i think
Click to expand...
Click to collapse
And one additional information: when i try to wipe/format date via TWRP (or CWM before i flash the last TWRP), it was unsuccessful - with messages Cant mount system, cache...

rxd1978 said:
And one additional information: when i try to wipe/format date via TWRP (or CWM before i flash the last TWRP), it was unsuccessful - with messages Cant mount system, cache...
Click to expand...
Click to collapse
Reboot to TWRP, then run "adb shell dmesg > dmesg.txt" on your computer, and post the resulting file.

_that said:
Reboot to TWRP, then run "adb shell dmesg > dmesg.txt" on your computer, and post the resulting file.
Click to expand...
Click to collapse
hi,
i want to say BIG THANK YOU 4ALL - for your advices.
I decide to send tablet as a complaint. I will inform you about results.

[Q] Troubleshooting laggy TF700T

Hello,
My TF700T is pretty laggy and I'm trying to workout if there's something under the covers that I can remedy.
Looking through the logcat (as attached), I can see some disturbing recurring items that might be contributing to these issues:
Failed on audit_set_pid with error: Protocol not supported
Caused by: libcore.io.ErrnoException: connect failed: ECONNREFUSED (Connection refused)
I'm on TWRP v2.8.0.1, and believe that I'm on BL 10.6.1.14.10 (based on the contents of device_info.txt).
Looking at the following, it's suggested to update the bootloader:
http://forum.xda-developers.com/showthread.php?t=2668805
However looking at the following it seems as though I have the most recent version of the BL?
http://forum.xda-developers.com/showthread.php?t=2425383
Can anyone advise help point me in the right direction? Apologies for the newb questions, I'm just getting nowhere fast!

You find your bootloader version on the bootloader menu screen (Power and Volume Down) and you seem to be on the latest 10.6.1.14.10.
When's the last time you did a clean install?
I would do a factory wipe in TWRP and reflash the rom.
You can restore your apps from a TiBu backup, but should not restore any system settings.
Also backup your launcher and restore it after the flash and you shoud be minutes away from your ususal setup.

2257
Hmmm ... I tried a TWRP Factory Reset and installed cm-11.0-20140403-CROMBikk4.4.2-tf700t_Signed.zip that I already had ready to go, and it is now hanging on the CROMBi-KK prompt when I reboot (stuck for at least half an hour). Have downloaded cm-11.0-20140921-tf700t-crombi-kk-R1_signed.zip and will try to install this, hopefully this resolves.

Ok, I'm back up with the latest Crombi-KK goodness, but the system is still pretty laggy and there are still some disconcerting logcat messages as below. Any suggestions on how to resolve?
Sent from my GT-I9505 using Tapatalk

Sorry, adding attachment, link was rejected when I tried posting from device.

RedDemon said:
Ok, I'm back up with the latest Crombi-KK goodness, but the system is still pretty laggy and there are still some disconcerting logcat messages as below. Any suggestions on how to resolve?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Did you check you bootloader version by booting into it?

berndblb said:
Did you check you bootloader version by booting into it?
Click to expand...
Click to collapse
Looks like you may be on to something, bootloader displays the following. I'm assuming it needs updating based on this output? If so, what is recommended?
Key driver not found ... Booting OS
Android cardhu-user bootloader <1.00e> released by "WW-epad-10.6.1.14.4-20130329" A03
Starting USB fastboot USB download protocol
The following message has also appeared a couple of times. Have select "I'm Feeling Lucky" both times, I wonder what's causing this and if there's a more permanent fix?
System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable.

RedDemon said:
Looks like you may be on to something, bootloader displays the following. I'm assuming it needs updating based on this output? If so, what is recommended?
Key driver not found ... Booting OS
Android cardhu-user bootloader released by "WW-epad-10.6.1.14.4-20130329" A03
Starting USB fastboot USB download protocol
The following message has also appeared a couple of times. Have select "I'm Feeling Lucky" both times, I wonder what's causing this and if there's a more permanent fix?
System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable.
Click to expand...
Click to collapse
Yep, your bootloader is just a touch too old. The .4 boots the KK rom, but it doesn't seem to run it well.
Head over to the CROMi-X 5.4 thread in the Development section. Scroll down in the OP until you see the 10.6.1.14.10 bootloader/TWRP package and download it.
Flash that package in your current TWRP and reboot.
Then boot to recovery and check the version. sbdags kind of promised just yesterday to update the package to include TWRP 2.8.0.1, and lj kind of promised to take care of it also. But I don't know if they did already - there was a lot of banter about "lazy bastards" going back and forth [emoji12]
If you see that you got TWRP 2.6.0.1 after the package flash, just flash 2.8.0.1 in fastboot and you should have no further trouble.
I don't think you will see the inconsistent system UI message again, but if you do, clean install CROMBi again.
BTW, where did you get that 'device info' file? I suspect it pulled the bootloader version from Software Information > Build Number. The only way to really tell your bootloader version running custom software is from the bootloader screen.

berndblb said:
Yep, your bootloader is just a touch too old. The .4 boots the KK rom, but it doesn't seem to run it well.
Head over to the CROMi-X 5.4 thread in the Development section. Scroll down in the OP until you see the 10.6.1.14.10 bootloader/TWRP package and download it.
Flash that package in your current TWRP and reboot.
Then boot to recovery and check the version. sbdags kind of promised just yesterday to update the package to include TWRP 2.8.0.1, and lj kind of promised to take care of it also. But I don't know if they did already - there was a lot of banter about "lazy bastards" going back and forth [emoji12]
If you see that you got TWRP 2.6.0.1 after the package flash, just flash 2.8.0.1 in fastboot and you should have no further trouble.
I don't think you will see the inconsistent system UI message again, but if you do, clean install CROMBi again.
BTW, where did you get that 'device info' file? I suspect it pulled the bootloader version from Software Information > Build Number. The only way to really tell your bootloader version running custom software is from the bootloader screen.
Click to expand...
Click to collapse
Lol ... love the banter, on the contrary, you guys are doing a stellar job helping others make the most of their devices, keep up the great work!
Thanks heaps ... have uploaded the bootloader to 10.6.1.14.10 using the following:
http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
The bootloader now says "Android cardhu-user bootloader <1.00 e> released by "WW-epad-10.6.1.14.10-20130801" A03", so looks like I'm on the right version now.
However, even after installing the same CROMBikk zip, I can't boot into the OS anymore (have tried a few installations to no avail).
Instead, I get the following (not sure if this is a problem or just a new feature of the latest bootloader), after which always returns to TWRP:
[4.xxxxxx] preinit ######### starting #########
Detecting filesystems...
mmcblk0p8 /data on internal (UDA) -> ext4
mmcblk1p2 /data on microSD (for Data2SD/ROM2SD) -> not present
mmcblk1p3 /system on microsSD (for ROM2SD) -> not present
4.xxxxx fm34: [fm34_config_DSP] DSP ACK, read 0xc0:1
4.xxxxx fm34: [fm34_config_DSP] Load TF700T DSP parameters
After this it reboots and enters TWRP.
Am I doing something wrong? Have I missed anything? Are there any additional steps I need to follow to ensure the integrity of the install?
It has also reverted back to TWRP v2.6.1.0 which you'd preempted, and in the past I've usually used the ADB / Terminal method to install TWRP to my device. However, given that I can't boot into my device, I can't do that anymore. So I've entered "Fastboot USB download protocol", and I have the option of "RCK", "Android" or "Wipe Data". I can't see any options to "select the usb icon and hit volume up to confirm" as per http://teamw.in/project/twrp2/105, and I can't even see the device anymore from the PC fastload utility. If I can get the OS up and running this wouldn't be such an issue, and I'd simply use the "ADB / Terminal method" as I have in the past.
I note that after the install, I get the following prompt in TWRP which I haven't seen before. Doesn't seem to matter if I opt to fix or not, I still can't boot into the OS.
Fix Superuser Permissions?
Root permissions appear to be lost.
Fix root permissions now?
(Fixes permissions on su binary and app)
BTW, where did you get that 'device info' file? I suspect it pulled the bootloader version from Software Information > Build Number. The only way to really tell your bootloader version running custom software is from the bootloader screen.
Click to expand...
Click to collapse
The device info file was created by CatLog, it seemed like the easiest way to determine the bootloader, but in retrospect it was inaccurate. Lesson learnt!

Mhhh, so you flashed CROMBi-KK with TWRP 2.6.0.1?
That might be the problem here.
The Teamwin instructions are a little outdated. You are in fastbot mode when you are on the screen with the 3 icons.
If you need more instructions on flashing the recovery in fastboot, check this guide:
http://forum.xda-developers.com/showthread.php?t=2688891

Thanks, great post. I'll use it to do some further troubleshooting and let you know how it goes
Sent from my GT-I9505 using Tapatalk

berndblb said:
Mhhh, so you flashed CROMBi-KK with TWRP 2.6.0.1?
That might be the problem here.
The Teamwin instructions are a little outdated. You are in fastbot mode when you are on the screen with the 3 icons.
If you need more instructions on flashing the recovery in fastboot, check this guide:
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
You're spot on again, after upgrading to TWRP 2.8.0.1 and reflashing the ROM, all is well in the world again (OK, at least on my tablet), doing a TiBU restore as we speak!
Thanks again for a fantastic guide. Tried a number of things despairingly and as a last gasp tried connecting the cable to another USB port. They're both USB 2.0 and both work fine for everything else so can't see why it would be an issue, but in the new USB port it works a charm. Thanks again so much, highly appreciated!

In my excitement of having resurrected my tablet, I didn't really comment on the end goal, which was to improve tablet efficiency and remove/reduce lag. Happy after playing around for a couple of days that things are much smoother with the latest bootloader and ROM. I can still see "Failed on audit_set_pid with error: Protocol not supported" frequently occur in the catlog, but I guess if the tablet is otherwise functioning well it isn't an issue. Thanks again for your help.
The ROM did unfortunately corrupt itself overnight when the device ran out of battery and it kept hanging on the Crombi-KK splash screen. After trying a few things I reflashed the ROM and restored again. A bit annoying, but not sure how it could be avoided (other than keeping it charged in like I'd usually do, although I'd like to think that things wouldn't so easily be corrupted).

[HELP] return to stock

So I've been running rooted stock for a while and decided to try out blisspop. After a few days I decided to return to stock, partly because I read about the 3.1.1 update coming out. I downloaded the 3.1 full OTA, flashed it with TWRP and all was fine. Things started to get wonky when I got home the other night and decided to update the controller( I hadn't done it after the 3.1 update rolled out). The controller wouldn't update and the tablet kept freezing up. Then the download for the 3.1.1 update showed up and of course I didn't flash it because I wasn't stock. Then I started getting google play services errors and I couldn't do a thing so I did a factory reset. During the setup process it keeps freezing up during 'Checking connection'. I can forget the network, go through the setup and get to the home screen but then I have no icons. I can restart the tablet and the the default icons appear where I can then connect to my wifi network but I can't add a google account(keep getting google services errors)(I enter my email address to add the account, hit 'next' and it freezes up). The weird things is this even happens when I reboot to bootloader and
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
and then
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
This is of course after downloading the recovery image(3.1 found here http://forum.xda-developers.com/shield-tablet/general/stock-recovery-images-ota-library-guides-t2988881) and verifying the md5 so I know everything is good. The really wierd thing is, I have none of these problems if I get back into the bootloader, flash TWRP, reboot into recovery and then flash bliss, gapps, and reboot.
Does this make sense to anyone?
Any help would be appreciated
Thanks

Update: I went through the same process and flashed the stock 2.2.2 recovery image. Same results, I cannot add a google account but I can connect to my wifi network. Right now it's downloading the 3.1.1 update, so we'll see in a bit.

deleted

All is good. I still have no idea what I screwed up.
After using the fastboot erase commands, and then flashing TWRP, I noticed some messages in twrp about not being able to mount /system, /data, etc. So who knows? So I tried to flash blisspop again and I ended up in a loop booting into twrp again and again.
So I erased everything again, flashed twrp, booted to recovery and formatted internal storage. I flashed the full 3.1.1 OTA, rebooted and my world is beautiful again(no google play services errors).
Hopefully these posts help someone, if some sense can be made of them.
Sent from my SHIELD Tablet using Tapatalk

Man this helped me out tremendously!!! I think just the steps to manually erase each partition (if thats what they're called) is what ended up helping me. I had to do it twice for it to work properly but it worked! And I'm pretty sure I tried everything the past few days. I wasn't having the same problem as you. My tablet was stuck on the nvidia boot screen after trying to flash stock recovery. Thought I bricked my device for a couple days. Thanks for posting!

unable to flash any update with twrp..need help.. with each ota file the error comes-- " package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K... this device has nvidia/omni_shieldtablet/shieldtablet:6.0.1/MOB30D/ "

manish.kumar86 said:
unable to flash any update with twrp..need help.. with each ota file the error comes-- " package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K... this device has nvidia/omni_shieldtablet/shieldtablet:6.0.1/MOB30D/ "
Click to expand...
Click to collapse
Please try to ask in only one place, it's confusing to those who try to help you when the same question is in the different posts
Sent from my SHIELD Tablet K1 using Tapatalk

I know but no solution from anywhere.. now i have even stuck in worse situation. Tries flashing all three version of stock image--
SHIELD TABLET K1 open source and binary driver release for OTA 1.2.0
SHIELD TABLET K1 open source and binary driver release for OTA 1.1.1
SHIELD TABLET K1 open source and binary driver release for preinstalled factory image
but not able to boot into recovery and also its not booting for hours.. i feel i cant revert from android 6.0.1 to any one of the stock image given by nvidia mentioned above..
Even tried experimental twrp and any other twrp i can find for shield k1, but its not going into recovery..
any help wd be great..
Exile1975 said:
Please try to ask in only one place, it's confusing to those who try to help you when the same question is in the different posts
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse

where is this battery.dtb file? its not in the folder i downloaded from nvidia and i cant find it anywhere

oilerseberle14 said:
where is this battery.dtb file? its not in the folder i downloaded from nvidia and i cant find it anywhere
Click to expand...
Click to collapse
Me neither