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
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
Hello, as I said in the title, I have a problem with the recovery menu (Same with OR) - problem is I can boot in recovery (the screen with the triangle) but there can not go to the menu. I press Volume Up + camera and nothing happens. Remains the same screen with the triangle and phone.
Please give me a solution because my phone is moving very slowly with Android 2.2.x
Device - Motorola a853 Milestone
Bootloader - 90.78
Button on the camera work, as well as the volume.
What could be the problem?
Sorry for bad English ..
Come on guys, 26 views and no response to my question?
I searched all forums and tried all the solutions posted there, but none worked! But those were old solutions ...
No one knows who could be my problem?
Not sure what kind of problem you are facing. You can surely try this.
Looks like OR is not loading in ur case. You can download the latest OR, I'm using minimod OR, copy the update.zip file into the root of SD card, again reboot into recovery. If u find ur milestone stuck in triangle button try pressing volume up button. This time it should invoke the OR or it should ask u to update the zip file.
Still if it doesnt works i think u have to take advice from experts who can help u to use ADB comnands to troubleshoot further. Anyways best of luck.
Sent from my Milestone using xda app-developers app
like the last post, you should verify if you have OpenRecovery folder and update.zip file in your /sdcard.
You can try via adb or terminal emulation "reboot recovery"
I tried what you said nagabushan.c, but it does not work ... Always the same problem, no menu displays..
At least do u get exclamatory mark when u booted or milestone while pressing camera button ? Then give a sec gap and then press volume up button.
Any device both rooted or non rooted should display this.
Try ADB steps..
Let us know what u observe
Sent from my Milestone using xda app-developers app
nagabushan.c said:
At least do u get exclamatory mark when u booted or milestone while pressing camera button ? Then give a sec gap and then press volume up button.
Any device both rooted or non rooted should display this.
Try ADB steps..
Let us know what u observe
Sent from my Milestone using xda app-developers app
Click to expand...
Click to collapse
I see an exclamation mark only when you press power + x (bootloader 90.78).
I tried ADB steps..not working.
Have you verified OpenRecovery folder and its update.zip on sdcard? Try to re-download and unpack it fresh new.
What rom you said you currently have?
Have you installed vulnerable recovery?
Have you verified OpenRecovery folder and its update.zip on sdcard? Try to re-download and unpack it fresh new.
I tried, does not work ...
What rom you said you currently have?
Stock rom 2.2.x.
Have you installed vulnerable recovery?
Of course, just as there's no difference ... the menu does not show.
The menu should show. Any menu. Either from stock or OpenRecovery. I would try with a different sdcard because the older kernel (2.6.29) in recovery does not support some cards well. If the buttons are working and you have installed everything correctly then it should work. I'd try with different sdcard.
Alternatively, you can try to tell recovery to apply update.zip from sdcard automatically
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
but note that I am not sure if you need to be rooted for that. I assume not. You can either install Terminal emulator from PlayStore or enable usb debbuging in settings and try to connect through adb if you choose to try.
To see if adb detects your device
Code:
adb devices
if all is OK you should get some output (aphanumeric) and after that 16 characters, it should display in what mode is your device (device for a normally booted system, recovery for device in recovery...)
And then
Code:
adb shell
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
reboot
I'm no expert but it might be an unsupported sdcard...
mrvek said:
The menu should show. Any menu. Either from stock or OpenRecovery. I would try with a different sdcard because the older kernel (2.6.29) in recovery does not support some cards well. If the buttons are working and you have installed everything correctly then it should work. I'd try with different sdcard.
Alternatively, you can try to tell recovery to apply update.zip from sdcard automatically
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
but note that I am not sure if you need to be rooted for that. I assume not. You can either install Terminal emulator from PlayStore or enable usb debbuging in settings and try to connect through adb if you choose to try.
To see if adb detects your device
Code:
adb devices
if all is OK you should get some output (aphanumeric) and after that 16 characters, it should display in what mode is your device (device for a normally booted system, recovery for device in recovery...)
And then
Code:
adb shell
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
reboot
I'm no expert but it might be an unsupported sdcard...
Click to expand...
Click to collapse
Here's what I get from cmd:
C:\android-sdk\platform-tools>adb devices
List of devices attached
04037B7518003010 device
C:\android-sdk\platform-tools>adb shell
# echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
cannot create /cache/recovery/command: directory nonexistent
#
My device is rooted wth "superoneclick" method.
es7ar said:
cannot create /cache/recovery/command: directory nonexistent
Click to expand...
Click to collapse
Create it.
Code:
adb shell
mkdir -p /cache/recovery
mrvek said:
Create it.
Code:
adb shell
mkdir -p /cache/recovery
Click to expand...
Click to collapse
C:\android-sdk\platform-tools>adb shell
$ mkdir -p /cache/recovery
mkdir -p /cache/recovery
mkdir failed for -p, Read-only file system
$
Try without -p
Code:
mkdir /cache/recovery
mrvek said:
Try without -p
Code:
mkdir /cache/recovery
Click to expand...
Click to collapse
I created the folder "recovery" inside "cache" with root explorer.
Now cmd shows me: ( check attachments )
are you missing "echo"?
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
it simply writes what is in the first argument (in quotes) to file named "command" located in /cache/recovery
Edit: you can ommit adb devices. You just test the first time when you connect to be sure if adb detects your device. After that it should generally give "device not found" or something like that if connection to device is lost.
I do not understand ...
The command "echo" - update_package = sdcard: update.zip "> / cache / recovery / command" should create a file called "command" in the folder "recovery" from the "cache"?
If so, there is no file called "command"
Sorry, I'm newbie ... I do not want to stress you out.
Edit : Hmm ...
Instead of reboot, like you said, I typed "reboot recovery" then restated the phone ... and the loading bar appears. The phone has rebooted when it came to approx. 30% ..
es7ar said:
I do not understand ...
The command "echo" - update_package = sdcard: update.zip "> / cache / recovery / command" should create a file called "command" in the folder "recovery" from the "cache"?
If so, there is no file called "command"
Sorry, I'm newbie ... I do not want to stress you out.
Click to expand...
Click to collapse
Yes, it should create that file with that content, to instruct recovery to automatically apply update.zip.
You can try to create that file manually with the
Code:
--update_package=SDCARD:update.zip
content in it.
Could you post the content of
Code:
mount
executed in adb? i was sure you can write to cache, it should be mounted read-write.
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
es7ar said:
Edit : Hmm ...
Instead of reboot, like you said, I typed "reboot recovery" then restated the phone ... and the loading bar appears. The phone has rebooted when it came to approx. 30% ..
Click to expand...
Click to collapse
hm...
could you please execute in adb:
Code:
ls -laR /sdcard/OpenRecovery /sdcard/*.zip
post output.
Okay, it looks like it was done!
You've explained it very well ... but I did not openrecovery and update.zip in sdcard.
I thank you so much for helping me! Thanks a lot!!
es7ar said:
but I did not openrecovery and update.zip in sdcard
Click to expand...
Click to collapse
That leads us back to the very begining of the process...
I guess you guys restoring roms like i just did, and eventually got into problem/error message that md5 mismatch.
I managed to fix it without using adb shell or terminal emulator on phone etc. In case that you can not boot into rom and you want to restore previous rom.
1. Download notepad ++ (it is free)
2. Put your SD card into PC
3. Navigate to folder "clockworkmod/backup/DateWhenBackupCreated"
IMPORTANT First try to rename your backup folder without spaces, and then try to restore.
If it is already without spaces, continue
4. In notepad++ open file "nandroid.md5" , delete all content of that file (simply by selecting it and "delete") , after that "save".
5. Put SD card back to phone and try to restore again. Should work fine. :victory:
Correct me if im wrong
Will try really soon..
Thanks a lot.
Good, post result how it went :good: :fingers-crossed:
I fix it this way:
Open ADB or Terminal Emulator
Code:
adb shell(for adb) or su(for Terminal Emulator)
# cd /sdcard/clockworkmod/backup/insert backup folder name
# rm nandroid.md5
# md5sum *img > nandroid.md5
Its about fixing it easy way not complicated one but ok, your choice
Sent from my super cool HTC Wildfire using xda app-developers app
Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks
The most probable that there's a problem with permissions.
Make
Code:
chown 0:0 init.rc
chmod 750 init.rc
before packing ramdisk.
Kostyan_nsk said:
The most probable that there's a problem with permissions.
Make
Code:
chown 0:0 init.rc
chmod 750 init.rc
before packing ramdisk.
Click to expand...
Click to collapse
Thanks a lot ! .... I had not checked the user/groups for the extracted files ...
gguemez said:
Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks
Click to expand...
Click to collapse
I suggest, use kitchen.
gguemez said:
Hi,
I am trying to build a custom boot image to get rid of the immutable files of my P7-L00.
Specifically I haved done this : At a specific point in the boot process the rc scripts execute the set_immutable command with a 1 parameters that sets the immutable bits in all the files mentioned in the set_immutable.list file. If this command is changed to a 0 it clears the immutable bit for all the files. I have buit the custom ramfs necesary for this but when I repack the boot image it will not boot.
I am using the following command for mkbootimg ....
mkbootimg --kernel mykernel.img --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x04000000 --base 0x07000000 --cmdline "k3v2mem k3v2_ion=1 vmalloc=448M maxcpus=4 initcall_debug=n" -o newimg.img
The resulting first page looks ok, it has the same offsets as my original working boot image, but as I mentioned before, it does not boot, but just cycles back to fastboot mode after about 1 minute.
Any help will be appreciated,
Thanks
Click to expand...
Click to collapse
You are correct in saying that modifying the setimmutable binary flag from 1 to 0 in the boot image solves the set_immutable.list problem referred to many times in various posts in this forum..
I have a P7-L07 emui2.3 B125 and a P7-L10 emui3.0 B609. I had no trouble modifying the boot.img for the L07 using
linux-kernelkitchen-0.002 under xubuntu. The L10 is a different story but the main problem is faulty flash memory.
At any rate, you don't really need to worry about the boot.img file at all. A simple and easy work around is to replace the file set_immutable.list with another empty file of the same name. This works quite well on my L10. I used the file manager FX to achieve this. As long as you have root access and can change file permissions correctly this method will work for you.
arthios said:
You are correct in saying that modifying the setimmutable binary flag from 1 to 0 in the boot image solves the set_immutable.list problem referred to many times in various posts in this forum..
I have a P7-L07 emui2.3 B125 and a P7-L10 emui3.0 B609. I had no trouble modifying the boot.img for the L07 using
linux-kernelkitchen-0.002 under xubuntu. The L10 is a different story but the main problem is faulty flash memory.
At any rate, you don't really need to worry about the boot.img file at all. A simple and easy work around is to replace the file set_immutable.list with another empty file of the same name. This works quite well on my L10. I used the file manager FX to achieve this. As long as you have root access and can change file permissions correctly this method will work for you.
Click to expand...
Click to collapse
Thank your for the info. In the P7-L00 with a KingUser Root I could not change the set_immutable.list to anything. Any attempt to modify the file, replace or change the permissions would fail, since the immutable bit was set.
Having fixed the problem I mentioned above I now find myself with the situation that if I change some, I can't say all files, in the system directory the phone reboot immediately. I dont know if this is due to the "partial" root some people say kinguser provides or to some other issue.
I will keep playing around, thanks for the help.
gguemez said:
Thank your for the info. In the P7-L00 with a KingUser Root I could not change the set_immutable.list to anything. Any attempt to modify the file, replace or change the permissions would fail, since the immutable bit was set.
Having fixed the problem I mentioned above I now find myself with the situation that if I change some, I can't say all files, in the system directory the phone reboot immediately. I dont know if this is due to the "partial" root some people say kinguser provides or to some other issue.
I will keep playing around, thanks for the help.
Click to expand...
Click to collapse
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.
majcomtech said:
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.
Click to expand...
Click to collapse
Thanks, do you also get the same effect of an immediate reboot when you modify system files? That is what I am really after, since I can't change anything I can't even update the SU or change any files ...
gguemez said:
Thanks, do you also get the same effect of an immediate reboot when you modify system files? That is what I am really after, since I can't change anything I can't even update the SU or change any files ...
Click to expand...
Click to collapse
if you want full root, i already made tut for that. http://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
majcomtech said:
changing the 1 to 0 of set_immutable in rc won't work. i already tried that thing. i used 609 boot.img, unpack and repack it successfully but it wont work.
Click to expand...
Click to collapse
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something. I an now trying to do this via a UPDATE with CWM...
Thanks again.
gguemez said:
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something. I an now trying to do this via a UPDATE with CWM...
Thanks again.
Click to expand...
Click to collapse
I expect you are quite fed up by now and I offer my commiserations. There may be however be another solution to your problem. Have you considered downloading a custom ROM for your L00 created (say) by KangVIP or Killprocess, and then extracting the boot image from the zip file and flashing that? These boot images have the set_immutable flag set to 0. As I recall, the ROMs from KangVIP are password protected so a Killprocess ROM or one from someone else might be better. If you do decide to try this out, make sure the build number of the downloaded ROM is similar to yours. The boot images differ between emui2.3 and emui3.0. Good luck!
gguemez said:
Thanks, I have tried this but in my case it has not worked. Everytime I reboot the phone the files are all back, as if there is a backup partition or something.
Click to expand...
Click to collapse
Seems like you have locked bootloader.
Kostyan_nsk said:
Seems like you have locked bootloader.
Click to expand...
Click to collapse
No, the bootloader is unlocked. I can change the boot partition at will, I have many times letf it unbootable and restored it with no problem. I will try to do something via the recovery parition but, the only one I have found that worked in my phone, always gives me errors when running my scripts (so I am obviously doing something wrong).
I got to the point of sending a script that says ... ui_print ("Hello World"); ... but that gives me an error too!
I will keep trying to figure this out, thanks for your help.
Guillermo
What value has "fblock=" parameter in "/proc/cmdline"?
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
How did you install that Hong Kong lollipop?
mca1 said:
hello dears,
i have very big problem with my c6603. i installed first lollipop hongkong version to my c6603. every function works but i want to install mods and other roms but; my phones usb port doesnt let the pc recognize as "phone". it is not driver problem ; it is hardware failure definetly. the port just charging my phone. And on the phone there is no recovery and download mode. But phone has root. i tried a few things to install custom recovery but couldnt be success. unlocked bootloader but no recovery as i said. i really appreciate if there is a solution. many thanks
Click to expand...
Click to collapse
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.
i installed hk lollipop zip from my custom twrp recovery. and when rom istall has finished ; recovery gone.
mrp1375 said:
Hi there.If you have root access and unlocked bootloader,you can install TWRP even without pc connection.
first you should download a terminal emulator app from google play.
then you should download the latest version of TWRP image file from here https://dl.twrp.me/yuga/.
Place it in the root of your /sdcard folder and rename it to twrp.img
Run the following commands in terminal app
Code:
su
and then we write recovery image file to FOTA with dd command.
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
and it's done.
press thanks if it was helpful.
Click to expand...
Click to collapse
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.
mca1 said:
thank you mrp1375 but i tried this method and when i want to go recovery phone only restarts. because phone has no stock recovery.
Click to expand...
Click to collapse
Below are 2 solutions to get a properly working recovery
Preperation:
1. Download Dual recovery installer: XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip
2. Install NDRUtils
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this: http://nut.xperia-files.com/path/XZDualRecovery/Kernel_Builder
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: X-plore File Manager The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!
thank you
mca1 said:
thank you
Click to expand...
Click to collapse
Does that mean it worked?
tetsuo55 said:
Does that mean it worked?
Click to expand...
Click to collapse
Yes it worked, thank you much. :good:
tetsuo55 said:
Below are 2 solutions to get a properly working recovery
Next up we will test if the TWRP you installed works or not
-open NDRUtils and choose to boot into TWRP recovery.
Now unhide the result that you got to continue with the installation:
OK: I am now in TWRP
flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and reboot.
Everything will work normally now.
Not OK: I am not in TWRP
Reboot the phone if you have to (hold power until you feel 3 vibrations and then turn the phone back on)
You need to download this:
To get the right file make sure to selec the xperia z c6603 and select the rom version you are using, you can view what you have in settings, about phone, build number.
it will be much easier for you if you install this: The reason i recommend this application is that it automatically makes sure the file rights are correct.
Go into the settings and enable superuser +mount root mode
Now you can browse to the folder where you downloaded the zip in the left pane.
go into the zip and and then into tmp
Select the boot.img
now move to the right pane and browse to the root of your SD card like the comment above
go back to the left pane and with boot.img still checked click copy.
Now follow the original instructions mrp1375 gave you, but notice the different filename
Open terminal
Type : su
Type: dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now you can reboot and if it worked the phone will vibrate twice and show a green led meaning you can press the down button to enter TWRP recovery.
Go into the recovery and now flash XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip so you get a proper installation
Now remember this very important fact:
Whenever you flash or wipe anything you MUST reinstall recovery and root again.
This is a failsafe strategy you can NEVER ignore becaus of your usb issues.
Keep SuperSu installer and XZ-lockeddualrecovery installer on your device at all times!
Click to expand...
Click to collapse
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!
comcastic08 said:
Hey! I have the same problem as the OP here. I followed the instructions like 5 times and still couldnt get it to work. The terminal is saying that "No space left on device" when i type "dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
any way to fix this? Thanks!
Click to expand...
Click to collapse
That error sounds like either you dont have root or you have a typo, can you make a screenshot?
tetsuo55 said:
That error sounds like either you dont have root or you have a typo, can you make a screenshot?
Click to expand...
Click to collapse
snag. gy/gi8Ji. jpg
sorry i cant post links yet
comcastic08 said:
snag. gy/gi8Ji. jpg
sorry i cant post links yet
Click to expand...
Click to collapse
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.
tetsuo55 said:
That doesnt look quite right it should look like this:
Code:
[email protected]:/ $
Then you type "su" (without the quotes) and press enter
The display then changes to:
Code:
[email protected]:/ #
Now you type "dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel" (without the quotes) and press enter
And then it should work properly.
Click to expand...
Click to collapse
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh
comcastic08 said:
i typed su before that code and the same error occured sadly
why did my usb port had to break ugh
Click to expand...
Click to collapse
Can I have another screenshot of that?
tetsuo55 said:
Can I have another screenshot of that?
Click to expand...
Click to collapse
snag .gy/AekHa. jpg
comcastic08 said:
snag .gy/AekHa. jpg
Click to expand...
Click to collapse
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.
tetsuo55 said:
In that screenshot i see again the same mistake i mentioned before
please do this
Just type only su and enter
and then send me the screenshot of that.
Click to expand...
Click to collapse
snag. gy/aWyCY .jpg
comcastic08 said:
snag. gy/aWyCY .jpg
Click to expand...
Click to collapse
All i can think of is that you have the wrong boot.img
tetsuo55 said:
All i can think of is that you have the wrong boot.img
Click to expand...
Click to collapse
i downloaded the one you said XZ-lockeddualrecovery2.8.23-RELEASE.combined.zip and renamed it to boot.img
even the twrp.img doesnt work ugh