Hello all.
Sorry if my question is trivial, but I haven't found any answer by searching the forum.
The problem is the following: I have a custom kernel zImage (which has some usb drivers enabled) and I am trying to find a way to flash it to Samsung Galaxy Tab 10.1 P7500.
I rooted the device, installed clockworkmod bootloader and able to install kernels prepared by other xda-developers like this one:
http://forum.xda-developers.com/showthread.php?t=1138167
But I can't get my head around the process of creation of zip package for ClockWorkMod. I haven't found any doc or manual how to do it.
I tried to replace zImage in .zip package from the above link and updated a hash value in Manifest file. But it didn't work.
the ClockWorkMod Recovery just writes:
-- Installing: /sdcard/kernel-updat.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
---
Hope somebody faced similar problem.
Any tip will be hugely appreciated.
Andrew
Just replace the zimage without changing anything else. Or compress it in tar format and flash via odin!
Sent from my amazing 10.1 galaxy tab
still not working
Panos_dm said:
Just replace the zimage without changing anything else. Or compress it in tar format and flash via odin!
Click to expand...
Click to collapse
Unfortunately replacing zImage doesn't work. Even if I unzip and zip the original package without changing anything the ClockWorkMod says "Installation aborted" when I try to install zip I created. I have tried to use 3 different zip-programs with the same result.
About the odin approach. Do you have a link at hand that explains how to do it ?
Huge thanks.
Andrew
one solution to the problem
This is how I solved problem with "Installation aborted":
1) Take a working rom zip file with zImage from here
droidbasement.com/galaxy/kernels/2636/26/p4-ux/3.2/boot-cm_2636.4_p4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip
2) create folder called 'kernel' in the same directory where zip file is.
3) copy your own zImage to the 'kernel' folder
4) type
zip -r orig-boot-cm_2636.4_p4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip kernel/
This replaces zImage in the .zip archive with your own zImage
So basically you don't need to recreate zip file, you need to replace zImage in the existing zip.
flashing with ODIN
Panos_dm said:
Just replace the zimage without changing anything else. Or compress it in tar format and flash via odin!
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
Hey Panos_dm, do I need to tar zImage only or anything else ?
I tarred zImage and tried to flash it with odin, but failed.
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
Do I need to have pit files for P7500 ?
I don't know what exactly goes non with odin, but I don't think that you need a pit file... I am no expert though. What I said about swapping kernels in a working zip, does the job for me. I want to try to flash stock recovery and kernel through this method, so I will be able to officially update to ics, without using Odin and increasing custom binary counter
Sent from my amazing 10.1 galaxy tab
Panos_dm said:
I don't know what exactly goes non with odin, but I don't think that you need a pit file... I am no expert though. What I said about swapping kernels in a working zip, does the job for me.
Click to expand...
Click to collapse
Thanks.
Can I ask you to post a link to zip and kernel sources that you used? It would be really helpful to me.
My kernel image that I built and inserted in working zip doesn't load. And I don't have a clue how to diagnose a problem since there is no access to boot log.
OK.. I used overcome rom and stock zimage and it worked. I haven't built a kernel myself though...
Sent from my amazing 10.1 galaxy tab
x-nordic said:
This is how I solved problem with "Installation aborted":
1) Take a working rom zip file with zImage from here
droidbasement.com/galaxy/kernels/2636/26/p4-ux/3.2/boot-cm_2636.4_p4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip
2) create folder called 'kernel' in the same directory where zip file is.
3) copy your own zImage to the 'kernel' folder
4) type
zip -r orig-boot-cm_2636.4_p4_ux_hc32-oc-xtra-vfpv3-d16_fp-010912.zip kernel/
This replaces zImage in the .zip archive with your own zImage
So basically you don't need to recreate zip file, you need to replace zImage in the existing zip.
Click to expand...
Click to collapse
I used this kernel image and flashed it to see what happens. It loads but the screen is scrambled. I followed your step to replace my zImage, but I was unable to flash the replacement. I used recovery mode to do it.
Any other solutions or tips to flash a custom zImage on P7510?
hsnm said:
I used this kernel image and flashed it to see what happens. It loads but the screen is scrambled. I followed your step to replace my zImage, but I was unable to flash the replacement. I used recovery mode to do it.
Any other solutions or tips to flash a custom zImage on P7510?
Click to expand...
Click to collapse
Someone manage to find a solutions ?
Related
People please tell me how to repack zip to tar....for purpose of flashing....
I tried 7zip but it did'nt worked it just puts file in tar format....
i want full details?????
Hi
download- 7Zip.
http://www.7-zip.org/
Enjoy !
avetny said:
download- 7Zip.
http://www.7-zip.org/
Enjoy !
Click to expand...
Click to collapse
Buddy i already told that 7zip just puts in tar format but do not convert the files in the tar components(Mdem,etc)
You might explain what you are trying to achieve by putting a zip into a tar .
Are you trying to make a CWM zip file flash-able via Odin .
jje
Can it be done ?
Lol, that sounds cool. Anyway, I think I'll keep flashing tars with odin and zips with CWM because what you sugest scares the **** out of me. Anyway I'll keep reading this thread out of curiosity.
so your trying to make an update.zip file into an odin.tar file to flash in pda?
I think he ment if you download (for example) new clockwork recovery version in zip format (ment for flashing thru phone recovery) can it be transformed into .tar (ment for flashing thru odin) !
I would also like to know this.
Sent from my GT-I9100 using Tapatalk
Tar To Zip
I dont know why you are trying to flash a zip via odin by converting it CWM works just fine if u have the latest kernel. I did find some old cwm kernels were not seeing zip files on my sd card make sure you have the latest. From here K13 or k14 at http://forum.xda-developers.com/showthread.php?t=1103399 bottom of the page worked for me.
im curious about this, ever since i rooted and flashed my kernel, i cant properly install ANY CWM roms. on aborts drring verification. I was consierding repacking the ZIP and flashing with ODIN.... just annoying i cant flash any of my roms
Thats usual if CWM is 3e not 4e .
jje
I would also like to know if its possible to repack cwm .zip file into ODIN .tar?? Why? I dont want to have root. I tried with yaffey-v0.2 but for now, no luck.
Only problem is to make a working system.img. Tar package can be done with commands in cygwin or in Samsung tool kit...
Help anybody??
hey gus
can some one help me with help me with installing firmware in samsung S3 1747 plizz, i have downloaded different firmware but it fails during installing.
mutayoba said:
can some one help me with help me with installing firmware in samsung S3 1747 plizz, i have downloaded different firmware but it fails during installing.
Click to expand...
Click to collapse
You are in the S2 Forum here. Which version of odin and which FW are you trying to flash? Whats the error message you get?
Yes it can be done and it's pretty easy to do. Google is you're friend. I've converted devil recovery and also modems and all work fine with odin.
I wanted to make an odin flashable tar of the stock param.lfs posted in Entropy's Return/Unbrick to stock thread. I made the tar file using terminal on my phone, as I have done in the past, but I did it wrong, and when I tested it, the flash failed and now my phone boots to the phone-!-pc screen.
I looked in the tar, and I had built it with the param.lfs in a directory named sdcard. Doh. So I tried to create the tar using 7zip on my Windows pc, and the resulting file is built correctly, but when I tried to flash it, the flash froze on param.lfs. So I don't know if the tar I made with 7zip is bad, or what.
Shouldn't it be possible to just tar the param.lfs file and then flash it in the PDA slot? I should be able to get the phone back by flashing just the param.lfs, shouldn't I? But now I don't know if I can make a working Odin flashable tar on Windows.
So if someone can post an odin flashable tar of Entropy's stock param.lfs, that would be helpful. Thanks.
creepyncrawly said:
I wanted to make an odin flashable tar of the stock param.lfs posted in Entropy's Return/Unbrick to stock thread. I made the tar file using terminal on my phone, as I have done in the past, but I did it wrong, and when I tested it, the flash failed and now my phone boots to the phone-!-pc screen.
I looked in the tar, and I had built it with the param.lfs in a directory named sdcard. Doh. So I tried to create the tar using 7zip on my Windows pc, and the resulting file is built correctly, but when I tried to flash it, the flash froze on param.lfs. So I don't know if the tar I made with 7zip is bad, or what.
Shouldn't it be possible to just tar the param.lfs file and then flash it in the PDA slot? I should be able to get the phone back by flashing just the param.lfs, shouldn't I? But now I don't know if I can make a working Odin flashable tar on Windows.
So if someone can post an odin flashable tar of Entropy's stock param.lfs, that would be helpful. Thanks.
Click to expand...
Click to collapse
I believe 7zip creates bogus tars in Windows.
Try cygwin - or use Heimdall to flash
I was pretty sure that 7zip made bad tar files. I also downloaded peazip, and found that it also makes bad tar files.
I found a good flashable I777 stock param.lfs in Connexion2005's Custom Boot Screen thread. I had never looked inside his attachment and had assumed it was a modified param.lfs. I used it to flash my phone back successfully.
Hey guys,
I'm a total noob at a lot of this so I need some help. I've rooted my Sg2 and am now attempting to flash a kernel with CWM so that I can start checking out some of these ROMs. Problem is, whenever I download the kernel file, I see no .tar file for me to be able to flash via Odin. All the how-to videos show a .tar file available for flashing but any kernel I download from the forums, none seem to have the .tar file included in the zip. I only see is a META-INF and a zImage file which help me in no way. What am I doing wrong?
Any help is greatly appreciated.
greystealth said:
Hey guys,
I'm a total noob at a lot of this so I need some help. I've rooted my Sg2 and am now attempting to flash a kernel with CWM so that I can start checking out some of these ROMs. Problem is, whenever I download the kernel file, I see no .tar file for me to be able to flash via Odin. All the how-to videos show a .tar file available for flashing but any kernel I download from the forums, none seem to have the .tar file included in the zip. I only see is a META-INF and a zImage file which help me in no way. What am I doing wrong?
Any help is greatly appreciated.
Click to expand...
Click to collapse
A kernal is zImage, however unless I'm wrong you don't want to flash a non stock kernal using Odin. I thought this would increase flash counter. Unless it is mobile odin i believe. However you could try this sticky and hopefully it will help...
http://forum.xda-developers.com/showthread.php?t=1311081
Thanks but no luck. That's just basically a way of flashing without your machine. You still need the correct file extension in order to flash. Tar is what I'm looking for. I'm not sure why this has become so difficult. I know that I must be doing something stupid. Any help anyone else?
codeworkx has a kernel, stock with ClockworkMod Recovery 5.0.3.2 that is a tar here.
The zedomax root CWM kernel, which you can download from this thread is also packaged as a tar for Odin.
creepyncrawly said:
codeworkx has a kernel, stock with ClockworkMod Recovery 5.0.3.2 that is a tar here.
The zedomax root CWM kernel, which you can download from this thread is also packaged as a tar for Odin.
Click to expand...
Click to collapse
That helps a LOT! Thank you!
I flashed my galaxy s ii GT I9100 with 4 files PDA, PHONE, CSC and PIT files. My phone flashed perfectly without any errors, but when I tried to flash it again with a single PDA file I cannot flash it popping up an error. Is that any one know how to fix this problem
Thank You..
Hi,
what error?
never had any error with single file flashing
greetz
Did you forget maybe to un-pack it?! couse when you download it, it is into a .RAR file....however: What's the error?
[email protected] said:
I flashed my galaxy s ii GT I9100 with 4 files PDA, PHONE, CSC and PIT files...
Click to expand...
Click to collapse
I think he unpack it, but i can't help you, because i flash only through CWM or Mobile Odin Pro.
MFG Chabstyle
flash problem
I unpacked the file and i put it in to PDA field and flashed it, but it gives me an error "fails" . Previously i flashed it with 4 files including pit file it flashed sucessfully "pass". But this time i don't have an pit file. Is it causing this matter I means the pit file?
What should i do to re flash my phone through odin?
Thank you friends
.pit file is ONLY for repartition, NOT for normal flashing!
[email protected] said:
I unpacked the file and i put it in to PDA field and flashed it, but it gives me an error "fails" .
Click to expand...
Click to collapse
What is the extension of the packed and upacked files?
Packed - zip, rar; unpacked - tar, md5; unpacked firmware file - img, no extension.
It's happened to me before and it's been a dodgy download try downloading it again might help
Sent from my resurrection remixed galaxy s2
This guide is to help those who may want to have more data storage including system partition for much more.
NOTE: DOING THIS WILL DEFINITELY VOID WARRANTY AND ANYTHING THAT HAS TO DO WITH IT. I WILL NOT BE HELD LIABLE SHOULD
ANYTHING GO WRONG.
THERE HAS BEEN REPORTED SUCCESS SO FAR BUT SHOULD YOU END UP WITH AN EXPENSIVE PAPERWEIGHT, THAT IS YOUR OWN DOING. PROCEED WITH CAUTION.....YOU ARE WARNED.
I HAVE PERSONALLY DONE THIS WITH SUCCESS. BELOW IS IMAGES AFTER I AM DONE WITH EVERYTHING.
PRE-REQUISITE
PATIENCE.............LOTS OF IT INCLUDING A STONE COLD HEART TO GO THROUGH THIS
A samsung S2 (i777/attain......to be more precise)
Backup, Backup, Backup...........that includes the phone internal memory.
Acceptance to loose everything stored in the phone internal memory.....if you need them, perform the step above.
A couple of files which i have provided the links to in the procedure and also below the post. Please use only what is provided here. Thanks.
PROCEDURE
1. Enter download mode (NOT through the reboot menu.)
Rather, hold in volume up and down and then while doing so plug in the usb cable to the phone from the computer.
2. Use Odin to install the full Samsung UCMD8 release (Already has pit file).
3. Flash the downloaded stock rom above using Odin.
4. Reboot to recovery and factory reset when done.
5. Boot device, install framaroot, enable usb debugging before rooting device.
6. Install mobile odin. Reboot.
7. In mobile odin, install new kernel w/ recovery (since this method is for i777, you can use Shift kernel....which i used, need to extract only the "zImage.img" file from the .zip file, if file is named something else rename it to "zImage" and place it on the device for Mobile Odin to read.
8. In Mobile Odin, install the modded .pit file attached below. Thanks to [-Stash-]
Read more about the partitions here and here.
NOTE: Using odin for pc for STEP 8 is also very much working.....espercially for those having issues flashing pit file with the mobile odin version.
9. Reboot to recovery; format / wipe partitions (this includes system, data, internal sd, cache, dalvik).
10. If internal cannot format or gives error, connect phone to pc and mount storage, you can then format as fat32 from windows or whatever operating system you are using (recommended system). When done, unmount and try step above again just to be certain.
11. Flash any new ROM of choice (I use SlimSaber by Cyril279), Gapps (I use slim full gapps,) modem for AOSP roms (I used UCMD8, works best for me but may not be the same for your location, please use what works best for you), and any other addon packages.
12. Optional........enable ART runtime in developer options. Reboot, and wait a long time for it to compile apps ahead of time.
13. Just enjoy :good::good:
Another link for my personal files used(same as those here)
CREDIT IN NO PARTICULAR ORDER
Gabes Dad............................... for most of the guide and also making me take the dive.
Cyril279
Chainfire
RockRatt
mtpi
[-Stash-]
alephzain
creepyncrawly
Mobile Odin .pit file
Great guide and idea! Thanks for your work!
I'm having trouble at step #8, Using Mobile Odin to install the modded .pit file.
I can't get Mobile Odin to see the .pit file, either as provided, in the .rar container, or as the bare .pit file.
I saw in the posts on this by [-Stash-], which you reference, that regular Odin was used to install the .pit file.
I've read elsewhere that Mobile Odin can't work with .pit files, but I gather you have found a way.
Your guide worked great up until #8, and also after #8.
I was able to continue on and install a great KitKat rom, TheGeekyNimrod's new Unofficial Carbon Rom and the RB-Shift kernel, just without the new partition sizes.
Thanks again for posting this guide, and doing the work necessary to come up with it. I'm looking forward to this better partition scheme.
I would be grateful for any help you could provide.
DanViolaMan said:
Great guide and idea! Thanks for your work!
I'm having trouble at step #8, Using Mobile Odin to install the modded .pit file.
I can't get Mobile Odin to see the .pit file, either as provided, in the .rar container, or as the bare .pit file.
I saw in the posts on this by [-Stash-], which you reference, that regular Odin was used to install the .pit file.
I've read elsewhere that Mobile Odin can't work with .pit files, but I gather you have found a way.
Your guide worked great up until #8, and also after #8.
I was able to continue on and install a great KitKat rom, TheGeekyNimrod's new Unofficial Carbon Rom and the RB-Shift kernel, just without the new partition sizes.
Thanks again for posting this guide, and doing the work necessary to come up with it. I'm looking forward to this better partition scheme.
I would be grateful for any help you could provide.
Click to expand...
Click to collapse
I would imagine you could still use regular ODIN for step 8, just put the phone back into download mode. Take this with a grain of salt as this is just a guess.
DanViolaMan said:
Great guide and idea! Thanks for your work!
I'm having trouble at step #8, Using Mobile Odin to install the modded .pit file.
I can't get Mobile Odin to see the .pit file, either as provided, in the .rar container, or as the bare .pit file.
I saw in the posts on this by [-Stash-], which you reference, that regular Odin was used to install the .pit file.
I've read elsewhere that Mobile Odin can't work with .pit files, but I gather you have found a way.
Your guide worked great up until #8, and also after #8.
I was able to continue on and install a great KitKat rom, TheGeekyNimrod's new Unofficial Carbon Rom and the RB-Shift kernel, just without the new partition sizes.
Thanks again for posting this guide, and doing the work necessary to come up with it. I'm looking forward to this better partition scheme.
I would be grateful for any help you could provide.
Click to expand...
Click to collapse
Sorry for the late reply............using odin to flash in download mode also works perfectly. the pit does not harm in anyway (at least for me so far).
When done with pit flash in download mode,.............wait for for a minute or two.
Boot to recovery and format all partitions including internal. Had to mount internal partition and format with pc.
Hope this helps
worked
Thanks. I did this. Although, when the phone boots the initial 'Samsung galaxy sii' splash is now changed to 'SAMSUNG' with the flash of the stock JB, i think. (actually, i dont remember if it was that, or if it was the ICS Semi_v18 ROM I flashed earlier for a different purpose). That splash screen seems to stay longer than before. Anyways, I used mobile odin (need the i777 flash kernel) to flash shift-v4.8 kernel, and then odin to flash the pit file from my computer. I did not have to format with the computer as the recovery seemed to do it fine.
anyone tried this on the SGH-S959G I curently run @cyril279 slimsaber and want to be able to install the full slim gaaps instead of the mini gapps. Plus I feel eventually we will all need bigger system partition if we keep these phones. Or do I need a different pit file?
Figured it out. Modified original pit.
Thanks a lot for the guide.
This worked fine for me. Initially, I didn't get a cellular signal but then I realized that I missed that instruction embedded in step #11. I'm currently using CM11 M10 build with it.
I assume this will work with any custom ROM, but would it work with stock ROMs that are flashed via Oden, or would this kind of flash put the old partition table back?
Hey, could reupload the .pit file? It's 404'd.
leeroyjenkins11 said:
Hey, could reupload the .pit file? It's 404'd.
Click to expand...
Click to collapse
Sure. Where I hosted the files has been down for weeks now. Thanks for alerting me.
hey i want to just use the stock rom with stock kernel. So could i just stop at which step. Please help me
virajjjj said:
hey i want to just use the stock rom with stock kernel. So could i just stop at which step. Please help me
Click to expand...
Click to collapse
I think the safest way would be to follow his steps all the way through step 10, then in step 11 re-install the UCMD8 stock firmware using desktop Odin.
Just wanted to say thanks for the writeup! I was frustrated with having to install PA Nano Gapps, so this guide and your modded .pit file were perfect. Just finished installing LS 3.2 Milestone with PA Stock Gapps! :highfive:
Confused & stuck at step 7
Updated: I finally succeed to re-partition; however, I could not go back to SHOstock3 v4 (4.1.2)
If my phone already has a recovery installed and is rooted, can I go ahead and install the modified pit file with mobile odin and proceed from there? why exactly would I need to flash ucmb8 through odin?
bleggy said:
If my phone already has a recovery installed and is rooted, can I go ahead and install the modified pit file with mobile odin and proceed from there? why exactly would I need to flash ucmb8 through odin?
Click to expand...
Click to collapse
Same question.
Sent from my SGH-I777 using XDA Free mobile app
When you flash a new pit through odin everything gets erased except external sd card so use a computer and follow the instructions.
Thanks. I'm attempting to follow the instructions, but I need to use Heimdall instead of Odin. If anyone is familiar with Heimdall, I'd greatly appreciate your help.
I downloaded I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5.7z file and extracted the contents to a folder.
[email protected]:~/heimdall$ ls
boot.bin I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5 Sbl.bin
cache.img I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5.7z zImage
factoryfs.img modem.bin
hidden.img param.lfs
and then boot into download mode and ran: sudo heimdall flash --kernel zImage --factoryfs factoryfs.img --cache cache.img --hidden hidden.img --param param.lfs --modem modem.bin
I receive the following:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
ERROR: Partition "kernel" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
What should I be doing differently?
EDIT: looks like partition names are capitalized! , so it should be sudo heimdall flash --KERNEL zImage --FACTORYFS factoryfs.img --CACHE cache.img --HIDDEN hidden.img --MODEM modem.bin
To be safe, I shouldnt mess with boot.bin, param.lfs, Sbl.bin, right? or is this necessary here?
Looking forward, does anyone know the exact command to flash the modified .pit file? Would it be:
sudo heimdall flash --repartition --pit .pit ?
Problem
Okay i did something wrong and just i had softbricked my phone and i can just enter into download mode but it fails and gives me write failed error. What can i do now. Help needed please
alright. this got me where I wanted to be:
sudo heimdall flash --KERNEL zImage --FACTORYFS factoryfs.img --CACHE cache.img --HIDDEN hidden.img --MODEM modem.bin
I still cant figure out how to flash the .pit in heimdall.
I receive this:
[email protected]:~/Downloads/heimdall$ sudo heimdall flash --repartition --pit i777_4GB\ data\ -\ 45mb\ preload\ -\ 1GB\ system.pit
[sudo] password for bleggy:
Action: flash
Arguments:
--repartition --pit <filename>
--<partition name>|--<partition identifier> <filename> [...]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
or:
--<partition name>|--<partition identifier> <filename> [...]
[--pit <filename>]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
Description: Flashes one or more firmware files to your phone. Partition names
(or identifiers) can be obtained by executing the print-pit action.
WARNING: If you're repartitioning it's strongly recommended you specify
all files at your disposal.
any ideas?
Edit: Just read it in i9100 thread that this method should not be used if you want to run stock rom. So flashed backed original pit file from i9100 thread and now the phone is running like as it should be running.