SKU conversion from DE 8.2.3.13 to WW 8.6.5.21 - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi,
I want to know how can I do to convert my SKU DE 8.2.3.13 to WW 8.6.5.21.
Thanks

I thought you could do sku conversion with nvflash? You have to have a low enough serial number.
I have a theory that you can change it via the staging partition, but I'm too busy to try.

gee one said:
I thought you could do sku conversion with nvflash? You have to have a low enough serial number.
I have a theory that you can change it via the staging partition, but I'm too busy to try.
Click to expand...
Click to collapse
I thought WW meant 'world-wide' and was basically compatible with anything, though it doesn't have specific regional support, for example any keyboard besides qwerty?
I was a US epad and used the WW without issue..just flashed it via recovery (stock recovery, in fact).

luna_c666 said:
I thought WW meant 'world-wide' and was basically compatible with anything, though it doesn't have specific regional support, for example any keyboard besides qwerty?
I was a US epad and used the WW without issue..just flashed it via recovery (stock recovery, in fact).
Click to expand...
Click to collapse
My serial is B50xx and I don't have any keyboard.
How can I do to flash via recovery the WW version and which file I have to put in SD card?
Thanks

the update from asus is not usable for direckt sku conversation.
but you can use this tut
http://forum.xda-developers.com/showthread.php?t=1093403
with the firmware file from asus.
on this way i have a ww change to de on a B90xxxxx.
but it is a little risky.

I thought you could;
Get stock recovery image branded to your region, use CWM to flash your stock recovery image, reboot recovery, then with the same region-branded ROM (asus update) you can let stock recovery flash your ROM back to stock and regional branding of your choice?
I have done this several times.....
(Honestly I think you guys are just trying to give them a hard time lol ADB to root? ADB to flash ROMs..? LOL I've done everything on my TF without access to a computer even..never used ADB with the TF, not once)
But please...defer to these guys' judgment, they seem more confident than I am of it..I learn by trial and error

luna_c666 said:
I thought you could;
Get stock recovery image branded to your region, use CWM to flash your stock recovery image, reboot recovery, then with the same region-branded ROM (asus update) you can let stock recovery flash your ROM back to stock and regional branding of your choice?
I have done this several times.....
(Honestly I think you guys are just trying to give them a hard time lol ADB to root? ADB to flash ROMs..? LOL I've done everything on my TF without access to a computer even..never used ADB with the TF, not once)
But please...defer to these guys' judgment, they seem more confident than I am of it..I learn by trial and error
Click to expand...
Click to collapse
As my tablet is virgin DE and I want WW, you say me this, step by step:
1) Get stock recovery image branded to your region. You are referring to the WW stock. Ok?
2) Use CWM to flash your stock recovery image. For this, first I need to root and then install CWM recovery to flash the WW stock recovery. OK? Boot loop if I restart the pad.
3) Then with the same region-branded ROM (asus update) you can let stock recovery flash your ROM back to stock and regional branding of your choice. How can I do this if my pad dont boot?
Regards

simemu said:
As my tablet is virgin DE and I want WW, you say me this, step by step:
1) Get stock recovery image branded to your region. You are referring to the WW stock. Ok?
2) Use CWM to flash your stock recovery image. For this, first I need to root and then install CWM recovery to flash the WW stock recovery. OK? Boot loop if I restart the pad.
3) Then with the same region-branded ROM (asus update) you can let stock recovery flash your ROM back to stock and regional branding of your choice. How can I do this if my pad dont boot?
Regards
Click to expand...
Click to collapse
I'm not an expert at this, but this is what I would try-
1) grab WW firmware and extract all the parts from it
2) create WW CWM by combining WW kernel (from step 1) with CWM ramdisk
3) create flashable WW rom (system, boot.img). root it and make it insecure if it suits you.
4) repackage EBT to blob (from step 1)
5) this is where it gets tricky to avoid the bootloops- go to recovery and flash 2,3,and 4 (4 via staging partition/adb in recovery). I'm not sure if you can flash them all at once or if you have to do 2, reboot to recovery, then 3 and 4.
Lastly, this is just a theory and if you don't have access to nvflash, it will probably result in a bricked tablet. Even with access to nvflash, there is still a huge chance of bootloops and soft-bricks. I purposely left out all the details to encourage you to fill them out on your own, but feel free to ask help if you get stuck somewhere.
sent from my cyanogen(mod) vision

gee one said:
I'm not an expert at this, but this is what I would try-
1) grab WW firmware and extract all the parts from it
2) create WW CWM by combining WW kernel (from step 1) with CWM ramdisk
3) create flashable WW rom (system, boot.img). root it and make it insecure if it suits you.
4) repackage EBT to blob (from step 1)
5) this is where it gets tricky to avoid the bootloops- go to recovery and flash 2,3,and 4 (4 via staging partition/adb in recovery). I'm not sure if you can flash them all at once or if you have to do 2, reboot to recovery, then 3 and 4.
Lastly, this is just a theory and if you don't have access to nvflash, it will probably result in a bricked tablet. Even with access to nvflash, there is still a huge chance of bootloops and soft-bricks. I purposely left out all the details to encourage you to fill them out on your own, but feel free to ask help if you get stuck somewhere.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Can I do this http://forum.xda-developers.com/showpost.php?p=14574969&postcount=145 but using WW instead of US ?
Then I update the tablet normally.
Regards

That might work. The updates from the ASUS website should have the full rom plus bootloader. You will be bone stock after doing that and might not be able to root, although I lost track of the root methods lately.

simemu said:
As my tablet is virgin DE and I want WW, you say me this, step by step:
1) Get stock recovery image branded to your region. You are referring to the WW stock. Ok?
2) Use CWM to flash your stock recovery image. For this, first I need to root and then install CWM recovery to flash the WW stock recovery. OK? Boot loop if I restart the pad.
3) Then with the same region-branded ROM (asus update) you can let stock recovery flash your ROM back to stock and regional branding of your choice. How can I do this if my pad dont boot?
Regards
Click to expand...
Click to collapse
Once you are in the bootloop, then you boot into recovery (android stock recovery) and let the file load from your sd card by naming it appropriately (WW_epad-user-blah blah blah.zip) by holding vol-while pressing power, when tablet comes on press vol+ within 5 seconds to enter recovery..then just wait, it should install your rom and get you out of the bootloop, which is caused because stockrom cannot be located at this point, flashing a new rom will solve the problem

after all you nedd, to make a factory reset ( wipe). and reboot.

Related

Getting back 8.6.5.21 after root attempt

Is it possible to get my hands on a stock 8.6.5.21 after trying to root with Razorclaw? This root involved using a 8.6.6.19 fw, but not it's slow as... :S
I'd rather not lose my data, if possible.
Cheers!
Hey if your ClockworkMod is working fine then download the 8.6.5.21 from the main Asus website nd put it on your external sd and go into clockwork recovery then go into install zip and install it
Thanks! Now I need to install clockworkmod
I had a similiar question, are the updates available from the ASUS website full ROM's or incrimental updates to the prevoiusly released FOTA versions?
Can they all be flashed via CWM to over-write an existing ROM? Regardless of the current version of the firmware on the phone(assuming a data/cache wipe to be safe)?
Do they overwrite the recovery partition or do you need a copy of the asus recovery to flash back to stock recovery?
N.
tiwas said:
Thanks! Now I need to install clockworkmod
Click to expand...
Click to collapse
There is an app called RecoveryInstaller.apk ~~ http://forum.xda-developers.com/showthread.php?t=1346180 ... IF YOU ARE ROOTED, then you can use this app and it'll install Clockworkmod for you.
Novae said:
I had a similiar question, are the updates available from the ASUS website full ROM's or incrimental updates to the prevoiusly released FOTA versions?
Can they all be flashed via CWM to over-write an existing ROM? Regardless of the current version of the firmware on the phone(assuming a data/cache wipe to be safe)?
Do they overwrite the recovery partition or do you need a copy of the asus recovery to flash back to stock recovery?
N.
Click to expand...
Click to collapse
The ASUS website ROM's are full ROM's. You can flash the stock ROM with the clockworkmod, however you won't be able to update unless you flash back to stock Clockwork. http://forum.xda-developers.com/showthread.php?t=1154947 click that link to download the stock clockwork.
shadymouse said:
The ASUS website ROM's are full ROM's. You can flash the stock ROM with the clockworkmod, however you won't be able to update unless you flash back to stock Clockwork. http://forum.xda-developers.com/showthread.php?t=1154947 click that link to download the stock clockwork.
Click to expand...
Click to collapse
Yep i had already grabbed that recovery file, my biggest problem is that i have a B40 that nachoroot doesn't work on and now my USB doesn't work properly so if i **** something up i have no recourse to fix anything via nvflash or adb.

[ROM] TF101 Rooted Stock 9.2.1.17 + bootloader + modded recovery US and WW

This is a full rom for stock(ish) 9.2.1.17 and includes the following:
9.2.1.17 US bootloader and kernel/boot.img
modded recovery based on Roach's 3.2.0.1
Superuser
su binary
busybox
adb enabled, ro.secure=0 (if you previously disabled adb, it will remain disabled, unless you wipe data)
The updater script will also clear cache and dalvik cache.
Plus, if you flash now, it will also fix the cwm recovery bootloops by writing zeros to the first 80 bytes of /misc (/dev/block/mmcblk0p3)
I was lazy and the progress bar in recovery does not udpate- it is a full rom so it does take a while to flash.
This is pretty close to a rooted stock experience. It isn't for everyone, but I think some will find it useful. I thought this would help out people who get in in a pickle by flashing various roms and ending up with unbootable systems, or people who tried a few other roms and want to return to a more stock experience. I think a custom recovery is safer with a rooted rom so that flashing via recovery is still available. This should still receive OTA updates, but they will probably fail to flash because the build.prop file is different (ro.secure=0 and adb). This rom will flash in situations where doaist's CWM friendly updates will not. As a matter of fact, this rom will probably flash on any version of cwm/custom recovery that can read it.
The recovery is modded- it is based on Roach's 3.2.0.1 and only sees the external sd card. I used Roach's ramdisk, but used the the inits, fstab, and ueventd files from the stock recovery. This recovery will seem identical, but you can look at the default.prop to see the difference. In future versions, I might change the version number in case there is any confusion.
NOTE and WARNINGS:
This is for the TF101 US only. The fingerprint checks are removed from the updater-script so it is up to you to know what you are flashing. (Don't flash this on your phone! and if you do, don't say a word and act like your phone is still working.)
This will overwrite your recovery. You can flash it back to something else after a reboot.
This will overwrite your bootloader/EBT. This might have unintended consequences so flash at your own risk. The stock OTA updates the bootloader, so this is why I included it here.
Flash at your own risk. I am not responsible for any damages or consequences.
ALL WARRANTIES REGARDING MERCHANTABILITY OR FITNESS OF PURPOSE, EXPRESSED OR IMPLIED, ARE DISCLAIMED.
Please thank Kuromera for hosting the files on a speedy server and check out the other files hosted there. See his thread here - http://forum.xda-developers.com/showthread.php?t=1549055
Download from here!
US version
ics_92117_stock_EBT_SOS.zip
MD5(ics_92117_stock_EBT_SOS.zip)= 201eae30cbeb00687d5cc69c14469027
WW version
ics_92117_WW_stock_EBT_SOS.zip
MD5(ics_92117_WW_stock_EBT_SOS.zip)= 1c8b1aea6d27643f70891b363ff5fa36
http://www.xdafileserver.nl/index.p...+(TF101)/ROMS/Stock+Roms+by+gee+one/With+Root
Alright, gonna try flash this from Revolution 3.0.1, gotta get back to .17, .11 is so unstable for me, random reboots and shutdowns, and I woke up this morning to a flat battery - from 100% before I went to bed...
Will report back inna bit!
+++
All good, thanks (and thanked)!
Flashed over Revolver 3.11, it automatically optimized the apps on first boot, so far so good.
The weather widget won't update my location, but I've had trouble with that on a lot of the stock firmwares. Could also be from the flash over revolver.
Anyways, thanks for the good work.
I'm very interested in a WW version of your update!!
Anything Ican do to help, just tell me, and I will try. But i might need a little guidingalong the way
Sent from my Transformer TF101 using xda premium
edit: OK, WW version should work now
ics_92117_WW_stock_EBT_SOS.zip
MD5(ics_92117_WW_stock_EBT_SOS.zip)= 1c8b1aea6d27643f70891b363ff5fa36
Having difficulties downloading.
I keep getting "download unsuccessful" If I download straight to the tab.
If I download on my PC the MD5 changes every time. File is listed as 300MB but shows up as 193MB???
Can anyone post a mediafire link?? Or anything.
Are you trying to download the US version?
The WW version is uploading now and will probably complete in about half an hour.
Yeah, my upload is slow.... So be sure to thank Kuromera for hosting the files http://forum.xda-developers.com/showthread.php?t=1549055
If anyone is having problems downloading, I uploaded to Box:
I've shared a folder with you through Box.
To access this folder, visit the following link: https://www.box.com/shared/a479f50d578d27a355f9
Due to my account limitations, I had to upload it as a multi-part zip (6 50mb sections, and a tiny trailing 7th section)
Hope that helps!
Sent from my Transformer TF101 using xda premium
OK, WW version is uploaded. Sorry for the confusion.
Quick question...do we nvFlash this or rename it/reboot as if it were a legitimate stock rom?
gVibeR said:
Quick question...do we nvFlash this or rename it/reboot as if it were a legitimate stock rom?
Click to expand...
Click to collapse
This flashes through clockworkmod or any other custom recovery. I think there is a recovery installer.apk in the dev section, or there are nvflash versions of some of the custom recoveries.
gee one said:
Are you trying to download the US version?
The WW version is uploading now and will probably complete in about half an hour.
Yeah, my upload is slow.... So be sure to thank Kuromera for hosting the files http://forum.xda-developers.com/showthread.php?t=1549055
Click to expand...
Click to collapse
Happens with both the US & WW versions. I watched the download stop at approx 190MB. Don't know what's causing it. I guess I'm the only one.
I';ll check the server hold on
Mmm cant see anything strange, the ww file and us file have both be downloaded succesfully allready but i'll keep watch. The server should support download managers btw.
gee one said:
This is a full rom for stock(ish) 9.2.1.17 and includes the following:
NOTE and WARNINGS:
This is for the TF101 US only. The fingerprint checks are removed from the updater-script so it is up to you to know what you are flashing. (Don't flash this on your phone! and if you do, don't say a word and act like your phone is still working.)
This will overwrite your recovery. You can flash it back to something else after a reboot.
This will overwrite your bootloader/EBT. This might have unintended consequences so flash at your own risk. The stock OTA updates the bootloader, so this is why I included it here.
=====================
The WW version make the same, overwrite the bootloader and recovery?
Thanks
Click to expand...
Click to collapse
Yes, they both update the bootloader and recovery. The recovery is based on Roach's 3.2.0.1. You can flash a different recovery after a reboot if you want to change it.
The stock recovery is too limiting with a rooted rom- it's practically useless actually since it won't always restore if changes have been made.
Updating bootloader really means what in practical terms? I am intending to flash this but this bootloader stuff makes me wonder...
Sent from my GT-I9100 using Tapatalk
So far all fine.
Sound finally on the normal volume.
Reboots not seen yet. (too early to tell)
Only problem i had was busy box and super user but fixed it in the end.
WW version.
Cheers!
gee one said:
Yes, they both update the bootloader and recovery. The recovery is based on Roach's 3.2.0.1. You can flash a different recovery after a reboot if you want to change it.
The stock recovery is too limiting with a rooted rom- it's practically useless actually since it won't always restore if changes have been made.
Click to expand...
Click to collapse
Thanks.
About recovery I understand is ease to flash a newest.
And about bootloader, what change? I can continue to flash custom roms and new kernels?
Obrigado
No one can please post an NVFlashable rom of the WW version??
I only need the system and the boot part, as using a dual boot system i can only update via nvflash
PLEASEEEEE!!
AllanJacques said:
Updating bootloader really means what in practical terms? I am intending to flash this but this bootloader stuff makes me wonder...
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
ValenteL said:
Thanks.
About recovery I understand is ease to flash a newest.
And about bootloader, what change? I can continue to flash custom roms and new kernels?
Obrigado
Click to expand...
Click to collapse
The bootloader gets updated with the OTA so I left it in to stay with the rooted stock experience. The bootloader I included is the one asus includes with their update. I'm not sure if other roms will be expecting older bootloaders. I think most nvflash versions use the oldest bootloader still, and I don't know if this will cause any issues. I don't foresee issues with other roms and kernels, although I did notice I had to wipe data completely to get some of the aosp roms to boot.
As I said, this is directed to someone who wants root and a more stock rom. You can edit system to debloat (and reinstall if you take too much out )
sent from my cyanogen(mod) vision

[HOW-TO] Return to stock rooted ICS US 9.2.1.21 from custom rom (One Stop Shop)

I decided to return to stock today so i could check out the newest ota which was not implemented in my fav rom yet. I soon realized its a pain in the ass to get there. Flash rom, update, update, etc, etc. And even worse is tracking down all the threads required for it.
Though I've narrowed it down to three or four, I thought i'd make a thread to put it all in one spot.
First off thanks to the members/devs that make these updates and roms for us. I dev on the HTC eVO 4g and know how time consuming and tedious it can be.
I am renaming and reuploading all the files required to ensure links stay current and are easy to follow. I will however be linking to all original threads where i got the files as well as giving props to the members who provided them.
I have a US version TF101 and will only be testing on that device. I dont know what works on tf101G, WW, TW models etc
I will update this thread as new rooted ota's come out.
ALL YOU NEED TO INSTALL IS A ALREADY ROOTED ASUS TRANSFORMER WITH A CUSTOM RECOVERY
THIS WILL NOT ROOT YOUR DEVICE, UN-ROOT YOUR DEVICE OR CHANGE YOUR CURRENT RECOVERY.
DONT FORGET TO BACK UP ALL YOURS APPS/DATA
FOR US VERSIONS ONLY
- STEP 1 - WIPE (DOWNLOAD) (This wipe zip was originally provided HERE by mike1986.
This script will erase and format your system and cache partition using EXT4 file-system ---Your external SD card and internal virtual SD card (/data/media) will remain untouched
- STEP 2 - FLASH STOCK ROOTED 9.2.1.11 FULL ROM AND REBOOT/SETUP (DOWNLOAD) originally provided here by MrNago
- STEP 3 - FLASH ROOTED OTA 9.2.1.17 AND REBOOT (DOWNLOAD) originally provided HERE by daoist
-STEP 4 - FLASH ROOTED OTA 9.2.1.21 AND REBOOT (DOWNLOAD) originally provided HERE by gee one
FOR WW VERSIONS ONLY
- STEP 1 - WIPE (DOWNLOAD) (This wipe zip was originally provided HERE by mike1986.
This script will erase and format your system and cache partition using EXT4 file-system ---Your external SD card and internal virtual SD card (/data/media) will remain untouched
- STEP 2 - FLASH STOCK ROOTED 9.2.1.11 FULL ROM AND REBOOT/SETUP (DOWNLOAD) originally provided here by MrNago
CANT FIND ROOTED VERSIONS OF THE NEXT FEW UPDATES THAT DONT REQUIRE ROOT KEEPER, SO IM STOPPING HERE. THIS WILL GET YOU STARTED THOUGH. i JUST DONT WANT TO BE RESPONSIBLE FOR NEWBS THAT CANT READ LOSING ROOT.
FAQ
-Will this root my transformer = no
-Will I lose root if i flash this = NO
-Can i flash this on top of a custom rom = NO
-Will this replace the custom recovery with the stock recovery? = NO, this will not touch your current recovery
-OMG, I lost root after this = NO you didnt or you did something wrong.
Can you explain why step 2 and 3 are needed?
You couldn't go from 1 to 4 if you want 9.2.1.21?
locutus7o9 said:
Can you explain why step 2 and 3 are needed?
You couldn't go from 1 to 4 if you want 9.2.1.21?
Click to expand...
Click to collapse
its my understanding that you have to have the last prior ota installed to be able to install the next. The last update may not include everything from the others.
Will this replace the custom recovery with the stock recovery?
xbs said:
Will this replace the custom recovery with the stock recovery?
Click to expand...
Click to collapse
I knew i'd forget one of the typicals in the FAQ..
Answer is no, this will not change/touch your current recovery
I wanted to return to stock Rom too, but I have seen your topic too late....
I first saved my root with rootsavekeeper
I have wiped cache and dalvik, and then install the rom
Now, I have a bootloop with the Asus logo, and if I try boot in recovery, I have the red robot
If u have a solution, I take it
Sorry for my english
jouix said:
I wanted to return to stock Rom too, but I have seen your topic too late....
I first saved my root with rootsavekeeper
I have wiped cache and dalvik, and then install the rom
Now, I have a bootloop with the Asus logo, and if I try boot in recovery, I have the red robot
If u have a solution, I take it
Sorry for my english
Click to expand...
Click to collapse
What ROM did you flash? If you flashed the official ROM from Asus you unrooted the TF.
Looks like you have stock recovery now.
Yes I have
My biggest problem is to get out on this sh*t Now
jouix said:
Yes I have
My biggest problem is to get out on this sh*t Now
Click to expand...
Click to collapse
Try this.
Hold Vol down plus power button
When you get the option of COld boot Linux or wipe data,
choose wipe data.
jouix said:
Yes I have
My biggest problem is to get out on this sh*t Now
Click to expand...
Click to collapse
What model do you have? B50, B60, B70?
If you have a B50 or B60, try this
Once you get back to stock honeycomb, you'll have to root it again.
@baseballfanz : Guy, you have saved my tablet .. I had almost throwed it in the garbage
@ldc2335 : I have bought it in France, and no idea about the version, sorry .. (I don't have the dock)
Well, now, I willl see if it is stable or not :
- if it is, I need to find the way to root it (but I have read it's not possible with the last Rom, right ?)
- if not ... I will try to return to Honeycomb and sell this piece of sh*t, and I will buy the Galaxy S3 or will wait for the Note 2
Thx again !!!!
I use NVflash way and from modded(rooted/CWM/Overclock) 9.2.1.17 directly flash back to stock clean 9.2.1.17 and it's very quick... and root it agan via Vipermod and flash 9.2.1.21 update zip.. Takes about lest than 30mins..
Thats one way to do it. I just dont wanna re-root etc.
Flash, reboot, flash, reboot, flash, reboot..done Definitly 30 mins or less.
jouix said:
@baseballfanz : Guy, you have saved my tablet .. I had almost throwed it in the garbage
@ldc2335 : I have bought it in France, and no idea about the version, sorry .. (I don't have the dock)
Well, now, I willl see if it is stable or not :
- if it is, I need to find the way to root it (but I have read it's not possible with the last Rom, right ?)
- if not ... I will try to return to Honeycomb and sell this piece of sh*t, and I will buy the Galaxy S3 or will wait for the Note 2
Thx again !!!!
Click to expand...
Click to collapse
If you can return to honeycomb, then just reroot and then flash any rom you want. Whats the issue?
Simple, clear, straightforward directions - very nice. The file naming is clever also, no "now which file do I flash next?..."
Does anyone have a clue where i can find cwm flashable WW Stock Roms with Original Recovery and no root?
Want to revert back to full basic!
(Tried to flash Stock Rom from Asus Website via CWM, didn't work...)
Try This
JohnMcLane said:
Does anyone have a clue where i can find cwm flashable WW Stock Roms with Original Recovery and no root?
Want to revert back to full basic!
(Tried to flash Stock Rom from Asus Website via CWM, didn't work...)
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=1558170
i just used the search bar above, im sure theres more than this one.
You will also need a NVflashable tf101 with this....
I hve succesfully flashed the .11 version, but when I try to update to the next version, it restarts, and starts loading the installation as it is supposed to, ut then it says "installation aported"
I am using Rootkeeper and CWM, and have temp. unrooted, I am using a B70 WW.
Anyone have a solution?
Sumsar94 said:
I hve succesfully flashed the .11 version, but when I try to update to the next version, it restarts, and starts loading the installation as it is supposed to, ut then it says "installation aported"
I am using Rootkeeper and CWM, and have temp. unrooted, I am using a B70 WW.
Anyone have a solution?
Click to expand...
Click to collapse
Same here, its an assert issue, I remember dealing with it when flashing my epic touch and I believe that had to do with the version of CWM that it was being flashed from
can anyone confirm?
EDIT: B40 using roach v5.5.0.4 r2 CWM

Need to return to stock to sell, what is the proper way?

I want to return to the latest stock firmware, no root, no CWM, everything factory defaulted. There are so many stock ROM threads I'm not sure which one to choose and most of them apparently leave CWM on the device.
What is the proper way to factory this thing?
Also, does flashing a stock ROM allow OTA updates from ASUS again?
Just download from ASUS site and flash with CWM, will make Completely stock, otas and all.
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
Pick your region and flash.
I'm sorry, I forgot to mention to run a superwipe script (theres one in the ARHD thread) then flash the asus fw on top of it, this will be the equivalent of a NvFlash.
Does both methods (superwipe/CWM and NVflash) put the default recovery from ASUS back on?
Yes. If you're considering the nvflash method I assume your tab is sbk1 right?
The reason I suggest superwipe and flash of firmware is he may be Sbkv2, which would make NvFlash useless. The asus update contains an SOS update in the blob partition, so yes, it would put stock recovery on.

[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.

Categories

Resources