Related
im unable to make a ftf file with flashtool. i unzip the file. then search it, select it in source folder. The flashtool never opens the file and subfiles. It never displays in the left column. Ive started with a zip file, then unziped it. Ive also tried winRAR to extract the files. Im using 2.9.1 Java 1.6.0_24 os 6.1
Any help or tips would be appreciated
Hey, you must sure that in the zip file just one file .ftf, if so, extract it. If there are 4 files like system, data ... you must rename the .zip file to .ftf
silveraero said:
Hey, you must sure that in the zip file just one file .ftf, if so, extract it. If there are 4 files like system, data ... you must rename the .zip file to .ftf
Click to expand...
Click to collapse
i thught you where changing it from a zip to a ftf. Not just renaming it
xxloudogxx said:
im unable to make a ftf file with flashtool. i unzip the file. then search it, select it in source folder. The flashtool never opens the file and subfiles. It never displays in the left column. Ive started with a zip file, then unziped it. Ive also tried winRAR to extract the files. Im using 2.9.1 Java 1.6.0_24 os 6.1
Any help or tips would be appreciated
Click to expand...
Click to collapse
All the files you want to bundle need to be in one folder and look similar to this
http://dl.dropbox.com/u/27083072/XDA/files.JPG
Then open flashtool and find the folder when you get to teh folder the location shoold appear blank, click open and you will get this
http://dl.dropbox.com/u/27083072/XDA/bundle.JPG
copy them to teh right, fill in the top, Device, Version, Branding and click OK
this is the file i downloaded. its a wb zip file. so i unzip it. i have a ziped and a unziped file on my desk top. then i open flashtool in administer. advance> bundle creation>select source folder.
this is the file folder. unzipped
a screen shoot of the folder.
http://forum.xda-developers.com/attachment.php?attachmentid=692379&stc=1&d=1313629311
once i select the main folder in flashtool it dont open it in small folder like you posted above.
uncompressed screen shot of folder.
http://forum.xda-developers.com/attachment.php?attachmentid=692389&stc=1&d=1313629741
xxloudogxx said:
uncompressed screen shot of folder.
http://forum.xda-developers.com/attachment.php?attachmentid=692389&stc=1&d=1313629741
Click to expand...
Click to collapse
OK, what you have is wolfbreaks rom, this is installed on your phone via xrecovery not an ftf file, if you want to install it you need to install xrecovery on your phone first, then install this from there.
You need a rooted rom for this, so is your rom rooted and what version are you on 2.1 or 2.3
I have x recovery on my phone know. That's how I upgraded from 2.1 to 2.3, because my phone is sim unlocked. Super user is v2.3.6.1 I followed a thread on the upgrade. I can link which thread when I'm home.
Sent from my X10i using XDA App
I've tried installing via x recovery, by loading the zip file on my as card and loading it with xrecovery. But I don't see the file when I'm in xrecovery. Something I'm prob doing wrong
Sent from my X10i using XDA App
first i would like to say thank you for all your help and tips. this site is the sh!t!! it was a noob mistake. when i looked back in the files in xrecovery it was listed.but once i scrolled down, there is was. oh man!! i spent hrs looking up threads and videos to see if there was something i was missing. there it was. one page down. lol. so i was able to install the new wb 3.5
thank you!!
time to look at what the differences in 3.6
These are the steps explaining you how to create a custom firmware based on the SmartQ firmware releases.
Warning : Creating a firmware and changing the files may cause your device to stop working, I won't be held responsible for any damage caused by this.
Creating a firmware file is actually very easy, not much is involved and nothing more than some basic software is required to create the files. If you don't understand the steps below than maybe you shouldn't fiddle around with this and wait for other members to create these.
There is nothing explained here about the flashing itself, as I will create a seperate How-To about that with pictures explaining the steps of the recovery.
Also there is nothing explained about kernel building itself, I have no clue how to do that and I'll leave that up to SmartQ.
Use the instructions below to make your own Firmware file with the software you want in it and make all configuration changes you want.
1. If you haven't already download the latest official firmware from SmartQ.
2. Extract the zip file. You then have 2 files, a Chinese .txt file with the release notes. And a file called "SmartQT15".
3. Rename the file "SmartQT15" to "SmartQT15.zip". Accept any warning about making the file useless, as in fact you are making it useful.
4. Extract the zip file. Then you end up with 4 new folders :
"boot" - This will be the files required for booting the OS. And possibly the recovery.
"data" - The user apps and data are in this folder.
"META-INF" - The certificate SmartQ used is in this folder and also the update script that manages the update process.
"system" - The actual Android OS.Stay clear of the boot folder, unless you are 100% sure about what you are doing, this may cause a bricked device without the possibility to reflash.
Add apps to the app subfolder in the data folder. Make sure if you do add apps to set the permissions in the update script file and make changes accordingly. The data-extra.tar file is extracted during the update process.
In the "META-INF\com\google\android" folder you can find the updater-script file, you can edit this with Notepad++. This file tells the CWM based recovery what to do and in this file the permissions are set for apps. Also is it required to edit this if you want to create a pre-rooted firmware.
Be carefull what to change in the system folder it can cause your OS not to boot, but it should be no problem to revert back to another build that did work previously as you didn't touch the boot folder and the recovery should work normally.
Once you have made all the changes you wanted to do. You follow the steps back.
5. zip the 4 folders backup using Winzip or WinRAR, whatever suits you best (You can use compression, I tried out Fast, Normal, Good compression in WinRAR and the firmware flashed without problems). Make sure you have the 4 folders in the "root" of your zip file. Use for filename "SmartQT15.zip"
6. Rename the "SmartQT15.zip" file to "SmartQT15" and accept any warning again about changing the extension of your file.
You have now created a flashable firmware file for the SmartQ Ten3 T15.
Copy his file to the root of an empty microSD card and follow my How-To about flashing Custom Firmwares.
Don't use the guide to flash original SmartQ firmwares as this won't work, by changing the firmware package you break the firmware signature and the recovery will check for this during flashing.
Signature checking can be disabled though in the recovery as I will explain in the new How-To.
If you have any questions feel free to post below and I'll do my best to answer them, all the above is based on my experience and from what I could find out on the Internet.
Hi @all,
I´m using the Flashtool and other provided tools here in the Forum for a long time (thanks to all people who are involved in the developing)
Now I want to give something back.
I´m not a developer but I understand (hopefully) basic things.
I have also some phones which does not support the flashmode so I am reliant to the fastboot mode and CWM.
At this point my goal was to flash the stock ROM to the Xperia Z.
I found a tuturial how to make a flashable zip file for CWM but it was for old devices with yaffs2 filesystem and the new ones have ext4.
After some search I found everything what is needed and I want to share it with you.
The Tutorial covers basic things but maybe it will help some people who will try it.
Step 1
Download the Stock-FW you want (FTF-File)
Step 2
Rename the .ftf File to .zip
Step 3
Extract the system.sin (with 7zip or WinRar for example)
Step 4
Open Flashtool go to "Tools" -> "Sin Editor" -> Choose the extracted system.sin and push "extract" Data
Step 5
You will get an system.ext4 file
Step 6
We have to extract the files which are in the system.ext4 file - for this I used the DiskInternal Linux Reader
Step 7
After extracting the files you have to put all the files in a folder named "system" (low letters)
Step 8
Create a folder named for example "Firmware"
Step 9
Put the "system" folder in the "Firmware" folder
Step 10
Download the Attached META-INF File - extract it and copy the META-INF Folder in the "Firmware" folder
Step 11
Now you have in your "Firmware" folder two sub-folders
"system" and "META-INF"
Now you only have to zip the both folders for example with 7zip or WinRar
Important: You have to set the compression to "Store"
Step 12
Copy the zip File to your SD-Card and flash it with CWM
If you want you can now add files to the system folder - like busy box - and or modify things and flash it over CWM.
Special thanks to Bin4ry
Best regards
UserX10
Learned ! Thank you.
Nice tutorial!
EDIT: The flashable zip is huge (990MB), did this have anything to do with the compression being set to 'store'?
xL3thalTuRdZz said:
Nice tutorial!
EDIT: The flashable zip is huge (990MB), did this have anything to do with the compression being set to 'store'?
Click to expand...
Click to collapse
If you don't set it to store it wont work at all, no rom/flashable zip have anything other than store compression the same goes for bootanimations
Edit: OP/Mod you might just want to change TFT file to FTF in step 1
Sent from my GT-i9100 using Tapatalk 2
Edit2: It seems like this only goes for bootanimations, sorry my bad.
Great.....learning it now
Thanks for the positive feedback.
Changed also the typo on Step 1
I've tried setting compression to 'Normal' and all seems to be going fine...
Sent from my C6603 using xda app-developers app
Can this be applicable to nxt devices like mine?thanks for the tutorial...
Sent from my LT22i using Tapatalk 2
how to extract from ext4
can you explain with details :fingers-crossed:
im getting ext4 file again after extracting !
ShivangDave said:
can you explain with details :fingers-crossed:
im getting ext4 file again after extracting !
Click to expand...
Click to collapse
You have to selected the .ext4 file open with LinuxReader. (like you .doc file with Word)
LinuxReader will "mounted" it in his own window, open your "new" disk (2Go) then select the "Save" option above...
tempofestival said:
You have to selected the .ext4 file open with LinuxReader. (like you .doc file with Word)
LinuxReader will "mounted" it in his own window, open your "new" disk (2Go) then select the "Save" option above...
Click to expand...
Click to collapse
did it via linux ! thanks any way !
When I tried to extract Xperia S's stock rom from the ftf using DiskReaderInternals, then the rom would boot but USB would never work. Even the guy above me (ShivangDave) tried extracting using DiskReaderInternals for Miro but the rom failed to boot and got stuck at the Sony logo. That's why it is better to use linux to extract the system.ext4 image.
i want to make a flashable zip to install aps
UserX10 said:
Important: You have to set the compression to "Store"
Click to expand...
Click to collapse
How do I set the compression to "Store"?
Thanks a lot for your guide!
MinnesotaVikings1961 said:
How do I set the compression to "Store"?
Thanks a lot for your guide!
Click to expand...
Click to collapse
whenever you add file in archive it will show a box first ! 'NORMAL' is default ! change it to 'Store' !
Please!
Does this tutoriral can be applied to other models as Neo V.
Thank you and best regards!
fer14 said:
Please!
Does this tutoriral can be applied to other models as Neo V.
Thank you and best regards!
Click to expand...
Click to collapse
This Tutorial should also work with the Neo V. Only one thing could be different.
But depending on your Android Version (when I remember well) it could be possible that you have instead of an ext4 file a yaffs2 file. In this case you can search the forum for an how to for this extension.
TheHawk002 said:
If you don't set it to store it wont work at all, no rom/flashable zip have anything other than store compression the same goes for bootanimations
Click to expand...
Click to collapse
I use a template for flashing various things and I just drop stuff in it using Normal compression and it flashes ok, might be more important for full ROMs or zips to be run on the Phone like a boot animation, but for flashing the odd apk or other file I don't think it matters.
UserX10 said:
This Tutorial should also work with the Neo V. Only one thing could be different.
But depending on your Android Version (when I remember well) it could be possible that you have instead of an ext4 file a yaffs2 file. In this case you can search the forum for an how to for this extension.
Click to expand...
Click to collapse
XperienceD said:
[GUIDE] How to make your regional firmware an .FTF file
[Guide] How make a FTF of stock firmware from SUS files
[GUIDE]How to make a rooted flashable rom from ftf file[FOR ALL XPERIA PHONES]
[tutorial] | how to extract system.sin
[tutorial] step by step method to extract ftf file from ics [ics]
[Tool] Yaffey - Utility for reading, editing and writing YAFFS2 images
Click to expand...
Click to collapse
UserX10 said:
Hi @all,
I´m using the Flashtool and other provided tools here in the Forum for a long time (thanks to all people who are involved in the developing)
Now I want to give something back.
I´m not a developer but I understand (hopefully) basic things.
I have also some phones which does not support the flashmode so I am reliant to the fastboot mode and CWM.
At this point my goal was to flash the stock ROM to the Xperia Z.
I found a tuturial how to make a flashable zip file for CWM but it was for old devices with yaffs2 filesystem and the new ones have ext4.
After some search I found everything what is needed and I want to share it with you.
The Tutorial covers basic things but maybe it will help some people who will try it.
Step 1
Download the Stock-FW you want (FTF-File)
Step 2
Rename the .ftf File to .zip
Step 3
Extract the system.sin (with 7zip or WinRar for example)
Step 4
Open Flashtool go to "Tools" -> "Sin Editor" -> Choose the extracted system.sin and push "extract" Data
Step 5
You will get an system.ext4 file
Step 6
We have to extract the files which are in the system.ext4 file - for this I used the DiskInternal Linux Reader
Step 7
After extracting the files you have to put all the files in a folder named "system" (low letters)
Step 8
Create a folder named for example "Firmware"
Step 9
Put the "system" folder in the "Firmware" folder
Step 10
Download the Attached META-INF File - extract it and copy the META-INF Folder in the "Firmware" folder
Step 11
Now you have in your "Firmware" folder two sub-folders
"system" and "META-INF"
Now you only have to zip the both folders for example with 7zip or WinRar
Important: You have to set the compression to "Store"
Step 12
Copy the zip File to your SD-Card and flash it with CWM
If you want you can now add files to the system folder - like busy box - and or modify things and flash it over CWM.
Special thanks to Bin4ry
Best regards
UserX10
Click to expand...
Click to collapse
I tried this on Xperia SP but the installation is aborted, does this supports Xperia SP? If not, how can I make another one for Xperia SP? Thanks
tdth said:
I tried this on Xperia SP but the installation is aborted, does this supports Xperia SP? If not, how can I make another one for Xperia SP? Thanks
Click to expand...
Click to collapse
which error ?
---------- Post added at 08:52 PM ---------- Previous post was at 08:50 PM ----------
tdth said:
I tried this on Xperia SP but the installation is aborted, does this supports Xperia SP? If not, how can I make another one for Xperia SP? Thanks
Click to expand...
Click to collapse
this works... make sure you have correct update-binary file and also script !
Hello, I would like to know how I could extract backed up TWRP data on my computer? maybe because the data was large TWRP split it into two files : data.ext4.win000 and data.ext4.win001 (sizes 1.5 and 1.2 GB)
How I got there:
I've been using XenonHD rom for quite a while, and this rom uses koush's superuser app.
I noticed there was a newer version on the market so I installed it; however it appears the one used by the rom developer was modified and therefore had a different package name: I ended up with two superuser apps, one of them asking to update the binaries, which I did.
After that the phone got stuck and rebooted two or three times before being stuck indefinitely at 'updating app' message right after the bootanimation. I tried:
- to wipe dalvik cache but it was still stuck;
- I reflashed the rom + gapps but it was still stuck;
- then I went to the /data/app/ folder (via TWRP) and deleted the superuser app i installed from market, as well as the corresponding data in /data/data, wiped cache and dalvik again: still the same...
-the I decided to make a backup via TWRP : one of the whole system, and one of Data partition only;
- then I realised I couldn't transfer it to my computer in TWRP, so I finally made a factory reset, re-flashed the rom+gapps, and then (it worked) copied my backup to the computer
now; how can I retrieve the data of my apps only, as I guess it is the system data that is messed up?
Of course I tried to restore the Data backup in twrp and it got stuck again the same way....
any help greatly appreciated!
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
forvrknight said:
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
Click to expand...
Click to collapse
It actually helped me, thanks a lot!
Two Questions
asim0 said:
On this file I used AccessData FTK Imager,
Click to expand...
Click to collapse
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
asim0 said:
All you have to do now is to merge the two data folders and voilà
Click to expand...
Click to collapse
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
pi_yush said:
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
Click to expand...
Click to collapse
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
number_thirty_two said:
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
Click to expand...
Click to collapse
Thanks number_thirty_two, I copyed thes to a folder I named untar in my home folder of CYGWIN, and extracted my system files perfectly
C:\cygwin\home\carl\untar\
system.ext4.win000
system.ext4.win001
tar xvfz system.ext4.win000
tar xvfz system.ext4.win001
Apologies for resurrecting this, but does anyone know how to extract them if they were compressed as .comp files?
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voil
Click to expand...
Click to collapse
Switching to another regional firmware (change of locale)
http://4pda.ru/forum/index.php?showtopic=678766&st=980
my region channel/tr
converted region hw/eu
google translated txt (cust fail fix.txt)
What version you have installed ? B510?
Enviado do meu HUAWEI MT7-TL10 através de Tapatalk
paulopais said:
What version you have installed ? B510?
Enviado do meu HUAWEI MT7-TL10 através de Tapatalk
Click to expand...
Click to collapse
B324,good for now.
I Have now the Gold Mate 7 TL10 from the Philippines. Here in Germany don`t work this whit the LTE Band 20. Can i change this and need i root?
murat1369 said:
Switching to another regional firmware (change of locale)
http://4pda.ru/forum/index.php?showtopic=678766&st=980
my region channel/tr
converted region hw/eu
google translated txt (cust fail fix.txt)
Click to expand...
Click to collapse
does this file works for all firmwares?
please clarify
Brilliant, thanks so much for this, worked like a charm. This worked for me going from Chinese 5.1.1 firmware (TL7-MT10C00B357) to European 5.1.1 firmware (MT7-TL10C900B311).
Chinese firmware downloaded from:
http://forum.xda-developers.com/mate-7/general/official-lollipop-chinese-versions-mate-t3214997
European firmware downloaded from:
http://www.carbontesla.com/firmware-ota-section/huawei-firmware-ota-collection/huawei-ascend-mate-7-firmware-ota/
speedojames said:
Brilliant, thanks so much for this, worked like a charm. This worked for me going from Chinese 5.1.1 firmware (TL7-MT10C00B357) to European 5.1.1 firmware (MT7-TL10C900B311).
Chinese firmware downloaded from:
http://forum.xda-developers.com/mate-7/general/official-lollipop-chinese-versions-mate-t3214997
European firmware downloaded from:
http://www.carbontesla.com/firmware-ota-section/huawei-firmware-ota-collection/huawei-ascend-mate-7-firmware-ota/
Click to expand...
Click to collapse
Hi Speedo.
I tried it myself, and I changed the oeminfo with no problems.
however i did not understand the instructions besides that.
could you post a little set of instructions?
PS: I made a tool to make changing oeminfo easier, it's in my other thread.
xd4d3v said:
Hi Speedo.
I tried it myself, and I changed the oeminfo with no problems.
however i did not understand the instructions besides that.
could you post a little set of instructions?
PS: I made a tool to make changing oeminfo easier, it's in my other thread.
Click to expand...
Click to collapse
I'll try and summarise as best I can below by amending the original text below. As I said this worked for me going from the Chinese to European firmware versions I quoted above.
1. Open ES File Explorer (enabling root access by selecting Root Explorer)
2. Navigate to the folder ../dev/block/platform/hi-mci.0/by-name/
3. Copy the file "oeminfo" from this folder to your internal memory and rename it oeminfo.bak
4. Make a copy of this file (again onto your internal memory) and rename it oeminfo.img
5. Download oeminfo.rar onto your computer and extract the archive onto your harddrive
6. Copy the file oeminfo.img from your internal memory into the folder where the archive was extracted above
7. Run the file oeminfo.exe from the archive folder, in the dialogue box that opens change the text
8. To go from Chinese to EU change from "cmmcchannel/cn" to "hw/eu"
9. Exit the program and copy the file oeminfo.img from the archive folder back to the internal memory replacing the file that is there.
10. Rename the file in the internal memory from "oeminfo.img" to "oeminfo"
11. Copy this file (oeminfo) from the internal memory back to the folder ../dev/block/platform/hi-mci.0/by-name/ replacing the existing file
12. Using ES File Explorer, long tap on the file, select properties and then change the permissions to read and write for the owner only. This means if the file if viewed in detailed mode the permissions will look like "-rw-------"
13. Open the folder ../data and then open the file custom.bin with a text editor (if the file is not there then create it, the file was there for me). Edit the file so it is a single line of text with the local you want to go to (so me I changed the text in the file to read "hw/eu") and save the edit
14. Using ES File Explorer, long tap on the edited file, select properties and then change the permissions to read and write for the owner only. This means if the file if viewed in detailed mode the permissions will look like "-rw-------"
15. Open the folder ../system/ then open the file build.prop (with a text editor) and find the line ro.build.display.id = ??? (this was quite a long way down the file for me). Replace the text after the equals sign (where I have put the question marks) with the text from the first line of the file verlist.img (where this is extracted from the firmware you want to transfer to reading verlist.img with a text editor).
16. Copy the file UPDATE.APP from the firmware you are transferring to a folder called "dload" in the base directory of either your sdcard or internal memory.
17. Remove the SuperSu root using the option "Full unroot" from within the Setting tab of the SuperSu app
18. If you have a custom recovery installed, flash back to the stock recovery using fastboot
19. Shutdown the phone, disconnect any cables and restart it by holding down the power, volume up and volume down buttons. This should boot into the stock recovery and start the installed of the firmware placed on either the sdcard or the internal memory noting this will delete all data in the internal memory
speedojames said:
I'll try and summarise as best I can below by amending the original text below. As I said this worked for me going from the Chinese to European firmware versions I quoted above.
Click to expand...
Click to collapse
Thanks James.
you switched to the same model firmware?
meaning TL10 ch to TL10 eu?
Yes, straight swap, with the version numbers as quoted above.
xd4d3v said:
PS: I made a tool to make changing oeminfo easier, it's in my other thread.
Click to expand...
Click to collapse
Which thread would that be, mate? I can't find it anywhere.
speedojames said:
I'll try and summarise as best I can below by amending the original text below. As I said this worked for me going from the Chinese to European firmware versions I quoted above.
1. Open ES File Explorer (enabling root access by selecting Root Explorer)
2. Navigate to the folder ../dev/block/platform/hi-mci.0/by-name/
3. Copy the file "oeminfo" from this folder to your internal memory and rename it oeminfo.bak
4. Make a copy of this file (again onto your internal memory) and rename it oeminfo.img
5. Download oeminfo.rar onto your computer and extract the archive onto your harddrive
6. Copy the file oeminfo.img from your internal memory into the folder where the archive was extracted above
7. Run the file oeminfo.exe from the archive folder, in the dialogue box that opens change the text
8. To go from Chinese to EU change from "cmmcchannel/cn" to "hw/eu"
9. Exit the program and copy the file oeminfo.img from the archive folder back to the internal memory replacing the file that is there.
10. Rename the file in the internal memory from "oeminfo.img" to "oeminfo"
11. Copy this file (oeminfo) from the internal memory back to the folder ../dev/block/platform/hi-mci.0/by-name/ replacing the existing file
12. Using ES File Explorer, long tap on the file, select properties and then change the permissions to read and write for the owner only. This means if the file if viewed in detailed mode the permissions will look like "-rw-------"
13. Open the folder ../data and then open the file custom.bin with a text editor (if the file is not there then create it, the file was there for me). Edit the file so it is a single line of text with the local you want to go to (so me I changed the text in the file to read "hw/eu") and save the edit
14. Using ES File Explorer, long tap on the edited file, select properties and then change the permissions to read and write for the owner only. This means if the file if viewed in detailed mode the permissions will look like "-rw-------"
15. Open the folder ../system/ then open the file build.prop (with a text editor) and find the line ro.build.display.id = ??? (this was quite a long way down the file for me). Replace the text after the equals sign (where I have put the question marks) with the text from the first line of the file verlist.img (where this is extracted from the firmware you want to transfer to reading verlist.img with a text editor).
16. Copy the file UPDATE.APP from the firmware you are transferring to a folder called "dload" in the base directory of either your sdcard or internal memory.
17. Remove the SuperSu root using the option "Full unroot" from within the Setting tab of the SuperSu app
18. If you have a custom recovery installed, flash back to the stock recovery using fastboot
19. Shutdown the phone, disconnect any cables and restart it by holding down the power, volume up and volume down buttons. This should boot into the stock recovery and start the installed of the firmware placed on either the sdcard or the internal memory noting this will delete all data in the internal memory
Click to expand...
Click to collapse
Thanks a lot speedojames for this very informative post. I followed your instructions and got this working in no time. The only difference was that I did not set the permission on oeminfo file, as ES File Explorer continued to give error on that. Rest was a breeze. Thanks again.