Could someone pull me some files from their Boost/Sprint 2nd gen Moto E ? I am trying to find a way to get the tethering to work on the Verizon variant.
You WILL have to be rooted to get these files. Even a temp root will work.
Keep in mind, temp root can disappear at any time. If you pull a file (copy it) and it shows up as 0 bytes, then you lost root before you pulled it. Reboot, temproot, and try again.
Files I need:
-Root-> data>> data>>> com.motorola.android.providers.settings (just copy the whole folder)
-Root-> data>> data>>> com.motorola.android.provisioning (copy folder)
-Root-> data>> data>>> com.motorola.service.selfprovisioning (copy folder)
-Root-> data>> data>>> com.motorola.service.vzw.entitlement (you many not have this exact folder. Mine was directly below the folder above "selfprovisioning")
-Root-> system>> app>>> HotspotLauncher (whole folder)
There might be a few more files when I can remember them.
I'll add them when I get a chance.
do you still need these files?
Does anyone have the firmware for the Sprint XT1526 either 5.0.2 or 5.1? Doesn't have to be signed, my bootloader is unlocked. But I need logo.bin, boot.img, system.img, NON-HLOS.bin and fsg.mbn. Is there anyway to pull these partitions from another XT1526 so that they are flashable by fastboot?
Hi,
I edited
Code:
/data/data/com.android.providers.telephony/databases/carriers.db
while trying to enable tethering and now my phone can only boot into recovery. Could anyone send me their version? I'm with BoostMobile but I hope it doesn't differ much with other carriers.
Never mind, turns out that file wasn't the problem.
Related
ZV6 is out!! And NO this is not Lollipop... it's still Android KitKat 4.4.2
Thanks to an anonymous donor we now have the ZV6 TOT. I have broken down the TOT and also uploaded the individual partitions which can be flashed if rooted. Speaking of root... ZV6 blocks Stump Root. If you wish to use ZV6 and have root you must install Bump'd TWRP while on ZV4 then manually flash the ZV6 boot/modem/system partitions... OR you may be able to root on ZV4 then take the official ZV6 OTA update and keep root -- the OTA has NOT been pushed yet so it is too early to say for sure. Remember to NEVER take an OTA if you have modified your SYSTEM partition at all (xposed/tethermod/etc) OR if you have TWRP installed.
Changelog:
Google Security Patches
Qualcomm Security Patch
International Voice over WI-FI
Improve unlock algorithm when phone is in the pocket
Enhancements to the LG Home (Sluggish UI fix)
Enhancement to the compass application
Enhancement to the Auxiliary cable recognition.
Mobilize Device Content Caching - An application caches HTTP web and app data on the device (not the Network), making the retrieval of data faster and saving bandwidth on the network
--TOT (*.zip) can be downloaded *HERE*
Flash this TOT using the same method as ZV4. You will need to select "Board DL" in LG Flash, otherwise you will get stuck. After the TOT flashes it will reboot your phone into the "MiniOS".. unplug the USB cable and press and hold the power button on the phone then press on the "Normal Boot" option on your phones screen. You are now on stock ZV6. Remember... there is no root for ZV6 so do not flash ZV6 TOT unless you don't mind being without root.
--Individual ZV6 partitions to flash manually can be downloaded *HERE*
I am removing the system.img from Codefire but thanks to @budeone system.img has been mirrored HERE. Feel free to make more mirrors of system...
The bootloader does NOT need to be updated in order to use the ZV6 boot/modem/system images. It's completely optional to flash the bootloader files (aboot, sbl1, dbi, laf, factory, tz, rpm). To flash the boot, modem and system partitions manually someone can make some new flashable *.zips containing the partitions... OR you can use my "flash2" *.zips which can be found under the How-To Manually Flash/Update Device w/ System.img, Boot.img and Modem.img section in my *[PSA] NO OTAs!! | Keep Root/Unlock | How-To: Block OTA, DL SW/FW, Update Manually* thread. You simply stick any loose system.img and/or boot.img and/or modem.img on your internal sdcard and flash my premade flashable zips in TWRP to install them.
--ZV4-to-ZV6 OTA Update Zip can be downloaded *HERE*
You must have a stock recovery and stock system partition for this to work. Being rooted may be OK but if you've edited or removed apks or other files or edited the build.prop then OTA zip may fail the integrity check. Root may not stick thru OTA.. until someone confirms one way or the othe the risk is yours.
Directions:
1. Remove USB cable from phone.
2. Power phone off.
3. Press and hold volume down + power until you boot into stock recovery.
4. Select "update with adb"
Rename zip file into update.zip
Code:
adb sideload update.zip
Alternate Directions to skip using ADB (needs microSD card):
1. Format microSD card as EXT4.
2. Rename zip to update.zip
3. Move update.zip onto external SD card. EZ way would be to stick SD card in phone then connect phone to PC and use MTP.
4. Power off and boot into stock recovery (vol down + power)
5. Select the Update from SDCARD option.
Alternate Directions to skip using ADB (must have root):
1. Stick OTA zip file in the /cache directory
2. Power off and boot into stock recovery (vol down + power)
3. Select the Update from cache option... then select the update zip you placed in /cache
As mentioned above.. ZV6 blocks Stump Root. Bump is not blocked.. so as long as you have root with ZV4 you can manually update to ZV6 and keep Bump'd TWRP or flash any Bump'd kernel or rom. No anti-rollback has been added to this update either.. so downgrading to ZV4 works!
Click to expand...
Click to collapse
Autoprime. Thank you for your work. +1
I've tried using the flash2 with system, boot and modem imgs being in flash2 folder on the internal storage. But It says it successfully flashed them but reboot and nothing.
Nada. I don't believe its really flashing them since it goes really quick.
Well, took me a bit to get back up and running... but yeah, not seeing much of a difference in this versus ZV4. (Well, except losing root since I'm impatient and flashed the TOT.)
Interesting any major changes or is it a security update
autoprime said:
ZV6 is out!! And NO this is not Lollipop... it's still Android KitKat 4.4.2
Click to expand...
Click to collapse
I'll mirror when I get home from work today. Thanks man!
@autoprime I read all the above, but do you know if we take zv6, can we revert by .tot to zv4? I know there's been issues with that in the past.
Warboy said:
I've tried using the flash2 with system, boot and modem imgs being in flash2 folder on the internal storage. But It says it successfully flashed them but reboot and nothing.
Nada. I don't believe its really flashing them since it goes really quick.
Click to expand...
Click to collapse
the flash2 files have a check in them to make sure the proper file is in its proper place before anything else.. this way it doesnt erase your partition if its not actually going to flash a new file. Perhaps the folder is named Flash2 with a capital F? If the folder is named "flash2" with lowercase f and is located at /sdcard/flash2/ on your phone.... and the files are named system.img modem.img and boot.img with all lowercase letters.. it should work. They have been confirmed working by many users across all G3 models.
If there is still an issue.. please provide a recovery.log if possible.
engine95 said:
@autoprime I read all the above, but do you know if we take zv6, can we revert by .tot to zv4? I know there's been issues with that in the past.
Click to expand...
Click to collapse
No issues downgrading. There'd be giant red letters everywhere otherwise. But I have now added a mention in the OP that specifies downgrading is still an option. :good:
ZV6 upgrade went just fine, as you stated. No problems using flash2 stuff and let TWRP save the root. It seems to upgrade the Home launcher as well as the contacts database. It also upgrades the Sprint data-sharing activity. In other words, ZVF6 works fine, but is not a big update.
Flashable zip should be up tonight. Tomorrow at latest.
http://forum.xda-developers.com/showthread.php?p=56937777
I have a working compass!
I flashed the modem.img first with no apparent change, then the system.img... Shazammm! After calibration, the compass seems to be accurate. This was the big flaw for me on an otherwise lovely device and now it seems to be working. Now I can look forward to a Lollipop update.
I pray it fixes the bluetooth. I have a Chrysler U Connect system and my G3 or a G3 Vigor for my girlfriend will not stay paired to the unit.
After unzipping the system.img zip, it's named "14-system.img".
I plan on using the "flash2" process of upgrading.
Do I need to rename "14-system.img" to just "system.img" for the flash2 procedure to work?
Thank you
EDIT: I went back and re-read Auto's manual update procedure and can confirm, yes, I do need to rename "14-system.img" to "system.img"
autoprime said:
the flash2 files have a check in them to make sure the proper file is in its proper place before anything else.. this way it doesnt erase your partition if its not actually going to flash a new file. Perhaps the folder is named Flash2 with a capital F? If the folder is named "flash2" with lowercase f and is located at /sdcard/flash2/ on your phone.... and the files are named system.img modem.img and boot.img with all lowercase letters.. it should work. They have been confirmed working by many users across all G3 models.
If there is still an issue.. please provide a recovery.log if possible.
Click to expand...
Click to collapse
The files are in the internal SDcard under "/sdcard/flash2/*.img" * being there respected names
here is the link to the recovery.log
http://pastebin.com/AE7y7KAH
Warboy said:
The files are in the internal SDcard under "/sdcard/flash2/*.img" * being there respected names
here is the link to the recovery.log
http://pastebin.com/AE7y7KAH
Click to expand...
Click to collapse
thanks for log. odd, the only error in the log is that it doesn't see the system.img file and then aborts.
for whatever reason it's checking /sdcard/flash2/ and not finding the file. Not sure where to go from here. Logs would suggest that the file name is incorrect or folder name is wrong. But you've said they are correct.. so.. idk.
To debug this further.. can you connect to adb shell while in TWRP? And paste the output from the following commands?
Code:
adb shell
cd /sdcard/flash2/
ls
autoprime said:
thanks for log. odd, the only error in the log is that it doesn't see the system.img file and then aborts.
for whatever reason it's checking /sdcard/flash2/ and not finding the file. Not sure where to go from here. Logs would suggest that the file name is incorrect or folder name is wrong. But you've said they are correct.. so.. idk.
To debug this further.. can you connect to adb shell while in TWRP? And paste the output from the following commands?
Code:
adb shell
cd /sdcard/flash2/
ls
Click to expand...
Click to collapse
http://imgur.com/J5FkM9V
http://imgur.com/RGnDXyZ
Warboy said:
http://imgur.com/J5FkM9V
http://imgur.com/RGnDXyZ
Click to expand...
Click to collapse
I'm officially stumped
everything looks right. just not meant to be on your device I guess.
I'm reaching here.. but maybe there's some issue if you used MTP? Versus using ADB push to put the image on your phone?
Have you noticed if the modem or boot image has updated (those would be fast flashes) and just system is not working? or all 3 not working? You'd have to check the software settings under About Phone to see if baseband(modem) or kernel changed.
you could always use the dd command to try and flash the image while in TWRP..
Code:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/flash2/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
The 2 dd commands should take a minute or three to complete.
Or just wait for engine95's stock rooted ZV6 rom.
autoprime said:
I'm officially stumped
everything looks right. just not meant to be on your device I guess.
I'm reaching here.. but maybe there's some issue if you used MTP? Versus using ADB push to put the image on your phone?
Have you noticed if the modem or boot image has updated (those would be fast flashes) and just system is not working? or all 3 not working? You'd have to check the software settings under About Phone to see if baseband(modem) or kernel changed.
you could always use the dd command to try and flash the image while in TWRP..
Code:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/flash2/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
The 2 dd commands should take a minute or three to complete.
Or just wait for engine95's stock rooted ZV6 rom.
Click to expand...
Click to collapse
Should it be Flash2 not flash2
thznutz87 said:
Should it be Flash2 not flash2
Click to expand...
Click to collapse
I tried having a capital F and that didn't change anything.
system.7z
https://mega.co.nz/#!G0onwR5T!QV-NZ2hpAIllAX9tKCNBDkGLyE7AWD241Stws-c6y18
I have a system.img file, which I extracted from a 20J KDZ. I would now like to convert it into a flashable zip. I have 2 reasons for this. One, I dont want to have to use LGUP to revert my phone to a 100% stock system. It is much easier to just flash a zip of the system partition. Two, I would like to get into modding and ROM development. I believe that it is best to start from pure stock and make changes from there, instead of basing your work off of something that someone else has already modded.
I found these threads but they're a bit old (Lollipop):
1. http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
2. http://forum.xda-developers.com/tmobile-lg-v10/development/lg-h901-stock-images-device-restore-t3241170
In one of them a member provided img's for recovery, boot, and system. In the other thread flashable zips of these img's were posted. These are for the Tmo v10. So it's not a matter of whether it can be done, but how. What tools are needed?
I downloaded the zip from one of the aforementioned threads, deleted the boot.img, replaced his system.img with mine, edited updater-script, and zipped up the meta-inf and system.img files with 7zip. I also checked to be sure that the block to be flashed was correct, it is the same (even though my img is for MM). I tried flashing with TWRP, I immediately get an error code 6.
What should I do?
Just off the subject slightly...but Eliminater74 already has a flashable zip (thought TWRP) for the 20J release. Its a 2 Part System.
Eliminator74's zip is modified. I want to take a 100% pure stock system.img (extracted from stock firmware) and put it into a zip that can be flashed in TWRP. When I say stock, that's what I mean. No root, no Xposed, no BusyBox, nothing. This has already been done for Lollipop on the v10, but I have MM. I have already explained why I want to do this. I'm currently looking into whether Superr's Kitchen can accomplish this.
He has a Fully Stock 20J release..just gotta read the thread..
AnonVendetta said:
I have a system.img file, which I extracted from a 20J KDZ. I would now like to convert it into a flashable zip. I have 2 reasons for this. One, I dont want to have to use LGUP to revert my phone to a 100% stock system. It is much easier to just flash a zip of the system partition. Two, I would like to get into modding and ROM development. I believe that it is best to start from pure stock and make changes from there, instead of basing your work off of something that someone else has already modded.
I found these threads but they're a bit old (Lollipop):
1. http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
2. http://forum.xda-developers.com/tmobile-lg-v10/development/lg-h901-stock-images-device-restore-t3241170
In one of them a member provided img's for recovery, boot, and system. In the other thread flashable zips of these img's were posted. These are for the Tmo v10. So it's not a matter of whether it can be done, but how. What tools are needed?
I downloaded the zip from one of the aforementioned threads, deleted the boot.img, replaced his system.img with mine, edited updater-script, and zipped up the meta-inf and system.img files with 7zip. I also checked to be sure that the block to be flashed was correct, it is the same (even though my img is for MM). I tried flashing with TWRP, I immediately get an error code 6.
What should I do?
Click to expand...
Click to collapse
What tool did you use to extract the KDZ? I am trying to get a stock boot.img for the H901J build and I cannot seem to find it. I used the WindowsLGFirmwareExtract 1.2.5.0 release and all I see are a ton of .bin files and system.img. Is boot.img inside system.img?
@Sippi4x4man: I also used WindowsLGFirmwareExtract. Inside the KDZ there is a DZ and DLL file. Just extract the DZ, then you see lots of BINs. The system.img is split up (since it's around 4GB alone), but the tool can combine the pieces into one file. I was able to figure out how to manually flash the IMG, by running a dd command with TWRP's terminal emulator.
dd if=/external_sd/system.img of=/dev/block/platform/f9824900.sdhci/by-name/system
It takes a few minutes to finish, followed by a message that says no more space is available (I guess /system got filled up). I think when you dd anything you are copying both free and used space, since an IMG is usually just a (sometimes raw) disk image. TWRP will also initially say that no system is installed, I just ignored it, the device boots fine, everything is pure stock, no issues at all. System is mountable after subsequent boots into recovery. I used Magisk and the phh Superuser Magisk module to gain root without modding system partition, and the Magisk version of Xposed. But I would still like to create a flashable zip to automate this. If I figure it out I don't mind uploading it so the community can benefit.
As for the stock boot.img, I would imagine that the boot.bin inside the DZ is probably what you're after. The file size seems about right. However, I tried renaming boot.bin to boot.img and flashing from TWRP. Device wouldn't boot. So maybe there is some other conversion process that needs to be done. I can't think of any other way to obtain a pure stock boot image, extracting it from stock firmware seems like a sure way. If you ever figure it out then please provide a copy. Make sure it isn't patched by SuperSU, Xposed, Magisk, etc. I could maybe merge it into a stock zip.
AnonVendetta said:
@Sippi4x4man: I also used WindowsLGFirmwareExtract. Inside the KDZ there is a DZ and DLL file. Just extract the DZ, then you see lots of BINs. The system.img is split up (since it's around 4GB alone), but the tool can combine the pieces into one file. I was able to figure out how to manually flash the IMG, by running a dd command with TWRP's terminal emulator.
dd if=/external_sd/system.img of=/dev/block/platform/f9824900.sdhci/by-name/system
It takes a few minutes to finish, followed by a message that says no more space is available (I guess /system got filled up). I think when you dd anything you are copying both free and used space, since an IMG is usually just a (sometimes raw) disk image. TWRP will also initially say that no system is installed, I just ignored it, the device boots fine, everything is pure stock, no issues at all. System is mountable after subsequent boots into recovery. I used Magisk and the phh Superuser Magisk module to gain root without modding system partition, and the Magisk version of Xposed. But I would still like to create a flashable zip to automate this. If I figure it out I don't mind uploading it so the community can benefit.
As for the stock boot.img, I would imagine that the boot.bin inside the DZ is probably what you're after. The file size seems about right. However, I tried renaming boot.bin to boot.img and flashing from TWRP. Device wouldn't boot. So maybe there is some other conversion process that needs to be done. I can't think of any other way to obtain a pure stock boot image, extracting it from stock firmware seems like a sure way. If you ever figure it out then please provide a copy. Make sure it isn't patched by SuperSU, Xposed, Magisk, etc. I could maybe merge it into a stock zip.
Click to expand...
Click to collapse
It's been a while from this post... But I'm looking after the same goal you were and got the same error 6 trying the same things you described in your previous posts. Despite of these long 4 years, let me try: did you finally achieve to make the flashable zip with system.img?
I do not own an LG V10 anymore.....it is the most garbage phone I've ever had.
I now use SuperR's Kitchen to create flashable zip from system.img. Works like a charm every time. Downside is that you need a PC to use it. It works for all phones (but you must also have an unlocked bootloader and custom recovery, or you will not be able to flash the zip). There are both free and donate versions, both will work fine.
AnonVendetta said:
I do not own an LG V10 anymore.....it is the most garbage phone I've ever had.
I now use SuperR's Kitchen to create flashable zip from system.img. Works like a charm every time. Downside is that you need a PC to use it. It works for all phones (but you must also have an unlocked bootloader and custom recovery, or you will not be able to flash the zip). There are both free and donate versions, both will work fine.
Click to expand...
Click to collapse
Thank you for your reply. My device is Lenovo Z6 Pro but I thought this wouldn't make a difference.
Just to be sure, what you get with SuperR's Kitchen is a zip including system.img file and not the /system folder, right? Thank you in advance.
Edit: I had tried with other kitchen softwares with no success but SuperR's Kitchen did the job as you said, like a charm. Tons of thanks.
@descarao81: No, SuperR's Kitchen does not include system.img/boot.img, you must provide them yourself. They are device-specific. And system.img is a very large file, so it cannot reasonably be included in the Kitchen zip.
Yeah, maybe I wasn't clear, I meant if the resultant zip would include those raw image files being the original image files provided by the user. It's clear now. Thank you.
Here is how to do it...
1. Go to:
https://forum.xda-developers.com/tm.../lg-h901-stock-images-device-restore-t3241170
Download from the link he provided.
2. Extract the .zip file that you downloaded.
3. Make a new folder called "rom"
4. Copy the META-INF folder from the folder you extracted and place it into the "rom" folder.
5. Download any other flashable rom for your device. Extract it.
6. Go to {EXTRACTED_FLASHABLE_ROM}\META-INF\com\google\android\update-binary in your flashable extracted rom folder. Copy the "update-binary" . Got to the "rom" folder and go to META-INF\com\google\android. Delete the update-binary there and replace it with the one you have copied.
7. Now copy the boot.img from the other rom that is for your device. And place it into the "rom" folder.
8. Now Finally Compress the all the files.
9. Now you will have a flashable system.img.
10. Go to TWRP and flash the .zip that you have just made!
Upytry2 said:
Here is how to do it...
1. Go to:
https://forum.xda-developers.com/tm.../lg-h901-stock-images-device-restore-t3241170
Download from the link he provided.
2. Extract the .zip file that you downloaded.
3. Make a new folder called "rom"
4. Copy the META-INF folder from the folder you extracted and place it into the "rom" folder.
5. Download any other flashable rom for your device. Extract it.
6. Go to {EXTRACTED_FLASHABLE_ROM}\META-INF\com\google\android\update-binary in your flashable extracted rom folder. Copy the "update-binary" . Got to the "rom" folder and go to META-INF\com\google\android. Delete the update-binary there and replace it with the one you have copied.
7. Now copy the boot.img from the other rom that is for your device. And place it into the "rom" folder.
8. Now Finally Compress the all the files.
9. Now you will have a flashable system.img.
10. Go to TWRP and flash the .zip that you have just made!
Click to expand...
Click to collapse
Trying that exactly when im home! Thank you!
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk
I was looking to attempt to root a phone (Asus zenfone v520kl) and stumbled upon a problem that I am stuck on and can't find a solid answer to.
Basically, the phone's bootloader is now unlocked and has the WW 3.3 firmware ( https://mega.nz/#!l7wBlQ4B!uB63yH5Rir24GaSfDMWKowqdz-N_sc6SJ-q1WuuGiqM/ ). I was planning on patching the boot.img with MAGISK but 7-Zip does not properly extract boot.img from the .raw file. (boot.img, system.img, cache.img and recovery.img end up with erros and their file size ends up with 0 after extracting. Most of the other img seem to extract just fine.)
So my questions:
1) is there another program that might be able to extract the .raw file. Suggested ways was 7zip or rename extension to .zip and extract which doesn't work either. Also downloading from different websites yield the same problem as they all seem to be the same file. If not,
2) Might there be a way to extract boot.img from the phone itself. (Making matters worse, the phone doesn't have root access and booting to recovery doesn't work. There is also no TWRP for this phone. I did try using TWRP for zenfone 3 deluxe for fun, but that ends up with a black screen.)
I wasnt able to restore my firmware through TWRP(was getting extractTarFork() process ended with ERROR: 255) so installed 7zip and extracted both firmware.vfat.win and dsp.emmc.win and moved them to my phone. I wasnt able to move the image folder inside /storage/emulated/0/firmware to /firmware folder so i use the chmod 755 and was able to move the files to /firmware, and my phone works just as it used to but the dsp.emmc.win thing has wierd things inside of it and i dont know where to put them. The folder has [SYS], lost+found and bunch of module.so.1 files(AlacDecoderModule.so.1, ApeDecoderModule.so.1, DolbyMobileModule.so.1 and bunch of more). My device is a Xiaomi Redmi Note 4(Snapdragon variant). I need some help with this. This is whats inside the folder (https)://ibb.co/Tb4Yh64 i cant post link so i did like this.