I see a few roms asking to update to the latest vendor and I have no idea where to find a file I can install through TWRP and no idea what to look for. Can someone help me out a bit? I've been looking on Google and fell on a few pages where I get a bunch of GitHub packages with no install instructions with a list of a bunch of sh, mk and other files.
Related
Hi Guys today I'm going to show u how to add OTA updates for your rom.
So what is it basically???
Everyone knows it lol
So lets start with the business.
1)First of all get the latest apk from here
https://www.otaupdatecenter.pro/
2)Put this app in your rom's /system/app
3)Pick a ROM ID that you will use in our database(No spaces)
4)Add the following properties to your build.prop:
otaupdater.otaid=<ROM ID you picked from previous step>
otaupdater.otatime=<Date/time of this build in yyyymmdd-hhmm format>
otaupdater.otaver=< version number/name>
5)Package your ROM, generate an MD5 of the zip file, and upload it on any file sharing site
6)Then make your account and add your rom (update) on the site (OTA)
7)You will need the ROM ID you picked, the device you packaged for, and the URL and MD5 of the zip file.
8)For any further updates, just make sure you update the "otatime" and "otaver" properties in build.prop
Hope this HELPS!
Wanna hit THANKS!!,
Then there's A button for that
How do you generate a md5 of the rom?
Nice guide, i understand everything excepting that step.
Isn't this taken from here: http://forum.xda-developers.com/showthread.php?t=1803562
Thanks
Helped me a lot for building my own rom trying to learn rn and it was very helpful of you
I have the PAC source downloaded and now I want to figure out how to add other features from either github or wherever to it. There's some things from the xposed framework that I'd like to implement in the ROM but I'm not sure how to go about doing it. I'm new to android programming, just been porting PAC to my phones that don't have support. Any help is greatly appreciated.
Help injecting features or settings
I use file manager pro from cheeta mobile to open the rom.zip then copy and paste the system/file context/meta inf /and any other files in the zipped folder to the ExtSdcard1 root directory, then open the copied files which will be opened for modifications, then add the mods directly to the appropriate locations ( use this method(very slow) or use an apk decompiler to make your changes to apps. There are instructions for that on xda forums. But since the update to lollipop we have seen the new compression format change to system.new.dat file compression so if you want to modify lollipop roms you have to find (Optimized) version or use the dat file decompiler to translate the system.dat.new file or others in that format to readable/writable or understandable format. Let us know if this gets you on track or if you have solved this issue, thanks.
Kinda makes this noob sick. I just got a new Moto G4 X1625 (not Amazon). Next came the steps to unlock the bootloader with Motorola and to install TWRP. Everything had gone so easily by following some how-to steps I jumped to the next step of installing SuperSU without doing a backup – thinking it was simply adding an app. Big mistake! Reboot and now always stuck on the logo boot animation.
Okay, so I found and tried use TWRP to install ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip in an attempt to get back to stock. No luck there since install always aborts with a "Could not find 'META-INF/com/google/android/update-binary' in the zip file."
I checked a couple of other ROMs and that META-INF directory doesn't seem to be included in them either.
What do I need to do just to get back to normal eliminating the effects of that SuperSU install? Help greatly appreciated.
That file you downloaded is not a flashable file.
Instead, read this linky
Thanks for the helpful clue @t0mm13b. I followed the approach at <http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/> and executed the listed commands from my MacOS Terminal. They did the job resulting in a fresh install after bootup.
2-1/2 questions…
1. Are flashable ROM files readily available? The ones I found all seemed missing the META-INF directory. Will they be .img files and not .zip?
2. Is TWRP not useful for these stock ROMs?
The ones I found all seemed missing the META-INF directory. Will they be .img files and not .zip?
Click to expand...
Click to collapse
As a general rule of thumb, read the accompanying text to the link of the download, on a web page where you find one. It will tell you if it's flashable or not.
Factory images, just like what you had to carry out previously, never have, and do not have the `META-INF` directory. They usually contain img files that requires `fastboot flash`.
On the other hand, OTAs and flashable zips will have that in their respective zip file.
Thanks again @t0mm13b for the clarification. I often didn't see info about whether a ROM is flashable in link or web page text, but it may have just been assumed based on being aware of what the zip contains.
I've been studying how to build my own LineageOS or AospExtended, but one thing always bothers me: every guide that explains the need of extracting blob files tell to extract them from an official nightly zip or from a repository called "TheMuppets" (https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-14.1/athene).
The question is: where do these blobs came from in the first place? Where were they compiled (like libxml.so)? The Nougat stock rom doesn't have all the blobs presented in proprietary-files.txt, so I can't just export them from a stock image extracted using TWRP, since a bunch of .so are still missing. How can I compile all .so not available at the stock rom or where are the official channels for obtaining the blobs?
I am trying to build a ROM, however I am missing a couple files, I need a vendor tree of hi6250-8-common so I can start building the ROM, does anyone have a copy of this folder? or even a GitHub link? I am still fairly new to this and I don't mind trying other options to fix my missing file issue.
I've found just a hi6250 vendor, device and kernel, I am no longer looking for the trees