while stationed in japan bought a asus tf300t since being stateside ive found that apps wont download and compatibility ,performance issues is there any way to change JP sku to a US or other looked for hours and cant find answer i could make sense of
I think Asus states this is not possible. But obviously we don't mind if someone really wants to test this Make sure your tablet is on the latest version for your SKU. Then simply flash a different SKU using fastboot. Fastboot is a command-line utility. So download the WW SKU, unzip it, and unzip the zip you have unzipped. That gives you a file named "blob". Try flashing that with:
Code:
fastboot -i 0x0b05 flash system blob
Not sure that works without having your bootloader unlocked, so you may have to do that first.
so would there be a better way to use restricted apps and tweak functionality like rooting a cell phone
Related
All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 30. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
data90 said:
All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 26. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
Click to expand...
Click to collapse
Before you update to the latest firmware, I would recommend that you use NVFlash as a backup for recovering if you brick your device. You can find the information here: http://forum.xda-developers.com/showthread.php?t=1901479
If you update the latest Asus firmware, V10.6.1.14.8, it will also update your bootloader with the latest version. Good luck.
Thank you for the idea of NVFlash but unfortunately I have one too many updates to utilize that wonderful software. If I was able to use it, then I would have dove in head first and then informed the populace of my findings. So lets see if I give my self a ~$450 paper weight.
data90 said:
All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 30. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
Click to expand...
Click to collapse
You are correct. The Asus firmware has the correct bootloader, recovery and rom. If you flash it from TWRP it will install the stock recovery. So you loose TWRP and root too. You're basically back to a stock system, except you're unlocked.
berndblb said:
You are correct. The Asus firmware has the correct bootloader, recovery and rom. If you flash it from TWRP it will install the stock recovery. So you loose TWRP and root too. You're basically back to a stock system, except you're unlocked.
Click to expand...
Click to collapse
When I went to flash the firmware from twrp it kept failing. (and i accidentally wiped the os from the device) So I flashed ics back onto it and then tried upgrading again from the stock recovery, but i kept getting the dead android. I also got the device to recognize that there was an update zip on the device so that it would send it into an updating state by itself, but that also produced the android with the caution sign.
Any ideas?
data90 said:
When I went to flash the firmware from twrp it kept failing. (and i accidentally wiped the os from the device) So I flashed ics back onto it and then tried upgrading again from the stock recovery, but i kept getting the dead android. I also got the device to recognize that there was an update zip on the device so that it would send it into an updating state by itself, but that also produced the android with the caution sign.
Any ideas?
Click to expand...
Click to collapse
There are a lot things that could be wrong. However, most likely are: 1. A wrong signed firmware, for example you have a US bootloader but you try to update with WW firmware. 2. You have a currupted zip file. 3. You forgot to unzip it once because there is a zip inside the other zip file. If non of the above are applied to you, you could try this.
1. Copy a second zip file to your Root directory on your Internal SD
2. Reboot your device
3. After rebooted, you should see the notification on your lower right corner with the new update
4. Just click on the updated notification and follow the instructions as it walk you through the updated precesses.
Please report back. If it does not work, you need to rename your second zip file and use the stock recovery to update the firmware. There is a link some where on this website will walk you through the processes. Good luck.
LetMeKnow said:
There are a lot things that could be wrong. However, most likely are: 1. A wrong signed firmware, for example you have a US bootloader but you try to update with WW firmware. 2. You have a currupted zip file. 3. You forgot to unzip it once because there is a zip inside the other zip file. If non of the above are applied to you, you could try this.
1. Copy a second zip file to your Root directory on your Internal SD
2. Reboot your device
3. After rebooted, you should see the notification on your lower right corner with the new update
4. Just click on the updated notification and follow the instructions as it walk you through the updated precesses.
Please report back. If it does not work, you need to rename your second zip file and use the stock recovery to update the firmware. There is a link some where on this website will walk you through the processes. Good luck.
Click to expand...
Click to collapse
I second LetMeKnow.
Download the firmware again unzip it once and put it into the root of your microSD card. The card should be formatted as FAT32.
If the recovery does not automatically recognize it, rename the file to EP201_768_SDUPDATE.zip.
As far as I can see you are on the .30 ICS so nvflash won't work for you.
Hello @ll,
I bought a TF700-Tablet a few days ago.
Before I read something about NVFlash and this should not be working with my BL (9.4.5.30).
But what excactly are the disadvantages with that BL?
As I understood, with NVFlash I can make a complete backup from that tablet und can restore it, if it would brick.
But all other functions are possible? Own recovery system (TWRP) and custom rom?
And how often could the tablet be bricked?
Thanks for some infos and best regards,
Shadow128
If the bootloader is unlocked (any version), you can install custom recoveries and custom ROMs/kernels. If it isn't unlocked, you need to run the unlock tool from the Asus support page.
NVFlash can be used only if you created blob files for the wheelie tool before. The procedure for creating those blobs originally worked only with bootloaders 9.4.5.26 and earlier, but the developers found a new way around the bootloader signature checking and released the Flatline tool (search for it in the dev section), which can create those blobs with any bootloader version. So you can run the Flatline procedure whenever you're ready (be sure to read the instructions thoroughly and don't do anything if you're not sure), and you can upgrade to the latest bootloader (10.6.1.14.10) and run any custom ROM you want.
And the blob files I need to restore the tablet, if it is bricked?
Or is there any other stuff, on which I need that blob files?
Shadow128 said:
And the blob files I need to restore the tablet, if it is bricked?
Or is there any other stuff, on which I need that blob files?
Click to expand...
Click to collapse
You need them only whenever you want to use nvflash - for backing up some of the raw partitions, and for restoring from a hard brick.
Ah ok. That sounds great with the flatline tool.
Many thanks for your explanation!
So here I am worrying about bricking my device if I go back to stock.
Here is some insight-
I have an unlocked XT1032 US retail moto g running Cyanogenmod 11 m4 snapshot. I am also running clockworkmod recovery and everything is working fine. I have heard of many people bricking their devices when they try and flash stock because the version doesnt match up with the bootloader version or something like that. My bootloader version is reported to be 4111.5 (The bootloader menu version is 41.11) from the "fastboot getvar all". So if I want to flash stock firmware what version do I need to choose. (can someone give me a link to the download?) Also is there any easier way to do this, perhaps can someone give me a clockworkmod backup of stock firmware and i can flash it via restore in the recovery. Also is there a way to get .img files of my whole phone via the dd command on the superuser shell. (Someone please give me a list of those commands to make a full image of my phone) so I can restore incase something goes wrong.
So pretty much all in all can someone please give me a link to the correct stock firmware for my phone that I can flash with NO issues and a list of commands that I can use to flash.
And just wondering what is mfastboot and how is it different from fastboot.
I should have made a backup with cwm recovery before I installed cm11 but I forgot which is why I made this thread. ALL HELP IS APPRECIATED! THANKS!
hey try downloading stock firmware from this link http://sbf.droid-developers.org/download.php?device=14&file=786
then follow instruction from this thread http://forum.xda-developers.com/showthread.php?t=2542219
if you failed once don't panic... just try another firmware from here http://sbf.droid-developers.org/phone.php?device=14
just make sure you choose firmware which is for retail US and also choose right version of android... but first try the firmware i have mentioned above...
skyguy126 said:
So here I am worrying about bricking my device if I go back to stock.
Here is some insight-
I have an unlocked XT1032 US retail moto g running Cyanogenmod 11 m4 snapshot. I am also running clockworkmod recovery and everything is working fine. I have heard of many people bricking their devices when they try and flash stock because the version doesnt match up with the bootloader version or something like that. My bootloader version is reported to be 4111.5 (The bootloader menu version is 41.11) from the "fastboot getvar all". So if I want to flash stock firmware what version do I need to choose. (can someone give me a link to the download?) Also is there any easier way to do this, perhaps can someone give me a clockworkmod backup of stock firmware and i can flash it via restore in the recovery. Also is there a way to get .img files of my whole phone via the dd command on the superuser shell. (Someone please give me a list of those commands to make a full image of my phone) so I can restore incase something goes wrong.
So pretty much all in all can someone please give me a link to the correct stock firmware for my phone that I can flash with NO issues and a list of commands that I can use to flash.
And just wondering what is mfastboot and how is it different from fastboot.
I should have made a backup with cwm recovery before I installed cm11 but I forgot which is why I made this thread. ALL HELP IS APPRECIATED! THANKS!
Click to expand...
Click to collapse
XdroidBD said:
hey try downloading stock firmware from this link http://sbf.droid-developers.org/download.php?device=14&file=786
then follow instruction from this thread http://forum.xda-developers.com/showthread.php?t=2542219
if you failed once don't panic... just try another firmware from here http://sbf.droid-developers.org/phone.php?device=14
just make sure you choose firmware which is for retail US and also choose right version of android... but first try the firmware i have mentioned above...
Click to expand...
Click to collapse
Yes what this guy says will work
Almost hard bricked my phone
Tomsgt said:
Yes what this guy says will work
Click to expand...
Click to collapse
during flash gpt.bin it said preflash valadition failed and on the bootloader screen it said partition table downgraded. Used CWM backup to restore and my phone is functioning again but I am still not stock. Please tell me what I am doing wrong? I have attached a screenshot of the command prompt screen.
Q30: i encounter '(bootloader) Preflash validation failed' error message when flashing Firmware Image
You may have updated to Android 4.4.4 via firmware image or OTA update. In this case you now also have the latest version of the Bootloader. That is why you get the above output when attempting to flash a 4.4.2 firmware image. ==> simply flash 4.4.4 images instead.
If the error still occurs, even with a 4.4.4 firmware image, then unlocking bootloader will be necessary.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2537119
There is no 4.4.4 Retail US yet. You can flash 4.4.4 Retail EU just fine. Recovery flashable zip here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
I have the retail us version though. She. Will the retail us 4.4.4 be available? And one important question when I do go back to stock 4.4.4 with the link you gave me via recovery, will my custom recovery get overwritten with the stock one?
XT1032 is a Global GSM model. you can flash an XT1032 ROM from anywhere in the world and it will work.
It's currently unknown when 4.4.4 US Retail will be available, but I do not think it will take too much longer.
Those zip files only include ROM and Kernel. Recovery will not be changed.
I'll be trying that tomorrow and I'll let you know if it works or not asap. But for now thanks!
You might also need to flash the 4.4.4 EU Retail radio zip available here:
http://forum.xda-developers.com/showthread.php?t=2649763
I read somewhere that when you flash stock ROM even though the recovery is not being changed, the stock ROM will overwrite the custom recovery in start up.
Is this true?
skyguy126 said:
I read somewhere that when you flash stock ROM even though the recovery is not being changed, the stock ROM will overwrite the custom recovery in start up.
Is this true?
Click to expand...
Click to collapse
Please help my phone is stuck in CWM recovery during the flash and I think the recovery is frozen. Can I hard reboot back to recovery or is my phone totaled? :crying:
This worked for me - http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.
Back at stock, just had to give CWM 10mins! Thanks everyone!
I have to upgrade my bootloader but need some advice on which version to install to upgrade.
I bought my tablet in the UK, and it was originally WW. After bricking it with a bad flash I replaced the mainboard today with a US board and on boot I found my bootloader was JOP40D.US_epad-10.6.1.15.3-20130416
I unlocked, flashed nvflash, then TWRP 2.8, KatKISS KK ROM and GApps. I'm having problems with KatKISS (neither external SD card works/mounts - same problem I had before the brick - I should have learned to stay away) so I want to leave it behind and flash the stock bootloader before moving on to another KK ROM.
The problem is that now when I boot into fastboot my bootloader is listed as WW_epad-10.6.1.15.3-20130416
How did that happen? I haven't changed my bootloader, and now I don't know whether to flash WW or US.
I really can't brick again so any advice is desperately needed.
Thanks
be4con said:
I have to upgrade my bootloader but need some advice on which version to install to upgrade.
I bought my tablet in the UK, and it was originally WW. After bricking it with a bad flash I replaced the mainboard today with a US board and on boot I found my bootloader was JOP40D.US_epad-10.6.1.15.3-20130416
I unlocked, flashed nvflash, then TWRP 2.8, KatKISS KK ROM and GApps. I'm having problems with KatKISS (neither external SD card works/mounts - same problem I had before the brick - I should have learned to stay away) so I want to leave it behind and flash the stock bootloader before moving on to another KK ROM.
The problem is that now when I boot into fastboot my bootloader is listed as WW_epad-10.6.1.15.3-20130416
How did that happen? I haven't changed my bootloader, and now I don't know whether to flash WW or US.
I really can't brick again so any advice is desperately needed.
Thanks
Click to expand...
Click to collapse
I've just re-flashed the nandroid I made before installing KatKISS and I'm back on build number: JOP40D.US_epad-10.6.1.15.3-20130416 but the bootloader is listed as WW_epad-10.6.1.15.3-20130416 still.
I'm really not sure which way to jump now? It appears my tablet is both WW and US - can anyone help at all?
SOLVED
be4con said:
I've just re-flashed the nandroid I made before installing KatKISS and I'm back on build number: JOP40D.US_epad-10.6.1.15.3-20130416 but the bootloader is listed as WW_epad-10.6.1.15.3-20130416 still.
I'm really not sure which way to jump now? It appears my tablet is both WW and US - can anyone help at all?
Click to expand...
Click to collapse
OK, so the answer it seems is that whatever your mainboard is - that's the SKU you flash, regardless of what your bootloader version is. ASUS surpisingly were the source of that info, though they declined to help any further because I had modded my device.
I seem to be the only person interested in the answer to this problem, but I thought I'd update in case someone finds themselves in the same boat as me sometime down the line and comes here looking for an answer.
I have flashed the latest ASUS US SKU, and now flashed TWRP 2.8, and both my bootloader and build are now showing as US.
Hi,
I´m a neewbie to Samsung. My phone is a S6 SM-G920F, Baseband G920FXXU1AOCW
I came form an HTC and I´ve seen that flashing things are very different. So here are my questions:
1. I think, my bootloader is unlocked but I didin´t know for sure. So how can I check this?
(My HTV showed me this by using fastboot, didn´t know if there is fastboot with Samsung and how to start it - only know the download-mode and how to enter TWRP recovery)
2. Flashing firmware via Odin (i. e. from sammobile.com) means to loose my root again, right?
3. If I loose root, where do I get custom Firmwares and how do I flash them (if this is possible)?
4. If not, is it enough to flash bootloader and modem through Odin?
All answers are appreciated. Thanks in advanced.
Maybe someone can link me to an step to step instruction...
Fastboot is android doesn't matter who makes the phone.
If you flash a rom from sammobile then you will go to whichever stock you pick.
Other ROMs are available here. The phone is new. There aren't many yet. Cyanogen mod isn't available yet.
Root is available by flashing cfautoroot with Odin. You will need to get the specific one.
You can replace the recovery by flashing twrp team win recovery project with Odin.
You can flash boot loader and modem. Make sure you get the right region. The modem frequencies are different in different places.
You may find flashing a whole ROM even stock will fail. This is because the partitions are not the same size for all s6 stock ROMs. Don't ask me why. You can open the tar find which file stopped the flash delete it from the tar and flash again.
quatzar said:
Fastboot is android doesn't matter who makes the phone.
If you flash a rom from sammobile then you will go to whichever stock you pick.
Other ROMs are available here. The phone is new. There aren't many yet. Cyanogen mod isn't available yet.
Root is available by flashing cfautoroot with Odin. You will need to get the specific one.
You can replace the recovery by flashing twrp team win recovery project with Odin.
You can flash boot loader and modem. Make sure you get the right region. The modem frequencies are different in different places.
You may find flashing a whole ROM even stock will fail. This is because the partitions are not the same size for all s6 stock ROMs. Don't ask me why. You can open the tar find which file stopped the flash delete it from the tar and flash again.
Click to expand...
Click to collapse
Thanks for answering. My questions had an other intention, I think.
My S6 is already rooted and I have a custom recovery (TWRP) :good:
I would like to know if you have to flash a whole firmware or only bootloader/modem? Because I didn´t seen a post here for a full firmware yet.
I am not familiar with the differences between htc whole firmware and samsung bootloader/modem
Actually I am on Firmware G920FXXU1AOCW. But there are newer ones like XXU1AOE3 or XXU1AOE4.
In the days of my htc you couldn´t flash only bootloader or modem, you had to flash a whole firmware (like radio, drivers, bootloader, modem etc.)
Flashing only modem and bootloader will it update i. e. touchscreen drivers? If not, where do I get this ones? You know, because of root I don´t get OTA´s anymore...
The modem just controls how your phone hardware connects to carrier towers etc.
The boot loader is a tiny thing that tells the processor where and how to load the OS.
The software for pretty much everything is in /system.
Many of these releases are the same software, region specific. The dates are fairly unimportant for the same version number. They generally reference the time when they were uploaded by someone. Not that they have updates and fixes.
Just wanted to know can I change my phone logo MetroPCS to say T-mobile with all the T-mobile add on. I have a Samsung Galaxy s6 by MetroPCS