How to dump a phone - Touch CDMA General

Say I have a phone that is running android. How would I go about and dumping the system files so I could make my own builds with.

crackeyes said:
Say I have a phone that is running android. How would I go about and dumping the system files so I could make my own builds with.
Click to expand...
Click to collapse
adb pull /system ./desktop

Thanks
I was able to dump said files now how do you create a NBH or a SQSH file. If you can just point me to directions i can figure it out.

crackeyes said:
I was able to dump said files now how do you create a NBH or a SQSH file. If you can just point me to directions i can figure it out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=595131
Right there in the first post I believe

Related

NASCAR Sprint Cup Mobile for Mogul Working

Hello All,
I found this on another board for my friend who is a BIG NASCAR fan and got it to work on her Mogul by following the included instructions. I have tested and it is working. The final test will be during this weekends race. Keep in mind that it's a Java App and you will need Java installed. The stylis isn't used, you have to use the arrow keys to control.
Enjoy, I will try to support it any way I can, but no promises.
http://rapidshare.com/files/116171004/NASCAR_Sprint_Cup_Mobile.zip
i dont have a windows folder on my mogul?
never mind, I found it...it was hidden
confirmed, this is working on my mogul also!!!! awesome I have been waiting for this!
Can someone make a cab file for this application
I installed this on mt VZW xv6800 and it works great. I probably cant get the subscription stuff being on VZW but i will test the rest of it on race day.
sliverr7x said:
Can someone make a cab file for this application
Click to expand...
Click to collapse
I don't think this is possible because of the procedure to get it working. A cab file cannot determine what the file name of the file created is, (At least as far as I know).
i must have done something wrong. I followed the instructions correctly I thought.
Using the second set of files that Brett posted I was able to get it to work and I'm not even a sprint customer. Here is what I did:
1. Copied the following files from Brett's zip file into the \Windows\Appdb\ directory. s40__d0.db,s40__d1.db,s40__d2.db,s40_suite.jar,s40 _suite.utf.
Click to expand...
Click to collapse
I had no appdb directory, so I created one, then copied all 5 files into it. I didnt however copy the bin directory over, since it didnt mention that....
I also tried copying with the folder and running things from inside the folder....
Excluding the above files make a note of the highest set of numbered files that starts with an s.
Click to expand...
Click to collapse
I had no files in there.....
2. Using my phones file explorer I browsed to \windows\appdb and opened s40_suite.jar.
3. I went through the normal install steps and received the same error that everyone did.
4. Closed java.
Click to expand...
Click to collapse
that worked fine, java ran, but it never got to an error. Just a white screen with exit and pause on the soft keys.
5. On your phone browse to the \windows\appdb\ folder.
6. There should be 2 new .jar and .utf files that that start with 's' and are one number higher then the number you made a note of earlier.
Click to expand...
Click to collapse
there were a bunch of s0 fies
7. On you PC rename all 5 files by replacing the 40 in each file's name with the number of the new file that was created.
Click to expand...
Click to collapse
went back to the original files from the zip file and renamed them all to s0
8. Copy all 5 files to \windows\appdb
Click to expand...
Click to collapse
copied everything back over and overwrote whatever files it asked to
9. Open java and launch app.
Click to expand...
Click to collapse
Went back to Resco and ran the s0 jar file that I had just copied back over.
No good. I get a 955 error
corey113888 said:
I installed this on mt VZW xv6800 and it works great. I probably cant get the subscription stuff being on VZW but i will test the rest of it on race day.
Click to expand...
Click to collapse
Capture some videos please. I wanna see 'em.

can anyone teach us how to cook an android rom?

just like what the title said,i think if any one can teach us how to cook an android rom thats will be good,then we can make our own rom.i dont really like the rom that we has right now(i dont mean the roms are not good,im very want to thanks the Acookers,those rom just changed too much base on the offical roms,i want a rom that has almost the same as the official rom with sense..)
ok,i found the android kitchen for the hd2,the download link is here http://www.megaupload.com/?d=EK281AVK , the original thread is here http://forum.xda-developers.com/showthread.php?t=738770 big thanks to the author
+1 for that
yea me too
wish someone would make a complete tutorial showing how to do it and explain every concept for noobs
first you need a good knowledge with linux os if not .... no hope
lol this is such wishful thinking. i'm a noob like yall and would love to give back to the modding community that's provided so much for me. but unfortunately, making a tutorial of this would be near impossible. or really hard at least. you can't put into a tutorial, as someone mentioned, a firm understanding of linux os. that's just too much information to try to shove into a tutorial.
but if this does happen, i'll happily eat me words because i'd love to be able to cook up some roms.
Not sure how to cook roms really, there's Coffe Shop v1 but the system.ext2 always comes up with 195MB from a 119MB image, and wouldn't boot, and the developer disappeared and hasn't updated it in a while.
Sent from my HDROID2 using XDA App
tarekkkkk said:
first you need a good knowledge with linux os if not .... no hope
Click to expand...
Click to collapse
i dont think so,just like cooking a wm rom,you dont have to know very deeply of the ce or wm,all you need is replace things,its just easy if some on tell you how.....but maybe im wrong....
There are android kitchens available on the site here... just search for it as I don't have a link to it at the moment...
It's not as easy as cooking for WinMo and it won't always boot but you can sure cook
pongster said:
There are android kitchens available on the site here... just search for it as I don't have a link to it at the moment...
It's not as easy as cooking for WinMo and it won't always boot but you can sure cook
Click to expand...
Click to collapse
whats the key word?is it for hd2?thanks
weixiong said:
whats the key word?is it for hd2?thanks
Click to expand...
Click to collapse
search android kitchen.. no its for android not hd2... but you can use it to get results...
any news
+1
any news
look up coffee shop you could of searched first and found this without starting a new thread
you don't need to be an expert in linux, but at least have the basics. If you wana start, let me know, PM me or something. I'll try to help any way I can... I'm no expert as well, tho...
for some recent roms, they all use standdard ext2 image, it's better you work it on linux,
on linux you can mount the rootfs.img data.img, system.ext2 image to linux, then you can easily to copy & paste it.
and you'd know how android & linux boot up by adding & edition those boot config file.
and hd2 android is not standard rom like other cellphone's, hd2 rom don't need to pack into a single file, this is more easy for edition. and everyone can split the rom into several files.
few files information:
system.ex2 will be mount as /system, where android files located
data.img will be mount as /data, where user data located
initrd.gz, linux boot from here.
rootfs.img in some roms, the initrd.gz boot up will load this file, and mount this file as /, and main boot files are here. if you don't have this file, the main boot config files are in initrd.gz.
I am not guru, just tell what I know.
thanks.
Somebody should my a video of this
qingcai said:
for some recent roms, they all use standdard ext2 image, it's better you work it on linux,
on linux you can mount the rootfs.img data.img, system.ext2 image to linux, then you can easily to copy & paste it.
and you'd know how android & linux boot up by adding & edition those boot config file.
and hd2 android is not standard rom like other cellphone's, hd2 rom don't need to pack into a single file, this is more easy for edition. and everyone can split the rom into several files.
few files information:
system.ex2 will be mount as /system, where android files located
data.img will be mount as /data, where user data located
initrd.gz, linux boot from here.
rootfs.img in some roms, the initrd.gz boot up will load this file, and mount this file as /, and main boot files are here. if you don't have this file, the main boot config files are in initrd.gz.
I am not guru, just tell what I know.
thanks.
Click to expand...
Click to collapse
Thanks a lot!

Building [ROM ZIP] From NAND (Lets Talk)

Okay, as I am sure we all see there has been a HUGE break through for our HD2 freedom thanks to all the Dev's here with the release of ClockWork Mod Recovery. I can for see a downpour of one particlular question flooding the forums... "Can you make a ROM ZIP Please".
I would assume that it can't be that much of a task to take a NAND build and make it flashable (Maybe I am wrong) but it seems all the hard stuff of creation is done, it becomes a matter of "format" (Maybe Not the Right Word). Extract Boot and System.IMG's, Editing a script?
So... Maybe we can all take the burden off some of the Devs doing this to our favorite builds? Then they can focus on what they do best... making this stuff work.
What is involved in doing this?
Hell, maybe I am way off and we should leave it to the Pro's?
I'm Ready.
DroidTh3ory said:
Okay, as I am sure we all see there has been a HUGE break through for our HD2 freedom thanks to all the Dev's here with the release of ClockWork Mod Recovery. I can for see a downpour of one particlular question flooding the forums... "Can you make a ROM ZIP Please".
I would assume that it can't be that much of a task to take a NAND build and make it flashable (Maybe I am wrong) but it seems all the hard stuff of creation is done, it becomes a matter of "format" (Maybe Not the Right Word). Extract Boot and System.IMG's, Editing a script?
So... Maybe we can all take the burden off some of the Devs doing this to our favorite builds? Then they can focus on what they do best... making this stuff work.
What is involved in doing this?
Hell, maybe I am way off and we should leave it to the Pro's?
I'm Ready.
Click to expand...
Click to collapse
I would have to agree. I'm not much of a developer but I can follow directions pretty good. I would come on board and like DroidTh3ory said, take some of the burden off some of the Devs.
I would also like to a see a Nandroid (backup of nand to sd) type option so as if the new rom we flashed is not what we were hoping we can roll back the nandroid.
DroidTh3ory said:
Okay, as I am sure we all see there has been a HUGE break through for our HD2 freedom thanks to all the Dev's here with the release of ClockWork Mod Recovery. I can for see a downpour of one particlular question flooding the forums... "Can you make a ROM ZIP Please".
I would assume that it can't be that much of a task to take a NAND build and make it flashable (Maybe I am wrong) but it seems all the hard stuff of creation is done, it becomes a matter of "format" (Maybe Not the Right Word). Extract Boot and System.IMG's, Editing a script?
So... Maybe we can all take the burden off some of the Devs doing this to our favorite builds? Then they can focus on what they do best... making this stuff work.
What is involved in doing this?
Hell, maybe I am way off and we should leave it to the Pro's?
I'm Ready.
Click to expand...
Click to collapse
I am not a developer. I would be more than happy to help with doing the conversions if someone posts a way to do it.
The developers need to spend their time developing their builds to be the best that they can be. We, as a community, need to help the developers by taking the little tasks, such as file conversions, from the developers so they don't have to sweat the little stuff.
Linux BASH scripts are my friend.
Well, dsixda kitchen does allow import of nandroid backups, and anyway unyaffs already extracts imgs
Sent from my HTC Desire
droidzone said:
Well, dsixda kitchen does allow import of nandroid backups, and anyway unyaffs already extracts imgs
Sent from my HTC Desire
Click to expand...
Click to collapse
droidzone...I've used unyaffs to extract system.imgs before and the only problem is that it only extracts them in a read-only kind of form because I can't edit anything and I have to get an act of congress just to see a PNG. I'll give the dsixda kitchen a shot.....downloading right now.
Yes, flashing (actually recovering) a rom from SD is safe and simple. With recovery we could do these by ourselves.
dbshane said:
Yes, flashing (actually recovering) a rom from SD is safe and simple. With recovery we could do these by ourselves.
Click to expand...
Click to collapse
Ok, then try the kitchen. It allows import of nandroids and once imported, you can mod it whatever way you want.
Sent from my HTC Desire
Well, the first step is done.. We now have recovery. Now when just need something to use it with.
I was looking through the different builds NAND, RAM and SD. Besides everything being wrapped up in .img's, the NAND ROMS have the same files. Comparing to the ONLY Flashable [.ZIP] ROM I see no similarities.
Maybe RaiderX303 or another DEV can put us in the direction we would need to go. Software, Files, Steps, Etc
droidzone said:
Ok, then try the kitchen. It allows import of nandroids and once imported, you can mod it whatever way you want.
Sent from my HTC Desire
Click to expand...
Click to collapse
Okay so... When you are referring to Nandroids and you referring to backups? We have 3 build types at our disposal right now... NAND, RAM, and SD.
What would we compile out of the ROMS the DEVs have provided to use?
DroidTh3ory said:
Well, the first step is done.. We now have recovery. Now when just need something to use it with.
I was looking through the different builds NAND, RAM and SD. Besides everything being wrapped up in .img's, the NAND ROMS have the same files. Comparing to the ONLY Flashable [.ZIP] ROM I see no similarities.
Maybe RaiderX303 or another DEV can put us in the direction we would need to go. Software, Files, Steps, Etc
Click to expand...
Click to collapse
I think installing the dsixda kitchen is the first step in all of this. I'm installing it right now and I'm going to give it a shot using JDMS's NAND ROM.....we'll see what happens if I can get it to boot up in recovery or not.
mazdarider23 said:
I think installing the dsixda kitchen is the first step in all of this. I'm installing it right now and I'm going to give it a shot using JDMS's NAND ROM.....we'll see what happens if I can get it to boot up in recovery or not.
Click to expand...
Click to collapse
All right, I will do the same with the NEXUSHD 1.9 and see what happens.??? LOL
Raiderx uploaded a rom in zip format. Can't you guys just take that and compare it to another build to see the differences?
DroidTh3ory said:
Well, the first step is done.. We now have recovery. Now when just need something to use it with.
I was looking through the different builds NAND, RAM and SD. Besides everything being wrapped up in .img's, the NAND ROMS have the same files. Comparing to the ONLY Flashable [.ZIP] ROM I see no similarities.
Maybe RaiderX303 or another DEV can put us in the direction we would need to go. Software, Files, Steps, Etc
Click to expand...
Click to collapse
The big issue to converting a NAND to UPDATE.ZIP is not about the files (just unpack boot.img and system.img and put the contents in the relative folders) but making the updater scripts specially for symlinks that ZIP not support so is needed that symlink are deleted and recreated on-the.fly by the updater script
updater scripts are under META-INF folder in the zip
rafpigna said:
The big issue to converting a NAND to UPDATE.ZIP is not about the files (just unpack boot.img and system.img and put the contents in the relative folders) but making the updater scripts specially for symlinks that ZIP not support so is needed that symlink are deleted and recreated on-the.fly by the updater script
updater scripts are under META-INF folder in the zip
Click to expand...
Click to collapse
My head just exploded.. LMAO. but Seriously, I see what your saying. Any tips on updating the Scripts? Would starting from a SD or RAM build be a better way to start?
rafpigna said:
The big issue to converting a NAND to UPDATE.ZIP is not about the files (just unpack boot.img and system.img and put the contents in the relative folders) but making the updater scripts specially for symlinks that ZIP not support so is needed that symlink are deleted and recreated on-the.fly by the updater script
updater scripts are under META-INF folder in the zip
Click to expand...
Click to collapse
LOL...I have to agree once more with DroidTh3ory because my head just started to hurt when I started reading all of that.......I think this is the reason even more why we need a Developers hand in all of this. I know we are all looked at as little vampires that suck the very last drop out of what you guys have to offer but we would honestly would love to help instead of just coming on here to download stuff and complain about how this doesn't work and that doesn't work and just be a pain in the devs butt........So if any Developer is watching from up above....PLEASE, show us the way...LMAO
DroidTh3ory said:
My head just exploded.. LMAO. but Seriously, I see what your saying. Any tips on updating the Scripts? Would starting from a SD or RAM build be a better way to start?
Click to expand...
Click to collapse
I would say since raf explained the basics for converting nand to update.zip that nand would be a good place to start
Sent from my HTC HD2 using XDA App
DroidTh3ory said:
My head just exploded.. LMAO. but Seriously, I see what your saying. Any tips on updating the Scripts? Would starting from a SD or RAM build be a better way to start?
Click to expand...
Click to collapse
mazdarider23 said:
LOL...I have to agree once more with DroidTh3ory because my head just started to hurt when I started reading all of that.......I think this is the reason even more why we need a Developers hand in all of this. I know we are all looked at as little vampires that suck the very last drop out of what you guys have to offer but we would honestly would love to help instead of just coming on here to download stuff and complain about how this doesn't work and that doesn't work and just be a pain in the devs butt........So if any Developer is watching from up above....PLEASE, show us the way...LMAO
Click to expand...
Click to collapse
Sorry guys
to make the updater scripts you have to understand a little bit about symlinks and packing/unpacking stuff.. otherwise will be a lot difficult
basically you just need to unpack the .img files and put the contents in the folders. than you need to creat/modify the scripts for the META-INF folder, that basically are different for any build.
that's it.
its always nice to see members helping each other.after all the devs are done marvellous job in recent days.
rafpigna said:
Sorry guys
to make the updater scripts you have to understand a little bit about symlinks and packing/unpacking stuff.. otherwise will be a lot difficult
basically you just need to unpack the .img files and put the contents in the folders. than you need to creat/modify the scripts for the META-INF folder, that basically are different for any build.
that's it.
Click to expand...
Click to collapse
Ok Rafpigna....here's what I got in my update script that I put together the best I can using other update scripts from different ROMS and builds that I've collected in the last 3 months.
show_progress 0.1 10
run_program PACKAGE:remtool.sh
copy_dir PACKAGE:system SYSTEM:
show_progress 0.2 40
copy_dir PACKAGE:data DATA:
show_progress 0.3 80
copy_dir PACKAGE:sdcard SDCARD:
show_progress 0.4 100
If there anything I should include or take out or should I go and jump off a building now?...LMAO

[Q] how to make nand file when you have sd file

can anyone help me how to make nand file when i have sd file cuz i cannot install from my sd card i need to install directly
thanks
I am not sure that I understand what is your exact problem. But if I'm right and you can not install rom from SD card and want to install it directly from computer, maybe you should try to use DAF versions ?
adecostres said:
I am not sure that I understand what is your exact problem. But if I'm right and you can not install rom from SD card and want to install it directly from computer, maybe you should try to use DAF versions ?
Click to expand...
Click to collapse
yes but there is only one daf version and i want to know how to convert the sd version to daf version
That's not very easy. You'd have to edit the intrid.gz and and zImage and other things to make it work. More effort than it's worth. What ROM you looking for? Is it a .zip SD card file or and Android folder type?
daniel.nano said:
yes but there is only one daf version and i want to know how to convert the sd version to daf version
Click to expand...
Click to collapse
To the point - the fact you're asking this question leads me to believe you're not skilled enough to know how to perform all of the changes this would require.
My suggestion is you forget about the SD version and make the move to the NAND Android instead.
The DAF version is a way for Windows to put Android on your phone through the built-in bootloader onto the NAND chip on your phone. SD android is a completely different structure and you'll never find an "SD DAF" Android.
could you perhaps extract the system folder from the CWM zip, then use mkyaffs2image to build a system.img and drop that in place of the original system.img from the DFT version? (and teh same with the boot folder boot.img too, i would assume)
Or is that make believe?
dkl_uk said:
My suggestion is you forget about the SD version and make the move to the NAND Android instead.
Click to expand...
Click to collapse
daniel.nano said:
can anyone help me how to make nand file when i have sd file cuz i cannot install from my sd card i need to install directly
thanks
Click to expand...
Click to collapse
To the point - the fact you're giving that answer leads me to believe you're not skilled enough to know how to read the whole question befor,,,,,,,,,,,,,,,,
hehe, sorry, couldnt resist.
samsamuel said:
could you perhaps extract the system folder from the CWM zip, then use mkyaffs2image to build a system.img and drop that in place of the original system.img from the DFT version? (and teh same with the boot folder boot.img too, i would assume)
Or is that make believe?
Click to expand...
Click to collapse
Extracting the system folder from CWM zip wont work. Its because during the zip installation the updater script is beeing called and it creates a lot of symlinks. So, if you just extract and convert, you will miss the whole bunch of symlinks (and permissions, etc..)
samsamuel said:
To the point - the fact you're giving that answer leads me to believe you're not skilled enough to know how to read the whole question befor,,,,,,,,,,,,,,,,
hehe, sorry, couldnt resist.
Click to expand...
Click to collapse
Really?
Never heard of DAF then?
We're limited to either SD or CWM install, are we?
dkl_uk said:
Really?
Never heard of DAF then?
We're limited to either SD or CWM install, are we?
Click to expand...
Click to collapse
Heh, dig deeper.
The op is limited to usb only so yea, in this case we are limited to daf only, and he finds there isn't as wide range of daf roms, hence the perfectly reasonable question.
which part of the original post can't you understand?
greg17477 said:
Extracting the system folder from CWM zip wont work. Its because during the zip installation the updater script is beeing called and it creates a lot of symlinks. So, if you just extract and convert, you will miss the whole bunch of symlinks (and permissions, etc..)
Click to expand...
Click to collapse
Ah I thought maybe something like that, but figured I'd ask anyway, for myself if nothing else.
samsamuel said:
Heh, dig deeper.
The op is limited to usb only so yea, in this case we are limited to daf only, and he finds there isn't as wide range of daf roms, hence the perfectly reasonable question.
which part of the original post can't you understand?
Click to expand...
Click to collapse
I'll assume your lack of English skills is the reason you've totally mis-understood every single thing i've written in this thread.
If I've missunderstood, it can only mean that even though it didn't sound like it, you do agree with me, in which case appology accepted, lets say no more about it.

[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?

Categories

Resources