Database Info

[Q] [q] ???help bricked maybe????

Hello, I believed I have an issue. Hope it not to serious. My problem is that i can't get passed the ASUS logo Splash screen.
1st: I was one stock jelly bean rooted cwm recovery v6.0.1.2 and decide I wanted to get on to Hydro 3.6 Jellybean (9/17)
2nd I downloaded the ROM wiped cache,delvic and factory reset then installed, didn't install at first so I tried a mirror and then it installed correctly restarted the tablet and here I am.
3rd: Tried clean rom 2.0 still no luck.
Please help I'm 15 and don't wanna break the bad news to my parents.
Ps: I am able to still boot into CWM recovery 6.0.1.2 tried everything nothing working and able to fastboot but cold boot and wipe data don't work and haven't shut off tablet since accident will remain on and charged.

jekovenatinsley said:
Hello, I believed I have an issue. Hope it not to serious. My problem is that i can't get passed the ASUS logo Splash screen.
1st: I was one stock jelly bean rooted cwm recovery v6.0.1.2 and decide I wanted to get on to Hydro 3.6 Jellybean (9/17)
2nd I downloaded the ROM wiped cache,delvic and factory reset then installed, didn't install at first so I tried a mirror and then it installed correctly restarted the tablet and here I am.
3rd: Tried clean rom 2.0 still no luck.
Please help I'm 15 and don't wanna break the bad news to my parents.
Ps: I am able to still boot into CWM recovery 6.0.1.2 tried everything nothing working and able to fastboot but cold boot and wipe data don't work and haven't shut off tablet since accident will remain on and charged.
Click to expand...
Click to collapse
It's just a softbrick. As long as you can get into fastboot you are ok.
I suggest reflashing the stock jellybean rom. You can download it from the asus website.
As for getting it into your device (i dont know if cwm supprots sd cards yet). You can use the adb push commands or you can flash twrp which supprots flashing from the sd card.
Also next time read the rom thread carefully. It specifically says you should use twrp.

Hey man try this, it works for me (Same situation but i'm 17 xD)
1) Download this http://www.mediafire.com/?5diezc69u1b16f8
2)Extract the "recovery1" folder in C:\ drive
3)Plug the tablet to PC and turn it on while pressing VOL- and POWER, then go to the fastboot mode (is the USB symbol)
4)Download from here ( http://support.asus.com/Download.asp...300T&p=20&s=16 ) the WW of US instead of the version of the tablet you have got, the extract the blob file in the "recovery1" folder
5)Open CMD, type cd c:\recovery1 then press enter
6)Type dir to see if all the files are in the folder
7)type this command fastboot -i 0x0B05 flash system blob
8)After is done, type fastboot -i 0x0B05 reboot
9)Enjoy!
If you can't do any of this steps, post here and I will help you

Fixed It!
ZerOMKD said:
It's just a softbrick. As long as you can get into fastboot you are ok.
I suggest reflashing the stock jellybean rom. You can download it from the asus website.
As for getting it into your device (i dont know if cwm supprots sd cards yet). You can use the adb push commands or you can flash twrp which supprots flashing from the sd card.
Also next time read the rom thread carefully. It specifically says you should use twrp.
Click to expand...
Click to collapse
Hey actually like 10 mins after I posted I was able to install Clean Rom.
I formated every partition except sd card in v6.0.1.2 cwm recovery as well as factory reset and wipe dalvik.
Actually I like cwm recovery better and it does support microsd cards now. This is the jb/touch bootloader.
Thanks for the Help anyways.

.
Same problem, when i try to flash JB Hydro 3.6... i stuck into bootloop... i flash the official asus update and it works... But when i try to flash the hydro rom it doesn't work.... Why?

I guess you have the new JellyBean Bootloader... because of that you can only flash ROM's which are made for it...

.
I know... i update from jb ota to hydro... but when i flash the 3.6 i got bootloop... and now i can flash this rom...

Bricked? Cant boot past Asus Screen

Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.

cavz903 said:
Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.
Click to expand...
Click to collapse
Are you sure to be still rooted ?
Simply question
If you aren't still root, just root again before to try some rom install

philos64 said:
Are you sure to be still rooted ?
Simply question
If you aren't still root, just root again before to try some rom install
Click to expand...
Click to collapse
sorry for the delay - thanks for the reply.
I dont know how to tell if im rooted from recovery.
So just went ahead and flashed the root file i found here:
http://www.androidgadgematic.com/2012/10/root-asus-transformer-pad-tf300-install-cwm.html
flashed Baked 7 and gapps again with same result.
(however i noticed at first reboot the asus screen shows a quick blue loading bar under center logo. then nothing.)
rebooted into TWRP - wiped - flashed root.zip again - restored backup.......asus screen.
another thing i noticed was when i try to install (flash) anything, it says no md5 found or if i select "force md5 check" it fails.
im a seasoned novice. I've gotten myself out of some sticky jams. but im totally lost here....

cavz903 said:
Hi guys, Im having a little Problem with my tf300. I've been running Baked 6 rom for a couple months and saw that version 7 was released which is full 4.2.1. Backed up, wiped, flashed, and rebooted.
Got stuck at Asus splash screen. unable to turn device off, it just turns right back on to the splash screen. I am able to hold volume down + power to get into TWRP recovery.
Restored back up, rebooted and still stuck on ASUS screen. Tried another backup with same result
Tried re-downloading rom copying it to external memory card and flashing again, still stuck at asus screen.
I am so lost here, not sure if i should throw this thing out the window, or get on my knees and pray.
any help is greatly appreciated.
I have googled the problem and have seen similar issues, but not anybody that can access recovery and still has the problem.
Click to expand...
Click to collapse
I suggest flash latest stock with twrp. You will loose twrp but with a working unit you can fastboot twrp again.

tobdaryl said:
I suggest flash latest stock with twrp. You will loose twrp but with a working unit you can fastboot twrp again.
Click to expand...
Click to collapse
thanks
ive looked around. but cant find a flashable stock download.
i did find a method to flash a blob via fastboot. but i dont know how to tell if i have a WW or a TW sku.(to DL firmware from asus site)
is TW for users in Taiwan? and WW for everybody else world wide?

cavz903 said:
thanks
ive looked around. but cant find a flashable stock download.
i did find a method to flash a blob via fastboot. but i dont know how to tell if i have a WW or a TW sku.(to DL firmware from asus site)
is TW for users in Taiwan? and WW for everybody else world wide?
Click to expand...
Click to collapse
The SKU versions on the asus firmware page, are as follows:
- US = USA
- CN = China
- TW = Taiwan
- WW = Worldwide
- DE = Germany
- JP = Japan
- TB = Belgium, Turkey, Luxembourg
But you can flash US or WW, they are compatible

philos64 said:
The SKU versions on the asus firmware page, are as follows:
- US = USA
- CN = China
- TW = Taiwan
- WW = Worldwide
- DE = Germany
- JP = Japan
- TB = Belgium, Turkey, Luxembourg
But you can flash US or WW, they are compatible
Click to expand...
Click to collapse
ok so, downloaded WW stock firmware from Asus site. flashed blob file via fastboot.
it said it finished "okay"
rebooted and, back at the Asus Screen.
and now i dont have recovery either. any suggestions?
thank you

any other ideas? im lost here... thanks

cavz903 said:
any other ideas? im lost here... thanks
Click to expand...
Click to collapse
This is normal. The stock blob contains stock recovery and is flashed over the recovery you have in place.
Time to reflash your twrp.

tobdaryl said:
This is normal. The stock blob contains stock recovery and is flashed over the recovery you have in place.
Time to reflash your twrp.
Click to expand...
Click to collapse
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.

cavz903 said:
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.
Click to expand...
Click to collapse
Flash the latest twrp (2.4.1.0). There were issues of using 4.2 and custom recoveries. That was the reason for the last two versions of twrp.
All custom roms here I have checked are pre rooted so the only time I flash root is with a stock rom.
If you were not already using twrp 2.4.1.0 then reflash your stock rom. Earlier versions might not flash the roms properly for 4.2. We need to get working first then you can flash your rom choice.
I hope your version of twrp is less than 2.4.1.0 because if not I'm lost at the moment. I'll be thinking and searching while you play.
Good Luck!
Note: Sorry I should have said twrp 2.4.1.0 JellyBean!

cavz903 said:
Ok so i will re-flash twrp via fastboot. but then what!? re-root via an update.zip? and flash a few custom rom? beacuse i am still stuck at the Asus boot screen.
Click to expand...
Click to collapse
How are you getting the roms onto your device to flash them, the TF300 doesn't have any external memory. Unless there is a way to push the file to the internal sdcard via fastboot, that I'm looking into right now, I dont understand how you are able to flash anything besides .img files or an update.zip.

flukeSG2 said:
How are you getting the roms onto your device to flash them, the TF300 doesn't have any external memory. Unless there is a way to push the file to the internal sdcard via fastboot, that I'm looking into right now, I dont understand how you are able to flash anything besides .img files or an update.zip.
Click to expand...
Click to collapse
Flash recovery with fastboot
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot
Note: recovery is in the directory with fastboot on the pc
Flash recovery with adb
adb shell
su
adb push twrp.blob /sdcard/twrp.blob
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
Note: twrp.blob is in the directory with adb and fastboot on the pc and is copied to the sdcard
Flash recovery with android terminal
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
exit
Note: twrp.blob is on the sdcard
/sdcard as used here is an example – paths to both (internal or external) sdcards change with rom and you need to look at the proper path for the sdcard you wish to use. A root browser is what I use for this.
These are examples for the tf300 there are others.
Red text are actual commands typed!
Maybe this will help to explain the most commonly used methods.
Your internal and external sdcards are normally mounted when your tablet is plugged into your pc
I'm sorry I had to respond!

tobdaryl said:
Flash recovery with fastboot
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot
Note: recovery is in the directory with fastboot on the pc
Flash recovery with adb
adb shell
su
adb push twrp.blob /sdcard/twrp.blob
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
Note: twrp.blob is in the directory with adb and fastboot on the pc and is copied to the sdcard
Flash recovery with android terminal
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
exit
Note: twrp.blob is on the sdcard
/sdcard as used here is an example – paths to both (internal or external) sdcards change with rom and you need to look at the proper path for the sdcard you wish to use. A root browser is what I use for this.
These are examples for the tf300 there are others.
Red text are actual commands typed!
Maybe this will help to explain the most commonly used methods.
Your internal and external sdcards are normally mounted when your tablet is plugged into your pc
I'm sorry I had to respond!
Click to expand...
Click to collapse
I apparently don't have drivers for adb for my tf300t. I have no problem with fastboot. I am able to successfully flash the recovery, but I am unable to push any data to my sdcard.
Without being able to fully boot my tablet, I'm not sure I can even get adb to work? If I install drivers for adb, won't I lose my fastboot capabilities that I currently have? My tablet shows up as a fastboot device in my device manager, would I just open it's properties and select new drivers for it?
My next idea is to get ahold of the system.img, boot.img and recovery.img from a rom to flash from fastboot. I can't seem to find these inside any roms I've downloaded yet, where would I find them? I am thinking I would prefer the latest stock asus rom if possible. I've downloaded the rom from Asus website, unzipped it and no .img files in it. I've also downloaded the rooted stock rom from xda here and also no .img files inside it. Does this even sound plausible, to flash those .img files from inside fastboot to make the tablet boot up?
Edit: Small side question, what exactly is "-i 0x0B05" that for? I seem to be able to accomplish flashing things without that small bit in my commands for example I can just type \fastboot flash recovery recovery.img and that works just fine. So what is that small code?

flukeSG2 said:
I apparently don't have drivers for adb for my tf300t. I have no problem with fastboot. I am able to successfully flash the recovery, but I am unable to push any data to my sdcard.
Since you did not provide data about your situation I looked at your previous posts. Notice the big red line in my signature about WIPE DATA.
I'll try to help but this is a hard one to fix. You have to be willing to keep chipping away till I give or we have success. It can be very frustrating.
Without being able to fully boot my tablet, I'm not sure I can even get adb to work? If I install drivers for adb, won't I lose my fastboot capabilities that I currently have? My tablet shows up as a fastboot device in my device manager, would I just open it's properties and select new drivers for it?
My next idea is to get ahold of the system.img, boot.img and recovery.img from a rom to flash from fastboot. I can't seem to find these inside any roms I've downloaded yet, where would I find them? I am thinking I would prefer the latest stock asus rom if possible. I've downloaded the rom from Asus website, unzipped it and no .img files in it. I've also downloaded the rooted stock rom from xda here and also no .img files inside it. Does this even sound plausible, to flash those .img files from inside fastboot to make the tablet boot up?
Edit: Small side question, what exactly is "-i 0x0B05" that for? I seem to be able to accomplish flashing things without that small bit in my commands for example I can just type \fastboot flash recovery recovery.img and that works just fine. So what is that small code?
Click to expand...
Click to collapse
-i 0x0B05 is an identification provided by google for Asus android products. Each vendor is provided with a number. My tablet does not require it either but some do so we just suggest it to everyone.
I'm skipping everything else you asked for the moment.
Prior to flashing CWM were you on JB or ICS?
Either way we need to replace your non working CWM with twrp (2.4.1.0). Here is the link if you were on JB then flash JB if you were on ICS flash ICS.

tobdaryl said:
-i 0x0B05 is an identification provided by google for Asus android products. Each vendor is provided with a number. My tablet does not require it either but some do so we just suggest it to everyone.
I'm skipping everything else you asked for the moment.
Prior to flashing CWM were you on JB or ICS?
Either way we need to replace your non working CWM with twrp (2.4.1.0). Here is the link if you were on JB then flash JB if you were on ICS flash ICS.
Click to expand...
Click to collapse
Hey I appreciate your help man. I was on CM10 JB 4.1.1, but that was before they required us to have the JB Bootloader, which is where I started to mess up at. I've had CWM since I was running CM10, so when I wiped data, it wasn't from a stock recovery, but I'm guessing that doesn't make a difference. Anyways right now, I'm waiting for the battery to charge up a bit, let it die out last night. I will post as soon as I get TWRP flashed.

flukeSG2 said:
Hey I appreciate your help man. I was on CM10 JB 4.1.1, but that was before they required us to have the JB Bootloader, which is where I started to mess up at. I've had CWM since I was running CM10, so when I wiped data, it wasn't from a stock recovery, but I'm guessing that doesn't make a difference. Anyways right now, I'm waiting for the battery to charge up a bit, let it die out last night. I will post as soon as I get TWRP flashed.
Click to expand...
Click to collapse
Good. While waiting you can download the latest ICS stock 9.4.3.30. You will find it in post 3 of this thread.

So I've got an interesting snag now. I've flashed TWRP 4 times, it never takes. When I boot into recovery, it's still CWM. When I use fastboot, it says it's sending and writing are both ok, but when I reboot into recovery it's still CWM 5.5.0.4.
Edit: I even went as far as to try using the JB version of TWRP, because I was on JB before, just not the 4.2.1 that requires JB bootloader. Still gives me the same result.
Edit 2: I have the stock boot.blob also I just tried flashing, same thing, still got CWM after flashing the blob.

flukeSG2 said:
So I've got an interesting snag now. I've flashed TWRP 4 times, it never takes. When I boot into recovery, it's still CWM. When I use fastboot, it says it's sending and writing are both ok, but when I reboot into recovery it's still CWM 5.5.0.4.
Edit: I even went as far as to try using the JB version of TWRP, because I was on JB before, just not the 4.2.1 that requires JB bootloader. Still gives me the same result.
Edit 2: I have the stock boot.blob also I just tried flashing, same thing, still got CWM after flashing the blob.
Click to expand...
Click to collapse
Your recovery has to be the same as your bootloader. Don't mistake JB in rom name and JB bootloader. They are two different things and if your bootloader is ICS then we need ICS.
OK. Let's see what we have to work with now. Boot into CWM, plug your tablet into your pc and check for adb access.(adb devices)

tobdaryl said:
Your recovery has to be the same as your bootloader. Don't mistake JB in rom name and JB bootloader. They are two different things and if your bootloader is ICS then we need ICS.
OK. Let's see what we have to work with now. Boot into CWM, plug your tablet into your pc and check for adb access.(adb devices)
Click to expand...
Click to collapse
It's not charging fast enough on my pc, so I had to disconnect it and plug it into the wall for awhile again. I can pm you if you'd like when I get it fully charged.

TWRP loop possible progress

I haven't seen this written anywhere yet but I've found something weird with the TWRP loop, months back I used the asus system wipe and got stuck in the TWRP loop because I supposedly erased all the data and file structures on my system but every now and then I keep checking for fixes and playing around with the tablet, today I charged it up again and went into TWRP, on the PC (win 7) ran the cmd "ADB reboot bootloader", for the hell of it I chose the middle option, the android, is said cold booting linux, the chrome asus logo came up with the spinning dot animation and I just waited and then it began updating my app's and my system loaded right up, everything was there. There's no sd-card in the external slot so it's pulling straight from the tablet, wifi connected, all my apps began updating from the marketplace, I can download, TWRP just says the tablet is blank. It seems to have no root access anymore though, hopefully this can be helpful. Also if I reboot it goes right back to TWRP but if I run the reboot bootloader cmd and choose the android it starts right back up without having to update everything again.

pariahcomplex said:
I haven't seen this written anywhere yet but I've found something weird with the TWRP loop, months back I used the asus system wipe and got stuck in the TWRP loop because I supposedly erased all the data and file structures on my system but every now and then I keep checking for fixes and playing around with the tablet, today I charged it up again and went into TWRP, on the PC (win 7) ran the cmd "ADB reboot bootloader", for the hell of it I chose the middle option, the android, is said cold booting linux, the chrome asus logo came up with the spinning dot animation and I just waited and then it began updating my app's and my system loaded right up, everything was there. There's no sd-card in the external slot so it's pulling straight from the tablet, wifi connected, all my apps began updating from the marketplace, I can download, TWRP just says the tablet is blank. It seems to have no root access anymore though, hopefully this can be helpful. Also if I reboot it goes right back to TWRP but if I run the reboot bootloader cmd and choose the android it starts right back up without having to update everything again.
Click to expand...
Click to collapse
so if you can get to bootloader. why dont you fastboot flash the blob file for the latest update? this would install system and new bootloader and stock recovery. from there regaining control of tablet. then just fastboot flash twrp and flash a custom rom....just a thought but if your getting into bootloader you should be able to flash blob.

I tried that right when I saw fast boot coming up, nothing would go through, I did fix it by using the method posted by Buster by using fast boot to systematically erase everything one by one then flash new firmware, just thought this info might be helpful, it's almost like twrp becomes a separate partition when you use asus wipe since everything is still there and bootable

kaos420 said:
so if you can get to bootloader. why dont you fastboot flash the blob file for the latest update? this would install system and new bootloader and stock recovery. from there regaining control of tablet. then just fastboot flash twrp and flash a custom rom....just a thought but if your getting into bootloader you should be able to flash blob.
Click to expand...
Click to collapse
I'm having issues and this won't help me. I flashed the JB version of twrp 2.5 instead of the 4.2 one and am getting a bootloop on the Asus screen. I reflash the update blob and it just doesn't boot

It IS Lupus said:
I'm having issues and this won't help me. I flashed the JB version of twrp 2.5 instead of the 4.2 one and am getting a bootloop on the Asus screen. I reflash the update blob and it just doesn't boot
Click to expand...
Click to collapse
search i have seen a guide for your specific issue on how to correct. it i was under q&a.

kaos420 said:
search i have seen a guide for your specific issue on how to correct. it i was under q&a.
Click to expand...
Click to collapse
I figured it out. I downgraded my bootloader back to 4.1(I know it went because I had the fastboot USB icon back) flashed the correct recovery and wiped everything. My data partition got corrupted. Got back into a working environment and flashed 4.2.1 again, with the proper recovery.
Sent from my HTC6435LVW using xda app-developers app

It IS Lupus said:
I figured it out. I downgraded my bootloader back to 4.1(I know it went because I had the fastboot USB icon back) flashed the correct recovery and wiped everything. My data partition got corrupted. Got back into a working environment and flashed 4.2.1 again, with the proper recovery.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
alternativly this should work as well for latest fw
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
(just for reference)
cheers
-Buster

Buster99 said:
alternativly this should work as well for latest fw
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
(just for reference)
cheers
-Buster
Click to expand...
Click to collapse
This is how I ended up fixing mine, can't thank you enough Buster

Sent from my GT-I9505 using XDA Premium 4 mobile app

[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

HELP!My tab got stuck in twrp 3.0

I was thinking of flashing the new marshmallow rom but it didnt work in CWm.So i flashed twrp 3.0.Afterwards i tried to do a factory reset but it gave some Error messages something like "Cannot mount.failed".Then i restarted the tab and again entered the recovery and found that Internal storage was 0mb.
Afterwards i popped in a sd card with the rom.But it still couldnt flash it and was stuck in the cyan boot screen.I thought that twrp 2.8 would work so i flashed the img file.It said it was successful.Then,i restarted and now when i enter the recovery it says error loading recovery its now stuck in that cyan boot screen and i cannot even enter in recovery mode.
What can i do?Please help.

Are u able to boot Android?

I would recommend you flash the stock blob in fastboot and start over from scratch.
That's called a buster99 and the instructions are here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
You use the TF700 stock blob naturally, he did this on a 300 but it works just the same on this tablet.

federico.guerrazzi said:
Are u able to boot Android?
Click to expand...
Click to collapse
No nor can i go to recovery.

berndblb said:
I would recommend you flash the stock blob in fastboot and start over from scratch.
That's called a buster99 and the instructions are here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
You use the TF700 stock blob naturally, he did this on a 300 but it works just the same on this tablet.
Click to expand...
Click to collapse
Thank.I will let u know the results.

berndblb said:
I would recommend you flash the stock blob in fastboot and start over from scratch.
That's called a buster99 and the instructions are here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
You use the TF700 stock blob naturally, he did this on a 300 but it works just the same on this tablet.
Click to expand...
Click to collapse
Thank u very much. It Worked!You r a lifesaver..

You're welcome, glad it worked for you.
You may want to be a little more careful what and how you flash.