Develop Bugs

[Guide]Running BackTrack5(Ubuntu Lucid v10.04) On Your ET4G!!!

-Found this little gem posted in this thread, located under the AT&T Samsung Galaxy S II Android Development Forum. So I decided to installed it on my phone and SURPRISE SURPRISE, turns out it works great on our Epic Touch 4G too !
-Anyways, you can follow the instructions which I've quoted right below, and they are also found in the link above. This installation/setup takes all but 5-10minutes if not less!!! Hardest part, if you wanna call it that(its really just the longest part), is downloading the required files. Once you've downloaded all 10 7zip files into a single location, just open ONE OF THEM and extract it by double clicking it and then dragging the bt.img file to your computer. AND you only have to do this to ONE of the downloaded files, no need to open each of them and drag out the bt.img 10 different times, BUT you do need to have all 10 of them copied into the same folder in order for the full image to extract correctly!
-Also, the instructions stated to run the following command:
Code:
su
cd /sdcard/bt
sh installbt.sh
startbt
bt
but they were made for the AT&T version, so on our phones you need to either:
a)copy the bt folder off of /sdcard/external_sd to /sdcard instead; or
b)use the following commands instead:
Code:
su
[B]cd /sdcard/external_sd/bt[/B]
sh installbt.sh
startbt
bt
-If you make use of it, please be sure to thank the originator of it, anantshri, on his thread here, and DooMLoRD on his thread here for assisting in porting it over from the Xperia10 to the SGSII! Good things!
{
"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"
}
DooMLoRD said:
\\----[ Announcement ]----//
[12/July/2011] Updated with new package (bt5_sgs2_shell_scripts_v2.zip) containing shell scripts & busybox
//----[ Announcement ]----\\
hi guys DooMLoRD & anantshri present to u:
BACKTRACK 5 on SGS2
all the work was done by anantshri, i mostly assisted by testing it on my SGS2 and modding it slightly so that it will work properly for SGS2... dont forget to thank him!
i will try n keep it short and simple...
for more details u can read the original thread at X10 sub-forums...
[DEV] BACKTRACK 5 on Xperia X10 chroot
[ Screenshots ]
on startup (shell):
in GUI:
phone + BT5 GUI:
[ Requirements ]
rooted device with busybox installed, if u are using CF-root kernel then u already have busybox installed
Some apps from Android Market:
Android Terminal Emulator
androidVNC
[optional] highly recomended keyboard: Hacker's Keyboard
7zip (for PC), for extracting the files
around 3.3 GB free on internal sdcard (/sdcard/)
[ How To : File Setup ]
u need to do this only once
download the files from the links provided in this thread
extract the files using 7zip to a temporary folder (needs 3.3GB free on that drive)
connect ur SGS2 to PC and mount USB storage
create a folder named 'bt' (without quotes) in the root of ur sdcard and copy the bt.img in that folder
also place the file bt5_sgs2_shell_scripts_v2.zip in root of sdcard, this file has to be flashed via recovery
once u verify that the above is correct then un-mount usb storage
reboot into recovery and flash the file bt5_sgs2_shell_scripts_v2.zip stored in root of sdcard (or if u are using CWM app then just select the file for flashing and the app will do the rest )
once ur phone reboots into OS just check the /sdcard/bt folder
final directory structure should look like this:
/sdcard/bt/bt
/sdcard/bt/bt.img
/sdcard/bt/installbt.sh
/sdcard/bt/startbt
/sdcard/bt/stopbt
once u verify that the above is correct then u can proceed
[ How To : Launch BT ]
start Terminal Emulator app on ur SGS2 and enter the following commands step by step (accept/allow any SuperUser request/popup that u may receive)
su
cd /sdcard/bt
sh installbt.sh
startbt
bt
now u are in BackTrack5 shell
to launch GUI (vncserver) enter the following command
ui
now note the number N shown localhost:N
e.g. as u can see from the above image that "New 'X' desktop is localhost:1", so N=1
the vncserver is running at (5900 + N, N=1 ; so server port is 5901)
now launch androidVNC app on phone and fill in the detials as follows
Nick : bt
Address : 127.0.0.1
Port : 5901
Password : 12345678
Username : <leave it blank>
Color Format : 24-bit color (4 bpp)
inside vnc window select input mode (i personally recommend the following)
TouchPad (here your screen works like a big touchpad use it to navigate mouse.)
and then press connect... now u are in BackTrack GUI!
if u want to exit/close BT5 then u need to follow these steps:
close the androidVNC app (Menu -> Disconnect)
go back into Terminal Emulator app and enter the following commands
u should be at this shell [email protected]:~#
killui
exit
now u will get back to this shell> #
now enter the following commands to stop bt and exit
stopbt
exit
exit
u can now exit the Terminal Emulator app
i would also recommend that u reboot ur phone
[ Important Info ]
root password is 12345678
[ Download Links ]
update.zip package containing shell scripts, busybox (which gets installed to temporary location) [to be flashed via recovery]
this will not disturb/conflict with busybox of ur ROM/CF-Root kernel
bt5_sgs2_shell_scripts_v2.zip (~800KB)
main bt.img
these links are 7zip archives split into 50mb files, u will need to download the following:
total size: 486MB
bt.7z.001 (50 MB)
bt.7z.002 (50 MB)
bt.7z.003 (50 MB)
bt.7z.004 (50 MB)
bt.7z.005 (50 MB)
bt.7z.006 (50 MB)
bt.7z.007 (50 MB)
bt.7z.008 (50 MB)
bt.7z.009 (50 MB)
bt.7z.010 (36 MB)
also uploading to mediafire for mirroring...
Mediafire Folder: http://www.mediafire.com/?f9gk3p3t9wip5
md5 hashes:
Code:
bt.7z.001 f19e769bf42b44867c8bb1d9bb9c5d44
bt.7z.002 a4dd26a98d2c6925d871fb108fb5fadb
bt.7z.003 ecca5a5d72c449117b1d3dbc23aeb1a2
bt.7z.004 8ad487a01e4d149f0247ad9288201f32
bt.7z.005 adab9cb3778cd8ac89ccc0e21997c3d7
bt.7z.006 ba6a28de70a1115dc316f45cea508215
bt.7z.007 f59757e891631607e1a35abadb231b3b
bt.7z.008 cdb8c28a1fbd03657bb42e8d69f0600b
bt.7z.009 426d892f872679e3d53d0ebb0376e138
bt.7z.010 c7d2957bc65340d967b9dd3646d7cb39
ENJOY!
Click to expand...
Click to collapse

ScreenShots

does injection and/or wep hacking works?

leond said:
does injection and/or wep hacking works?
Click to expand...
Click to collapse
Unfortunately it does not...I know the main purpose running BackTrack is being able to use its Networking Security Tools, but it is based on Ubuntu Lucid, v10.04 LTS, so you're still able to run a fully functional operating system on your mobile phone! ATM its more of a novelty than a practicality but Im hoping they find a way to turn the tables soon !

Double Post

Triple Post

Nice thanks for trying it and sharing it!

Question the 10 files that you say to download they can not be extracted? i tryed or am i doing it wrong and when i run commands it fails at bt and says chroot cant execute bin/bash no such file or directory help please!

can you still txt and make calls with this?? looks awesome tho

kyhassen said:
can you still txt and make calls with this?? looks awesome tho
Click to expand...
Click to collapse
It side loads it, so you still get all your notifications and phone calls, and if you just hit the home button it'll take you back to the android OS, it doesn't NOT replace it
donnyevo4g said:
Question the 10 files that you say to download they can not be extracted? i tryed or am i doing it wrong and when i run commands it fails at bt and says chroot cant execute bin/bash no such file or directory help please!
Click to expand...
Click to collapse
They ALL have to be downloaded into the same location before you can successful extract it. ie, if you have bt.7z.001 - bt.7z.009 and are missing bt.7z.010, it will not work....did you download and flash the zip? There's more steps than just extracting the bt image(10 7zip files), also just a heads up, when flashing the zip make sure to clear both cache and dalvik, or you may get an installation error...let me know if you need additional help

all ten of the files i downloaded and put into a folder called bt and i flashed the zip and did not get any error message i have 7zip on my pc and it does not even give me the option to extract what am i doing wrong when i right click on the files and go to properties the file type is not a unzippable file

donnyevo4g said:
all ten of the files i downloaded and put into a folder called bt and i flashed the zip and did not get any error message i have 7zip on my pc and it does not even give me the option to extract what am i doing wrong when i right click on the files and go to properties the file type is not a unzippable file
Click to expand...
Click to collapse
Gotcha! wasn't really sure what kind of error you were having but if that is it, all you need to do is double click on any one of the files, I used the bt.7z.001, and when it opens, just drag the bt.img file to your desktop, and let it extract! Its not really a zip so thats why it doesn't have an option to extract it in the menu but again just double click on anyone of them and you'll be all good broda!

ok i got the one file to extract but the others wont now what do i do once i have that image file do i put it in the bt folder and then run commands?

donnyevo4g said:
ok i got the one file to extract but the others wont now what do i do once i have that image file do i put it in the bt folder and then run commands?
Click to expand...
Click to collapse
-Yup you got it! They way 7z file work is that it evenly breaks a larger file down into multiple smaller .7z files.
-In this example, the bt.img file is about 486MB. So, 9/10 of the bt.7z files are 50MB each and then the 10th file, holding the remain bytes, is 36MB. So once you have them all downloaded into the same location, you can open ANY one of them and drag its content to the hard drive, and it will extract the entire 486MB, using all of the files. And you only have to do this ONCE, you DON'T have to open each of them and drag all of their content out.
-So yea, now copy the bt.img file to the bt folder located in the /sdcard/external_sd folder, and then copy the entire bt folder to the /sdcard folder instead(Im guessing the ATT version doesn't have an external sd card, cuz the cd /sdcard/bt command is for the /sdcard location and not /sdcard/external_sd, which is where flashing the zip places the bt folder). So in the end you're going to use this /sdcard/bt folder and not /sdcard/external_sd/bt...EDITED..and don't quote me on the .7z file sizes from above, not really sure how large they are cuz looking at the file now in my phone its 3.26GB, I was using 50MB for an easy explanation and arguments sake only, thx...and Im actually gonna update OP w/ the step needing to copy the bt folder from the /sdcard/external_sd location to /sdcard instead

now im getting a chroot error when i type bt it says chroot execute bin/bash innput/output error? HELPPPPP

donnyevo4g said:
now im getting a chroot error when i type bt it says chroot execute bin/bash innput/output error? HELPPPPP
Click to expand...
Click to collapse
post exactly what you have done so far and what commands you are able to enter successfully and at what command you are getting the error, thx

Posting now stay online

Heres the error im getting look towards the bottom

donnyevo4g said:
Heres the error im getting look towards the bottom
Click to expand...
Click to collapse
ok and where's the rest of the info I asked for?

i can only fit so much in the screen shot what else you looking for

ASUS ZenPad Z8 (ZT581KL) (P008) (Verizon) - Firmware

I found some firmware files for the Asus Zenpad Z8 ZT581KL for Verizon. Neither Asus or Verizon host any firmware for this device, despite having other similar device firmware available (like the ZT500KL, etc), which sucks.
VZW_ZT581KL_V3.4.16_all_user_M101901_16.0.0_160519.zip
ASUS Factory VZW_ZT581KL_V5.4.1_all_user_M101901_16.0.0_170202 androidhost.ru.zip
ZT581KL_T3.3.8_pre_burn_image_20160516.zip
ZT581KL_Z581KL_EMERGENCY_DLOAD.7z
ZT581KL_FUSE_Security_Keybox_160728.rar
Z581KL_initrd_diff.zip
ASUS.Flash.Tool.v1.0.0.45.zip
Running a stock, factory reset device, I was able to flash VZW_ZT581KL_V3.4.16_all_user_M101901_16.0.0_160519.zip using Asus Flash Tool 1.0.0.45, which successfully downgraded Tablet from V3.4.23 to V3.4.16.
I tried flashing ZT581KL_T3.3.8_pre_burn_image_20160516.zip but it did not work and error-ed out with no brick or anything. Usually the firmware is in a .raw format so you can flash either via zip file which has raw file in root folder of archive, or via the raw file itself. I tried both and was not successful. For some reason this archive had a .bin file instead of a .raw file. I tried renaming them but still didn't work. However, I was able to extract the .bin to find the firmware files inside just like the other version firmwares (that were in raw). One thing I have not tried yet, is to try manually flashing the individual firmware files from the extracted bin, and see if that works--or if someone else with this tablet wants to try, here are the files. If successful, it might lower kernel version down more to allow root exploits to root device.
I have not tried flashing V5.4.1, but I'm confident it will work. I do not know if via the Asus Flash Tool/Asus Tablet will allow doing a flash to V5.4.1 and downgrade back down to V3.4.16, but just did V.3.4.23 (stock orig fw already on device) to V.3.4.16 and it worked. I did receive an OTA to upgrade to V3.4.18 (or was it V.3.4.21, I can't remember) and took the upgrade (then flashed back to V.3.4.16), so it appears that when doing an OTA it will "leap-frog" to the next higher version release until you are on the newest build, so the first OTA you get won't do a direct upgrade from V3.4.16- to V5.4.1 or V5.4.5, but will upgrade it in an incremental way, via the next higher version release.
Hopefully someone can try to root their tablet if any of these files are of any help. I might work up courage to try 3.38 again via manual fastboot, but if you do it and succeed, I would love to hear about it.
The other files hosted ZT581KL_Z581KL_EMERGENCY_DLOAD.7z and ZT581KL_FUSE_Security_Keybox_160728.rar have to do with re-flashing the Qualcomm Snapdragon SoC (un-bricking), and the other one something to do with clearing/setting FUSE when the phone leaves factory or something, I'm not sure. Hopefully they can be of some use to someone to unlock this device. It would be nice. So here u go.
https://www.androidfilehost.com/?w=files&flid=289525 - link to ASUS_ZenPad_Z8_ZT581KL_P008_Verizon files

Has anyone tried flashing 'ZT581KL_T3.3.8_pre_burn_image_20160516' yet? Just wondering if it was successful; I haven't tried it yet.

smokejumper76 said:
Has anyone tried flashing 'ZT581KL_T3.3.8_pre_burn_image_20160516' yet? Just wondering if it was successful; I haven't tried it yet.
Click to expand...
Click to collapse
can you tell me how to extract the .raw from .bin, I will try to flash the device.

fuyangui said:
can you tell me how to extract the .raw from .bin, I will try to flash the device.
Click to expand...
Click to collapse
I used 7zip to extract the firmware from the archive.. Open 'ZT581KL_T3.3.8_pre_burn_image_20160516.zip' with 7zip. It should come up with a folder named 'ZT581KL_T3.3.8_pre_burn_image_20160516'. Go in that folder. There will then be a file shown called 'userdata.bin'. In 7zip, if you right click that file, then select 'Open Inside', it should open inside the .bin file and show the firmware files. From there, you can extract them somewhere. Hopefully, you can try to apply each .img file separately (fastboot), one at a time, and see if it works. Thank you!

Sorry to resurrect this old thread but I might have some info that will help others.
First off thanks for the OP for the download links as I cannot find the OEM ROMS anywhere for this device.
Second here are some more instructions that you may need if you are having issues with this device.
Use ASUS FLash Tool v1.0.0.45, it has the device model that you need and was the one that worked for me. Then download ASUS Factory VZW_ZT581KL_V5.4.1_all_user_M101901_16.0.0_170202 androidhost.ru.zip from the link the OP posted, it should be the first file, then this is the step that I missed and took forever to figure out. You have to open that zip file and extract the .raw file, so you should have a file called ZT581KL_all_VZW_user_V5.4.1.raw. That is the file that you need to select in the Asus Flash Tool by clicking the little box with a down arrow inside it, then boot your tablet into Fastboot (Hold down the Power and Volume Down buttons) then once in fastboot, make sure you select the right model for this tablet it should be, ZT581KL, then I left Wipe Data as no, then connect your tablet to your computer with a USB cable, and you should see your Serial Number and a round icon under the State column. Then once that is all correct click the Start button, you may get an error about some FPS thing that can't be downloaded or something just hit OK, then you should see under the Description column that it's flashing the ROM, wait for a while and you should then have a "Flash Image Successfully (The serial number for your device will show here)" under the description and your tablet will reboot.
My tablet was originally on v5.4.5, this ROM will take you back to v5.4.1 but then through the tablet settings you can do an upgrade to v5.4.4 then do another one and it will be at v5.4.5 then you are all set.
So the issue I was having with the tablet was after a factory reset it would freeze at the setup screen and not let me continue, it took me forever to find out how to get it fixed and the instructions above worked for me, so if anyone else is having similar issues then hopefully this will help. I literally spent days and searched through about 70 forums to try and find a fix for it, I even reached to Asus for help, which they basically told me I had to pay to send it in and have it fixed, I was just about to give up when I came upon this thread and the OP's download links, so thanks again smokejumper76. If anyone has any questions about my instructions feel free to reply/comment.
Thanks!

Downgrade success
I used the files provided by OP and was able to successfully flash from 5.4.1 to 3.4.16. I got this tablet from a friend a few years back that he acquired from his work when it went out of business. It has the frp lock on it and im looking at the few available options. So, since this tablet had been sitting for two years. Its Guinea pig time. I'll flash the 3.3.8 and check back. It seems you can go forward or backward in so versions with the flash tool. So I'm not too worried about brick. If I can just get usb debugging on I'll be gold. Possible exploits if it runs.

Well. The 3.3.8 is not packaged properly for flashing. And that 600mb file expands to 9gb. There is a file "system.img" inside that's roughly the right size as the system and has the correct file structure. I have a friend who is going to help me repack that rom correctly for flashing. Meanwhile I am going to look into the 3.4.16 rom and see if I can't set usb debug to on and flash the modded image. From there I should be able to sideload su. I'll report back.

mofugggz said:
Well. The 3.3.8 is not packaged properly for flashing. And that 600mb file expands to 9gb. There is a file "system.img" inside that's roughly the right size as the system and has the correct file structure. I have a friend who is going to help me repack that rom correctly for flashing. Meanwhile I am going to look into the 3.4.16 rom and see if I can't set usb debug to on and flash the modded image. From there I should be able to sideload su. I'll report back.
Click to expand...
Click to collapse
Any update? Thank you for your efforts!

smokejumper76 said:
Any update? Thank you for your efforts!
Click to expand...
Click to collapse
I have the same tablet as well. Root would be great, any chance of unlocking the BL?

klister said:
I have the same tablet as well. Root would be great, any chance of unlocking the BL?
Click to expand...
Click to collapse
hi
any advance with this?
Enviado desde mi P008 mediante Tapatalk

WHat is the password to the files

I used the emergency download file to unbrick the Japanese version of z581kl. However, maybe the partition structure is different, when I try to write to the system partition, it says that there is no partition. What should i do? I'm sorry for my bad English.

allisondanielle said:
WHat is the password to the files
Click to expand...
Click to collapse
https://www.asusflashtool.com/ - Description Page with Password
Unzip Password: asusflashtool.com

I installed ZT581KL_T3.3.8_pre_burn_image_20160516.zip on my z581kl.
That resulted in Android 6.0 AOSP working!
There is a bug that screen rotation is not possible, but everything else is fine.
There is a bug that the screen cannot be rotated, but other than that, everything is fine. After installing TWRP, you need to mount /system and the location of system.img, and then execute the following command from the TWRP terminal.
mkdir new-system
mount system.img new-system
cp -a -R -p new-system/* /system
Translated with www.DeepL.com/Translator (free version)
{
"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"
}

清水侑磨 said:
I installed ZT581KL_T3.3.8_pre_burn_image_20160516.zip on my z581kl.
That resulted in Android 6.0 AOSP working!
There is a bug that screen rotation is not possible, but everything else is fine.
There is a bug that the screen cannot be rotated, but other than that, everything is fine. After installing TWRP, you need to mount /system and the location of system.img, and then execute the following command from the TWRP terminal.
mkdir new-system
mount system.img new-system
cp -a -R -p new-system/* /system
Translated with www.DeepL.com/Translator (free version)View attachment 5251235View attachment 5251237View attachment 5251239
Click to expand...
Click to collapse
I flashed the zt581kl image using EDL mode as described in this blog because the partition structure of the zt581kl is different from that of the zt581kl.
z581klでEDLモードに入る方法
xxxxx
itgameinfo.blogspot.com

Hi. New to the forum. I’m looking to downgrade my asus zt581kl so that I can root. Can someone show me the exactly step by step to downgrade my table? The above replies are a bit confusing to follow.

Tmupt said:
Hi. New to the forum. I’m looking to downgrade my asus zt581kl so that I can root. Can someone show me the exactly step by step to downgrade my table? The above replies are a bit confusing to follow.
Click to expand...
Click to collapse
Maybe start here:
https://www.getdroidtips.com/v5-4-1-nougat-verizon-asus-zenpad-z8/

I've been messing around with some of the files, and I was able to brick and unbrick the device following the firehose SOP PDF instructions. It basically flashes a barebones boot w/o any OS, and you have to flash a complete firmware to it to restore it back.
I was also able to install TWRP but it showed 0 space avail, I think because I didn't wipe it. I'll play with that later.
Used these links (use google translate)
z581klでEDLモードに入る方法
xxxxx
itgameinfo.blogspot.com
zenpad 3 8.0に簡単にTWRPを導入する+fastbootの裏技
xxxxx
itgameinfo.blogspot.com
I need to ask @清水侑磨 about how to flash ZT581KL_T3.3.8_pre_burn_image_20160516.zip. I think the userdata.bin file is a NAND dump created by Chinese Miracle 2 / Infinity Box but I'm having problems getting it to read the partitions. I was able to get the tablet in EDL mode, so I'm not sure what I'm doing wrong.

Anyone have a QPST .QCN file for ZT581KL for this device? Flashing 3.3.8 from that preburn file will nuke your IMEI. Mine got changed to all 1s and lost provisioning connectability w/ carrier. in fastboot/adb, so I need to restore it. If anyone could make a QCN (with your IMEI removed of course) so I can do that I would be most appreciative.

smokejumper76 said:
I've been messing around with some of the files, and I was able to brick and unbrick the device following the firehose SOP PDF instructions. It basically flashes a barebones boot w/o any OS, and you have to flash a complete firmware to it to restore it back.
I was also able to install TWRP but it showed 0 space avail, I think because I didn't wipe it. I'll play with that later.
Used these links (use google translate)
z581klでEDLモードに入る方法
xxxxx
itgameinfo.blogspot.com
zenpad 3 8.0に簡単にTWRPを導入する+fastbootの裏技
xxxxx
itgameinfo.blogspot.com
I need to ask @清水侑磨 about how to flash ZT581KL_T3.3.8_pre_burn_image_20160516.zip. I think the userdata.bin file is a NAND dump created by Chinese Miracle 2 / Infinity Box but I'm having problems getting it to read the partitions. I was able to get the tablet in EDL mode, so I'm not sure what I'm doing wrong.
Click to expand...
Click to collapse
Sorry for the late reply.
To boot AOSP, instead of burning the system.img from edl or fastboot, use adb.
The method is as follows
1、Start TWRP.
2、Connect your PC to USB.
3、Go to the directory where system.img is located, and press
adb push system.img /sdcard/
4、Enter the shell
adb shell
5、Mount system.img.
mkdir new-system
mount system.img new-system
6、Copy the contents of the mounted system.img to the system partition.
cp -a -R -p new-system/* /system
(If this fails, check that the system partition is mounted. If the system partition is mounted but you cannot write to it, format the system partition.)
7、After rebooting, you should see an Android message
Translated with www.DeepL.com/Translator (free version)

[GUIDE] Flash 'fastboot ROMs' for Lenovo Z6 Pro

Disclaim
All steps described here have been many times tested and proved to be safe but, you may know that sometimes in life unexpected things happen. I'm not responsible for any damage in your devices, do things at your own risk.
Introduction
Thanks to xda user @alexeei we can install almost every Z6 Pro stock ROMs using the Fastboot Mode. You always should check the package content and the installation script(s) to be sure that you know exactly what is gonna be installed. You can find all the ROMs listed and linked in this index.
Let's go with the guide.
0. Pre-requirements
- The Bootloader must be unlocked.
- Lenovo drivers installed in your computer. You can download them here . Thanks @benjieb
1. Download and extract the ROM
You cand find many of them here. Extract the downloaded file and a folder will be created with these contents:
- All the files required for the installation in Fastboot Mode.
- The ROM files.
- The .bat file(s) which contain(s) all the actions that will be performed during the installation.
{
"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"
}
You always should check the content of the .bat file(s). Read post #2 to get more info about this.
2. Reboot your device in Fastboot Mode
Shut down your device and boot it holding pressed both Volume Down + Power buttons until the Fastboot Mode menu appears. You can navigate in the Fastboot Mode menu with volume buttons to choose the options and the Power button to confirm, but at this point you don't need to do any action in this menu.
3. Connect the device to the computer with USB cable
4. Execute the .bat file
Just execute the .bat file with a double click and a CMD window will be opened and the installation will start. Only a few lines will appear at the beginning and then nothing will happen, it will seem to be stopped but actually it's not, just be patient because this screen could last around ten minutes. So despite of the 'Invalid sparse file format at header magic", keep the faith and don't do anything but wait.
The device will reboot once the installation is done.
5. Errors in the log. No voice in calls.
Some errors may appear in the CMD window during the installation, this is because some partitions are 'critical' and we're not allowed to modify them via fastboot. Usually this is not a problem because these "small partitions" don't prevent the new ROM to work normally, except if you're installing Android 10 from Android 9. If you change Android version with this method you will find that your micro doesn't work in calls. You can fix it installing these "small partitions" from TWRP.
Any correction, info or advise about this post will be very welcome.

About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.

descarao81 said:
About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.
Click to expand...
Click to collapse
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom

hilary trump said:
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom
Click to expand...
Click to collapse
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
Thanks. The rom has not released yet. I just pre-ordered a chinese variant tablet P11 pro TB-J706F

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
I found the link as follows
mirrors.lolinet.com/firmware/lenovo/ Tab_P11_Pro/TB-J706F/TB-J706F_S210002_201015_ROW.zip
But inside the package there is no BAT file though

How to skip(bypass) Google sign-in NSTV Pro 2019 with any firmware versions!

*** You should unlock bootloader ***
-In fastboot mode:
Code:
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! F.ck the spy.
For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana

Wow you know how long I have been waiting for this?
I did not test it yet but I will soon, hopefully today. Will work with both Dev image and regular image?
Thanks @mrhamed
By the way, Do you know if this method also works on a 2017 Pro 16gb version?

This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
{
"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"
}

mrhamed said:
This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
Click to expand...
Click to collapse
awesome.
by the way what is that screenshot?
If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?

cHECKjAM said:
awesome.
by the way what is that screenshot?
If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?
Click to expand...
Click to collapse
It's my device screen.
I don't like to lock-bootloader, so AI not works at this time, I'm testing "MagiskHide Props Config" to try hide the booloader-state and I hope enable AI with unlocked bootloader:
https://forum.xda-developers.com/showpost.php?p=83972471&postcount=4626

@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2
What Im hoping is that bluetooth will work. Because when I flash the dev image earlier and used the ↑ ↑ ← ← method and choose skip setup, bluetooth has not been working. Can not find any bluetooth devices when i search for them. The same problem on 2 different devices.
So now Im trying this method right now to see if it works better.
If it does not work I need to try the the none-developer image instead.
However this method seems to bootloop.. Im not sure whats happening.. I see the nvidia logo and then reboots again and same..
---------- Post added at 08:31 PM ---------- Previous post was at 08:26 PM ----------
The steps I took:
I boot to TWRP first through bootloader.
Format and wipe all partitions basically making it totally fresh.
Then I boot to bootloader and run the flash-all without the reboot continue.
Then I boot back to TWRP and mount system.
Then pull the file and append the line, then push it back.
Then reboot to system.
Now bootloop...
just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..

cHECKjAM said:
@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2
just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..
Click to expand...
Click to collapse
-Remove "ro.setupwizard.mode=DISABLED" from (end of file: system/build.prop).
-Try to bootup completely and setup ethernet with internet connection. then power off device.
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
I hope it works.

If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code:
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.
- Flash vbmeta_skip.img:
Code:
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.
If two steps does not works too! you have to: Root and install Magisk

mrhamed said:
If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code:
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.
- Flash vbmeta_skip.img:
Code:
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.
If two steps does not works too! you have to: Root and install Magisk
Click to expand...
Click to collapse
I dont get any method working..
The other thread with the "how to root" is lacking so much details and steps I have no idea how it is supposed to be done..
So I tried flashing the totally default dev image 8.2 . Everything boots and goes in to the setup mode
From there if I unplug ethernet I cant go anywhere.. I then reboot to bootloader and from there boot in to twrp.
Mount the system and modify the prop file as you said. then reboot to system again. Still cant bypass setup.
I also tried the exact same with flashing the vb skip image instead of default vbmeta
same result..
And it is painfully long process and every new try is a pain.
Can you please buddy please:
Write a step by step n exactly how to from scratch:
Flash 8.2 image + root + bypass google setup entirely..

Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.

mrhamed said:
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
Click to expand...
Click to collapse
Hey buddy..
I have not had time until now to try this again.. My shield has been semi-bricked since last try and have not been able to use it until now. So maybe can look in to getting this working during the vacation.
Have you gotten any better idea on how exactly to make this work? I followed all your steps last time and failed twice..

Is there anyone out there except for @mrhamed that has got this method working?
If so please share any real tutorial/steps/guide or whatever that can help.. thanks

mrhamed said:
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
Click to expand...
Click to collapse
Are you MIA?

EDIT: oops. wrong thread.

8.2.3 - 2019 Pro here, removing ethernet works like a charm.

LifelessLife said:
8.2.3 - 2019 Pro here, removing ethernet works like a charm.
Click to expand...
Click to collapse
Maybe you can explain a bit more?

mrhamed said:
*** You should unlock bootloader ***
-In fastboot mode:
Code:
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! F.ck the spy.
For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana
Click to expand...
Click to collapse
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.

jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
I think 9.0.0 broke alot of things we have been taking for granted. if not using a Google account is that important to you, best to go ahead and revert back for now.

jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system

mrhamed said:
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
Click to expand...
Click to collapse
Just pulled the build.prop again and the setupwizard was still disabled. Did a reboot and still requires Google sign in. Guess its back to 8.2.3.

I have no more idea and it should works!
add more options to build props:
ro.setupwizard.network_required=false
ro.setupwizard.wifi_required=false
ro.setupwizard.enable_bypass=1
ro.setupwizard.mode=DISABLED

How To Guide [GUIDE] Change Splash screen for this phone!

NOTE: I am not responsible for any bricked devices. DO THIS AT YOUR OWN RISK!
Click to expand...
Click to collapse
I recently changed my splash screen logo from samsung to a custom one i made in pixlr. Its looks coool. A video is attached below.
REQUIREMENTS:
- ROOTED A32 4G
- usb c cable (to connect to pc)
- windows PC (for zipping and etc.)
- ADB installed on your pc. (For running shell commands) [OR YOU COULD USE SOME TERMINAL EMULATOR]
If your doing this on your phone just follow along, i included seperate commands.
STEPS:
1. Download attached up_param.bin (i extracted this from android 11 firmware. it shld work with fine with 12 they are same. Since downloading whole firmware takes alot of time)
2. Install 7zip if you already didn't from here.
3. Make a working directory anywhere
4. Use 7 zip to extract up_param.bin to a folder.
After extracting this is what you should see
{
"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"
}
These are all the images!
5. modify files as you like. (MAKE SURE THE DIMENSIONS ARE THE SAME. AND DO NOT REMOVE ANY IMAGE IT COULD BRICK)
NOTE: DO NOT TOUCH DOWNLOAD MODE IMAGES. if you f**k them up you will never be able to get into download mode again
You can replace boot_warning.jpg, logo.jpg (main file responsible logo), letter.jpg (the logo that shows for a split second), svb_orange.jpg (boot loader unlock warning)
6. select all images -> right click -> add to archive.
7. set it to tar.
8. set compression method to GNU.
This is what it should look like
9. Click on OK.
10. Now connect your A32 to the PC. (enable USB debugging)
11. Copy over the tar file that was generated by 7zip to anywhere. i am gonna assume we placed it in the internal storage (/sdcard/)
12. Run the following commands.
NOTE: I am editing the original thread since i checked in up param file of my new a13 fw and found new file. Its for if the battery temperature is too high. if you modify the up param from a11 fw and flash that it may not exist and the phone will boot loop if it wants to display the menu...
iM UPLOADING A13 stock up_param HERE FROM A325FXXU2CVK3.
Uploaded as up_param-a13.bin
adb shell (Phone users skip this.)
su
(Grant su permission if the popup comes up).
Then run
ls -l /dev/block/platform/****/by-name
After you get a long output. Search for up_param.
(We all have the same phone but just in case some people with diff samsung mtk phones come here).
now we just have to run 2 more commands and we are done!
Taking backups incase something goes wrong.
(People with different phones replace your up_param partition name here.)
dd if=/dev/block/mmcblk0p35 of=/sdcard/backup-param.bin
Now flashing our new modified up_param with new images
dd if=/sdcard/filename.tar of=/dev/block/mmcblk0p35
WE ARE DONE! now reboot and enjoy the new logo!

CREDITS:
- Orignal post: here.
Also video attached below

Captain_cookie_200 said:
I recently changed my splash screen logo from samsung to a custom one i made in pixlr. Its looks coool. A video is attached below.
REQUIREMENTS:
- ROOTED A32 4G
- usb c cable (to connect to pc)
- windows PC (for zipping and etc.)
- ADB installed on your pc. (For running shell commands) [OR YOU COULD USE SOME TERMINAL EMULATOR]
If your doing this on your phone just follow along, i included seperate commands.
STEPS:
1. Download attached up_param.bin (i extracted this from android 11 firmware. it shld work with fine with 12 they are same. Since downloading whole firmware takes alot of time)
2. Install 7zip if you already didn't from here.
3. Make a working directory anywhere
4. Use 7 zip to extract up_param.bin to a folder.
After extracting this is what you should see
View attachment 5775661
These are all the images!
5. modify files as you like. (MAKE SURE THE DIMENSIONS ARE THE SAME. AND DO NOT REMOVE ANY IMAGE IT COULD BRICK)
NOTE: DO NOT TOUCH DOWNLOAD MODE IMAGES. if you f**k them up you will never be able to get into download mode again
You can replace boot_warning.jpg, logo.jpg (main file responsible logo), letter.jpg (the logo that shows for a split second), svb_orange.jpg (boot loader unlock warning)
6. select all images -> right click -> add to archive.
View attachment 5775663
7. set it to tar.
8. set compression method to GNU.
This is what it should look like
View attachment 5775665
9. Click on OK.
10. Now connect your A32 to the PC. (enable USB debugging)
11. Copy over the tar file that was generated by 7zip to anywhere. i am gonna assume we placed it in the internal storage (/sdcard/)
12. Run the following commands.
adb shell (Phone users skip this.)
su
(Grant su permission if the popup comes up).
Then run
ls -l /dev/block/platform/****/by-name
After you get a long output. Search for up_param.
View attachment 5775673
(We all have the same phone but just in case some people with diff samsung mtk phones come here).
now we just have to run 2 more commands and we are done!
Taking backups incase something goes wrong.
(People with different phones replace your up_param partition name here.)
dd if=/dev/block/mmcblk0p35 of=/sdcard/backup-param.bin
Now flashing our new modified up_param with new images
dd if=/sdcard/filename.tar of=/dev/mmcblk0p35
WE ARE DONE! now reboot and enjoy the new logo!
Click to expand...
Click to collapse
Very good thanks

kilam9900 said:
Very good thanks
Click to expand...
Click to collapse
hehe your welcome. hope it works epikly for you. (if you do it)

Captain_cookie_200 said:
hehe your welcome. hope it works epikly for you. (if you do it)
Click to expand...
Click to collapse
I will do it but I am scare to f**k size so I will do it on PC

kilam9900 said:
I will do it but I am scare to f**k size so I will do it on PC
Click to expand...
Click to collapse
oh lmao. if you do end up breaking your up_param it would still boot fine. but downlaod mode would break until a proper up param file is flashed again.

Captain_cookie_200 said:
oh lmao. if you do end up breaking your up_param it would still boot fine. but downlaod mode would break until a proper up param file is flashed again.
Click to expand...
Click to collapse
I'm reassured

I recommend using dd oflag=direct,sync if=/sdcard/filename.tar of=/dev/block/mmcblk[...] otherwise you may get all sorts of problems, even a bricked phone, especially if you reboot straightaway after flashing. Inside Android all data transfers are cached, it's not the Download tool where everything is synchronous (or at least flushed before reboot).

uluruman said:
I recommend using dd oflag=direct,sync if=/sdcard/filename.tar of=/dev/block/mmcblk[...] otherwise you may get all sorts of problems, even a bricked phone, especially if you reboot straightaway after flashing. Inside Android all data transfers are cached, it's not the Download tool where everything is synchronous (or at least flushed before reboot).
Click to expand...
Click to collapse
i didnt have to deal with anything like that. i did multiple flashes atleast 15 flashes using dd to the up param partition and i did not brick my phone at all. worse you could get is a black screen while booting. and your download mode would not work. but its easy to get it back just flash the up param file again the one that was backed up. although thanks for the info. i did this using recovery. could also be done while booted into android itself

Captain_cookie_200 said:
i didnt have to deal with anything like that. i did multiple flashes atleast 15 flashes using dd to the up param partition and i did not brick my phone at all. worse you could get is a black screen while booting. and your download mode would not work. but its easy to get it back just flash the up param file again the one that was backed up. although thanks for the info. i did this using recovery. could also be done while booted into android itself
Click to expand...
Click to collapse
I ran into this problem when rebooted the phone using the "reboot" shell command right after the "dd". When rebooting from the UI all caches are flushed, of course, but the "reboot" command is a bit crude method I suppose (although in Linux it's always absolutely graceful). Anyway, the logo screen looked absolutely fine, and the system booted okay, but when I tried to enter Download I got the black screen and the boot loop, and no way to either enter Download, Recovery or boot the system. In fact the only thing that still worked was forced reboot (Power + Vol Down). I was able to get out of this situation by connecting the charger and holding Power + Vol Down to force the phone into the off state, then I connected it to the PC and tried entering the Download mode once again, and this time it worked although the graphics was all messed up.

uluruman said:
I ran into this problem when rebooted the phone using the "reboot" shell command right after the "dd". When rebooting from the UI all caches are flushed, of course, but the "reboot" command is a bit crude method I suppose (although in Linux it's always absolutely graceful). Anyway, the logo screen looked absolutely fine, and the system booted okay, but when I tried to enter Download I got the black screen and the boot loop, and no way to either enter Download, Recovery or boot the system. In fact the only thing that still worked was forced reboot (Power + Vol Down). I was able to get out of this situation by connecting the charger and holding Power + Vol Down to force the phone into the off state, then I connected it to the PC and tried entering the Download mode once again, and this time it worked although the graphics was all messed up.
Click to expand...
Click to collapse
did you touch the download mode images in any way? i dont know why this happened for you. i guess i did press the reboot button instead of using the command. since i do it on first fw reflash and i flash a gsi immdiiately afterwards... download shouldnt have died like that tho. i messed with my down load images completely. i competely replaced them with diff new images that are diff sizes too. i dont know why this is happening for you. my download works fine. although it reverts to the old download image somehow once on downloading mode. for confirmations it does show my edited images.

Captain_cookie_200 said:
did you touch the download mode images in any way? i dont know why this happened for you. i guess i did press the reboot button instead of using the command. since i do it on first fw reflash and i flash a gsi immdiiately afterwards... download shouldnt have died like that tho. i messed with my down load images completely. i competely replaced them with diff new images that are diff sizes too. i dont know why this is happening for you. my download works fine. although it reverts to the old download image somehow once on downloading mode. for confirmations it does show my edited images.
Click to expand...
Click to collapse
I suppose your Download still worked fine because the up_param tar archive was complete and not corrupt, and even image files were normal and not chopped in the middle of the data stream. In my case it was the latter, when cache is not flushed the data stream is just cut, and such a simple program as Download obviously cannot handle broken files. The Download tool itself is kept in the separate "debugger" flash memory, I guess it has the default graphics too which can be displayed if no graphics is found in up_param.

uluruman said:
I suppose your Download still worked fine because the up_param tar archive was complete and not corrupt, and even image files were normal and not chopped in the middle of the data stream. In my case it was the latter, when cache is not flushed the data stream is just cut, and such a simple program as Download obviously cannot handle broken files.
Click to expand...
Click to collapse
oh i see. thanks for telling about this. it would help people alot from preventing to brick their phone from bricking

Captain_cookie_200 said:
oh i see. thanks for telling about this. it would help people alot from preventing to brick their phone from bricking
Click to expand...
Click to collapse
Correction: 'dd oflag=direct,sync' does not work in Android shell, the working alternative is 'dd conv=fsync'

Captain_cookie_200 said:
I recently changed my splash screen logo from samsung to a custom one i made in pixlr. Its looks coool. A video is attached below.
REQUIREMENTS:
- ROOTED A32 4G
- usb c cable (to connect to pc)
- windows PC (for zipping and etc.)
- ADB installed on your pc. (For running shell commands) [OR YOU COULD USE SOME TERMINAL EMULATOR]
If your doing this on your phone just follow along, i included seperate commands.
STEPS:
1. Download attached up_param.bin (i extracted this from android 11 firmware. it shld work with fine with 12 they are same. Since downloading whole firmware takes alot of time)
2. Install 7zip if you already didn't from here.
3. Make a working directory anywhere
4. Use 7 zip to extract up_param.bin to a folder.
After extracting this is what you should see
View attachment 5775661
These are all the images!
5. modify files as you like. (MAKE SURE THE DIMENSIONS ARE THE SAME. AND DO NOT REMOVE ANY IMAGE IT COULD BRICK)
NOTE: DO NOT TOUCH DOWNLOAD MODE IMAGES. if you f**k them up you will never be able to get into download mode again
You can replace boot_warning.jpg, logo.jpg (main file responsible logo), letter.jpg (the logo that shows for a split second), svb_orange.jpg (boot loader unlock warning)
6. select all images -> right click -> add to archive.
View attachment 5775663
7. set it to tar.
8. set compression method to GNU.
This is what it should look like
View attachment 5775665
9. Click on OK.
10. Now connect your A32 to the PC. (enable USB debugging)
11. Copy over the tar file that was generated by 7zip to anywhere. i am gonna assume we placed it in the internal storage (/sdcard/)
12. Run the following commands.
NOTE: I am editing the original thread since i checked in up param file of my new a13 fw and found new file. Its for if the battery temperature is too high. if you modify the up param from a11 fw and flash that it may not exist and the phone will boot loop if it wants to display the menu...
iM UPLOADING A13 stock up_param HERE FROM A325FXXU2CVK3.
Uploaded as up_param-a13.bin
adb shell (Phone users skip this.)
su
(Grant su permission if the popup comes up).
Then run
ls -l /dev/block/platform/****/by-name
After you get a long output. Search for up_param.
View attachment 5775673
(We all have the same phone but just in case some people with diff samsung mtk phones come here).
now we just have to run 2 more commands and we are done!
Taking backups incase something goes wrong.
(People with different phones replace your up_param partition name here.)
dd if=/dev/block/mmcblk0p35 of=/sdcard/backup-param.bin
Now flashing our new modified up_param with new images
dd if=/sdcard/filename.tar of=/dev/block/mmcblk0p35
WE ARE DONE! now reboot and enjoy the new logo!
Click to expand...
Click to collapse
NOTE: I am editing the original thread since i checked in up param file of my new a13 fw and found new file. Its for if the battery temperature is too high. if you modify the up param from a11 fw and flash that it may not exist and the phone will boot loop if it wants to display the menu...
iM UPLOADING A13 stock up_param HERE FROM A325FXXU2CVK3.
Uploaded in orignal thread as up_param-a13.bin

I made it and works perfectly, thanks for the tutorial!!

ApiYoshi said:
I made it and works perfectly, thanks for the tutorial!!
Click to expand...
Click to collapse
glad to hear thatt. and your welcome

how to apply this on snapdragon devices
they don't have up_parem.bin file ??

elswerky said:
how to apply this on snapdragon devices
they don't have up_parem.bin file ??
Click to expand...
Click to collapse
they do? check inside bl file of your firmware. Or using the partition list command should show it

Captain_cookie_200 said:
they do? check inside bl file of your firmware. Or using the partition list command should show it
Click to expand...
Click to collapse
Bl file itself doesn't have up_parem.bin file
Unlike exynis devices which have it
And am.nit familiar with partition as you said if you can helping me
Talking about tab S6 w8th android 12 , OneUi 4.1