Related
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.
So, after finally deciding to upgrade from 4.1 to 4.2.1 I inadvertently installed just the JB TWRP recovery.
Won't do anything but sit on the asus screen and repeatedly flash
So, after trying to flash the proper recovery (and the 4.2.1 update) multiple times. I decided I'll try downgrading back to 4.1
That worked. I'm back on the 4.1 bootloader.
GREAT!! Flashed back to the 2.5 TWRP for 4.1 Alls, good, it gets me into recovery and able to see partitions and stuff.
Try to restore from my backup gets me a failed on it.
wipe everything(save for sd card)
Factory reset
restore just boot partition SUCCESS!
restore both boot and system SUCCESS!!
reboot. nada
Any help, would be appreciated.
It IS Lupus said:
So, after finally deciding to upgrade from 4.1 to 4.2.1 I inadvertently installed just the JB TWRP recovery.
Won't do anything but sit on the asus screen and repeatedly flash
So, after trying to flash the proper recovery (and the 4.2.1 update) multiple times. I decided I'll try downgrading back to 4.1
That worked. I'm back on the 4.1 bootloader.
GREAT!! Flashed back to the 2.5 TWRP for 4.1 Alls, good, it gets me into recovery and able to see partitions and stuff.
Try to restore from my backup gets me a failed on it.
wipe everything(save for sd card)
Factory reset
restore just boot partition SUCCESS!
restore both boot and system SUCCESS!!
reboot. nada
Any help, would be appreciated.
Click to expand...
Click to collapse
Make sure the nandroid you are trying to restore is on an external sd card and then format data form within the wipe screen. Sounds like your data partition got corrupted.
sbdags said:
Make sure the nandroid you are trying to restore is on an external sd card and then format data form within the wipe screen. Sounds like your data partition got corrupted.
Click to expand...
Click to collapse
Thank you. This worked. I'm back up and running
Sent from my HTC6435LVW using xda app-developers app
It IS Lupus said:
Thank you. This worked. I'm back up and running
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
You are welcome! :good:
If you still want to update to 4.2.1 (i did it just for a friend that wanted root and wanted to test out cm10.2) and got some probs with partition mounting as well.
i earlier posted a solution for a nother prob (but it deals with PIT probs) ( http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 ) and it solved it without the need to downgrade.
cheers
-Buster
Buster99 said:
If you still want to update to 4.2.1 (i did it just for a friend that wanted root and wanted to test out cm10.2) and got some probs with partition mounting as well.
i earlier posted a solution for a nother prob (but it deals with PIT probs) ( http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 ) and it solved it without the need to downgrade.
cheers
-Buster
Click to expand...
Click to collapse
Just to clarify, when you force fastboot by paper clip resetting+volume down, the screen should show something like "entering fastboot/download mode..." correct? Failing that, with just the Asus logo and "the device is unlocked", then it's not in fastboot mode at all, right? Because I tried your method, but when issuing fastboot commands, PC says "waiting for device." "Fastboot devices" returns no serial number. How many times should I try to jump-start the hardware, do you think? Thanks.
its like normal fastboot
when you see rck, android, wipe data - this is fastboot mode(check top left corner)
cheers
-Buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
greydelta38 said:
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
Click to expand...
Click to collapse
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
greydelta38 said:
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
Click to expand...
Click to collapse
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
JoinTheRealms said:
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
Click to expand...
Click to collapse
Yeah - I'm also wondering what bootloader you are running with it.
If you are not current on either flash the bootloader/TWRP package from CROMi-X OP, boot back into system, let it bootloop if it does, boot back into TWRP and reflash the rom.
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
greydelta38 said:
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
Click to expand...
Click to collapse
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
berndblb said:
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
Click to expand...
Click to collapse
sbdags said:
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
Click to expand...
Click to collapse
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
greydelta38 said:
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
Click to expand...
Click to collapse
You need to specifically format data in twrp not just wipe data. Only formatting will restore the device now once data corruption has occurred.
My buddy is having a hard time flashing a new ROM on his tablet. Currently he's running Cyanogen with TWRP.
Apparently TWRP formatted his tablet randomly and he hasn't been able to install a new ROM because his tablet won't mount the system or cache. It keeps failing. Neither system or cache are selectable to mount and it says "E: unable to mount '/system' "
And ADB isn't pushing anything.
Any thoughts why?
Sunset Rider said:
My buddy is having a hard time flashing a new ROM on his tablet. Currently he's running Cyanogen with TWRP.
Apparently TWRP formatted his tablet randomly and he hasn't been able to install a new ROM because his tablet won't mount the system or cache. It keeps failing. Neither system or cache are selectable to mount and it says "E: unable to mount '/system' "
And ADB isn't pushing anything.
Any thoughts why?
Click to expand...
Click to collapse
TWRP formatted his tablet randomly??? Never heard of such a thing!
And we need more information:
What versions of bootloader, CM, TWRP and you are trying to push what in ADB?
Do you have access to fastboot? What rom are you trying to flash?
What did he do - as best as he can remember?
berndblb said:
TWRP formatted his tablet randomly??? Never heard of such a thing!
And we need more information:
What versions of bootloader, CM, TWRP and you are trying to push what in ADB?
Do you have access to fastboot? What rom are you trying to flash?
What did he do - as best as he can remember?
Click to expand...
Click to collapse
It wiped his data when he went to decrypt data and it asked for a password. He hit cancel and it said system memory 0gb
He has the newest twrp, he was on 10.2 trying to go to 11, and he was trying to push the mounting through adb and was getting errors. Because he is unable to select them In twrp
He has fastboot but it doesn't respond to commands at all.
Thank you for any help
fastboot
Sunset Rider said:
It wiped his data when he went to decrypt data and it asked for a password. He hit cancel and it said system memory 0gb
He has the newest twrp, he was on 10.2 trying to go to 11, and he was trying to push the mounting through adb and was getting errors. Because he is unable to select them In twrp
He has fastboot but it doesn't respond to commands at all.
Thank you for any help
Click to expand...
Click to collapse
Sounds like a soft brick.. Due to a wrong recovery flash or he flashed the newest version of twrp, and did a full data wipe.. It has known issues!!!!!
Becareful from here.. Like berndblb said we need verify we still have fastboot access!!:fingers-crossed:
What is the OS of the PC your using to fastboot from??
Well I tried installing cromi for him and it stalls at 87%
Sunset Rider said:
Well I tried installing cromi for him and it stalls at 87%
Click to expand...
Click to collapse
UPDATE: We restarted the tablet, mid installation because it froze, and it booted up to his old 10.2 just fine. I recommended he do a clean format now but he doesn't want to do anything lol.
So right now I'm just thanking God he didn't brick it hard
Sunset Rider said:
It wiped his data when he went to decrypt data and it asked for a password. He hit cancel and it said system memory 0gb
Click to expand...
Click to collapse
Did he have the tablet encrypted or did the request for a decryption password just show up unexpectedly? If it's the latter - I have read about this a number of times - unfortunately still cannot make rhyme or reason out of it, but I suspect it's a corrupted recovery....
He has the newest twrp, he was on 10.2 trying to go to 11, and he was trying to push the mounting through adb and was getting errors. Because he is unable to select them In twrp
Click to expand...
Click to collapse
The newest meaning 2.6.3.2?
He has fastboot but it doesn't respond to commands at all.
Thank you for any help
Click to expand...
Click to collapse
Which probably means he doesn't have the correct fastboot drivers installed. That would No. 1: Get fastboot working. Download the Google Universal Naked drivers, install them and try
Code:
fastboot devices
If that returns the tablet's serial number, you're in business. You could then flash CWM 6.0.4.6 in fastboot. I would probably wipe data (hope he has everything backed up) and flash the rom.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
lj50036 said:
Sounds like a soft brick.. Due to a wrong recovery flash or he flashed the newest version of twrp, and did a full data wipe.. It has known issues!!!!!
Becareful from here.. Like berndblb said we need verify we still have fastboot access!!:fingers-crossed:
What is the OS of the PC your using to fastboot from??
Click to expand...
Click to collapse
@lj50036 could you elaborate on the issues of TWRP 2.6.3.2.? sbdags included it it in his bootloader/TWRP flash package for CROMi-X and one guy just softbricked flashing CROMi_X after flashing that package, he seems to have done everything else correctly and I suspect the recovery is buggy???
TWRP
could you elaborate on the issues of TWRP 2.6.3.2.? sbdags included it it in his bootloader/TWRP flash package for CROMi-X and one guy just softbricked flashing CROMi_X after flashing that package, he seems to have done everything else correctly and I suspect the recovery is buggy???
Click to expand...
Click to collapse
My issues are first hand.. It flashes just fine, everything seems to function correctly.. It's only the wiping of data that has a issue.... It just hangs says its doing it thing but nothing ever happens..After a hard reboot TWRP now asking for password will not mount any storage of any kind... The fastest way to a soft brick.... I posted on the TWRP forum, about the issue... Maybe we need a new forum letting people know about the issue, so we dont end up with a riot!!!
lj50036 said:
My issues are first hand.. It flashes just fine, everything seems to function correctly.. It's only the wiping of data that has a issue.... It just hangs says its doing it thing but nothing ever happens..After a hard reboot TWRP now asking for password will not mount any storage of any kind... The fastest way to a soft brick.... I posted on the TWRP forum, about the issue... Maybe we need a new forum letting people know about the issue, so we dont end up with a riot!!!
Click to expand...
Click to collapse
Thanks! Though I would love to see what a riot on XDA looks like LOL
berndblb said:
Did he have the tablet encrypted or did the request for a decryption password just show up unexpectedly? If it's the latter - I have read about this a number of times - unfortunately still cannot make rhyme or reason out of it, but I suspect it's a corrupted recovery....
The newest meaning 2.6.3.2?
Which probably means he doesn't have the correct fastboot drivers installed. That would No. 1: Get fastboot working. Download the Google Universal Naked drivers, install them and try
Code:
fastboot devices
If that returns the tablet's serial number, you're in business. You could then flash CWM 6.0.4.6 in fastboot. I would probably wipe data (hope he has everything backed up) and flash the rom.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
@lj50036 could you elaborate on the issues of TWRP 2.6.3.2.? sbdags included it it in his bootloader/TWRP flash package for CROMi-X and one guy just softbricked flashing CROMi_X after flashing that package, he seems to have done everything else correctly and I suspect the recovery is buggy???
Click to expand...
Click to collapse
It was version 2.6.3.0.
He had no decrypted files he was just seeing what it did when he hit decrypt data. I asked for a password which he obviously never set and hit cancel. And it said he had nothing in internal storage.
However, after the install froze on an older Cromi version I put on his sd card (from my 700t), we held down the power button and rebooted. It booted up fine to his previous Cyanogen 10.2. WITH all of his internal storage still there, EVEN THOUGH, he did a format from TWRP already.
So it's definitely a problem with TWRP. His tablet is back to the way it was before the fiasco and he is afraid to do anything else.
Sunset Rider said:
It was version 2.6.3.0.
He had no decrypted files he was just seeing what it did when he hit decrypt data. I asked for a password which he obviously never set and hit cancel. And it said he had nothing in internal storage.
However, after the install froze on an older Cromi version I put on his sd card (from my 700t), we held down the power button and rebooted. It booted up fine to his previous Cyanogen 10.2. WITH all of his internal storage still there, EVEN THOUGH, he did a format from TWRP already.
So it's definitely a problem with TWRP. His tablet is back to the way it was before the fiasco and he is afraid to do anything else.
Click to expand...
Click to collapse
Are you sure about this???
Because TWRP 2.6.3.0 was too big for the recovery partition of the TF700 and never properly installed????
For any reliable advice you need to provide the bootloader version (which you still haven't given us) and if you have a working system, you should be able to boot into recovery and give us it's version number.
For installing CM 11 on the TF700 you need to be on the 10.6.1.14.10 bootloader and have the CWM 6.0.4.6 recovery.
TWRP 2.6.3.2 supposedly works with CM 11, but I would not trust it - read about too many problems with it....
And anyway - in terms of performance, neither CM 10.2 or CM 11 beats CROMi-X on this tablet - period.
Here I am
berndblb said:
Are you sure about this???
Because TWRP 2.6.3.0 was too big for the recovery partition of the TF700 and never properly installed????
For any reliable advice you need to provide the bootloader version (which you still haven't given us) and if you have a working system, you should be able to boot into recovery and give us it's version number.
For installing CM 11 on the TF700 you need to be on the 10.6.1.14.10 bootloader and have the CWM 6.0.4.6 recovery.
TWRP 2.6.3.2 supposedly works with CM 11, but I would not trust it - read about too many problems with it....
And anyway - in terms of performance, neither CM 10.2 or CM 11 beats CROMi-X on this tablet - period.
Click to expand...
Click to collapse
Hey guys, this is Wade, the cause of the whole fiasco.
It was the newest TWRP 2.3.6.2, but I imagine it might've been a problem with the bootloader? I had no idea that the bootloader needed updating; I thought that once you could boot what you wanted, that was it, but obviously I'm mistaken. Where do I find the bootloader version? It was the latest posting to the Asus download site, or the V8, 2013 bootloader edition for JB. 4.2
Basically, I had tried several times that day installing CM11 and the gapps with CWM 6.0.3.1 (which ROM manager says is the up to date version? WTF?) to no avail. It kept giving me md5sum errors, and I couldn't find anything to easily fix that. CWM would also not respond to commands from ROM manager other than backups... If i told it to bootload and flash, it would just reboot normally... ADB also would fail, despite saying that i COULD connect to fastboot.
So i read on the actual CM forum that the newest TWRP 2.6.3.2 would do the trick as well, and tried that. But ya, once i booted into twrp, it threw a password query at me. I never set a password, so I pressed cancel, and that's when the partition showed up as blank.
I went to reboot, but it warned that I had no OS installed. That's about when I freaked out. It would see my microSD fine, but wasn't able to talk to /system to actually flash anything, and ADB would just give "error:closed" if I tried any mount commands there.
So ya, I invited my buddy over, and he recommended we try flashing an old CROMI-X, and it WORKED! sort of. It started to flash, even though a previous CM 10.2 and it's gapps (which I was already running and knew worked) wouldn't!
Then it froze installing Youtube, and after ten mins we held down the power.
And it booted back into CM 10.2 like nothing had happened.
Even though TWRP said I had succesfully factory reset AND wiped AND formatted the internal by that point. Lies!
So ya, I imagine it's a combination of pilot error, and TWRP being a little fluky. My question - where did that 87% CROMI-X flash go, and how can I get rid of it? And i reflashed CWM 6.0.3.1, but I'm still wary of going into the bootloader, just in case bastard TWRP is still lurkin
UPDATE
Wadesauce said:
I had no idea that the bootloader needed updating; I thought that once you could boot what you wanted, that was it, but obviously I'm mistaken. Where do I find the bootloader version? It was the latest posting to the Asus download site, or the V8, 2013 bootloader edition for JB. 4.2
Click to expand...
Click to collapse
So it was definitely the old ASUS 4.2 bootloader I was using. I had no idea that dasunsrule32 wanted us to use his April 2013 bootloader for 10.2 as well, the site that told me how to put CM 10.2 on my tab said to use the old ASUS one.
Finally manned up and tried my first soft reboot, and it brought up the ASUS menu with the blue loading bar - it seemed like it wanted to go into bootloader. Then it went blank and the regular ASUS logo showed, and then the CM logo and booted. So i didn't walk away from this unscathed; something low-down got messed with...
Can I update the bootloader to his, despite the problems ive been having? How do I do that?
And why does ROM manager only offer 6.0.3.1??
And since CM11 is based on 4.4, wont it eventually be better than CROMi-X?
Wadesauce said:
So it was definitely the old ASUS 4.2 bootloader I was using. I had no idea that dasunsrule32 wanted us to use his April 2013 bootloader for 10.2 as well, the site that told me how to put CM 10.2 on my tab said to use the old ASUS one.
So can I update the bootloader to his, despite the problems ive been having? How do I do that?
And why does ROM manager only offer 6.0.3.1??
And since CM11 is based on 4.4, wont it eventually be better than CROMi-X?
Click to expand...
Click to collapse
Can you still boot into fastboot mode on your tablet and can your PC see the tablet in fastboot mode?? What is the OS on your PC??
i dunno
lj50036 said:
Can you still boot into fastboot mode on your tablet and can your PC see the tablet in fastboot mode?? What is the OS on your PC??
Click to expand...
Click to collapse
I haven't tried booting into bootloader, or even a full power down/power up yet. This is the device I use for school and right now would be a pretty sh**y time for anything serious to happen to it.
I am mainly afraid that TWRP hasn't left yet, or that I won't be able to access the CWM that ROM manager says I just successfully reflashed.
I don't really want to plug it back into the computer until I know more about what happened to it. Is it likely that the CROMI that we tried flashing or the old TWRP will cause me problems? Remember that CROMI said it was 87% successful (had loaded kernel and system and all that jazz)
And I have 64 bit Win7, it should have appropriate drivers
Feedback
Wadesauce said:
I haven't tried booting into bootloader, or even a full power down/power up yet. This is the device I use for school and right now would be a pretty sh**y time for anything serious to happen to it.
I am mainly afraid that TWRP hasn't left yet, or that I won't be able to access the CWM that ROM manager says I just successfully reflashed.
I don't really want to plug it back into the computer until I know more about what happened to it. Is it likely that the CROMI that we tried flashing or the old TWRP will cause me problems? Remember that CROMI said it was 87% successful (had loaded kernel and system and all that jazz)
And I have 64 bit Win7, it should have appropriate drivers
Click to expand...
Click to collapse
Well you just let me know.. I will be here to help out if you would like it ....As always thx lj
Wadesauce said:
Hey guys, this is Wade, the cause of the whole fiasco.
It was the newest TWRP 2.3.6.2, but I imagine it might've been a problem with the bootloader? I had no idea that the bootloader needed updating; I thought that once you could boot what you wanted, that was it, but obviously I'm mistaken. Where do I find the bootloader version? It was the latest posting to the Asus download site, or the V8, 2013 bootloader edition for JB. 4.2
Basically, I had tried several times that day installing CM11 and the gapps with CWM 6.0.3.1 (which ROM manager says is the up to date version? WTF?) to no avail. It kept giving me md5sum errors, and I couldn't find anything to easily fix that. CWM would also not respond to commands from ROM manager other than backups... If i told it to bootload and flash, it would just reboot normally... ADB also would fail, despite saying that i COULD connect to fastboot.
So i read on the actual CM forum that the newest TWRP 2.6.3.2 would do the trick as well, and tried that. But ya, once i booted into twrp, it threw a password query at me. I never set a password, so I pressed cancel, and that's when the partition showed up as blank.
I went to reboot, but it warned that I had no OS installed. That's about when I freaked out. It would see my microSD fine, but wasn't able to talk to /system to actually flash anything, and ADB would just give "error:closed" if I tried any mount commands there.
So ya, I invited my buddy over, and he recommended we try flashing an old CROMI-X, and it WORKED! sort of. It started to flash, even though a previous CM 10.2 and it's gapps (which I was already running and knew worked) wouldn't!
Then it froze installing Youtube, and after ten mins we held down the power.
And it booted back into CM 10.2 like nothing had happened.
Even though TWRP said I had succesfully factory reset AND wiped AND formatted the internal by that point. Lies!
So ya, I imagine it's a combination of pilot error, and TWRP being a little fluky. My question - where did that 87% CROMI-X flash go, and how can I get rid of it? And i reflashed CWM 6.0.3.1, but I'm still wary of going into the bootloader, just in case bastard TWRP is still lurkin
Click to expand...
Click to collapse
Jeez - where to start?
First of all: Do yourself a favor and ditch ROM Manager. It does not work well with the TF700 and several people have hard bricked using it. You have been very lucky so far!
Second: Do not flash anything until you are 150% sure you know what you are doing, you understand the requirements for your situation and have everything you need at hand.
Do not flash anything EVER if you do not know what bootloader version you have. That's like getting into your car blind folded and trusting that your GPS will drive you safely to your destination.
Every ROM has it's requirements in terms of bootloader version and recovery and they are usually clearly stated in the first couple of paragraphs in the OP of the rom thread. If not: Stay away from that rom unless you know exactly what you are doing!
TWRP 2.6.3.2 has major issues when formatting data from it. Stay away from it for now.
To find out what you can do to get a stable system back, you need to know where you are and what you have.
Boot into the bootloader (and do not use ROM Manager to do it!) and read the tiny script. It'll probably be 10.6.1.14.10 or .8
Post the result.
Boot into the recovery to check what you have installed. Versions matter!
The proper way of installing a custom recovery is in fastboot mode. Which is different from ADB, btw - you've been mixing those up I think.
Google "adb fastboot tutorial" and do some reading. Once you understand, get it set up on your PC, boot the tablet into the bootloader, connect both via original USB cable and test the connection with
Code:
fastboot devices
If it returns the serial number of your tablet, you are in business and we can continue from there.
Happy studying!
Getting there...
berndblb said:
Google "adb fastboot tutorial" and do some reading. Once you understand, get it set up on your PC, boot the tablet into the bootloader, connect both via original USB cable and test the connection with
Code:
fastboot devices
If it returns the serial number of your tablet, you are in business and we can continue from there.
Happy studying!
Click to expand...
Click to collapse
Alright, I have done some reading as far as all of this goes. I understand a lot of it better now.
So I'm positive now that it was because I hadn't updated my bootloader before trying through CWM. And TWRP obviously was no more useful.
I haven't quite checked what the bootloader version is - I think there may be something wrong with it still (given my weird boot-up) and I don't want to go there until I'm totally sure what I'm doing. I'd hate to hit bootloader and then realize something was seriously wrong, and my time was ticking.
However, I have never changed the bootloader since I used ASUS's one from their website originally - since it says v8, I imagine thats the .8 one?
Before I uninstalled ROM manager, I checked what it said my recovery was - and it said I had CWM 6.0.3.1 still, even though the TWRP fiasco has just gone down. I used ROM to reflash the same 6.0.3.1 from the device, and it said it was successful.
So before I begin, could i possibly ask a few questions?
1) Could I have corrupted the bootloader?
2) Can more than one recovery exist? Is it maybe true that CWM 6.0.3.1 would be the one I will boot into if I went into recovery? I REALLY don't want it to be TWRP again as it might not survive the experience (I had put TWRP on via fastboot). Should I just get to bootloader, flash a new recovery right away and go from there?
3) When I go to finally solve it, what are the hypothetical steps I should take? Right now, as far as I can tell, it will be:
a) Make sure all drivers are working, and files (including backup) are on my PC.
b) reboot into bootloader, check version.
c) flash the 10.6.1.14.4 bootloader
d) reboot
e) reboot into bootloader
f) flash CWM. 6.0.4.6
g) reboot
i) reboot into bootloader, into recovery, then flash CM 11 and gapps
j) reboot
Ya? No? Any help would be appreciated
Wadesauce said:
Alright, I have done some reading as far as all of this goes. I understand a lot of it better now.
So I'm positive now that it was because I hadn't updated my bootloader before trying through CWM. And TWRP obviously was no more useful.
I haven't quite checked what the bootloader version is - I think there may be something wrong with it still (given my weird boot-up) and I don't want to go there until I'm totally sure what I'm doing. I'd hate to hit bootloader and then realize something was seriously wrong, and my time was ticking.
However, I have never changed the bootloader since I used ASUS's one from their website originally - since it says v8, I imagine thats the .8 one?
Before I uninstalled ROM manager, I checked what it said my recovery was - and it said I had CWM 6.0.3.1 still, even though the TWRP fiasco has just gone down. I used ROM to reflash the same 6.0.3.1 from the device, and it said it was successful.
So before I begin, could i possibly ask a few questions?
1) Could I have corrupted the bootloader?
2) Can more than one recovery exist? Is it maybe true that CWM 6.0.3.1 would be the one I will boot into if I went into recovery? I REALLY don't want it to be TWRP again as it might not survive the experience (I had put TWRP on via fastboot). Should I just get to bootloader, flash a new recovery right away and go from there?
3) When I go to finally solve it, what are the hypothetical steps I should take? Right now, as far as I can tell, it will be:
a) Make sure all drivers are working, and files (including backup) are on my PC.
b) reboot into bootloader, check version.
c) flash the 10.6.1.14.4 bootloader
d) reboot
e) reboot into bootloader
f) flash CWM. 6.0.4.6
g) reboot
i) reboot into bootloader, into recovery, then flash CM 11 and gapps
j) reboot
Ya? No? Any help would be appreciated
Click to expand...
Click to collapse
1. No, your bootloader is still good because you still can boot into your system. You need your bootloader to initiate your hardware before your OS is booting.. I am very sure that is the case but it would be nice for someone to confirm it...
2. Your recovery partition is too small for two custom recoveries to exist. So it is almost impossible for you to have two recoveries..
Before you want to go further, it is easier to find out your bootloader and recovery versions so you know what is the next step that you need to do. Otherwise, it is just a guess or a shot in the dark... I think that you are fine but you need to wait for some experts to confirm it... Good luck...:fingers-crossed:
Please bear with me
LetMeKnow said:
Before you want to go further, it is easier to find out your bootloader and recovery versions so you know what is the next step that you need to do. Otherwise, it is just a guess or a shot in the dark... I think that you are fine but you need to wait for some experts to confirm it... Good luck...:fingers-crossed:
Click to expand...
Click to collapse
Sorry hahah, I know I must seem really frustrating...
I have held off for 2 reasons:
1. The first time I did a soft reboot after my fiasco, upon boot it went through the first series of steps trying to load into the bootloader, but then booted fine. Another time a few days after, it rebooted while i was using it, and just went blank after the asus logo. Holding the power down caused it to boot fine. Still, neither of those had ever happened before, and I am pretty sure that some point along the line of bootloader-->OS something is broken. Hopefully on the OS side.
2. I am not going to attempt to boot into recovery until I know that it isn't the same TWRP 2.6.3.2 that got me into this whole fiasco. I know it sounds like a catch 22, not wanting to reboot into recovery to check what it is, but I have NO IDEA how to get out of this TWRP as it stands. I had to flash a CROMI (which failed at 87%) and hard reboot. Not willing to go out on a limb and assume that hard-reboot will work during any step of that process.
So, why do I have to check it? Can't I boot into bootloader, flash a new bootloader, flash a new recovery, and then reboot normally? Assuming I'll be able to establish fastboot (drivers still work, so fingers crossed on that one).
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