Related
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
Hey guys Lets get the ball rolling and get some development out into the light.
First you will have to download the OTA from Google.
Google’s OTA(13300): http://cache.pack.google.com/edgedl....1f63ef63d1f43c6222116806e5bea38a47e9f124.zip
Next download “SquashFS Exracter”, this tool is used to extract the System.img.
SquashFS Exracter: https://mega.co.nz/#!oEMFQCrC!JbD_9XeS28xu7vZBDipBzDWqdnF1i9cKMRzq2i_vEDU
When you are ready to go, simply drag system.img onto unsquashfs.exe, and the extraction will do its thing.
A new folder named “squashfs-root” will be where the system.img were located. This folder contains the extracted System.
Have a look around, and please report findings! :fingers-crossed:
Findings
/res/ - Contains some of the images used for the system. The boot animation is placed here.
/netflix/ - Self-explanatory. The Netflix app for the Chromecast.
/chrome/content_shell.pak – Contains a lot of useful information for the right eyes.
/chrome/osd_images/**** - Contains images used for the on-screen-display atm. volume slider.
/chrome/locals/ - Contains language files for the Chromecast.
Thx to ddggttff3 and tchebb for the links etc. :good:
Just FYI guys, here is link for newest OTA, build 19084, so you can check, what's new is inside.
http://cache.pack.google.com/edgedl/googletv-eureka/stable-channel/ota.19084.stable-channel.eureka-b3.0149464816d26917f37cb4a263171183cc00957a.zip
For extract system.img download and use SquashFS Exracter tool from previous post.
bormeth said:
Hey guys Lets get the ball rolling and get some development out into the light.
First you will have to download the OTA from Google.
Google’s OTA(13300): http://cache.pack.google.com/edgedl....1f63ef63d1f43c6222116806e5bea38a47e9f124.zip
Next download “SquashFS Exracter”, this tool is used to extract the System.img.
SquashFS Exracter: https://mega.co.nz/#!oEMFQCrC!JbD_9XeS28xu7vZBDipBzDWqdnF1i9cKMRzq2i_vEDU
When you are ready to go, simply drag system.img onto unsquashfs.exe, and the extraction will do its thing.
A new folder named “squashfs-root” will be where the system.img were located. This folder contains the extracted System.
Have a look around, and please report findings! :fingers-crossed:
Findings
/res/ - Contains some of the images used for the system. The boot animation is placed here.
/netflix/ - Self-explanatory. The Netflix app for the Chromecast.
/chrome/content_shell.pak – Contains a lot of useful information for the right eyes.
/chrome/osd_images/**** - Contains images used for the on-screen-display atm. volume slider.
/chrome/locals/ - Contains language files for the Chromecast.
Thx to ddggttff3 and tchebb for the links etc. :good:
Click to expand...
Click to collapse
I've been playing with unsquash in linux to add stuff to /etc. I realised linux can have a symlinks to a symlincs. So we can rederect /system/etc to /data/etc if we want to. It's probebly not so secure to have several symlincs in a chain, but I wanted ta add stuff like motd and profile to etc without reflasing it evertime I make a change.
First on then Cromecast
-----------------------------
cp -pr /system/ /data
On Debian 7
---------------
su root
apt-get install squashfs-tools
mkdir flash
cd flash
wget http://pdl.team-eureka.com/ota/19084.001.zip
unzip 19084.00.1.zip
unsquashfs system.img
cd squashfs-root
mv etc etc.bk
ln /data/system/etc -s etc
cd ..
rm system.img
mksquashfs squashfs-root system.img
rm -r squashfs-root
zip test1.zip *
And then you flash it with flashcast. Now we got a writable etc catalog. I haven't tryed symlinkc all catalogs in the system dir, but bin and etc are working fine as symlincs to /data/system dir.
Just FYI guys, there is again new build, and here is link for that OTA, build 46278.
http://cache.pack.google.com/edgedl/googletv-eureka/stable-channel/ota.46278.stable-channel.eureka-b3.ef7fdf1f7153dacecc77b7d1a3bb22a97e27ec7e.zip
For extract system.img download and use SquashFS Exracter tool from first post.
Mape0661 said:
I've been playing with unsquash in linux to add stuff to /etc. I realised linux can have a symlinks to a symlincs. So we can rederect /system/etc to /data/etc if we want to. It's probebly not so secure to have several symlincs in a chain, but I wanted ta add stuff like motd and profile to etc without reflasing it evertime I make a change.
First on then Cromecast
-----------------------------
cp -pr /system/ /data
On Debian 7
---------------
su root
apt-get install squashfs-tools
mkdir flash
cd flash
wget (i cant post links... -_-)
unzip 19084.00.1.zip
unsquashfs system.img
cd squashfs-root
mv etc etc.bk
ln /data/system/etc -s etc
cd ..
rm system.img
mksquashfs squashfs-root system.img
rm -r squashfs-root
zip test1.zip *
And then you flash it with flashcast. Now we got a writable etc catalog. I haven't tryed symlinkc all catalogs in the system dir, but bin and etc are working fine as symlincs to /data/system dir.
Click to expand...
Click to collapse
when i try this my CC just hangs at the black screen after the Eureka logo. instead of modifying etc, i just added a text file to etc so i could see if it got flashed. my file is there, and i can use SSH/Telnet and the web controls, it just wont boot past the black screen. Any advise?
casper33 said:
when i try this my CC just hangs at the black screen after the Eureka logo. instead of modifying etc, i just added a text file to etc so i could see if it got flashed. my file is there, and i can use SSH/Telnet and the web controls, it just wont boot past the black screen. Any advise?
Click to expand...
Click to collapse
Were you modifying the image as root? If not, you can have permission issues when rebuilding the squashfs file.
ddggttff3 said:
Were you modifying the image as root? If not, you can have permission issues when rebuilding the squashfs file.
Click to expand...
Click to collapse
well now i feel stupid, indeed i wasn't root, thank you!
Hi I need specific help with the mksquashfs.exe command in Windows to repack system.img to system.sfs
Specifically, if I have the system.img on c:\ temp folder, what is the syntax to end up with system.sfs in same directory.
Can anybody help?
I've been trying to flash a nandroid backup that I downloaded as a zip file via clockworkmod.
I've placed the nandroid zip in the clockworkmod/backup folder, but when I go to restore in clockworkmod it is not seen (only a backup I made earlier).
I pushed the .zip via adb into the /mnt/shell/emulated/clockworkmod/backup/ directory.
Any ideas how to get this to work? I need to return to stock for an insurance claim.
Thanks for any help!
can you do this using ADB ?
adb shell
cd /mnt/shell/emulated/clockworkmod/backup/
ls -la
what is your output?
If there is an error above, try cd /data/media/clockworkmod/backup/
or cd /data/media/0/clockworkmod/backup/
SaHiLzZ said:
can you do this using ADB ?
adb shell
cd /mnt/shell/emulated/clockworkmod/backup/
ls -la
what is your output?
If there is an error above, try cd /data/media/clockworkmod/backup/
or cd /data/media/0/clockworkmod/backup/
Click to expand...
Click to collapse
Output was:
Code:
drwxrwx--- root sdcard_r 2014-02-10 21:27 2014-02-10.21.23.00
drwxrwx--- root sdcard_r 2014-02-12 20:10 2014-02-12.20.04.30
-rw-rw---- root sdcard_r 1034657679 2014-02-11 00:22 ruu.zip
Still can't see the ruu.zip file that I want to restore when I'm in clockworkmod. Is it because it's a .zip or a permission error? I presume the others are folders.
1. Wrong folder location. Evident by no other folders.
2. You can NOT restore ruu.zip file. It need to be unzipped and the content pushed to a new folder
SaHiLzZ said:
1. Wrong folder location. Evident by no other folders.
2. You can NOT restore ruu.zip file. It need to be unzipped and the content pushed to a new folder
Click to expand...
Click to collapse
Thanks, I got it to show up.
Next problem however, is a MD5 mismatch. No knowledge on how to fix this, if possible. Are you aware?
Thanks again
Maybe an older cwm version. Sorry can't help. But there maybe an option to skip md5 check if you are certain you have right file
sent from my mobile device
SaHiLzZ said:
Maybe an older cwm version. Sorry can't help. But there maybe an option to skip md5 check if you are certain you have right file
sent from my mobile device
Click to expand...
Click to collapse
No worries, thanks though. Ended up flashing a different stock rom instead. Removed tampered, relocked and s-on. Finally.
SPRINT FACTORY SYSTEM IMAGE FILES
LG LS991 ZV5/ZV6
I have compressed and uploaded FACTORY SYSTEM image files for both ZV5 and ZV6.
NOTE: You should only flash the image version you are currently running!
Sprint LS991 ZV5 Factory System Image File:
ZV5 System Image Link
MD5: 29f64a55862a5f43e5ac450d073a6a84
Sprint LS991 ZV6 Factory System Image File:
ZV6 System Image Link
MD5: e31125d22df1882d5247b046476b04c5
You may flash these by using the same command from the software you used to root your G4
1.) Unzip and copy the img file to your phones internal memory.
2.) Open an administrator command prompt in windows with your phone plugged in and go to original directory you used to root your phone. (LG ROOT)
3.) Type 'Ports.bat' in the window prompt to view what port your LG G4 is connected to.
4.) Type in the window (change COM4 to your port number if different):
Code:
Send_Command.exe \\.\COM4
5.) In the command prompt type (change to ZV5 to ZV6 if you are restoring that version):
Code:
dd if=/data/media/0/systemZV5.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
Once completed, reboot and you will have a fully stock system again.
/.
SPRINT FACTORY ROOTED SYSTEM IMAGE FILES
LG LS991 ZV5/ZV6
I have compressed and uploaded ROOTED FACTORY SYSTEM image files for both ZV5 and ZV6.
NOTE: You should only flash the image version you are currently running!
Sprint LS991 ZV5 Factory System ROOTED Image File:
ZV5 Rooted System Image Link
MD5: 06c7820e317d0870a5e6e35325eed29e
Sprint LS991 ZV6 Factory System ROOTED Image File:
ZV6 Rooted System Image Link
MD5: 703cc7070911e009ece40d960763a4d3
You may flash these by using the same command from the software you used to root your G4
1.) Unzip and copy the .img file to your phones internal memory.
2.) Open an administrator command prompt in windows with your phone plugged in and go to original directory you used to root your phone. (LG ROOT)
3.) Type 'Ports.bat' in the window prompt to view what port your LG G4 is connected to.
4.) Type in the window (change COM4 to your port number if different):
Code:
Send_Command.exe \\.\COM4
5.) In the command prompt type (change to ZV5 to ZV6 if you are restoring that version):
Code:
dd if=/data/media/0/rootedsystemZV5.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
Once completed, reboot and you will have a fully ROOTED stock system.
/.
OTA Update File: (From OTA Captured)
Warning: Once you take the ZV6 Upgrade, you can NEVER TOT back to ZV5 (at this time) or you will brick your device! There is protection in-place to prevent reverting versions.
Sprint LS991 ZV5--->ZV6 Factory Update File:
ZV6 Update Link
MD5: 42ceb7516080e2d20d7ce56d4581707e
Update ZV6 Instructions:
Update ZV5 To ZV6 Update File Instructions:
*you may need to update your adb/drivers first*
http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160 -thanks to @misteroh
1.) Put Back To Factory ZV5 (No Root or Modded Files!)
2.) Copy the updateZV6.zip file to the same directory you have the ADB files / command you used for root
3.) Plug in phone to computer and open an Admin Command Prompt in the ADB files directory you used to root
3.) Boot your phone to RECOVERY (turn off - hold down power and vol down till you see recovery txt and release)
4.) From phone recovery menu scroll down and select 'Apply Update From ADB'
5.) In your admin command prompt, type 'ADB SIDELOAD updateZV6.zip'
Wait for the update to finish before touching! Don't turn of power or interrupt! When ADB terminal returns after completion, remove cable and reboot. You now should have ZV6!
* Developers *
Kernel/Modem Files: (Use At Your Own Risk - More For Developers!)
ZV6 Kernel Image Link
MD5: c53b75439e4baad9f7309366d454db70
ZV6 Modem Image Link
MD5: 7ec96d6c92e599f0f621fe3e93c8d932
ZV5 Kernel Image Link
MD5: c18bc2cc8d68b19e808011953040d69d
ZV5 Modem Image Link
MD5: e9e59fa19964fa1682c96092fa47118b
Thanks so much for doing this for us!
Just to make sure I got this right: I'm currently on ZV5 rooted. If I wanted to take the ZV6 OTA I would use the method above with the ZV5 image and then I'll be totally stock? What will get wiped? Once I take ZV6 OTA is there a way to root it?
---------- Post added at 06:50 PM ---------- Previous post was at 06:50 PM ----------
Agimax said:
Request: I forgot to pull ZV5 Modem and Kernel partition images before i updated to ZV6. If someone could be so kind as to pull both of those, i will upload and add them to the link also.
Click to expand...
Click to collapse
I'll do it you tell me how. I'm on rooted ZV5
Yes, you can root ZV6.
If you do it right you won't lose anything.
I posted a thread on ZV6 root in general forum.
mswlogo said:
Yes, you can root ZV6.
If you do it right you won't lose anything.
I posted a thread on ZV6 root in general forum.
Click to expand...
Click to collapse
Thanks, i am also posting Stock Rooted Images in post #2 for those that want them. It will be a few hours before the Images finish uploading. I'll also upload the ZV6 update zip for those that need it. I'm about 60% done with the UltraPOP V1 ROM for the G4 also
SantinoInc said:
Thanks so much for doing this for us!
I'll do it you tell me how. I'm on rooted ZV5
Click to expand...
Click to collapse
Thank you!
Open Command Prompt (Admin rights) In Windows or Linux or Android Terminal
1.) type 'adb shell' then at the $ prompt type 'SU' to gain superuser rights in the shell window and accept the prompt on the Phone
2.) Type For The Kernel:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/kernelZV5.img
3.) Type for the Modem:
Code:
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modemZV5.img
I already have them for ZV6. I appreciate this!
Agimax said:
Thank you!
Open Command Prompt (Admin rights) In Windows or Linux or Android Terminal
1.) type SU to gain superuser rights in the shell window and accept the prompt on the Phone
2.) Type For The Kernel:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/kernelZV5.img
3.) Type for the Modem:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modemZV5.img
I already have them for ZV6. I appreciate this!
Click to expand...
Click to collapse
My ADB skills are garbage. Do I just open a command prompt in C>program files> ...platform tools
When I type SU there it says its not recognized as a command.
Edit: On terminal editor when I typed the command for the Kernel I get: NO such file or directory.
I've been rooting since EVO 4G and I still can't do shiiiiit on ADB. It's sad.
SantinoInc said:
My ADB skills are garbage. Do I just open a command prompt in C>program files> ...platform tools
When I type SU there it says its not recognized as a command.
Edit: On terminal editor when I typed the command for the Kernel I get: NO such file or directory.
I've been rooting since EVO 4G and I still can't do shiiiiit on ADB. It's sad.
Click to expand...
Click to collapse
Sorry, type 'adb shell' from command prompt first then after you get a $ prompt type `su' which you will have to accept prompt on phone.
Was my fault not yours, I also gave you the commands for the G2 instead of G4 by accident, use these: (I corrected original post too)
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/kernelZV5.img
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modemZV5.img
/.
So, I think I messed up. I reverted to v5 unrooted, then tried to upgrade to v6 rooted and Im getting a security error on the LG screen.
Agimax said:
Sorry, type 'adb shell' from command prompt first then after you get a $ prompt type `su' which you will have to accept prompt on phone.
Was my fault not yours, I also gave you the commands for the G2 instead of G4 by accident, use these: (I corrected original post too)
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/kernelZV5.img
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modemZV5.img
/.
Click to expand...
Click to collapse
Getting permission denied for both the modem and kernel. Thoughts? Also, if this was successful where exactly would the MODEM and KERNEL be saved? I'm guessing the rootfolder of the internal SD card?
---------- Post added at 09:55 PM ---------- Previous post was at 09:53 PM ----------
jaxbierley said:
So, I think I messed up. I reverted to v5 unrooted, then tried to upgrade to v6 rooted and Im getting a security error on the LG screen.
Click to expand...
Click to collapse
From rooted V5 you used the method in the OP of this thread? Did following the instructions in the OP lead you to stock unrooted V5? If so, were you able to take the OTA to V6? At what step did stuff get messed up exactly? I'm asking because I'm going to be attempting this soon too but I'm being overly cautious with this phone.
SantinoInc said:
Getting permission denied for both the modem and kernel. Thoughts? Also, if this was successful where exactly would the MODEM and KERNEL be saved? I'm guessing the rootfolder of the internal SD card?
---------- Post added at 09:55 PM ---------- Previous post was at 09:53 PM ----------
From rooted V5 you used the method in the OP of this thread? Did following the instructions in the OP lead you to stock unrooted V5? If so, were you able to take the OTA to V6? At what step did stuff get messed up exactly? I'm asking because I'm going to be attempting this soon too but I'm being overly cautious with this phone.
Click to expand...
Click to collapse
I first did V5 unrooted. All worked well. Then I did the exact same thing, except with V6 rooted and got a security error. I did not receive the OTA either. I just did a TOT restore, and still no OTA. I'm going to try to upgrade V6 with the images in the OP and see what happens. Perhaps I should have done the stock unrooted image before trying the rooted image.
jaxbierley said:
So, I think I messed up. I reverted to v5 unrooted, then tried to upgrade to v6 rooted and Im getting a security error on the LG screen.
Click to expand...
Click to collapse
You need to put v5 unrooted back on the phone, then use the 'UpdateZV6.zip' smaller file to update (in the third post -has dropdown step instructions).
jaxbierley said:
I first did V5 unrooted. All worked well. Then I did the exact same thing, except with V6 rooted and got a security error. I did not receive the OTA either. I just did a TOT restore, and still no OTA. I'm going to try to upgrade V6 with the images in the OP and see what happens. Perhaps I should have done the stock unrooted image before trying the rooted image.
Click to expand...
Click to collapse
Also important:
After taking the ZV6 update - WE CAN NEVER USE TOT GOING BACK TO ZV5, there is protection in place and will brick your device. I posted in the ZV5 TOT thread hoping the OP would attach the disclaimer a few days ago.
Luckily, you didn't take the ZV6 update yet so you are safe.
SantinoInc said:
Getting permission denied for both the modem and kernel. Thoughts? Also, if this was successful where exactly would the MODEM and KERNEL be saved? I'm guessing the rootfolder of the internal SD card?
Click to expand...
Click to collapse
Would be saved on the root of your internal memory SDCARD (Not External).
Permission Denied Possibilities:
1.) You aren't rooted or your superuser prog is set to deny
2.) You didn't type SU in the shell that changes the $ to the # and asks your phone with a popup for root permission.
3.) You denied the popup for the shell asking your phone for root.
If after you ran 'adb shell' command and then typed 'su' there should be a popup for permission to access on your phone and then the '#' sign will appear in the shell prompt.
* also i don't want to confuse others about the instructions for pulling the Modem & Kernel from the ZV5 with flashing System images or thinking this is part of the process in the OP when it is not. *
/.
Agimax said:
Also important:
After taking the ZV6 update - WE CAN NEVER USE TOT GOING BACK TO ZV5, there is protection in place and will brick your device. I posted in the ZV5 TOT thread hoping the OP would attach the disclaimer a few days ago.
Luckily, you didn't take the ZV6 update yet so you are safe.
Click to expand...
Click to collapse
yea, i had thought i was screwed. thanx for the help, sideloading update now. Then going to root with info in post 2. Thanx for all of this information
jaxbierley said:
yea, i had thought i was screwed. thanx for the help, sideloading update now. Then going to root with info in post 2. Thanx for all of this information
Click to expand...
Click to collapse
Glad you finally got it!:good:
I wish they would change the ZV5 TOT method with a huge RED warning for people on ZV6.
I need a DEODEX ROM!
Is there anyone who make deodex rom?
Agimax said:
Glad you finally got it!:good:
I wish they would change the ZV5 TOT method with a huge RED warning for people on ZV6.
Click to expand...
Click to collapse
Ok, I finally got it to work w/o an issue. I just overlooked granting SU permission on the phone as you pointed out. Now I just have to find where it saved the modem and kernel img...
EDIT: Found them. Where is the best place to upload them? I think they are too big to upload here on XDA
---------- Post added at 11:41 AM ---------- Previous post was at 11:20 AM ----------
modem ZV5: http://expirebox.com/download/fba59672c924499cc80c414e4374b11d.html
kernel ZV5: http://expirebox.com/download/5be7fe2143d04fd4ca51ccd3164ba124.html
These files will self delete in TWO days. Feel free to mirror them or do whatever you like with them!
SantinoInc said:
Ok, I finally got it to work w/o an issue. I just overlooked granting SU permission on the phone as you pointed out. Now I just have to find where it saved the modem and kernel img...
EDIT: Found them. Where is the best place to upload them? I think they are too big to upload here on XDA
Click to expand...
Click to collapse
Wherever you would like just PM or Post the link please and i will re-upload them to the Androidfilehost site with the rest of them.
Thank you for doing this!
EDIT: just saw the edited links. I will grab them tonight. Thanks again.
I've tried to find a tutorial for this, but seems like it doesn't exists. So I've learned about S6, Note 5 and even a russian Note 3 Neo tutorials to make it work. So let's start!
What do you need?
-Patience
-A PC with a Photo Editor (Paint.net should do the trick)
-Terminal Emulator with a little of practice
-(Optional) an external keyboard, since you have to execute quite a lot of commands and there's no way to copy paste into a terminal like in CMD.
1)We start by pulling "param.bin" file out:
It's located in /dev/block/mmcblk0p8 so we have to execute these commands:
Code:
su
dd if=/dev/block/mmcblk0p8 of=/mnt/sdcard/param.bin bs=4096
2) This will extract param.bin to your main sdcard folder, then we have to create a new folder and then untar it, by executing this:
Code:
mkdir /sdcard/param
cd /sdcard/param
tar xf /sdcard/param.bin
3) If everything went fine, you should see a folder called "param" with all the bootloader's images. We will focus on logo.jpg, but you can change the others like download.jpg and warning.jpg. Extract these files to your PC and edit them, make sure that the images doesn't go up to 400 kb, otherwise they will not show in the device. To achive this you can downgrade the JPEG quality from 100% to 80% or any % you feel confortable to use. Once you finish the editing process, place them inside your main /sdcard folder.
4)Now we have to paste your edited images inside /sdcard/param folder and retar param.bin, we have to execute these commands:
Code:
cp -f /sdcard/logo.jpg /sdcard/param/logo.jpg
(OPTIONAL) cp -f /sdcard/warning.jpg /sdcard/param/warning.jpg
(OPTIONAL) cp -f /sdcard/download.jpg /sdcard/param/download.jpg
rm -f /sdcard/param.bin
cd sdcard/param
tar cf - `ls | sort -t.` > /sdcard/param.bin
5) Last but not least, we have to place param.bin back again in the system, so:
Code:
dd if=/sdcard/param.bin of=/dev/block/mmcblk0p8 bs=4096
If everything went fine, reboot and you will see the new logos come up! Make sure to backup param.bin once it gets extracted, in case if something goes wrong. There's no way to brick the device, the major risk is a blackscreen while booting, but the device will boot fine so you can repair it without problem (IF you made a backup, otherwise you will have to reflash the bootloader in ODIN).
I hope you like it! Leave your questions below and I'll try to answer them ASAP. Cheers!
tar xf /sdcard/param.bin gives me sh: tar: not found
MehmetAliCan said:
tar xf /sdcard/param.bin gives me sh: tar: not found
Click to expand...
Click to collapse
Make sure that the param.bin is located in /sdcard and not in any other folder. Try to run the script in SH Script Runner as Root and see if it works.
Thanx for your work.can we copy/past into terminal cmd without external keybord.??
---------- Post added at 02:24 PM ---------- Previous post was at 01:38 PM ----------
tar cf - `ls | sort -t.` > /sdcard.....gives me no such file...tar:error exit delayed from previos errors
khalifnet said:
Thanx for your work.can we copy/past into terminal cmd without external keybord.??
---------- Post added at 02:24 PM ---------- Previous post was at 01:38 PM ----------
tar cf - `ls | sort -t.` > /sdcard.....gives me no such file...tar:error exit delayed from previos errors
Click to expand...
Click to collapse
Nope, there's no way to copy/paste in terminal emulator atm.
There's a zip below, unzip it and paste the *.sh script file inside your device and run it (Root Browser works for me) as root. If everything went fine, you should see this dialog:
Code:
Finished executing script file
exit value 0
stdout:
null
stderr:
null
Then a file named "param.bin" will be generated in your main SDCard folder. After that run the last command to paste it inside the bootloader again:
Code:
dd if=/sdcard/param.bin of=/dev/block/mmcblk0p8 bs=4096
Reboot and you will see your new bootlogo!
Thnx mr galaxynote2 for your reply.i follow your tuto and succed to have both param.bin and param.modifyed logo.jpg ,place it in sdcard but when when i execut cmd to retar it gives me no such a directory
Plz mr galaxynote2 have a look in attached file
khalifnet said:
Plz mr galaxynote2 have a look in attached file
Click to expand...
Click to collapse
That's because you're already in sdcard/param. There's no need to use "cd sdcard/param" command. Just go ahead with the tutorial :good:
This works great, you can copy paste with "terminal emulator for android" made by Jack Palevich, is in the play store, I use multi-window to open the browser and terminal, then copy from browser and long-press on terminal to paste.
I edited the .jpg with faststone image viewer
Don t succed at all.i don t know why?!any help?!thnx and sorry for my english
khalifnet said:
Don t succed at all.i don t know why?!any help?!thnx and sorry for my english
Click to expand...
Click to collapse
That's because you're using (') instead of (`). Use the script I provided earlier :good:
Thanks mr galaxynote2 for your quik reply.finally all the process goes fine but no change.still got note4 bootlogo.can copy past modifyed logo.jpg in param folder??thanx
i always ended up with black screen xD even how much i resize the .jpg the original photo size is 89.9kb . resizing my new logo to 69.1 kb, 76.9 kb still dont work xD do you have technique to make it work . im using photoshop and i i also tried Paint.net. . no luck
Thanks for the tutorial!
Does anyone else also have a tar checksum error or has anybody a solution to this?
BTW, i'm using the COH4 version bootloader.
@galaxynote2 this guide should work on F variants as well, but not with mmcblk0p8 but mmcblk0p12 (or at least that is what diskinfo tells me )
great guide though :good:
Ok , time for some troubles
I followed this guide and tried to do this with a custom image . It bricked my phone and I need help plz.
The power button do nothing at all , recovery mode is not starting , the only thing that works is download mode , that is a good sign .
Now , I flashed OI6 bootloader from wanam's thread , Nothing happens , after the flashing is done , the phone turns into black screen and I have to remove battery to start download mode again.
flashed N910CXXU1COH4_N910COXA1COH4_N910CXXU1COH4_HOME.tar.md5 , still nothing happens !
What is really interesting is that the download mode uses the green warning image from @galaxynote2 thread .
I think I need the stock param.bin to be flashed via oden . but I do not know how to do so , is this right ? and how ?
Thanx a lot for any help.
APCOtech said:
Ok , time for some troubles
I followed this guide and tried to do this with a custom image . It bricked my phone and I need help plz.
The power button do nothing at all , recovery mode is not starting , the only thing that works is download mode , that is a good sign .
Now , I flashed OI6 bootloader from wanam's thread , Nothing happens , after the flashing is done , the phone turns into black screen and I have to remove battery to start download mode again.
flashed N910CXXU1COH4_N910COXA1COH4_N910CXXU1COH4_HOME.tar.md5 , still nothing happens !
What is really interesting is that the download mode uses the green warning image from @galaxynote2 thread .
I think I need the stock param.bin to be flashed via oden . but I do not know how to do so , is this right ? and how ?
Thanx a lot for any help.
Click to expand...
Click to collapse
If u tried wanams bootloader it wont work even if you put to bl/ap .. try 5.1.1 bootloader posted in DN5 rom it will work just put it to BL
Near_07 said:
If u tried wanams bootloader it wont work even if you put to bl/ap .. try 5.1.1 bootloader posted in DN5 rom it will work just put it to BL
Click to expand...
Click to collapse
Thanx , i will try it now
EDIT : It worked , thanx a lot @Near_07
Keep getting invalid tar header checksum?
Finally , without a brick
Used Paint.net only and the quality down to 40% , final size 189KB
Too bad , I could not hide the kernel msg with red background.
Thanx @galaxynote2 for the tutorial , @Near_07 for helping