Related
Since we have rooted it now SPL seems to be useless.
----
Well, this is the original SPL image on Tattoo, nothing related to update.zip.
----
I was trying to reverse it, and just found why it refuses to erase, but I could not find why it refuses to download data from the host.
----
By now, to flash SPL or the first splash, you need a custom kernel with additional partition information and then use flash_image is OK.
tewilove said:
Since we have rooted it now SPL seems to be useless.
Click to expand...
Click to collapse
useless !! nope defo not, thanks for the input..
are you new here or regular user with new I.D. ??
..
definitely tewilove ; i loved this since long time.... is it correct that i rename it as update.zip & boot into recovery, then apply update.zip ???
one more question : will it change my baseband version from G to H ?, which is non 3G to 3G firmware...
i am dying here someone would come up with this innovative upload. thanks tewilove for this wonderful upload....
@tewilove, ur zip file is not signed.... when i tried updating it in recovery mode, it says verification failed, no signature....
what to do buddy ?
manuvaidya said:
@tewilove, ur zip file is not signed.... when i tried updating it in recovery mode, it says verification failed, no signature....
what to do buddy ?
Click to expand...
Click to collapse
sign it urself using testsign.jar
svprm said:
sign it urself using testsign.jar
Click to expand...
Click to collapse
how do i do it ??? little brief explanation would have been much better rather than telling me do it myself right ???
I have a dead Tattoo.. stucked in tattoo logo at the boot... it's possible to use this spl for heal?
Lox_Dev said:
Original post:
Now you are going to sign the zip file. Download attached testsign.zip and copy it in your <SDK>/tools folder. Extract it here. It should create a sign subfolder with a testsign.jar file in it.
Then, from <workdir> folder, do:
java -classpath <SDK>/tools/sign/testsign.jar" testsign file.zip file-signed.zip
Ok, now your zip file is ready to be deployed using cyanogen recovery image.
Click to expand...
Click to collapse
Test Jar:http://forum.xda-developers.com/attachment.php?attachmentid=220533&d=1251207154
after i signed the file and try to flash i get the following message:
E:Can't find update script
Any ideas?
svprm said:
Test Jar:http://forum.xda-developers.com/attachment.php?attachmentid=220533&d=1251207154
Click to expand...
Click to collapse
i am sorry. i couldnt succeed in signing it with testsign.jar file u uploaded....
could u please do it for me... just a favour. i think i am missing out some important step whicch i couldnt figure it out.... please test sign it & upload it here.....
moved to here
TeamWIN has now made their Kernel Manager app work with the XOOM. What it allows you to do, is flash kernels inside android. No more booting into fastboot, or even running update.zips.
https://market.android.com/developer?pub=Team+Win
Just downloaded and just what we need, it is awesome, will get the paid version as promised in the irc LOL
bwcorvus said:
TeamWIN has now made their Kernel Manager app work with the XOOM. What it allows you to do, is flash kernels inside android. No more booting into fastboot, or even running update.zips.
https://market.android.com/developer?pub=Team+Win
Click to expand...
Click to collapse
It corrupted my kernel just fyi to the devs
sfld said:
It corrupted my kernel just fyi to the devs
Click to expand...
Click to collapse
it didn't corrupt your kernel. Just manually push the BCM4329.ko file through adb.
or just to be safe just push everything again manually. That way you know everything was done right.
sfld said:
It corrupted my kernel just fyi to the devs
Click to expand...
Click to collapse
if there are issues, please join us in #kernel-manager on irc.freenode.net. we encourage all devs to participate in troubleshooting any outstanding issues on all devices.
this broke my wifi. what do i do? i have no idea how to do the steps above with adb
grasshoxda said:
this broke my wifi. what do i do? i have no idea how to do the steps above with adb
Click to expand...
Click to collapse
Download and run the one click root file, it will repatch with the kernel that comes in it or you can place the files from the latest kernel release into it. I think thats the best option for you if you are not comfortable using adb.
Get the one click root here.
http://forum.xda-developers.com/showthread.php?t=1011196
i reran rootmyxoom and have wifi back. how to i use this then without losing wifi?
slatejones said:
Download and run the one click root file, it will repatch with the kernel that comes in it or you can place the files from the latest kernel release into it. I think thats the best option for you if you are not comfortable using adb.
Get the one click root here.
http://forum.xda-developers.com/showthread.php?t=1011196
Click to expand...
Click to collapse
lol just finished doing exactly that thanks tho
how do i go about placing the new files into it?
grasshoxda said:
lol just finished doing exactly that thanks tho
Click to expand...
Click to collapse
It could be an issue with the download. Find the file with astro or root explorer and delete it then redownload, or download to your computer and place it on the xoom and have the app install from the sd card instead of downloading it.
If it still doesnt work for you, just reflash the one click root and give it a day or two for the devs to update the app or something.
Hope everything works out for you
grasshoxda said:
how do i go about placing the new files into it?
Click to expand...
Click to collapse
Well.... Uhhh.... Thats not something I tried myself. But I think it would be pretty easy... When you extract the root my xoom folder to your computer, open it up and find the kernel files... then replace them with the updated files from the 1.3.2 zip file. Just unzip the 1.3.2 folder and copy and paste.
Hope this helps
ive opend the rootmyxoom folder and i dont know where to put the contents from the zip
grasshoxda said:
ive opend the rootmyxoom folder and i dont know where to put the contents from the zip
Click to expand...
Click to collapse
I dont have a current version of the one click root, but I would think to look inside either the wifi root folder or the tiamat folder (inside the rootmyxoom folder). Whichever one has the same files from the 1.3.2 folder, copy and paste them over to that folder inside the rootmyxoom folder and you should be golden.
ive looked thru them all , i dont see any files in any of those folders that look like the ones that come in the zip
open up the tiamit files in the root my xoom folder and replace with whatever kernel you want to use. I did this three times with tiamit 1.3.0, and .1 and .2. You can try to just replace the entire file or go in and replace the indiviual files from within the tiamit kernel folder. Be careful though if you replace the wrong files or mix them up could be bad results, usually just no wifi or bootloops.
Oh by the way i always did all this on a windows based computer that way the files look the same or similar
grasshoxda said:
ive looked thru them all , i dont see any files in any of those folders that look like the ones that come in the zip
Click to expand...
Click to collapse
This works great, now if only there can be a similar app that installs themes
Wow, Kernel manager just solved my problem of flashing the new tiamat 1.4.0 kernel.
Was having issues in CWM, instead of pulling my hair out in testing it out via trial by error. Had a (status 0) error while flashing kernel in CWM.
It was resolved by using Kernel Manager!!!
Can't access link to download apk? Anyone have this problem?
Edit: got it downloaded
Sent from my Xoom using Tapatalk
worked great with 1.3 but as soon as i tried 1.4 it broke my wifi, gonna wait till next update and try again, dont like the 1click root method
Hello everyone,
Can someone please inform and post a thread link of a battery mod that works on the i9001? By battery mod I mean small zip file that is installed from recovery and changes the stock battery meter
You can make it yourselt.
1. Use Root Explorer to get your framework-res.apk file
2. Go to http://uot.dakra.lt/ to customize it yourselt.
3. Go to http://forum.xda-developers.com/showthread.php?t=1253707 to download the Root-i9001-Signed.zip
4. Put the modified framework-res.apk in the above zip file and delete the unneeded files.
5. Update the updater-script file, resign the zip file.
6. Flash the zip file in recovery.
Do you like this one?
quest221 said:
You can make it yourselt.
1. Use Root Explorer to get your framework-res.apk file
2. Go to http://uot.dakra.lt/ to customize it yourselt.
3. Go to http://forum.xda-developers.com/showthread.php?t=1253707 to download the Root-i9001-Signed.zip
4. Put the modified framework-res.apk in the above zip file and delete the unneeded files.
5. Update the updater-script file, resign the zip file.
6. Flash the zip file in recovery.
Do you like this one?
Click to expand...
Click to collapse
If you use manveru0's kernal and recovery you can now flash the update files as they come from the kitchen
quest221 said:
You can make it yourselt.
1. Use Root Explorer to get your framework-res.apk file
2. Go to http://uot.dakra.lt/ to customize it yourselt.
3. Go to http://forum.xda-developers.com/showthread.php?t=1253707 to download the Root-i9001-Signed.zip
4. Put the modified framework-res.apk in the above zip file and delete the unneeded files.
5. Update the updater-script file, resign the zip file.
6. Flash the zip file in recovery.
Do you like this one?
Click to expand...
Click to collapse
Hmm... yes, nice, but I'm not in to designing things. I was looking for something that has been already created
what's the version of your Rom?
quest221 said:
what's the version of your Rom?
Click to expand...
Click to collapse
Firmware version : 2.3.4
baseband version I9001XXKP4
Kernel Version : [email protected] #7
Build Number : GINGERBREAD.XXKP4
I use Go launcher (from my opinion it's the best), if you think otherwise please post the better launcher, I am opened to experiment others.
Many thanks,
Ciprian
I don't have a I9001XXKP4 Rom in my hard drive. If you can send your your framework-res.apk, I can make one for you.
quest221 said:
I don't have a I9001XXKP4 Rom in my hard drive. If you can send your your framework-res.apk, I can make one for you.
Click to expand...
Click to collapse
I would like something like http://img225.imageshack.us/img225/9943/smoothbatt.png if it is possible.
I have attached framework-res.apk
opps a
hey guys!
just used this. twice great kitchen, really revamped some of the more boring icons on stock roms. thanks for the tip!!
1framework-res_I9001XXKP4_signed.zip is the file that I updated the updater-script so you can flash it in the in-build recovery.
1framework-res_I9001XXKP4_original_signed.zip is your original file. If there are any issues, you can flash it back in the in-build recovery.
How to:
Copy the zip file to the internal SD card, not the external one, go to recovery, flash it.
quest221 said:
1framework-res_I9001XXKP4_signed.zip is the file that I updated the updater-script so you can flash it in the in-build recovery.
1framework-res_I9001XXKP4_original_signed.zip is your original file. If there are any issues, you can flash it back in the in-build recovery.
How to:
Copy the zip file to the internal SD card, not the external one, go to recovery, flash it.
Click to expand...
Click to collapse
Thanks, exactly what I needed. I flashed it and all is ok
quest221 said:
1framework-res_I9001XXKP4_signed.zip is the file that I updated the updater-script so you can flash it in the in-build recovery.
1framework-res_I9001XXKP4_original_signed.zip is your original file. If there are any issues, you can flash it back in the in-build recovery.
How to:
Copy the zip file to the internal SD card, not the external one, go to recovery, flash it.
Click to expand...
Click to collapse
can i use it on 2.3.6 rom?
nope because you will end up in a bootloop by flashing this
its only for XXKP4
urm, Ive tried to do as you told in post number 2(by cooking it according to my own preference)
but my problem starts from step number 5
5. Update the updater-script file, resign the zip file.
Click to expand...
Click to collapse
I already received the cooked file
but I dont know how to change the update script and end up failing to update using the zip file.
can you please help me?
or link me to a place that really can help me to learn better on changing the update script.
try this one, I updated the updater-script, you can compare it with the one from kitchen.
PS: Forgot to update the update-binary file, now try the new one. It should work.
Thanks!!!! But I got an error that states
E:error in /tmp/sideload/package.zip
(status 2)
I wonder whats wrong.
looked in a thread
http://forum.xda-developers.com/showthread.php?t=1194245&page=3
and from what I understand it seems to be a problem with the update binary. But Im just an end user and this is too much for me.
anyway maybe Ill try to flash the cranium ROM and try to cook again a new one and use your update script.
cheers!!
Hi,
Is there any posibility to change framework-res.apk file without CWM? I don't want to instal CWM becouse of it has a problem with front side cam and I need this cam. It's can't be overwritten when the phone works. Maybe some adb and push command is possible.
Could you help me by describing the whole procedure? Sorry for my English.
@quest221
Can you maybe make one for Android 2.3.5 like the screenshot @ page 1?
I have baseband I9001XXKPF, Build XXKPG
I update the zip file with the new update-binary file.
Is there any posibility to change framework-res.apk file without CWM?
Click to expand...
Click to collapse
Yes, I just use the recovery from Samsung, not the third-party.
Check the post #2, that's the steps. Also replace the update-binary file with the one in my zip file.
Can you maybe make one for Android 2.3.5 like the screenshot @ page 1?
Click to expand...
Click to collapse
Upload your framework-res.apk file.
V20B (CIS)
V20O (DEU)
Root on V20B
information deleted
I used google translator and that's the result of the post above:
All items are strictly in the order do not jump over them and keep the sequence!
Spoiler (+ / -) (I advise you to read before flashing)
to the root of drive C:
Two. Download Attachment SmartFlashTool_External.rar (1.18 MB) Number of downloads: 37
and extract the root of drive C:
3. Download Attachment Superuser.zip (611.2 KB) Number of downloads: 51
and put ( no need to unpack ) File on the SD-card phone
4. Turn off the phone.
Five. We hold the Volume Up (+) and insert the USB cable one end into the computer, the other into the phone
6. We will have the text of S / W Upgrade Please wait while upgrading ...
Spoiler (+ / -)
7. Run the file B_SmartFlashTool_Extern.exe
Eight. Go to the tab ROM copy D / L
9. Select the two files that you extracted from the archive [PATCHED] BIN_LGP970AT-00-V20a-CIS-XXX-JAN-06-2012 +0.7 z
10. Check:
Spoiler (+ / -)
11. Click the Start button
12. Go to the process of the firmware, go to drink coffee \ tea shorter depart away from your computer to your phone
13. When you sign Download Comlete! Go to the phone
Spoiler (+ / -)
14. On the phone, we see the regime Recovery (touch it, the management of a finger)
15. Select install zip from sdcard
16. Then choose zip from sdcard
17. Prolistyvayem and choose Superuser.zip
18. Prolistyvayem and select Yes - Install SuperUser.zip
19. Select + + + + Go back + + + +
20. Choose wipe data / factory reset
21. Prolistyvayem and select Yes - delete all user data
22. Then reboot system now
That's it! Phone is loaded, if you do it right!
As a result, we have a firmware with the Root-V20A human touch and Recovery! Thank you all and good luck to you in the firmware!
Click to expand...
Click to collapse
Dont exactly know, what it does, but as far as I get it, it roots the device and installs CWM touch.
Credits go to poster, if it is successful.
Hey, thanks for posting here. Here is v20b : http://www.lgmobiles.com/gsm/download/P970 V20B(Gingerbread Version).rar
We don't have it for N version. I saw the russian forum and wanted to ask you about howvyou managed to root v20a before this method.
Sent from my LG-P970 using XDA App
this method is working just v20a(attachment patched bin file) right?
Where how I convert .kdz to .bin file?
I know russian very well.So i shortly translate all procedure done here.
They patched original 20A bin file , changing system recovery.img with clocworkmod recovery.img touch version.
Download 20A.bin extract it,and put somewhere in your computer.
and below there is a CWM flashable superuser.zip.
Download it and put to your Sd kart.Do not extract.
Then simply flash that patched 20A bin file with smart flash procedure posted here from radkor
http://forum.xda-developers.com/showthread.php?t=1448803
After finished flashing with smartflash tool go to cwm recovery and install superuser.zip
and you get rooted original 20A ginger.
Nice option for flashing and rooting
but we do not have 20N bin file yet.
we have only indian version 20B bin file, redpik posted it above
Thread moved
Unless it's a ROM or kernel you've created yourself, this doesn't belong in Development.
Doesn't SmartFlash auto erases all user data (factory reset at first boot)?
Okey... Maybe, tomorrow I will be a version (.bin) V20N
Sorry for my English
Kraaz said:
I know russian very well.So i shortly translate all procedure done here.
They patched original 20A bin file , changing system recovery.img with clocworkmod recovery.img touch version.
Download 20A.bin extract it,and put somewhere in your computer.
and below there is a CWM flashable superuser.zip.
Download it and put to your Sd kart.Do not extract.
Then simply flash that patched 20A bin file with smart flash procedure posted here from radkor
http://forum.xda-developers.com/showthread.php?t=1448803
After finished flashing with smartflash tool go to cwm recovery and install superuser.zip
and you get rooted original 20A ginger.
Nice option for flashing and rooting
but we do not have 20N bin file yet.
we have only indian version 20B bin file, redpik posted it above
Click to expand...
Click to collapse
Ok. Let me try to understand this. They replace "system recovery.img" which is reside in the original rom bin file with "cwm recovery.img" (where to get this file?) and then flash it using smartflash tool. So after reset by smartflah, cwm is already in the phone installed. Then all is easy, proceed to install superuser.zip, etc..etc.zip.
How is it possible to obtain root by inserting cwm in the rom while cwm itself require root to run? Also, what's the "system recovery.img" that got replaced. Is it important?
Please investigate more. Need more info on how "patching" is done too. I don't understand russian.
Sent from my LG-P970 using XDA App
SnegovikRZN said:
Okey... Maybe, tomorrow I will be a version (.bin) V20N
Sorry for my English
Click to expand...
Click to collapse
Can you help to make one for v20b? The link post above by redpik contain bin file for v20b. If succeed, we're going to have the 1st v20b rooted. Hell yeah!
Sent from my LG-P970 using XDA App
adxgrave said:
Ok. Let me try to understand this. They replace "system recovery.img" which is reside in the original rom bin file with "cwm recovery.img" (where to get this file?) and then flash it using smartflash tool. So after reset by smartflah, cwm is already in the phone installed. Then all is easy, proceed to install superuser.zip, etc..etc.zip.
How is it possible to obtain root by inserting cwm in the rom while cwm itself require root to run? Also, what's the "system recovery.img" that got replaced. Is it important?
Please investigate more. Need more info on how "patching" is done too. I don't understand russian.
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
I guess you need to investigate more how android works. Flashing recovery image with the whole system in a bin file makes cmw part of the "original" firmware so,like recovery that only can erase all this one can read/write in the system files. Sounds normal. I read on Samsung forums that they get root for latest versions by flashing a patched odin file and then a su zip. I will try it
Sent from my LG-P970 using XDA App
adxgrave said:
Can you help to make one for v20b? The link post above by redpik contain bin file for v20b. If succeed, we're going to have the 1st v20b rooted. Hell yeah!
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Since Telcel's v20a is is just out, its going to be pretty good news if it works.
mihaiolimpiu said:
Doesn't SmartFlash auto erases all user data (factory reset at first boot)?
Click to expand...
Click to collapse
Yes it does.
Redpik said:
I guess you need to investigate more how android works. Flashing recovery image with the whole system in a bin file makes cmw part of the "original" firmware so,like recovery that only can erase all this one can read/write in the system files. Sounds normal. I read on Samsung forums that they get root for latest versions by flashing a patched odin file and then a su zip. I will try it
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Then we can say that this is universal method as long as cwm can be patch into the rom. Finding exploit is not necessary anymore. So, what's the function of the file replaced in the rom. Is it the original lg recovery method which is not available anymore if this we use this method?
Thanks for the explanation, I wonder why it hasn't be use before, maybe because lack of rom file in bin format?
Edit: downloading rom in your link, pls post how to proceed if you get hold of it.
Sent from my LG-P970 using XDA App
adxgrave said:
Then we can say that this is universal method as long as cwm can be patch into the rom. Finding exploit is not necessary anymore. So, what's the function of the file replaced in the rom. Is it the original lg recovery method which is not available anymore if this we use this method?
Thanks for the explanation, I wonder why it hasn't be use before, maybe because lack of rom file in bin format?
Edit: downloading rom in your link, pls post how to proceed if you get hold of it.
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
The problem is that we don;t know how to extract .bin files and modify the content. Just the first post has the good link I posted the stock v20B so he would patch it
Redpik said:
The problem is that we don;t know how to extract .bin files and modify the content. Just the first post has the good link I posted the stock v20B so he would patch it
Click to expand...
Click to collapse
to get the files out of a kdz: grab them while someone is using the KDZ program to update their phone. The files are extracted and put into "C:\ProgramData\LGMOBILEAX\Phone" but as soon as the program detects no phone the entire directory is blown away. Too fast to grab the files. So either you update for real (in which case you have the time to grab the files) or you create a symbolic link between the C:\ProgramData\LGMOBILEAX\Phone folder and another folder you create say name it C:\test. What happens is that files get extracted and then \phone folder deleted when no phone is detected but the files remain on the \test folder. So you get your files which are a "model.dll" file (in p970 case i guess something like lgp970.dll) and a .wdb file which is the firmware. How to proceed though to tinker further with the .wdb file so as to get bin file and baseband still elludes me
I bet our rom cooker knew how to unpack and repack. So, anyone?
Sent from my LG-P970 using XDA App
jimakos29 said:
to get the files out of a kdz: grab them while someone is using the KDZ program to update their phone. The files are extracted and put into "C:\ProgramData\LGMOBILEAX\Phone" but as soon as the program detects no phone the entire directory is blown away. Too fast to grab the files. So either you update for real (in which case you have the time to grab the files) or you create a symbolic link between the C:\ProgramData\LGMOBILEAX\Phone folder and another folder you create say name it C:\test. What happens is that files get extracted and then \phone folder deleted when no phone is detected but the files remain on the \test folder. So you get your files which are a "model.dll" file (in p970 case i guess something like lgp970.dll) and a .wdb file which is the firmware. How to proceed though to tinker further with the .wdb file so as to get bin file and baseband still elludes me
Click to expand...
Click to collapse
update: doing some research and it seems to extract the bin files you need lgutils and the .dll file you get from the kdz extraction but I am not at home to look into it any further.
Stable ROOT METHOD found!
You don't need this, disabling LG MODEM DEVICE under modems makes UNLOCKROOT work on every firmware! TESTED on 20N german version!
Disabling LG MODEM DEVICE under modems makes UNLOCKROOT work on every firmware! TESTED on 20N german version!
Here is the proof
http://forum.xda-developers.com/showpost.php?p=22195743&postcount=417
Here are the drivers I used:
http://forum.xda-developers.com/showpost.php?p=22196019&postcount=21
I used Windows 7 32 bit, the original poster used Win7 64 bit...
not available
Make sure you use Notepad++ to edit the updaterscript. If you have problems. Take an updater-script from a working rom and see if it flashes successfully.
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
Copy the entire META-INF folder from any rom and paste it in your rom's zip.
EG- If your rom is based on cm7, copy cm7's meta-inf
I copied META-INF from Adrenaline ROM
And it didn't work
assert failed:raw_boot_img
Could it be a kernel problem (boot.img)
Sent from my GT-S5830 using xda premium
Which boot.img are you using?
You need to use a boot.img from a custom kernel, stock boot.img wont work.
Mate Upload Your Rom and PM it to me and i'll look at what is wrong if u like.
Are you sure you never used any of the Dsixda kitchen tools?
Because they are not compatible with the Ace.
Plus, I hope you never converted it into update-script.
Is your rom CM7 based, or stock based?
Im using stock boot.img
I thought it would work... I don't like custom kernels like nims or CF-Root.
As soon as I get home I'll send you ROM.
It was originally update-script and changed with dsixda kitchen to updater-script.
Stock based
Sent from my GT-S5830L using xda premium
Tovagulet said:
Im using stock boot.img
I thought it would work... I don't like custom kernels like nims or CF-Root.
As soon as I get home I'll send you ROM.
It was originally update-script and changed with dsixda kitchen to updater-script.
Stock based
Sent from my GT-S5830L using xda premium
Click to expand...
Click to collapse
So that's the problem.
Dsixda scripts are not compatible with the Ace.
did the stock rom u are basing this rom on have a Meta-Inf. or was it from a system.img
Tovagulet said:
Im using stock boot.img
I thought it would work... I don't like custom kernels like nims or CF-Root.
As soon as I get home I'll send you ROM.
It was originally update-script and changed with dsixda kitchen to updater-script.
Stock based
Sent from my GT-S5830L using xda premium
Click to expand...
Click to collapse
After creating zip usi.g dsixda kitchen. Extract zip and copy meta-inf folder from.other rom and replace. Stock kernel wont work. Extract the zip of any custom kernel, copy system folder and boot.img and paste in the root directory of extracted files of rom. Zip back everything. It will work.
tj_droid said:
After creating zip usi.g dsixda kitchen. Extract zip and copy meta-inf folder from.other rom and replace. Stock kernel wont work. Extract the zip of any custom kernel, copy system folder and boot.img and paste in the root directory of extracted files of rom. Zip back everything. It will work.
Click to expand...
Click to collapse
Yes exactly.
Do right as he said and your rom will boot.
Cheers.
tj_droid said:
After creating zip usi.g dsixda kitchen. Extract zip and copy meta-inf folder from.other rom and replace. Stock kernel wont work. Extract the zip of any custom kernel, copy system folder and boot.img and paste in the root directory of extracted files of rom. Zip back everything. It will work.
Click to expand...
Click to collapse
So I just replace boot.img with a custom kernel and start building from that?
or after creating the .zip I also have to copy the META-INF from another ROM?
Tovagulet said:
So I just replace boot.img with a custom kernel and start building from that?
or after creating the .zip I also have to copy the META-INF from another ROM?
Click to expand...
Click to collapse
Just replace META-INF in your rom with META-INF from Blackhawk(if stock rom) and make necessary edits.Your rom will work perfectly.I personally haven't had any problem by using stock kernel.
POTATO!!!!
Tovagulet said:
So I just replace boot.img with a custom kernel and start building from that?
or after creating the .zip I also have to copy the META-INF from another ROM?
Click to expand...
Click to collapse
Ok. Read carefully.
After creating the zip via dsixda kitchen. Close it and dont touch it at all. The follow the steps from my last comment.
Buddy.
Just upload your meta-inf..
and i'll look into it.
Got this problem before , it's because the assert command in updater-scripts do not support boot.imgs larger than 4MB .
Just remove the assert() and replace the commands in the proper format (replace commas at the end of command with semi-colons) as well as grab a proper update-binary , your boot.img should work .
Sent from Ursa's claws.
CallMeVentus said:
Got this problem before , it's because the assert command in updater-scripts do not support boot.imgs larger than 4MB .
Just remove the assert() and replace the commands in the proper format (replace commas at the end of command with semi-colons) as well as grab a proper update-binary , your boot.img should work .
Sent from Ursa's claws.
Click to expand...
Click to collapse
I'm working on a Samsung Galaxy GT-B5510, having the same problem trying to install custom ROMs and kernels. All failing with the same error you describe here. However, when I edit the script and rerun it, it does not throw an error but it looks like the kernel is not replaced. The only thing I didn't do was change the update-binary. What do you mean by a "proper" one?
Thanks.
MrRimmer said:
I'm working on a Samsung Galaxy GT-B5510, having the same problem trying to install custom ROMs and kernels. All failing with the same error you describe here. However, when I edit the script and rerun it, it does not throw an error but it looks like the kernel is not replaced. The only thing I didn't do was change the update-binary. What do you mean by a "proper" one?
Thanks.
Click to expand...
Click to collapse
The ones inside the custom ROMs where flashing a custom kernel has been a success in
I give up writing anymore signatures.