So whats with /system/etc/EC and its FU.cfg files.. and corresponding fu binary (in /system/bin I presume). It stands for firmware update, and there is a rom file that probably can be flashed (DONT!). Why is this in here? is this for flashing the wifi bios? Have any asus updates utilized this tool?
I believe its used for flashing the dock firmware.
its the dock firmware
Ahh.. so the dock actually has a bios by insyde software - wonder which one.. Thanks for the info.. both of you!
Related
hey guys....well i downgraded my nexus s 9020T for 4.0.3 to 2.3.6...however but while switching it on the 2.3.6..im getting a lock symbol while switching it on..and when i insert my sim onto the phone ..it is recognising the network but not catching the signal
kindly help me out
The lock symbol at the bottom means your bootloader is unlocked. This means you can replace your recovery partition to CWM or the likes, as well as flash superuser to the OS and flash custom ROMs. You would have achieved this through the "fastboot oem unlock" command.
The signal issue may be related to a bad flash. I would be going into recovery, doing a factory/data reset, formatting /system and /boot, and then flash the 2.3.6 file you have again. Remembering of course to backup anything currently on the phone, and doing a NANDROID backup if you don't have a working one already.
thank so much for the information...after doing this..can my phone still OTA official updates from google once they are released??
roshan567 said:
thank so much for the information...after doing this..can my phone still OTA official updates from google once they are released??
Click to expand...
Click to collapse
As long as you flash a official update
Sent from my ice cream powered Nexus S
a friend of mine is doing the flashing...any idea as to how can i know whether he has flashed an official update or not?
also what is the different between flashable roms n the increamental updates given in this link??
http://forum.xda-developers.com/showthread.php?t=1063664
are both official versions given out by google?
Yes, all of the links in that thread are official Google builds. The full/flashable ROMs are the full operating system in one file. You can install this over any Android version/ROM since the zip will contain all of the files necessary to get the system working.
The incremental updates should only be used if you have a specific (official) Android version and wish to only install the updated files. For example, if you have the official Google release of 2.3.6 and wish to upgrade to 4.0.3, you can use the 2.3.6 -> 4.0.3 incremental update. Otherwise, if don't have one of the supported incremental update versions or if you're using a non-stock ROM then you'll need to download the full ROM.
thank you so much for the information....
i am downgrading my OS to 2.3.6 from 4.0.3..how can i find out whether the 2.3.6 OS ive installed is the original OS???
You can find out BEFORE flashing the rom by comparing checksums, the zip file should have the exact same checksum as indicated in the filename of the files in that thread. Also, that thread just links to files from googles servers used for official updates.
Once it's installed there is no point trying to finding out if it is 100% stock.
Harbb said:
You can find out BEFORE flashing the rom by comparing checksums, the zip file should have the exact same checksum as indicated in the filename of the files in that thread. Also, that thread just links to files from googles servers used for official updates.
Once it's installed there is no point trying to finding out if it is 100% stock.
Click to expand...
Click to collapse
thanks for the information...i didn understand properly how do u do checksums..can you pls explain it??im a noob..
Checksum (or hash) is a way to verify a file. It will create a word/number/pattern/etc according to an algorithm based on all the data in the file. With MD5, SHA1, etc we have a practically guaranteed chance of comparing the two files. Those files there are straight from google and google has provided the checksums in the filename (part of the checksum, at least). If you have any file at all and it has the same code as that, we can be happy that it's the exact same file - thus 100% stock
You can use software such as Checksum or my personal favourite HashTab to find the various comparing techniques.
hey thanks a lot for your information..it really helps....
when i upgraded to ICS my phone stopped receiving reception after 2 days..when i downgraded it after unlocking the bootloader it still wasnt receiving recepetion...why does this happen?
Hi
So i have question about firmware changing.
It's possible to move from TW 9.2.2.3 firmware to WW 9.2.2.3 wf.?
Did somebody operation like that? It's save or not?
I don't have root and CWM recovery because this things isn't possible for now on latest ICS firmware, so only one possibility i flash update.zip by stock recovery.
So it's save or not and maybe some advice?
Thank you
I think it's possible with nvflash and I did it with the staging partition once, although I didn't test it extensively - maybe 5 mins to see if it worked. I didn't test if wifi worked or if it crashed every 10 mins.
The Belgium (TB) version of the 91117 rom is being switched to WW, so you might want to pull that apart and see if there is any fancy magic going on in there. There are instructions on the ASUS site.
If you only have stock recovery, it might be tough because of firmware checks to prevent you from doing exactly what you are suggesting. Again, the TB rom might offer some insight.
gee one said:
I think it's possible with nvflash and I did it with the staging partition once, although I didn't test it extensively - maybe 5 mins to see if it worked. I didn't test if wifi worked or if it crashed every 10 mins.
The Belgium (TB) version of the 91117 rom is being switched to WW, so you might want to pull that apart and see if there is any fancy magic going on in there. There are instructions on the ASUS site.
If you only have stock recovery, it might be tough because of firmware checks to prevent you from doing exactly what you are suggesting. Again, the TB rom might offer some insight.
Click to expand...
Click to collapse
Thanks!
I'm above B70, so nvflash will not work...:-\
I saw this TB version switched to WW on Asus site for 9.2.2.3 also, but I'm afraid it will not work with TW because of firmware checks...
So I need to wait for root possibility and CWM recovery?
Hey Guys,
I would like to change my SKU. I've found this thread and used the method mentioned there, but it doesn't work for me. I got a VF SKU and would like to change to WW on my TF300TG.
At the moment i've got Android 4.1.1, so I downloaded WW_epad-10_6_2_8-UpdateLauncher from asus.com. I know it's not the latest firmware, but I would like to try the OTA update after flashing the firmware. (just to see whether it works or whether the Firmware Updates are Mac-bound)
So I downloaded the file, unzipped WW_epad-user-10.6.2.8 and renamed it into EP101_SDUPDATE. Then I put it onto the root of my microSD and went into recovery mode, but there nothing happens. When I choose RCK, I only see that green Android thing with a red !. What did I wrong? Any suggestions?
Thanks for your help.
Best regards
MyHTCFlyerProblems said:
Hey Guys,
I would like to change my SKU. I've found this thread and used the method mentioned there, but it doesn't work for me. I got a VF SKU and would like to change to WW on my TF300TG.
At the moment i've got Android 4.1.1, so I downloaded WW_epad-10_6_2_8-UpdateLauncher from asus.com. I know it's not the latest firmware, but I would like to try the OTA update after flashing the firmware. (just to see whether it works or whether the Firmware Updates are Mac-bound)
So I downloaded the file, extracted WW_epad-user-10.6.2.8 and renamed it into EP101_SDUPDATE. Then I put it onto the root of my microSD and went into recovery mode, but there nothing happens. When I choose RCK, I only see that green Android thing with a red !. What did I wrong? Any suggestions?
Thanks for your help.
Best regards
Click to expand...
Click to collapse
I thought you had to name it:
Code:
EP201_768_SDUPDATE.zip
Don't forget to unzip the ROM from the first zip file.
Thank you, now it works like a charme! I didn't notice that EP101_SDUPDATE.zip is for the Transofmer Pad TF101 where the advice comes from. Thank you very much!
I've written a blog post that describes how to flash the RoW factory images on the Shield Tablet US version.
http://jaredmorgs.github.io/2015/01...-US-Version-into-a-Rest-of-World-Version.html
Everything flashes OK, but the one thing that's missing is the Modem files.
It seems that the Modem files are not included in the factory images, and one suggestion was to wait for an OTA to land then you would get them. But that doesn't seem to be the case when installing the 5.0 (OTA 2.0) factory images.
Does anyone know how to get access to the required modem files to flash through ADB to the device? Would I need to pull them from the very first factory image set? Would I need to pull them from a random OTA between 4.4.2 and 5.0.1?
And if so, has someone already extracted the modem files to a side-loadable zip?
It would be great to be able to change the LTE bands.
So if anyone has any solution for this...?
The blog post has an answer from someone who confirms that both modem firmwares are loaded on the device, however a check by the upgrade scripts determines whether the US or RoW modems are flashed.
As yet, I'm unable to confirm how to force the tablet to load the RoW firmware.
there is a thread currently looking at this:
http://forum.xda-developers.com/shi...eriment-flashing-ww-lte-firmware-lte-t2951111
it's probably better to focus efforts there
perky nerky said:
there is a thread currently looking at this:
http://forum.xda-developers.com/shi...eriment-flashing-ww-lte-firmware-lte-t2951111
it's probably better to focus efforts there
Click to expand...
Click to collapse
Correct. Please lock off thread.
Here is some firmware that I have acquired, will update the post when I get more.
Stock Firmware:
Coming Soon
Combination Firmware:
SM-F900U FA90
Combination firmware is only to be used to recover the device in case it is bricked or you have messed something up
Mine just in case
Newb question: what app do you use to just look in the ext4 files, without burning to a new partition?
sadly androidfilehost is damn slow for me.
deadman96385 said:
Here is some firmware that I have acquired, will update the post when I get more.
Stock Firmware:
Coming Soon
Combination Firmware:
SM-F900U FA90
Combination firmware is only to be used to recover the device in case it is bricked or you have messed something up
Click to expand...
Click to collapse
Hi deadman, could you also provide the "F" version of the FW? I canno't find it.
Thank you in advance
not_required said:
Newb question: what app do you use to just look in the ext4 files, without burning to a new partition?
Click to expand...
Click to collapse
7zip. Reads almost any FS image. (if its a sparse image when 7z fails to open you need to use simg2img first on it)
SM-G532G/DS
Scrap piece of information
Well, I don't have this phone but it is just a piece of scrap with zero new information.
Can it enable esim
Can flashing comb stock rom help enabling esim using imei calc
This is a great post. I like this topic. I found many interesting things from this site. Thanks for posting this again.