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?
Related
Sorry for the newb-ish question. I'm in a mad rush to build my FM app and would prefer not to have to research this issue for hours.
I have my FM app running on Blayo ROM, using btipsd_cli, and I think it should then work on the stock ROMs. AFAICT they also include btipsd_cli.
So I want to test on a stock ROM. Which one should I use ? I'm avoiding the RUU's because I don't want to have to mess with Windows etc.
So I'm looking at: OTA_Legend_Froyo_S_Vodafone_UK_3.14.161.1-2.05.161.1_R_P_release_135177_156984k4i146wit81sj23a.zip
But the embeded firmware.zip includes an HBoot and radio and recovery.
I don't want to lose my S-Off, or my CM recovery.
Can I do this ? What's the easiest/safest way ? Or any other stock ROM I should use ? Perhaps I should test with the oldest ROM and the newest ROM.
Thanks much !
Sure m8. Just extract whichever img you want and flash it via fastboot. I'm not sure about system.img. Some guys reported that flashing system.img doesn't actually work. In that case put it on /sdcard, fire up CWM, format system partition, mount it and then inside adb shell unyaffs the image into /system dir.
EDIT: Ahh one more thing. You can't just install any OTA you want. What OTA does is binary patching of existing files. That said it means you have to have binaries that actually match to their patches but I guess you knew that before
Sent from my HTC Legend
BlaY0 said:
Sure m8. Just extract whichever img you want and flash it via fastboot. I'm not sure about system.img. Some guys reported that flashing system.img doesn't actually work. In that case put it on /sdcard, fire up CWM, format system partition, mount it and then inside adb shell unyaffs the image into /system dir.
EDIT: Ahh one more thing. You can't just install any OTA you want. What OTA does is binary patching of existing files. That said it means you have to have binaries that actually match to their patches but I guess you knew that before
Click to expand...
Click to collapse
Thanks BlaY0 !
No I didn't know about the patching of files. So that's what the *.p files are for... Yuck, that's messy IMO.
I WOULD have known if I spent much time in this area but I haven't. A few months back I finally had my phone in a nice state and haven't looked back. It was VERY painful doing all that, and at least twice I messed up badly and had to restart. So I don't want to repeat that.
I haven't figured out how all the partitions/image files interact, so I won't go down that road at this time. I'm guessing it may not be possible to go back to stock temporarily and then revert to the other ROMs easily.
So for now I think I'll continue to use your ROM as a proxy for a stock ROM and hopefully my app will work as well on stock ROMs. BTW, I'm now running your new 8.4 and it's working very nicely thank you...
Those .p files are standard bsdiff patches. At least they should be, but HTC once again made some internal changing to that so I was unable to manually apply those patches on my PC.
If you are S-OFF which I believe you are, all you have to care about are boot.img and system.img. 1st is image made of kernel + initrd and 2nd is basically yaffs2 image. 1st can be flashed with flash_image and 2nd can be unpacked with unyaffs (after you format system partition and mount it on /system via CWM). All needed tools are available in CWM recovery and they are also part of AOSP and are compiled separately each as its own bin. Flashing can also be done via fastboot, but I'm not sure about HTC's system.img as I'm not S-OFF. You should try that.
Sent from my HTC Legend
I can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..
I used the version available on Rootzwiki... not sure if thats the answer you wanted. I'm running 4.0.3 ICS on my wifi XOOM OC to 1.54. No FC's, reboots or anything of the sort. You'll need to be sure that you have su-install.zip, and other img files needed. As I said, you'll find them all on the rootzwiki website under xoom hope this helps, if not good luck.
You are talking about two different things here. I don't know where to start here you're all mixed up. There are several ways to flash a ROM, you can fastboot flash the .img files such as what you are referencing to. Or you can flash an update .zip file from recovery. The way you flash the ROM depends on the source, if its a bunch of *.img files you use fastboot, if it's a *.zip file you use recovery. Just follow the directions given for installation that are provided with the ROM you are downloading.
sboehler said:
I can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..
Click to expand...
Click to collapse
Hello, and welcome to XDA! =] Anyways on with your question. There are two ways to flash a ROM to your xoom. One being fastboot/adb, where you use the command line on your computer to send commands to your device and make it do stuff. This is where you use system.img, boot.img, recovery.img.
The second, is CWM (ClockWorkMod recovery) This, as far as im aware, is the most common way. This is where the .zip's come in. Because you take the .zip you put it on your external SD card. boot into recovery (after flashing CWM of course) and flash the rom. CWM is nice because you can also make a 100% snapshot of your internal memory state via making a nanodroid back up. That way if anything messes up you have a 100% backup you can restore at anytime if you need it.
In a nutshell, You use *.img files with fastboot and .zip files with CWM.
Anyways. If you're new to rooting. Please check out these two threads, They'll help you get started. =]
Xoom Heaven: Root+Non Root Users Are Welcome!
[Guide] Setting up and using adb/fastboot-unlock, flash custom recovery & root
The second guide I did use to flash my own zoom so I can assure you it does work.
Hi,
I don't know if this is the correct section to get this question answered, but I'll try:
I have a new tablet, which is not really known at the moment. I managed to root it and next step would be to port Clockworkmod Recovery to it. Since I only found guides where I always have to repo sync the entire CyanogenMod github (which is 19GB+ as I heard), I searched for an alternative where I could save some traffic
I found a clockworkmod recovery from another tablet and wondered if it was just possible to unpack it, modify the recovery.fstab and repack it again.
Is this possible or do I have to modify more than the recovery.fstab? If yes, could you point me to the right direction?
Regards
dump your stock recovery
unpack the stock recovery and save the vold.fstab somewhere.
upload the stock recovery here
http://builder.clockworkmod.com/
get the output and flash`it
if the key`s are not working, unpack the new cwm, and the old recovery, and put the keys from the old recovery.
if you get some mount points erros, you will have to upload also the saved vold.fstab on the clockwork site when you cook the image.
if this does not offer you a good result, you will need to find a similar device (processor, resolution) that has allready a cwm, and try it
the recovery file is ramdisk/sbin/recovery
Hi,
thanks for showing me a way. Unfortunately builder.clockworkmod.com says it didn't find Android magic. This makes sense, as the image is a uImage with lzma compressed data inside. It seems koush's builder handles only "plain" recoveries...
Bad luck
I guess I'll try your second advice and search for a CWM for a similar device, unpack it, replace the fstab file and repack it again.
Thanks again!
hello I have made the porting on http://jenkins.cyanogenmod.com/job/recovery/lastBuild/console
I end up having a zip archive, how can I make my tablet to read that. I have installed cwm recovery and it is rooted. Let me know how can install it and replace my recovery with this.
BTW I have the original stock firmware of my tablet.
let me know thanks
I wonder whether there is help for someone who thought he knew how to flash a kernel but apparently is deluded. I have the original nexus seven Wi-Fi tablet android version 4.3 build number JWR66V. The system still wants to update me to 4.3 because I ripped some files out of the cache directory to prevent OTA updates. I have both fastboot and adb. I have read the stickies about flashing.
The phone is rooted and the bootloader is unlocked. I use TWRP custom recovery, and it's a good thing, because I solidly bricked myself up just trying to get my lollipop. I know there are tools to root a nexus seven even with stock lollipop, so I thought I'd upgrade my phone to stock lollipop and then use one of those methods. I tried both the stock lollipop kernel and the one provided by chain fire, which I understand is rooted already. (I'm assuming upgrading to lollipop will lose me my root, unless I want to recover back to 4.3.)
I tried to do these things a couple of different ways. When I tried fast boot, I got the message "error: neither -p product specified nor ANDROID_PRODUCT_OUT set". There was a YouTube video suggesting how to deal with this error message. I'm pretty sure I followed the instructions but no go. (I was using the "flash all" command.) This was after I had put the file containing lollipop in the directory, both zipped and unzipped (so that I had an .img file instead of a zip file). I tried using both the zip file with all of the lollipop partitions and the system image file individually. No go. I also had a message that android-info.txt could not be found, even though it was in the same, working directory.
I could be wrong but I don't think you can install a complete updated kernel from a file on the device. I think that works only with update.zip.
I'm still thinking fastboot is my best bet, but there are dependencies apparently and I don't know what files to include in its directory. Then, am I wise to go to stock and then root, or should I simply flash the stock kernel already rooted? I assume that's what chainfire is providing, correct?
I notice the lollipop official ROM nor Chainfire’s supposedly-rooted image have any file named nakasi. I have only .img files, no .zip files.
I found a dozen sets of instructions on how to flash a kernel but something I need is missing from all of them. Does anyone know what it is or can anyone offer some helpful advice?
Thank you,
Leon M.
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: