Database Develop

"[TUT]Rooting,Custom boot.img & recovery.img for newbies

Firstly i did not do this guide. it took it from this forum and just compile so that newbie like me can easily root their tattoo.....
ROOTING TATTOO
Download the ZIP file attached to this post. Extract the files to a safe location - perhaps C:\Tattoo ?
Now, you'll need adb for windows. You can get it from COBURN website's server here: ADB for windows.
Make sure your device is in USB Debug Mode (Settings > Applications > Development).
Extract all the files in the adb4win zip file to your C:\Tattoo folder.
Now, go to Command Prompt. In XP, it's under System Tools in Accessories. In Vista/7, it'll be under accessories.
Do the following at the command line:
C:\Users\Coburn> cd C:\Tattoo
Then you will get this C:\Tattoo
Next type in this:
C:\Tattoo> adb-windows shell "mkdir /data/local/bin" (with the quotes!).
If you get a error (like mkdir failed, file/folder exists), this is fine!
just means that the folder already exists in your phone
Now, run this command:
C:\Tattoo> adb-windows push m7 /data/local/bin/m7
this will just take a few seconds
Run this:
C:\Tattoo> adb-windows shell "cd /data/local/bin && chmod 755 ./m7" (with the quotes!)
This allows you to run the sucker. Looks like something nothing happen but it did something.
C:\Tattoo> adb-windows shell
This will dump you at a "$" shell. do the following:
C:\Tattoo> adb-windows shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
...lotsa text will flow down your screen. This is normal.
Soon, you'll be greeted with this:
#
This is the root prompt! If you get stuff like this:
# usage: reboot ...
usage: reboot ....
usage: reboot ...
Just keep your cool, press enter and the # will pop again. This is due the exploit spawning reboots to gain the shell.
Next type in this:
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
Check if u have root, type:
id
you will get
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
The uid=0(root) is important, so call your phone is root.
REMOUNT PARTITION (SU)
Now you need to install su. Exit your root shell (via CTRL+C) and download this su.zip and extract it to C:\Tattoo.
DO NOT EXIT THE COMMAND PROMPT WINDOW.
in your command prompt window, do this:
C:\Tattoo> adb-windows push su /data/local/bin/su
Then break out a shell...
C:\Tattoo> adb-windows shell
at the $ prompt, enter:
$ chmod 755 /data/local/bin/su
$ cd /data/local/bin/
$ while 'true' ; do ./m7 ; done
It will change from $ to #
Type in this:
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
Next type in this:
# chown root.root /data/local/bin/su
# chmod 4755 /data/local/bin/su
# mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system
After that, you can exit out of the root shell, and try a normal shell and this:
$ /data/local/bin/su
...which should make you get a nice # prompt.
Custom Boot.img:
Boot img v2:http://forum.xda-developers.com/show...0&postcount=38
Tattoo-hack.ko:http://forum.xda-developers.com/atta...2&d=1266670581
Download this flash_image:http://forum.xda-developers.com/attachment.php?attachmentid=287463&d=1267386499
adb push flash_image ./data/local/bin/flash_image
adb push Mainfram3.boot.02.img /sdcard/Mainfram3.boot.02.img
adb push tattoo-hack.ko ./data/local/bin/tattoo-hack.ko
c:\tattoo>adb shell
$ su
su
su: access granted, courtesy of www.magicandroidapps.com
# insmod /data/local/bin/tattoo-hack.ko
#mount -o rw,remount /dev/block/mtdblock5 /data
#mount -o rw,remount /dev/block/mtdblock3 /system
#chmod 755 /data/local/bin/flash_image
#/data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
Cutom Recovery Img:
After custom boot.img
adb push TCRI.alpha.img /sdcard/TCRI.alpha.img
c:\tattoo>adb shell
#/data/local/bin/flash_image recovery /sdcard/TCRI.alpha.img
once again i did not make the guide...i only compile it from different thread and put them as 1....tats all....thanks to all the devs that came up with the guide.....

hi!
will be possible flash official ROM made HTC after rooting proces?
I'm totaly new to this android applications

correct me if im wrong...you can always flash official rom frm htc for that paticular phone model....whether root or not....

the flash image no longer exists...

@Bikers
Download here:http://forum.xda-developers.com/attachment.php?attachmentid=287463&d=1267386499
@shazarul
Correct the link in the post.

c:\tattoo>adb shell
$ su
su
su: access granted, courtesy of www.magicandroidapps.com
i get permision denied! I know there is somewhere else a thread like this but i jus t can't find it...

try it with root 1 click by maverixx

have change the flash_image link..... biker i think u have to root it again???/ i think should b the easy way out....

just flashed custom boot img using this tutorial, thanks !

Thanks a lot, but I have a problem.
When I get to:
Code:
adb push Mainfram3.boot.02.img /sdcard/Mainfram3.boot.02.img
I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had the same problem with http://forum.xda-developers.com/showthread.php?t=644279&page=6 1 click root script when pushing to /sdcard...

have you tried to put it directly in your sd card? Did you putted your phone in MSSync at the usb options?

try to unmount sdcard from the phone, with the command in the notification bar of the tattoo

i am having this error while flashing custom recovery image ...
# /data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
/data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
error opening /sdcard/Mainfram3.boot.02.img: No such file or directory
#
Click to expand...
Click to collapse
where am i getting it wrong ??? till that i have no issues in following tutorial...
please help me...

chtamina said:
try to unmount sdcard from the phone, with the command in the notification bar of the tattoo
Click to expand...
Click to collapse
this suggestion solved my problem.... thanks chtamina..... you made my day...

Simple blue Theme for sense 3.0

This is for htc raider only.
I have changed a few apk's to make most of the green blue.
I have also changed some of the icons, plus the bootup and bootdown animations.
I have not been able to zip my apk's but have the apk's and you can use adb to push them to your htc raider.
If you are interested let me know and I will share them.
I'll add some screenies asap.
Theme is based on mma.
Please have a backup before you try this, I'm not responsible if you break your phone!!!!
Here's the zip file.
Simple Blue
The zip file is not flashable!!!! only in zip for downloading, you need to extract and use adb to push to the phone.
Here's a link to my wallpapers.
wallpapers
Here's the adb code
Code:
adb remount
adb push Rosie.apk /sdcard/Rosie.apk
adb push HtcDialer.apk /sdcard/HtcDialer.apk
adb push HTC_IME.apk /sdcard/HTC_IME.apk
adb push SystemUI.apk /sdcard/SystemUI.apk
adb push framework-res.apk /sdcard/framework-res.apk
adb push com.htc.resources.apk /sdcard/com.htc.resources.apk
adb push Settings.apk /sdcard/Settings.apk
adb push Browser.apk /sdcard/Browser.apk
adb push bootanimation.zip /sdcard/bootanimation.zip
adb push downanimation.zip /sdcard/downanimation.zip
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p29 /system
busybox cp -R /sdcard/Rosie.apk /system/app/
busybox cp -R /sdcard/HtcDialer.apk /system/app/
busybox cp -R /sdcard/HTC_IME.apk /system/app/
busybox cp -R /sdcard/SystemUI.apk /system/app/
busybox cp -R /sdcard/framework-res.apk /system/framework/
busybox cp -R /sdcard/com.htc.resources.apk /system/framework/
busybox cp -R /sdcard/Browser.apk /system/app/
busybox cp -R /sdcard/Settings.apk /system/app/
busybox cp -R /sdcard/downanimation.zip /system/customize/resource/
sync
mount -o remount,ro /dev/block/mmcblk0p29 /system
reboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

font in your theme
I like the font you are using, What is it?
Cheers
BR

It's the Sony Ericsson font.
Brau0303 said:
I like the font you are using, What is it?
Cheers
BR
Click to expand...
Click to collapse

hackit said:
This is for htc raider only.
I have changed a few apk's to make most of the green blue.
I have also changed some of the icons, plus the bootup and bootdown animations.
I have not been able to zip my apk's but have the apk's and you can use adb to push them to your htc raider.
If you are interested let me know and I will share them.
I'll add some screenies asap.
Theme is based on mma.
Please have a backup before you try this, I'm not responsible if you break your phone!!!!
Here's the zip file.
Simple Blue
The zip file is not flashable!!!! only in zip for downloading, you need to extract and use adb to push to the phone.
Here's a link to my wallpapers.
wallpapers
Here's the adb code
Code:
adb remount
adb push Rosie.apk /sdcard/Rosie.apk
adb push HtcDialer.apk /sdcard/HtcDialer.apk
adb push HTC_IME.apk /sdcard/HTC_IME.apk
adb push SystemUI.apk /sdcard/SystemUI.apk
adb push framework-res.apk /sdcard/framework-res.apk
adb push com.htc.resources.apk /sdcard/com.htc.resources.apk
adb push Settings.apk /sdcard/Settings.apk
adb push Browser.apk /sdcard/Browser.apk
adb push bootanimation.zip /sdcard/bootanimation.zip
adb push downanimation.zip /sdcard/downanimation.zip
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p29 /system
busybox cp -R /sdcard/Rosie.apk /system/app/
busybox cp -R /sdcard/HtcDialer.apk /system/app/
busybox cp -R /sdcard/HTC_IME.apk /system/app/
busybox cp -R /sdcard/SystemUI.apk /system/app/
busybox cp -R /sdcard/framework-res.apk /system/framework/
busybox cp -R /sdcard/com.htc.resources.apk /system/framework/
busybox cp -R /sdcard/Browser.apk /system/app/
busybox cp -R /sdcard/Settings.apk /system/app/
busybox cp -R /sdcard/downanimation.zip /system/customize/resource/
sync
mount -o remount,ro /dev/block/mmcblk0p29 /system
reboot
Click to expand...
Click to collapse
Link not working anymore
Sent from my HTC PH39100 using Tapatalk

[Q] HELP with REVONE!!!

I am able to get everything to work up till ./revone -P. it then tells me no need to reboot. I have tried to continue just from there, and to reboot and continue. Whenever i type in ./revone -s 0 -u i get error code 1.
Here is my whole process:
Code:
Mihirs-MacBook-Pro:HTCOneRoot Work$ ./adb-mac push revone /Data/local/tmp/
failed to copy 'revone' to '/Data/local/tmp/': No such file or directory
Mihirs-MacBook-Pro:HTCOneRoot Work$ ./adb-mac push revone /Data/local/tmp
failed to copy 'revone' to '/Data/local/tmp': No such file or directory
Mihirs-MacBook-Pro:HTCOneRoot Work$ ./adb-mac push revone /data/local/tmp
3047 KB/s (648208 bytes in 0.207s)
Mihirs-MacBook-Pro:HTCOneRoot Work$ ./adb-mac shell
[email protected]:/ $ cd /dat/local/tmp
/system/bin/sh: cd: /dat/local/tmp: No such file or directory
2|[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ ls
revone
[email protected]:/data/local/tmp $ chmod 755 revone
[email protected]:/data/local/tmp $ ./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful - please reboot to continue.
[email protected]:/data/local/tmp $ exit
Mihirs-MacBook-Pro:HTCOneRoot Work$ ./adb-mac reboot
Mihirs-MacBook-Pro:HTCOneRoot Work$ ./adb-mac shell
[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ ./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone failed (error code = -1)
255|[email protected]:/data/local/tmp $
Please help me!
I have tried this entire process through terminal emulator, and through adb commands from my macbook pro.
Any suggestions will be appreciated!

After restarting you need to do the first few steps up to the chmod command again

After this:
"[email protected]:/data/local/tmp $ ./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful - please reboot to continue."
Do reboot hold of "power button" , don't use any commands for reboot.

from the revone thread post #2:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

error code -1
can someone please help me with this ...i follow all commands and still receive error code -1?????? im getting extremely frustrated I have tried all possible solutions im on my final solution which is to flash a sense based 4.3 rom by sideloading the rom....but im lost so please fellow developers help me out please

Amazon Fire 5th Gen 2015 Root[only hd 7 and os 5.0.1]

NOTE THIS ROOT ONLY WORKS WITH FIRE OS 5.0.1 AND ONLY THE HD 7 NOT THE 10 OR 8
WE HAVE GAINED ROOT!!!
Thanks to @jkchr1s for the help and the windows bat file, @csolanol for actually finding the root, and @diegocr as well as the @Chainfire SuperSu for the root binaries!!
Heres a video for you guys who need help:
https://www.youtube.com/watch?v=ux-2b3X3BlI&feature=youtu.be
Just download the zip file from this link and remember to use a windows/linux device for now.
Mediafire Mirror #1
For windows hit install.bat and follow trough the steps
For Linux run it through the linux command prompt
2nd way to root:
1. Download supers from chain fires website https://download.chainfire.eu/696/supersu/
2. Download @ggow custom recovery or @cnsoal Twrp
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
http://forum.xda-developers.com/ama...ecovery-cyanogen-recovery-2015-11-04-t3240726
3. Place the recovery image in the same folder as adb and fastboot.
4. Put your fire in fastboot mode
5. Boot into the custom recovery via "fastboot boot <recoverimsgename>.img.
6. You should be in the cynogen recovery (Or twrp depending on which recovery you downloaded_
7. Then pick adb sideload, and select it and manually install drivers. If you're too lazy just place su in your SD card and flash the zip from there.
8. Adb sideload supersu and you'll get root!!
REMEMBER WE ARE NOT LIABLE IF YOUR TABLET IS BRICKED!!!
I have also left the boot.img tool as well as the modified versions of the boot.img files just incase if anyone else wants to probably dig deeper and explore more about the boot.img file

Have you tried adding the su binary to /sbin in the ramdisk, and editing default.prop to ro.secure=0?

just adding it to /sbin wont solve this. you would have to add all the selinux info for it also and then also manage to start the su daemon.
ro.secure=0 is already inside the attached boot.img above, doesn't seem to help

If we have r/w to the filesystem, take a look at the root script in this LG package: http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
Do you think this method would work?

Lol wow! Seems to be sparked by my discovery of this new root method! Anyhow, @jkchr1s might be on to something.
---------- Post added at 11:12 AM ---------- Previous post was at 11:10 AM ----------
jkchr1s said:
If we have r/w to the filesystem, take a look at the root script in this LG package: http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
Do you think this method would work?
Click to expand...
Click to collapse
I'll try it!
EDIT: DON'T DO IT! IT CONTAINS LG DEVICE SPECIFIC THINGS AND IT COULD BRICK YOUR DEVICE. GOOD THING I LOOKED AT THE INSTALL.BAT BEFORE I TRIED IT!

Vlasp said:
Lol wow! Seems to be sparked by my discovery of this new root method! Anyhow, @jkchr1s might be on to something.
---------- Post added at 11:12 AM ---------- Previous post was at 11:10 AM ----------
I'll try it!
EDIT: DON'T DO IT! IT CONTAINS LG DEVICE SPECIFIC THINGS AND IT COULD BRICK YOUR DEVICE. GOOD THING I LOOKED AT THE INSTALL.BAT BEFORE I TRIED IT!
Click to expand...
Click to collapse
I don't mean to run the root.bat file, look at the root script. It copies SuperSU binaries, adds a su service, and chcon's the necessary files.

jkchr1s said:
I don't mean to run the root.bat file, look at the root script. It copies SuperSU binaries, adds a su service, and chcon's the necessary files.
Click to expand...
Click to collapse
Yeah, but we are going to have to change the device specific stuff (if it matters for our device).

I have updated the thread!! Thanks @jkchr1s for the clear steps and @diegocr for helping out and giving us r/w ability.

This will work for rooting this device now.

Someone is root .............
With boot.img

Vlasp said:
This or KingRoot will work for rooting this device now.
Click to expand...
Click to collapse
I adapted the guide and u know what?. I am root!!!
Did all the steps by hand and SuperSu is working, i can make su in adb shell.
I can't write a guide right now, i have to go out of the house but this is done guys.

Vlasp said:
This or KingRoot will work for rooting this device now.
Click to expand...
Click to collapse
What do you mean? KingRoot says it failed booting with the boot-firestarter.img

jkchr1s said:
What do you mean? KingRoot says it failed booting with the boot-firestarter.img
Click to expand...
Click to collapse
yeah, sorry. only the tutorial will work.

Vlasp said:
This will work for rooting this device now.
Click to expand...
Click to collapse
Dosent work?

Vlasp said:
yeah, sorry. only the tutorial will work.
Click to expand...
Click to collapse
Sorry, I'm not seeing a guide or tutorial on that link. That's a link to KingRoot.

Just for those of you that wanna root it just now:
Files needed and a boot.img to apply with fastboot boot boot.img:
https://www.dropbox.com/s/nurzm8q3pqx2v4z/root_fire.zip?dl=0
Unzip the attachment and push the files directory contents to /data/loca/tmp using adb
Example: adb push Superuser.apk /data/local/tmp/
adb push su /data/local/tmp/
...
and then do the follwing in adb shell:
mkdir /system/app/SuperSU
chmod 0755 /system/app/SuperSU
chcon ubject_r:system_file:s0 /system/app/SuperSU
cp /data/local/tmp/Superuser.apk /system/app/SuperSU/SuperSU.apk
chmod 0644 /system/app/SuperSU/SuperSU.apk
chcon ubject_r:system_file:s0 /system/app/SuperSU/SuperSU.apk
mkdir /system/bin/.ext
chmod 0755 /system/bin/.ext
chcon ubject_r:system_file:s0 /system/bin/.ext
cp /data/local/tmp/su /system/xbin/su
chmod 0755 /system/xbin/su
chcon ubject_r:system_file:s0 /system/xbin/su
cp /data/local/tmp/su /system/bin/.ext/.su
chmod 0755 /system/bin/.ext/.su
chcon ubject_r:system_file:s0 /system/bin/.ext/.su
cp /data/local/tmp/su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
chcon ubject_r:system_file:s0 /system/xbin/daemonsu
cp /data/local/tmp/su /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chcon ubject_r:zygote_exec:s0 /system/xbin/sugote
cp /data/local/tmp/supolicy /system/xbin/supolicy
chmod 0755 /system/xbin/supolicy
chcon ubject_r:system_file:s0 /system/xbin/supolicy
cp /data/local/tmp/libsupol.so /system/lib/libsupol.so
chmod 0644 /system/lib/libsupol.so
chcon ubject_r:system_file:s0 /system/lib/libsupol.so
cp /system/bin/sh /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chcon ubject_r:system_file:s0 /system/xbin/sugote-mksh
cp /system/bin/app_process32 /system/bin/app_process32_original
chmod 0755 /system/bin/app_process32_original
chcon ubject_r:zygote_exec:s0 /system/bin/app_process32_original
cp /system/bin/app_process32 /system/bin/app_process_init
chmod 0755 /system/bin/app_process_init
chcon ubject_r:system_file:s0 /system/bin/app_process_init
rm /system/bin/app_process
rm /system/bin/app_process32
ln -s /system/xbin/daemonsu /system/bin/app_process
ln -s /system/xbin/daemonsu /system/bin/app_process32
touch /system/etc/.installed_su_daemon
chmod 0644 /system/etc/.installed_su_daemon
chcon ubject_r:system_file:s0 /system/etc/.installed_su_daemon
Once all is done you need to fastboot boot boot.img again to establish proper perms to the new files. Actually we can't change ownership of files to root from adb.
Run this command in adb shell:
/system/xbin/su --install
Then reboot and voila! you are root.
Sorry for text format by chrome doesn't allow me to format it as code...

Awesomeslayerg said:
Dosent work?
Click to expand...
Click to collapse
@csolanol said it does...

Proof [emoji12]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

chown 0.0 /system/app/SuperSU gives me operation not premitted

Awesomeslayerg said:
chown 0.0 /system/app/SuperSU gives me operation not premitted
Click to expand...
Click to collapse
Yup, i edited the post to delete that line. That ownership change will be applied when you reboot from fastboot with the custom boot.img again. Note the end of the post.

TWRP Flashable BootSplash ZIP

Just a simple TWRP Flashable BootSplash Zip for example to replace the warnings when you unlocked/rooted your device.
It will open up_param.bin and repack it with the jpg,s inside the zip.
Simply replace svb_orange.jpg , logo.jpg and booting_warning.jpg with a jpg of your own choice.
Make sure the images don't exceed 500kb, and keep exact same resolution (1440x3040 24bbp)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*** Download ***
Script:
Code:
#!/sbin/sh
OUTFD=$2
ZIP=$3
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
cd /tmp
rm -rf arter97
mkdir arter97
cd arter97
unzip -o "$ZIP"
ui_print " - mounting data partition"
mount /data
if [ ! -e /data/media/0/up_param.bak ]; then
ui_print " - backing up current up_param to /sdcard/up_param.bak"
cat /dev/block/platform/13d60000.ufs/by-name/up_param > /data/media/0/up_param.bak
chown 1023:1023 /data/media/0/up_param.bak
chmod 664 /data/media/0/up_param.bak
fi
ui_print " - installing new logo.jpg"
chmod 755 tar
mkdir tartemp
cd tartemp
/tmp/arter97/tar -xf /dev/block/platform/13d60000.ufs/by-name/up_param
cp /tmp/arter97/logo.jpg .
chown root:root *
chmod 444 logo.jpg
touch *
/tmp/arter97/tar -pcvf ../new.tar *
cd ..
cat new.tar > /dev/block/platform/13d60000.ufs/by-name/up_param
ui_print " - installing new svb_orange.jpg"
chmod 755 tar
mkdir tartemp
cd tartemp
/tmp/arter97/tar -xf /dev/block/platform/13d60000.ufs/by-name/up_param
cp /tmp/arter97/svb_orange.jpg .
chown root:root *
chmod 444 svb_orange.jpg
touch *
/tmp/arter97/tar -pcvf ../new.tar *
cd ..
cat new.tar > /dev/block/platform/13d60000.ufs/by-name/up_param
ui_print " - installing new booting_warning.jpg"
chmod 755 tar
mkdir tartemp
cd tartemp
/tmp/arter97/tar -xf /dev/block/platform/13d60000.ufs/by-name/up_param
cp /tmp/arter97/booting_warning.jpg .
chown root:root *
chmod 444 booting_warning.jpg
touch *
/tmp/arter97/tar -pcvf ../new.tar *
cd ..
cat new.tar > /dev/block/platform/13d60000.ufs/by-name/up_param
ui_print " - unmounting partition /data"
umount /data > /dev/null 2>&1
ui_print " "
ui_print "finished"
ui_print "Edited for s10+ by Whiskey103"
cd /
rm -rf /tmp/arter97
sync
Credits:
@Radzian - used his base zip and edited for s10+
@ianmacd for pointing to the error in my first attempt.

Any custom recovery and/or firmware for the Sprint S10 5G? I'm willing to try new things on mine.

Thx, my phone bricked.