Ok so I decided that I wanted to see what all the Froyo fuss was about, so I started getting my phone ready following instructions on the site. I own a Samsung i-9000m (in canada from bell - actually sasktel but we get phones from bell). anyways, I figured i'd do a rom manager backup. I did one, had some trouble with my phone and now I need to do a restore. Reading on the web they all point to an update.zip file. All I have is the following on my internal SD
ClockworkMod\2010-11-24-14.32.54\ and the following files in that folder:
cache.img
datadata.img
system.img
data.img
nandroid.md5
I tried restoring from rom manager but it doesn't find any files, I've booted into recovery but doesn't recognize the img files......any help would be amazing. Am I missing a step, google is no help
loooks like i needed the recovery update.zip file i'm assuming.....for some reason I didn't have it in the clockworkmod folder....
I have spent several weeks working on this (reading thread after thread) on modifying stock firmware and im running into a problem. I more or less want to know if what i want to do is actually possible. I have downloaded the original .tar.md5 firmware image, opened with 7zip and "extracted" the .tar file (more or less just removed the hash) and then extracted the .img files from the .tar file. I have unpacked/mounted/modified/repacked using several methods (dsixda kitchen -which havent been able to work around adding the java path since after i add the path cygwin thinks im missing clean app until i remove the path in which case i get an error saying it cant find java/ i have tried mounting using ext4_utils in ubuntu) my issue arises when i take my modified and repacked system.img file i cant get it to work either by 1. zipping it in a .tar with the other .img files and flashing with odin, 2. zipping system.img alone into a .tar and flashing with odin, 3. installing cwm/root and flashing the system.img)
More or less my question is
1. is it possible to modify the stock firmware and load it onto the tablet without rooting
2. can system.img be flashed by itself or does it need the other .img files in the same .tar
3. does the tar file require being signed before flashing even with CWM recovery and root already on the tablet?
I have used these forums for a while to find answers, but i am new to posting, i havent needed to post a question until now since i spend as much time researching as i can before bothering people with a question (i like to figure stuff out and hate to admit defeat) Thanks in advance for the help despite my noobishness
Hello everyone,
I'm new to low-level Android hacking, so I guess I need some help.
What I am trying to do is getting the stock files from an LG E400, and modify 1-2 things, repack, flash, and see if it works for me.
My first step:
1) Rooting the LG E400
2) Flash CWM Recovery
3) Create a backup
4) Get boot.img from the backup.
So I have a boot.img (which I think is stock, because rooting does not modify the contents of the boot image as far as I know.)
After that, I followed this tutorial to extract the kernel and the ramdisk.
I used a hex editor for this. I saved the kernel and the ramdisk as separate files, and I tried to gunzip the ramdisk. That seemed to work. However, after that, when I try to run cpio on the file, I get a lot of "Malformed number" errors, and only two empty folders are extracted.
And that is where I'm stuck at.
Are the LG phone boot.img-s encrypted somehow? Am I doing something wrong?
If anyone can help me, I would be really grateful.
Thanks in advance
Hi guys, I'm fairly new to this whole ftf system so I am having a bit of trouble extracting the boot.img out of it. I am working on a pure stock 6.0 ROM but need the boot.img extracted, I already got the system just need boot. I have tried using flashtool to convert the boot.sin to a boot.img and it tried making a 450 terabyte file when I clicked dump data. Any advice would be great. I also just tried renaming extension but that yielded a black screen upon immediate boot.
As a side note I don't think this is even going to work because starting from 6.0 and above the file system changed from system folder to the new format with the .dat files and that really makes things even more complicated than they already are.
Hello, I´m a newbie on this matters.
I´m trying to cook a custom rom from a stock rom for this android pc with RK3328 chip. The rom I´ve downloaded is an 8.1 android image version, an the app I used is RK3xxx_firmware_tools_5.78.35.00 that I´ve downloaded from the chinagadgetsreviews.
When I uncompressed the rom.img, system.img and boot.img with this app, I got three folders called: "Android", (with a "Image" subfolder with the boot.img, kernel.img, recovery.img... and a package-file file), "boot", (with a boot.img.unkrnl.dump folder who contains many folders and .rc files, boot.img.unkrnl.cfg file and boot.img.cfg file), and "system", (with the app, etc, bin... folders and the build.prop, compatibility_matrix.xml, manifest.xml and vendor files). Also got a system_statfile with these 3 folders.
I´d like to remove some apps from this rom and include others, and if it is possible, changing the recovery.img from it. The recovery partition has 64MB of size, and the original recovery.img has only 9057 KB. The recovery.img I´d like to install is the twrp_RK3328_v3110 adapted for this chip (who has only 5258 KB), but I wonder if I could simply replace the original recovery.img with this twrp one on the "Image" subfolder I said (renaming it first to recovery.img) and after repack the rom, or, like I'm afraid, more things have to be done.
Thanks a lot in advance.
Anybody doesn't know how?
porkero said:
Hello, I´m a newbie on this matters.
I´m trying to cook a custom rom from a stock rom for this android pc with RK3328 chip. The rom I´ve downloaded is an 8.1 android image version, an the app I used is RK3xxx_firmware_tools_5.78.35.00 that I´ve downloaded from the chinagadgetsreviews.
When I uncompressed the rom.img, system.img and boot.img with this app, I got three folders called: "Android", (with a "Image" subfolder with the boot.img, kernel.img, recovery.img... and a package-file file), "boot", (with a boot.img.unkrnl.dump folder who contains many folders and .rc files, boot.img.unkrnl.cfg file and boot.img.cfg file), and "system", (with the app, etc, bin... folders and the build.prop, compatibility_matrix.xml, manifest.xml and vendor files). Also got a system_statfile with these 3 folders.
I´d like to remove some apps from this rom and include others, and if it is possible, changing the recovery.img from it. The recovery partition has 64MB of size, and the original recovery.img has only 9057 KB. The recovery.img I´d like to install is the twrp_RK3328_v3110 adapted for this chip (who has only 5258 KB), but I wonder if I could simply replace the original recovery.img with this twrp one on the "Image" subfolder I said (renaming it first to recovery.img) and after repack the rom, or, like I'm afraid, more things have to be done.
Thanks a lot in advance.
Click to expand...
Click to collapse
All I can say is, extract the ROM until you get to the system folder then look for /system/app and /system/priv-app folders, delete the apps you don't want and add the ones you want. Then, remove your recovery.img and place your TWRP.img in its place then repack everything into the file format that you need then try flashing it.
If that doesn't work, you'll have to start doing your own research to get your ROM put together correctly.
Sent from my SM-S767VL using Tapatalk