Database Info

[q] can you flash rom w/fastboot

I somehow have locked myself out but still have access to CWM and FASTBOOT. So, how do I use FASTBOOT to install a rom? Is it even possible? I just flashed CWM again, but still cannot get my CWM Backup copy to work.

up.
My friend has same issue, change build.prop.. no backup, no adb, only fastboot with cwm. Any ideas? Ext SD don't work in CWM\TWRP.
upd: Answer myself - Plug into usb in recovery, update driver in device manager to ADB Device, use adb

See here http://forum.xda-developers.com/showthread.php?t=1680570

What happens if clockworkmod recovery cannot read zip files???

fastboot flash zip rom.zip

prototype7 said:
fastboot flash zip rom.zip
Click to expand...
Click to collapse
Do I need a system.img file???

ri123 said:
Do I need a system.img file???
Click to expand...
Click to collapse
No, just the regular zip, you could also try reflashing the recovery (fastboot flash recovery recovery.img).

prototype7 said:
No, just the regular zip, you could also try reflashing the recovery (fastboot flash recovery recovery.img).
Click to expand...
Click to collapse
What about fastboot update command???

No
Hit the thanks button if i helped

Is this procedure compatible with the meta inf folder???

noooo!! i try "fastboot flash zip rom.zip" and it says FAILED remote partition does not exist!! what can i do now??

nooo!!! it says ( failed remote partition does not exist)

Xperia S with the same problem mine says
(remote: Partition not found)

The command you can used to flash a zipped ROM like the stock one from Asus is...
Fastboot -i 0x0b05 flash system yourrom.zip
I usually flash these using twrp recovery but I think that will do it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Maybe I just can't follow instructions or anythng, but I attempted my first ROM flash and it didn't work.
I tried the Blackbean 5 ROM, with TWRP. I found a set of instructions saying how to flash with TWRP, so I followed them, and I think I've soft-bricked my TF300T. Just stays on the Asus logo, and in top left it says "The Device is UnLocked."
I DID make a recovery in TWRP, and I attempted to flash that back with no luck.
Maybe I'm doing it wrong, so can someone help me out here?
funnel71 said:
The command you can used to flash a zipped ROM like the stock one from Asus is...
Fastboot -i 0x0b05 flash system yourrom.zip
I usually flash these using twrp recovery but I think that will do it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I tried this with the stock ROM, from their website, and it didn't help...
So I'm not sure what my problem is now.
Then again, when it comes to ROMs, I'm a noob.
EDIT: I still have TWRP, my recovery, and the Blackbean ROM .zip on the device.

TsarProdigy said:
Maybe I just can't follow instructions or anythng, but I attempted my first ROM flash and it didn't work.
I tried the Blackbean 5 ROM, with TWRP. I found a set of instructions saying how to flash with TWRP, so I followed them, and I think I've soft-bricked my TF300T. Just stays on the Asus logo, and in top left it says "The Device is UnLocked."
I DID make a recovery in TWRP, and I attempted to flash that back with no luck.
Maybe I'm doing it wrong, so can someone help me out here?
I tried this with the stock ROM, from their website, and it didn't help...
So I'm not sure what my problem is now.
Then again, when it comes to ROMs, I'm a noob.
EDIT: I still have TWRP, my recovery, and the Blackbean ROM .zip on the device.
Click to expand...
Click to collapse
Background first when stock were you JB or ICS? Blackbean OP does not specify. At the moment I'm to lazy to read through thread or flash to find the answer. If you were on stock JB you can only use JB roms, if you were on ICS you can only use JB after stock upgrade to JB.
Forget Blackbean for now and let's concentrate on getting you fully functional on stock again. If you were on ICS then download stock 9.4.3.30 and unzip once that leaves you with a zip. Place that zip on your ( /sdcard ) or external sdcard ( /Removable/MicroSD ) and flash with Twrp. If you were JB then the instructions are the same except use stock 10.4.2.13.
If you do this you will loose your recovery ( Twrp ) but you should have a functional unit.
Non stock rom install.
Be sure you use proper rom for your bootloader ( ICS or JB ). Choose one that gives you instructions as to what to wipe, etc. You can adlib after you get your feet wet. If the op gives instructions use them if not then you may or may not have a happy ending with generic instructions.:good:
If you need anything explained let me know and I'll step by step for what you don't understand.
The reply you tried to follow said "I think", you should have investigated before following. Don't get me wrong, I'm not saying that was incorrect but the poster was in doubt and you should be also.
When we say "I think" we kind of assume you are going to do some reading and be comfortable with everything before you continue.
I took a little time to look over Blackbean and as I suspected it is for the ICS bootloader not JB.

same problem
I am having the exact same problem. I did manage to install the clean rom 2.5 custom rom successfully originally, and i made a backup through CWM, but I cant install any other rom on there for some reason. Yesterday I managed to go back to stock Asus jellybean rom successfully, and then had to root it and install CWM again successfully. I have again tried again today to install that EuroSkank rom, but alas, I get stuck at the ASUS boot logo permanently and nothing happens?
What might I be doing wrong??
I am on Jellybean. Thankfully the CWM is working fine and I could also restore my cleanrom2.5 backup.
tobdaryl said:
Background first when stock were you JB or ICS? Blackbean OP does not specify. At the moment I'm to lazy to read through thread or flash to find the answer. If you were on stock JB you can only use JB roms, if you were on ICS you can only use JB after stock upgrade to JB.
Forget Blackbean for now and let's concentrate on getting you fully functional on stock again. If you were on ICS then download stock 9.4.3.30 and unzip once that leaves you with a zip. Place that zip on your ( /sdcard ) or external sdcard ( /Removable/MicroSD ) and flash with Twrp. If you were JB then the instructions are the same except use stock 10.4.2.13.
If you do this you will loose your recovery ( Twrp ) but you should have a functional unit.
Non stock rom install.
Be sure you use proper rom for your bootloader ( ICS or JB ). Choose one that gives you instructions as to what to wipe, etc. You can adlib after you get your feet wet. If the op gives instructions use them if not then you may or may not have a happy ending with generic instructions.:good:
If you need anything explained let me know and I'll step by step for what you don't understand.
The reply you tried to follow said "I think", you should have investigated before following. Don't get me wrong, I'm not saying that was incorrect but the poster was in doubt and you should be also.
When we say "I think" we kind of assume you are going to do some reading and be comfortable with everything before you continue.
I took a little time to look over Blackbean and as I suspected it is for the ICS bootloader not JB.
Click to expand...
Click to collapse

maggoty said:
I am having the exact same problem. I did manage to install the clean rom 2.5 custom rom successfully originally, and i made a backup through CWM, but I cant install any other rom on there for some reason. Yesterday I managed to go back to stock Asus jellybean rom successfully, and then had to root it and install CWM again successfully. I have again tried again today to install that EuroSkank rom, but alas, I get stuck at the ASUS boot logo permanently and nothing happens?
What might I be doing wrong??
I am on Jellybean. Thankfully the CWM is working fine and I could also restore my cleanrom2.5 backup.
Click to expand...
Click to collapse
( EuroSkank ) is also an ICS rom not JB - Clean rom 2.5 is JB. For now unless you have NVFlash you can't go back to ICS from JB and you can't run ICS rom with JB bootloader. (I'm using ICS and JB here to declare the bootloader )

Ok, Thank you very much.
tobdaryl said:
( EuroSkank ) is also an ICS rom not JB - Clean rom 2.5 is JB. For now unless you have NVFlash you can't go back to ICS from JB and you can't run ICS rom with JB bootloader. (I'm using ICS and JB here to declare the bootloader )
Click to expand...
Click to collapse

any1 with Partition not found problem, open zip and look at the folders, delete everything except folder you want (which is propably system) then write
fastboot flash system yourzip.zip
if this doesn't work for you then extract files from the folder and repack only files from the system folder and use the command above.
It doesn't work for me (dunno why) but it's something

[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] 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] Help understanding my current rom/recovery situation

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.

Need help updating from rooted 5.1.1

I have a Shield Tablet (post battery fire exchange) and I would like to update it to the newest firmware/os... It is currently rooted, running BitO-Kernel, and stock nvidia rom. I did all the rooting and flashing on this tablet originally, but I never kept it up to date with newer updates. I heard on this forum awhile back that it's not just as simple as flashing a new rom, something about having to flash some other system stuff first or some partition or something. Basically I'm looking for a guide on how to update a Shield Tablet from rooted 5.1.1 to the newest OS version avalible. I tried sreaching the forum, but I couldn't find what I was looking for (maybe I'm not using the right search keyworks).

Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20wifi&tx=$additional,shield

redpoint73 said:
Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet wifi&tx=$additional,shield
Click to expand...
Click to collapse
Thanks I appreciate the help! Yes it's an original tablet (not the k1). It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root. I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
https://forum.xda-developers.com/shield-tablet/help/how-update-rooted-shield-tablet-to-t3355436

bluegizmo83 said:
It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root.
Click to expand...
Click to collapse
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
bluegizmo83 said:
I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
Click to expand...
Click to collapse
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.

redpoint73 said:
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.
Click to expand...
Click to collapse
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works. After that, I should be able to flash any current update (like 6.0) also, correct? And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?

bluegizmo83 said:
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works.
Click to expand...
Click to collapse
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!
bluegizmo83 said:
After that, I should be able to flash any current update (like 6.0) also, correct?
Click to expand...
Click to collapse
Correct.
bluegizmo83 said:
And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?
Click to expand...
Click to collapse
Not 100% sure. It's a full OTA zip, not an incremental update. So in those cases (full OTA) it may not need the preceding update installed. But again, I'm not sure.

redpoint73 said:
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!.
Click to expand...
Click to collapse
Ok thanks again, I appreciate all the help! One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?

bluegizmo83 said:
One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?
Click to expand...
Click to collapse
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!

redpoint73 said:
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!
Click to expand...
Click to collapse
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?

bluegizmo83 said:
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?
Click to expand...
Click to collapse
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".

redpoint73 said:
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".
Click to expand...
Click to collapse
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.

bluegizmo83 said:
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.
Click to expand...
Click to collapse
I'm not sure if it matters with the OTA. My feeling is, that it won't matter, and it will still install.
My guess is that in the worst case, the OTA fails, and you have to resort to flashing the recovery OS version.