Database Info

initlogo.rle: display an image on boot

You can display a "splash" screen of sorts upon boot. You just have to have a file named initlogo.rle in your root directory. The trick is that the root directory is overwritten each time you boot with the contents of your boot image (mtd2). There are instructions elsewhere on the forums for updating this image.
You can prove to yourself that this works by just copying logo.rle to initlogo.rle in your updated boot image and you will see the "G1" screen twice.
The hurdle I'm running into is generating my own images. There is a program called to565 that takes in an image and spits out the resulting image in the appropriate format (give it the -r flag to generate an rle) [edit, correct flag is -rle]. However, everything I generate with this just looks like random colored bars when I boot up (and sometimes at the bottom of the screen I see part of whatever was left in the framebuffer when I shut down). Supposedly to565 takes in a raw rgb888 file, and perhaps I'm not generating those properly. I tried saving to "raw image" from gimp but so far everything is just different variations on colored bars.
I may give up at this point, but I thought others might be interesting in picking up where I left off.

Huh. Interesting. I'll see if I can give it a whirl. Thanks for posting the info you've found so far

I took a quick look at the source of that to565 program. It looks like you need to use -rle instead of just -r. Did you try that?

JesusFreke said:
I took a quick look at the source of that to565 program. It looks like you need to use -rle instead of just -r. Did you try that?
Click to expand...
Click to collapse
You sir, are correct! I just did it with -rle and it works.

How to create a boot image:
1. put a properly encoded initlogo.rle in root directory
2. insert this line in init.rc in the boot: section (optional, this disables the stock android boot animation)
Code:
setprop debug.sf.nobootanimation 1
3. wrap it all up and flash it to mtd2
Attached:
1. A boot image with these changes made. To try it on your phone, first back up your mtd2 image (the boot image). Type the following in a root shell to back it up to your sdcard:
Code:
cat /dev/mtd/mtd2 > /sdcard/mtd2.img
Then, unzip boot-rc29-customlogo.img.zip it and stick it on your sdcard and type the following in a root shell:
Code:
cat /dev/zero >> /dev/mtd/mtd2
flash_image boot /sdcard/boot-rc29-customlogo.img
(when you do the cat, it will tell you "write: No space left on device," which is fine)
To restore your original boot image, do the cat and then flash_image your mtd2.img backup.
2. Samples of the raw image as well as the rle encoded version.
3. A nifty photo of this working on 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"
}

WOW awesome!! great job will test this out when i get back from the airport

i couldn't wait so i did it works perfectly. i just can't get rid of the first boot .img.(i see the instruction but i need further help) if this helps i have a vista 64 but, I'm also running VM to any operating system.

humble said:
i couldn't wait so i did it works perfectly. i just can't get rid of the first boot .img.(i see the instruction but i need further help) if this helps i have a vista 64 but, I'm also running VM to any operating system.
Click to expand...
Click to collapse
Yeah, actually I haven't found a way to get rid of the G1 logo on boot. If you change logo.rle on the root filesystem, it still shows that image. I'll post a longer guide to generating your own boot.img later tonight (although I posted a bunch of it in another thread already). You could always create your own boot.img and replace logo.rle to prove to yourself that it doesn't change that initial logo... but I've tried it. It must be somewhere else (including, perhaps, some on-phone memory that we can't access).

hmmm so i've done this correctly since the boot image works...however i no longer have WIFI access. Does anyone knoe whats going on? under settings it keeps saying turning wifi ON... but it doesnt.
EDIT: So i reflashed the original backup img and now its fine. I wonder where i went wrong?

mack said:
hmmm so i've done this correctly since the boot image works...however i no longer have WIFI access. Does anyone knoe whats going on? under settings it keeps saying turning wifi ON... but it doesnt.
Click to expand...
Click to collapse
Did you use the boot.img I posted or one of your own? I'm not having any trouble with wifi, and I'm booted with that one. Do you see anything in dmesg about wifi?
Edit: also, it looks like JesusFreke had some issues with wifi not working when he was doing custom boot images. Dunno the details but maybe it's related.

thanks alansj (sorry i miss read). and my wifi still works

alansj said:
Did you use the boot.img I posted or one of your own? I'm not having any trouble with wifi, and I'm booted with that one. Do you see anything in dmesg about wifi?
Edit: also, it looks like JesusFreke had some issues with wifi not working when he was doing custom boot images. Dunno the details but maybe it's related.
Click to expand...
Click to collapse
I used your img that you posted with the hackdroid...LOVED it by the way =)
Could it be i'm on RC19 firmware? I'm reading jesusfreke's post but i'm fairly new to the linux thing so i'm having trouble understanding.
anyway i guess i'll just stick to stock until something new comes a long...
Thanks Alansj

mack said:
Could it be i'm on RC19 firmware?
Click to expand...
Click to collapse
Good guess. You could first apply the RC29 via sdcard and then flash the boot image.
To apply RC29, download this file, put it on your sdcard, name it update.zip, then reboot your phone while holding down power+home and when you get the recovery screen press alt+L then alt+s.

will this work with 30

jriley60 said:
will this work with 30
Click to expand...
Click to collapse
The general process will work, but the boot image I posted is based on rc29. The two things in the boot img are a kernel and a ramdisk (which includes a few of the basic system files). I don't think there was a kernel update in rc30, but I think there were updates to init.rc and possibly adbd (haven't checked). So, flashing with that boot.img I posted would undo the changes in those files done by rc30.
The better approach would be to take the boot.img from the full rc30 release, add your own initlogo.rle, and reflash from that.
I will now go and write a more detailed tutorial on how to edit boot.img

that would be awesome. Thank you!

Kinda off-topic, but where did you get the font that you used in the logo? I'd like to make my own, and I was wondering if I could use it...

amgupt01 said:
Kinda off-topic, but where did you get the font that you used in the logo? I'd like to make my own, and I was wondering if I could use it...
Click to expand...
Click to collapse
I just pixel-edited the logo from the android site (had to invent a couple of characters)... no font.

jriley60 said:
that would be awesome. Thank you!
Click to expand...
Click to collapse
I just posted it here

alansj said:
I just pixel-edited the logo from the android site (had to invent a couple of characters)... no font.
Click to expand...
Click to collapse
Good work, man! Someone is actually working on the android logo font here: http://androidcommunity.com/forums/f37/new-android-ttf-logo-font-ver-1-0-a-6537/#post68847
Just FYI.

[GUIDE] How to do a FULL low level backup of your Android Device

This Guide is simple and is straight the point, but is helpful and may come in handy for those who experience a hard-bricked phone or missing file in your phone like I did. Basically, nandroid is not a FULL backup, it only backs up your system, data, sd-secure, and boot partitions. A low level backup does every partition on your phone (even low level ones) and puts it on your sdcard. Now note that a full backup can create quite a large backup size total.
Credits to XDA user closeone for teaching me how to do this:
In a terminal emulator app perform this command in your terminal:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img
(Quoted from closeone)
That command is a disk to file command with the parameter if (Input file) of mmcblk0 (the entire device) and the parameter of (output file) to the SD Card as a file called mmcblk0.img
Click to expand...
Click to collapse
the "0" basically says "the whole phone" and as such backs it up. This will back up your radios, system, data, and every other partition you didnt even know existed in your phone.
I have been around android for a long time, but I did not know this, I hope this helps someone.

A couple of things you should mention: you're not responsible for any issues which may or may not arise or user errors.
Secondly, if the if= and the of= get reversed, well it would overwrite the phone's info, at least to the point DD can't run or encounters an error and stops.
Sent from my LG-P999 using xda premium

How do you restore this back to the device?
and if this restores without an issue, this might be a solution to the infamous ICS Brick bug in Samsung Galaxy Note and Galaxy SII.

Reverse the if= and the of= "if" is input file "of" output file. Think of this as being similar to making an ISO of a CD or DVD. And depending on what utilities are available and how the device is recognized, it could be a solution. If the device is recognized by a program which can flash .img files, for example for my phone we have nvflash which can. CWM can also be scripted to write them.
Sent from my LG-P999 using xda premium

Волк said:
Reverse the if= and the of= "if" is input file "of" output file. Think of this as being similar to making an ISO of a CD or DVD. And depending on what utilities are available and how the device is recognized, it could be a solution. If the device is recognized by a program which can flash .img files, for example for my phone we have nvflash which can. CWM can also be scripted to write them.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I am not sure about the reverse... a working file system needs to be remounted as read+write before it can be overwritten. I am guessing this COULD be done in recovery mode using adb shell but still quite risky. If anything, I have a feeling it can hardbrick the device unless the boot and recovery partitions are left untouched. Comments?

Thank you, this is what I was looking for!
I want to encrypt my device, thus I won´t be able to backup with Clockworkmod afterwards.
Does this command also backup /sdcard1? That would be odd somehow, because you cannot write the backup to a partition you are just about to backup itself...
How can I issue this command with adb?
I would like to connect my device to my Linux workstation, use adb to issue the backup command and write the backup to my local harddrive. How could I do that with adb?
Best regards

papperlapapp said:
Thank you, this is what I was looking for!
I want to encrypt my device, thus I won´t be able to backup with Clockworkmod afterwards.
Does this command also backup /sdcard1? That would be odd somehow, because you cannot write the backup to a partition you are just about to backup itself...
How can I issue this command with adb?
I would like to connect my device to my Linux workstation, use adb to issue the backup command and write the backup to my local harddrive. How could I do that with adb?
Best regards
Click to expand...
Click to collapse
Wow talk about a blast from the past lol. Honestly man I left the dev scene for about a good year and some months up until.... two days ago lol, so I'm rusty as all get out. I'd have to get back on my stuff to answer it for you to be honest. Even at the time of my creating this, I didn't necessarily KNOW how to do it, closeone just taught me how and I felt like this could have possibly saved someone from a potentially disastrous encounter, I wasn't knowledgeable enough to tell you much is what I'm trying to say.

I have a generic rooted tablet and im unable to find a custom recovery and i want to send my rom to a dev who can or want to made cwm/twrp for me, so this is my question: is it a safe way to copy my actual rom? Im asking that cuz im scared to brick my tablet. Thanks

acuicultor said:
I have a generic rooted tablet and im unable to find a custom recovery and i want to send my rom to a dev who can or want to made cwm/twrp for me, so this is my question: is it a safe way to copy my actual rom? Im asking that cuz im scared to brick my tablet. Thanks
Click to expand...
Click to collapse
Is the tablet rooted? I might be able to look at it, give me a PM.
Sent from my HTC One using xda app-developers app

{
"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 the specs. Thanks

Is this possible to do without a rooted phone? What about via adb shell or as an external device?

http://forum.xda-developers.com/showthread.php?t=1818321 showed more advance function for low level backup.

would you please explain how you reach the point where you can run the dd command?

awambawamb said:
would you please explain how you reach the point where you can run the dd command?
Click to expand...
Click to collapse
dd is a Linux command, so you should do adb shell from your Windows Command Prompt. Obviously abd should be installed beforehand.
http://www.theandroidsoul.com/how-to-install-adb-on-windows-full-guide/
Well, I am beginner, if this is not what you asked, sorry in advance

I need mmcblk0.img from someone please for htc m8s if anyone has ir can get a hold of cheers ?

Do I have the "correct" nvflash blob files?

I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
{
"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'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, it doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and if I find I have a bad nvflash blob file).
For other's info, I'd originally asked about re-running the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set. In preparation for recreating one, I moved the /sdcard/AndroidRoot folder to another location. I happened to reboot and noticed the AndroidRoot folder and its contents are automatically recreated upon rebooting. So for these files, there's no need to re-run the fastboot command for another set.
I did notice one "issue" viewing the /sdcard/AndroidRoot folder in Windows 7 after the initial reboot. While they display fine via my TF300T's File Manager, it took either disconnecting/reconnecting my usb cable or rebooting one more time for them to display correctly in Windows 7.
I still plan on re-running nvflash to create a new bricksafe.img, factory-config.img, and unlock-token.img set just to be extra safe.

wha2do said:
I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
I'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and I find I have a bad nvflash blob file).
Can I rerun the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set? While I'm at it, I figure I should be able to rerun nvflash and create a new bricksafe.img, factory-config.img, and unlock-token.img... Is that possible and does it make sense?
Thanks!
Click to expand...
Click to collapse
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.

totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
Thanks for the confirmation. I dislike relying on an unverified backup only to find out too late that it's not valid or usable! And out of curiosity, you went through a recovery successfully? It'd be great if you had a link to the thread/post you followed.

I had missed one step after upgrading the jb bootloader (didnt force shutdown after upgrade, just let it load) and were stuck with official jb with no root or recovery, so i tried to use nv flash and messed up even more , post 3 in this thread helped me get the bootloader to work so I cound install TWRP again using fastboot.
I do not recommend testing it "just for fun" but it worked for me. Search for "nvflash restore" if you have any problems.

totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
I'm curious about your sizes matching mine; more specifically my unlock-token.img file size matching yours. Maybe fine if you used your unlock-token.img file when you did your recovery. If didn't use, might want to (if you still can) go back and recreate it and compare with your original...see below why.
Being OCD on backups, I created a new bricksafe.img, factory-config.img, and unlock-token.img and compared the files. I was a bit surprised to see factory-config.img and unlock-token.img were not exact copies of the original set created. Factory-config.img had some bits that varied, but was mostly the same. I'm figuring it's something "internal" as I haven't changed anything on my table between runs and is fine...
But seeing a large size change between the two unlock-token.img files, I went back through my logs, etc. Lo and behold, I had a typo and hadn't changed the partition from 14 to 7! So I had made duplicate backups of the factory-config partition by accident. The actual file size is 8,192 KB and not 5,120 KB.
That could have been a real problem down the road if ever I need to recover (assuming this file is vital to the particular recovery procedure). So if nothing else...the lesson to learn is always double check what you've done to make sure!

i have Found MSM8994DownloadTool with rawprogram0 . but not for Gflex2 ,

Hello
i have Found MSM8994DownloadTool with Rawprogram0 for MSM8994 .
but its for another model i not exactly remember which model it is ,
i have attach Tool with post , if some one have good knowledge and experience and he can convert and make working for Gflex2
ill wait ,
https://mega.nz/#!lQBUCSTZ!Xty3MTICufa5Tj-vnQUdtJIDK2lFSPIxodKOwzxaawQ

well, Its the same as OP2, same problem.... same chipset.
check that, maybe we can fix it very easily
{
"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"
}
Im working on it

tomorrow I have news.
Almost done Rawprogram0.xml to fix download mode.
The second problem will be if it flash or not...
Im going to sleep, tomorrow I finish

Man, just wanted to say, I appreciate your efforts @pelelademadera. I haven't been able to make any progress on this matter. Hope you do.

pelelademadera said:
tomorrow I have news.
Almost done Rawprogram0.xml to fix download mode.
The second problem will be if it flash or not...
Im going to sleep, tomorrow I finish
Click to expand...
Click to collapse
Thats Good news im waiting .please share news

mauchito said:
Man, just wanted to say, I appreciate your efforts @pelelademadera. I haven't been able to make any progress on this matter. Hope you do.
Click to expand...
Click to collapse
well, rawprogram0 is done,
But I cannot flash it, maybe patch0, or rawprogram2 problem, IDK I have headache of reading and editing.
The log error was fixed, and rawprogram was correct, at least every partition, mabe incorrect in primaryGPT and backupGPT, someone with a working phone maybe can check it.
When my headache gone, I continue editing patch0.
in my opinion the problem is not the flasher and files, the problem are prog_emmc_firehose_8994_lite.mbn, but not 100% sure.
the file I share is a rar file, with correct files for ATT h950, so, if your version is not an h950, CHECK THAT PLEASE BEFORE.
and is very probable that system size and userdata size does not match, so rawprogram0 must be checked for the other versions
https://drive.google.com/folderview?id=0B8KKKARP5vh4enpzUThnR19wQU0&usp=sharing
when finish upload, the file will be there... 2 -3 minutes and there is

If someone knows someone, with a working phone, I need a few partitions backup.
I need someone with a rooted phone, that can share to me or here ddr.img.
its /dev/block/mmcblk0p29 so backup with dd.
adb shell
su
dd if=/dev/block/mmcblk0p29 of= "somewere to save"
upload and share, I have the size and everything, but not the img to use

pelelademadera said:
If someone knows someone, with a working phone, I need a few partitions backup.
I need someone with a rooted phone, that can share to me or here ddr.img.
its /dev/block/mmcblk0p29 so backup with dd.
adb shell
su
dd if=/dev/block/mmcblk0p29 of= "somewere to save"
upload and share, I have the size and everything, but not the img to use
Click to expand...
Click to collapse
I'll try to do it later today (955 - 15c), how many space is required to save this partition?

Lg g flex2 h950
Hi
There was lollipop version 5.0.2 in my phone at the time of purchase. After the upgradation with android version of H95011z, i got a problem with my phone ,now the phone always shows the below massage all the time...
***Secure booting Error !
Error code: 1006
And also USB is not working and download mood is not working , factory hard reset is not working.
Please help me in this issue. I am really waiting for your help.
Thanks for your cooperation.

i tried:
dd if=/dev/block/mmcblk0p29 of= "/sdcard/mmcblk0p29"
and
dd if=/dev/block/mmcblk0p29 of= "/storage/external_SD/mmcblk0p29"
both returns to # almost immediately but there is no file saved, what am I doing wrong?

lol, try this:
dd if=/dev/block/mmcblk0p29 of=/data/media/0/DDR_mmcblk0p29.img
but I found this tool earlier (some months ago) and tryed to get working with flex 2, mine is a working device, and can't test by me, but shared in this forum, and no success
this is originally for OnePlus 2
I think better way, if we found the emmc pinouts on the pcb
Currently know, two necessary pins not in the pcb (data0, clk) but someone found the clk pinout on the pcb other side.

stars2 said:
lol, try this:
dd if=/dev/block/mmcblk0p29 of=/data/media/0/DDR_mmcblk0p29.img
Click to expand...
Click to collapse
same problem, it goes back to # in a second but no file saved.
any ideas @pelelademadera ?

no "" in output
Thanks so much

pelelademadera said:
no "" in output
Thanks so much
Click to expand...
Click to collapse
dd if=/dev/block/mmcblk0p29 of="/sdcard/mmcblk0p29"
dd if=/dev/block/mmcblk0p29 of="/sdcard/mmcblk0p29.img"
dd if=/dev/block/mmcblk0p29 of=/sdcard/mmcblk0p29.img
dd if=/dev/block/mmcblk0p29 of="/storage/external_SD/mmcblk0p29"
dd if=/dev/block/mmcblk0p29 of="/storage/external_SD/mmcblk0p29.img"
dd if=/dev/block/mmcblk0p29 of=/storage/external_SD/mmcblk0p29.img
dd if=/dev/block/mmcblk0p29 of=/data/media/0/DDR_mmcblk0p29.img
dd if=/dev/block/mmcblk0p29 of="/data/media/0/DDR_mmcblk0p29.img"
none of above worked, maybe is a problem of path?
what I do is:
Send_Command.exe \\.\COM4
#id (just to be sure)
#dd etc. etc.
#LEAVE
Am I doing wrong?

Which file you need?

superdioz said:
dd if=/dev/block/mmcblk0p29 of="/sdcard/mmcblk0p29"
dd if=/dev/block/mmcblk0p29 of="/sdcard/mmcblk0p29.img"
dd if=/dev/block/mmcblk0p29 of=/sdcard/mmcblk0p29.img
dd if=/dev/block/mmcblk0p29 of="/storage/external_SD/mmcblk0p29"
dd if=/dev/block/mmcblk0p29 of="/storage/external_SD/mmcblk0p29.img"
dd if=/dev/block/mmcblk0p29 of=/storage/external_SD/mmcblk0p29.img
dd if=/dev/block/mmcblk0p29 of=/data/media/0/DDR_mmcblk0p29.img
dd if=/dev/block/mmcblk0p29 of="/data/media/0/DDR_mmcblk0p29.img"
none of above worked, maybe is a problem of path?
what I do is:
Send_Command.exe \\.\COM4
#id (just to be sure)
#dd etc. etc.
#LEAVE
Am I doing wrong?
Click to expand...
Click to collapse
This command is correct:
dd if=/dev/block/mmcblk0p29 of=/data/media/0/DDR_mmcblk0p29.img
But you need to do it from adb shell, not from download mode, and with superuser acces
Enviado desde mi Lead4 mediante Tapatalk

pelelademadera said:
But you need to do it from adb shell, not from download mode, and with superuser acces
Click to expand...
Click to collapse
ok, i needed that piece of information, check the attachment and tell me if you need anything else

superdioz said:
ok, i needed that piece of information, check the attachment and tell me if you need anything else
Click to expand...
Click to collapse
Great, when I have notices, I post here
Enviado desde mi Lead4 mediante Tapatalk

I had tried your above method. the tool gave firehose error. Changed the file name to firehose8994.mbn. Then it gave Sahara error. I think we should have a Sahara.xml file also.

nothing, fails, thats a shi%&
if I send my phone to usa, I waste more money than buying a new one....
I ordered a G3 D851, when flex 2 becomes repairable, I repair it.
Too much time for me, no more locked bootloaders phones for me, thats all cause we cannot flash anything from a recovery...

How To Guide Two ways to backup TB-J706F without unlocking bootloader.

For many users, unlocking the bootloader is unacceptable, because the tablet will stop updating via OTA. However, there are ways to save important partitions without unlocking them, which can be useful in case of damage during flashing or update.
1. The first method is described here. It works, I tested it. The Read button reads the partition to a file, the Load button writes from the image file to the partition.
Disadvantages: you can't copy the whole FS of the tablet at once, you have to copy the partitions one by one.
2. The second way goes here. It works on Linux, Windows, and MacOS. I checked it on the Live CD Mint 20.2. The tablet was recognized, the partition table was read and I successfully copied one boot partition.
Disadvantages: Difficult for Windows users.
Cons: You can copy selected partitions in any combination or the whole tablet at once.
---
It is very likely that these 2 methods will work for other models of tablets as well...

Were you able to use the --skip parameter with edl?
I used --skip=super,userdata the other day but it still backed up those partition (long wait for userdata )

MrCrayon said:
Were you able to use the --skip parameter with edl?
I used --skip=super,userdata the other day but it still backed up those partition (long wait for userdata )
Click to expand...
Click to collapse
Sorry, not tried this option. Will to try later.

MrCrayon said:
Were you able to use the --skip parameter with edl?
I used --skip=super,userdata the other day but it still backed up those partition (long wait for userdata )
Click to expand...
Click to collapse
Yes, you are right. This command not works, it made backup of all partitions. I made issue for author.

f1tm0t said:
Yes, you are right. This command not works, it made backup of all partitions. I made issue for author.
Click to expand...
Click to collapse
My PR has been merged, skipping should work now.

MrCrayon said:
My PR has been merged, skipping should work now.
Click to expand...
Click to collapse
Yes, my issue is same. Can't try this just now, so sad.

Tested fixed version some days ago - now --skip option works fine. Dump of all partitions in one folder (except biggest userdata:
Spoiler: Scr
{
"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 have a question, what about userdata when it is encrypted?
How to get/set the key from the TEE?
Or are the chinese ROMs are unencrypted?
Best regards

CryptMan said:
I have a question, what about userdata when it is encrypted?
Click to expand...
Click to collapse
My userdata permanently unencrypted with no-verity-opt-encrypt. TWRP says "Decrypted with default password"

f1tm0t said:
For many users, unlocking the bootloader is unacceptable, because the tablet will stop updating via OTA. However, there are ways to save important partitions without unlocking them, which can be useful in case of damage during flashing or update.
1. The first method is described here. It works, I tested it. The Read button reads the partition to a file, the Load button writes from the image file to the partition.
Disadvantages: you can't copy the whole FS of the tablet at once, you have to copy the partitions one by one.
2. The second way goes here. It works on Linux, Windows, and MacOS. I checked it on the Live CD Mint 20.2. The tablet was recognized, the partition table was read and I successfully copied one boot partition.
Disadvantages: Difficult for Windows users.
Cons: You can copy selected partitions in any combination or the whole tablet at once.
---
It is very likely that these 2 methods will work for other models of tablets as well...
Click to expand...
Click to collapse
Hi mate,
I've used the method #1 that you linked, to take a full backup of my pad pro (thanks for sharing this, helped a lot since I really wanted to have a backup to restore to out-of-box if needed in the future).
I ended up with 91 partitions saved, but it seems a lot of these partitions would never really get touched or changed, no matter what you do to your tablet (in terms of rooting, custom roms etc), so I wanted to ask you if you could give a break down of what you think are the essential ones that would need to be restored to revert back to "out of the box". For example. I suspect a lot of the partitions house data such as serials, mac addresses, component firmware etc, etc, and such-like which would not need to be written back to the device during a restore.
I'm attaching a pdf I made showing all the partitions available through use of QFIL, if you could reference it in any advice/help with your answer I would be grateful. Thanks

The firmware writes to different sections, in particular to frp and frpinfo and others. If you want to get the tablet back to the same state as you backed it up, you must have a copy of all partitions.
For a regular backup you don't need a copy of all partitions, just the ones you need.
Besides, I recommend to have backups of those partitions that are not in the firmware in case the internal memory fails or human errors (like ticking "Erase all before download" in QFil settings)

f1tm0t said:
The firmware writes to different sections, in particular to frp and frpinfo and others. If you want to get the tablet back to the same state as you backed it up, you must have a copy of all partitions.
For a regular backup you don't need a copy of all partitions, just the ones you need.
Besides, I recommend to have backups of those partitions that are not in the firmware in case the internal memory fails or human errors (like ticking "Erase all before download" in QFil settings)
Click to expand...
Click to collapse
thanks, great explanation, i appreciate it

f1tm0t said:
1. The first method is described here. It works, I tested it. The Read button reads the partition to a file, the Load button writes from the image file to the partition.
Disadvantages: you can't copy the whole FS of the tablet at once, you have to copy the partitions one by one.
Click to expand...
Click to collapse
Hi @f1tm0t ,
i'm going to use method 1), can you please share me how to get the firehose that was mentioned in that article?
Thank you!

khanhj said:
how to get the firehose
Click to expand...
Click to collapse
You need to download rom (firmware) for your device, unzip it in separate folder and point to folder from QPST.

@f1tm0t thank you for your reply.
The reseller send it (TB-J716F) to me with custom global rom and unlock bootloader, so i follow the guide to flash stock Chinese rom and lock bootloader, it worked but widevine L3. Then i put the update.zip to push it through version 14.0.127 with locked bootloader but still widevine L3.
I'm going to backup 5 important partitions: fpinfo, persist, uefivarstore, secdata, frp, then redo all processes again.
BTW do you have any idea what is this: https://github.com/zenlty/Qualcomm-Firehose

in the extracted ROM (ZUI 12) there is 2 firehose which one should i use?

khanhj said:
which one should i use?
Click to expand...
Click to collapse
You must to use prog_firehose_ddr.elf
khanhj said:
BTW do you have any idea what is this: https://github.com/zenlty/Qualcomm-Firehose
Click to expand...
Click to collapse
Sometimes I use this with Linux: https://github.com/bkerler/edl

f1tm0t said:
You must to use prog_firehose_ddr.elf
Sometimes I use this with Linux: https://github.com/bkerler/edl
Click to expand...
Click to collapse
i tried to flash ROM ZUI 12 now i got this
Can you advise what should i do?

As my expirience say - you need unlock bootloader.

f1tm0t said:
As my expirience say - you need unlock bootloader.
Click to expand...
Click to collapse
yes but i dont know how to unlock bootloader at this state.
Thank you for your replies!
--
Edit: oh well, i flash the ROM ZUI 12 again, stick on option Reset State machine and Delete before download, my device able to boot up again to ZUI with unlocked bootloader.
I hope anyone had the same issue can fix it.