yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] patates:
Impossible to get OTA 2.2.33.138

First, sorry for my english ... Sadly I can't update my TF103C with this OTA. Let me explain: When I have received my tablet I rooted with Root Zenforce and I have deleted some "unnecessary" system apps (with Root Uninstaller) as PCLINKS, MEMO... There are some days the tablet has proposed to make an OTA update (release xxx.138) and I have accepted this installation, the tablet restarts and : big crash, big fear. Fortunately the tablet has rebooted handing the old settings. I thought at first to an incompatibility with the root but going to take a look in the log in "\ cache \ recovery" I discovered that an original app missing was the origin of the bug (problem due to the lack of PCLINK). I read that Asus Tablets didn't tolerate the removal of any system implementation when OTA update. So I have reinstalled in applications system these famous Asus apps I had saved for safety: The update tool doesn't offer me anymore this OTA, when I launch a new update request I have the right systematically to "your system is up to date" and yet I'm still xxx.135. So I'm stuck with the problem of the battery. I have unrooted: without success, it doesn't matter, I also emptied the cache CM / DM / Google Frameworks (and stopped processes) also unsuccessful. I conducted a "wipe data factory reset" and "wipe cache partition" via the original recovery of the tablet (vol - + power / recovery) doesn't work either. Besides, would you have any idea when TWRP recovery will be compatible with the TF103C? I also thought of a filtering MAC address by ASUS server but it seems unlikely to me. Someone tells me It could be a build.prop problem.... It may be that I definitely want to benefit from the OTA update because it solves the battery problem, very annoying. I wanted to downgrade to the latest rom Asus dated September 2014 (V2.2.33.101, about 700MB) with recovery option and a "adb flash all" but Asus says the downgrade can cause problems. The downgrade via a zip image on the internal memory or micro SD does not work, only the update function works. I think it's weird that it's impossible to reset the tablet with a clean rom. I would have been able to perform all the updates OTA and repair the battery software problem. I would be extremely grateful if you could upload the file dlpckgfile for the OTA 138, so I could force the update (recovery, sideload), I was looking for the file from anywhere on the internet ... If you have another solution I take! If Asus comes a new version of the ROM I would be very happy .... Thank you for your help :)
[Android Q&A, Help & Troubleshooting] Brick3d:
Soft Bricked

hey guys, in the honor of my name...I have an issue..

I just got this beast tablet a while ago, rooted it, and decided to make 1 or 2 small build prop changes (dalvik heapsize and utility modified from 0.75 to 1.25) and delete some of the bloatwarez on the devices.

Just today, I wanted to make a reboot because I like to do that everyday to keep things smooth..

It crashed at the kernel (asus) logo. Now ive been googling like crazy to find a solution to this, but nothing seems to fix it

heres what i did:

* wipe cache

* wipe data

* download latest firmware (i hadnt done the ota upgrade when system was working) and tried installing via sideload (gave me the error about the signature being incorrect)

* placed FW (unzipped once with the full name) in the root of my micro SD card and tried to get the recovery to recognize it (which it should if i understand all the posts right)

If anyone of you knows how to fix this (and by the way..this device definately needs some CWM or TWRP love) please share!!

!!!!EDIT!!!!

Is there anyone with a rooted tf103c that can make a backup of system.img using terminal or ADB?

regards

Brick3d
[Android Q&A, Help & Troubleshooting] xboxhacker:
help with root....

hello people.

i need some help rooting my K010 MG10 TF103c. I bought it at besbuy. It has the OTA .138 build.

I have tried the RootZenFone version 1.4.6.4 The TF103c is listed as working to get root. Upon ever try, it says FAIL.

So i goto fastboot and erase ADF and reboot as someone instructred. Run RootZenFone again, still FAIL. Even had it in airplane mode.

SO whats next, what am i missing? I have already tried Z4root, TowelRoot and Root Genius....all no good.

Thanks!!
[Android Q&A, Help & Troubleshooting] majored:
system image rooted k010

im on mine right now where is this img at ??? and would i post that ?? 6362901450 if its not huge ill zip n text . Better yet you have 4shared??

---------- Post added at 11:38 AM ---------- Previous post was at 11:18 AM ----------

go to 4shared i use their apk. search root zenfone im using

Rootzenfone.apk 1.4... theres your root exploit
[Android Q&A, Help & Troubleshooting] xboxhacker:
---------- Post added at 11:38 AM ---------- Previous post was at 11:18 AM ----------

[/COLOR]go to 4shared i use their apk. search root zenfone im using

Rootzenfone.apk 1.4... theres your root exploit[/QUOTE]

i have tried several different versions of rootzenfone. none of them work to root my k010. the most recent one i have tried was version 1.4.6.4r

I put the tab into airplane mode. Click "ok".... it says "hacking" , then says "failed"

And according to this, K010 should work with it.

http://www.asuszenfoneblog.com/2014/10/download-rootzenfone-1464r-apk.html

:confused:

---------- Post added at 08:30 PM ---------- Previous post was at 07:53 PM ----------

What version of build does your K010 have? And what version of android does it have?

Thanks!
[Android Q&A, Help & Troubleshooting] BethanyJane:
Did you make sure you turned your WiFi off and tell it to forget all WiFi networks? I have the TF103C (K010) android 4.4.2 and my first attempt with Rootzenfone 1.4.6 was an epic fail until I followed those instructions properly lol

PS, I don't think I had it in airplane mode either....
[Android Q&A, Help & Troubleshooting] majored:
k010

ww 2.2.33.112
[Android Q&A, Help & Troubleshooting] xboxhacker:
I GOT ROOT!! Thanks to Transformerforums_dot_com

I have the latest OTA version BBY-2.2.33.138 KK4.4.2

Had to go about it the hard way. LOL

I downloaded the Asus Demo APKs and the calculator. Installed all 3. The demo app crashes EVERY TIME it tries to start. So i ran the RootZenFone v1.4.6 anyway. It said hacking...then tried to run the demo again, then said reboot. I rebooted it, it updated some apps, and now has root!

Here are the APKs and info about the demo app.

http://www.asus.com/microsite/demo/Demo2.1_content.htm

Download and install the files from the BBYexclusive.zip (ONLY IF YOU HAVE THE BBY SKU UNIT)

Open the calculator and type "nene741603enen" then hit the "=" key for the trigger.

Hit OK in the warning.

Hit OK for offline mode

Start the RootZenFone app

Turn off WIFI

In RZF hit OK to root. It will say hacking... then it will try to start the demo mode.

Once it completes, reboot the tablet.

Other SKUs are available on the site. Use any of these demo APK files, and information at your own risk!
[Android Q&A, Help & Troubleshooting] Botandroid:
After the last update my Asus charge like a charm!
[Android Q&A, Help & Troubleshooting] Brick3d:
http://xdaforums.com/showthread.php?t=2450045 < that is the way to pull system.img from your tablet. I have a 4 shared account or Mega if you could upload it there :) thanks again

#Edit#

Here is another way to pull system.img using ADB, its somewhat easier

http://howtorootcherrymobilesnap.weebly.com/adb/how-to-extract-img-files-via-adb-ex-bootimg
[Android Q&A, Help & Troubleshooting] Monki:
Patates - Thanks a lot for your post and for hosting the 138 update. I'm still struggling to force an update due to an AWS.APK error...but i'm getting there haha.
[Android Q&A, Help & Troubleshooting] Brick3d:
Getting stuff done

Hey guys,

Forum member Monki has been so kind to go through the effort of getting me the system.img file i need to flash back my system (through ADB).

Now, as I tried to flash it, it gives me the error about the .img file exceeding the max download size.

Does anyone know a fix for this? Or...if it would be possible to get an update zip forced on the device, mine keeps giving me a checksum error at the end of it and cancels (verification error)

MIght this be due to the flashing of a wrong firmware? I cant remember the firmware i was running but never did an upgrade through ota. Ill try it with all different updates available on the asus website

Hope someone can help me on this
[Android Q&A, Help & Troubleshooting] majored:
zaggskeys universal

beautiful curved BT keyboard i love it the keybd protector dubbs for an upright for your device 79.99$ ouch cost more than my microsoft/mouse dongle keybdcombo BUT my thumb to pinky practically span the whole keyboard OH YES i can play it with one hand

---------- Post added at 12:53 PM ---------- Previous post was at 12:45 PM ----------

https://docs.google.com/file/d/0B3tP9VfkRMWtbVFwRW14WDhfejA/edit?usp=docslist_api
[Android Q&A, Help & Troubleshooting] MZachEchem:
Different versions of TF103c

Been trying to study over this thread as a new field of study for me (pure noob). Had been working with developers for my non-profit organization developing educational program centered around the TF103C. They had successfully been rooting the TF103c and now I ran into new problem.

By luck of the draw previous development had been done with TF103c-A1-Bundle & everything worked fine. Recently purchased a dozen TF103c-A2-EDU-BK and can't root. Anyone have ideas? Thanks.
[Android Q&A, Help & Troubleshooting] AWildColin:
If you can get a root shell via adb while in recovery, you should be able to use dd to push the system.img to the equivalent /dev/mmcblk#p# partition, assuming the dd binary ships with the stock recovery on this tablet.

I ordered one and it should be arriving today. Even better, I have some development experience and if I can find the time, I'll probably be able to put together a working custom recovery, depending on if the bootloader is locked or not.
[Android Q&A, Help & Troubleshooting] Brick3d:
Thanks for your insight, and welcome to the forum here! I have already tried to gain root ADB acces, but it seems to be locked. I can only issue a certain amount of commands, none of them give me the system.img I need. Like I said, Monki has given me his system.img, but unfortunately, the image size cannot exceed 500mb (the one i have is 1.7 gb) and I have no clue on how to decrease it enough to get it to 500. Maybe you could lend me a hand on that?

Also, the bootloader is locked, so no possibilities of CWM. If I had CWM, it'd be an easily solvable issue i guess...
[Android Q&A, Help & Troubleshooting] AWildColin:
Have you tried yanking the system.img from a stock update.zip from Asus for the same version you're running? Is it also >500mb?

---------- Post added at 09:26 AM ---------- Previous post was at 09:21 AM ----------

Better idea. Check out http://xdaforums.com/moto-x/general/verizon-fastboot-flash-fix-t2489249

I thought this issue sounded familiar. It's for a different phone, but that modified fastboot binary *should* let you get past the file size limitation.
[Android Q&A, Help & Troubleshooting] Brick3d:
Well it gets me somewhere... Now it comes back with " could not allocate 18790*** bytes" (which is the system.img size)

Edit: Since ou seem to be having more experience with development than i have myself, do you know if the total image size can be decreased by using 4096 blocks when extracting system.img?
[Android Q&A, Help & Troubleshooting] sadsac:
Just got one of these for my wife and its a conundrum - don't update the firmware but root it and remove bloatware or update firmware but then can't root. I've gone option 1!
[Android Q&A, Help & Troubleshooting] AWildColin:
Doubtful. Because the bootloader is locked, it probably won't flash any system images that aren't signed with a certain key. Trying to shrink the image will almost definitely cause any package verification to fail. I wish I had more time to work on this.

The only thing I can suggest is trying to find a custom fastboot binary that will let you successfully upload the stock system image without *****ing about the image size (or beg Asus to unlock the bootloader so we can get a custom recovery image on that bad boy with root access and dd).

Try the fastboot binary on http://highonandroid.com/android-sm...re-error-could-not-allocate-1778070480-bytes/?
[Android Q&A, Help & Troubleshooting] el_polilla1990:
Hello I have this tablet, I have bootloop for having changed the build.prop, you could help me recover? thanks in advance :)
[Android Q&A, Help & Troubleshooting] el_polilla1990:
Already solved, I found the system.img of .138 and install it for fastboot, with the command fastboot flash system system.zip after unzipping the file. I hope help you

https://cloud.mail.ru/public/e77f5b...C-2.2.33.138-release-user-20150108-signed.zip
[Android Q&A, Help & Troubleshooting] csj2k:
Thank you so much!
[Android Q&A, Help & Troubleshooting] fidorulz:
Anyone please help

I erased some bloat and now cant update to 138 as per above

I read this post many times but still not sure what to do. I know it says to patch the missing apps by downloading the firmware which I did but im not sure what files need to be patched or how

I included my logs from recovery in case it helps.

I think its system/app/Books.odex thats missing but not sure

https://mega.co.nz/#!zBkn1R6C!b8jtPVHmdFWXxrx8wqGsnndOgNXGiHlwlR-NKqYkH-o

Any help is welcome
[Android Q&A, Help & Troubleshooting] veverone:
Stock firmware, no root, how to OTA update from *.101

Hi,

I've purchased this tablet not long ago and, performance wise, it is very good. However, the memory management is a bit dodgy and my apps crash when less than 20% of RAM is free (less than 200 MB).

Maybe this was fixed from version 101 to version 138 and I would like to update.

However, ASUS has not officially delivered a complete firmware file and I've read here that most of you recieved intermediate updates via OverTheAir method.

Personally, I recieved such an update notification once, when I first bought this, and the instalation failed. It had version *.80 on it.

I knew that an update exists, so I've downloaded the *.101 firmware from ASUS official website and placed it on an SD card.

The update notification appeared this time and it was succesfull.

However, Since, I did not recieved any new notification and everyone says that updates are pushed throught OTA to version *.138.

Why I'm not getting that notification? I did not modified the stock ROM in any way and I did a factory reset right after updating it.

Do I need an SD card to get it to appear?

Kind regards
[Android Q&A, Help & Troubleshooting] baronz:
Me too, i have the same problem, bought the tablet, asked for update that failed. Now i'm stuck on version .101, can't get otas and asus support claim that .101 is the last available version :(
[Android Q&A, Help & Troubleshooting] baronz:
can you tell me how to flash like you did ? do i need root ?
[Android Q&A, Help & Troubleshooting] silver91342:
Thanks man this worked to get me from .122 to .138.

For the people having trouble it flashes like a nexus using adb and flash update batch file in the link above. I can see how people had trouble flashing it, I did have root and deleted system app's so I wasn't getting OTA's anymore. I tried sideloading the updates in adb but that didn't work so I unrooted and factory reset. This method is very similar to how you flash a nexus, I have done it many times on my Nexus 4,5,7,9 so I recommend at least you know some of that process.

Little guide for everyone else (I am not responsible if you brick your device, do this at your own risk!!!!) I DID NOT have root and bootloader is locked.

I had Google adb USB drivers installed already (http://developer.android.com/sdk/win-usb.html)

I installed Intel adb USB drivers proir to flash (https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices)

I use Minimal adb to flash my nexus, so If you never tried this tool before I don't recommend you flash this way (http://xdaforums.com/showthread.php?t=2317790)

I used the full upgrade installer from el_polilla1990 (someone really should mirror that before it goes away)

1. Install drivers and download system image, its big file so it takes a while (1.6GB).

2. Put device into Droidboot(fastboot) mode by turning it off and holding VOl+ and Power at the same time

3. Connect to PC USB while in fastboot

3a. If you have minimal adb installed then run the command "fastboot devices", if you get the serial number in return this method should work then close adb.

4. Unzip the file once and inside should be update_image.bat which is a one-click installer (signed correctly). Inside this folder is minimal adb files anyway so I recognized that its a one-click installer.

5. It should take a while flashing all the parts but once it's done the tablet will reboot to .138.

The system.img is too big to flash itself since the one click parsed it into 3 parts to flash it correctly, but a FULL .138 system.img is in there :good:.
[Android Q&A, Help & Troubleshooting] baronz:
Thanks silver91342, i will try this or else i have to send back the tablet to asus cause it won't update. Do you think that if something goes wrong i can revert to the UL_K010_v2.2.33.101.zip found in asus website by putting it on the sd ?

EDIT: thank you very much, i did as you write and now i got v2.2.33.138 firmware working !
[Android Q&A, Help & Troubleshooting] silver91342:
Cool! was waiting for someone else to try it. BTW if you had UL firmware on your tablet you shouldn't flash a WW one on there! I don't know if the .101 files on Asus site is a one-click like this one, but I assume it should be able to recover it, although I don't see why anyone would want to now that we have a one-click install/restore .138.

I haven't had any bugs so far and the tablet is smoother now than .122. Flashing via adb has always had the best results for me, its how you normally flash a nexus.
[Android Q&A, Help & Troubleshooting] baronz:
i had a WW .101 and flashed the WW .138, now the battery bug is gone and the tablet is smooth and working fine !
[Android Q&A, Help & Troubleshooting] pretty pixel:
Factory image/firmware download

Hi - can someone please provide me with the link for where I can download the latest UK factory image/firmware. Guidance on flashing procedure would also be appreciated. Thank you.
[Android Q&A, Help & Troubleshooting] pIxiLatEd:
So, I have read through this and I am a little confused. Will this method/file posted by el_polilla1990 work if you rooted the device and removed the bloat? or will I have to replace the bloat first in order for this to work? Thanks.
[Android Q&A, Help & Troubleshooting] sadsac:
Worked for me but I unrooted first and factory reset as advised, used the linked intel USB drivers and minimal adb
[Android Q&A, Help & Troubleshooting] pretty pixel:
Firmware link

Could someone provide me with a link to the WW .138 firmware please. It is not available on the UK Asus website. Thank you
[Android Q&A, Help & Troubleshooting] silver91342:
This is a full flash to stock .138, it should wipe root and it shouldn't matter if you uninstalled app's.

ASUS never posted the factory images of any updates to this tablet, el_polilla1990 somehow got a restore to .138 (one-click) that flashes the tablet with .138 stock.
[Android Q&A, Help & Troubleshooting] pIxiLatEd:
This worked like a champ! While I was sure to mash the button, I still want to type "Thanks" to el_polilla1990 & all who contribute.
[Android Q&A, Help & Troubleshooting] pretty pixel:
Thank you for the reply. I am currently on WW .138 and rooted. Is it possible to reflash .138 completely to remove root? If so, how do I do this please? Thank you.

---------- Post added at 10:55 PM ---------- Previous post was at 10:50 PM ----------

I am already on .138. Can I reflash following your method above to remove root?
[Android Q&A, Help & Troubleshooting] silver91342:
To remove root I believe you can just do a factory reset from recovery.
[Android Q&A, Help & Troubleshooting] pretty pixel:
Root still remains after a factory reset.
[Android Q&A, Help & Troubleshooting] Botandroid:
Is there a simple and ease way to make root? EROOT for example?
[Android Q&A, Help & Troubleshooting] pretty pixel:
Thank you for the instructions. I can confirm the procedure has re-flashed my device successfully and removed root. Thank you also to [MENTION=5735412]el_polilla1990[/MENTION] for the firmware :)
[Android Q&A, Help & Troubleshooting] pIxiLatEd:
Install SuperSU if you don't already have it. Go under settings and scroll down a ways. Its under cleanup ... full unroot.
[Android Q&A, Help & Troubleshooting] Tr33x0rs:
I purchased this tablet about 2 weeks ago and really enjoy it. I have similar problems as others, where my apps will just close out of nowhere. I also do not like that I cannot write to my SD card, and when I hook it up to my PC, and try to view files, its indicating as though there is nothing in "/documents/", although I'm certain there is.

Does rooting the device allow you to write to the SD card? Also, does anyone have any ideas as to why I'm not able to view my files from my PC? Thank you in advance for the help!
[Android Q&A, Help & Troubleshooting] baronz:
3rd part apps can't write to sd since kitkat, some app has a fix for this if you are rooted.
[Android Q&A, Help & Troubleshooting] kbfixit:
root post .138 OTA

I followed the instructions with RootZenPhon 1.4.5 and 1.4.6 and both tell me "failed" after deleting ADF in the fastboot console. Has anyone been successful rooting for the first time on .138?
[Android Q&A, Help & Troubleshooting] FINAL94:
New update failed

I'm on .138 and i have download the update. I have a copy of the file dlpgkfile but when i force the ota with the guide in the older post it don't work. Whit the older update (101-138) it work but whit the last the recovery don't begin the install even with the file "Command" it the right place please help me!

Sorri for the bad englesh i'm italian ;)
[Android Q&A, Help & Troubleshooting] SunOfMan7:
Alternate root method!

After struggling with the op root method that always failed for me. I searched the internet for alternate root methods. I googled Intel Bay Trail z3745 root and found a way to root our transformer t103 using a tethered recovery option. I dont know if we can post other sites url but a quick search is not hard. You have two options. Cmw or Twrp. I used the Twrp method and after four attempts, I finally achieved root. I know im not giving much detail but im just letting everyone know there is another way. My only problem is that after months of trying to root this thing with no progress, when I finally did root I was so happy that I didnt make a back-up. Smh. Dont know if Asus have plans to update this thing. Would be nice but I would have to revert back to complete stock.
[Android Q&A, Help & Troubleshooting] SunOfMan7:
Here yall go. Enjoy.

http://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096?nocache=1
[Android Q&A, Help & Troubleshooting] patates:
Would someone kindly upload files DLPKGFILE(.zip) 141 and 143 (WW SKU) on Google Drive (or other) because I want to force OTA update with adb . The current version of my build is 138 but the update via android settings not working. Thanks a lot :)
[Android Q&A, Help & Troubleshooting] mbush78:
Here is 141, I haven't received 143 yet

http://xdaforums.com/android/help/asus-transformer-tf103c-ota-update-141-t3195325
[Android Q&A, Help & Troubleshooting] SunOfMan7:
Strange I never received the 141 or the 143 update! All my asus apps been updating lately but no system updates and i check regularly.
[Android Q&A, Help & Troubleshooting] mbush78:
I just got this 141 today. I think it tried to update a month ago but because I'm rooted and deleted a bunch of items that update failed and I thought no more of it till today's notice showed up. So I backed up the file, flashed the 138 system.img, rerooted then, copied the update back over and forced it to apply through recovery. All seems ok at this time, waiting to see if a 143 comes in or not. Honestly first I heard of the update