[Q] EasyFlasher problem with Transformer TF101G - General Questions and Answers

Without going into a long sad story, I have an Asus Transformer TF101G which is effectively bricked.
It boots up into a semblance of CyanogenMod 9 but without any basic Android features/apps?
So I'm attempting to unbrick it using EasyFlasher 0.8.3.
I have a folder on my desktop with all the necessary files downloaded, Easy Flasher, APX drivers, Asus stock rom etc.
I have the APX drivers installed on my PC.
I have my TF101G connected to my PC in APX mode, confirmed in Device Manager.
I have the Asus stock rom in a folder called asusupdate, US_epad-user-9.2.1.17.zip
When I run EasyFlasher i get the following messages
Flashing Asus stock zip
>Extracting files.. please wait..
>Extracting blob archive..
ERROR! Blob wasn't extracted! Check your .zip file in AsusUpdate folder!
Make sure it is the original .zip that you downloaded from ASUS
>Extracting from blob...
>Cleaning up before flashing...
>Checking file sizes
>SOS size 0kb
>APP size 0kb
>EBT size 0kb
>LNX size 0kb
Done!
What have I done wrong?
Do I have the wrong folder/directory structure? 'C:\Users\Chrisp\Desktop\Unbrick TF101G'
Is this process OK for a TF101G or is it only for a TF101 ?
Any/all advice would be appreciated!
Thanks
Chris

chrisp9au said:
Without going into a long sad story, I have an Asus Transformer TF101G which is effectively bricked.
It boots up into a semblance of CyanogenMod 9 but without any basic Android features/apps?
So I'm attempting to unbrick it using EasyFlasher 0.8.3.
I have a folder on my desktop with all the necessary files downloaded, Easy Flasher, APX drivers, Asus stock rom etc.
I have the APX drivers installed on my PC.
I have my TF101G connected to my PC in APX mode, confirmed in Device Manager.
I have the Asus stock rom in a folder called asusupdate, US_epad-user-9.2.1.17.zip
When I run EasyFlasher i get the following messages
Flashing Asus stock zip
>Extracting files.. please wait..
>Extracting blob archive..
ERROR! Blob wasn't extracted! Check your .zip file in AsusUpdate folder!
Make sure it is the original .zip that you downloaded from ASUS
>Extracting from blob...
>Cleaning up before flashing...
>Checking file sizes
>SOS size 0kb
>APP size 0kb
>EBT size 0kb
>LNX size 0kb
Done!
What have I done wrong?
Do I have the wrong folder/directory structure? 'C:\Users\Chrisp\Desktop\Unbrick TF101G'
Is this process OK for a TF101G or is it only for a TF101 ?
Any/all advice would be appreciated!
Thanks
Chris
Click to expand...
Click to collapse
Bumping this question as I really do need help, or at least some sort of response.
Thanks
Chris

Related

[Q] XXKG5 files for ODIN

Hi,
I need help from kind heart people in this forum if they can help to re-packaged the XXKG5 files from xda-developer into ODIN flashable files like example
CODE_I9100XXKG5_xxxxxx.tar.m d5
MODEM_I9100XXKG5_xxxxxx.tar.md5
GT-I9100-CSC-xxxxxx.tar.md5
I have downloaded the XXKG5 files from xda-developer BUT the package contains files like boot, cache, factoryfs, hidden, modem, param.lfs, sbl and zImage of which I cannot flash with ODIN.
Any help would be greatly appreciated as I would like to have XXKG5 on my SGS2.
Thanks.
i guess you extract the .tar file don't you? just double click 7e file that you originally download and use the extracted file as it is. do not need to extract once again.
prydoxs said:
i guess you extract the .tar file don't you? just double click 7e file that you originally download and use the extracted file as it is. do not need to extract once again.
Click to expand...
Click to collapse
I didn't. Yes I extracted the first compressed file dowloaded. Then all I get are the files like in Image 1. Since Odin cannot flash the compressed file in Image 1....IF I extracted the compressed file in Image 1 then all I get are the files like in Image 2...
As you can see, either way I can't flash with Odin.
If you downloaded from xda it shouldntt look like that.You only need to double click on the file and it extracts.if you didn't download from here then here it is
http://forum.xda-developers.com/showthread.php?t=1075278
Read the first notice part about extracting the file to make sure you understand clearly.

[Q] Extract Files from ROM

Hi there,
Is it possible to extract files from ROMs here?
Tried open with 7-zip, but only i see are errors.
what exactly out of the roms are you trying to open?
Sorry, i tried open ROMS for CWM, like PRIME or Revolver.
ok but what type of file? is it just a zip or is it the blob file
It's a blob file inside the cwm rom zip file... what to do?
Maybe try this?
http://forum.xda-developers.com/showthread.php?t=1068548

[Q] some questions about update official blob

Hello, I'm very new to this forum so plz forgive me if I post this in the wrong place.
I recently bought a asus tf300 and flash the cmw recovery img. Since I'm unlock the bootloader, I no longer get update from ASUS website. My question is how am I manually update the blob file that I download from ASUS support website.
I have look alot threads about this issue, and I find out there are mainly three methods that can update the blob.
1. Using Asus Manual upload:
According to Asus website, they said just put the zip file in the micro sd card and the system will pop up an notification that will help u upload.
2. Using CMW to upload:
upload the blob with CMW recovery. There are some thread that tells me it will brick the device. But some people said it is ok to use CMW to upload the blob, therefore I'm a little bit confused about this method.
3. Wolf's way:
http://forum.xda-developers.com/showthread.php?t=1622628
The following is my questions:
1. what is the difference between these three method?
2. if the CMW is okay can someone tells me the right way to upload the blob. Such as using the original build.prop something like that?
3. is it ok to use the wolf's way to update the blob?
Sorry for so many questions and my poor English.
I'd use the ADB / Terminal emulator method (Wolf's way mostly)
Place on transformer, then flash the 'blob' file through the staging partition.
You'll need to reinstall CWM and reroot everytime you do this, unless you manually extract the SOS partition out of the blob file ASUS gives you with blobtools then repack it.

OLiFE prime offline, need system.img, boot.img, recovery.img

Hey guys,
it seems that the original OLiFE.tar.gz file with system.img, recovery.img and boot.img is offline, and i need these files for flashing
it with frankstools.
Has anybody got a copy of the OLiFE.tar.gz or can explain to me how to get the system.img, recovery.img and boot.img out
of a nvflash android rom?
i want to flash http://forum.xda-developers.com/showthread.php?t=1852702 this ubuntu image
thanks in advance
Im uploading OLiFE prime atm but its gonna take a loooooooong time with my upload connection lol
I'm currently downloading: OLiFE-Prime-Edition.tar.gz
curti.nogg said:
I'm currently downloading: OLiFE-Prime-Edition.tar.gz
Click to expand...
Click to collapse
lol ive just been uploading it for like the last 6 hours.... oh well now we have a mirror
Thanks a lot! Yesterday I was desperate because the whole Internet relied on lilstevies server
If you already have an android rom installed use the olife -> backup -> stock option and then copy the files from the backup folder to the images folder
Ok any nvflashable image has this three components included, they are just named blob.APP, this is system.img, blob.LNX, this is boot.img, and blob.SOS, this is recovery.img.
Just rename them and you have your files.
Ananasnonym said:
Ok any nvflashable image has this three components included, they are just named blob.APP, this is system.img, blob.LNX, this is boot.img, and blob.SOS, this is recovery.img.
Just rename them and you have your files.
Click to expand...
Click to collapse
Cheers couldn't remember the files to re-name, ill chuck that up on the install guide
Any chance someone still has a valid link? I’ve dug up an old TF101 which could still be useful on Ubuntu…

[Completed] [Q] Unknown Serial, Cannot Wipe, or Factory Reset. Stuck in Boot Logo Screen

Hi
I have an Asus Fonepad 8 (K016 or FE380CG. 2GB RAM, 16GB ROM), I know it's not popular around here.. But any help is very welcome.
My initial device's state
- Stock rom 4.2.2
- Root (installed: Greenify, App Ops, Coolify, System App Remover (Jumobile))
- I uninstalled about 20 system apps
then I received OTA update to Lollipop and it displayed the infamous android "error" with the red exlamation mark. so i uninstalled every root app, EXCEPT System App Remover (silly me i forgot the most crucial part), probably meaning that some system apps are still gone. I also did full unroot inside SuperSU.
I tried factory resetting in order to successfully update to Lollipop, but once I get to the setup Welcome screen, these dreaded messages show up. ENDLESSLY
Unfortunately, com.android.phone has stopped working
Unfortunately, com.android.systemui has stopped working
Unfortunately, com.process.acore has stopped working
Click to expand...
Click to collapse
One time, the endless torture stopped and I was able to access Settings. I opened Applications and there was very (infact, too) few apps installed. Less than 200MB of RAM is used. I thought the factory settings failed, so I tried doing the same thing again in fastboot mode. But still a no-go.
Then I tried
Code:
fastboot -w
and it did say "success" but it couldn't format. "File system not supported". I forgot the exact message but that, i think is the point.
In Droidboot Provision OS, there is an option called "SD download". I put the official ROM for my device (.zip) in my SD card, then tried doing exactly that. Still no-go. Below is the entire (not exact) process
Copying E:\ASUS_UPDATE.zip to /cache (i renamed my firmware .zip file to that)
Copying asus update file (i have no idea where this file (if it even is a file) is located)
then my device reboots
a brief "no command" error appears
reboots back to my faulty state
Click to expand...
Click to collapse
I then tried to erase cache and userdata, and ran
Code:
fastboot update fw.zip
This appears
archive does not contain android-info.txt
archive does not contain android-product.txt
Click to expand...
Click to collapse
Desperate enough, I tried to again erase cache and userdata and system (probably my worst decision). and the device is now stuck in boot logo screen.
My awesome representation of my device's boot logo screen
ASUS
powered by
ANDROID
Click to expand...
Click to collapse
I booted my device back to fastboot, and my serial number was shown as "unknown". The same appeared when i type below code in cmd in my PC.
Code:
fastboot devices
One thing to be noted. I am really confused with ASUS's official firmware.
There is no recovery.img, system.img, userdata.img or cache.img
Here is a list of files and directories inside of it:
META-INF (folder)
recovery (folder, 2 files: recovery-from-boot.p and install-recovery.sh)
system (folder, a lot of folders inside like "app", "bin", "etc", "fonts")
boot.img
fastboot.img
splash1.img
splash1_s.img
splash2.img
splash2_s.img
splash2.img
splash2_s.img
ifwi.zip
modem.zip
Click to expand...
Click to collapse
I do not have nandroid or any kind of backup.
I have googled and tried everything I could find for the past 9 hours. So, i think it's high time I ask experts about this.
I am thinking of taking it to the service center. But any more knowledge regarding this beforehand is very valuable to me.
I know this is too long but I've highlighted the most important parts.
Any kind of help is welcome.
Hi, thank you for using XDA Assist. Unfortunately there is not a dedicated forum and there is very little information about your device on XDA. There is nothing on how to flash the stock firmware. But it sounds like that's what you need to do right now. Looking at ASUS's web site it looks like there should be another zip file. ifwi.zip, in the one you extracted. That's most likely where the image files you are missing reside.
jd1639 said:
Hi, thank you for using XDA Assist. Unfortunately there is not a dedicated forum and there is very little information about your device on XDA. There is nothing on how to flash the stock firmware. But it sounds like that's what you need to do right now. Looking at ASUS's web site it looks like there should be another zip file. ifwi.zip, in the one you extracted. That's most likely where the image files you are missing reside.
Click to expand...
Click to collapse
Hi. Thank you so much for replying and taking the time to read my long "story".
Sadly, yes. There is little to no community for my device.
Regarding ifwi.zip, below is part of the content of the file.
FE380CG_16_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_16_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
FE380CG_1_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_1_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
FE380CG_2_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_2_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
FE380CG_32_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_32_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
Click to expand...
Click to collapse
I doubt that it's the system image. The file size is just way too small.
The folder with the largest size is System, and inside there are a lot of folders (app (system apps and asus's bloatwares are inside), bin, etc, fonts, framework, etc, and build.prop). It almost looks like ASUS doesn't package system into a .img file, rather in a folder. That's why I am also looking for a script file that "copies" this folder into the device, if it exists.
I am now downloading the latest (was just uploaded by ASUS) firmware, which is Lollipop.
I'll dig in the file and see if I can find anything interesting.
Ok, download's finished.
Below is the root directory of the new firmware.zip
META-INF (folder)
recovery (folder)
system (folder)
boot.img
droidboot.img
splash.img
file_contexts (no extension)
l_recovery.fstab
partition.tbl
ifwi.zip
modem.zip
Click to expand...
Click to collapse
ifwi.zip has the same contents, only a newer version.
I tried fastboot update fw.zip and the same error pops up
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
I have attached a screenshot of updater-script I found inside META-INF/com/google/android. and screenshots of the directories of the firmware zip's contents. Hoping any is helpful to solve this.
First, I know nothing specific about your device. But do you have a custom recovery on your device? CWM or TWRP. The updater-script looks like it should be flashed in a custom recovery, not with fastboot. Edit, also, what's in the system folder, etc. Are there image files in there?
jd1639 said:
First, I know nothing specific about your device. But do you have a custom recovery on your device? CWM or TWRP. The updater-script looks like it should be flashed in a custom recovery, not with fastboot. Edit, also, what's in the system folder, etc. Are there image files in there?
Click to expand...
Click to collapse
Sorry for the late reply.
I just got the device back from the service center.
I inquired about where I can get the firmware file, and the guy said ASUS's website, but to flash it I need a tool.
It seems that this tool then copies the entire system folder to the device.
Anyways, the problem is solved now. Thank you very much for your help.
Glad you got it fixed. I'll close this thread.

Categories

Resources