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...

[CF3D] Help please! Couldn't find a solution..I'm stuck!!

Okay I've done enough research before deciding to make this post but couldn't find any solution.
Situation is I tried to install CF3D using CWM and now I'm stuck at the black boot screen that says GT N7000.
I tried to log into ADB shell and execute /system/lib/cf3d_uninstall.sh since that is the general solution but it seems I do not have the file there. Can someone give me the sh file if they have or tell me how to remove the drivers manualls through the ADB shell so that I can boot back normally. I did not backup before doing this..and I guess today isn't my day! Please help me remove the drivers! It's a little urgent.
I am new to the ADB shell concept and these are the commands I executed after connecting:
adb devices
adb shell
su
ls -d */
cd system
cd lib
sudo cf3d_uninstall.sh
Here it says that the file isn't found.
Edit: Nevermind.. Restoring back to CM9 for tonight...
Click to expand...
Click to collapse

tried these ?
sh system/lib
sh /cf3d_uninstall.sh

Should I just execute the contents of this shellscript via ADB? I found these on Google Code
Code:
#!/system/bin/sh
mount -o rw -o remount /dev/block/mtdblock4 /system
stop
cat /system/lib/libGLESv1_CM_ORG_CF3D.so > /system/lib/libGLESv1_CM.so
chown 1000.1000 /system/lib/libGLESv1_CM.so
chown 1000:1000 /system/lib/libGLESv1_CM.so
chown system.system /system/lib/libGLESv1_CM.so
chown system:system /system/lib/libGLESv1_CM.so
chmod 644 /system/lib/libGLESv1_CM.so
cat /system/lib/libGLESv2_ORG_CF3D.so > /system/lib/libGLESv2.so
chown 1000.1000 /system/lib/libGLESv2.so
chown 1000:1000 /system/lib/libGLESv2.so
chown system.system /system/lib/libGLESv2.so
chown system:system /system/lib/libGLESv2.so
chmod 644 /system/lib/libGLESv2.so
#rm /system/lib/libGLESv1_CM_ORG_CF3D.so
#rm /system/lib/libGLESv2_ORG_CF3D.so
rm /system/lib/cf3d_uninstall.sh
rm /system/lib/cf3d_sh
reboot -f
reboot
reboot normal
toolbox reboot
busybox reboot -f
busybox reboot
busybox reboot normal

nokiamodeln91 said:
tried these ?
sh system/lib
sh /cf3d_uninstall.sh
Click to expand...
Click to collapse
Heya it says "Can't open 'cf3d_uninstall.sh' "

What Rom are you on?

nokiamodeln91 said:
What Rom are you on?
Click to expand...
Click to collapse
Ultimate N7000 XXLSC JellyBean 4.1.2 v5.1 ... And I really don't wanna reflash :/

Pl first try to locate where the cf3d files are and then run the command with right paths

[RESOLVED] CF3D Uninstall after boot loop
agvulcan said:
Okay I've done enough research before deciding to make this post but couldn't find any solution.
Situation is I tried to install CF3D using CWM and now I'm stuck at the black boot screen that says GT N7000.
I tried to log into ADB shell and execute /system/lib/cf3d_uninstall.sh since that is the general solution but it seems I do not have the file there. Can someone give me the sh file if they have or tell me how to remove the drivers manualls through the ADB shell so that I can boot back normally. I did not backup before doing this..and I guess today isn't my day! Please help me remove the drivers! It's a little urgent.
I am new to the ADB shell concept and these are the commands I executed after connecting:
adb devices
adb shell
su
ls -d */
cd system
cd lib
sudo cf3d_uninstall.sh
Here it says that the file isn't found.
Click to expand...
Click to collapse
Resolved (for me) :
I actually had the same error using the same command you did. You made a mistake though : when using an "sh" script, you have to invoke it's command, simply using "sh" before the name of the script you attempt to launch.
This is the way you have to go :
you should have typed : "sudo sh cf3d_uninstall.sh"
I actually managed to get it to work this way, and to stop boot loop / freeze (call it whatever you want), as it actually DID uninstall CF3D faulty drivers.
DO NOT USE CF3D with Jelly Bean, at the moment at least. Though Chainfire wrote he wouldn't develop anymore his drivers for JB, as it would need too much coding, again. Stick to GB or even ICS (it used to work for me)
--------
Full technique :
Prerequisites :
-CWM
-Aroma File Manager : Download it here :
Way to go :
-Take out your SD card from your device
-Copy Aroma FM to your Ext. SD Card using a microSD adapter (you can find one at any classical SD card retailer for a few bucks)
-Stick it back in your device
-Launch ClockWorkRecoveryMod
-"Install zip file"
-"Install from SD Card'
-Choose Aroma FM zip file, and install it.
-Tap on option key to get option menu, and launch the shell
-Then type :
su
cd system
cd lib
sh cf3d_uninstall.sh
Your device will automatically reboot, and boot your system normally.
See Ya

Chain Fire 3d boot loop .. not booting help plz ASAP
hello.. i am facing the same problem
i am using Panasonic T11, i had rooted it but it does not have any CWM,etc
when i installed Chain Fire 3d. it prompt me to reboot, bt it was boot looped, and i tried the ways u suggested
the problem its shows this errors in pic . plz suggest me something i can do about my phone
{
"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"
}
when i tried to go in recovery mode it shows ENTRY QPST DOWNLOAD
plz help me

[guide] working motion control fix for b609

Hello fellow P7 owners, I installed B609 and was disappointed to find motion control not working.
After many hours of reinstalling, downgrading upgrading etc, i found a 2 minute fix for this problem, no reboots no hassles
What you NEED:
ROOT
ADB (if going to use PC for shell, terminal emulator works too)
2 MINUTES
Here is how to fix:
connect up your phone and make sure adb is working
type
Code:
adb logcat *:W
into cmd or terminal
go to settings and enter motion control menu (it will be blank)
press ctrl+c on your cmd or terminal to stop logcat and look for line that says "FileNotFoundException:" there will be a file name (mine was /data/cust/hw_motion_config.xml)
It will look like
Code:
java.io.FileNotFoundException: /data/cust/xml/hw_motion_config.xml: open failed: ENOENT (No such file or directory)
go to a file browser and check your /cust to find a folder called xml (mine was /cust/hw/default/xml) and copy that xml folder to your /cust/preinstalled/public/ folder
type in shell or terminal
Code:
mount -o remount,rw
rm /data/cust
ln -s /cust/preinstalled/public /data/cust
if no errors occured in steps, go to motion settings and you're good to go!
This worked for my P7-L10 running B609, unlocked bootloader and full root (no kingo etc)
Please hit THANKS if this helped you

better way:
1,connect up your phone and make sure adb is working
2,type in shell or terminal
Code:
mount -o remount,rw
rm /data/cust
ln -s /cust/hw/norrmal /data/cust or if you are in EU ln -s /cust/hw/eu /data/cust (mentioned /cust/hw/default is for chinese)
3, reboot and you are ok - you can wipe dalvik-cache too
ENJOY

Z!L0G80 said:
better way:
1,connect up your phone and make sure adb is working
2,type in shell or terminal
Code:
mount -o remount,rw
rm /data/cust
ln -s /cust/hw/norrmal /data/cust or if you are in EU ln -s /cust/hw/eu /data/cust (mentioned /cust/hw/default is for chinese)
3, reboot and you are ok - you can wipe dalvik-cache too
ENJOY
Click to expand...
Click to collapse
thanks for this :good:
it is really easy and solve the problem

Z!L0G80 said:
better way:
1,connect up your phone and make sure adb is working
2,type in shell or terminal
Code:
mount -o remount,rw
rm /data/cust
ln -s /cust/hw/norrmal /data/cust or if you are in EU ln -s /cust/hw/eu /data/cust (mentioned /cust/hw/default is for chinese)
3, reboot and you are ok - you can wipe dalvik-cache too
ENJOY
Click to expand...
Click to collapse
Maybe I should clarify that my method will work for all but is aimed at those with custom ISP builds.
Say you got to making a thread like this before me, your method only works for those who have a "normal" folder which I did not have

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.

Rebrand P10 Plus Emui 8 (No Downgrade While Rebranding)

Ok I Have Found a guide to Rebrand P10 Plus on oreo.
many people were not rebranding because the method which we were using to rebrand needs to downgrade our devices which has high chances of bricking
THINGS NEEDED BEFORE PROCEDING:
1.unlocked device
2. A rooted p10 plus
3.nocheck recovery for p10 plus(MHA_RECOVERY8_NoCheck also works with our devices)
4.adb
STEPS:
1.Unlock Your Bootloader
2.root your devices via magisk or su.
3.Get the Stock Firmware Files you want to use from Firmwarefinder or other Source and rename the files
update_data_full_public.zip -> update_data_public.zip
update.zip -> update.zip
update_full_VKY-L29_hw_spcseas.zip -> update_all_hw.zip
4.Copy them via MTP to your internal memory
5.Boot into fastboot mode and flash no check recovery.
6.Install Magisk Manager
7.Download oeminfo binary file https://mega.nz/#!X0AjASKS!KvXMfbtd8...XlBi0SDZdzJwfo copy to internal memory.
8.Boot into Android System enable adb debbuging in developer settings.
9.copy oeminfo to internal memory
10.adb shell
11.su
12.accept the prompt at your P10 Plus
13.mkdir /data/local/tmp
14.mv /sdcard/oeminfo /data/local/tmp
15.cd /data/local/tmp
16.chmod +x oeminfo
17. ./oeminfo VKY-L29C636 hw/spcseas (in my case) (Rename it according to a firmware which you are rebranding to)
18. mkdir /data/update/HWOTA
cd /sdcard/
19.mv *.zip /data/update/HWOTA
20.Paste recovery command:
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_all_hw.zip" >> /cache/recovery/command
exit
21.adb reboot recovery
22.Phone will reboot and starts to install and Rebrand your Phone .
CREDITS: oslo83 a nice guy who guided me
View attachment 4674976