Database Develop

[Q] How make file .kdz or CP AP for CWM

I flash my OB with v20o (smartflash - root), its ok, root,
Now i can flash with v20C.kdz , original p970H.
I used tool to extrat files ap and cp.
Root is a big problem.
Flash smartflash or kdz, bam my root bye.
How i can make file .zip to flash for CWM.

FLash it with R&D testtool + workaround, use cwm injection method (search for it).
Thats how you ll get your phone with the correct software + root

I found use cwm injection method, but is not clear to me.
When i flash with V20o - rooted, i used smartflash, after process reboot in cwm and install from zip superuser. Thats it i do.
After flash using smartflash phone reboot in cwm, send superuser and ok.
the question is how inject cwm. I read topic about this but is not clear for me.
Can you help me?

I can only guide you here again: http://forum.xda-developers.com/showthread.php?t=1512203
I think it doesnt work with smartflash. But if you use an already rooted version, there also is no need to inject
If you are in CWM, simply make a full wipe and you can install any custom ROM you want already.
Then there is no need to really root and boot it

in this topic
http://forum.xda-developers.com/showpost.php?p=23788913&postcount=170
File cp ap, flash smartflash, auto reboot in cwm mode, install SU.
how make cwm inject in file to flash? is the question.
Phone simple reboot in cwm after flash witch SF.
And don't send SU to phone in first boot, bye bye root, need flash again and send zip SU.
I want make this in other V20XX, its cool.

When you are in CWM, you need to flash superuser.zip, then you can restart.
And dont forget to wipe

How inject cwm in my files, i have files and i need how inject cwm. that it

N00BY0815 said:
When you are in CWM, you need to flash superuser.zip, then you can restart.
And dont forget to wipe
Click to expand...
Click to collapse
All this ok for me.
Simple i do, in my files, i want inject cwm. Only this so

I think is that
Op afraid that lg might know this and patch it. I call that's a bull. I don't think lg engineer didn't know how to use dd. As long as we have unecrypted bin file we can patch it. Btw, how can one conceal a patching method using simple dd when you have unpatch file and patched file to compare? Even I managed to figure it out. Op true intention known only to himself.
So, to patch your bin file: (this is done on ubuntu, i don't know if windows got dd)
1. Download cwm at http://download.clockworkmod.com/rec...8.1.3-p970.img to the folder where you keep your bin file.
2. Open terminal and cd to the same folder as above
3. What we need to find is the location where we're suppose to copy cwm into the bin file. dd is bit-stream reader and it will show us the location in term of bytes. We need to search for ANDROID! string. So type:
dd if=LGP970AT-00-V20b-SEA-XXX-JAN-02-2012+0_AP.bin| strings -n 8 -t d| grep ANDROID!
result:
1436661 ANDROID!
1703936 ANDROID!
6422528 ANDROID!
bla..bla..bla...
4. Look of the last entry which contain the ANDROID! string and take note of its byte location (6422528 in this case)
5. Now it's time to copy cwm into the bin file. Type:
dd if=<cwm.img> bs=1 seek=<byte location> conv=notrunc of=<rom.bin>
So in this case:
dd if=recovery-clockwork-touch-5.8.1.3-p970.img bs=1 seek=6422528 conv=notrunc of=LGP970AT-00-V20b-SEA-XXX-JAN-02-2012+0_AP.bin
6. That's it. Your rom is ready to be flash using smartflash tool. You can run the same command in step 3 to verify that cwm is succesfully copied into the bin file. If at the same byte location the ANDROID! string change to [email protected] then you're good to go.
Don't waste your bandwidth to download the op's file if you can do this yourself and beside there's nothing to test, not that op modified the rom in any way. You would be better off testing huexxx zues rom imho.
Savvy?
Edit: Forgot to add. Credit goes to people who found this rooting method. I didn't found it only take a look at it.
Sent from my LG-P970 using XDA App

[HOW-TO][TUTORIAL]Building Kernel from source

Hi all,
I am a developer in GT-I9100G sub-section. I made a tutorial over there for I9100G on building a kernel. Since the method is very similar, I thought of posting a tutotial here for N7000 too so that it will help many new and aspiring developers to build their own kernel for GT-N7000.
Okay. Let's learn how to build kernel for Galaxy Note N7000. There are many ways to build. I am just presenting here the way I build and make kernel.
NOTE 1: Follow the instructions exactly.
NOTE 2: Kernel is opensource. If you make any changes to it, you're expected to share your source. (Usually people share it over github )
NOTE 3: FLASHING KERNEL IS RISKY AND DANGEROUS. BE CAREFUL. BUILD AND FLASH ON YOUR OWN RISK.
What you need to have:
Ubuntu 10.04 and above (I use 10.04 )
ARM tool chain (Download HERE. Click on IA32 GNU/Linux TAR under Advanced Packages)
Samsung's opensource kernel for N7000 (Download HERE. Go to Mobile->Mobile Phone-> Select GT-N7000 and download the zip)
Setting up toolchain:
Extract the tar you downloaded(Suggestion: Extract to one folder where you can have everything. In my case /home/superatmos/build_kernel).
After extracting, you'll see a folder named arm-2010q1. Inside there will be many folders (ex. bin, lib and so on.)
Folder structure will be: /home/<your_name>/build_kernel/arm-2010q1
Setting up kernel:
Extract the zip you've downloaded from samsung's opensource.
You'll find two zips.
Extract GT-N7000_Kernel.tar.gz to /home/<your_name>/build_kernel/
Folder structure: /home/<your_name>/build_kernel/GT-N7000_Kernel
Setting up initramfs:
Samsung's zImage is divided into two parts: Opensource kernel (which you downloaded from samsung's website) and initramfs (which is root file system to boot up the device).
Since I don't have the device, I don't have initramfs either. :-( (If some kernel developer for GT-N7000 can provide a sample initramfs for reference, I can attach it here and give credits to him )
The initramfs(let the folder name too be initramfs) folder need to be copied to /home/<your_name>/build_kernel/
Folder structure: /home/<your_name>/build_kernel/initramfs
Now the entire setup is ready. Let's start modifying kernel configuration.
Setting up kernel config:
Go to /home/<your_name>/build_kernel/GT-N7000_Kernel/arch/arm/configs folder.
Copy c1_rev02_q1_defconfig file and paste it in kernel root folder (/home/<your_name>/build_kernel/GT-N7000_Kernel/).
Rename c1_rev02_q1_defconfig to .config in kernel root folder.
Now open Makefile which is in your kernel root folder(/home/<your_name>/build_kernel/GT-N7000_Kernel/).
Modify the below lines (I guess line 195 and 196).
Code:
ARCH ?= arm
CROSS_COMPILE ?= /home/<your_name>/build_kernel/arm-2010q1/bin/arm-none-linux-gnueabi-
Save and close.
Modifying kernel configuration:
Now open .config file(which you renamed). If its not seen, it might be hidden. Go to View->Show hidden files and there you go.
Do the below things:
Adding local version:
Change CONFIG_LOCALVERSION=" " to anything you like. I add this way:
CONFIG_LOCALVERSION="-N7000-superatmos"
Adding initramfs path:
You need to let kernel know the path from which it needs to take initramfs.
Change CONFIG_INITRAMFS_SOURCE=" " to ../initramfs (In this tutorial it's the path. If you had copied anywhere else, give the path properly).
Enough for now. Once you get experience, you can modify many configurations as per your liking and save. This configuration can be changed by GUI too with the command make menuconfig.
The Important part: Building the kernel:
Open terminal.
Go to path /home/<your_name>/build_kernel/GT-N7000_Kernel/
Type make.
THAT'S ALL. YOUR zImage is ready and is available in /home/<your_name>/build_kernel/GT-N7000_Kernel/arch/arm/boot/zImage.
Install the zImage on the device:
Go to the path where zImage is present and type the below line in command line.
Code:
tar cvf N7000_kernel.tar zImage
Flash the tar using odin.
DONE. CONGRATULATIONS. NOW YOU'VE YOUR OWN KERNEL.
Give me your feedback so that I can improve this tutorial and make modifications to the tutorial if necessary. And of course do post here about how your build went. All the best.

Reserved

Reserved

Last one

Superatmos good too see you in N7000 forum.Wil you launch Superatmos Rom for N7000
Sent from my LG-P500 using xda premium

Been using windows all the time. Seems its good time to learn linux and ubuntu

muhamet said:
Superatmos good too see you in N7000 forum.Wil you launch Superatmos Rom for N7000
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Not as of now. I don't have the device. But I have plans to extend this tutorial to deodexing, modifying initramfs, building custom rom and more.

looks interesting.
i just want to make sure.. if for some reason i used odin to flash the tarred zImage and it's a broken zImage. or corrupted file or false configuration that will break the booting process. will i see be able to go to download move or cwm mode ?
what are the risks here besides the regular odin risks ?

ufk said:
i just want to make sure.. if for some reason i used odin to flash the tarred zImage and it's a broken zImage. or corrupted file or false configuration that will break the booting process. will i see be able to go to download move or cwm mode ?
what are the risks here besides the regular odin risks ?
Click to expand...
Click to collapse
The risks are considerable, to say the least. Read what happened with one b0rked kernel here:
http://forum.xda-developers.com/showthread.php?t=1526852
The end result: about 40-50 hard bricked devices.

ufk said:
i just want to make sure.. if for some reason i used odin to flash the tarred zImage and it's a broken zImage. or corrupted file or false configuration that will break the booting process. will i see be able to go to download move or cwm mode ?
what are the risks here besides the regular odin risks ?
Click to expand...
Click to collapse
Yes. Flashing kernels is always risky. But as per my experience, its very hard to brick the device unless you do something unusual.
so it depends on you. BUILD AND FLASH AT YOUR OWN RISK.

thanks and ok for this part ^^
but i have a question....
do you know the way for mod a stock kernel to add root / cwr when source code not avalable??
for exemple the lp6 kernel... do you know a way for extract the zimage for look on it and include root / crw on the Zimage directly...
if you have some idea please help comunauty for found a way for this ^^ (i have send pm to chainfire to take information for this mod but no response..)

ReDroiD™ said:
thanks and ok for this part ^^
but i have a question....
do you know the way for mod a stock kernel to add root / cwr when source code not avalable??
for exemple the lp6 kernel... do you know a way for extract the zimage for look on it and include root / crw on the Zimage directly...
if you have some idea please help comunauty for found a way for this ^^ (i have send pm to chainfire to take information for this mod but no response..)
Click to expand...
Click to collapse
you need to have crosscompiler, kernel repacker, busybox and su
1.Copy the original zImage to de directory where you extracted the kernel repacker
Rename it to zImage.org
create a temp directory in the kernel repacker directory
Open a linux shell and go to kernel repacker directory
./extracter.sh -s zImage.org -d temp (hit enter)
2.Go to the temp directory and edit init.rc with your favourite editor and put this on a new line at the end off the file.
service install_su /sbin/install_su.sh
user root
oneshot
Save the file and exit
3.copy busybox and su to the tmp folder in your extracted kernel folder
make sure they are markt als executable.
4.copy install_su.sh to the sbin folder in your extracted kernel folder
5.Open a linux shell and go to kernel repacker directory
./repacker.sh -s zImage.org -d zImage -r temp -c gzip
congratulations you must cooked your first modified kernel
6.tar the kernel using this command tar -H ustar -c zImage >code.tar
code need to be enterd in initd_support.sh
#!/tmp/busybox sh
if cd /system/etc/init.d >/dev/null 2>&1 ; then
for file in S* ; do
if ! ls "$file" >/dev/null 2>&1 ; then continue ; fi
/system/bin/sh "$file"
done
fi
code need to be enterd in init.rc
service initd_support /sbin/initd_support.sh
user root
oneshot
tools needed for cross compiler and kernel repacker
cross compiler
https://sourcery.mentor.com/public/...eabi/arm-2009q3-67-arm-none-linux-gnueabi.bin
Kernel repacker tool
https://github.com/project-voodoo/kernel_repack_utils
This will add busybox and SU (that means u will get root)...i dont know how to add recovery though...may be somewhere in intrafms we need to install the script...

perfect...i test this

Good!
Inviato dal mio GT-N7000 con Tapatalk 2

Could someone post ZCLP6's zimage i wanted to try in the beginning of the week but i have a very very slow connection, i'm not enough motivated to download the whole zip.
Thanks
One confirmation superatmos : bootloader and kernel are two different things, i mean bootloader is not included in zimage ?

mohamed454 said:
Could someone post ZCLP6's zimage i wanted to try in the beginning of the week but i have a very very slow connection, i'm not enough motivated to download the whole zip.
Thanks
One confirmation superatmos : bootloader and kernel are two different things, i mean bootloader is not included in zimage ?
Click to expand...
Click to collapse
Here you go.

no problem for extract
but when i whant extract old lp5 with recovery or other one i canot extract without error... the rebuild kernel have security form is creator?

ReDroiD™ said:
no problem for extract
but when i whant extract old lp5 with recovery or other one i canot extract without error... the rebuild kernel have security form is creator?
Click to expand...
Click to collapse
Try dsixda kitchen to extract and then follow the other procedures

Thanks for the zimage. It's telling me 2 hours for the cross compiler (i told you very slow connection :-/ )
Where is install_su.sh, i found a similar one for i9000 i think so :
#!/tmp/busybox sh
source='/tmp/su-2.3.6.1-ef'
dest='/system/xbin/su'
if /tmp/busybox [ ! -f /system/xbin/su ];
then
/tmp/busybox mount -o remount,rw /system
/tmp/busybox mkdir -p /system/xbin
/tmp/busybox cp $source $dest
# make sure it's owned by root
/tmp/busybox chown 0.0 $dest
# sets the suid permission
/tmp/busybox chmod 06755 $dest
/tmp/busybox mount -o remount,ro /system
fi;
Click to expand...
Click to collapse
Grgsiocl, what about bootloader ?

mohamed454 said:
Thanks for the zimage. It's telling me 2 hours for the cross compiler (i told you very slow connection :-/ )
Where is install_su.sh, i found a similar one for i9000 i think so :
Grgsiocl, what about bootloader ?
Click to expand...
Click to collapse
That's the superuser script...tomorrow I will update with new procedures and in detail..I think now I know how to add the recovery as well after doing some reverse engineering on cf kernels...will update tomorrow

Get modem.bin from a running Gingerbread [Mini 2 6500L]

Hello there, a friend of mine has a Galaxy Mini 6500L (the "L" stands for "Latin America", I'm from Paraguay btw), so, he wants to install a custom rom but I'm afraid that he lose the modem and **** up the HDSPA, so, is there a way to backup that modem to flash it with odin or install it from recovery?
I can root the phone if necessary ...
Cheers
PS: theres is no Stock ROM in sammobile for the 6500L

firstly this cannot happen but if you want to backup the modem
then you can do so by mounting the radio partition of the mobile (if it is already mounted then that's very good)
to get radio partition type "cat proc/mtd" in the terminal
and yeah you will need root for doing this
but modem for original galaxy mini 2 will also work on l

the problem is that the L version has a modem that works in differents frequencies ... happened with my galaxy ace (s5830L), im gonna root the phone and im gonna look on /dev ...
thanks ...
PS: I get a stock rom of the 6500L, but is one package, is there a way to get just modem.bin?

what it contains

just S6500LWHLI1_S6500LUVOLI1_S6500LWHLI1_HOME.tar.md5 and I can't decompress that file ..
thanks

that is a tar file use winrar

I decompress that and I get
system.img.ext4
boot.img
recovery.img
fat.bin
cache.img.ext4
hidden.img.ext4
thanks

that fat.bin can be modem
or it may be available in the hidden.img.ext (can mount with virtual sheep)

[DEV][Q] How can i make a odin package of a modifidy stock rom?

Hi Guys,
I Have a rooted Galaxy s advanced. I have modified the stock rom (build I9070XXLQE) android 4.1.2. and now i'm trying to make a flashable odin pakage. after exporting the data and system block to a .img file. and putting them in a md5sum file. Odin get stuck on initializing. does someone know how how to make a working odin pakage for the i9070?

And why would you like to do that?
Isn't it easier to rather make a nand backup?
I do not respond to tech support via PM

dikkekip said:
Hi Guys,
I Have a rooted Galaxy s advanced. I have modified the stock rom (build I9070XXLQE) android 4.1.2. and now i'm trying to make a flashable odin pakage. after exporting the data and system block to a .img file. and putting them in a md5sum file. Odin get stuck on initializing. does someone know how how to make a working odin pakage for the i9070?
Click to expand...
Click to collapse
Do this in windows:
tar -H ustar -c nameofthefile.img > nameofthefile.tar
md5sum -t nameofthefile.tar >> nameofthefile.tar
rename nameofthefile.tar nameofthefile.tar.md5
You need in the same folder md5sum.exe and tar.exe
Sent from my GT-I9070

rolling out on 350 devices
Shaaan said:
And why would you like to do that?
Isn't it easier to rather make a nand backup?
I do not respond to tech support via PM
Click to expand...
Click to collapse
Naidroid backup is nice and works great. the problem is I have to roll out the modified rom on 350 i9070 android devices. so a odin package would be nice. Do I have to flash the data package with the odin files to copy everything ?

still no luck, I'm able to make a odin package now. the only problem is the device that I flash. has no system applications, problems like no keyboard and a crashing google services..
plz help ?
I'm using
adb shell
dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/system.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/mnt/extSdCard/userdata.img bs=4096
dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/system.img bs=4096

dikkekip said:
still no luck, I'm able to make a odin package now. the only problem is the device that I flash. has no system applications, problems like no keyboard and a crashing google services..
plz help ?
I'm using
adb shell
dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/system.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/mnt/extSdCard/userdata.img bs=4096
dd if=/dev/block/mmcblk0p3 of=/mnt/extSdCard/system.img bs=4096
Click to expand...
Click to collapse
Are u missing /preload partition?
Sent from my GT-I9070 using xda app-developers app

I've solved the problem,
i have fixed the premission of the systemapps
I think the app does something like chmod 777
anyway after using the premmision fix app.
the new odin package worked good!
tnx for the feedback

Root, Install custom Recovery, ROMs without connecting your Galaxy S3 i9305 to PC!!!

[My i9305 is not connecting with PC, I tried *#7284# (UART & USB > PDA), but it didn't work...
so I have to find the following way to root my device & to install custom ROMs... It worked perfectly...
But I still want to connect my phone to PC through USB, any help will be appreciated. Thanks]
First, download and install 'Framaroot.apk'. It is available at http://forum.xda-developers.com/showthread.php?t=2130276
Now, open the app and tap on 'Aragorn'. And your device is rooted .
It you want to use custom ROMs, you need custom recovery. So,
Install 'Terminal Emulator.apk' form Play Strore.
Download any TWRP/CWM recovery image for i9305 (.img file). [For TWRP images: http://techerrata.com/browse/twrp2/i9305]
Place it on your internal storage (on root directory).
Rename the .img file to 'recovery.img'
Now, open 'Terminal Emulator' and type following commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p9
or, You can use 'Mobile Odin' / 'Recovery Tools - Flasher' [available in Google Play] to flash .tar recoveries.
You are DONE .

I think it is more advisable to flash recovery using an Application rather than the command line, since one digit here and there, you have a bricked phone.
I would suggest use an app like this after rooting the phone

mtatohin said:
[My i9305 is not connecting with PC, I tried *#7284# (UART & USB > PDA), but it didn't work...
so I have to find the following way to root my device & to install custom ROMs... It worked perfectly...
But I still want to connect my phone to PC through USB, any help will be appreciated. Thanks]
First, download and install 'Framaroot.apk'. It is available at http://forum.xda-developers.com/showthread.php?t=2130276
Now, open the app and tap on 'Aragorn'. And your device is rooted .
It you want to use custom ROMs, you need custom recovery. So,
Install 'Terminal Emulator.apk' form Play Strore.
Download any TWRP/CWM recovery image for i9305 (.img file). [For TWRP images: http://techerrata.com/browse/twrp2/i9305]
Place it on your internal storage (on root directory).
Rename the .img file to 'recovery.img'
Now, open 'Terminal Emulator' and type following commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p9
You are DONE .
Click to expand...
Click to collapse
Framaroot did not work for my GT-I9305. It says 'Error #6' . Are they different from each other? Exynos? I am in UK using international edition.

after rooting using framaroot I flashed costum recovery.IMG using mobile Odin. that is safer

@ enarsee: Yeah, you can use 'Mobile Odin' too. Thanks for your suggestion.
@ shayind4: I'm getting the same error on 4.3 ROM! I think you have to try something else. You can try this http://forum.xda-developers.com/showthread.php?t=2352669
@ reymasters: Yes, you can use it. Its safe and easy. I will edit my post.

98926828
This method doesn't work with my GT-I9305 also. I'm so sorry I flashed 4.3 with odin...

elektronchika said:
This method doesn't work with my GT-I9305 also. I'm so sorry I flashed 4.3 with odin...
Click to expand...
Click to collapse
This method works upto 4.1.2