[MOD] [TETHERING] Native Tethering Enable for 1.82.605.6 - HTC 10 Themes, Apps, and Mods

If all you want to do to your phone after obtaining s-off with SunShine and flashing TWRP is to have native tethering enabled, then this mod is for you. Simply download to your phone storage and flash via TWRP. The only thing this mod does is to flash a copy of default.xml with the modifications required to enable native tethering.
NOTE: This is specifically for the latest firmware, version 1.82.605.6. If you're not on that version, check out this thread to update your firmware.

pastorbennett said:
If all you want to do to your phone after obtaining s-off with SunShine and flashing TWRP is to have native tethering enabled, then this mod is for you. Simply download to your phone storage and flash via TWRP. The only thing this mod does is to flash a copy of default.xml with the modifications required to enable native tethering.
NOTE: This is specifically for the latest firmware, version 1.82.605.6. If you're not on that version, check out this thread to update your firmware.
Click to expand...
Click to collapse
Does this work for all variants? Sprint? Verizon?

tabp0le said:
Does this work for all variants? Sprint? Verizon?
Click to expand...
Click to collapse
Doubtful, as I'm pretty certain default.xml is carrier specific. It likely would work on other builds, but you'd be risking a soft brick if you flashed this on a phone for a different carrier.
It's quite easy to make your own. First, use a file manager to copy the default.xml file from /system/customize/ACC to the sd card, copy the file to your computer, make the necessary edits to the file, (follow part 1 of this post) and use a tool like muCommander to open the patch that I posted and inject your newly edited default.xml. Make sure once you copy your file over the one included in my patch that you change the permissions to 644.
If that's beyond your skills, post your default.xml and I'll make the patch for you when I have the time.

pastorbennett said:
Doubtful, as I'm pretty certain default.xml is carrier specific. It likely would work on other builds, but you'd be risking a soft brick if you flashed this on a phone for a different carrier.
It's quite easy to make your own. First, use a file manager to copy the default.xml file from /system/customize/ACC to the sd card, copy the file to your computer, make the necessary edits to the file, (follow part 1 of this post) and use a tool like muCommander to open the patch that I posted and inject your newly edited default.xml. Make sure once you copy your file over the one included in my patch that you change the permissions to 644.
If that's beyond your skills, post your default.xml and I'll make the patch for you when I have the time.
Click to expand...
Click to collapse
Great! I can do it, thank you!

theres a Verizon HTC 10 forum, this would of been better posted there

afuller42 said:
theres a Verizon HTC 10 forum, this would of been better posted there
Click to expand...
Click to collapse
This subforum is linked from there. It's all good. And hello, fellow Minnesotan!

pastorbennett said:
This subforum is linked from there. It's all good. And hello, fellow Minnesotan!
Click to expand...
Click to collapse
Gotcha. Didn't know that.
And hello, ready for the long winter this year? It's coming up real fast. Faster than I would like.

afuller42 said:
Gotcha. Didn't know that.
And hello, ready for the long winter this year? It's coming up real fast. Faster than I would like.
Click to expand...
Click to collapse
Sounds like it's going to be a very white winter. But I'm cool with it. I'm a bit of an optimist when it comes to winter: it's the season when all the bugs die. BTW, I'm located roughly 25 miles SW of Mankato, literally in the middle of nowhere.

Related

[SYSTEM_DUMP] True Stock up to JH7

The last time I looked, the only dump for the Captivate on xda was a JF6 version, posted a few weeks ago, and the OP had taken out a few AT&T apps prior to doing it, making it not a true stock. This morning I decided to rip out the content out of the factoryrfs.rfs files from each of the three firmwares we have. I am planning to poke around in these a bit and try my hand at some deodexing, but I have also uploaded them for anyone else to play with them, or to restore any files they might have inadvertently deleted:
Here are the links:
JF6
JH2
JH3
JH7
rajendra82 said:
The last time I looked, the only dump for the Captivate on xda was a JF6 version, posted a few weeks ago, and the OP had taken out a few AT&T apps prior to doing it, making it not a true stock. This morning I decided to rip out the content out of the factoryrfs.rfs files from each of the three firmwares we have. I am planning to poke around in these a bit and try my hand at some deodexing, but I have also uploaded them for anyone else to play with them, or to restore any files they might have inadvertantly deleted:
Here are the links:
JF6
JH2
JH3
Click to expand...
Click to collapse
What do JF and JH stand for?
freedonkey said:
What do JF and JH stand for?
Click to expand...
Click to collapse
They relate to the month in which they were built. F means june, h is august. Both of the jh roms are test roms and unfinished, but functional and snappier than the stock jf6 rom.
Sent from my Samsung SGH-i987
Thanks for this.
Aye... Thanx for the system dumps.
Anyone seen these for the i9000?
alphadog00 said:
Anyone seen these for the i9000?
Click to expand...
Click to collapse
Easy to get the files out yourself. Extract the factoryrfs.rfs file out of the firmware tar file, boot into linux and do:
sudo mount -o loop factoryrfs.rfs <any_directory_of_your_choice>
Then copy the files from the mounted location to another, and you have the raw system dump.
Pardon my ignorance but what do these dumps do/provide? How are they different from the firmware from Samsung Firmware?
glio1337 said:
Pardon my ignorance but what do these dumps do/provide? How are they different from the firmware from Samsung Firmware?
Click to expand...
Click to collapse
The firmware from Samsung Firmware contains the applications and default configuration settings packed into a factoryrfs.rfs (which itself is then inside a .tar file). That format is suitable for Odin to flash onto the phone, but you can't access the individual files inside the .rfs. What I did was to unpack the .rfs file, so that the individual files inside are available for whatever you want to do with them. These are not suitable for flashing on the phone as a whole, but someone could take something, modify it and push it to their phone, or make a custom ROM out of it. A simple example is the circle battery indicator mod, where someone modified the framework-res.apk to show percentage, and then made a custom ROM update.zip with it. Without access to the original file, this would not have been possible. Everyone has these files on the phone in one version or another (unless they manually edit or delete them). I just wanted all versions of the files ever released or leaked.
I dont know if this is the place to ask but how we can extract particular app to be able to install it as .apk
here is what i need
http://forum.xda-developers.com/showthread.php?t=776739
zagorka said:
I dont know if this is the place to ask but how we can extract particular app to be able to install it as .apk
here is what i need
http://forum.xda-developers.com/showthread.php?t=776739
Click to expand...
Click to collapse
All the apks are inside the zip files, stored the same way they would normally reside on your phone. I am pretty sure the stock Clock widget is a touchwiz widget, and will not work on your wife's Aria. Hell it won't even work on our own phone if you switch to a different launcher.
rajendra82 said:
All the apks are inside the zip files, stored the same way they would normally reside on your phone. I am pretty sure the stock Clock widget is a touchwiz widget, and will not work on your wife's Aria. Hell it won't even work on our own phone if you switch to a different launcher.
Click to expand...
Click to collapse
I am talking about ClockPackage not SamsungWidget_CalendarClock or SamsungWidget_StockClock. It's the one in applications not the widgets.
zagorka said:
I am talking about ClockPackage not SamsungWidget_CalendarClock or SamsungWidget_StockClock. It's the one in applications not the widgets.
Click to expand...
Click to collapse
Clockpackage is in the zip files. Here is the JH3 version for you. Not sure if it'll install. When I try to push to the Android 2.1 Emulator, I get:
adb install ClockPackage.apk
1404 KB/s (0 bytes in 2921292.002s)
pkg: /data/local/tmp/ClockPackage.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Which tells me that the package is probably dependant on TouchWiz 3.0 or some other library already installed on the phone.
rajendra82 said:
Clockpackage is in the zip files. Here is the JH3 version for you. Not sure if it'll install. When I try to push to the Android 2.1 Emulator, I get:
adb install ClockPackage.apk
1404 KB/s (0 bytes in 2921292.002s)
pkg: /data/local/tmp/ClockPackage.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Which tells me that the package is probably dependant on TouchWiz 3.0 or some other library already installed on the phone.
Click to expand...
Click to collapse
Yes, I was able to extract the .apk and .odex files but couldnt install them.
Probably you are right it is too much trouble. I'll look for some alternative.
Thank you
I think he zipaligned the system apk's too
designgears said:
I think he zipaligned the system apk's too
Click to expand...
Click to collapse
I am very new to android, so I am not sure of the implications of this. After further investigation, there is a newer version of the bat files (Auto_Deodexer_2.3), but that version does not do any zipaligning. I added my own bat file to do this after the deodexing, but is what the older version did (zip align every apk in the app directory) bad, and why? If that is the case, which of the apk files should I not zipalign?
On a similar note, the newer bat file asks me to give a bootclasspath. When I give it the values in the init.rc, it skipped deodexing few of the apks in the app directory. When I added twframework.jar to the bootclasspath ahead of framework.jar, it skipped fewer files. I am sure that the older version was buggy, and made mistakes. What should the proper bootclasspath be to not skip deodexing the following files, and to properly deodex the others:
BluetoothOPP.apk+odex
Camera.apk.odex
FactoryTest.apk+odex
MiniDIary.apk+odex
TouchwizCalendar.apk+odex
Figured out the bootclasspath to use. OP and the JH3 file updated. If you downloaded the deodexed JH3 version yesterday, please replace it with the newer version.
What exactly does deodexing and zipaligning do? I understand it makes it faster but how so?
Sent from my SAMSUNG-SGH-I897 using XDA App
frenchtoasted said:
What exactly does deodexing and zipaligning do? I understand it makes it faster but how so?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
All this is highly theoretical knowlege on my part, so if anyone has better information, feel free to correct me:
Deodexing:
Some of the apks and jar files on the default stock ROM have their code split between apk/odex and jar/odex pairs instead of in a single file. This is done by the developers to supposedly save space, and memory usuage, and to speed up the booting process. Unforunately having separate odex files means that replacing any part of the whole system is much harder. Deodexing the ROM puts the code from the odex files back into the apk and jar files so that every application and jar is self contained and could be replaced with an equivalent.
Zipaligning:
Zipaligning is an optimization of apk files to align all uncompressed data within them on 4-byte boundaries to reduce the memory usage. Since deodexing rebuilt the apks with the code from the odex files, they would have become unaligned. I realigned them to make them optimized again.
This is not necessarily a performance tweak at first, but once you are able to replace the slower parts of the system as a result of it, you should start to get more benefits out of it.
would it be possible to get the allshare package from the deodexed rom? will it work with any other device?

[GUIDE] Changing your bootanimation and delete those ugly sound

*EDITED*
This is very easy now after having the permanent ROOT -- thanks to PAUL for wonderful Visionary+, Evostance for brilliant guide, and those geniuses who make this happened (you know who )
First you need to get permanent root. Here is the link to the guide:
http://forum.xda-developers.com/showthread.php?t=834427
(If you read till page 10, you will definitely know how to do it and what to expect).
Second, go buy ROOT EXPLORER from the market. (Best explorer for rooted phone period).
Go to /system/customize/resource
Make sure you enable the r/w (read write option), other wise you cant do modification.
You will see both the audio and bootanimation there.
If you hated that sound (just like me), just delete the audio.mp3. If you want to change the bootanimation, just copy your bootnimation.zip to overwrite the default one.
That's all....reboot the phone....and you will have your peace...and enjoy the new bootanimation.
kuailan said:
I am just wondering is the good old way of adb pushing the bootanimation.zip work for HD? I do noticed the stock animation are located in /customize/resource folder in the system ROM. Has anyone try changing the bootanimation? Just hated those sound in bootup (prefer no sound).
Click to expand...
Click to collapse
firstly i'd like to state, this is development and not Q & A not being mean just stating.
secondly if you had read the ref guide which is pinned to the top you might have got your answer.
finally your answer...
NO
you can not write on the nand with the temp root. no can you adb push.
permanent root is on its way and i believe the nand will be unlocked on that so you may have write permissions. once this has been obtained then you can push a custom boot animation if required.
El_Nino9 said:
firstly i'd like to state, this is development and not Q & A not being mean just stating.
secondly if you had read the ref guide which is pinned to the top you might have got your answer.
finally your answer...
NO
you can not write on the nand with the temp root. no can you adb push.
permanent root is on its way and i believe the nand will be unlocked on that so you may have write permissions. once this has been obtained then you can push a custom boot animation if required.
Click to expand...
Click to collapse
First of all thank you for the answer (actually I also thought so, and your answer just confirmed that)
And as for posting in develeopment, I DO believe that changing bootanimation is part of Android development (anything that involved creating/modifying and changing of the default system files). Just like recovery or flashing tools, people also develop bootanimation changer application to make life easier for others.
Also I did some search, and this is the first post for any bootanimation for Desire HD. I hope once "root" has been accomplished. People can just use this thread to put the guide to changing those animation.
Therefore I do read and follow the guidelines.
-----------------edited---------------------
kuailan said:
First of all thank you for the answer (actually I also thought so, and your answer just confirmed that)
And as for posting in develeopment, I DO believe that changing bootanimation is part of Android development (anything that involved creating/modifying and changing of the default system files). Just like recovery or flashing tools, people also develop bootanimation changer application to make life easier for others.
Also I did some search, and this is the first post for any bootanimation for Desire HD. I hope once "root" has been accomplished. People can just use this thread to put the guide to changing those animation.
Therefore I do read and follow the guidelines.
Click to expand...
Click to collapse
well glad you're a happy bunny
but several things,it isn't development as you were asking a question at time of writing.
secondly themes section deals with bootanimation and things like that. sound can be disabled by just renaming the file i.e. add a .bak after mp3 just for back up purpose or you can delete the file entirely up to the user.
with customs roms, they may be in a different location. i do believe that AOSP builds are located in media where as in sense builds /customize/resource
it can change depending on the developers choice really. thats why when a person releases a theme, it states what rom the user must be using to avoid problems.
anyways there's no need to carry on with that as you have got what you wanted, full root so you can do w.e. you like know
my personal favourite boot animation was the original hero one, but since that doesnt work anymore/havent found 1 that has been converted to work with the new roms, i like "making fro-yo" it just draws a pic of a frozen yoghert and colours it in.
I purchased Bootanimation changer by Andres Schomis a while back when I was still using the original Desire. There are quite a few nice and interesting ones there. My fav so far is the pissing droid (to piss off some of my iphone mate ) and the alienware. I am sure they are also available in this forum (just do a search). There is no option for desire HD yet, but seem like the one that work for Desire also work just fine in HD. To make the app work, you will need to set the custom path. I highly recommend that app for bootanimation.
Somehow I feel this thread should be in the Themes/Apps subforum instead Since it basically has to do with customization. Anyway, thanks a lot for the instructions.
phunkycow said:
Somehow I feel this thread should be in the Themes/Apps subforum instead Since it basically has to do with customization. Anyway, thanks a lot for the instructions.
Click to expand...
Click to collapse
Agreed with you there mate
I do like the instructions, always helpful for those not browsing the development threads (which do take up a lot of reading time )
Ok can some one tell me what i'm i doing wrong?? it's been more then 6 hours since I started working on this.
Here is my anamtion
Download me please
I cant figure out whats wrong with it....
I even saved it as store with winrar even tried copying the files inside the HTC stock zip and still same problem
can someone help me please?
Bump any one can help?
Just delete the bootanimation.zip inside the /system/customize/resource
Then just copy your animation to the same path /system/customize/resource.
Make sure your animation is also named bootanimation.zip
For some reason I'm not able to enable the r/w function in the resource folder. The only place I can do it is in the root directory (with system, sdcard etc). Any idea of why this is happening? (my phone is perma-rooted and I have granted Super user permissions).
kuailan said:
Just delete the bootanimation.zip inside the /system/customize/resource
Then just copy your animation to the same path /system/customize/resource.
Make sure your animation is also named bootanimation.zip
Click to expand...
Click to collapse
I did my animation that made with Photoshop dont work any idea why? any other animation works fine
Sylpher said:
For some reason I'm not able to enable the r/w function in the resource folder. The only place I can do it is in the root directory (with system, sdcard etc). Any idea of why this is happening? (my phone is perma-rooted and I have granted Super user permissions).
Click to expand...
Click to collapse
This drove me mad for a while too.
I uninstalled root explorer then re-installed and I could the select r/w for all folders.
hi
do i need s-off for this or is just permanent root enough??
thnx
anyone got any good animation zips and sounds?
combat goofwing said:
anyone got any good animation zips and sounds?
Click to expand...
Click to collapse
yeah, thats what i wanna know too
Does anyone know what would happen if you removed the boot animation entirely? Will the phone still boot ok?
I'm happy not to have one at all if it speeds things up
Guys
first I didn't find the bootanimation in system ressource i found it in data/local/
along with the android-audio.mp3
second I tried to change these file it worked but the animation doesn't show up and I have just a small android when I boot up
What can I do ?
PS : my file may be too big 27 megabite for the bootanimation.zip
I tried already, but why whenever I reboot, the bootanimation.zip would revert to the original one?

KitKat Write to ext_sd FIX | DOWNLOAD NOW

KitKat Write to ext_sd FIX
Sometimes when you edit the build.prop and restart your phone, the changes you have made in the build.prop are gone.
This zip must be flashed through recovery, custom recovery of course.
After flashing this, your apps will be able to read/write on external memory. Apps like Titanium Backup for example, or any app that needs to read/write the external memory of the device.
For example in Titanium Backup you can set your external memory as the default storage for backups, this way saving some internal memory.
INSTRUCTIONS
Put the zip on your sdcard
Go to recovery
Click Install
Choose /external_sd
Click on KitKat Write to ext_sd FIX
Swipe to confirm Flash
These instructions are for TWRP recovery, but in CWM it's pretty much the same.
Thanks to @TEKHD for making this for SAMSUNG devices.
I just ported this to HTC and modified the platform.xml
Should work on both stock and custom rooted ROM's.
NO S-OFF required.
WARNING :
I am not responsible for any damage to your device while installing this, proceed at your own risk.
This zip was tested on a HTC ONE M8 device.
Dev-Host Download link
KitKat Write to ext_sd FIX
Download link soon....what is soon ? Why open a thread without a link. Why not wait until you got an actual file to share ?
I find that so weird......and useless
Mr Hofs said:
Download link soon....what is soon ? Why open a thread without a link. Why not wait until you got an actual file to share ?
I find that so weird......and useless
Click to expand...
Click to collapse
Ok, delete it if you want. The link will be up in a few hours. Do what you want.
EDIT : The file is up for download in the first post.
Do what i want......yeah thought it was the opposite way haha
I won't delete it, but good for you that you got the link up. As you probably have read in the xda rules that so called "placeholders" are not very welcome
Cheers.
Mr Hofs said:
Do what i want......yeah thought it was the opposite way haha
I won't delete it, but good for you that you got the link up. As you probably have read in the xda rules that so called "placeholders" are not very welcome
Cheers.
Click to expand...
Click to collapse
Yes, I know the XDA rules, and I understand your point of view.
No ''placeholders'' here
GRAPHIKXS said:
KitKat Write to ext_sd FIX
Sometimes when you edit the build.prop and restart your phone, the changes you have made in the build.prop are gone.
This zip must be flashed through recovery, custom recovery of course.
After flashing this, your apps will be able to read/write on external memory. Apps like Titanium Backup for example, or any app that needs to read/write the external memory of the device.
For example in Titanium Backup you can set your external memory as the default storage for backups, this way saving some internal memory.
INSTRUCTIONS
Put the zip on your sdcard
Go to recovery
Click Install
Choose /external_sd
Click on KitKat Write to ext_sd FIX
Swipe to confirm Flash
These instructions are for TWRP recovery, but in CWM it's pretty much the same.
Thanks to @TEKHD for making this for SAMSUNG devices.
I just ported this to HTC and modified the platform.xml
Should work on both stock and custom rooted ROM's.
NO S-OFF required.
WARNING :
I am not responsible for any damage to your device while installing this, proceed at your own risk.
This zip was tested on a HTC ONE M8 device.
Dev-Host Download link
KitKat Write to ext_sd FIX
Click to expand...
Click to collapse
You should add info that You are not the one who tested it first even, xseroboy - that's what you should have in your profile. You better write step by step tutorial, as it will take less time to change the file by hand, than it will take to flash the file.... or should I say, copy it from the original?
Garrett_PL said:
You should add info that You are not the one who tested it first even, xseroboy - that's what you should have in your profile. You better write step by step tutorial, as it will take less time to change the file by hand, than it will take to flash the file.... or should I say, copy it from the original?
Click to expand...
Click to collapse
Say what?
GRAPHIKXS said:
Say what?
What step by step tutorial man, are you crazy?
I've flashed this and it's all good, the tutorial is more then enough, or you are an idiot?
Click to expand...
Click to collapse
Taking our little misunderstanding yesterday, i must say that you come in pretty strong (hostile)....calling people crazy....and an idiot. I would strongly yet kindly suggest that you consider your your words as it's not the other party here calling you any names.
You kinda did the same to me
Cheers
mateenf said:
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart.
Click to expand...
Click to collapse
Relax, and see above.
Mr Hofs said:
Taking our little misunderstanding yesterday, i must say that you come in pretty strong (hostile)....calling people crazy....and an idiot. I would strongly yet kindly suggest that you consider your your words as it's not the other party here calling you any names.
You kinda did the same to me
Cheers
Click to expand...
Click to collapse
OKI DOKI
Garrett_PL said:
Relax, and see above.
Click to expand...
Click to collapse
Ok, I don't see where it says : xseroboy.
If you show me a thread where it says that he create this, I'll thank him too.
And another thing. THE ARE ALL THE INSTRUCTION YOU/ALL NEED.
Just flash it.
No need for editing anything else, this was flashed by me on my own HTC ONE M8 by flashing it without any problems.
Thank you thank you thank you thank you thank you....

[Q] Please help, can someone export the /vendor/ folder?

Hi guys!
I had an Essential phone before, but switch to a Pixel 2 XL. VoLTE was working before, but not anymore. So I started digging to get the VoLTE working with a bypass. I need someone to make an export of the /vendor/ folder, where certain .mbn files are stored. They contain certain provider related data which may get VoLTE working, in my case for a dutch provider.
So if you are rooted you could help me out!
Using any root explorer, copy the /vendor/ from the root to your sd card. Zip this folder and upload it to a Google Drive or something. Much obliged!
Thanks alot!
trantium said:
Hi guys!
I had an Essential phone before, but switch to a Pixel 2 XL. VoLTE was working before, but not anymore. So I started digging to get the VoLTE working with a bypass. I need someone to make an export of the /vendor/ folder, where certain .mbn files are stored. They contain certain provider related data which may get VoLTE working, in my case for a dutch provider.
So if you are rooted you could help me out!
Using any root explorer, copy the /vendor/ from the root to your sd card. Zip this folder and upload it to a Google Drive or something. Much obliged!
Thanks alot!
Click to expand...
Click to collapse
Or you could download the fastboot images from Essential?
rignfool said:
Or you could download the fastboot images from Essential?
Click to expand...
Click to collapse
Believe me, I tried. The vendor folder (I think) gets populated once the Essential has been powered on once. I extracted literally everything I could to find these .mbn files. No luck.
trantium said:
Believe me, I tried. The vendor folder (I think) gets populated once the Essential has been powered on once. I extracted literally everything I could to find these .mbn files. No luck.
Click to expand...
Click to collapse
gimme a sec, ill up it, also what vendor month?
aer0zer0 said:
gimme a sec, ill up it, also what vendor month?
Click to expand...
Click to collapse
No more bricks... Ok?
I doubt you'll buy a 3rd phone :silly:
rignfool said:
No more bricks... Ok?
I doubt you'll buy a 3rd phone :silly:
Click to expand...
Click to collapse
Lol,I completely forgot. I have the images broke down in kitchen. I just wanna know which version? Sept?
aer0zer0 said:
Lol,I completely forgot. I have the images broke down in kitchen. I just wanna know which version? Sept?
Click to expand...
Click to collapse
September is fine! It doesn't matter really
https://www.androidfilehost.com/?fid=1322778262904007292
all yours @trantium
aer0zer0 said:
https://www.androidfilehost.com/?fid=1322778262904007292
all yours @trantium
Click to expand...
Click to collapse
Thanks alot mate!
aer0zer0 said:
https://www.androidfilehost.com/?fid=1322778262904007292
all yours @trantium
Click to expand...
Click to collapse
Ah damn it, the mbn folder is not there. I guess it gets generated once the device has been booted once.
Do you have any idea where I can find the mcfg_sw.mbn file? :fingers-crossed:
trantium said:
Ah damn it, the mbn folder is not there. I guess it gets generated once the device has been booted once.
Do you have any idea where I can find the mcfg_sw.mbn file? :fingers-crossed:
Click to expand...
Click to collapse
Mbn file isn't something you would find there. Mbn is an image file for low level flashing in fast boot.
aer0zer0 said:
Mbn file isn't something you would find there. Mbn is an image file for low level flashing in fast boot.
Click to expand...
Click to collapse
That is weird, then how does Essential get their mcfg_sw.mbn files for its lte network configuration? In a Pixel, there is a /vendor/mbn/mcfg/* folder containing provider configurations from almost all providers in the world.
trantium said:
That is weird, then how does Essential get their mcfg_sw.mbn files for its lte network configuration? In a Pixel, there is a /vendor/mbn/mcfg/* folder containing provider configurations from almost all providers in the world.
Click to expand...
Click to collapse
No idea, I don't see anything like that in vendor. @jacksummers thoughts
aer0zer0 said:
Mbn file isn't something you would find there. Mbn is an image file for low level flashing in fast boot.
Click to expand...
Click to collapse
aer0zer0 said:
No idea, I don't see anything like that in vendor. @jacksummers thoughts
Click to expand...
Click to collapse
It doesn't either in the Pixel, but after flashing and booting for or inserting a sim card for the first time makes it appear.
I don't know how this is possible, are you able to make a .mbn search inside other folders?
Since it's system-as-root I just wildcarded .mbn, nothing
aer0zer0 said:
No idea, I don't see anything like that in vendor. @jacksummers thoughts
Click to expand...
Click to collapse
Essential uses a compatibility matrix. Xml for a lot of the network stuff as far as i know and embedded deep in what we would call the device tree.so with the compatibility matrix they set the bools and its just true or false. Oh and in the manifest.. with each vendor img it seems they are simplifying it too, so probably the thing u are referencing is in there just as something else. Theres always a multitude of ways to hardcode something. If it was me i would hardcode it in the device tree source files and set it with bools. It allows for easy changes. And easier readability.
jacksummers said:
Essential uses a compatibility matrix. Xml for a lot of the network stuff as far as i know and embedded deep in what we would call the device tree.so with the compatibility matrix they set the bools and its just true or false. Oh and in the manifest.. with each vendor img it seems they are simplifying it too, so probably the thing u are referencing is in there just as something else. Theres always a multitude of ways to hardcode something. If it was me i would hardcode it in the device tree source files and set it with bools. It allows for easy changes. And easier readability.
Click to expand...
Click to collapse
Thanks for the explaination. An example .mbn file can be found here: http://www.renovate-ice.com/svn/leedroid-11/trunk/system/vendor/mbn/mcfg/configs/mcfg_sw/generic/
Just browse inside the folders and you will bump to a mcfg_sw.mbn file eventually.
Any idea how to get something like this from the Essential?

Houston, I have a problem.

Okay, like a smart person I went and deleted the build.props file in the systems folder. I wish I could explain, but I was trying to delete something else, and I guess I deleted the wrong file. I did not make any backups. (I did make a backup; but I never moved it the the sd card.) Now, the question is can someone just upload that same file, and will my rom be saved? (Using Qfil)
I wish I can help you but my LG V35 is bootloader locked and non-rooted
There you go. I added a txt extension because the app wasn't allowing me to upload it otherwise.
I have a bootloader unlocked, rooted v35 with an unmodified (to my knowledge) build.props file. I rarely ever need to modify that file on any rooted device and don't know if this is all you need, but here it is. ( I am on Android 8 ULM)
rpgdev said:
There you go. I added a txt extension because the app wasn't allowing me to upload it otherwise.
Click to expand...
Click to collapse
Thank you! You are a freaking lifesaver!

Categories

Resources