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?
Related
Well, I'm not much of a guide person, but there's a great tool that's been out for a long time that has proven to be quite useful to me. THIS IS NOT A REPLACEMENT FOR FREEZA'S GUIDE. That's an excellent guide, and he deserves full credit for it. This guide is for those of you who want to trim/debloat after you flash. It also serves many other handy uses, which I shall explain in a few.
Also keep in mind, this will work on damn near ANY rooted Android phone. In fact, I used to use it QUITE a lot on my old Sprint Hero. This is essentially ADB without the need to know how to use the command line.
~~ This guide is a constant WIP ~~
What is Android Commander?
It's an all-in-one tool that was designed using adb. It provides the following:
[*]Complete root-based file manager
[*]Applications Manager
[*]Rebooting/Powerdown Abilities
[*]Storage Monitor
[*]All around awesome tool
It's completely free to use and is written by a talented XDA developer.
Requirements:
Windows XP or higher: As if I'm going to give you link to this
My little ADB Package: http://dl.dropbox.com/u/345001/Images/AC Guide/ADB.rar (For anyone wondering why I'm giving this seperate, it's to save you the trouble of having to download the entire android sdk and going through the convoluted method of using the SDK manager to grab adb)
Android Commander written by our very own XDA user PanPiotr: http://androidcommander.com/
1. Download my ADB package, and extract is somewhere. Inside is a folder called ADB, with two dlls and the adb executable. Remember where you put it.
2. Download and install Android Commander.
3. Right click and run Android Commander as administrator. It will ask you to set the ADB path near the bottom. Select the ADB folder that contains the 3 files above, which you downloaded already.
4. If it doesn't automatically start the app after selecting the folder, simply press exit, and run it again as administrator. This time, the app will start up
And this is what you see!
{
"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"
}
Now for starters, you'll notice a plethora of information. Try not to get overwhelemd. Android Commander is a ridiculously comprehensive utility. And the best part is that it's based entirely on ADB. Now, by default, you'll see your Windows files on the left pane, and the Android files on the right.
Let's begin with the debloating. Start by finding the "System" folder first.
From here, head on over to the "app" folder.
So this should be pretty self explanatory. Start selecting checkboxes for apps and bloatware that you don't want/need. Then, just click the "delete" button. It will delete them all in one shot.
I know this seems a bit anticlimactic, but that's more or less it for the debloating guide, because that's only one of the many uses AC has. Read on to the next few posts for a few scenarios/possibilities that you may encounter while using custom ROMs.
Basic Scenarios/Uses
This post covers basic scenarios and uses for Android Commander.
[If you've been directly linked to this post, please see the post above for information on installing and getting Android Commander up and running]
Remember, AC can start functioning as quickly as just moments after you see the white HTC screen. It doesn't have to be fully on for you to use AC and all its features. Android Commander can also be used from recovery as well.
Help! I used SetCPU, checked "Set On Boot", overclocked too high, and now my device is in a boot loop
Not a problem! I've done this too many damn times to count. The solution comes down to two options; one, be super fast when booting up and try and clock down SetCPU when you get in (very frustrating), or use AC! Remember, Android Commander can be used either in recovery or even during boot! So what we're going to do is start it up, and uninstall SetCPU. Let's open up Android Commander, and select "Applications Manager". It will ask you if you would like to update the list of applications, click yes.
From this point on, you can now see all of your applications. Simply click on one of the applications, and either uninstall it using the buttons above, choosing to delete its data or not.
By the time your device finishes rebooting, or when you boot out of recovery, you'll find SetCPU gone and your device no longer locking up and bootlooping! Easy, huh?
Did you know you can reboot the device from Android Commander?
Yes, you can . Simply click on the "Phone" menu up top:
Pick what you want to boot in. Also, yes, you see "screenshot" in there, but it currently doesn't work for the EVO 3D. It should for older devices though.
Did you know you can flash a recovery image through AC?
Indeed, you can.
More to come!
Advanced Uses - For Devs/Themers
This section is intended for both budding and veteran ROM cooks, modders, and themers.
Did you know that you can set file permissions with Android Commander? You can do what root explorer does, just fine. If you choose to use the 7.9.9.9 beta and up, you can easily set file permissions of any file, as shown below
MORE TO COME
First part of the guide is up
Thanks for this, I look forwards to seeing what more comes to this guide. Well done man.
empiire said:
Thanks for this, I look forwards to seeing what more comes to this guide. Well done man.
Click to expand...
Click to collapse
Glad you find it useful. It's got a ton of potential for devs such as yourself, I'd highly recommend you experiment with it, there's stuff I still don't even know about yet.
It even has it's own pre-"su"'d command line built into it.
Updated the "basic use" post to include more awesome little details
This is a nice tool! im definitively gonna be using this! thanks!!
steal25 said:
This is a nice tool! im definitively gonna be using this! thanks!!
Click to expand...
Click to collapse
Let me know what other cool features you end up finding, I'm sure you'll run into plenty of stuff I haven't found yet.
This will be loaded before the sun sets. Thanks for sharing - great utility.
Sent from here using this. Black. Slab.
Thats a pretty slick app.
I did everything stated in the first post, and for some reason it doesn't say I am rooted. so I don't have the application manager. to be clear I don't need the SDK installed, just your file? I extracted it into a new directory and then set that as the path when I started up AC, it starts up, finds my phone, can explore it, reboot it, but it still says I am not rooted in the lower left corner of AC. I am not a noob when it comes to doing stuff with android, but am noobish with adb, never used it before, so i thought this would be a great tool for me to learn...if I can get it to work.
jbermi said:
I did everything stated in the first post, and for some reason it doesn't say I am rooted. so I don't have the application manager. to be clear I don't need the SDK installed, just your file? I extracted it into a new directory and then set that as the path when I started up AC, it starts up, finds my phone, can explore it, reboot it, but it still says I am not rooted in the lower left corner of AC. I am not a noob when it comes to doing stuff with android, but am noobish with adb, never used it before, so i thought this would be a great tool for me to learn...if I can get it to work.
Click to expand...
Click to collapse
Hmm. Did you run AC as admin?
LiquidSolstice said:
Hmm. Did you run AC as admin?
Click to expand...
Click to collapse
yep, followed everything in the first post...and yes, the phone is rooted. LOL. I am going to uninstall AC and try again, and see if that works...
problem - phones rooted - viper rom 1.2.1 stock kernal - downloaded the two files you have, installed your AC, and unzipped the ADB - start up, point it to that folder, then it has the little window that says DEVICE: NOT FOUND. have debug on, charge, i am the admin on the pc.
-----sorry------ now it runs only after i posted.... sometimes thats all it takes - now to test it out, looks very useful, and easy.... thank you
Thanks, Liquid. Way faster then using Root Explorer or manual adb. Wish I'd known about this ages ago.
Very usefull...but We realy need a UI manager to change icons ect....
Thanks Liquid - I used your LiquidSense ROMs over on the Hero side, and now that I've got my E3D, it's great to see you devving over here. I used Android Commander a lot on the Hero, so good to see it will still work for the E3D! Thanks for the Guide!
-mb
when i use the sign .zip file tool, i put a file on my desktop, then run the tool and cannot figure out where is put the new signed file at? Any help?
i changed the output folder to desktop, and nothing, it doesn't sign the file and ouput it....hmm...
Great guide! I use Android Commander for just about everything. Nice point on using it to get out of a boot loop. I discovered that when I had my Hero, and it saved me many times.
Sent from my s-off Shooter!
Previous thread Name was [GUIDE]What Is Meant By Firmware, Stock & Custom ROMs And Flashing
{
"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"
}
Welcome to the world of Google Android.
Do terms like ‘Android ROM’ confuse you? Is your understanding of ‘flashing’ limited to acts of exhibitionism? Do you feel left out or clueless when your friends talk about flashing the latest custom ROM to their Android device ? here is a guide for you to make your life easier
Hey guys, this is a guide which will help many people (new users).
Note-
Red color means -> its important !!
Click to expand...
Click to collapse
Understanding ROM’s and Builds
A ROM is essentially a custom version of Android. Each tweaks, combines, or optimizes Android to offer something standard versions lack. Within ROM’s, you have what are known as builds (basic branches of Android code) that offer certain features and characteristics.
Think of it as a crude metaphor for Microsoft Windows. There’s XP, Vista, and Windows 7. All three are Windows operating systems and can typically run the same programs, but there are major differences between them. Within each OS, there’s further distinction between Vista Home, Vista Pro, and Vista Ultimate. Likewise, one ROM can spawn multiple versions. For instance, there are several flavors of Drake’s Hero ROM..
Be advised that some ROM’s require a wipe (erases all information stored on your phone) before or after installation. This is done when you enter the recovery mode and perform a “factory data reset.”
What is Firmware?
The read-only operating systems that we just discussed above are also called ‘firmware’, as they stay firmly in place without modification access to the users of the device. Modification of firmware is still however possible, just not under normal usage. Many devices require specialized hardware to be used for the purpose while other devices have the storage set as read-only through software protection only, which can be removed or overridden without the need for any specialized hardware, just by using software written for the purpose, often but not always requiring connection to a computer.
Thus, the terms ‘operating system’ and ‘firmware’ both refer to the same thing and can be used interchangeably when applied to such devices.
Flashing
The ROM memory used in smartphones and tablets etc. is often same as flash memory found in SD cards and USB flash drives, simply optimized for better speed and performance while running the operating system. As explained above, it is read-only under normal usage and requires a special procedure for any modifications to be made to its contents. The procedure of modifying or replacing the contents of such flash memory is known as flashing. Thus, in layman’s terms, flashing is essentially the same as installing or modifying the firmware of a device that is stored on its protected flash memory.
2 – Mobile Operating Systems
ROM as the Operating System
When it comes to smartphones and tablets, the term ROM is used to refer to the firmware stored in the internal memory of the device, rather than the internal memory itself. It can also refer to a file prepared for the purpose of replacing this firmware with another version of using a special method.
Thus, when you are told by someone to download a ROM, they are referring to the file that contains the firmware in a format ready to be installed to your phone to replace it’s existing firmware. Similarly, when asked what ROM is your phone running or when told by someone their phone is running a particular ROM, they are again talking about the particular variant of the firmware.
Types of ROMs->
Unlike most desktop operating systems, mobile operating systems can be found in installable format in multiple forms, which can be categorized as follows.
A)Truly Stock ROMs / firmware:
This is the operating system in its default form, without any modifications made to it except for any device-specific support required to run it on the particular device. Truly stock firmware provides the standard user experience of the operating system without any cosmetic or functional changes made.
B)Manufacturer or Carrier branded Stock ROM / Firmware:
This type of firmware has had enhancements added over the default operating system by the device manufacturer or the mobile service carrier. This often includes interface enhancements, proprietary applications and in most cases, restrictions intended to limit the use of the device with a specific carrier or region. There are often further restrictions preventing installation of firmware not released by the carrier or manufacturer.
C)Custom ROM / firmware:
Independent developers who like to customize their devices beyond the standard options provided often tend to release the fruits of their labor for the rest to enjoy, in form of custom ROMs.
3 – Stock Vs. Custom ROMs
Both stock and custom ROMs have their merits and demerits and choosing between the two requires careful consideration. In this section, we are going to make a comparison between the two types of ROMs to help you make the right choice. Let us begin by taking a look at their advantages and disadvantages.
Advantages & Disadvantages of Stock ROMs
Stock firmware is the result of a lot of research and testing done by the operating system vendor, the device manufacturer and/or the mobile service carrier. Therefore, it carries several advantages:-
1>It is usually quite stable upon release.
2>Almost all bugs are patched during the extensive beta testing before release.
3>It carries the official support by the firmware vendor, device manufacturer and the mobile service carrier.
4>Updates are pushed automatically to the device by the carrier.
Along with its advantages, stock firmware also carries its disadvantages and these include:
1>Updates aren’t frequent, as development is done mostly by corporations who have to follow a scheduled release cycle.
2>Providing feedback to the manufacturer in case of any issues is either impossible, unwelcome (often with Apple devices), or a long, tedious process.
3>Similarly, getting official support can be a hassle as well, involving a tedious process.
4>If the device manufacturer and operating system developer are different (as is the case with Android and Windows Phone 7), any updates released by the operating system vendor need to be edited by the device manufacturer or mobile carrier to add compatibility and additional software before release. Hence, some devices get updates delayed by months.
5>Updates are often released first in the United States, leaving the rest of the world waiting. (A world does happen to exist beyond the United States, we’ve confirmed it ourselves!)
6>Worse still, when manufacturers choose to no longer release official updates for their older devices in favor of newer ones, their users are essentially stuck with old versions of the operating system. This case is evident with many Android devices barely a year and a half old.
Advantages & Disadvantages of Custom ROMs-
Custom ROMs are as good or as bad as the effort put into them by their developers. Key advantages of custom ROMs are:
1)First and foremost, choice! There are thousands of custom ROMs out there for a range of devices, each offering a diverse set of features not found in the stock ROM.
2)Update frequency – custom ROMs are often under active development and newer releases of the core operating system are incorporated in them way before updated official ROMs are released.
3)Providing feedback is as easy as leaving a message on the development forum for the ROM in question.
Getting support with your issues at the forums is similarly easy, as not only the main developers themselves but also other experienced users of the ROM from the community are glad to help you with your issues and in the process, improve the ROM for everyone.
4)Custom ROMs usually have all the extra restrictions removed
5)Performance enhancements and optimizations found in many custom ROMs can make them much faster than stock ROMs ,enabling users to get the most out of their devices.
5)Overclocking options are built into some custom ROMs, further speeding up the devices.
6)Undervolting options found in some ROMs on the other hand result in improved battery life.
7)Old phones with little internal memory can benefit most from custom ROMs that allow them to use the external SD card memory for the apps exactly the way they would use the internal memory.
So with all these advantages, there should be no reason to stick with the stock ROM, right? Not necessarily! Like all things in life, custom ROMs come with their disadvantages as well:
1)Due to the lack of extensive testing prior to release, many custom ROMs can be buggy in the beginning and installing a ROM with missing or corrupt critical files can even brick your phone.
2)Several custom ROMs that are ports of ROMs from other phones can have missing functionality that hasn’t been made to work on your phone with the ROM yet.
Installing a custom ROM usually involves wiping your phone to factory settings, so you lose your data and start from scratch. Fortunately, Android’s built-in contact syncing along with apps offering message, call log and app backup/restore make this process easier, letting you retain your data.
The installation process can be cumbersome and requires you to root your phone and often circumvent its security features to allow for custom ROM installation in the first place.
Installing a custom ROM will in most cases void your phone’s warranty, though often the process is reversible, meaning you can turn your phone back to stock as long as it isn’t bricked.
Choosing the Right Custom ROM
With several custom ROMs available for most Android devices, choosing the right one isn’t always easy. The question of ‘which is the best ROM for _____ phone / tablet’ is as often frowned-upon at the forums as it is asked, since there is no universal answer for it. One ROM may be the best for me while another might suit you better. The only solution is to read a lot, go through the feature list, read user response and if required, ask the developer questions at the forum page for the ROM. Attempt to install the ROM only after you are fairly satisfied that doing so will not harm your device to the extent you can’t fix.
Power saving tips:
Dont use a live theme
Use a dark wallpaper
Turn off wi-fi & bluetooth when not in use
Stop friendstream, facebook & peep updating every 5mins. Set mine to manual.
Set email app to manual
Set screen brightness to auto or 40% (lower if you can put up with it).
How does one flash a kernel?
The process is a simple as flashing a ROM, put the .zip on ur sdcard, go into recovery,wipe cache,dalvik-cache, install .zip from sdcard, reboot phone and ur done.
You can find stock firmwares here -
sampro.pl
sammobile
Important (Read it carefully) -> Forum & Marketplace Rules & announcements
Android 2.3(Gingerbread) user guide
Android 2.2 (froyo) user giude
Addons (links)....
Simple ways to speed up your Android Device
A Few CM7 Tip and Tricks
[HOWTO] Enable CRT Animations on all Android 2.3 Devices
[Video][HOWTO] Create simple MIUI Lockscreens for Yourself
ANDROID TIPS & TRICKS
[TUT] How to force install apps to SD card without ROOT!!!
Some other guides by our awesome developers-
A Newbie Guide for your Galaxy Ace by EmoBoiix3
[Newbie Guide] adb/fastboot/bootloader/android 101 + Q & A by seraph1024
Newbie Friendly How To's w/ Instructional Videos by dcogen
[GUIDE]Overclocking,its benefits and risks for Ace by Prawesome
TUT]Decompiling an apk,converting dex to jar(NEWBIE FRIENDLY) By Prawesome
[TUTORIAL] UOT Kitchen By ingbrzy
[GUIDE][CM7] Changing Boot Animation by tanmayjindal
[TUTORIAL] How to upgrade, root, flash Recovery & Custom ROM Samsung Galaxy Ace S5830 by hubix
How to unbrick Samsung Galaxy Ace
Video giudes-
A simple introduction to the basic use of the Android operating system. (Youtube)
How to root Galaxy ACE on Gingerbread (youtube)
How to Root Samsung Galaxy Ace S5830 on Froyo(youtube)
What is Root? ( Android )(youtube)
How to use Odin to update galaxy ace (youtube)
Guide: How to download eBooks to Android!
Useful posts -
[UPDATE] DEODEX+ROOT - it`s easy! by Lovetz
All samsung galaxy ace roms,tweaks,kernels by mv_style
That should be enough to get you started.
I hope this guide helps you.......
Dont forget to press Thanks button
First. It's too wordy though. Otherwise, good piece of info!
Sent from my GT-S5830 using xda premium
Sticky-worthy thread!
Also: can you improve the formatting?
Number two: *GUIDE
Sorry if I sounded like a perfectionist a**.
adeklipse said:
Sticky-worthy thread!
Also: can you improve the formatting?
Number two: *GUIDE
Sorry if I sounded like a perfectionist a**.
Click to expand...
Click to collapse
Done formatting ...liked it ?
Nice guide you have there
Just needs to be a little more noob-proof
Excellent thread man...This should be stickied
thread such as these should be stickied,though it needs some editing in terms and some noob-proof overall good job
usb connection problem
hi i have a galaxy ace with cynogenmod 7.2 and i have a problem i cannot find a fix for.
problem:
when plugging in my device into my computer it failes to connect. my computer posts a pop up box instead of saying your device has installed and is ready to use it says the following...
! USB device not recognised
one of the usb devices attached to this computer has malfunctioned and windows dose not recognize it.
for assistance in solving this problem click this message.
i have done the same thing with my sisters phone and her phone connects fine with usb debugging.
what can i do to solve this issue as i would like to use odin to flas back to stock gingerbread 2.3.4
i have looked and searched for months on end and got nowhere please xda help
baileydroid said:
hi i have a galaxy ace with cynogenmod 7.2 and i have a problem i cannot find a fix for.
problem:
when plugging in my device into my computer it failes to connect. my computer posts a pop up box instead of saying your device has installed and is ready to use it says the following...
! USB device not recognised
one of the usb devices attached to this computer has malfunctioned and windows dose not recognize it.
for assistance in solving this problem click this message.
i have done the same thing with my sisters phone and her phone connects fine with usb debugging.
what can i do to solve this issue as i would like to use odin to flas back to stock gingerbread 2.3.4
i have looked and searched for months on end and got nowhere please xda help
Click to expand...
Click to collapse
Type devmgmt.msc in run command popup open of device manager go to Universal serial bus controller there is a yellow mark on samsung usb driver unistall it.after uninstallation have a look on help down there is a button for scan hardware changes press it. go to driver and scan automatically u done
note:-make sure u connected to internet when doing this
Forget the 10 post dev section limit, they just have to read this 5 times!!
Sent from my GT-S5830 using xda premium
----Thread updated----
changelog-
-deleted some useless imformation
-Video tutorials
-Links to other threads
-addons
and more.....
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 ): .
Site: https://copperhead.co/
CopperheadOS is the next-gen hardened android distribution, for those fine folks amongst us who have need for a high-security smart phone. As we all know, there are latent bugs in just about everything, but CopperheadOS [COS for short] attempts to work around these by hardening the Linux kernel and also hardening the user space.
{
"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"
}
The detailed features can be found here: https://copperhead.co/android/docs/technical_overview
An extensive article on this bright new operating system can be found here:
http://arstechnica.com/security/2016/08/copperhead-os-fix-android-security/
Here is a lengthy interview with the main developer of copperhead where he discusses what sets COS apart from other contenders [blackberry in particular] as well as his use of OpenBSD code and the PAX kernel to build COS:
http://www.tomshardware.com/news/copperhead-nexus-more-secure-priv,30565.html#xtor=RSS-181
Tor is currently working in parallel with COS to deliver a slightly modified version of COS which adds some other functionality.
You can read about this here:
https://blog.torproject.org/blog/mission-improbable-hardening-android-security-and-privacy
…and here:
http://arstechnica.com/security/2016/11/tor-phone-prototype-google-hostility-android-open-source/
Installation of CopperheadOS
I tried the traditional install instructions here: https://copperhead.co/android/docs/install
...and found that even with attempts to do the command line work on a Linux box it still doesn't quite work right. One of the prerequisites is you have to download the Android Software Development Kit [SDK]. I did this on the Linux box and it still didn't quite install all the way, I got some sort of error I don't recall right now.
Flashing via TWRP doesn't work all the way either due to a lack of either META-INF or checksum signatures in the contained zip file.
So let's try this:
(1)
First you need to acquire the ROM from Nexus 6P the download section here: https://copperhead.co/android/downloads?device=angler
Get the latest factory image, don't worry about the OTA update.
Also get the unofficial TWRP recovery from here: http://forum.xda-developers.com/nexus-6p/general/recovery-twrp-3-0-2-3-unofficial-touch-t3516951
(2)
After you download the angler-factory-[blah-blah-blah].tar.xz file, decompress it somewhere convenient onto your computer where you also have the ADB and fastboot .exe's handy.
Inside this decompressed archive you will find another archive entitled image-angler-[some characters].zip. Again, decompress this zip file into your ADB folder and you will see a list of the following items:
Code:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
vendor.img
You should also see elsewhere in the main directory the following items:
Code:
bootloader-angler-angler-03.62.img
radio-angler-angler-03.78.img
Move these items into your ADB directory if you have not already done so.
(3)
Backup your Nexus 6P now with TWRP, and copy all of the archived backup items off of the phone onto your personal computer.
While still in TWRP, do the advanced wipe command and format the various partitions of your phone. Then power off.
(4)
Put your phone into fastboot mode by powering it off then holding the volume down button while powering on.
(5)
Open up your ADB command line console and type in "fastboot devices". You should see your phone serial number and "fastboot" next to it.
(6)
Following the lead by some of our intrepid developers here at this link:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
...We're going to flash these image files manually using fastboot.
Type in the following commands one at a time:
(7)
If you have not already done so, ensure that your bootloader and radio are up to the requisite versions:
Code:
fastboot flash bootloader bootloader-angler-angler-03.62.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-03.78.img
fastboot reboot-bootloader
(8)
Next we'll flash the main system files:
Code:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
(9)
I'm unclear as to whether or not it's necessary to flash the user data, but if you do, you will need to reflash TWRP afterwards and resize your data partition if you have the 64 GB or 128 GB models.
Code:
fastboot flash userdata C:/images/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
(10)
Optional:
The default install script will flash the recovery that came with COS. You may or may not need to do this.
Code:
fastboot flash recovery recovery.img
(11)
When done, reboot and enjoy.
Current limitations of CopperheadOS:
No built-in root capability.
Therefore, no ability to install backed up apps from Titanium Backup.
Therefore, no ability to do root-level ad blocking. (This must be done by other means which I will write up on soon.)
No Google apps, although FDroid is installed by default.
Apparently installing google apps goofs up OTA updates (I haven’t confirmed this yet)
Lock screen / bootup pattern is limited to 3x3. CyanogenMod and others give you the ability to do up to 6x6 patterns.
Automatic updates don’t seem to download properly. I see a notification that an update is available but it never seems to start the download.
TWRP recovery doesn’t seem to “stick”. It disappears upon reboot.
SuperSU doesn’t seem to flash properly with traditional TWRP zip install methods.
ROM size is rather large compared to CyanogenMod .
RAM usage seems to be higher than CyanogenMod , but this may be due to defenses against buffer overflows (apparently part of the defensive code borrowed from the ultra-secure OpenBSD.)
Frankly this entire ROM looks quite promising but it feels somewhat rough right now, it comes across as a work in progress.
If you’re in a position where you positively need the best possible security due to your occupation, this is the way to go. Everything is handled on the phone itself, Google is cut out of the loop, which is good, and you’re left with a bare-bones smartphone that will get you around safely and securely but not quite in the same style as cyanogen mod or another stripped-down of similar variety.
[RESERVED]
Nice write-up and review. Seems interesting.
Root access on CopperheadOS? Lol, no.
Sent from my LG-H831 using Tapatalk
ChongoDroid said:
Root access on CopperheadOS? Lol, no.
Click to expand...
Click to collapse
As mentioned in post #1, the fine folks at the Tor Project are working feverishly on a modified fork of Copperhead with more bells and whistles, namely root access, google, OrWall, Orbot, and maybe a few other bells and whistles.
Problem is it's still in development and the install process is even more convoluted. See here: https://blog.torproject.org/blog/mission-improbable-hardening-android-security-and-privacy
This would be a much better middle ground that I think we could get behind. It still feels somewhat "work-in-progress"-ish so we may need to wait a few months to easily and elegantly get going with something more secure that OEM android.
@ChongoDroid:
We are indeed staying frosty around here even though we aren't in Vancouver. It's still cold outside.
If you wanna use signal without play services then I'd suggest this https://play.google.com/store/apps/details?id=org.smssecure.smssecure
Sent from my LG-H831 using Tapatalk
CaptShaft said:
As mentioned in post #1, the fine folks at the Tor Project are working feverishly on a modified fork of Copperhead with more bells and whistles, namely root access, google, OrWall, Orbot, and maybe a few other bells and whistles.
Problem is it's still in development and the install process is even more convoluted. See here: https://blog.torproject.org/blog/mission-improbable-hardening-android-security-and-privacy
This would be a much better middle ground that I think we could get behind. It still feels somewhat "work-in-progress"-ish so we may need to wait a few months to easily and elegantly get going with something more secure that OEM android.
Click to expand...
Click to collapse
I've been using said "Mission Improbable" flavor of CopperheadOS for a few weeks now and it's working great for me. Have to admit though that I've been using this variant over the vanilla COS for Google Play services rather than the Tor implementations. Updating is a bit of a pain as you have to return to the Linux box for each and every OS update. But the advertised features do indeed work well. CopperheadOS itself leaves little to be desired, although I miss TWRP. While not as good Adaway in my experience, DNS66 eases the ad pain: https://f-droid.org/wiki/page/org.jak_linux.dns66
sicmatron said:
I've been using said "Mission Improbable" flavor of CopperheadOS for a few weeks now and it's working great for me. Have to admit though that I've been using this variant over the vanilla COS for Google Play services rather than the Tor implementations. Updating is a bit of a pain as you have to return to the Linux box for each and every OS update. But the advertised features do indeed work well. CopperheadOS itself leaves little to be desired, although I miss TWRP. While not as good Adaway in my experience, DNS66 eases the ad pain: https://f-droid.org/wiki/page/org.jak_linux.dns66
Click to expand...
Click to collapse
Mission Improbable looks very interesting. So can you install the Google Play Store easily then on it?
emacsomancer said:
Mission Improbable looks very interesting. So can you install the Google Play Store easily then on it?
Click to expand...
Click to collapse
When doing the Mission Improbable magic, Google Play Store and everything required for it is being baked into the OS. I don't understand the process nearly as much as I would like, my understanding is that the script package (Mission Improbable is nothing more than that really) takes the COS base, inserts OpenGapps, Orwall and Torbot and fixes the signatures accordingly.
sicmatron said:
When doing the Mission Improbable magic, Google Play Store and everything required for it is being baked into the OS. I don't understand the process nearly as much as I would like, my understanding is that the script package (Mission Improbable is nothing more than that really) takes the COS base, inserts OpenGapps, Orwall and Torbot and fixes the signatures accordingly.
Click to expand...
Click to collapse
That sounds excellent. I wonder if I can find a Nexus 6P (would have to be 128gb since no sdcard slot) at a reasonable price point after the holidays. I would really like to have a somewhat more secure mobile phone.
On a sidenote, it appears that something newer/faster than 6P isn't going to be supported by COS anytime soon:
The Pixel phones won't be supported without funding specifically for supporting them. Right now, we have no Pixel devices and no funding towards supporting them. There's no time available to do something like a proper crowdfunding campaign for this. We could post a kickstarter campaign with simply a goal without any rewards or a video... I doubt it would get funded, since we receive such a small amount via donations despite supporting a lot of different methods to donate. Going from 3 to 5 devices would be a huge increase in workload even after adding the initial support, and then we'd be expected to commit to supporting them for 3 years.
Click to expand...
Click to collapse
Maybe I'm just crazy but isn't the point of Copperhead to prevent complex/sophisticated attacks? I mean if you're just trying to keep out a thief or prying eyes of a significant other then having an encrypted (locked bootloader) 6p running the latest OS would be more than enough. So when the threat model get's bumped up (sophisticated hacker, state sponsored, etc) then stuff like PAX, hardened kernel etc can defend against complex attacks, even 0days. So if you need that kind of security, why in the hell would you need root? For an adblocker? Really?
Tor doesn't need root to work, just use the VPN feature.
I can see the need for Google Apps (all though if you're hiding from state sponsored hackers, using Google might not be a good idea.) so I am a little interested but anyways I'll never discourage others from development so ignore me, I'm just old school when it comes to security.
ChongoDroid said:
So when the threat model get's bumped up (sophisticated hacker, state sponsored, etc) then stuff like PAX, hardened kernel etc can defend against complex attacks, even 0days. So if you need that kind of security, why in the hell would you need root? For an adblocker? Really?
Click to expand...
Click to collapse
Or for running Titanium Backup to move your old apps + data and settings from the old phone onto the new one. It's an uphill battle with Google Play in the first place and Helium (or others) doesn't play well with Copperhead OS right now.
After data migration, Root could be thrown away and we'd be fine.
ChongoDroid said:
Tor doesn't need root to work, just use the VPN feature.
Click to expand...
Click to collapse
The folks over at tor point this out:
We require SuperUser and OrWall instead of using the VPN APIs because the Android VPN APIs are still not as reliable as a firewall in terms of preventing leaks. Without a firewall-based solution, the VPN can leak at boot, or if Orbot is killed or crashes. Additionally, DNS leaks outside of Tor still occur with the VPN APIs on some systems.
ChongoDroid said:
I can see the need for Google Apps (all though if you're hiding from state sponsored hackers, using Google might not be a good idea.) so I am a little interested but anyways I'll never discourage others from development so ignore me, I'm just old school when it comes to security.
Click to expand...
Click to collapse
I agree wholeheartedly. Google = jsut another backdoor for Big Brother spying via NSL's and the Mass Surveillance. I'm attempting to live without GP now, but some apps are behaving weirdly. And I have to manually sideload the apps from google after another update. FDroid is good but apps like Signal aren't' distributed or maintained through FDroid yet.
If there was some sort of backend where FDroid could process the GP app updates without direct connection to GP, that would be great.
To all interested: http://forum.xda-developers.com/general/rooting-roms/guide-hosts-based-adblocking-root-t3526537
Here I discuss a method of getting going with hosts-based adblocking minus root, and I did this specifically here on Copperhead. Enjoy!
Would adb backup work to replace helium? Tbh I haven't had it work on 7.0+ even with root reliably.
Sent from my LG-H831 using Tapatalk
---------- Post added at 10:22 PM ---------- Previous post was at 10:20 PM ----------
Hmm I'll look on https://ipleak.net to see if I'm getting leaks on VPN and I don't use tor but I'll check it out
Sent from my LG-H831 using Tapatalk
I just did a bunch of tests on a handful of browsers and even on the leakiest (chrome) browser I didn't get anything compromising. Maybe the bugs in the VPN APIs have been fixed because everything is kosher on my end.
Using Private Internet Access, AES-256, SHA256, RSA 4096. Make sure webrtc is blocked if you're using a different vpn app and use chrome.
Sent from my LG-H831 using Tapatalk
Im using copperhead os too and my only issue with it is that most of the good privacy apps , orwall and afwall , all require root. Obviously copperhead isnt rootable. Is there any other similar privacy based builds available?
Is there any instructions on how to install the Copperhead ROM? The instructions are not very descriptive on the copperhead site and the instruction here didn't work.
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.