As the title states. I have been deep diving into my 1III modem files and have found (what I think) is a file that has something to do with what operators are allowed to use VOLTE and VOWIFI.
How ever try as I might, I can't open this file. It is not Microsoft Database File or if it is it's highly modified from its original form.
Just wondering if anyone out there new how to open it? I have attached the file (as a zip) so that maybe someone smarter than me can maybe work it out.
Cheers, Bentree.
How to Enable Volte and 5G Without Permanent Root on Xperia 5 III and 1 III
First of all, Thanks to @johndaniel, @htcmage, @gorEisberg @Forbesii @morphvale @arjun_m4 for sharing all the information and files required for this guide. FIRST THING FIRST: Data is priceless. Always backup before you modify your phone...
forum.xda-developers.com
shoaib130088 said:
How to Enable Volte and 5G Without Permanent Root on Xperia 5 III and 1 III
First of all, Thanks to @johndaniel, @htcmage, @gorEisberg @Forbesii @morphvale @arjun_m4 for sharing all the information and files required for this guide. FIRST THING FIRST: Data is priceless. Always backup before you modify your phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Unfortunately that doesn't work for me. The way Sony has locked down my device in my region is rather complicated. It's rather annoying.
bentree said:
Unfortunately that doesn't work for me. The way Sony has locked down my device in my region is rather complicated. It's rather annoying.
Click to expand...
Click to collapse
I have the same problem. I've tried all the guides, the only thing that worked for me was manually editing build.prop, that was an absolute nightmare to do and still haven't quite worked out how I managed to do that.
Only other option was to use magisk which I've reverted back to as the 30 volume steps has been great for me while in bed.
DrDrag0n said:
I have the same problem. I've tried all the guides, the only thing that worked for me was manually editing build.prop, that was an absolute nightmare to do and still haven't quite worked out how I managed to do that.
Only other option was to use magisk which I've reverted back to as the 30 volume steps has been great for me while in bed.
Click to expand...
Click to collapse
Yeah it's great when you have 30seconds spare and you are in a rush.
Another file worth looking at tho (and is loaded before all the other xml files) is "mcfg_sel_db.xml". I think it's what sets the limits for certain areas.
I have attached the one that is loaded for TW region firmware. Each region firmware has different xml file.
Cheers, Ben.
bentree said:
Yeah it's great when you have 30seconds spare and you are in a rush.
Another file worth looking at tho (and is loaded before all the other xml files) is "mcfg_sel_db.xml". I think it's what sets the limits for certain areas.
I have attached the one that is loaded for TW region firmware. Each region firmware has different xml file.
Cheers, Ben.
Click to expand...
Click to collapse
We might need to wait for TWRP to be fully compatible with A13 so we can manually edit build.prop from TWRP or ADB.
If we don't want to use magisk that is
The build.prop edits are what we're missing on our regional phones for VoLTE & VoWifi. The mbn files can only do so much, if it's not enabled in the build.prop then it's not possible to use
5g works fine with the mbn file though.
bentree said:
As the title states. I have been deep diving into my 1III modem files and have found (what I think) is a file that has something to do with what operators are allowed to use VOLTE and VOWIFI.
How ever try as I might, I can't open this file. It is not Microsoft Database File or if it is it's highly modified from its original form.
Just wondering if anyone out there new how to open it? I have attached the file (as a zip) so that maybe someone smarter than me can maybe work it out.
Cheers, Bentree.
Click to expand...
Click to collapse
Enable VoLTE/VoWiFi in unsupported countries without root (requires Shizuku)
Hi all, Bellow you can find some info on how to attempt to enable VoLTE in unsupported countries (tested in Romania, Digi carrier) using Shizuku and Pixel IMS app for it. This assumes that you have ADB and drivers properly setup beforehand. 1...
forum.xda-developers.com
works for sony
liwetlt said:
Enable VoLTE/VoWiFi in unsupported countries without root (requires Shizuku)
Hi all, Bellow you can find some info on how to attempt to enable VoLTE in unsupported countries (tested in Romania, Digi carrier) using Shizuku and Pixel IMS app for it. This assumes that you have ADB and drivers properly setup beforehand. 1...
forum.xda-developers.com
works for sony
Click to expand...
Click to collapse
Yeah no, it works for some operators but you need to still modify modem files with EFS tools and that all requires root access.
bentree said:
Yeah no, it works for some operators but you need to still modify modem files with EFS tools and that all requires root access.
Click to expand...
Click to collapse
Yes, it works if the profile of your operator matches the others that are already in the firmware.
liwetlt said:
Yes, it works if the profile of your operator matches the others that are already in the firmware.
Click to expand...
Click to collapse
Sort of but you still need to manually load the profile using efs tools first. That requires root access. Also even then it can still be blocked by sony firmware in other parts of the operating system.
bentree said:
Sort of but you still need to manually load the profile using efs tools first. That requires root access. Also even then it can still be blocked by sony firmware in other parts of the operating system.
Click to expand...
Click to collapse
Roots not too much of an issue seing as it's possible to remove with ease and relock the bootloader. It's unfortunate we can't change build.prop on A13 just yet. When the TWRP update comes out I'm sure the edits will make it work for you as they have me
I think mcc2countryoperator.mdb is not the key one, here is the diff between XQ72 and NTT SO-51B:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cscomic said:
I think mcc2countryoperator.mdb is not the key one, here is the diff between XQ72 and NTT SO-51B:
View attachment 5907033
Click to expand...
Click to collapse
Indeed you could be right but it would definitely be nice to know what it says....
bentree said:
Indeed you could be right but it would definitely be nice to know what it says....
Click to expand...
Click to collapse
mcc2countryoperator.mdb in path /mdb/mcfg/ are both the same, for both XQ-72 and SO-51B mcfg_hw.mbn
bentree said:
As the title states. I have been deep diving into my 1III modem files and have found (what I think) is a file that has something to do with what operators are allowed to use VOLTE and VOWIFI.
How ever try as I might, I can't open this file. It is not Microsoft Database File or if it is it's highly modified from its original form.
Just wondering if anyone out there new how to open it? I have attached the file (as a zip) so that maybe someone smarter than me can maybe work it out.
Cheers, Bentree.
Click to expand...
Click to collapse
I think we have no method to enable 5G for NTT Docomo version, except edit TA partition and persist with SETool2.
Till now, I flash my SO-51B to XQ-BC72 one partition by one partition through twrp.
It took no effect when I flashed modem, modemst1 and modemst2 and system and so on. But it lost signal after I flash persist.
So I guess, maybe NTT version is different from other, it will check someother information for somewhere, most probably is TA.
It means, even you make your phone to another version, you will lost your signal.
Related
Has anyone bought the HTC Desire VC and tried it on VZW?
Im almost positive that its the EXACT same thing as the HTC Droid Incredible 4G LTE, kinda like with the Inc2 and the s710d?
What do yall think?
http://www.htc.com/sea/smartphones/htc-desire-vc/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Desire VC spec sheet
It's not an exact match. The chipset is inferior to the Inc 4G's and the battery is a little smaller. Design and software wise, it's an identical match, though.
And the screen resolution is lower. Meh! It is more like a match for the Dinc2, except it seems even worse than the Dinc2! What???
Older CPU than Droid Incredible 2 (MSM7227A, Snapdragon S1 vs MSM8255 Snapdragon S2)
Lesser RAM (512 MB vs 768 MB)
Lower Res Camera (5 MP vs 8 MP)...
A 2010 phone sporting a 2011 OS in 2012... Thank you very much HTC, just what I want. No one can justify the existence of this phone. EVEN as a budget phone it is sub-par.
litetaker said:
A 2010 phone sporting a 2011 OS in 2012... Thank you very much HTC, just what I want. No one can justify the existence of this phone. EVEN as a budget phone it is sub-par.
Click to expand...
Click to collapse
I mean, it's intended for a totally different market, which makes a difference. The main feature of this phone is the CDMA/GSM dual-band capability. It isn't intended to be a flagship device, it's just intended to fill some gaps in the international market.
Looks more like a Thunderbolt to me.
Stuck on HTC logo screen (HTC desire VC T328d)
Hello.
My HTC desire VC is stuck on HTC logo screen just after a booting sound and showing "HTC quietly brilliant , Beatsaudio" .
Android can't start anymore.
My phone is already rooted under the instruction of root for htc desire vc
After rooting, I install the "font installer root" and I chose some system fonts to be replaced in this application.
As soon as after rebooting, the problem started.
I have downloaded the kernel from htcdev.com but I don't know what it is for and how to use it.
please reply me as soon as possible.
erizchen said:
Hello.
My HTC desire VC is stuck on HTC logo screen just after a booting sound and showing "HTC quietly brilliant , Beatsaudio" .
Android can't start anymore.
My phone is already rooted under the instruction of root for htc desire vc
After rooting, I install the "font installer root" and I chose some system fonts to be replaced in this application.
As soon as after rebooting, the problem started.
I have downloaded the kernel from htcdev.com but I don't know what it is for and how to use it.
please reply me as soon as possible.
Click to expand...
Click to collapse
You're in the wrong forum, although it appears you don't have a forum for your device on XDA.
The kernel isn't going to help you, you just need to push back your default fonts. If you knew how to use adb, that'd be really simple. If you don't know how, Google it. If there's even one available, download a ROM and pull the /system/fonts/ folder and push it through adb to your device. If all else fails, do a factory reset through HBOOT. You might lose everything, but at least your device will work.
IceDragon59 said:
You're in the wrong forum, although it appears you don't have a forum for your device on XDA.
The kernel isn't going to help you, you just need to push back your default fonts. If you knew how to use adb, that'd be really simple. If you don't know how, Google it. If there's even one available, download a ROM and pull the /system/fonts/ folder and push it through adb to your device. If all else fails, do a factory reset through HBOOT. You might lose everything, but at least your device will work.
Click to expand...
Click to collapse
Please help me again.
I was trying to set "mount storage" and I accidentally chose the format /system because they are all in chinese fonts and I can't read.
After translating, I know it was formatted ... How to do , sir ?
erizchen said:
Please help me again.
I was trying to set "mount storage" and I accidentally chose the format /system because they are all in chinese fonts and I can't read.
After translating, I know it was formatted ... How to do , sir ?
Click to expand...
Click to collapse
Find out if there is an ROM or RUU you can install on your device. You already lost all your settings if you formatted /system, so you might as well start over. Other than that, I don't know what to tell you.
IceDragon59 said:
Find out if there is an ROM or RUU you can install on your device. You already lost all your settings if you formatted /system, so you might as well start over. Other than that, I don't know what to tell you.
Click to expand...
Click to collapse
There is only Kernel available in htcdev.com . I've downloaded it.
My friend has the same handset with me. (HTC Desire VC) but his ph is not rooted .
Can I take some files from him ?
erizchen said:
There is only Kernel available in htcdev.com . I've downloaded it.
My friend has the same handset with me. (HTC Desire VC) but his ph is not rooted .
Can I take some files from him ?
Click to expand...
Click to collapse
Potentially, yes, you could. Use ADB on his device to pull /system, then push it to your device's /system. I don't know if this could cause problems, but it might let you boot and save any important data then do a factory reset if needed.
IceDragon59 said:
Potentially, yes, you could. Use ADB on his device to pull /system, then push it to your device's /system. I don't know if this could cause problems, but it might let you boot and save any important data then do a factory reset if needed.
Click to expand...
Click to collapse
I got it. thanks
I backup my friend's ROM and restore back to mine using CWM nandroid recovery.
But, after this, I can't switch on wifi and bluetooth. It shows error. What's wrong with that ?
erizchen said:
I got it. thanks
I backup my friend's ROM and restore back to mine using CWM nandroid recovery.
But, after this, I can't switch on wifi and bluetooth. It shows error. What's wrong with that ?
Click to expand...
Click to collapse
you need to flash the kernel with boot.img using adb
Aldo101t said:
you need to flash the kernel with boot.img using adb
Click to expand...
Click to collapse
I was suggested that there are some missing files in /system/lib/modules folder. I'm trying to get these files. Is it proper way ?
Because I don't know how to use adb and the steps will contain cmd.
I downloaded the kernel from htcdev.com. The file name is "primodd-ics-crc-3.0.16-ead8920.zip".
When I extract this, I got "primodd-ics-crc-3.0.16-ead8920.tar.gz". Which file do I have to flash ?
Do you mean I have to flash both kernel and boot.img at the same time ?
kernel is in boot.img
Sent from my ADR6410LVW using xda app-developers app
erizchen said:
I was suggested that there are some missing files in /system/lib/modules folder. I'm trying to get these files. Is it proper way ?
Because I don't know how to use adb and the steps will contain cmd.
I downloaded the kernel from htcdev.com. The file name is "primodd-ics-crc-3.0.16-ead8920.zip".
When I extract this, I got "primodd-ics-crc-3.0.16-ead8920.tar.gz". Which file do I have to flash ?
Do you mean I have to flash both kernel and boot.img at the same time ?
Click to expand...
Click to collapse
What you downloaded is the kernel source. This will allow you to build a kernel but is not an actual kernel.
After a kernel is built it is then merged with the ramdisk to make a boot.img. This is the file you will need to reflash the kernel on your device.
The system/lib/modules folder is the location of the needed .ko files for Bluetooth and WiFi to work correctly. If you have a device that has working Bluetooth and WiFi you can pull the files from there by doing adb pull /system/lib/modules. This will pull all of the files from that folder. Then on your device you can add them to the ROM you are flashing or you can push them using adb. The command for that is adb push filename /system/lib/modules.
My friend told me he has same files as mine in /system/lib/modules
These are the file list
bluetooth.ko
bnep.ko
btwilink.ko
cfg80211.ko
compat.ko
fm_drv.ko
hidp.ko
kineto_gan.ko
mac80211.ko
rfcomm.ko
wl12xx.ko
wl12xx_sdio.ko
He has only those files (not include "bcm4329.ko")
What should I do now ?
erizchen said:
My friend told me he has same files as mine in /system/lib/modules
These are the file list
bluetooth.ko
bnep.ko
btwilink.ko
cfg80211.ko
compat.ko
fm_drv.ko
hidp.ko
kineto_gan.ko
mac80211.ko
rfcomm.ko
wl12xx.ko
wl12xx_sdio.ko
He has only those files (not include "bcm4329.ko")
What should I do now ?
Click to expand...
Click to collapse
Did those files come with the kernel? If not then that may be why it isn't working. The bcm4329.ko is the WiFi module so if that isn't in your list then that is why it's not working (assuming your device uses that WiFi module).
blazingwolf said:
Did those files come with the kernel? If not then that may be why it isn't working. The bcm4329.ko is the WiFi module so if that isn't in your list then that is why it's not working (assuming your device uses that WiFi module).
Click to expand...
Click to collapse
I mean not like that.
The file list is exactly the same as my friend's phone which is identical to mine.
His phone can run wifi and bluetooth properly without bcm4329.ko file in /system/lib/modules.
But my phone cannot turn on wifi and bluetooth.
------------- updated --------------
I have successfully fixed the problem.
Because my HTC is S-On, boot.img didn't restore properly.
So, I flash boot.img with fastboot under the instruction of this post by Cyb0rgz
Need HTC Desire VC ROM
erizchen said:
I got it. thanks
I backup my friend's ROM and restore back to mine using CWM nandroid recovery.
But, after this, I can't switch on wifi and bluetooth. It shows error. What's wrong with that ?
Click to expand...
Click to collapse
hello Sir,
i have similar problem with my Desire VC and i cant find a copy anywhere to restore my phone. please can you upload a copy of ROM so i can use to restore my HTC. i will be very grateful as i have tried to get back to stock ROM with no success
Hey Xda developers,
I'm kinda frustrated at the moment so I'm sorry if I sound that way. I recently bought a Sony Xperia Z Ultra (for 2 months now). And yesterday I came to the conclusion that I had cracks in my screen. Not long after that I realised that my touchscreen was dead too. How did this all happen? I have no clue as to why but probably because I always put it in my pocket all day. It probably couldn't handle the forces while bending my leg when sitting while the thing is pretty big. (so my advice is don't put it in your pocket).
After that I thaught I'm so happy that I have an extra insurance on my phone. But my happiness was soon gone when I called the insurance company wich told me there was no record stating I had an insurance.
A lot of phonecalls later they said everything is gonna be allright and they will fix it (i told them I had evidence in my mail). So I decided to copy all my data from my broken Sony Xperia Z Ultra.
The Touchscreen is defective but it still powers on and android seems to be running fine. I had no problem with phonerecordings photos screenshots movies etc. Then I came to my notes/memos which took my whole day and I still haven't figured it out.
Here is the problem:
I can acces the internal memory from my phone but a lot of files and folders are not displayed including the databases which hold the memos at least thats what I think.
I have a Sony Xperia Z Ultra and c6833 model (European version I believe) it has stock firmware on it, its rooted and has SU on it. The Usb debugging mode is on. I'm using windows 7 ultimate and the normal (windows) file explorer (I don't think this is the problem). Show hidden files folders and drives is activated all the boxes that begin with hide are unchecked. When googling I stumbled on a lot of answers with folder options in windows. This is not the problem, the problem is that windows sees the internal memory as a device not as a driveletter. Therefore Windows hides these system files and folder options doesn't effect that (atleast thats how I understand it).
Since my device is rooted I know there most be a solution. An android expert answered that if your phone is rooted you can acces it without the touchscreen. Sadly he didn't post the solution for that. Here is the thread:
http://www.justanswer.com/android-devices/7a5nt-folders-starting-dot-s2-using.html
I've read about ADB but i'm not sure how this might help me I found some information about how to use ADB for flashing a new rom but ofcourse thats not what I want.
http://androidteen.com/setup-adb-and-fastboot-driver-with-android-sdk/
There are some topics right here on xda developers showing me the directory on where to find the memo database but I can't even see those folders:
http://forum.xda-developers.com/showthread.php?p=24036872
(someone also suggested using Kies but I don't have a Samsung obviously)
http://forum.xda-developers.com/showthread.php?t=1534157
I also tried using PC Companion from Sony. Sadly I saw no option to copy memo's with the backup utility so I called Sony. They told me its not possible to copy notes after the spokeswomen asked a few colleagues there was also no other way of syncing notes with the pc she said. (remember that I can't install any apps or do anything on the phone since the touchscreen doesn't work not even marginally)
So I kinda ran out of options so the only thing left for me to do was to create a topic right here. Any detailed information on this matter would help tremendously (at least I hope). I really want to have those notes So any help would be greatly appreciated.
Thanks in advance.
Man, you are very lucky that you had USB debugging enabled! Adb is indeed the way to go, if you know the directory you want then you need the PULL command:
http://eagle.phys.utk.edu/guidry/android/pushpull.html
If you're unsure of which directory or file it is, it's possible the below will work to copy off all apps and data although I'm not sure how it'll treat system apps:
http://www.howtogeek.com/125375/ho...kup-without-rooting-or-unlocking-your-device/
Or, a more complex but entirely more reliable process below:
http://forum.xda-developers.com/showthread.php?t=1818321
Hope that helps.
Sent from my C6833 using XDA Premium 4 mobile app
Thank you so much for posting your reply. I've been very busy these days but I finally got to it.
I was able to get in to the Z ultra using the ADB method but sadly I had no succes.
I could see more then I could using windows explorer but the data folder was empty. I don't understand what went wrong because I'm sure my device is rooted (titanium backup worked very well and I had SU installed). Sadly I didn't make any recent backups with Titanium backup. I see more people that can't see there data folder on there device while its rooted so I guess I'm not the only one.
For other people this ADB method would work very well I guess.
Maybe its the way I rooted my device I don't know. (I used a Chinese programm then let Su take over root control)
Anyway thanks for the help. My device is beeing picked up tomorrow for repair so I'll just factory reset it.
erik0072 said:
Thank you so much for posting your reply. I've been very busy these days but I finally got to it.
I was able to get in to the Z ultra using the ADB method but sadly I had no succes.
Anyway thanks for the help. My device is beeing picked up tomorrow for repair so I'll just factory reset it.
Click to expand...
Click to collapse
Why make this so complicated with ADB? Use a file manager on your device like root explorer. Find the files, copy them to your SDcard partition in a new folder. Connect to your pc and copy/paste the files to your computer.
Here's my data folder. Copying files from here everyday from an app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
erik0072 said:
Thank you so much for posting your reply. I've been very busy these days but I finally got to it.
I was able to get in to the Z ultra using the ADB method but sadly I had no succes.
I could see more then I could using windows explorer but the data folder was empty. I don't understand what went wrong because I'm sure my device is rooted (titanium backup worked very well and I had SU installed). Sadly I didn't make any recent backups with Titanium backup. I see more people that can't see there data folder on there device while its rooted so I guess I'm not the only one.
For other people this ADB method would work very well I guess.
Maybe its the way I rooted my device I don't know. (I used a Chinese programm then let Su take over root control)
Anyway thanks for the help. My device is beeing picked up tomorrow for repair so I'll just factory reset it.
Click to expand...
Click to collapse
Bit late. But like superuser said find the files and copy them to your sd card. If you touchscreen doesn't work then you will need an otg cable and a mouse and control phone that way when touchscreen has gone.
SÜPERUSER said:
Why make this so complicated with ADB? Use a file manager on your device like root explorer. Find the files, copy them to your SDcard partition in a new folder. Connect to your pc and copy/paste the files to your computer.
Here's my data folder. Copying files from here everyday from an app
Click to expand...
Click to collapse
Sent from my C6833 using Tapatalk
Warning use this tool at your own risk i am not responsible for you bricking your device
That being said lets talk about what this does and how it works
see picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 3072502
How it works
1. your Fire TV Must have root and busy box installed plus adb network turned on for this to work
2. click on 2 amazon fire tv firmware installer.bat
3. follow script to install everything you will need
4. if you are having trouble watch my youtube video
Tool Options
1 Root device
2. install fire tv launcher
3. disable ota updates
4. install cwm recovery
5. firmware downgrade and restore to software version 51.1.0.2_user_510058520 for CWM recovery install
6. unlock the bootloader
7. Install custom boot menu
8. Install Pre Rooted Stock rom update bueller-51.1.4.0_514006420
Newest versoin V6
CHANGE LOG
V1 release
V2
added root
added firedtv launcher
added ota disable
cleaned up tool
new interface
V3
total rework
added CWM recovery
added recovery restore as part of firmware restore
V4
added option 6 unlock the partially bootloader
V5
updated CWM recovery file
added Boot menu install option to tool
V5.1
added full bootloader unlock to the tool
V6
Added option 8 install prerooted stock rom. flashing this file will update you to bueller-51.1.4.0_514006420
Link to script tool HERE
Firmware is include in the Super Tool from V3 on
Mirror backup server
http://www.rootjunky.com/backup-file-server/
Video on how to use this script tool
Amazon Fire TV Firmware installer Tool
CREDITS
RBOX for all his work on the Fire TV
http://www.aftvnews.com/ For some great post and tutorials that helped me make this tool
Worked great! Thanks a lot!
MadFlava said:
Worked great! Thanks a lot!
Click to expand...
Click to collapse
yep working on a video now and tweaking the tool but the one posted does work
Tomsgt said:
Warning use this tool at your own risk i am not responsible for you bricking your device
That being said lets talk about what this does and how it works
see picture
View attachment 2829336
How it works
1. your Fire TV Must have root and busy box installed plus adb network turned on for this to work
2. Download the firmware from Rootjunkysdl.com; example bueller-ota-51.1.1.0_user_511069920-signed.bin
3. then rename firmware to update.zip
4. place update.zip in folder with batch files
5. click on 2 amazon fire tv firmware installer.bat
6. follow script to install
7. if you are having trouble watch my youtube video
Link to script tool HERE
Video on how to use this script tool
Amazon Fire TV Firmware installer Tool
Click to expand...
Click to collapse
Nice!
Can you tell me how long it takes to copy file over wifi?
I had an idea to do this with the files manually copied to the usb drive. I wanted the instructions to be where the user copies the script file to a thumb drive along with one or all of the bueller.xxxxx.bin files. the script does a list of bin files in current director and and lists them with numbers and waits for user to enter a number to select the file of choice (this allows for downgrading also.) it then performs actions. chmod, echo then cp and reboot in the script file. this should be rather easy for someone who has scripting skills with input & variables in android.
update.zip Did Not Convert
I copied this firmware update, bueller-ota-51.1.1.0_user_511069920-signed.bin, to the Fire TV Firmware Restore Tool and renamed it to update.zip. I did not get the popup regarding changing the extension. And the update.zip file remains with a .bin extension as seen below. Any ideas on why it did not convert?
Just wanted to chime in and say thanks, I had tried to do the manual upgrade one my 2nd fire tv and it was not working for some reason, this did the trick and was easy to use. Ended up getting the firmware updated and the remote upgrade for both my fire TV's so thanks for this!
Skater4599 said:
Just wanted to chime in and say thanks, I had tried to do the manual upgrade one my 2nd fire tv and it was not working for some reason, this did the trick and was easy to use. Ended up getting the firmware updated and the remote upgrade for both my fire TV's so thanks for this!
Click to expand...
Click to collapse
glad you like the tool i am thinking about expanding it to do more. we will see
Will this work?
I set Windows 7 to show extensions for known file types. I then changed the name to update.zip and it converted to a compressed zip file. Below is what is showing in the Fire TV Firmware Restore Tool.
And below is the content of the update.zip folder.
Can I proceed with the firmware upgrade? I am somewhat concerned because your video shows the update.zip file type to be to be "ZIP File" where as my file type is "Compressed (zipped) Folder (.zip)" .
mjbxx said:
I set Windows 7 to show extensions for known file types. I then changed the name to update.zip and it converted to a compressed zip file. Below is what is showing in the Fire TV Firmware Restore Tool.
View attachment 2831213
And below is the content of the update.zip folder.
View attachment 2831219
Can I proceed with the firmware upgrade? I am somewhat concerned because your video shows the update.zip file type to be to be "ZIP File" where as my file type is "Compressed (zipped) Folder (.zip)" .
Click to expand...
Click to collapse
looks good to me
Script tool updated with lots of new stuff check it out HERE V2
Download links not worked...
Waiting for fix
Finally Have The New Firmware Update
Took the plunge with Amazon Fire TV Firmware Installer Tool and installed the latest firmware update. It worked like a charm. It really bothered me that this update was taking so long to arrive and now I finally have it. BTW, you will also have immediate access to the remote control firmware update as well, by going into KFTV settings. Thanks for providing a video tutorial and the tool necessary for achieving this milestone for me.
mjbxx said:
Took the plunge with Amazon Fire TV Firmware Installer Tool and installed the latest firmware update. It worked like a charm. It really bothered me that this update was taking so long to arrive and now I finally have it. BTW, you will also have immediate access to the remote control firmware update as well, by going into KFTV settings. Thanks for providing a video tutorial and the tool necessary for achieving this milestone for me.
Click to expand...
Click to collapse
Glad I could help
Should this work properly with BusyBox Free? Just want to make sure.
Thank you for putting this together!
Spelvin said:
Should this work properly with BusyBox Free? Just want to make sure.
Thank you for putting this together!
Click to expand...
Click to collapse
yes busybox free should be fine
Any chance you can add in StickMount and moving apps to an external drive? Thats the next big thing I want to do. It would be awesome if it could be automated, then I could install XBMC as my dashboard and be all set. Im holding off installing XBMC just because there is so little storage space on the FireTV.
Hey there this seems like a great tool! But, having a bit of an issue right now. My FTV is rooted with busy box installed. I ran the firmware update tool and everything seemed to go as planned, but my FTV in recovery said the update not successful and rebooted into the old firmware. Now I do have Xposed installed with some modules and XBMC launcher also installed and running. I also have the OTA update also disabled. Would these things cause this error? Any help is much appreciated! Cheers
I used version 2 of the tool and it worked GREAT!!!! I will say it DID take a while to upload the firmware to the point I thought something went wrong. It took about 23 minutes before I saw the install screen on my TV...BUT it DID work!!!!!!! Thanks for making this script!!!
mikespe said:
I used version 2 of the tool and it worked GREAT!!!! I will say it DID take a while to upload the firmware to the point I thought something went wrong. It took about 23 minutes before I saw the install screen on my TV...BUT it DID work!!!!!!! Thanks for making this script!!!
Click to expand...
Click to collapse
glad you like it. my fire tv is ethernet cabled not wifi and the upload is only about a minute
Tomsgt said:
glad you like it. my fire tv is ethernet cabled not wifi and the upload is only about a minute
Click to expand...
Click to collapse
does not work with latest update . comes back and states did not install updates
Im about to send this one back
cant get netflix to work unable to connect try again bull
everything else works rooted google and netflix i downloaded but you need a mouse
I figured i'd downgrade the firmware and start there to see if that would make a difference
Hi,
I contacted gearbest to root my TV box and they sent me a link from Baidu. I tried to download it but I can't because it want a Chinese number to register. Somebody can download and upload on mega or something else the Rom? Thanks
Link: http://pan.baidu.com/s/1bpDQFhX Password: nd93
https://docs.google.com/uc?id=0B5VjVTtm8AqmX3gxa0pOcU5kNjg&export=download
However, this version is not pre-rooted, it is the latest release as of now (rel. date 2016-07-19).
To update:
Extract the 3 files (update.zip, factory_update_param.aml & recovery.img) to the SD Card
start the "update / backup" app on your box
select the update.zip and confirm
box will restart and install the new firmware
other version pre-rooted?
I try to find to root this tv box but i loose my time.
DIDIMR said:
other version pre-rooted?
Click to expand...
Click to collapse
All releases so far are not rooted. You can gain root access via ADB though.
I used adbLink to open the shell & "mount -o remount,rw /system".
Deleted the bootanimation and other things to test if it actually works... it does.
Editing the build.prop is also possible (ro.adb.secure=0, ro.secure=0, for example).
I tried to install my own version of TWRP 3.x, the command was successful ("dd if=/sdcard/recovery.img of=/dev/block/mmcblk1p6") but it didn't stick and the stock recovery was still active.
Since it's Marshmallow, I wasn't able to manually recreate the systemless root method.
I'm not going to try further for now, waiting if they will release an update, etc.
Bingo,
Can you make a root installer for this device or do we need chainfire to make a new SuperSU? I have 50 units that I need to root but can't find an installer. I need it for Titanium Backup to restore my custom setup.
atvbc said:
Can you make a root installer for this device? I need it for Titanium Backup to restore my custom setup.
Click to expand...
Click to collapse
I'm looking into it, but with my limited knowledge, most approaches seem to be a dead end due to Marshmallow. (It's also my first box ever bought in general...)
I already have my custom TWRP img ready, but it doesn't stick when I flash it.
ADB says it was "dd" successfully but rebooting straight to recovery brings up the stock recovery.
I hope someone beats me to it. ^^
I also wrote an inquiry, asking for an IMG file, so I can use with the customization tool... I don't think they have one ready yet...
And those twats sitting on the source files and can't poop out an alternative variant of the firmware with root? Beetch please.
AFAIK, all boxes with Android 6 are in this state (looked at some other firmwares).
The old tricks from Lollipop don't work here anymore, like booting a custom recovery.img from SD, etc.
edit: can't mount "sbin" as RW (ofc. knowing where it's coming from)
edit: tried an old signed ZIP (root update for Android 4.x) via stock recovery: it went through, verified... I'm afraid this won't work with a custom ZIP trying to recreate latest SuperSU install method...
atvbc said:
I have 50 units that I need to root but can't find an installer.
Click to expand...
Click to collapse
Ok Heisenberg, slow down... :laugh:
atvbc said:
...or do we need chainfire to make a new SuperSU?
Click to expand...
Click to collapse
SuperSU would work "ootb" but the stock firmware has no 'unzip' in 'sbin', so the original script will fail.
And since we don't have a custom recovery that can support 'unzip'. that's another dead end.
I tried flashing 3 different versions of my custom recovery zip (with diff. timestamp, etc).
They all went through without error but the device isn't even bothered, still brings up the stock recovery.
I also modified the original update.zip that contains the whole firmware with all partitions and just replaced the recovery.
Signed it, flashed it, no error, reboot... yup, stock recovery is still there. ^^
edit: small progress, I can now update the recovery... as proof I changed the "error pic" with the little droid and wrote something nice on it ^^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Awesome Bingo Bronson! At least it's a start. Now if only we could get TWRP working on these... I've tried all the S905 TWRP img files available but no joy yet, at least not booting from microSD card. Android 6.0 Marshmallow has been rooted on several smart phones; can we learn something from those methods and maybe hack together a working root?
atvbc said:
I've tried all the S905 TWRP img files available but no joy yet
Click to expand...
Click to collapse
SDK 23 devices do things slightly different, yes, but the main reason for the old images not working is (ofc. ^^) the ramdisk cpio and the small but important differences in the hardware (boards) and the according references in the files.
I'm going through the ramdisk cpio piece by piece as we speak, takes "a while" for users like me...
Let's hope it will at least boot with an error and not just flicker and remain on the "Google TV" bootloader screen.
I'm editing the stock recovery from 2016-07-28 (language fix update).
If I fail numerous times, I will get on my knees and send Abdul the files and some monayyy. ?
edit: calling it a day... will continue tomorrow afternoon (GMT+1 ^^)
So basically if someone can get TWRP to boot on these then root should be fairly easy? I guess the only road block after that would be getting sbin mounted rw so we can install the SuperSU binary.
atvbc said:
So basically if someone can get TWRP to boot on these then root should be fairly easy? I guess the only road block after that would be getting sbin mounted rw so we can install the SuperSU binary.
Click to expand...
Click to collapse
I've used systemless root on a number of 6.0.1 devices... Qualcomm, MTK... based one the arch. this one should work just as well.
'sbin' is part of the ramdisk, so it's always 'ro' (hence: "knowing where it's coming from" ^^) so no need to try to force anything here.
Btw. that was the default 'sbin' from the stock system, the 'sbin' from a custom recovery has all the goodies on board.
Ramdisk: applying the changes necessary for TWRP is not that difficult, just need to finish the matching ramdisk cpio...
That being said, I haven't gotten anything done since my last post which is annoying... had to work on "non Android" related things.
Currently rechecking the blocks & partition table, so everything can be mounted properly (given it boots up ^^).
Any updates?
Eager to get this.
robinkooli said:
Any updates? Eager to get this.
Click to expand...
Click to collapse
I gave up with slapping it together manually, I may try again on the weekend when I'm able to use my Linux PC again and build it from source like it should be done...
If you want to try, your updater-script can look like this:
Code:
set_bootloader_env("upgrade_step", "3");
write_raw_image(package_extract_file("recovery.img"), "recovery");
show_progress(0.200000, 10);
set_bootloader_env("upgrade_step", "1");
set_bootloader_env("force_auto_update", "false");
I had the fstab files edited with the info from the block & partitions report but no success so far.
( I avoided porting / using old files from TV boxes running Android L based firmwares...)
Aldideos said:
Hi,
I contacted gearbest to root my TV box and they sent me a link from Baidu. I tried to download it but I can't because it want a Chinese number to register. Somebody can download and upload on mega or something else the Rom? Thanks
Link: http://pan.baidu.com/s/1bpDQFhX Password: nd93
Click to expand...
Click to collapse
Just download Kingroot or Kingoroot . One of the two will root it . And if successful try get supersume so you can get rid of the bloat they install and install SuperSU
Autolounge said:
Just download Kingroot or Kingoroot . One of the two will root it . And if successful try get supersume so you can get rid of the bloat they install and install SuperSU
Click to expand...
Click to collapse
I had already tried this, but no root
Aldideos said:
I had already tried this, but no root
Click to expand...
Click to collapse
Can you run CPUZ and post your specifications so I can find a method or possibly test certain methods if I have it .
My Mini M8S II doesn't go past logo screen after using Kongo Root (Windows edition) over ADB internet.
Autolounge said:
Can you run CPUZ and post your specifications so I can find a method or possibly test certain methods if I have it .
Click to expand...
Click to collapse
valid.x86.fr/a/zc7944
its a cpuz validation url. not allowed to post links due to this being a new account.
If anyone here has the skills to root this box and can prove it, I will donate one and pay for shipping if you're within Canada/USA. I'm looking for a zip file based root that can be applied from a flash drive or SD card (ezroot style).
Root
atvbc said:
If anyone here has the skills to root this box and can prove it, I will donate one and pay for shipping if you're within Canada/USA. I'm looking for a zip file based root that can be applied from a flash drive or SD card (ezroot style).
Click to expand...
Click to collapse
I am fairly certain I can put together something for you. I have a pretty good history with android, custom ROMS, blahblahblah. I have a Android box from Tops with the S905 in it and rooted mine manually from my laptop. I don't have this particular model but they can't be that different. What version of Android is this running?
Android 6.0,
ARM64
Kingo Root, KingROOT (APK's) don't work.
Kingo Root (Windows) bricked my M8S II ): .
Hello! So, this thread is a result of a promise that was given to @tsongming long ago, and I finally found some spare time to write about.
This guide is also the only one of its kind AFAIK, so you won't be able to find this anywhere, and also this method is applicable to ANY device, as I did this to some others, for testing purposes.
I am currently in Turkey, and it's not possible to use dipper for WiFi Calling or Vi-WiFi, but there are many phones that carry the exact same chip-set, which enables to add this feature to my own phone. So, if you are going to continue to read and apply on your phone, please open a new tab right now and find a phone that supports Vo-WiFi and/or Vi-WiFi in your area, with the same chip-set, and find its EDL ROM!
This process requires TWRP!
What does it do?
It basically changes the behavior of your phone towards the carrier, and allows you to connect to the networks that has 4G goodies.
Also, by following this guide and making changes on your phone, you accept that I am not responsible for any damage you may cause to your device, you are on your own.
In my case, the phone I used was GM9Pro. It has same SDM845 chip-set as dipper has, and since it's a Turkish brand, it's Vo-WiFi and Vi-WiFi support was unquestionable with no doubts.
The program you will need specifically for this job is: 7-Zip. You can download here: https://www.7-zip.org/ It's an open source software that supports many compression formats, but specifically focused on 7Z.
So, when you download and open the EDL ROM package, you will see that there are TONS of img files. The ones we need are modem images. In my case, there were 2 separated modem images that would work for me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
They seemingly carry the exact same files, but I preferred the modem_a.img file to continue.
Before continuing, I wanted to warn: if the phone you have the EDL files does not contain the files I'll mention below OR the file structure is nothing like it, you have two options:
Find another device.
Check the other image files to see if there are anything that would work.
Find a physically working device that you can access to its filesystem. You will need to search and extract the required files in order to continue.
At this point, in order to show the path I watched and help you to examine the file structure for the second option I provided above, I'll add screenshots here.
So, once we got our modem image out the zip or rar or tarball file, we will open it with 7-Zip. This should be the file structure:
Go into image folder:
These are pretty much how your modem.img file should look like.
When you browse to this folder, rest of the process is up to your localisation and carrier.
I browsed into my carrier's folder with this path you can see in the screenshot:
So, after that step, you will extract the mbn file of your carrier, and DO NOT CLOSE THIS WINDOW, we will need it one second later. At this step, I heavily recommend you to extract the carrier folder which includes "volte" and "nonvolt" folder, and replace them as I'll tell below.
The important part is, you should NOT modify the mbn file, because it is signed and you will break the signature by editing it.
When you got into dipper, REBOOT INTO TWRP. You can't do this without TWRP!
Once you got into TWRP, make sure "firmware" partition is mounted. We will modify it. "firmware" partition is basically the storage of modem files of your phone.
By going into "Advanced > File Manager", you will reach into your phone's root directory. Go into the firmware folder, and follow the path you did on 7-Zip. The folder names, et cetera HAVE TO be same, to make it work. If they are different, well, it just won't work. There's an another method to accomplish it, but I did not look into that.
You also will want to backup these mbn files you are going to modify, so, simply move them to your /sdcard in order to make them backed-up and deleted from that folder simultaneously.
Also, you can use "adb pull" to backup on your PC.
Sooo, at this point: We simply copy the path at the 7-Zip for our adb argument, and add "/firmware/" to it. You also need to convert back-slashes into slashes. It should look like this:
Code:
/firmware/image/modem_pr/mcfg/configs/mcfg_sw/generic/eu/vodafone/volte/turkey/
What now? I will hope that you know how to use ADB, you can modify this file manually. To proceed, you need to have ADB installed in your computer. How? See this: https://www.xda-developers.com/what-is-adb/
Now, thinking that I extracted my mbn files into the desktop, the command I will use will be this:
Code:
adb push "C:\Users\username\Desktop\mcfg_sw.mbn" "/firmware/image/modem_pr/mcfg/configs/mcfg_sw/generic/eu/vodafone/volte/turkey/"
After this process, just reboot your phone and make sure it works. As I suggested above, you might need to do this for all folders, for example "/firmware/image/modem_pr/mcfg/configs/mcfg_sw/generic/eu/vodafone/". I would try to copy both of the folders into my device, as it has "volte" and "nonvolt" folders inside.
On MIUI, you also might need to use QFIL to activate the configuration by hand, you can find more info about it on the Internet. Don't ask something you can find on Google here.
Lastly, this works on AOSP ROMs flawlessly, because it's implemented in a way that it should be, but MIUI is questionable, and I'm not sure if you will have issues on MIUI since I haven't used it for a long time.
Have fun lads, and #StayHome.
Also I should add that these changes will be removed when you flash a firmware package it'll be reset.
buddy are you turkish user? forum.miuiturkiye.net 'via dei Did you share it?
I need Turkish in this guide. My English is not enough for this technical subject
MehmetNY said:
buddy are you turkish user? *** Did you share it?
I need Turkish in this guide. My English is not enough for this technical subject
Click to expand...
Click to collapse
Sorry, since I don't speak Turkish, it's not possible to translate or rewrite in that language.
Nice work!
I do not have a need to make these changes to my Mi8. However, I will definitely share your link with people that will be very interested in making these changes.
It seems that this method would likely work well for my friends that still use LeEco Pro 3 with Snapdragon 821 processors. Also, those guys are also still using Hannah Montana Linux, so maybe they will also consider upgrading to Biebian. :laugh:
Thanks for posting!
tsongming said:
Nice work!
I do not have a need to make these changes to my Mi8. However, I will definitely share your link with people that will be very interested in making these changes.
It seems that this method would likely work well for my friends that still use LeEco Pro 3 with Snapdragon 821 processors. Also, those guys are also still using Hannah Montana Linux, so maybe they will also consider upgrading to Biebian. :laugh:
Thanks for posting!
Click to expand...
Click to collapse
Thank you, I'll also modify the thread for adding carriers for regions in order to enable VoLTE, of course will come with this features at the title too.
Well yes biebian is superior, their banner was a bit aggressive but apparently they recently changed it to a less aggressive ones.
I'm still confused by this thread. Can this be used to enable VoLTE/VoWiFi on Mi8? My carrier, T-Mobile, supports it and VoWiFi with my SIM works in a different phone but I could never get it working in Mi8.
mr3p said:
I'm still confused by this thread. Can this be used to enable VoLTE/VoWiFi on Mi8? My carrier, T-Mobile, supports it and VoWiFi with my SIM works in a different phone but I could never get it working in Mi8.
Click to expand...
Click to collapse
Obviously yes!
I'd like to try this guide out but where do you find EDL ROM for different devices? Any reason not to start off Pixel 3 as that is SD845? Thanks.
mr3p said:
I'd like to try this guide out but where do you find EDL ROM for different devices? Any reason not to start off Pixel 3 as that is SD845? Thanks.
Click to expand...
Click to collapse
Well since its not being marketed in many countries, it'd be a good reason t8 not try it if ypu don't live in USA, due to high probability of lacking required files for this process. However, you always can give it a shot.
Well to find EDL ROM, use Google or official websites, some release EDL ROMs like Xiaomi (the community calls it MiFlash ROMs sadly), but you're likely to find them on Google. They also mention them as QPST ROMs, since QPST is also used for flashing ROMs on bricked devices.
would any of these be suitable?
https://developers.google.com/android/drivers
I'd like to try this to enable VoWiFi in USA but can't located a suitable EDL ROM
mr3p said:
I'd like to try this to enable VoWiFi in USA but can't located a suitable EDL ROM
Click to expand...
Click to collapse
Since you live in the US : Try the steps that I found on this thread first: https://forum.xda-developers.com/Mi-9/how-to/wifi-calling-volte-mi-9-t3917887
This may not work for everyone, but it definitely worked for me and like you I am located in the US.
VoLTE *#*#86583#*#*
VoWIFI *#*#869434#*#*
Dialing these codes automatically adds extra switchable options and I am now getting a better signal ( My phone is now primarily using band 12 from a much closer tower) Previously I could only lock onto bands 4 and 5 from my house. and able to use VoWiFI
Again, this may not work for everyone,I have Tmobile, and I should have been getting these features without using the codes. The update to VoWifi even persisted through my recent update from Xiaomi.EU 4.30 to 5.7
I'm also on TMobile but those codes don't work here. FWIW, I using latest Global stable firmware.
mr3p said:
I'm also on TMobile but those codes don't work here. FWIW, I using latest Global stable firmware.
Click to expand...
Click to collapse
I am using Xiaomi.EU works fine here
this applies to enabling (4g+) carrier aggregation?
tsongming said:
I am using Xiaomi.EU works fine here
Click to expand...
Click to collapse
Is there an EDL ROM for Xiaomi.EU or can modem_a.img be extracted? I'm on LOS17 and would very much like to get VoWiFi working.
I unpacked a couple of SD845 device ROM to try and get this working.
OnePlus 6T modem.img under /image/modem_pr/mcfg/configs/mcfg_sw/generic/na/tmo/commerci/
has 2 files:
mcfg_sw.bmn
mcfg_sw.sig
Should the .sig file also be copied or does it matter? There is no VoLTE folder as shown in your example. Does this mean I need to try ROM from a different SD845 device that has a VoLTE folder for TMO?