I can get into recovery but after that then to android with red exclamation or usb fastboot screen or fdr screen cold boot. Once I get to red x andy I can go no further. Tried all combo of button pushes and will not go to blue menu for clear cache partition fdr or re start. I am trying to clean cache . It just sits at Andy then after about 5 Min's tab reboots by itself. Have tried about 6 times same thing happens each time, Any idea what is happening or what I am doing wrong or is recovery clean cache partition gone? Thanks
Other wise JB install went smooth no problems and tab is working well . seems smoother . Also kept root with voodoo.
Same here...
I had this same issuethis once, after update with the same intention, was considering either clear cache or to do a full wipe from that level as opposed to doing it through settings. Almost had a stroke u I saw the animated android with the famous (or rather infamous red triangle) Ended up using the one in Backup and Restore in system settings. Think I will try this again, since this concerns me. Anyone else seeing this? If recovery is broken in JB, we have another wait on out hands. Sigh
ditto, starting to see a trend...
Same here, I've had no luck getting past the initial stock recovery screen. Not good.
When you flash OTA update you lose custom recovery.
i have custom recovery installed on JB but it is useless. nothing wants to mount.
ultramegaman963 said:
i have custom recovery installed on JB but it is useless. nothing wants to mount.
Click to expand...
Click to collapse
Same here. Seems as though mount points changed and I can't seem to get adb in twrp...
What is different?
cmdrdredd said:
When you flash OTA update you lose custom recovery.
Click to expand...
Click to collapse
I am using Asus stock recovery. When I got tablet it was on .22 rooted tab everything ok. got ota for .26 kept root all ok still could get into recovery got .30 ota kept root again with voodoo. everything o k got into recovery wiped cache no problem. got JB ota everything ok tried to get into recovery and my above post happened? I am confused as to how jb is now custom recovery versus all other otas. What has turned from stock recovery to custom recovery
Tomv5314 said:
I am using Asus stock recovery. When I got tablet it was on .22 rooted tab everything ok. got ota for .26 kept root all ok still could get into recovery got .30 ota kept root again with voodoo. everything o k got into recovery wiped cache no problem. got JB ota everything ok tried to get into recovery and my above post happened? I am confused as to how jb is now custom recovery versus all other otas. What has turned from stock recovery to custom recovery
Click to expand...
Click to collapse
I kept root with OTA Root Keeper. So I was able to reflash TWRP from Goomanager. But anyway it cannot mount either the internal storage nor the microSD card. There seems to be no working recovery for JB, yet.
FreakyPriest said:
I kept root with OTA Root Keeper. So I was able to reflash TWRP from Goomanager. But anyway it cannot mount either the internal storage nor the microSD card. There seems to be no working recovery for JB, yet.
Click to expand...
Click to collapse
That's not entirely accurate... if you mount /system in twrp, you will see externalSD is mounted instead. Kind of goofy. Messed me up good, since I expected to install supersu through recovery. Now I have no root and no useful recovery! Anyone know the mount point cure?
Sent from my ASUS Transformer Pad TF700T using xda premium
still nothing
xfinrodx said:
That's not entirely accurate... if you mount /system in twrp, you will see externalSD is mounted instead. Kind of goofy. Messed me up good, since I expected to install supersu through recovery. Now I have no root and no useful recovery! Anyone know the mount point cure?
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
Has anyone been able to get past red exclamation point andy in recovery mode yet?
http://forum.xda-developers.com/showthread.php?t=1886901
This recovery works with the JB Kernel. Flash it using fastboot.
FineWolf said:
http://forum.xda-developers.com/showthread.php?t=1886901
This recovery works with the JB Kernel. Flash it using fastboot.
Click to expand...
Click to collapse
I like a few others was stuck at the infamous red triangle with no way to get into TWRP. Lost custom recovery. Did the above mentioned in fastboot and was able to flash CWM and then was able to flash Supersu via CWM. Got me out of a jam, unfortunately missed the opportunity to NVFLASH on .26, had already upgaded to .30
merge thread?
amaury48 said:
I like a few others was stuck at the infamous red triangle with no way to get into TWRP. Lost custom recovery. Did the above mentioned in fastboot and was able to flash CWM and then was able to flash Supersu via CWM. Got me out of a jam, unfortunately missed the opportunity to NVFLASH on .26, had already upgaded to .30
Click to expand...
Click to collapse
Could one of the moderators merge this thread with Red triangle in locked stock recovery ? They are both concerning the same thing thanks Tom
Related
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
confuz said:
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
Click to expand...
Click to collapse
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
CyberdyneSystems said:
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
Click to expand...
Click to collapse
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
try this thread...otherwise...you need to RMA it to asus,or the store you bought it from
http://www.scottsroms.com/showthread.php/1637-Tf300t-sku?p=13102#post13102
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
probably the bootloader, looks for a simple command,file....its not there,so its stuck in a loop
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
First declare your bootloader. Have you ever been on a jb-rom, stock or otherwise?
Looking at git for cm it appears the kernel is 2.6, so I would expect that is not a jb rom.
cwm has some issues on this unit.
get into cwm and use fastboot to flash twrp for the proper bootloader you have.
or get into fastboot by use of power and volume down
at that point you can twrp a rom into place; probably not to restore your backup as twrp and cwm have issues reading each others backups.
Good Luck!
Note: If you can power up and access recovery (cwm in your case) you are not bricked and should be able to recover. I have as well as many others. Take your time and go a step at a time! Make back ups and make sure you have fastboot and adb access to your unit! If you are still ics bootloader consider nvflash once you have this mess sorted.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Dfanzz said:
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Click to expand...
Click to collapse
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
k4killer said:
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
Click to expand...
Click to collapse
Great that ur nandroid worked! I know they r working on it... dont really have a time frame... just be on the lookout
I was on locked on stock OTA JB.
I unlocked a few days ago, then last night flashed TWRP. Created a nandroid, then rooted.
Today I've spent several hours downloading ROMs, doing Titanium backups, surfing forums, backing up my personal files etc. i.e. using my tablet normally without problems.
I decided it was time to flash a ROM so booted in TWRP to create a fresh nandroid. Then when it finished I rebooted the system with the plan to copy the nandroid to my pc.
The tablet booted, but then after 30s or so rebooted. It's now stuck in this boot loop. So I tried a cold boot, and then restoring the latest nandroid and the problem persists. I'm currently trying to restore the pre root nandroid I made.
To recap - I am on stock OTA JB, with TWRP v2.3.1.0 recovery. Any thoughts?
Ok just to update - the pre root nandroid seems to be stable at the moment. So... What to do?
Should I reflash the recovery? Try a different recovery?
Any ideas why the nandroid would be borked when the system seemed stable when I created it?
Sent from my Galaxy Nexus using Tapatalk 2
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
No it doesn't, it just replaces stock recovery and allows you to gain root.
You could start your own thread. Or, you could read the thread in Android Development that gives clear instructions for noobs to gain root and install TWRP or CWM.
Sent from my Galaxy Nexus using Tapatalk 2
which ROM were you trying to flash? was it a JB rom?
bshpmark said:
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
Click to expand...
Click to collapse
After you install TWRP, you just need to flash a root zip file with TWRP to gain root..
bshpmark said:
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
Click to expand...
Click to collapse
Flash a rooted custom rom. ull gain root + rom easily
mike-y said:
which ROM were you trying to flash? was it a JB rom?
Click to expand...
Click to collapse
Since this thread got immediately hijacked i'm not sure but I'm going to assume this part of your post was aimed at me...
I wasn't trying to flash a ROM at all. I hadn't even got that far. All I'd done was flash the recovery, root it and then create a nandroid. It was creating the nandroid that seemed to trigger the boot loop, even though that makes zero sense.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
can you get back into fastboot connected to your PC?
I'd try to re-flash TWRP. Also make sure you are using the JB version, not the ICS version.
http://teamw.in/project/twrp2/97
I just unlocked and flashed TWRP on my tf300 (with the OTA JB update) this morning, and everything is working fine. I also flashed a root file without any issue.
I reflashed TWRP and re-rooted it seems to be OK.
Then I found I couldn't get any ROMs to work - they all froze at the boot screen. The solution to that problem lies in flashing the US update of JB rather that the WW. Now I'm running Hydro with Untermensch's kernel.
One thing I did notice with TWRP 2.3 is I get the error "can't mount /storage" in the log whenever I do anything. A bit of research suggests this might be an issue with TWRP 2.3, not present in 2.2. I wonder if that is what was causing the boot loop issue I had previously.
I can't seem to find a blob of 2.2 to downgrade to so I'm living with it for now and hope it's not going to cause problems down the line.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Good that TWRP always using the same names for a DL Link. So here is the 2.2 for JB Bootloader
If you are looking for ICS just edit the dl link .
http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.2.2.0-tf300tg-JB.blob
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The stock Asus firmware includes bootloader, kernel, recovery and apps. You have flashed the stock recovery. Head over to the twrp thread or my ROM thread in my sig to see how to get twrp 2.5 onto your tab.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
Yes, you did. Everytime you install stock file of any version, it will update your bootloader, rom, and kernel. Just use Motochopper to root your device and reinstall your custom recovery with goomanager.
No, it is stock recovery. Just reroot with motochopper and install custom recovery with goomanager. Have fun. :good:
Right, thanks! If I want to stay completely stock I just need to figure out why the newer update is failing. Could be the file name now I think about it.
Otherwise I'll re-root and re-TWRP...
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The Android on his back is your stock recovery and it does not find a valid update file.
Weird is, that your system seems to see the 10.6.1.14 file (I assume you get an automatic notification and click "install" or "update" ) and then the recovery does not seem to install it...?
You could have a bad download, so try that first if you want to get the latest stock rom, or you can try to rename the downloaded file to EP201_768_SDUPDATE.zip, put it on your microSD card and reboot into recovery. The recovery should recognize the update file and start flashing it.
But since you are unlocked anyway - why don't you give CromiX a try? It runs so much better than the stock rom!
And for that, yes you would have to root again using the Motochopper tool and then install TWRP 2.5 with Goo Manager.
If you go that route make sure you flash the latest bootloader from the OP of the CROMiX thread first, boot back into your old rom once before you flash CROMiX.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Anatosuchus said:
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Click to expand...
Click to collapse
It's based on the stock rom, cleaned up and tweaked and optimized. Everything works - and better than on stock! I recommend selecting the option to disable fsync during installation. It boosts performance considerably, and since the rom is totally stable, the "risk" is neglible.
You will love it!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
OK, ChromiX installed! Looks interesting already, will tinker with it over the next couple of days.
Hi
At the weekend I tried to update my TF300T from CM10.1 to CM10.2. That didn't work as I ended up in a boot loop. Then I thought, maybe I need to flash the latest system blob.
So I did that, only to find that I then couldn't install anything from zip or sd card as the recovery would not mount anything at all. Still got fastboot, so I've tried TWRP 2.6. TWRP 2.5, TWRP 2.4 and CWM, none of them will mount anything at all.
So I find myself with stock ROM, but no way of rooting or installing any custom ROMs.
I'm sure I've made a bloop somewhere, so all suggestions to resolve welcome!
Thanks
Rob
What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.
aarsyl said:
What is your bootloader? Sometimes, if you reflash the same recovery, it *may* work properly the second time around.
I am using TWRP 2.6 with my 127.5 bootloader, just for your knowledge.
Click to expand...
Click to collapse
That was the tip I needed - I knew I had the right bootloader but I had downloaded the wrong TWRP (I had flashed the JB version instead of the 4.3 version). Doh!
Now flashed CM10.2 and is running Android 4.3. CPU-Z tells me I'm rooted though at the moment I can't get any root apps to work with SuperSU. I'll leave that for another day!
Rob
I have the Nvidia Shield 16 Gig Wifi tablet and Ive only had it for about 2 months. I wanted to unroot and completely go back to out of the box settings. I flashed the stock recovery, and boot. When i flash system.img it says insufficient space. Im really freaking out over this. I now have CWM running as recovery, but im stuck in a bootloop/softbrick. Ive had this with other tablets before but it was fixable, Im stumped with this one. I really need help here. Please and thank you for help, I need it ASAP.
ProSniper54 said:
I have the Nvidia Shield 16 Gig Wifi tablet and Ive only had it for about 2 months. I wanted to unroot and completely go back to out of the box settings. I flashed the stock recovery, and boot. When i flash system.img it says insufficient space. Im really freaking out over this. I now have CWM running as recovery, but im stuck in a bootloop/softbrick. Ive had this with other tablets before but it was fixable, Im stumped with this one. I really need help here. Please and thank you for help, I need it ASAP.
Click to expand...
Click to collapse
So, basically you left your shield tablet without a rom installed? If you have CWM recovery, you could flash a Full OTA found here http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
It happened to me to. So I downloaded a Philz built in Jan (I googled it)**** and I flashed the full 2.1 ota.
You could flash the TWRP 2.8.5.0 found here:http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90 and then flash the full ota.
Then, Im thinking, you could flash stock recovery. I'd recommend flashing TWRP though, I had a problem with CWM and I could not flash full 2.1 OTA with it.
PS: Did you try wiping system from CWM and then flashing system with fastboot?
****EDIT: I found the Philz I used: https://goo.im/devs/playground/shieldtablet/Philz_Touch-01-02-2015_14.18-TN8-WiFi.zip
but Ive moved forward to TWRP since I couldn't make nandroid backups with it.
NaminatoR1254jaime.sier said:
So, basically you left your shield tablet without a rom installed? If you have CWM recovery, you could flash a Full OTA found here http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
It happened to me to. So I downloaded a Philz built in Jan (I googled it)**** and I flashed the full 2.1 ota.
You could flash the TWRP 2.8.5.0 found here:http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90 and then flash the full ota.
Then, Im thinking, you could flash stock recovery. I'd recommend flashing TWRP though, I had a problem with CWM and I could not flash full 2.1 OTA with it.
PS: Did you try wiping system from CWM and then flashing system with fastboot?
****EDIT: I found the Philz I used: https://goo.im/devs/playground/shieldtablet/Philz_Touch-01-02-2015_14.18-TN8-WiFi.zip
but Ive moved forward to TWRP since I couldn't make nandroid backups with it.
Click to expand...
Click to collapse
Okay I have to thank you a ton for getting my tablet working again. Only problem now, I cant system update anymore, I get an android guy with a red warning sign in him. Any suggestions?
ProSniper54 said:
Okay I have to thank you a ton for getting my tablet working again. Only problem now, I cant system update anymore, I get an android guy with a red warning sign in him. Any suggestions?
Click to expand...
Click to collapse
Probably because you have custom recovery still or you are rooted.
The android red guy happens bc you are rooted (it'll happen even if you have stock recovery).
To system update, you have to be without custom recovery AND unrooted.
EDIT: Im theoretically speaking. I am rooted, therefore, I dont update via OTA.
i tried to recover to factory but i am stuck at system.img which dun seem to be copying into my tablet i manage to flash twrp in and wat else can i do to make it working again?
thanks