Database Develop

Tattoo Custom Recovery Image

I'm starting this thread to document the work on creating a custom recovery image for the Tattoo.
The main goal is to provide a recovery image that will serve as the launchpad for flashing custom roms.
The Tattoo Custom Recovery Image will provide:
1) A way to use an update.zip signed with test-keys (already accomplished);
2) A way to perform a full backup of mtd2,mtd3,mtd4 and mtd5 (boot,system,cache and data).
3) A way to perform a full restore of the backup achieved by 2);
4) Adb support (already accomplished);
4.1) Adb shell support.
I'm open to input about using nandroid. Right now, without a S-OFF/ENG SPL this looks useless.
Also, if you have any other special need for recovery, please feel free to express it

Alpha release
Tattoo's Custom Recovery Image, Alpha Release
This first release includes:
- ADB enabled recovery
- ADB enabled root shell
- Accept update.zip signed with test keys
- All partitions mounted
- Custom recovery program (the last two options are stubs, not really working yet)
- Included in /sbin: busybox, flash_image and BART
- I've not used BART and, at the moment, cannot attest if it works or not.
- Backup script in /sbin/backup.sh
- Restore script in /sbin/restore.sh
With this custom recovery you can now do a full backup of your unit, by dumping the mtd block devices to your sdcard. Afterwards, you can use flash_image to recover your Tattoo to it's previous state.
I'm releasing this image as is. This is not a point-and-click recovery tool. If you don't know what you're doing, you can seriously damage your unit. The only reason I'm releasing this is in an effort to provide other devs with a way to easily recover their units, back to day-to-day configuration, while experimenting with them.
To flash:
Copy TCRI.alpha.img to /sdcard.
Run "flash_image recovery /sdcard/TCRI.alpha.img"
To reboot into recovery (quickest way)
adb reboot recovery
Please comment

thanks for you work

i try to flahs and get permission denied, do you know why?

flash_image: permission denied

chusen said:
i try to flahs and get permission denied, do you know why?
Click to expand...
Click to collapse
Partition remounted writeable from a fresh rebooted system with the tattoo-hack.ko module inserted??
But I'm sure you did that before because of:
I'm releasing this image as is. This is not a point-and-click recovery tool. If you don't know what you're doing...
Click to expand...
Click to collapse
;-)
-bm-

Thank you very much for your excellent job

Someone could install custom alpha recovery?
thx

@-bm-:yes I will try that way since the beginning. i mount with rw permissions /system and /data. i know is not a point-and-click recovery tool but i think i need more permissions but where?

Where did you guys get your flash_image binary from ?
The error you're getting is from flash_image, not from my recovery image.
I'll attach the flash_image I've been using to this post.
Please tell me if this solves your problem. You need tattoo-hack.ko module inserted, if you're using a release kernel.
Edit: You have the correct permissions in your flash_image binary, right ? After pushing it to the device, don't forget to chmod 755

It works I like drawing, jejeje.
Backup and Restore functionality appears to have no further
The adb root shell is perfect
Very good Work
for when the beta version? and the final version? lol

I try to dump the system userdata and boot.img and when i try to extract with unyasffs and i get this when i try to extract system.img
Code:
4 [main] unyaffs 3940 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
644 [main] unyaffs 3940 open_stackdumpfile: Dumping stack trace to unyaffs.exe.stackdump
and this with others
Code:
broken image file

Code:
[email protected]:~/Tattoo/images/boot/1$ ../../unpack.pl ./boot.1.img
Page size: 2048 (0x00000800)
Kernel size: 1899580 (0x001cfc3c)
Ramdisk size: 160952 (0x000274b8)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1 console=null
Writing boot.1.img-kernel ... complete.
Writing boot.1.img-ramdisk.gz ... complete.
528 blocks
[ boot.1.img-ramdisk.gz decompressed to boot.img-ramdisk ]
My image dumping script is OK
Take a look here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
The boot.img is not a yaffs2 image. It's a special format, comprised by a 2k header, a kernel image and a ramdisk.
The system.img is a yaffs2 image. From unyaffs's homepage: "Unyaffs is a program to extract files from a yaffs file system image. Now it can only extract images created by mkyaffs2image."
Chusen, I think it would be better to create a new thread for this, since it doesn't concern the custom recovery image directly.

Thank god for custom recovery!
Now we can really start cooking ROMs... gonna break out the tools tonight and get Android 1.6/2.1 sources ready to compile.

leon1984 said:
for when the beta version? and the final version? lol
Click to expand...
Click to collapse
You tell me
Next in line is to tie the backup/restore scripts to the UI, which won't be too hard.
Later, I may mess around with nandroid and bart, to see if they provide something more than my scripts.
Afterwards, when we have some custom roms available, I may create a downloader/updater option, to make it easier to install those.
Also, I'm taking requests for new features

suggestions about scripts
Excellent work, mainfram3. Thank you.
I have extracted the img file, and check backup.sh and restore.sh scripts. The code for checking sdcard remaining space is done. Here it is:
Code:
## TEST: Check free space in sdcard
NEED_KB="200000"
REM_KB=`du /sdcard | awk '{print $6}'`
if [ ${REM_KB%K} -lt $NEED_KB ]; then echo "Not enough space in /sdcard, exiting"; exit; fi
backup space min set to 200MB.
There is another suggestion about restore.sh. Because of backing up img to /sdcard/Backup, $1 might not be needed, right?

mainfram3 said:
Code:
[email protected]:~/Tattoo/images/boot/1$ ../../unpack.pl ./boot.1.img
Page size: 2048 (0x00000800)
Kernel size: 1899580 (0x001cfc3c)
Ramdisk size: 160952 (0x000274b8)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1 console=null
Writing boot.1.img-kernel ... complete.
Writing boot.1.img-ramdisk.gz ... complete.
528 blocks
[ boot.1.img-ramdisk.gz decompressed to boot.img-ramdisk ]
My image dumping script is OK
Take a look here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
The boot.img is not a yaffs2 image. It's a special format, comprised by a 2k header, a kernel image and a ramdisk.
The system.img is a yaffs2 image. From unyaffs's homepage: "Unyaffs is a program to extract files from a yaffs file system image. Now it can only extract images created by mkyaffs2image."
Chusen, I think it would be better to create a new thread for this, since it doesn't concern the custom recovery image directly.
Click to expand...
Click to collapse
and if you want to extract the boot.img here are the two scripts you need to fully extract the kernel(zImage) and ramdisk
split_bootimg.pl
and
extract-ramdisk.sh
they are attached below

jamezelle:
extract-ramdisk.sh missed #!, and the ramdisk zip file should be passed to $1 of this script.

mainfram3 said:
1) A way to use an update.zip signed with test-keys (already accomplished);
Click to expand...
Click to collapse
Hi mainfram3,
I don't want to jack your thread - could you add a little elaboration on this point, or provide a URL so I can learn a little more? The SPL on the phone (oem-78 or fastboot mode) accepts updates signed with the test key from the SDK? (Or some other key?) (On the Eris, the "rom.zip" files unpacked by the RUU are prepended with a mystery blob of 256 bytes - s'pose it could be a mic/sig, but if that's what it is, it don't appear to be in a standard DSA/RSA format, and those .zip files are not signed using the .apk/.jar manifest-signing method)
FYI here's an entertaining story of an epic fail in a related area. After reviewing the fastboot sources from the android tree, I decided that I wanted to spy on the (Windows) RUU update program by sniffing the USB bus - in particular to see if it was explicitly passing signatures in .sig files. (That's an undocumented command-line behavior in fastboot.)
Turns out that recent versions of libpcap and Wireshark allow for USB bus capture on Linux - and using the "usbmon" kernel module in Ubuntu 8.04 LTS, sniffing the USB (5k packet size) seems to work without hitch, even at USB 2.0 speeds. So I took it one step further, and installed WIn Xp SP3 in a QEMU VM on the Ubuntu machine, with the intention of running the RUU updater inside the Xp VM and sniffing the USB bus in the host OS (Linux) machine.
The result? QEMU/Win Xp VM can talk to the phone in either fastboot or adb mode, but bluescreens as soon as you start to move data at any appreciable rate. Doesn't seem to be dependent on whether monitoring is taking place. I might try putting the phone behind a cheapo USB 1.1 hub, and see if that helps, but for the moment I am stopped out on this hack.
bftb0

cn.fyodor said:
jamezelle:
extract-ramdisk.sh missed #!, and the ramdisk zip file should be passed to $1 of this script.
Click to expand...
Click to collapse
it works yea sorry about the
#/bin/sh
i didnt write the scripts btw

[Q] How to remove / replace the boot logo?

I have already successfully removed the boot and shutdown animations (incl. sound) via "adb shell" commands:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
mv /system/media/bootani.qmg /system/media/_bootani.qmg
mv /system/media/samsungani.qmg /system/media/_samsungani.qmg
mv /system/media/video/shutdown/shutdown.qmg /system/media/video/shutdown/_shutdown.qmg
mv /system/media/audio/ui/PowerOff.wav /system/media/audio/ui/_PowerOff.wav
mv /system/etc/PowerOn.snd /system/etc/_PowerOn.snd
mv /system/etc/PowerOn.wav /system/etc/_PowerOn.wav
mount -o remount,ro /dev/mtdblock3 /system
exit
or just download the attached shell script and execute it as su:
adb push nobootani.sh /data/local/nobootani.sh
adb shell
Code:
su
cd /data/local
chmod 777 nobootani.sh
./nobootani.sh
exit
Btw the tablet now boots much faster.
But the boot splash screen from Samsung is still there.
EDIT:
I found out that the boot logo is actually a JPEG image located in the Secondary Bootloader (sbl.bin) on partitions bml4 and bml5 (both are identical on my Tab).
The partion layout seems to be the same as for the Galaxy S series:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S#Modifications
(here you can also find the secret codes to check firmware etc.)
This command gives the partition info:
cat /proc/LinuStoreIII/bmlinfo
To dump any partition (e.g. SBL) to SD card:
dd if=/dev/block/bml4 of=/sdcard/bml4_dump bs=1
I attached the extracted boot logo.

Thanks xdadevel,
Followed your instructions above and it worked like a charm - my Tab boots up MUCH faster now.
I think to remove the Samsung boot logo you would have to edit something like init.rc in the bootimg, repackage it, and then copy it across.

Im trying to do this and get
Can not mount permission denied.
Failed for bootani.qmg, Read-only system file.
Any ideas?

xdadevel said:
I have already successfully removed the boot and shutdown animations (incl. sound) via "adb shell" commands:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
cd /system/media
rm bootani.qmg
rm samsungani.qmg
cd /system/media/video/shutdown
rm shutdown.qmg
cd /system/media/audio/ui
rm PowerOff.wav
cd /system/etc
rm PowerOn.snd
rm PowerOn.wav
mount -o remount,ro /dev/mtdblock3 /system
exit
Btw the tablet now boots much faster.
But the boot splash screen from Samsung is still there.
I've been reading about the methods for other Samsung devices, such as:
flashing a PDA tar with Odin
fastboot flash splash1
packing the logo png as an update.zip
None of these worked.
Instead I bricked my tablet and flashed "P1_20100909.pit" and "GT-P1000_P1000XXJK1.rar" (from samfirmware.com) to make it work again.
Click to expand...
Click to collapse
Very easy, thanks for the idea! I copied the files to my external SDcard just in case though... Maybe it would be nice for you to remind people of that. Cheers!

mklass said:
Im trying to do this and get
Can not mount permission denied.
Failed for bootani.qmg, Read-only system file.
Any ideas?
Click to expand...
Click to collapse
Have you rooted your phone?

smithdc said:
Have you rooted your phone?
Click to expand...
Click to collapse
Yes it is
Cheers

I hope this work on the US TMobile verison?
Sent from my Samsung Galaxy Tab

It does work on the U.S. TMobile tab, I tried it. to me it boots faster, but seems to shut down slower.

Thanks! I follow your instruction but instead of deleting, I just rename them with .old extension (maybe one day will need them.. who knows.. )
Now it boot much faster!!

Hi,
is there any way to replace the boot logo?

deafjam said:
It does work on the U.S. TMobile tab, I tried it. to me it boots faster, but seems to shut down slower.
Click to expand...
Click to collapse
Thanks in might give it a shot.
Sent from my Samsung Galaxy Tab

So again is there a way to replace the boot logo?
Sent from my GT-P1000 using XDA App

saintxseiya said:
So again is there a way to replace the boot logo?
Click to expand...
Click to collapse
As I pointed out in the first post the boot logo is located in the secondary bootloader partition which an ARM binary. The logo is not accessible via the file system. You would have to dump this binary, modify it and flash it again (e.g. with Odin).
The risk is that if something goes wrong (corrupted binary, signature check failed etc.) your device will not boot anymore. Not even into the flashing mode because it is also part of the secondary bootloader.
Such perma brick can maybe reverted with professional tools like JTAG if you are willing to disassemble your device.
http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/1
Noone so far seemed to replace the boot logo successfully.
One way could be to overwrite the original jpeg (see first post) with a black jpeg of exactly the same size (=20701 bytes). If there's no signature check and the jpeg format is valid this should work.

xdadevel said:
As I pointed out in the first post the boot logo is located in the secondary bootloader partition which an ARM binary. The logo is not accessible via the file system. You would have to dump this binary, modify it and flash it again (e.g. with Odin).
The risk is that if something goes wrong (corrupted binary, signature check failed etc.) your device will not boot anymore. Not even into the flashing mode because it is also part of the secondary bootloader.
Such perma brick can maybe reverted with professional tools like JTAG if you are willing to disassemble your device.
http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/1
Noone so far seemed to replace the boot logo successfully.
One way could be to overwrite the original jpeg (see first post) with a black jpeg of exactly the same size (=20701 bytes). If there's no signature check and the jpeg format is valid this should work.
Click to expand...
Click to collapse
Thanks for the answer!
I searched the net also about these mysterious qmg Files, i do not understand why is Samsung using that kind of files, it just makes us unhappy not to customize the tabs

thanks worked very well, however, I have the t-mobile tab and the t-mobile splash screen stills shows up on boot is there any way to get rid of that one or is it similar to the samsung one that your having trouble removing?

Just flash an unbranded firmware, they will be gone then
Sent from my GT-P1000 using XDA App

xdadevel said:
Noone so far seemed to replace the boot logo successfully.
One way could be to overwrite the original jpeg (see first post) with a black jpeg of exactly the same size (=20701 bytes). If there's no signature check and the jpeg format is valid this should work.
Click to expand...
Click to collapse
Actually it works to overwrite the boot logo in sbl.bin with a custom jpeg file. The size must be less or equal 20701 bytes. I filled the remaining bytes of the original jpeg data with 0x00 but be careful NOT to overwrite the bytecode after the jpeg!!
When booting the device I can see the custom logo for 2-3 seconds.
After that, however, the Samsung boot logo shows up again!
Must be located in another place as well.

This sounds great! Could you make a quick tut how to do that exactly please?
Is there a virtual testlab for the tab or an emulator?
Sent from my GT-P1000 using XDA App

saintxseiya said:
This sounds great! Could you make a quick tut how to do that exactly please?
Is there a virtual testlab for the tab or an emulator?
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
No, unfortunately not. Just flash the european firmware

kg4mxz said:
No, unfortunately not. Just flash the european firmware
Click to expand...
Click to collapse
I am already on jk5 i want to customize my tab.
Sent from my GT-P1000 using XDA App

[Q] My Bricked Nook Color - Restore after each reboot

I'm having some problem with my Nook Color that he only boots to ClockWork Mod in a bootable sd card.
Sometimes it boots to CyanogenMod, but when it boots keeps looping in boot screen (That one with a arrow running in circles).
Sometimes it starts the system, but nothing works. If I begin any app it crashes just after and force close, so it's useless.
I tried to install a ROM update in CWM, but I don't think it worked well, because takes less than 30s to install the package and says "Instalation Complete", but nothing changes at all.
And when I tried to install the ROM by the adb using
Code:
adb shell recovery --update_package=DATA:ROM.zip
Get this in response
Code:
4+0 records in
4+0 records out
4bytes (4B) copied, 0.013824 seconds, 289B/s
1088+0 records in
1088+0 records out
1088 bytes (1.1KB) copied, 0.020752 seconds, 51.2KB/s
When the system boots he allows me to unninstall apps and install apps for short time. But everytime he reboot it's all gone.
I tried erase my information from it, but it's useless. Everytime it resets back to the same lock screen and desktop full of my bugged apps.
I searched a lot before post here, cause there's a lot of people with similars problems, but some of them solved their problems with files that aren't online anymore and I can get them anymore.
It's been 4 months since it stoped working. If someone can help, I'll be glad.
I don't know what informations are needed to be helped, so ask for anything and I'll reply fast as I can.

Here are some pictures from the CloworkMod I'm using and tried to install this
HTML:
http://forum.xda-developers.com/showthread.php?t=1444943
ROM. The ROM works with lag in SD card, so I keep trying to install it on internal memory. But something seems to be wrong.
ICS Ok (At least it seems)
Gapps for ICS says that his Install is ok
Failed to format /data

[Q&A] [Z1][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A

Q&A for [Z1][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Z1][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

goldsmit409 said:
Hi i have a c6902 with unlocked bootloader i flashed stock kernel from here http://forum.xda-developers.com/showthread.php?p=57364878#post57364878 it says "3.4.0-perf-gaee6e5a [email protected] #1 Thu Oct 9 09:14:33 2014"
now i installed the recovery from this Z1-lockeddualrecovery2.7.154-BETA.installer.zip by running install.bat and chosing 1 option it says recovery installed and reboots . but it does not show, i tried with NDRutil as well but it does not bring the recovery
Can some one tell me what i am ding wrong?
thanks
Edit: maybe this can help, I am rooted
Code:
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is C6902
Firmware is 14.4.A.0.157
=============================================
Step2 : Sending the recovery files.
=============================================
9 KB/s (29 bytes in 0.003s)
5108 KB/s (15757 bytes in 0.003s)
246 KB/s (501 bytes in 0.001s)
2903 KB/s (11842 bytes in 0.003s)
5045 KB/s (56834 bytes in 0.011s)
1501 KB/s (3082 bytes in 0.002s)
187 KB/s (385 bytes in 0.002s)
6742 KB/s (657704 bytes in 0.095s)
6670 KB/s (2965179 bytes in 0.434s)
6230 KB/s (2598631 bytes in 0.407s)
5892 KB/s (1875928 bytes in 0.310s)
2118 KB/s (8759 bytes in 0.004s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Jul 31 13:39 /data/local/tmp/recover
y/busybox
Press any key to continue . . .
##########################################################
#
# Installing XZDR version 2.7.154 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
mount: permission denied (are you root?)
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': File exists
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': File exists
cp: can't create '/system/bin/recovery.philz.cpio.lzma': File exists
chmod: /system/bin/recovery.twrp.cpio.lzma: Read-only file system
chmod: /system/bin/recovery.cwm.cpio.lzma: Read-only file system
chmod: /system/bin/recovery.philz.cpio.lzma: Read-only file system
Copy chargemon script to system.
cp: can't create '/system/bin/chargemon': File exists
chmod: /system/bin/chargemon: Read-only file system
Copy dualrecovery.sh to system.
cp: can't create '/system/bin/dualrecovery.sh': File exists
chmod: /system/bin/dualrecovery.sh: Read-only file system
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': File exists
chmod: /system/bin/rickiller.sh: Read-only file system
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': File exists
chmod: /system/app/NDRUtils.apk: Read-only file system
Copy disableric to system.
cp: can't create '/system/xbin/disableric': File exists
chmod: /system/xbin/disableric: Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': File exists
cp: can't create '/system/.XZDualRecovery/busybox': File exists
chmod: /system/xbin/busybox: Read-only file system
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
WARNING: linker: app_process has text relocations. This is wasting memory and is
a security risk. Please fix.
WARNING: linker: app_process has text relocations. This is wasting memory and is
a security risk. Please fix.
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Press any key to continue . . .
Nevermind got it to work
Thanks
Click to expand...
Click to collapse
Can you please post how you did it?
I got same problem(It's my second day with Xperia so i don't know much about what locks Sony installed there).

choose the option 3,after this you smartphone reboot into recovery mode, later download the last version of super su or superuser in zip format. flashing through recovery mode and, that's all, rooted and recovery installed.

juliheavy said:
choose the option 3,after this you smartphone reboot into recovery mode, later download the last version of super su or superuser in zip format. flashing through recovery mode and, that's all, rooted and recovery installed.
Click to expand...
Click to collapse
Thanks for tip.
I found what was wrong there - new kernel(C690X_14.4.A.0.157) was locking it.
After downgrading to C690X_14.4.A.0.108 it all worked.

Death_Master said:
Can you please post how you did it?
I got same problem(It's my second day with Xperia so i don't know much about what locks Sony installed there).
Click to expand...
Click to collapse
Death_Master said:
Thanks for tip.
I found what was wrong there - new kernel(C690X_14.4.A.0.157) was locking it.
After downgrading to C690X_14.4.A.0.108 it all worked.
Click to expand...
Click to collapse
ah obviously! ? well thinking

how to make CWM the default recovery specially when pressing the vol + when booting, i made a backup in internal sd using cwm but cannot be restored by philtouch, recovery is not yet stable

i have a recovery problem
when i root the phone.. intall recovery.. ( also follow the steps) and in recovery i cant make nothing with system, when i intall rom its freezee and i see only the sony logo so help me pls, once work that but i dont know why what do i wrong ?

when tried to install the recovery on my unrooted phone its stock on libvdm opened <loljavasucks> what can i do ??

Confirm working on C6902 Stock Kernel 14.4.A.0.157 (locked bootloader)
:good: You're awesome! Good job!
. . . it was stuck at Speeding up backups. , then I decided to disconnect and restart my phone, and finally I could get into the Recovery. No problem at all. Now I'm on a custom ROM.

/system/xbin/su /system/bin/sh not found
I am trying to install Z1-lockeddualrecovery2.8.2-RELEASE.installer, but it says /system/xbin/su /system/bin/sh not found.
I use superSu and I cant grant the program superSu access, it doesn't pop up on my phone.

ihacker rom known issue
hi there, im having issue on ihacker rom i dnt no what to do how to fix "unable to read xzdr.prop it was known issue on his rom..what i shall do.red light is signaling when im going to boot to recovery.how to fix my recovery
C6903 .157 Z1

Advanced Stock Kernel
Hello there gurus.
Being on a stock fully rooted kernel (14.4.A.0.157) flashed with FlashTool (unlocked bootloader), and thus with stock recovery (ie no custom recovery installed). I went to NUT''s most excellent site and made a “XZDualRecovery 2.8.2 Advanced Stock Kernel” by uploading the kernel.sin file which I got from the FTF file created with FlashTool. This creates a flashable.zip file meant to be installed from inside a custom recovery solution.
My question is then, if I extract the boot.img file from this flashable.zip, could I then flash this image using fastboot ( fastboot flash boot boot.img ) ?
Could I then use that solution to install a CM12 nightly build, which I assume would promptly overwrite what I just did instead of reflashing a CM12 boot.img and go from there?
Would I gain anything at all from doing this instead of just using the Z1-lockeddualrecovery2.8.2-RELEASE.installer.zip package?
I'm so confused now.

Can somebody help me ?
I start the install.bat and press 1 ( i have SuperSU ) and it says " Waiting for Device , connect USB cable now " but when i connect my phone ( C6903 ) i does nothing. I tried rebooting in flash mode and in fastboot mode but my pc does nothing. How am i supposed to flash the Kernel if it isn't working ? How do i make it work ?

Install.bat does nothing for a long time
Sony Xpeira Z1 C6903
BuildNr. 14.1.G.1.534
SU: SuperSU
rooted
So i downloaded flashable.zip and installable.zip and started install.bat and it says waiting for device please connect.
So i connect my phone and it does nothing.
I tried rebooting my phone in fastboot mode and also in flash mode.
It did nothing.
What am i supposed to do ?
Please help me ... i don't want to stay with Android 4.2

Problem with links
I try to download a file, but the page sent me to http://nut.xperia-files.com/filenotfound.php

link die ?

Is there a method for lollipop yet? I flashed a prerooted rom but didn't flash the recovery and just rebooted. I tried thw 2.8.9 installer but nothing happened on my phone (choosing method number 1)
Edit: Nevermind, I forgot that I reinstalled this laptop so ADB Drivers were missing. It still stops stops while transfering the files. It stops after the 6th file transfer.

ok i got a probably stupid question . .
i have z1 and its rooted with no reco0very installed..
if i install recovery and make a full backup and do a factory reset of the phone and install lolipop official , will the backup work if i go back and do restore of kk backup?

Installing the kernel in Lollipop
I had 4.4.4 rooted whitout any recovery, but then I installed lollipop via ota in my z1 c6902 locked bootloader. Can I install the dualrecovery in my phone without any problem?.

Im on 2.8.10 how to install xposed framework?
Do I need to edit/modify xzdr prop file? Or can I direct install?
Z1 5.0.2.
242 fw.

[Tutorial] Edit your Note 4's Boot Splash Screen!

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