Hi Y6 users. This is for Y6 only.
This tutorial will show you how to change the boot splash logo of Huawei Y6.
Risk of bricking is unknown so assume high, this will modify your oeminfo partition.
Tested on:
SCL-L01
SCL-L02
SCC-U21
Download the zip i provided. Includes 15 images.
Here is how to change your splash logo via terminal. (You may install Termux or other app if you don't have terminal)
Code:
su
mount -o rw,remount /system
mkdir /sdcard/oem
(Now paste the zip i provided into /sdcard oem)
[Sdcard is actually internal storage if you didn't know]
cd sdcard/oem
unzip oemlogo.zip
cp ./oemlogo /system/bin/
chmod 755 /system/bin/oemlogo
oemlogo
oemlogo -d
oemlogo -e
oemlogo -c 1.bmp
oemlogo -e
oemlogo -p
reboot
(That's it! 1.bmp stands for the first splash logo and i have included 10 splash images, if you want to use another image then type the number of that image .bmp)
How to change it via adb:
Connect your phone to the pc, and in Minimal Adb&Fastboot console, or whatever you are using type:
Code:
adb root
adb remount
adb shell mkdir /sdcard/oem
adb push oemlogo.zip /sdcard/oem/ (For this to work you need to have Oemlogo.zip in the folder you installed Minimal Adb&Fastboot)
adb shell
cd sdcard/oem
unzip oemlogo.zip
cp ./oemlogo /system/bin/
chmod 755 /system/bin/oemlogo
oemlogo
oemlogo -d
oemlogo -e
oemlogo -c 1.bmp
oemlogo -e
oemlogo -p
reboot
(That's it! 1.bmp stands for the first splash logo and i have included 10 splash images, if you want to use another image then type the number of that image .bmp)
All credits to @DestructoSphere who made the script and made this possible
Also thanks to @EzeMaxtor for the Huawei splash images.
DOWNLOAD: https://mega.nz/#!mZwghRoA!2l-4QkDwrmvCoqrNITDreIXnKUgbcW-YliYPJLJN29s (LATEST v4)
Older releases:
Release 3[v3]: https://mega.nz/#!HZBnjbSb!hw0Xw1LaEqT8o9w00u9jx2bpYQHiTQAYVKLsv0hpoMQ
Release 2[v2]: https://mega.nz/#!LMp0GZqB!0l1k7rtdojNoApMJMqvGQc01QGHQibNBroHQY3xOxW0
First release [v1]( 8 images are broken): https://mega.nz/#!vNhmXaAL!xfLMGUIeH-Sr2QFGsGMjCJ3_1WQqYvc5EwrjojlVHfQ
Images included:
https://imgur.com/a/8Jmw7tw - 1.bmp
https://imgur.com/a/aO2ZGrq - 2.bmp
https://imgur.com/a/RrHUA1q - 3.bmp
https://imgur.com/a/vmzE9C7 - 4.bmp
https://imgur.com/a/mPELj2h - 5.bmp
https://imgur.com/a/fD1bQGB - 6.bmp
https://imgur.com/a/9bqJkDD - 7.bmp
https://imgur.com/a/hVQ3hxm - 8.bmp
https://imgur.com/a/zlIXNCe - 9.bmp
https://imgur.com/a/19TYaaT - 10.bmp
https://imgur.com/a/bhs1Cxe - 11.bmp
https://imgur.com/a/nvy3Jon - 12.bmp
https://imgur.com/a/MXlW17c - 13.bmp
https://imgur.com/a/GhsD8se - 14.bmp
https://imgur.com/a/j8KBiaA - 15.bmp
https://imgur.com/a/RANJwWH - 16.bmp
https://imgur.com/a/6c1YdIt - 17.bmp
https://imgur.com/a/XhWUnm6 - 18.bmp
https://imgur.com/a/LIb7un8 - 19.bmp
https://imgur.com/a/odfET0v - 20.bmp
If you want other images than these you may PM me on Xda/Telegram (@Thespartann) so i can convert the image so it works as an splash logo.
Also an tutorial is coming soon so you can convert it yourself.
!These images are not made by me, i only made them work as the splash logo!
If i helped press the thanks button
works like charm ! . for anyone who faced any issues with running adb Root . use adbd Insecure
great, finally after 3 years i delete tim static logo from my Y6
works under termux really fine.
my favourite image was n3.thanks a lot.
Thank god! Finally I also removed the terrible oem splash screen, I have ATU-L11 version of Y6.
I also used 3.bmp, through adb.
Multumesc mult!
EDIT: too fast... after a couple of restarts the old logo came back What does Huawei have that's so hard to modify?!
:good:
Related
Hi guys
I've imported the SH-06D from Japan and the phone is running great, however I'd like to remove some system apps etc to help speed up the phone (it's still on 2.3.5) and obviously tweak it as well.
I know there is an existing thread on the SH-01D (predecessor to the SH-06D) but I'm wondering if anyone has successfully rooted the SH-06D and if so, is there an (easy) process to do this?
Another reason I want to root, is to install the UI from the upcoming Evangelion Nerv edition of the SH-06D that is due to be released in a few days.
ICS for the SH-06D is just around the corner (due to be released in July) but I'd realy appreciate any help, assistance or tips in rooting the phone as it is now.
Cheers! :fingers-crossed:
Anyone?
:-(
here is a link to root the sh-06d :
http://itsuki.ddo.jp/gadget/index.php?SH-06D
THANK YOU!
Have you tried this method and does it work? Can you assist me in following those directions?
Cheers
interfreak said:
THANK YOU!
Have you tried this method and does it work? Can you assist me in following those directions?
Cheers
Click to expand...
Click to collapse
i haven't tried since i don't have this phone.
i can try to help you if you want.
testnumero said:
i haven't tried since i don't have this phone.
i can try to help you if you want.
Click to expand...
Click to collapse
Thanks mate!
I'm fumbling through the process now - it's a little hard when you are using google translate lol!
OK, I've run through all the steps but..
When I get to the end of the process:
C:\Users\interfreak\Desktop
$ su
su
su: permission denied
:-(
interfreak said:
OK, I've run through all the steps but..
When I get to the end of the process:
C:\Users\interfreak\Desktop
$ su
su
su: permission denied
:-(
Click to expand...
Click to collapse
i don't know what is the problem, try to do steps again.
Tried, same result. :-(
interfreak said:
Tried, same result. :-(
Click to expand...
Click to collapse
i'll ask to translate it
Thanks mate!!! :highfive:
I want to know untill now has SH-06D been rooted?
I wish someone could dump ROM or launcher from SH-06 NERV version:fingers-crossed:
I'm working on the translation for root on Sharp Aquos SH-06D.
Please give me one or two more days!
That is highly impossible, having full root in J Phone are hard enough. Unlocking the bootloader is a wet dream for almost everyone who likes J phone
lightout said:
I want to know untill now has SH-06D been rooted?
I wish someone could dump ROM or launcher from SH-06 NERV version:fingers-crossed:
Click to expand...
Click to collapse
I'm trying to hard reset my SH-06D, but I can't do it via settings-privacy. I can select to wipe, but nothing happens.
Any suggestions?
I got the Nerv edition
Hey man, how did the rooting go? I ordered the Nerv edition of this phone, and I want to root it (mainly to pair my sixaxis controller for psx emulation) but wanted to consult with you first as a precaution.
Here is the a rough translation of the root guide found here:
http://itsuki.ddo.jp/gadget/index.php?SH-06D
Big thanks to testnumero for the help!
Please don't ask me directly for help. I don't own this phone.
A quick look at root
• With root you can freeze preinstalled bloatware and backup application settings and game save data.
• 3D content from /system can be played on other devices and 3DTVs.
Unresponsive apps can be frozen which will help the device run smoother and have a longer battery life.
Applications which are frozen disappear from your drawer making the device look cleaner and keeping your mind at ease.
• The process is similar to the one used for SH-01D.
• If an update patch is released or the Android 4.0 summer update is released then this guide will no longer be of help.
(Make sure your device is the following: Android Ver. 2.3.5 Build No. 01.00.03)
• If your device becomes a paperweight I won’t be held responsible.
• Follow this guide at your own risk.
↑
Preparations – Before you begin
• Install Android SDK and SHARP ADB USB drivers and make to use ADB.
• 「Settings」→「Applications」→「Development」→「USB Debugging」 checked.
• SH-06D and micro USB cable to connect to your PC
↑
Required Files
• Download "shdisphook" from the following link and extract.
http://goo.gl/Bs6Iq
• Download shsdgetroot-omap4.zip from the following link and extract.
http://www1.axfc.net/uploader/File/so/78144
• Download shbootgetroot-su.lzh from the following link and extract.
http://www.mediafire.com/?6i0n32jlwbxe8cp
• Keep all extracted files in the same folder.
↑
Creating files
• Create a file named "shdisphook.bat" in the folder with the extracted files.
Copy and paste the following and save.
adb push onload.sh /data/local/
adb push libsdservice_jni.so /data/local/
adb push shdisphook /data/local/
adb shell chmod 755 /data/local/onload.sh
adb shell chmod 755 /data/local/shdisphook
adb reboot
adb wait-for-device shell /data/local/shdisphook
pause
• Create a file named "oncmd.sh" and put the following in the description.
(Save the line break as LF)
chmod 777 /cache
chmod 666 /cache/recovery
• Replace the contents of the file "installfile.cmd" with the following and save.
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/mount -o rw,remount -t rootfs rootfs /"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 777 /sbin"
adb push su /sbin
adb push busybox /sbin
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chown 0.0 /sbin/su"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chown 0.0 /sbin/busybox"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 6755 /sbin/su"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 755 /sbin/busybox"
adb shell /data/local/shsdgetroot-omap4 -c "/sbin/busybox --install -s /sbin"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 755 /sbin"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/mount -o ro,remount -t rootfs rootfs /"
adb push Superuser.apk /data/local/
adb shell /system/bin/pm install -t -f -r /data/local/Superuser.apk
adb shell /system/bin/rm /data/local/Superuser.apk
exit /b
↑
Step 1
• Open command prompt to the folder with the extracted files and navigate to "shdisphook".
Execute "shdisphook.bat". (You can also just double click on the .bat file)
• The device will reboot so just wait for the [Press any key to continue] message to appear.
If more than a few minutes have passed and nothing has appeared then, force close and execute "shdisphook.bat" again.
(When you fail your PC will reboot or your SH-06D WiFi will start. There is a high rate of success when you immediately unlock the lock screen for your device when it goes to sleep.)
↑
Step 2
• Open command prompt and send oncmd.sh to SH-06D to change permissions
adb push oncmd.sh /data/local/oncmd.sh
adb shell chmod 755 /data/local/oncmd.sh
• 「Settings」→「microSD and device storage」→「Unmount microSD」 This will execute the file "oncmd.sh" , which was sent to the device earlier.
(Cancel the message for 「Unmount microSD」)
• Enter the following commands.
adb shell mv /cache/recovery /cache/recovery_
adb shell ln -s /dev/shsd /cache/recovery
• Execute the following adb shell ls -l /cache and if you see the following message you have succeed.
drwxrwx--- root root 2011-11-11 03:39 lost+found
drw-rw-rw- system cache 2012-01-24 10:48 recovery_
lrwxrwxrwx shell shell 2012-03-02 13:24 recovery -> /dev/shsd
• Next execute adb shell ls -l /dev/shsd you should get the following message if you were successful.
crw-rw-rw- system cache 231, 0 2012-04-23 02:01 shsd
↑
Step 3
• Execute adb push shsdgetroot-omap4 /data/local
• Execute adb shell /system/bin/chmod 755 /data/local/shsdgetroot-omap4
• Execute adb shell /data/local/shsdgetroot-omap4 -v -m -u
• The “# “mark will appear there will be no response. Close command prompt for now.
• Execute installfile.cmd
• Check if you have root with the following adb shell→su
↑
After you reboot
• After you reboot you will lose root rights so execute shdisphook.bat→Cancel Unmount microSD →execute installfile.cmd and you should have root again.
The reason why you cannot do a clean wipe or nothing happen is because the recovery section has been move out into another location, causing it to not loading the recovery correctly.
Check with SH-01d part, I have asked similar question there and I revert the recovery in order to wipe the phone..
You need to rearrange the following section like on the sh-01d when you hit this part:
(Following is Original command that you relocated the recovery for root)
adb shell mv /cache/recovery /cache/recovery_
adb shell ln -s /dev/shsd /cache/recovery
And replace with the revert command found on sh-01d thread. You will need to redo all the steps from step 1 to step 2 and STOP AFTER YOU REVERT the RECOVERY.
You should be able to do a full wipe with no issue then. DO NOT POWER DOWN or RESET!!! You will have to REDO it again as it REQUIRES SHDSIHOOK to input shell command.
Hope it helps
waiting！！！！！！！！！！
Hi,
I want to let Android OS to boot automatically when the charger connected (for HTC Magic) without pressing power button
I found this guide
---------------------------------------------------------------------
Complete boot when charging
If your phone only gets one of those ugly battery symbols when a charger is connected to a powered off phone this is because the init process is interrupted by /system/bin/chargemon. That file is a binary ARM program, I replaced it with a simple script containing only a single line:
echo skipping chargemon
The file was created and installed with the following steps:
Code:
echo "echo skipping chargemon" > chargemon.script
adb pull /system/bin/chargemon chargemon.backup
adb push chargemon.script /sqlite_stmt_journals
adb shell
$ cd /sqlite_stmt_journals
$ su
# mount -o remount,rw /dev/block/mtdblock0 /system
# cat chargemon.script > /system/bin/chargemon
# chmod 755 /system/bin/chargemon
# reboot -p
When the command su is given above, it might have to be acknowledged in a dialog on the phone screen.
The final command reboot -p shuts down the phone. As the USB cable is still connected it will power on again, and if everything has gone fine the phone will complete its boot process without halting with any battery symbol.
-------------------------------------------------------------------
But I can't find "chargemon" in System/bin
Please Help
Thanks for every one
chargemon file is only present in sony xperia phones. So you won't find it in other models.
gavohan said:
Hi,
I want to let Android OS to boot automatically when the charger connected (for HTC Magic) without pressing power button
I found this guide
---------------------------------------------------------------------
Complete boot when charging
If your phone only gets one of those ugly battery symbols when a charger is connected to a powered off phone this is because the init process is interrupted by /system/bin/chargemon. That file is a binary ARM program, I replaced it with a simple script containing only a single line:
echo skipping chargemon
The file was created and installed with the following steps:
Code:
echo "echo skipping chargemon" > chargemon.script
adb pull /system/bin/chargemon chargemon.backup
adb push chargemon.script /sqlite_stmt_journals
adb shell
$ cd /sqlite_stmt_journals
$ su
# mount -o remount,rw /dev/block/mtdblock0 /system
# cat chargemon.script > /system/bin/chargemon
# chmod 755 /system/bin/chargemon
# reboot -p
When the command su is given above, it might have to be acknowledged in a dialog on the phone screen.
The final command reboot -p shuts down the phone. As the USB cable is still connected it will power on again, and if everything has gone fine the phone will complete its boot process without halting with any battery symbol.
-------------------------------------------------------------------
But I can't find "chargemon" in System/bin
Please Help
Thanks for every one
Click to expand...
Click to collapse
ajparag said:
chargemon file is only present in sony xperia phones. So you won't find it in other models.
Click to expand...
Click to collapse
Check out this video - http://www.youtube.com/watch?v=ViZ2uoc90zQ Here you will find a feature that starts the OS at a pre-defined time. We can replace that command with start-on-charger-connect.
Xperia Mini Pro does not start
I replaced the chargemon file and put my version with only one line(with 755 permissions):
echo startting...
but now, mi xperia mini does not start only shows the screen "sony ericcson"
any way to recover my phone, please ??
hi,
have anyone found a generic way to autoboot android phone?
Hi guys, has anyone found a generic way to auto boot android devices on charge?
I've been reading up on this and found various suggestions, all based on files within /system/bin such as ipod, playlpm , lpm or chargemon. My device has none of these files (yes its routed and yes my explorer is showing hidden files)
I've searched through all the files in /bin and cannot find any mention of "ChargingAnimation" in any of the files there..
I have found the charge animation image files which show when the device is being charged when powered off "/res/images/charger", but I can't find the code that triggers this image. If I could, I would add the line to reboot there.
Any help greatly appreciated.
I have a Tesco Hudl 1 with 4.2.2
Hello
There's a way for making a backup with RAW extension that can be flashed with fastboot in asus fonepad (i don't know about others)
See this: http://forum.xda-developers.com/showthread.php?t=1818321
Back up of the whole memory block (via adb)
Connect the phone in ADB mode and unlock the screen.
Open one Cygwin Terminal and enter (replace mmcblk0 if needed):
Code:
adb forward tcp:5555 tcp:5555
adb shell
su
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0
You will see the cursor blinking at the left. Now the phone is waiting to send the block over the network.
Open another Cygwin terminal and type:
Code:
adb forward tcp:5555 tcp:5555
cd /path/to/store/the/backup
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw
You will see how the image size is growing until it finishes. Now you have the whole phone backed up in raw format. You can see the contents of the GPT partition with gptfdisk tool, available for windows, linux and such. See official website and sourceforge to get it. You can do it the same from ClockWorkMod Recovery but you have to mount first the /system partition since the busybox included with clockworkmod does not come with netcat and you have to use the one from the system partition.
With further linux tools you could edit or extract single partitions from the whole block.
Click to expand...
Click to collapse
But it's for rooted devices only. how can i make a backup with busybox non-root?
Hey Guys,
i got a broken Tolino Vision 3 HD from a friend to fix the issues with the android. It´s a popular ebook reader in Germany.
At the moment I got the device it stuck in language selection and the partition for the ebooks wasn´t shown after USB connection.
So I downloaded the new software version from the vendor "mytolino" (I am not allowed to post urls). I tried to update via
fastboot update
Click to expand...
Click to collapse
but i got this error:
archive does not contain 'android-info.txt'
error: update package '..\update.zip' has no android-info.txt
Click to expand...
Click to collapse
. So I unpack the .zip and try to flash the images manualy. This didn´t work. After this is tried to copy the update.zip to /sdcard via adb push but this didn´t work, too.
Question:
Is there any way to flash the device with the given update.zip?
Regards and all good wishes from sunny Germany
Did you tried to do factory reset? Are you able to boot into recovery using key-combination?
The more heavy way I used yesterday to reanimate my Tolino page after trying to install OpenGapps on them (no, did not work oO).
I am not allowed to post URL's because of "Noob-Protection" in Forum. There is a "Tolino Vision 2 rooten" howto in web. Some parts of them you can use to solve your problem.
1. Create own ADB-Enabled custom recovery (Did worked for me only with 10.0.1 update package). Should be done on Linux
Code:
$ mkdir custom_recovery
$ cd custom_recovery
$ unzip ../update.zip recovery.img
$ mv recovery.img recovery.img.orig
$ abootimg -x recovery.img.orig
$ mv initrd.img initrd.img.orig
$ mkdir initrd
$ cd initrd
$ zcat ../initrd.img.orig | cpio -vid
Adjust default.prop with values "ro.secure=0", "ro.debuggable=1" und "persist.sys.usb.config=mass_storage,adb".
Code:
$ find . | cpio --create --format='newc' | gzip > ../initrd_adb_enabled.img
$ cd ..
$ abootimg --create recovery_adb_enabled.img -f bootimg.cfg -k zImage -r initrd_adb_enabled.img
You get error : "updated is too big for the Boot Image" with new size value. Calculate this value to hexadecimal and adjust the "bootsize" in "bootimg.cfg" to hex-value
Do abootimg again.
2. Use the custom recovery to trigger update manually
Code:
$ fastboot boot ../custom_recovery/recovery_adb_enabled.img
$ adb shell
# mount -t vfat /dev/block/mmcblk0p4 /sdcard/
# exit
$ adb push update.zip /sdcard/update.zip
$adb shell
# cd /sdcard
# busybox unzip update.zip META-INF/com/google/android/update-binary -d /tmp
# busybox chmod u+x /tmp/META-INF/com/google/android/update-binary
# /tmp/META-INF/com/google/android/update-binary 3 1 /sdcard/update.zip # Update installieren
# sync && sleep 5 && sync # sicherheitshalber, wenn man dran glaubt
# reboot
Source: google for "e-reader-forum Toolino vision 2 rooten"
Hey all,
I am learning how Android works and am trying to figure out how I can update the Android filesystem by extracting a ramdisk from normal boot.img, adding some files, then flashing it back. So far, I have been unsuccessful in doing this and am hoping to figure out why. Here's the steps below I have taken:
Using a Google Pixel 4a, Android 11, kernel v 4.14 (i.e. not GKI)
High level:
Extract ramdisk.cpio from boot.img using magiskboot via adb on device, modify extract contents, sent back up to magiskboot, repackaged, then flashed via fastboot.
Detailed steps:
Grab ramdisk.cpio
Code:
$ # obtain the ramdisk.cpio from magiskboot
$ adb -d shell "cd ${BOOT_IMG_PATH}; ./magiskboot unpack boot.img"
$ adb -d pull /${BOOT_IMG_PATH}/ramdisk.cpio /tmp/
$ # attempt to modify the filesystem
$ mkdir /tmp/rd && cd rd
$ cpio -i < /tmp/ramdisk.cpio
$ touch yolo
$ echo "why doest this work" > system/wtf.txt
$ echo "why doest this work" > sys/wtf.txt
$ echo "why doest this work" > vendor/wtf.txt
#patch this directory back up and send to magiskboot
$ find . | cpio -oH new > /tmp/new.ramdisk.cpio
$ adb -d push /tmp/new.ramdisk.cpio ${BOOT_IMG_PATH}/ramdisk.cpio
$ adb -d shell "cd ${BOOT_IMG_PATH}; ./magiskboot repack boot.img
$ adb -d pull /${BOOT_IMG_PATH}/new-boot.img /tmp/
# apply this modifyied boot.img
$ adb reboot bootloader
fastboot flash boot /tmp/new-boot.img
fastboot reboot
After doing this, I'll adb back in to verify:
Code:
adb -d shell "find / -name "wtf.txt" 2>/dev/null
# silence.... always silence... no file change
* I am aware that Wu modifies the extracted dtb file from boot.img with a "magiskboot dtb dtb patch" command but that doesn't seem to apply to my particular boot.img as the fstab doesn't seem to be around
* I am aware that vbmeta and codesigning, I have disabled vbmeta via fastboot
* I am aware that there's A/B slots for flashing. I have tried flashing both slots to make sure the updated ramdisk is seen
* I am aware of magiskboot's kernel patch from skip_initramfs -> want_initramfs. I could use some clarification on this if it pertains to my problem
* My Android device uses "mount method C" from Wu's great writeup https://github.com/topjohnwu/Magisk/blob/master/docs/boot.md. That is, it's init's job to mount everything on my device. I guess I feel confused as to why init wouldn't mount the additional files that I've added to the ramdisk
Extremely grateful for help or guidance on what I've overlooked. Thanks y'all
You should probably examine your modified boot file to see if the new stuff is in there.
I don't use your tools or even deal with cpio as a file type.
Code:
C:\>echo Hello > sbin\bogus
C:\>imgutil /i boot.img sbin/bogus
C:\>imgutil /l boot.img
...
sbin/bogus
...