Database Info

[Q] TF101G back to stock rom.

Hi guys,
I've been thinkin about selling my TF101g and buy a new model, but my tablet has custom recovery and Rom, and I would like turn it all stock, and i couldn't find any thread to the Tf101g.
Can somebody help me with a thread that works?

lennao said:
Hi guys,
I've been thinkin about selling my TF101g and buy a new model, but my tablet has custom recovery and Rom, and I would like turn it all stock, and i couldn't find any thread to the Tf101g.
Can somebody help me with a thread that works?
Click to expand...
Click to collapse
Hi, I'm new to this forum (first post).
I had the same problem - e.g. I wanted to return to stock. I flashed ' PERI 1-click recovery' and the latest version of Revolver custom ROM for the TF101G but I couldn't get 3G to work (unknown Baseband), and PERI wouldn't let me flash the stock ROM - it gave an error 'assert failed' 'Status 7'.
Thought I'd b*****d it thoroughly and couldn't find a thread telling me how to get back to Stock, but trial and error prevailed.
This is what I did (assume you already have ROOT and a custom recovery installed):
1. Download the latest ASUS stock ROM zip from the ASUS site to the PC. Make sure you select the right one for your model (mine's the WW TF101G version)
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101G&p=20&s=16
2. For some reason ASUS put the stock ROM zip image inside another zip file, so extract it from the downloaded zip file and copy the extracted stock ROM zip (e.g. WW_epad-user-9.2.2.6.zip) to TF101G Internal Storage (not an external SD)
3. The custom recovery you have installed my allow you to flash the stock ROM, in which case just do steps 7 and then 10 onwards. Mine (PERI) gave me an Assert Failed error, in which case ....
4. Download ClockWork Recovery for the Transformer. I used Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3 from this site and it worked just fine. I don't know which other versions work and which don't:
http://forum.xda-developers.com/showthread.php?t=1577929
5. Copy the downloaded Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip to TF101G Internal Storage (not external SD)
6. Now boot the TF101G into recovery mode (Power + Volume Down until prompt appears, then Volume Up for recovery)
7. Wipe all caches (including the user data cache)
8. Flash Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip - you'll see lots of scrolling @@@@@@@s, don't worry that's normal
9. Once the Install is complete, Boot into recovery mode again - you should now be in Clockwork Recovery V5.8.1.8
10. Flash the stock ROM (e.g. WW_epad-user-9.2.2.6.zip). Wait until the install is complete.
11. Reboot normally. You will see a blue status bar which will take a while to complete and then it will reboot itself, you may see a message 'Android is Updating' which will also take a while to complete.
After doing this, you should now have the stock ROM, stock recovery, no ROOT and you will be asked to set up the Tablet for the first time, i.e. back to stock.
P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data.
Hope this helps.

i dont understand. If youre going to sell the tf101 why not load it up with custom overclockable kernel, new JB rom, and a custom touch recovery? those are added features compared to a lame stock version of the transformer.

serafis said:
Hi, I'm new to this forum (first post).
I had the same problem - e.g. I wanted to return to stock. I flashed ' PERI 1-click recovery' and the latest version of Revolver custom ROM for the TF101G but I couldn't get 3G to work (unknown Baseband), and PERI wouldn't let me flash the stock ROM - it gave an error 'assert failed' 'Status 7'.
Thought I'd b*****d it thoroughly and couldn't find a thread telling me how to get back to Stock, but trial and error prevailed.
This is what I did (assume you already have ROOT and a custom recovery installed):
1. Download the latest ASUS stock ROM zip from the ASUS site to the PC. Make sure you select the right one for your model (mine's the WW TF101G version)
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101G&p=20&s=16
2. For some reason ASUS put the stock ROM zip image inside another zip file, so extract it from the downloaded zip file and copy the extracted stock ROM zip (e.g. WW_epad-user-9.2.2.6.zip) to TF101G Internal Storage (not an external SD)
3. The custom recovery you have installed my allow you to flash the stock ROM, in which case just do steps 7 and then 10 onwards. Mine (PERI) gave me an Assert Failed error, in which case ....
4. Download ClockWork Recovery for the Transformer. I used Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3 from this site and it worked just fine. I don't know which other versions work and which don't:
http://forum.xda-developers.com/showthread.php?t=1577929
5. Copy the downloaded Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip to TF101G Internal Storage (not external SD)
6. Now boot the TF101G into recovery mode (Power + Volume Down until prompt appears, then Volume Up for recovery)
7. Wipe all caches (including the user data cache)
8. Flash Clockwork_Recovery_5.8.1.8_by_JvS_Corp_V3.zip - you'll see lots of scrolling @@@@@@@s, don't worry that's normal
9. Once the Install is complete, Boot into recovery mode again - you should now be in Clockwork Recovery V5.8.1.8
10. Flash the stock ROM (e.g. WW_epad-user-9.2.2.6.zip). Wait until the install is complete.
11. Reboot normally. You will see a blue status bar which will take a while to complete and then it will reboot itself, you may see a message 'Android is Updating' which will also take a while to complete.
After doing this, you should now have the stock ROM, stock recovery, no ROOT and you will be asked to set up the Tablet for the first time, i.e. back to stock.
P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data.
Hope this helps.
Click to expand...
Click to collapse
thx man, i'll try this at home tonight!!

haxin said:
i dont understand. If youre going to sell the tf101 why not load it up with custom overclockable kernel, new JB rom, and a custom touch recovery? those are added features compared to a lame stock version of the transformer.
Click to expand...
Click to collapse
because it doesn't exist a JB ROM with 3G working, and usually, when i'll sell something, i prefer selling with the stock image, it's more guarantee that will work properly, like when leaving the store, so they can root and change roms themselves.

lennao said:
thx man, i'll try this at home tonight!!
Click to expand...
Click to collapse
In my post, where I said "P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data", I meant "...without losing your apps / settings / data". That way you can carry on using it until you sell it, and then just do a factory reset once you have a buyer.
Good luck.

serafis said:
In my post, where I said "P.S. If you don't wipe the User Data cache, you can flash to stock without using your apps / settings / data", I meant "...without losing your apps / settings / data".
Good luck.
Click to expand...
Click to collapse
hey,
i would like to thank you, your tutorial works fine! and was pretty easy too, nothing complicated.
thx again!

lennao said:
hey,
i would like to thank you, your tutorial works fine! and was pretty easy too, nothing complicated.
thx again!
Click to expand...
Click to collapse
Excellent, glad it worked out.

[Q] Semi-bricked tf300t

I'll preface this by saying the following:
I know there are a lot of brick guides out there, and most are relatively easy to get out of. I've worked myself into a bit of a pickle, though.
It started when I noticed that there was an update available through the CM updater. I figured, what the hell, I'm running a nightly and this is likely to be a stable release, so I went ahead and downloaded it. I got home and checked the get.cm page, and sure enough, a new, stable build had recently been released. Being the diligent soul that I am, I made sure to do a full backup before I installed the .zip. Everything worked out just fine, the backup went swell, the update finished without problems, and then I rebooted my device.
All I see is the Asus splash screen. It just stays there. So I think, no big deal, it just didn't work out like I wanted, I'll go format my data (which I didn't do the first time around, in hopes that everything would carry over) and install again. The same thing happens. I haven't started panicking yet, since I still have 3 backups (1 older Jellybean, and one much older ICS). None of them work. I wipe everything that I can think might help. Data, system, cache, dalvik, you name it. Nothing was working, and I was starting to freak out. Then I decided to try to get some action through fastboot, hoping that I could push a .zip that wasn't the CM10 update that had started everything. In my search for a push command, I thought it would be a good idea to try a wipe from fastboot. This wiped everything. Not only the system, boot, etc. partitions, but also my personal partition that had all of my data. This in itself isn't a big problem, but it also left the partitions unformatted. Now I have a device that is devoid of data and can't do anything but get into CWM and fastboot.
What the hell can I do? Am I doomed? Is there no way to get out of the hole I've dug myself into?
tl;dr failed update, things got really real, really fast.
Specs before the initial update
ROM: CM10 nightly, Jellybean 4.1.x
CWM: 5.5.0.4
Kernel Version (?): 9.4.3.30-20120604 (I'm not sure with this, it says something about "android carhu-user" before it)

same thing just happened to me. Im going to download another version of CM and try that. It might just be that.

DerangedLoofah said:
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
Click to expand...
Click to collapse
That's the thing, though, I have no idea how I'm supposed to get it to my device now...

http://forum.xda-developers.com/showthread.php?t=1989076
Have you tried this? I was just thinking about it because I can't reflash my recovery and thought this may be the way to start over.

OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2

Glad you got it!

nitsuj79 said:
Glad you got it!
Click to expand...
Click to collapse
DerangedLoofah managed to get it, but I still haven't had any luck.

DerangedLoofah said:
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
How did you flash it in fastboot? I can't figure out how to get to something that's on the external SD card. What were the exact commands you used?

1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.

nitsuj79 said:
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
Click to expand...
Click to collapse
Does that work with CWM? I don't have the stock bootloader on it.

This works only if you didn't flash custom recovery, it is the best method for locked devices. But you can still flash any stock ROM from CWM (but I suggest to use TWRP, you can install it from external sd). And you can push the ROM to internal memory via adb. I think you can install stock ROM via fastboot too, I am not sure, but the command fastboot update should help.

I managed to get it working again. If you can get to fastboot, push a bootloader that supports an external SD cards (like TWRP) and then from that install one of the official ASUS firmwares. From there, you have to root again, but it's better than having a device that won't boot at all.

[Q] New (virgin/stock) TF700 to CROMI 3.2 - is this right?

Hi there, been loitering on the sidelines for a while, reading many many threads and now ready to leap in. I have bought a TF700 Infinity and want to get it fully modded, enhanced, streamlined and dripping in XDA goodness. I want to know if the things I have planned are a) in the correct order, b) are the correct/most suitable methods and c) are inadvisable or unecessary for any reason.
Root the device
- Using the DebugFS method (details HERE and HERE).
Unlock Bootloader
- Using the ADB tool from blackmambazzz
- If the ADB tool doesn't work then I'll use the download from the Asus website
Install recovery (TWRP)
- I will try using GooManager first (hence the reason to root)
- If GooManager doesn't work then I will try the ADB tool again (option 1)
- If I get problems with the latest version I will try TWRP v2.3.1.0 (as some people have reported that this could be better)
Flash JB bootloader
- Boot into recovery (as per the instructions in the All-In-One Guide For Asus Infinity post)
- Flash the 10.4.4.25 JB bootloader found in this post
Flash ROM (CROMi 3.2)
- Using the downloads from the CleanROM Inheritance 3.2 post, flash CleanROM Inheritance and choose my options through the Aroma installer
Flash stock kernel (by _that)
- Use TWRP to flash the stock kernel through the CROMi installer v1.6 found in the CleanROM Inheritance 3.2 post
Hopefully that will get me from out of the box virgin TF700 to a fully charged awesome tablet/laptop that is smooth and powerful. Hopefully I've done my research and got it right but please let me know if there is anything incorrect. Thanks!

The procedure depends which firmware is installed your new TF700.
If 9.4.5.26 or earlier: Do not install ANY updates before you read the [BRICKPROOF] thread in the dev forum about nvflash, then decide on further steps.
If 10.4.4.x: You can't root this version directly. Either you downgrade to 9.4.5.30 first, or you simply unlock directly and continue with installing TWRP via fastboot.
Also, when you install CROMI, you can directly select the modified stock kernel, it's not a separate step.

hello! i am stuck in a point installing CROMI.
I have unlocked tf700 and installed cmw recovery.
every thing is fine.
i have put the zip file with CROMI in the internal memory but cwm is not seeing it.
it says also can't mount mmc when i try to look for the files inside...
where am i wrong?
thanks!

marci4na said:
hello! i am stuck in a point installing CROMI.
I have unlocked tf700 and installed cmw recovery.
every thing is fine.
i have put the zip file with CROMI in the internal memory but cwm is not seeing it.
it says also can't mount mmc when i try to look for the files inside...
where am i wrong?
thanks!
Click to expand...
Click to collapse
Try power off your device, wait a few seconds, then boot back into cwm see if that helped!

If all else fails I would switch over to TWRP I prefer it way more then cwm.

_that said:
The procedure depends which firmware is installed your new TF700.
If 9.4.5.26 or earlier: Do not install ANY updates before you read the [BRICKPROOF] thread in the dev forum about nvflash, then decide on further steps.
If 10.4.4.x: You can't root this version directly. Either you downgrade to 9.4.5.30 first, or you simply unlock directly and continue with installing TWRP via fastboot.
Also, when you install CROMI, you can directly select the modified stock kernel, it's not a separate step.
Click to expand...
Click to collapse
Thanks _that, your work on the stock kernel is most appreciated and I can't wait to experience the fruits of your hard work. My confusion with needing to apply it afterwards was that your kernel was included in the 3.2.1 of CROMi last night (24th Jan). At the time of the post it was still a post-ROM activity.
I should get the TF700 today so will check out the firmware version. Initially I was confused about the 9.4 / 10.4 version numbers on the forums but I think that this refers to the 'Build Number' in Menu > Settings > About Tablet menu. Assuming the tablet is on 10.4.4.x, my plan is to:
Unlock using ADB tool or Asus unlock app
Install TWRP recovery using ADB tool (if this does not work, root and use GooManager)
Flash CROMi from TWRP using Aroma installer to select the _that stock kernel and browser2ram
Allow to settle for 5-10 minutes
Enjoy
I'm not including the root step as I understand that CROMi is pre-rooted.

mrlee1980 said:
My confusion with needing to apply it afterwards was that your kernel was included in the 3.2.1 of CROMi last night (24th Jan). At the time of the post it was still a post-ROM activity.
Click to expand...
Click to collapse
3.2 already contained "my" kernel, 3.2.1 contains the nodpi variant.
mrlee1980 said:
I should get the TF700 today so will check out the firmware version. Initially I was confused about the 9.4 / 10.4 version numbers on the forums but I think that this refers to the 'Build Number' in Menu > Settings > About Tablet menu.
Click to expand...
Click to collapse
Correct.
mrlee1980 said:
Assuming the tablet is on 10.4.4.x, my plan is to:
Unlock using ADB tool or Asus unlock app
Install TWRP recovery using ADB tool (if this does not work, root and use GooManager)
Flash CROMi from TWRP using Aroma installer to select the _that stock kernel and browser2ram
Allow to settle for 5-10 minutes
Enjoy
I'm not including the root step as I understand that CROMi is pre-rooted.
Click to expand...
Click to collapse
Looks good. Note that the ADB tool has no error handling. If it does not work, it makes sense to invest some time to get adb and fastboot working on your PC, it is always helpful.
If you don't have any apps installed yet, you don't even need to let it settle - just don't expect absolute smoothness in the first minute, while it's still doing some background stuff.

OK, having fun with this. The TF700 arrived with 4.1.1 and boot loader 10.4.4.16, so I unlocked (pushed unlock APK to tablet through the ADB tool v6) and installed TWRP 2.3.3.0 through the ADB tool. I backed up and then flashed CROMi 3.2.1 ODEX and got through the entire process 'successfully' and rebooted.
Then nothing. I got stuck at the "Android is updating" / "Finishing boot" screen for 20 minutes. Got nervous, searched the forums and found that while some people see the screen for 5 secs, there was one person who hit the problem and a reboot sorted it out. Tried a few reboots but to no avail (battery depleting all the time) and I tried reflashing the ODEX version 3 more times but got stuck at the same point each time.
I reverted to my backup and tried to flash the JB bootloader ZIP (in case it was the 10.4.4.16 bootloader) from TWRP but couldn't get it working. The ZIP would appear to load successfully, I rebooted into Android and selected the firmware update option in the notifications area. I selected 'Install' at the pop-up and the tablet rebooted but no change to the bootloader when I checked in settings.
In the end I flashed the DEODEX version and this seemed to work. I'll try again with the ODEX (MD5 checked out OK) later.

mrlee1980 said:
OK, having fun with this. The TF700 arrived with 4.1.1 and boot loader 10.4.4.16, so I unlocked (pushed unlock APK to tablet through the ADB tool v6) and installed TWRP 2.3.3.0 through the ADB tool. I backed up and then flashed CROMi 3.2.1 ODEX and got through the entire process 'successfully' and rebooted.
Then nothing. I got stuck at the "Android is updating" / "Finishing boot" screen for 20 minutes. Got nervous, searched the forums and found that while some people see the screen for 5 secs, there was one person who hit the problem and a reboot sorted it out. Tried a few reboots but to no avail (battery depleting all the time) and I tried reflashing the ODEX version 3 more times but got stuck at the same point each time.
I reverted to my backup and tried to flash the JB bootloader ZIP (in case it was the 10.4.4.16 bootloader) from TWRP but couldn't get it working. The ZIP would appear to load successfully, I rebooted into Android and selected the firmware update option in the notifications area. I selected 'Install' at the pop-up and the tablet rebooted but no change to the bootloader when I checked in settings.
In the end I flashed the DEODEX version and this seemed to work. I'll try again with the ODEX (MD5 checked out OK) later.
Click to expand...
Click to collapse
Have you tried to flash .25 JB bootloader and reflash cromi ODEX 3.2.1 with _that stock no dpi kernel? make sure wipe cache and dalvik cache first before flashing.

mrlee1980 said:
I reverted to my backup and tried to flash the JB bootloader ZIP (in case it was the 10.4.4.16 bootloader) from TWRP but couldn't get it working. The ZIP would appear to load successfully, I rebooted into Android and selected the firmware update option in the notifications area. I selected 'Install' at the pop-up and the tablet rebooted but no change to the bootloader when I checked in settings.
Click to expand...
Click to collapse
The settings screen does not show the bootloader version. The bootloader version is only displayed when you hold down Volume-down while powering on - tiny text in the upper left corner while the bootloader menu is shown.

[Q] Stuck on boot animation Cromi X 5.2.2 Help

So finally took the plunge and flashed Cromi-X 5,2,2. Current set up is bootloader 10.8, TWRP 2.5.0 unlocked and rooted. I was running fine for a couple of days and decided to try cromi control to turn of a couple of notifications.I didnt reboot from cromi control as I read there was a bug. I powered off using the power button and when powering back on I was stuck on boot animation. Options I chose on the original flash was _thatv4 10.8 with defaults. No ET / OV / OC / No tweaks. So i decided to dirty flash 5.2.2 again without formating data I got to upgrading apps and when it rebooted, back stuck on animation. I am going to try flashing my original stock asus nandroid.prior to 5.2.2 just to get it working for the evening.
Doing a search of the thread now... See this has been covered on 5.2.1. I may have to wipe / format data IDK
Any suggestions?
Thanks

Update
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.

GPWILL said:
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.
Click to expand...
Click to collapse
It is always good to have the latest bootloader and TWRP. What is your firmware or bootloader now? What do you want to achieve or usage on your device? _that v7 on Cromi X is a nice combo with speed and stability...

GPWILL said:
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.
Click to expand...
Click to collapse
Glad you got it working again. It's strange - what happened is typical for rebooting from the Cromi app, but you didn't.....
Did you do a factory wipe in TWRP before installing CROMi-X?
Also, it certainly wouldn't hurt to update your recovery. Just flash the bootloader/TWRP package in the CROMi-X OP and reboot to system.

My current working is 10.6.1.14.8 from ASUS and TWRP 2.5.0. I did a factory wipe in TWRP before flashing Cromi 5.2.2. Everything went smooth. I let google restore my apps when running thru the setup wizard. A little painful but only took 30 minor so. I didnt restore any apps or data from my TB. So I let it run for a couple of days with no issues. I ran into trouble with the chromi control. Wanted to get rid of that annoying external card notification. Powered off using the power button and boom. Things went south. I am not a overclock / tweak poweruser. Just wanted a little tweak since it looks like ASUS is not going to update anymore. My tab is a little over a year old and my only complaints have been browser lag and the painful lag of using the tablet when apps updates. My intent is to get 5.2.2. Run thru set up / installer a couple of times so I could get use the installer and then at some point venture into rom2sd or data2sd. Next go around I will get 5.2.2 working and nandroid that. I had tried B2R and it works ok. But with 5.2.2 it seems to give the tab a big 'push'. The browser worked way faster. I tried both stock and Chrome with 5.2.2 and was nice and smooth..
Thanks for the responses. If you think of anything else I appreciate it. Been on this forum for awhile and you guys are great!

GPWILL said:
My current working is 10.6.1.14.8 from ASUS and TWRP 2.5.0. I did a factory wipe in TWRP before flashing Cromi 5.2.2. Everything went smooth. I let google restore my apps when running thru the setup wizard. A little painful but only took 30 minor so. I didnt restore any apps or data from my TB. So I let it run for a couple of days with no issues. I ran into trouble with the chromi control. Wanted to get rid of that annoying external card notification. Powered off using the power button and boom. Things went south. I am not a overclock / tweak poweruser. Just wanted a little tweak since it looks like ASUS is not going to update anymore. My tab is a little over a year old and my only complaints have been browser lag and the painful lag of using the tablet when apps updates. My intent is to get 5.2.2. Run thru set up / installer a couple of times so I could get use the installer and then at some point venture into rom2sd or data2sd. Next go around I will get 5.2.2 working and nandroid that. I had tried B2R and it works ok. But with 5.2.2 it seems to give the tab a big 'push'. The browser worked way faster. I tried both stock and Chrome with 5.2.2 and was nice and smooth..
Thanks for the responses. If you think of anything else I appreciate it. Been on this forum for awhile and you guys are great!
Click to expand...
Click to collapse
With your current firmware, 10.6.1.14.8, you should have the latest bootloader but you still need to update your TWRP to a later version, 2.6.1.0 or 2.6.3.0.. You need to pick one. I am still using 2.6.1.0 and it works fine at the moment and no plan to update to 2.6.3.0. I am very sure that you know how to update your custom recovery, TWRP,
If I am not mistaken, you have the old backup but not the 5.2.2 backup before it crashed... It is always a good idea to backup your good working current setup so you can go back or restore if something is going wrong.. One more thing about backup, it would be nice if you can keep your backup and personal stuff on your External SD, Not the internal SD...
Rom and kernel selections: Cromi v5.2.2 is the latest and the fastest in my opinion so it is your first choice unless you something else in mind.. You only have a few selections on kernel and they are all good and serve with a different purposes. sbdags is very closed to stock with a minimal modifications. _that v7 is the latest and more modifications comparing to sbdags. However, it is faster and more stable or most stable of all according to testers and users... Hund's kernel is the fastest of all with even more modifications and options for users to change settings. Testers and users report back with a little less stable comparing to _that but I don't have a single problem with this kernel... However, it is running a little warmer than sbdags and _that because it is running with higher frequency...Max kernel is another option but it seems like there is no supports at the moment. No one knows where he is, haha... Hopefully, we can hear back from him again...
Installation: Totally clean installing because you are already having issue...
1. Backup anything that you want to save including your personal data and files
2. Copy cromi and kernel that you want to install to your External SD because you want to format your data partition
3. Format your data partition and I mean Format, not wipe.
4. Wipe everything on your device including your system but not your external SD..
5. Install cromi and kernel of your choices
6. Reboot and let it sits for a few minutes, then you can do your setup from the setup wizard
7. Go back to your TWRP and do a nandroid backup to your External SD, just in case so you restore it
8. Install your apps or whatever you want from the google store, not from your TB so you can have a good and stable backup
9. After you are done with all the apps and games installation, you may want to do another backup in the TWRP
10. Now you can do whatever you want from this point and if you have more settings to do, you may want to do another backup as a Final backup and a good working one... You can delete the other backup from the previous if you have the final and working backup. You just need one good working backup..That is it..
You can always go back to TWRP to restore just your data or just a system or a whole backup. Those are the options that you can restore and good luck...:fingers-crossed:

LetMeKnow said:
With your current firmware, 10.6.1.14.8, you should have the latest bootloader but you still need to update your TWRP to a later version, 2.6.1.0 or 2.6.3.0.. You need to pick one. I am still using 2.6.1.0 and it works fine at the moment and no plan to update to 2.6.3.0. I am very sure that you know how to update your custom recovery, TWRP,
If I am not mistaken, you have the old backup but not the 5.2.2 backup before it crashed... It is always a good idea to backup your good working current setup so you can go back or restore if something is going wrong.. One more thing about backup, it would be nice if you can keep your backup and personal stuff on your External SD, Not the internal SD...
Rom and kernel selections: Cromi v5.2.2 is the latest and the fastest in my opinion so it is your first choice unless you something else in mind.. You only have a few selections on kernel and they are all good and serve with a different purposes. sbdags is very closed to stock with a minimal modifications. _that v7 is the latest and more modifications comparing to sbdags. However, it is faster and more stable or most stable of all according to testers and users... Hund's kernel is the fastest of all with even more modifications and options for users to change settings. Testers and users report back with a little less stable comparing to _that but I don't have a single problem with this kernel... However, it is running a little warmer than sbdags and _that because it is running with higher frequency...Max kernel is another option but it seems like there is no supports at the moment. No one knows where he is, haha... Hopefully, we can hear back from him again...
Installation: Totally clean installing because you are already having issue...
1. Backup anything that you want to save including your personal data and files
2. Copy cromi and kernel that you want to install to your External SD because you want to format your data partition
3. Format your data partition and I mean Format, not wipe.
4. Wipe everything on your device including your system but not your external SD..
5. Install cromi and kernel of your choices
6. Reboot and let it sits for a few minutes, then you can do your setup from the setup wizard
7. Go back to your TWRP and do a nandroid backup to your External SD, just in case so you restore it
8. Install your apps or whatever you want from the google store, not from your TB so you can have a good and stable backup
9. After you are done with all the apps and games installation, you may want to do another backup in the TWRP
10. Now you can do whatever you want from this point and if you have more settings to do, you may want to do another backup as a Final backup and a good working one... You can delete the other backup from the previous if you have the final and working backup. You just need one good working backup..That is it..
You can always go back to TWRP to restore just your data or just a system or a whole backup. Those are the options that you can restore and good luck...:fingers-crossed:
Click to expand...
Click to collapse
Been awhile since I played with fastboot. Can I just flash the bootloader and twrp zip from the 5.2.2 Cromi thread and be ok? I know to flash this first and reboot into rom before flashing 5.2.2 again. Otherwise I will get fastboot going again.
"10.6.1.14.10 US Bootloader and TWRP 2.6.1.0 DOWNLOAD 1" This is in scenario 2 which doesnt really apply because I dont have a custom rom installed yet at this point.
I am saving these notes for future reference. Thanks for the time in writing these up.

GPWILL said:
Been awhile since I played with fastboot. Can I just flash the bootloader and twrp zip from the 5.2.2 Cromi thread and be ok? I know to flash this first and reboot into rom before flashing 5.2.2 again. Otherwise I will get fastboot going again.
"10.6.1.14.10 US Bootloader and TWRP 2.6.1.0 DOWNLOAD 1" This is in scenario 2 which doesnt really apply because I dont have a custom rom installed yet at this point.
I am saving these notes for future reference. Thanks for the time in writing these up.
Click to expand...
Click to collapse
I think that it would fine since you are running TWRP 2.5. Please be careful when you install custom recovery and bootloader. If you make a mistake, it could brick your device, just my two cents.. Please ask a lot of questions to be sure...
Note: From your TWRP 2.5, install 10.6.1.14.10 first and reboot so the blob can update your bootloader. When it boots into the system, then you need to reboot it back into your TWRP 2.5 and install the TWRP 2.6.1.0. When it is done, then you need to shut it down and use your power button and volume down to boot back into your new TWRP...Good luck..:fingers-crossed:
Always check your download "MD5 Sum" to verify that you have a good download....

You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?

GPWILL said:
You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?
Click to expand...
Click to collapse
I never use the method from cromi thread but I trust sbdags as a great developer and so many users used this method without a problem...
If you are still running stock firmware version 10.6.1.14.8, then you still can use goomanager to update your TWRP... If you prefer it that way, then goo still works for you...If you are on stock version 10.6.1.14.8, you are already on the latest bootloader unless you want the latest stock firmware V14.10 which you will update it with Cromi any way...
1. Use goo to update the correct TWRP, 2.6.3.0 or 2.6.1.0
2. Boot into your new TWRP and install the Cromi and follow the instructions that I wrote earlier
Good luck..:fingers-crossed:

GPWILL said:
You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?
Click to expand...
Click to collapse
Not quite.
You cannot flash BL or TWRP separately from that package. It's either both or none.
But flashing the package would be the easiest and safest method to get you on a current recovery in my opinion.
GooManager: For a few weeks now Goo did not support flashing recoveries anymore. I've read it often enough that I consider that information confirmed - although I have not tested it myself.
Now - just yesterday I read a post where a user reported that Goo got an update and he flashed TWRP successfully. That's one report I know of - if you want to give it a try, go for it. It can't hurt.
The thing is, to use GooManager you have to root the stock rom you are running.
I don't know if the stock rom you are running is rooted, but why bother if you can just flash sbdags package??

Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.

GPWILL said:
Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.
Click to expand...
Click to collapse
Well goomanager didnt work for me. Just sits on "downloading" forever. only option was to upgrade to 2.6.3.1
Off to get fastboot working..

GPWILL said:
Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.
Click to expand...
Click to collapse
_thatv7 is one of the kernel choices - changing a kernel does not do anything to the bootloader.
Look at these elements of the system as parts of an engine: If the bootloader is the starter motor, the kernel may be the distributor.....
Thanks for trying Goo, the score is 1:1
Anyway, to get fastboot working is worth the effort. It's great for troubleshooting or pulling logs and such. It's very helpful to have a working fastboot connection BEFORE you run into some trouble and really need it to work

I guess my question is if I choose _thatv7 will bootloader .8 work? The 10 after the kernel choice is what has put me down this road.
fastboot and adb working. So getting there albeit slowly.
This thread really helped a lot in my learning process..
http://forum.xda-developers.com/showthread.php?t=2546420&highlight=flash+10+6+1+14+10+fastboot
Thanks again for all the info and help.

GPWILL said:
I guess my question is if I choose _thatv7 will bootloader .8 work? The 10 after the kernel choice is what has put me down this road.
fastboot and adb working. So getting there albeit slowly.
This thread really helped a lot in my learning process..
http://forum.xda-developers.com/showthread.php?t=2546420&highlight=flash+10+6+1+14+10+fastboot
Thanks again for all the info and help.
Click to expand...
Click to collapse
There's hardly anything different between the. 8 and . 10 bootloader. V7 works fine with either.
Sent from my DROID4 using Tapatalk

berndblb said:
There's hardly anything different between the. 8 and . 10 bootloader. V7 works fine with either.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Update:
Updated TWRP to 2.6.1
fastboot and adb working
Flashed 5.2.2 Cromi-X _thatv7 this time around. (used the advice from above)
Set up apps
I will def nandroid this working config..
All good now.
Thanks to everyone!
FYI I updated goomanager and tried it again on my old setup and it still did not work updating twrp. Stuck on downloading app...

GPWILL said:
Update:
Updated TWRP to 2.6.1
fastboot and adb working
Flashed 5.2.2 Cromi-X _thatv7 this time around. (used the advice from above)
Set up apps
I will def nandroid this working config..
All good now.
Thanks to everyone!
FYI I updated goomanager and tried it again on my old setup and it still did not work updating twrp. Stuck on downloading app...
Click to expand...
Click to collapse
Fastboot is a prefer method to use...:good: I always use fastboot for this stuff. It is fast and easy without any hassle...
How is it running? It should be running very reasonable speed and smoothness...

LetMeKnow said:
Fastboot is a prefer method to use...:good: I always use fastboot for this stuff. It is fast and easy without any hassle...
How is it running? It should be running very reasonable speed and smoothness...
Click to expand...
Click to collapse
It is running pretty nice. Stock browser and Chrome are a little faster than my stock setup with B2R. I have had a few " laucher has stopped" errors. This happened before I installed any apps with thatV7. Didnt get a single laucher error before on thatv4. Stock laucher. Nice and smooth on apps and such. Both stock browser and chrome are faster but not anything like "WOW". Just a little better. Nice to have it built in. I am going to give this a few more days and see if the laucher errors settle down. If it stablizes I will get another nandroid of it and try the ROM2SD to see if I can get the wow factor going.

5.0 to 5.0.1 Update Manual Flash (NOT OTA)

Ok so.. here's a quick guide to flashing 5.0.1 on the Nvidia Shield Tablet. I have the 16GB Wifi version so if you have a different version (LTE or non-US tablet) this guide may or may not apply to you. I also essentially dirty flashed this in CWM recovery. If you're using TWRP WIP, no idea if it will blow up or not. Standard disclaimer applies if your Tablet blows up or anything, i'm not responsible. You do these steps at your own risk. I'm going on the premise that you have the Shield drivers already installed and have some flashing knowledge.
This is an upgrade from 5.0 to 5.0.1
This guide DOES NOT utilize the OTA zip that your tablet downloaded.
1. Download http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29082_493.9700.zip (AGAIN, US 16gb WIFI only, there's another thread here somewhere with other full download links) I copied it to external SDCard rather than tablet storage.
2. adb reboot recovery to get into CWM or shut down and use the hardware keys to reboot to recovery
3. In CWM, install zip from external sd card and flash it like a normal rom. CWM reports this sucessful and reboot to 5.0.1 and let it settle. It updates binaries and blah blah. Oh also root and recovery are now gone. You should still have fastboot.
4. reboot into fastboot, hardware keys again or using adb reboot bootloader.
5. Now you follow the excellent post by sandrodjay for restoring CWM and root. (If you didn't wipe, most of the preliminaries in sandrodjay's post should already be done. Debug mode and whatnot) http://forum.xda-developers.com/shi...t-lollipop-t2972316/post57719881#post57719881
After the dust settled for me, i was on 5.0.1 and had CWM and root back. YMMV.

terrigan said:
Ok so.. here's a quick guide to flashing 5.0.1 on the Nvidia Shield Tablet. I have the 16GB Wifi version so if you have a different version (LTE or non-US tablet) this guide may or may not apply to you. I also essentially dirty flashed this in CWM recovery. If you're using TWRP WIP, no idea if it will blow up or not. Standard disclaimer applies if your Tablet blows up or anything, i'm not responsible. You do these steps at your own risk. I'm going on the premise that you have the Shield drivers already installed and have some flashing knowledge.
1. Download http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29082_493.9700.zip (AGAIN, US 16gb WIFI only, there's another thread here somewhere with other full download links) I copied it to external SDCard rather than tablet storage.
2. adb reboot recovery to get into CWM or shut down and use the hardware keys to reboot to recovery
3. In CWM, install zip from external sd card and flash it like a normal rom. CWM reports this sucessful and reboot to 5.0.1 and let it settle. It updates binaries and blah blah. Oh also root and recovery are now gone. You should still have fastboot.
4. reboot into fastboot, hardware keys again or using adb reboot bootloader.
5. Now you follow the excellent post by sandrodjay for restoring CWM and root. (If you didn't wipe, most of the preliminaries in sandrodjay's post should already be done. Debug mode and whatnot) http://forum.xda-developers.com/shi...t-lollipop-t2972316/post57719881#post57719881
After the dust settled for me, i was on 5.0.1 and had CWM and root back. YMMV.
Click to expand...
Click to collapse
What CWM version are you using? My CWM is reporting a failure to update because it thinks I'm still running Android 4.4.2.

dibblebill said:
What CWM version are you using? My CWM is reporting a failure to update because it thinks I'm still running Android 4.4.2.
Click to expand...
Click to collapse
Did you for download full ota zip 700mb or did you try flashing partial which you would get through system update

Full ZIP not OTA. The 700mb download. Also i'm using the flashed recovery.img from sandrojay's post which is CWM 6.0.5.0. Are you guys on 5.0 or 4.4.4? I suppose i should mention this is an upgrade from 5.0 to 5.0.1

terrigan said:
Full ZIP not OTA. The 700mb download. Also i'm using the flashed recovery.img from sandrojay's post which is CWM 6.0.5.0. Are you guys on 5.0 or 4.4.4? I suppose i should mention this is an upgrade from 5.0 to 5.0.1
Click to expand...
Click to collapse
I'm running the stock lollipop build. I tried removing the checks from the updater script but it still won't install.

dibblebill said:
I'm running the stock lollipop build. I tried removing the checks from the updater script but it still won't install.
Click to expand...
Click to collapse
Are you running the same CWM?

dibblebill said:
I'm running the stock lollipop build. I tried removing the checks from the updater script but it still won't install.
Click to expand...
Click to collapse
It sounds like you are trying to install the partial ota can you confirm

Yeah this guide isn't meant to utilize the OTA zip. My first instruction is to download the whole 700mb update.

mcord11758 said:
It sounds like you are trying to install the partial ota can you confirm
Click to expand...
Click to collapse
terrigan said:
Yeah this guide isn't meant to utilize the OTA zip. My first instruction is to download the whole 700mb update.
Click to expand...
Click to collapse
I see that now. Downloading the full OTA. Modified your link to the "do" version.

It worked this time though I oddly didn't need to reflash CWM
Sent from my Sony Xperia Z3

Thanks for the topic. Anyone has a link for full 5.0.1 for EU WIFI version ?

Aanze said:
Thanks for the topic. Anyone has a link for full 5.0.1 for EU WIFI version ?
Click to expand...
Click to collapse
I flashed the NA one as someone mentioned that they seems to be the same - worked fine on my system.

Thanks for the feedback, trying it right now

terrigan said:
Ok so.. here's a quick guide to flashing 5.0.1 on the Nvidia Shield Tablet. I have the 16GB Wifi version so if you have a different version (LTE or non-US tablet) this guide may or may not apply to you. I also essentially dirty flashed this in CWM recovery. If you're using TWRP WIP, no idea if it will blow up or not. Standard disclaimer applies if your Tablet blows up or anything, i'm not responsible. You do these steps at your own risk. I'm going on the premise that you have the Shield drivers already installed and have some flashing knowledge.
This is an upgrade from 5.0 to 5.0.1
This guide DOES NOT utilize the OTA zip that your tablet downloaded.
1. Download http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29082_493.9700.zip (AGAIN, US 16gb WIFI only, there's another thread here somewhere with other full download links) I copied it to external SDCard rather than tablet storage.
2. adb reboot recovery to get into CWM or shut down and use the hardware keys to reboot to recovery
3. In CWM, install zip from external sd card and flash it like a normal rom. CWM reports this sucessful and reboot to 5.0.1 and let it settle. It updates binaries and blah blah. Oh also root and recovery are now gone. You should still have fastboot.
4. reboot into fastboot, hardware keys again or using adb reboot bootloader.
5. Now you follow the excellent post by sandrodjay for restoring CWM and root. (If you didn't wipe, most of the preliminaries in sandrodjay's post should already be done. Debug mode and whatnot) http://forum.xda-developers.com/shi...t-lollipop-t2972316/post57719881#post57719881
After the dust settled for me, i was on 5.0.1 and had CWM and root back. YMMV.
Click to expand...
Click to collapse
Does this upgrade method loose all data (like factory reset) or not loosing anything other than CWM and root? Thanks.

If you don't wipe, no. Everything stays.

layanto said:
Does this upgrade method loose all data (like factory reset) or not loosing anything other than CWM and root? Thanks.
Click to expand...
Click to collapse
I've got good news... Your data and apps remain untouched, only litle problem depending on number of apps is time to "optimize apps" on first boot after update

Thank you for this!

Aanze said:
Thanks for the feedback, trying it right now
Click to expand...
Click to collapse
Did it work?

Just to make it clear for all, I've flashed the wifi version....
Tried with all (really all) the recovery in XDA ending with error.
The only recovery that worked is the 6.0.5.0!!
Updated dirty flashed but ended with lag for me, so clean install, and now all is good.
(was unlocked bootloader)
Lost recovery and lost root of course, but with adb takes 2 minutes to put them back.

ciribaski said:
Just to make it clear for all, I've flashed the wifi version....
Tried with all (really all) the recovery in XDA ending with error.
The only recovery that worked is the 6.0.5.0!!
Updated dirty flashed but ended with lag for me, so clean install, and now all is good.
(was unlocked bootloader)
Lost recovery and lost root of course, but with adb takes 2 minutes to put them back.
Click to expand...
Click to collapse
+1 as I've also just flashed the full wifi update to 5.0.1 using CWM v6.0.5.0, without wiping data, and everything came back up nicely. Still giving the tablet a chance to settle in after re-rooting with SuperSU v2.40, but hoping that the extreme lag doesn't return. If it does, I suppose I'll have to try a full wipe.
One thing I noticed is that after the very first reboot (without rooting, immediately after flashing the update), the system was very busy, and this could have been due to FolderMount trying to mount folders on boot using root when the tablet was NOT rooted. I'd recommend disabling FolderMount from auto-mounting on boot if you have it configured that way.
Thanks for providing this full 5.0.1 update package OP!