Related
Hi XDA,
I'm using dsixda's Kitchen, trying to edit a stock rom (LFB-i9300).
I got everything extracted, but I had to remove the .md5 extension of the stock rom and I had to rename system.img to factoryfs.img, else Kitchen wouldn't recognize the rom. I think something went wrong in this process of getting the rom recognized. I loaded the rom and I chose to add in root, busybox and I de-odexed the files (I chose Api level 14, this is the right one for 4.0.4, right?).
Then I build the rom, zipaligned and signed it and then I moved the zip to my i9300. Then I get this error when I'm trying to flash the rom:
*Installing update...*
E:Error in /emmc/m0_signed_071212_225202.zip (Status 0)
*Installation aborted.*
I know the i9300 isn't officially supported but I was told Kitchen would also work with the i9300.
Btw, when extracting factoryfs.img and the file for CSC, Kitchen said something about crc32 problems, it expected something different than it calculated.
I hope someone could help me solve this problem.
Regards,
dejong12
did you check updater-script file?
Yup, I checked it, but no errors were returned and I couldn't anything in the file itself.
dejong12 said:
Yup, I checked it, but no errors were returned and I couldn't anything in the file itself.
Click to expand...
Click to collapse
can you post updater-script file and the original update-script file please using pastebin
Here are update_script and updater_script.
I read I need an edify file, but does anyone have that premade? I don't know the mount points etc.
dejong12 said:
I read I need an edify file, but does anyone have that premade? I don't know the mount points etc.
Click to expand...
Click to collapse
this the correct updater scripts for gs3 , you need update binary as well
http://pastebin.com/C9ktKbXs
auras76 said:
this the correct updater scripts for gs3 , you need update binary as well
http://pastebin.com/C9ktKbXs
Click to expand...
Click to collapse
Where can I get the correct update binary?
I just have to paste this file into my current updater script?
dejong12 said:
Where can I get the correct update binary?
I just have to paste this file into my current updater script?
Click to expand...
Click to collapse
i will send you
---------- Post added at 11:41 PM ---------- Previous post was at 11:40 PM ----------
dejong12 said:
Where can I get the correct update binary?
I just have to paste this file into my current updater script?
Click to expand...
Click to collapse
https://hotfile.com/dl/163449391/6b7935c/update-binary.html
auras76 said:
i will send you
---------- Post added at 11:41 PM ---------- Previous post was at 11:40 PM ----------
https://hotfile.com/dl/163449391/6b7935c/update-binary.html
Click to expand...
Click to collapse
Thank you for the file! Btw, I don't think I can use this for every rom I want to create if I choose different options, or can I?
dejong12 said:
Thank you for the file! Btw, I don't think I can use this for every rom I want to create if I choose different options, or can I?
Click to expand...
Click to collapse
you can use for every rom for sg3
auras76 said:
you can use for every rom for sg3
Click to expand...
Click to collapse
I've replaced update-binary and updater-script in my finished zip but I'm getting an status 6 error now, could you tell me what I did wrong?
dejong12 said:
I've replaced update-binary and updater-script in my finished zip but I'm getting an status 6 error now, could you tell me what I did wrong?
Click to expand...
Click to collapse
Flash rom again.. after getting the error, go to advanced>report error..
Then reboot your device... you will find a recovery.log file in clockworkmod directory of your sdcard...
There you can spot the error...
adiles said:
Flash rom again.. after getting the error, go to advanced>report error..
Then reboot your device... you will find a recovery.log file in clockworkmod directory of your sdcard...
There you can spot the error...
Click to expand...
Click to collapse
Here's the error report: http://pastebin.com/Yt8BHvrf/
Some lines say ALE8, but that's not the version I'm trying to flash...
The error is here
line 1 col 29: syntax error, unexpected BAD
Upload your script.
I will help you.
Andersondj said:
The error is here
line 1 col 29: syntax error, unexpected BAD
Upload your script.
I will help you.
Click to expand...
Click to collapse
The script I used was posted a few posts ago in this thread.
dejong12 said:
I've replaced update-binary and updater-script in my finished zip but I'm getting an status 6 error now, could you tell me what I did wrong?
Click to expand...
Click to collapse
create a folder named (aur) to rom zip and put boot.img , modem.bin and this file
- https://hotfile.com/dl/163506889/899d8be/flash_image.html
auras76 said:
create a folder named (aur) to rom zip and put boot.img , modem.bin and this file
- https://hotfile.com/dl/163506889/899d8be/flash_image.html
Click to expand...
Click to collapse
This doesn't work for me, I still get that status 6 error.
dejong12 said:
This doesn't work for me, I still get that status 6 error.
Click to expand...
Click to collapse
this is bad zip
auras76 said:
this is bad zip
Click to expand...
Click to collapse
Ok, I tried to rebuild the zip, but I want to make sure, do I have to create that map in the root folder of the zip? And is the name with or without parenthesis?
Use at your own risk - untested
I am not responsible for bricked devices.
Back up before doing anything
Compiled using the following device tree: https://github.com/CyanogenMod/android_device_sony_z3c
Working:
Nothing, as far as I am concerned which is why you should use at your own risk.
Not Working:
Everything, as far as I am concerned which is why you should use at your own risk.
UPDATED - File: See Post Update Below | [md5] 4889d4bad5b07326c530ccc9e575acd1
If you do not know what to do with it you should do nothing.
The commands I used to make zip package was:
Code:
. build/envsetup.sh
lunch
make bacon
(Brunch and Breakfast are for official devices only, I believe)
NOTE:
No more errors when extracting proprietary files.
Thank you to Kali- and chirayudesai for setting up device tree at: android_device_sony_z3c
And, thank you to the people who spared the time in correcting my silly mistakes, and for responding to my even sillier questions.
When i select choose form sdcard1 from main recovery menu, i get a wiping cache messages, and then it reverts back to the main screen, same when selecting internal storage.
When using TWRP from a different fasbooted kernel (AndroPlus Kernel for Stock FW / ROM), i get status 7.
Cheers
delect first sentence in update script leads to success of flashing this rom,it boots up,with animation,but when screen shows starting applications then it reboots,cannot enter the system.
spida_singh said:
When i select choose form sdcard1 from main recovery menu, i get a wiping cache messages, and then it reverts back to the main screen, same when selecting internal storage.
When using TWRP from a different fasbooted kernel (AndroPlus Kernel for Stock FW / ROM), i get status 7.
Cheers
Click to expand...
Click to collapse
Did you try flashing with CWM-Based Recovery 6.0.4.7 by DooMLoRD?
jsscx said:
delect first sentence in update script leads to success of flashing this rom,it boots up,with animation,but when screen shows starting applications then it reboots,cannot enter the system.
Click to expand...
Click to collapse
Thank you both for your feedback
Recompiled with repo sync
Updated: http://review.cyanogenmod.org/#/q/status:merged+project:CyanogenMod/android_device_sony_z3c,n,z
No more errors when extracting proprietary files.
Did not touch updater script, though, so you find yourself with the same issues.
For those who do not know how to download from free file host servers:
I use Ad block so did not come with any issues, also never had a problem before today with go4up.
Mod edit
why the installer file is .exe to be download, is there any mirror / direct link to download and test this CM12 by .zip file, exe format may sound confusing and i am not comfortable to download it, i am keen to try, thanks.
the site u chose is full of apps crap,which caused many issues yesterday,though it's fast?
---------- Post added at 06:59 PM ---------- Previous post was at 06:52 PM ----------
edcarsky said:
why the installer file is .exe to be download, is there any mirror / direct link to download and test this CM12 by .zip file, exe format may sound confusing and i am not comfortable to download it, i am keen to try, thanks.
Click to expand...
Click to collapse
DONT install it ,click the address below the big download icon,yeah this site is sick,full of fcking apps
MOD please delete thread as I have created devDB project instead.
Thank you
edcarsky said:
why the installer file is .exe to be download, is there any mirror / direct link to download and test this CM12 by .zip file, exe format may sound confusing and i am not comfortable to download it, i am keen to try, thanks.
Click to expand...
Click to collapse
jsscx said:
the site u chose is full of apps crap,which caused many issues yesterday,though it's fast?
---------- Post added at 06:59 PM ---------- Previous post was at 06:52 PM ----------
DONT install it ,click the address below the big download icon,yeah this site is sick,full of fcking apps
Click to expand...
Click to collapse
Uploading file directly on xda: http://forum.xda-developers.com/devdb/project/?id=7198#downloads
No more hosting issues
Thread closed
Thread closed per OP's request.
The new thread can be found here.
Thread closed
Hi,
I am Using LAVA A97 device recently launched. I need to root this mobile to apply some tweaks. I tried various methods like flashing the zip from the SD card and sideload. The error I got always is "Signature Verification Failed". I tried finding custom recoveries and even tried porting custom recoveries but all stopped at the boot image.
Please help me to root this device or port me a custom recovery. I will provide you the files you needed.
Have you tried enabling OEM bootloader setting in developer options?
vshlkmr said:
Have you tried enabling OEM bootloader setting in developer options?
Click to expand...
Click to collapse
Ya I allowed oem unlocking in developer options. But when i boot to fastboot mode and enter command
Code:
fastboot oem unlock
it struck on the boot screen. I have waited for an hour but nothing happened. I just removed battery and rebooted my mobile.
I can give you the stock rom can you make it pre rooted
Please tell me the procedure to add su files in marshmallow system.img and flash it
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
karljsamuel said:
Please tell me the procedure to add su files in marshmallow system.img and flash it
Click to expand...
Click to collapse
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
vshlkmr said:
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
Click to expand...
Click to collapse
I tried the above mentioned steps in my Ubuntu 16.04 with Android Kitchen and Superr's Kitchen. With Android kitchen, I unpacked the system.img and the kitchen made the boot image and made the ro.secure=0. Then I added the necessory files from @Chainfire SuperSU.zip as per the update-binary script mentioned and repacked system.img with Superr's Kitchen. When I flashed modified system.img and boot.img with flash tool.
The superSU app said that su binaries are not installed and it cant install them also it asked me to reroot the mobile phone.
I also tried with Dirtycow exploit also but not worked.
Mobile is running Marshmallow API 23
Can you make me a custom recovery. I followed the steps mentioned in this forum to port a custom recovery but it struck in the boot logo.
The Stock Firmware file Now I have in my mobile can be downloded from Google Drive.
Boot.img Recovery.img and build.prop file is uploaded as Zip to Google Drive
How are you flashing the files back to phone? What software you using? And maybe superuser cannot find the binaries bcoz maybe lava a97 picks it's binaries from someplace else (like maybe /system/bin)
vshlkmr said:
How are you flashing the files back to phone? What software you using? And maybe superuser cannot find the binaries bcoz maybe lava a97 picks it's binaries from someplace else (like maybe /system/bin)
Click to expand...
Click to collapse
Flashed with SPD upgrade tool.
The su binaries and apk files are placed as mentioned by chainfire in the update-binary provided by him for flashing the zip via custom recovery.
It told me to run su --install but the adb shell does not work after customising the rom
karljsamuel said:
Flashed with SPD upgrade tool.
The su binaries and apk files are placed as mentioned by chainfire in the update-binary provided by him for flashing the zip via custom recovery.
It told me to run su --install but the adb shell does not work after customising the rom
Click to expand...
Click to collapse
Is USB debugging enabled?? Also switch the phone to cd rom and install the drivers
While installing the modified system.img it give me error
- exec '/system/bin/sh' failed: No such file or directory (2) -
Even there is no such file in the stock rom. only a file named sh0 was present
I reflashed the rom and adb shell is working properly without the /system/bin/sh file
How to root lava a97
Hey bro I read your thread and also I myself tried many ways to root my lava a97
Did u got any method to root it??
Please tell
karljsamuel said:
Ya I allowed oem unlocking in developer options. But when i boot to fastboot mode and enter command
Code:
fastboot oem unlock
it struck on the boot screen. I have waited for an hour but nothing happened. I just removed battery and rebooted my mobile.
I can give you the stock rom can you make it pre rooted
Click to expand...
Click to collapse
Lava A97 is CortexA7 device
use fastboot tools to flash TWRP and then flash SuperSU.zip
I'm gonna port TWRP for Lava A97 soon
And will test it.
pm me and I'll give you TWRP after success in testing
OK?
---------- Post added at 09:40 AM ---------- Previous post was at 09:35 AM ----------
vshlkmr said:
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
Click to expand...
Click to collapse
Thanks alot bro???
TWRP port test failed
Hey bro i have rooted my lava a97 IPS
Recovery- cyanogen recovery ported by me
And flash super su
Can anyone Provide me the recovery & Su files Please?
---------- Post added at 04:42 AM ---------- Previous post was at 04:40 AM ----------
Mrutunjaya said:
Hey bro i have rooted my lava a97 IPS
Recovery- cyanogen recovery ported by me
And flash super su
Click to expand...
Click to collapse
I Also Want 2 Root My Device Please Can U Help Me?
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
Sometimes Huawei releases an update package without approving it. For instance, my device (VIE-L29C636) is getting a B382 update, but the update isn't approved for installation. Here's how to update to those update packages.
NOTE: Using this method, you can also safely upgrade your device even if it is rooted, or has some files system partitions altered. (Of course after finished this process, your device will become unrooted and any alteration to the system partitions mentioned below will revert).
Prerequisites:
Your device is already running EMUI 5 (do not attempt this procedure on EMUI 4 ROM, as the partition layout may differ, and the various firmware (modem, sensor hub, etc.) may not compatible.
Unlocked Bootloader AND FRP.
Latest TWRP from OpenKirin (more on that, including download link, click here).
Huawei Update Extractor, for extracting UPDATE.APP.
imgtool, to convert the sparse android image into an ext4 raw image file.
Method:
Download your preferred update package from Firmware Finder app (Make sure to select the one which has 'FullOTA' designation on it. The package doesn't have to be a 'PV' package). Choose 'update.zip' and the other zip that has your region name on it (for instance, on my C636, look for the zip which has 'spcseas' on it's name). I will refer this 2nd zip as 'regional zip'.
Extract the 'UPDATE.APP' from both zip archive.
Using the Update Extractor on a Windows PC, Extract BOOT, SYSTEM, PRODUCT and VENDOR partitions from UPDATE.APP retrieved from 'update.zip', and extract CUST and VERSION from UPDATE.APP retrieved from your regional zip. You should end up with BOOT.IMG, SYSTEM.IMG, PRODUCT.IMG, VENDOR.IMG, CUST.IMG and VERSION.IMG.
Convert PRODUCT.IMG, VENDOR.IMG and VERSION.IMG to an ext4 image using imgtool, for example:
Code:
imgtool PRODUCT.IMG extract
Beware of overwriting the converted image. imgtool is hardcoded to output the converted file to 'extracted/image.img' folder. ALWAYS rename the image.img to something like 'product.ext4.img' after conversion.
Reboot your device to bootloader mode. Flash BOOT.IMG, SYSTEM.IMG and CUST.IMG via fastboot. For example:
Code:
fastboot flash boot BOOT.IMG
Reboot your device to recovery mode. Type
Code:
fastboot reboot
and hold the Vol Up button on your device to enter recovery mode.
Upload the *.ext4.img converted earlier to your device (doesn't matter where, but I recommend using a safe place like '/sdcard', or USB OTG or external micro SD card). you can use 'adb push', MTP or OTG to upload/copy the ext4.img files to your device.
for each *.ext4.img files, flash it to the appropriate named partitions in
Code:
/dev/block/platform/hi_mci.0/by-name/*
. You can use adb shell on your PC, and a command line program called dd on your device. For faster transfer, try to adjusting the block size to 8M. Example commands (execute from adb shell):
Code:
dd if=/sdcard/product.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/product
dd if=/sdcard/vendor.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/vendor
dd if=/sdcard/version.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/version
Exit TWRP (reboot to system), wait for several minutes for the system to build up it's AOT cache, and enjoy your new EMUI 5 with newer security patch, newer kernel and various features and bug fixes .
EDIT: I apologize that IMGTOOL isn't available in binary form for windows. You can try to use Linux virtual machines to run the IMGTOOL. Any modern GNU/Linux distro should be able to run the IMGTOOL.
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
In my case (upgrading from VIE-L29C636B370 to B382), it doesn't erase user data at all. And there is no reason it should erase the data.
But as always, backup your data before performing this procedure, in case something goes wrong.
How to extract product version Vendors use imgtool..
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
I'm sorry, I forgot to mention that IMGTOOL is only available as binary in GNU/Linux OS. I think you have to use a VM running a GNU/Linux distro to extract product.img, version.img and/or vendor.img using the IMGTOOL.
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
faakher said:
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
Click to expand...
Click to collapse
Good Evening i had tried the guide but in my VIE-L09 doesn't work. What can i do? Bootloop infinity
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
great post, but as a simple user, i have no idea how to do this steps.
i have a p9 plus c605 b361 and rooted, and i cant update to anything
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
heeey...anyone here ?!!?
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
AYahooo said:
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
Click to expand...
Click to collapse
what this is ?!
---------- Post added at 06:51 PM ---------- Previous post was at 06:45 PM ----------
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
maahmd said:
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
Click to expand...
Click to collapse
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
Tecalote said:
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Click to expand...
Click to collapse
I know this but I have a version vie-l29c185 So I do not know which version I chose
maahmd said:
I know this but I have a version vie-l29c185 So I do not know which version I chose
Click to expand...
Click to collapse
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Tecalote said:
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Click to expand...
Click to collapse
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
maahmd said:
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
Click to expand...
Click to collapse
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Tecalote said:
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Click to expand...
Click to collapse
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
maahmd said:
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
Click to expand...
Click to collapse
I don't know what you mean now
Download the Nocheck Recovery for L29 from the Link I give you
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
and do the instructions from the OP
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But with the RIGHT Firmware for your VIE-L29 device (3 zips from Firmware Finder /FullOTA)
After updating Firmware Bootloader is closed and Root is gone.
You have to open again (Factoryreset low-level wipe - if it doesn't do 100% do it manually from settings /advanced settings /backup restore /Factoryreset with wipe of internal storage - this is important! ) and flash TWRP and Root again