Ok, I have a rom there's a system.img and boot.img. Previously I took someone else's update.zip deleted the boot.img and system.img from their update.zip, replaced it with my boot & system img and it worked.
Now I was given a new rom from a manufacturer and when I try swapping the boot & system this time, and applying the ROM it doesn't seem to work.
What am I missing here? If I up the system.img and boot.img can someone create the update.zip for me?
Or can you give me an update.zip file where I can just drop in my boot & system.img
Are you signing the update.zip afterwards?
What error does the logcat give you?
hmm. Not familiar with log cat or signing.
Let me add some additional information that may help.
There's a tablet manufacturer that is testing their ROM. Unfortunately they didn't give it to me in update.zip format.
They gave me a bunch of files that include boot.img and system.img and there's a recovery.img (as well as a bunch of other files).
The device is a tegra 2 device.
Previously I loaded the VeganN rom which is designed for the Viewsonic G tab. Though my device isn't a Viewsonic G tab the rom worked (with the exception of certain things like camera etc).
The tablet I have, the manufacturer sent me a "recovery rom". Basically it was a stock Android rom, even that rom didn't really work all too great but I was able to install that rom installed using the following method:
Took the Vegan ROM's update.zip file, delete that system.img and boot.img and replaced it with the one sent to me by the manufacturer. That worked.
Now the manufacturer sent me an updated package which also includes a boot.img and system.img and this time the system doesn't boot.
I suspect it has something to do with my update.zip file. For whatever reason it worked before (replacing the files) but didn't work this time.
Still need signing? The manufacturer wanted me to use Ubuntu and run a script with a .sh extension and said that would flash the unit with the new ROM.
I'm not a Linux expert but I did install Ubuntu as a VM but I couldn't figure it out. I figured if I had an update.zip I'd be in business.
Any guidance you can provide is appreciated.
Well, If I replace just the system.img from someone else's update.zip it boots but there seems to be some quirks so I'm guessing the issue I have is replacing the boot.img any ideas?
I just receveid an OTA update, but the installation stuck because the system is rooted.
I found the update.zip file on my Handy, but it contains some directory (Meta-inf, patch and system) and a big file update.app that I believe contais all the update file.
Is it possible to extract the file from update.app and then create an update that can I launche from TWRP? And if so how could I do it?
Thanks
You can't.
flash back a stock recovery.
After ulocking bootloader and root the OTA didn't work with original recovery that's why I wanto to create an update that works with TWRP
did you try?
ItalianWolf said:
did you try?
Click to expand...
Click to collapse
Yes I reinstalled the original recovery that you can find in t he root package and I completely unroot the phone using the unroot command in SuperSu.
Then I launch the update but after reboot it stuck at 11%, so I create the dload folder in my handy memory and copied there the content of update.zip and then forced the update. In this case, after reboot, it load until 99% that it reboot, but the installed version is still the 170 and not the 188.
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
ItalianWolf said:
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
Click to expand...
Click to collapse
What does here mean?
Which thread?
Thanks
Harlock1978 said:
What does here mean?
Which thread?
Thanks
Click to expand...
Click to collapse
Sorry, forgot link: http://forum.xda-developers.com/p8l...-lite-android-6-0-marshmallow-t3305550/page40
You need the Huawei Update Extractor Tool, and do the following:
Load the UPDATE.APP file inside the HUET
Extract boot.img, system.img, and cust.img, from UPDATE.APP inside the HUET
Flash the respective files via Fastboot
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
AmINoS007 said:
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
Click to expand...
Click to collapse
If you have to, flash the B052 recovery... you can always flash the Marshmallow recovery if it doesn't let you update.
I only flashed boot.img, cust.img, and system.img, when I upgraded; didn't flash Marshmallow's recovery at all.
Don't think you can even get OTA updates on the Marshmallow beta anyway (even via a normal bootloader-locked device).
Sorry for my late answer but I was travelling only with a Mac and I couldn't use Huaweu Update extractor.
This are the file that you can find in UpdateApp 188:
00.SHA256rsa.img
01.crc.img
02.curver.img
03.verlist.img
04.efi.img
05.fastboot1.img
06.boot.img
07.recovery.img
08.recovery2.img
11.cache.img
13.dtimage.img
14.dsp.img
15.fastboot.img
16.hifi.img
17.mcuimage.img
18.modemimage.img
19.modemnvm1.img
20.teeos.img
21.trustfirmware.img
And also the following directory:
META-INF
patch
system
Which file should I install, I didn't find a system.img and there are two different recovery
Thanks
You should not install any OTA with TWRP...
Flash back the stock recovery, update, then flash the twrp again, it's way easier and more secure, than doing a flashable zip from an OTA update without knowing what to do with the file within.
The OTA updates usually doesn't contain the SYSTEM.IMG file you are looking for, it contains individual files and scripts to patch up the current system partition to work with the new update.
From the two recoveries you should use the RECOVERY.IMG (the one without the 2 in it).
But again, I do recommend to flash the original recovery(not the one in the update), do the update, and put twrp back.
Where can I find the original recovery from ALE-L21C432B170, so that I can flash the original recovery again?
TIA
I found the original recovery and flashed it then I did a complete unroot and tried again to do the OTA update but it stopped at 11%.
Is there a different way to update?
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
johnnyphive said:
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
Click to expand...
Click to collapse
Well, for starters do NOT take the OTA. It will either fail or boot loop your phone. Due to the fact you have a modified boot.img you will need to update manually using fastboot with the full image. Re-apply the modified kernel after you finish updating the partitions, but BEFORE booting the first time. You can follow most guides on how to manually update a full image using fastboot, just add the step of flashing the modified kernel before booting.
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
johnnyphive said:
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
Click to expand...
Click to collapse
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
v12xke said:
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
Click to expand...
Click to collapse
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
johnnyphive said:
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
Click to expand...
Click to collapse
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
v12xke said:
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
Click to expand...
Click to collapse
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied?
Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
johnnyphive said:
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied? Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
Click to expand...
Click to collapse
I don't think you can flash EX kernel from now on. I think you have to use a modded boot.img that will contain his kernel/ramdisk. This is my guess. You really should be getting your information in the dedicated thread where everyone is actually installing and using it. Google "oreo 4 core" and you will find the XDA thread is the first hit. Good luck. :good:
Hello guys!
For the may update, a friend sent me a zip archive containing the stock boot.img that I used to flash in twrp when flashing kernels. Now that june update came up.. how can I create one in order to do the same thing? If it's helpful, it had a META_INF folder in it. Thank you in advance!