Database Info

request special splash screen

please, can someone give us hero rom splashscreen as haykuro hero rom ?
yes, new htc logo gif with little android saying bye bye

Here you have the splash
{
"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"
}
But we can't use the program "CreateG1Splash.exe" because converts it into a static file.

and how we can flash a animated splash screen then? the splash screen is fantastic!!

there's a boot.gif file in /system/media. This file is the second splash when android is starting up. I will probe to change it with this one.
It doesn't work. I've copied from roger rom to /system/media boot_configuration.xml, boot.mp3 and boot.gif but i still see the android animation

@ all,
I am on Rogers Rom and for me the above animated splash screen is working
Here are my steps:
Code:
adb remount
adb shell cp system/media/boot.gif /sdcard
adb shell rm -r system/media/boot.gif
adb push boot.gif /system/media/boot.gif
adb shell reboot
Enjoy it.
Regards
Puky70

Puky70 said:
@ all,
I am on Rogers Rom and for me the abovve animated splash screen is working
Here are my steps:
Code:
adb remount
adb shell cp system/media/boot.gif /sdcard
adb shell rm -r system/media/boot.gif
adb push boot.gif /system/media/boot.gif
adb shell reboot
in another site I found this but don't work too :
Rinominate l'immagine in boot.gif
Scaricate l'audio boot.mp3
Mettete i 2 file nella cartella tools dell'sdk
adb remount
adb push [boot.gif] /system/media
adb push [boot.mp3] /system/media
adb shell reboot
Tra le parentesi quadre mettete il percorso del file.
it's here : http://www.androidiani.com/forum/htc-magic-modding/1514-cambiare-secondo-splash-screen-magic.html
Enjoy it.
Regards
Puky70
Click to expand...
Click to collapse
this code doesn't work for me
when I put this "adb shell cp system/media/boot.gif /sdcard"
it says "cp not found"
any issue ? plz

hi,
you can find the path for cp and rm via:
> adb shell
# which cp
# which rm
for example in my rooted rogers rom:
>adb shell
# which cp
/system/xbin/cp
# which rm
/system/bin/rm
# exit
adb remount
adb shell /system/xbin/cp /system/media/boot.gif /sdcard
adb shell /system/bin/rm /system/media/boot.gif
adb push boot.gif /system/media/boot.gif
adb shell reboot
greetz

magic_munich said:
hi,
you can find the path for cp and rm via:
> adb shell
# which cp
# which rm
for example in my rooted rogers rom:
>adb shell
# which cp
/system/xbin/cp
# which rm
/system/bin/rm
# exit
adb remount
adb shell /system/xbin/cp /system/media/boot.gif /sdcard
adb shell /system/bin/rm /system/media/boot.gif
adb push boot.gif /system/media/boot.gif
adb shell reboot
greetz
Click to expand...
Click to collapse
why it's not working on my Vodafone magic?
I getting a "no such file" for the '/system/media/boot.gif'
?

the ion rom also seems to have no boot.gif in the system/media folder. i cant get a custom splash screen either...

DOH!
so my vodagroan magic with ION deffinatly cant have a custom animated boot up screen, darn it! i already changed the splash screen, would have been ace if i could have changed the boring ANDROID screen too. hopefully some smart bugger will save the day?!
JamesRead
HTC Magic
GoogleION (r2)
Rooted
OverClocked 527.3Mhz
Custom Splash
dxTop - Carbon Glow
HTC Dream
Haykuro 6.0.1H
Rooted
Overclocked 467.2Mhz
Custom Splash

I am having trouble find cp and rm. I issued #which cp and it comes up which: not found.

mack said:
I am having trouble find cp and rm. I issued #which cp and it comes up which: not found.
Click to expand...
Click to collapse
Those commands are busybox commands and you'll need to create links to the commands or try to type "busybox" before the commands :
busybox cp
busybox rm
If you installed busybox you can also create the needed links by entering : busybox --install -s , this will install the links into /data/local/bin

Has anyone found out where this is on the G1? I did a find and it came up blank.
I would love to have this on my G1, if anyone has an idea on how to do it.
Thanx!

Can anyone find this file in the Ion? I tried moving the copy of the boot splash that I saved onto my SD card into the /system/media folder using Astro and ADB, but no dice.

mack said:
I am having trouble find cp and rm. I issued #which cp and it comes up which: not found.
Click to expand...
Click to collapse
I did something similar ... all I did was grab the file from the phone to use as a backup:
Code:
adb pull /system/media/boot.gif boot.gif.orig
then put the new one in
Code:
adb push boot.gif /system/media/boot.gif
worked for me

Problems
Ok, Im not the greatest, but I like to think I have a grasp on whats going on here...
First, Im on a Dream running JACxHero 1.2 rom.
As far as adb, here's what Ive been doing:
adb remount
adb shell
rm -r /system/media/boot2.gif
ls /system/media (to make sure I took it away)
exit
adb push boot2.gif /system/media
ls /system/media (to make sure I got new one there)
exit
reboot
Well, I dont remember where I put the exit... but still, as you can tell, Im getting rid of, checking, replacing, and checking the boot2 gif. SHOULD be there.
Ok, so then it boots to Hero with the droids popping out, then the ORIGINAL boot 2 (wtfwtf), then jams up on the new gif I added.
SO, where is the original boot 2 lurking so that it keeps coming up after I rm'ed it??
Also, looking thru the XML, (Im not great with this, so slap me if Im wrong) it looks like boot 2 & 3's image sources are the same file?
form the xml:
"BootAnimation image="/system/media/boot.gif" image2="/system/media/boot2.gif" image3="/system/media/boot2.gif" loopimage="/system/media/boot2.gif" image_bg="/system/media/boot_bg.gif" audio="/system/media/boot.mp3" screenX="10" screenY="180" useAudio="1""
So, maybe if I change the bold portion to read "image3="/system/media/boot3.gif", and pushed a new boot3 image, it could run 3? Only issue I see is that it says to loop boot 2.......
Ideas?

Hummeroid said:
Ok, Im not the greatest, but I like to think I have a grasp on whats going on here...
First, Im on a Dream running JACxHero 1.2 rom.
As far as adb, here's what Ive been doing:
adb remount
adb shell
rm -r /system/media/boot2.gif
ls /system/media (to make sure I took it away)
exit
adb push boot2.gif /system/media
ls /system/media (to make sure I got new one there)
exit
reboot
Well, I dont remember where I put the exit... but still, as you can tell, Im getting rid of, checking, replacing, and checking the boot2 gif. SHOULD be there.
Ok, so then it boots to Hero with the droids popping out, then the ORIGINAL boot 2 (wtfwtf), then jams up on the new gif I added.
SO, where is the original boot 2 lurking so that it keeps coming up after I rm'ed it??
Also, looking thru the XML, (Im not great with this, so slap me if Im wrong) it looks like boot 2 & 3's image sources are the same file?
form the xml:
"BootAnimation image="/system/media/boot.gif" image2="/system/media/boot2.gif" image3="/system/media/boot2.gif" loopimage="/system/media/boot2.gif" image_bg="/system/media/boot_bg.gif" audio="/system/media/boot.mp3" screenX="10" screenY="180" useAudio="1""
So, maybe if I change the bold portion to read "image3="/system/media/boot3.gif", and pushed a new boot3 image, it could run 3? Only issue I see is that it says to loop boot 2.......
Ideas?
Click to expand...
Click to collapse
I wanted to do this before... but never seemed to work...
I would replace both gif's with my own... but it would be all staticky(if that's a word... haha...)...
I gave up because no matter what I did... it always ended up not working :/

bump
anyone have any new ideas. how to change from custom cyan image to this?

http://ostebaronen.dk/\
On here it states that ONLY HTC Branded magics can do animated boot screens, Mine will do it with a hero rom but i cant put my own on my 32B running cyanogenmod. I think cyanogen changed the bioot screen on his rom so maybe you need to talk to him?

bonesy said:
http://ostebaronen.dk/\
On here it states that ONLY HTC Branded magics can do animated boot screens, Mine will do it with a hero rom but i cant put my own on my 32B running cyanogenmod. I think cyanogen changed the bioot screen on his rom so maybe you need to talk to him?
Click to expand...
Click to collapse
Cyanogen made a hero build? News to me.
If he didnt, then yeah, he changed his, but thats not a gif. The Cyanogen I run definitely doesnt do gif ani boot screens

How to root the CDMA Hero

Ok everyone. First off do not update your phone if Sprint offers an upate. I don't think they are going to but if they do anytime soon and you update this exploit could likely be fixed. When updates are released the devs will make updates that keep root so do not update!
That said, this is a very newbie guide. This is meant for Windows but I will post instructions for linux as well (Ubuntu). I just need to warn you that I can't adb into my phone from Ubuntu so I have to do it through Windows. Don't know why it doesnt work but it doesnt. Mac users you can always (assuming you can get it to work in Ubuntu) download a live cd and boot into Ubuntu to try this. I don't have a mac (nor do I want one) so I can't give instructions (though I assume they should be relatively the same).
Step 1:
First you need to download the Android SDK. It may soumd confusing but it's not. There are tools in here that we need. You can get it from http://developer.android.com/sdk/index.html. This is a modular SDK and all the tools we need are in this download. Once downloaded you just need to extract it in a directory of choice.
The next thing we download is asroot2. This is a script that was developed that runs an exploit in Android's linux that allows us to run root. The link for that is here: http://forum.xda-developers.com/attachment.php?attachmentid=244212&d=1257621154. Unzip that file and place it in a directory of your choice. Also download http://www.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-heroc-v1.2.3.img and place that into the same directory you extracted asroot2.
Step 2:
Connect the phone to the USB port.
Ubuntu is easy for this (again assuming it works for you). Simply open a terminal and cd into the directory that you extracted the sdk into. Then cd into the tools directory. Then run the following commands:
sudo ./adb push /directory_you_placed_asroot2/asroot2 /data/local/
sudo ./adb shell chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
If all goes well you should be presented with a new prompt. This is the linux terminal built into Android. This will allow us to execute all the commands we need to execute because the asroot2 script gave us root access.
In Windows it is a little more difficult. You have to first install the driver for the phone. When Windows asks you for the drivers direct Windows to the directory you extracted the SDK into. You should see a folder called usb_driver. If you are running the 32 bit version of Windows select the x86 folder. If you are using a 64 bit version then select the x64 folder. Then select the android_usb.inf file. This should install the drivers.
If running XP or lower you will need to go to the start menu and click run, then you enter cmd and press enter. If Vista or higher you will press the start button and type cmd and press enter. When you are at the command prompt you cd to the directory you extracted the sdk into. Then cd into the tools directory. Then execute the following commands:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
Now your phone is officially rooted! We arent done yet though. Now you need to flash the recovery image. If you are still in adb shell type in exit until you are out. You should be in the directory where you extracted the recovery image. If not go there. Type in the following:
adb push recovery-RA-heroc-v1.2.3.img /sdcard/
Once that is done, type in adb shell (or sudo ./adb shell in ubuntu). If your command prompt is a dollar sign then type in su and press enter. If it is a pound sign you are good. Then type in the following:
adb shell flash_image recovery recovery-RA-heroc-v1.2.3.img
Once that is finished you are done. To reboot into recovery type in adb shell reboot recovery. You should reboot into recovery mode. Right now there is not a lot you can do but once we have some devs who make some roms then we will be well on our way to an even more awesome phone. Any questions please ask away. Also, I am sorry if this tutorial is hard to understand or badly laid out. My daughter is crawling all over me so it's hard to type or think. Good luck all and thanks to everyone who rooted this phone and made the recovery and did such a great job!

chuckhriczko said:
adb shell flash_image recovery recovery-RA-heroc-v1.2.3.img
Click to expand...
Click to collapse
Is this the right command, every time I try I get : "adb: not found"
The transfer to the sd card seemed to go fine, and I am @ root (#).
Am I missing something?

You beat me to it!!!! I was planning on laying out the steps to make sure I had my head on straight.
To continue with your guide: (The following are questions, not procedures)
1. We run a Nandroid back up to lock in our stock ROM so if we ever do something stupid, aka brick the phone, we can push this back on?
2. What comes on the SD card? Is it needing to be backed up when I go to a 16GB class 6 card?
3. Insert the new SDcard and use the ext2/swap/fat32 script
4. convert ext2 to ext3, (now ready for apps2SD?)
Anything else you can add would be nice.
Again thanks for the steps! They are clear for me.

rockcrawler said:
Is this the right command, every time I try I get : "adb: not found"
The transfer to the sd card seemed to go fine, and I am @ root (#).
Am I missing something?
Click to expand...
Click to collapse
Sounds like you need to add the directory where you have adb to be added to he path. is your adb in the same dir as the image?

rockcrawler said:
Is this the right command, every time I try I get : "adb: not found"
The transfer to the sd card seemed to go fine, and I am @ root (#).
Am I missing something?
Click to expand...
Click to collapse
You may currently be in adb shell already. If you are showing the pound sign this is likely. The command is supposed to be run outside of adb shell. Try the command below:
flash_image recovery recovery-RA-heroc-v1.2.3.img

Treefallingquietly said:
Sounds like you need to add the directory where you have adb to be added to he path. is your adb in the same dir as the image?
Click to expand...
Click to collapse
I apologize, but that went right over my head.
I have used this command to copy the image to the sd card.
Code:
adb push recovery-RA-heroc-v1.2.3.img /sdcard/
I got this output:
Code:
C:\androidSDK\android-sdk-windows\tools>adb push recovery-RA-heroc-v1.2.3.img /s
dcard/
1640 KB/s (3352576 bytes in 1.996s)
I then do the following with the noted result:
Code:
C:\androidSDK\android-sdk-windows\tools>adb shell
$ su
su
# adb shell flash_image recovery recovery-RA-heroc-v1.2.3.img
adb shell flash_image recovery recovery-RA-heroc-v1.2.3.img
adb: not found
Any help as to where I making my mistake would be greatly appreciated.

Treefallingquietly said:
You beat me to it!!!! I was planning on laying out the steps to make sure I had my head on straight.
To continue with your guide: (The following are questions, not procedures)
1. We run a Nandroid back up to lock in our stock ROM so if we ever do something stupid, aka brick the phone, we can push this back on?
Click to expand...
Click to collapse
Yes. A nandroid backup completely backs up every piece of information on your phone. It is a complete image of your phone and if it needs to be restored for whatever reason you just load up recovery and can restore it the way it was before.
Treefallingquietly said:
2. What comes on the SD card? Is it needing to be backed up when I go to a 16GB class 6 card?
Click to expand...
Click to collapse
What do you mean exactly? The only thing that gets copied to an sd card is the nandroid backup so yes, when switching to an sd card just do another backup. Or you can also copy the nandroid folder from your existing sd card to your new one.
Treefallingquietly said:
3. Insert the new SDcard and use the ext2/swap/fat32 script
4. convert ext2 to ext3, (now ready for apps2SD?)
Click to expand...
Click to collapse
Yes and no. Just run the ext2/swap/fat32 script and it should be ready for apps2sd. You can convert to ext3 if you want. Generally on normal hard drives ext3 is faster, however there has been some controversy with that on android phones. As for converting to apps2sd, right now the best way is probably the manual method which I can write up a tutorial on as well. The dream forum has some good tutorials on it as they were the first to do it. I actually need to go back and re read some of those because it's been so long since I did it. I tried the apps2sd apk but that didnt seem to work for me.

rockcrawler said:
I apologize, but that went right over my head.
I have used this command to copy the image to the sd card.
Code:
adb push recovery-RA-heroc-v1.2.3.img /sdcard/
I got this output:
Code:
C:\androidSDK\android-sdk-windows\tools>adb push recovery-RA-heroc-v1.2.3.img /s
dcard/
1640 KB/s (3352576 bytes in 1.996s)
I then do the following with the noted result:
Code:
C:\androidSDK\android-sdk-windows\tools>adb shell
$ su
su
# adb shell flash_image recovery recovery-RA-heroc-v1.2.3.img
adb shell flash_image recovery recovery-RA-heroc-v1.2.3.img
adb: not found
Any help as to where I making my mistake would be greatly appreciated.
Click to expand...
Click to collapse
Yeah. The problem is that you are trying to adb shell twice. After you adb push then just run the command adb shell flash_image recovery recovery-RA-heroc-v1.2.3.img. That should work.

chuckhriczko said:
You may currently be in adb shell already. If you are showing the pound sign this is likely. The command is supposed to be run outside of adb shell. Try the command below:
flash_image recovery recovery-RA-heroc-v1.2.3.img
Click to expand...
Click to collapse
Now I get the Following:
Code:
# flash_image recovery recovery-RA-heroc-v1.2.3.img
flash_image recovery recovery-RA-heroc-v1.2.3.img
error opening recovery-RA-heroc-v1.2.3.img: No such file or directory
#
And this outside adb shell, in the same directory where I did the push:
Code:
C:\androidSDK\android-sdk-windows\tools>adb shell flash_image recovery recovery-
RA-heroc-v1.2.3.img
error opening recovery-RA-heroc-v1.2.3.img: No such file or directory
Ideas?

rockcrawler said:
Is this the right command, every time I try I get : "adb: not found"
The transfer to the sd card seemed to go fine, and I am @ root (#).
Am I missing something?
Click to expand...
Click to collapse
yes he left out the /sdcard/in the path and if you are in teh shell you don't need the adb portion of the command.

rockcrawler said:
Now I get the Following:
Code:
# flash_image recovery recovery-RA-heroc-v1.2.3.img
flash_image recovery recovery-RA-heroc-v1.2.3.img
error opening recovery-RA-heroc-v1.2.3.img: No such file or directory
#
And this outside adb shell, in the same directory where I did the push:
Code:
C:\androidSDK\android-sdk-windows\tools>adb shell flash_image recovery recovery-
RA-heroc-v1.2.3.img
error opening recovery-RA-heroc-v1.2.3.img: No such file or directory
Ideas?
Click to expand...
Click to collapse
Ok. Most likely you dont have the recovery image in the directory. Try this. Copy the recovery image to the tools directory of the sdk. Then, outside of adb shell, (making sure you are in the tools directory of the sdk) execute the following command:
adb shell flash_image recovery recovery-RA-heroc-v1.2.3.img
This should work as long as you have the recovery image in the correct directory.

can i use the rom from modaco? or at least the themes?

magicalan said:
can i use the rom from modaco? or at least the themes?
Click to expand...
Click to collapse
No way! This rom is a GSM rom and if it works at all and does not brick your phone then it wont have the right software to make your phone work. A dev has to create a rom specially for the CDMA Hero that has the right drivers.

chuckhriczko said:
Ok. Most likely you dont have the recovery image in the directory. Try this. Copy the recovery image to the tools directory of the sdk. Then, outside of adb shell, (making sure you are in the tools directory of the sdk) execute the following command:
adb shell flash_image recovery recovery-RA-heroc-v1.2.3.img
This should work as long as you have the recovery image in the correct directory.
Click to expand...
Click to collapse
I am feeling really special, not being able to make this work, but that is the folder that it has been in all this time. I have even downloaded and pushed it several times. Proof:
{
"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"
}
So I am not sure where I am messing up.
Thanks for all the help and hard work on this BTW!

rockcrawler said:
I am feeling really special, not being able to make this work, but that is the folder that it has been in all this time. I have even downloaded and pushed it several times. Proof:
So I am not sure where I am messing up.
Thanks for all the help and hard work on this BTW!
Click to expand...
Click to collapse
Meh. Not hard work. Just experience. The hard work is what the rom devs do. And it is difficult at first but once you get it trust me, you get it.Okay let's try this. Go into the command prompt (not adb shell) into the folder where adb and the recovery image is. Try to execute the following command and see if it works.
Code:
adb push recovery-RA-heroc-v1.2.3.img /sdcard/
This will put the recovery image on the sdcard. If this works then we will continue.

chuckhriczko said:
Meh. Not hard work. Just experience. The hard work is what the rom devs do. And it is difficult at first but once you get it trust me, you get it.Okay let's try this. Go into the command prompt (not adb shell) into the folder where adb and the recovery image is. Try to execute the following command and see if it works.
Code:
adb push recovery-RA-heroc-v1.2.3.img /sdcard/
This will put the recovery image on the sdcard. If this works then we will continue.
Click to expand...
Click to collapse
Done.
Code:
C:\androidSDK\android-sdk-windows\tools>adb push recovery-RA-heroc-v1.2.3.img /s
dcard/
1747 KB/s (3352576 bytes in 1.873s)
C:\androidSDK\android-sdk-windows\tools>

rockcrawler said:
Done.
Code:
C:\androidSDK\android-sdk-windows\tools>adb push recovery-RA-heroc-v1.2.3.img /s
dcard/
1747 KB/s (3352576 bytes in 1.873s)
C:\androidSDK\android-sdk-windows\tools>
Click to expand...
Click to collapse
Sweetness. Ok. Now type in the following:
Code:
$ adb shell
$ cd /sdcard/
$ su
# flash_image recovery recovery-RA-heroc-v1.2.3.img
That should work. Note, don't type in the $ or the #. Those are just there to show what the command prompt should look like.

THANK YOU!!!!!
chuckhriczko said:
Sweetness. Ok. Now type in the following:
Code:
$ adb shell
$ cd /sdcard/
$ su
# flash_image recovery recovery-RA-heroc-v1.2.3.img
That should work. Note, don't type in the $ or the #. Those are just there to show what the command prompt should look like.
Click to expand...
Click to collapse
Worked Like a charm, THANK YOU!!! Just booted to the recovery image and all is well.
p.s. Might want to edit the origional instructions, one your daughter goes to bed, to include the cd to the sd card, that is where my problem was.

rockcrawler said:
Worked Like a charm, THANK YOU!!! Just booted to the recovery image and all is well.
p.s. Might want to edit the origional instructions, one your daughter goes to bed, to include the cd to the sd card, that is where my problem was.
Click to expand...
Click to collapse
If I am able to I will. I understand that the instructions were a little hard to follow for beginners which was what I wanted to avoid. Glad you got it working though. Welcome to the world of Android hacking and please enjoy your stay

I'm getting suck trying to push the recovery img out to my sdcard
Code:
C:\AndroidSDK\tools>adb push recovery-RA-heroc-v1.2.3.img /sdcard/
cannot stat 'recovery-RA-heroc-v1.2.3.img': No such file or directory
I believe I have root access:
Code:
C:\AndroidSDK\tools>adb shell
$ su
su
#

How to backup compressed data from your android device to your computer

Disclaimer
Code:
Whatever you do, it's your decision and you do it on your own risk!
I am not responsible for bricks, any kind of damages, data loss or any other unwanted result!
Everything you do is done on YOUR OWN RESPONSIBILITY!
And I am also not responsible if you lose the chat with your crush.
You might want to transfer your internal storage such as /sdcard to your computer directly and compressed as fast as possible.
So here is how you do it (on linux using bash):
Reboot your phone into TWRP, connect your device to your computer, and run the following command:
Code:
adb shell mkfifo /bk.pipe && adb exec-out 'tar -cvap data/media/0 2>/bk.pipe' | dd of=sdcard.tar & adb shell cat /bk.pipe &
In this example your data (in this case /data/media/0) will be backed up to your computer into the file sdcard.tar.
Compression is done automatically and you will get a nice output on your terminal on which file is being backed up currently.
When everything is finished you should get a message similar to this on your terminal:
Code:
79692237+2 records in
79692238+0 records out
40802425856 bytes (41 GB, 38 GiB) copied, 3550,38 s, 11,5 MB/s
(On the result of this you can see that the speed is around 12 MB/s, means that 1 GB backups in less than 1 minute)
When you get that, it means that your backup has finished and you can safely remove the usb cable.
Note that you can do this with any directory on your device, so if you desire to back up /data, just write data instead of data/media/0.
Example of the resulting sdcard.tar file (opened on my computer):
{
"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"
}
Decompressing your data directly to your device might get a little trickier:
Code:
adb shell mkfifo /rst.pipe && adb push sdcard.tar /rst.pipe & adb shell 'cd /; cat /rst.pipe | tar -xv'
If that does not work, you can just extract the content of the tar file normally onto your computer and then copy the files over using adb push or copy the tar file to your phone and extract it using the following command:
Code:
adb push sdcard.tar /sdcard/sdcard.tar
adb shell 'cd /; tar -xvf /sdcard/sdcard.tar'
And that should do the job as well.
---
See also:
tar to pipe but keep -v verbose output separate from STDERR
Transferring binary data over ADB shell (ie fast file transfer using tar)
Compose and pipe a gzipped tar archive in one go
Bash tar and output to log file
GNU Tar
Encrypting and Compressing
How encrypt data/text stream instead of a file?
Post on my blog:
How to backup compressed data from your android device to your computer

Is it possible to do this with windows cmd?

Hmm, that looks really complicated. How about rsync instead?
(Note: This requires root and it requires rsync... It's present on CyanogenMod and probably other custom roms, but usually not on stock ROMs...)
Code:
1. Create rsync.conf:
[root]
path = /
read only = no
uid = root
gid = root
2. Upload the file to the phone
$ adb push rsync.conf /sdcard/
3. Restart adbd with root permissions
$ adb root
4. Set up TCP forwarding of the rsync daemon through adb
$ adb forward tcp:9873 tcp:873
5. Run the daemon on the phone
$ adb shell /system/xbin/rsync --daemon --config /sdcard/rsync.conf --no-detach
6. Copy files in both directions
rsync -v rsync://localhost:9873/root/
rsync --help
Edit: You can also run rsync via SSH, e.g. with the help of SSHdroid:
Code:
rsync -e "ssh -l root -p 2222" -v <phone-ip>:/

adbsync utility by @Renate NST is pretty perfect for this too. I've got a batch automation for Windows packaged up in my Odds and Ends thread but I'm sure it wouldn't be hard to get something similar setup for Linux.

Nice!
Is there a way to do this but instead of coping files, copy the raw data from the internal memory? So that I can recover deleted files from the device from the generated raw file.

Tarcis said:
Nice!
Is there a way to do this but instead of coping files, copy the raw data from the internal memory? So that I can recover deleted files from the device from the generated raw file.
Click to expand...
Click to collapse
Something like (run in the host console)
Code:
adb exec-out "cat <sdcard partition> 2>/dev/null" > sdcard.raw
Or
Code:
adb exec-out "dd if=<sdcard partition> bs=64k 2>/dev/null" > sdcard.raw
This works on Windows too.
Something like on the first post that works on Windows but without the progress report (which is what the FIFO is for):
Code:
adb exec-out "tar czf - /sdcard" > sdcard.tar.gz
adb exec-out is an undocumented adb command that works like adb shell but without creating a pseudoterminal thus it works with binary content.

Has it been confirmed that all files are backed up this way? Main issue I have when backing up via MTP is that not all files seem to be transferred properly e.g. Carbon/Helium backups missing the json file.

tech3475 said:
Has it been confirmed that all files are backed up this way? Main issue I have when backing up via MTP is that not all files seem to be transferred properly e.g. Carbon/Helium backups missing the json file.
Click to expand...
Click to collapse
As far as I know, tar backups all files recursively in the directory you specified. Hence that should work perfectly fine. I recommend to use TWRP 3+ for this, but you can also try it on android itself.

Tarcis said:
Nice!
Is there a way to do this but instead of coping files, copy the raw data from the internal memory? So that I can recover deleted files from the device from the generated raw file.
Click to expand...
Click to collapse
It depends on your device, but in general, you can transfer any binary data over exec-out in highspeed.
Code:
adb root
adb exec-out "dd if=/dev/block/mmcblk0" > mmcblk0.img
In this case it would copy the whole internal storage including all partitions and everything from 0 to end of your internal emmc to your computer.
On newer devices/systems you can also use the following to copy the single partitions (in this example /data) as raw image to your pc:
Code:
adb root
adb exec-out "dd if=/dev/block/bootdevice/by-name/userdata">userdata.img
Examples for partition names: system, data, userdata, cache, boot, LOGO, recovery, ...
If you want to compress all partitions separately into a tar archive, following command should do:
Code:
adb root && adb exec-out 'cd /dev/block/bootdevice/by-name && tar -ca ./' > allpartitions.tar
This would also work on windows.

char101 said:
Something like (run in the host console)
Code:
adb exec-out "cat <sdcard partition> 2>/dev/null" > sdcard.raw
Or
Code:
adb exec-out "dd if=<sdcard partition> bs=64k 2>/dev/null" > sdcard.raw
This works on Windows too.
Something like on the first post that works on Windows but without the progress report (which is what the FIFO is for):
Code:
adb exec-out "tar czf - /sdcard" > sdcard.tar.gz
adb exec-out is an undocumented adb command that works like adb shell but without creating a pseudoterminal thus it works with binary content.
Click to expand...
Click to collapse
xdvs23 said:
It depends on your device, but in general, you can transfer any binary data over exec-out in highspeed.
Code:
adb root
adb exec-out "dd if=/dev/block/mmcblk0" > mmcblk0.img
In this case it would copy the whole internal storage including all partitions and everything from 0 to end of your internal emmc to your computer.
On newer devices/systems you can also use the following to copy the single partitions (in this example /data) as raw image to your pc:
Code:
adb root
adb exec-out "dd if=/dev/block/bootdevice/by-name/userdata">userdata.img
Examples for partition names: system, data, userdata, cache, boot, LOGO, recovery, ...
If you want to compress all partitions separately into a tar archive, following command should do:
Code:
adb root && adb exec-out 'cd /dev/block/bootdevice/by-name && tar -ca ./' > allpartitions.tar
This would also work on windows.
Click to expand...
Click to collapse
Thank you so much for the commands, but I ran them on Windows, and I get no error, but the output file is 1kb.
I tried running on dos prompt, I´ll try again tomorrow on cygwin

thank but too hard for me
can i have another software to do this?

There are a few ways which you can make a Nandroid backup. The recommended way is to use a custom recovery to create one, and it’s the only way to restore from one. You should be able to use any custom recovery that offers Nandroid backup capabilities — if you don’t want to search around, the best choices are CWM and TWRP. Once you’ve flashed a custom recovery onto your device, you can boot into it and choose to create (or later on, restore from) a Nandroid backup. It’ll go through the process and create a backup file on your microSD card or other equivalent storage location.

Emma Tayler said:
There are a few ways which you can make a Nandroid backup. The recommended way is to use a custom recovery to create one, and it’s the only way to restore from one. You should be able to use any custom recovery that offers Nandroid backup capabilities — if you don’t want to search around, the best choices are CWM and TWRP. Once you’ve flashed a custom recovery onto your device, you can boot into it and choose to create (or later on, restore from) a Nandroid backup. It’ll go through the process and create a backup file on your microSD card or other equivalent storage location.
Click to expand...
Click to collapse
Then tell me how to create a nandroid backup from your internal storage (/sdcard or /data/media/0)

Tarcis said:
Thank you so much for the commands, but I ran them on Windows, and I get no error, but the output file is 1kb.
I tried running on dos prompt, I´ll try again tomorrow on cygwin
Click to expand...
Click to collapse
Then open the file using e.g. notepad and show me the contents. It could be an error message or something...

cuddas said:
thank but too hard for me
can i have another software to do this?
Click to expand...
Click to collapse
I'm actually making backup tools which you can then use to create backups easily, maybe I'll also make a program with a user interface for windows where you can do that much easier.
Of course I cant promise anything atm cuz I have some other things to do as well.

xdvs23 said:
Disclaimer
Code:
adb shell mkfifo /bk.pipe && adb exec-out 'tar -cvap data/media/0 2>/bk.pipe' | dd of=sdcard.tar & adb shell cat /bk.pipe &
Click to expand...
Click to collapse
replace with this one
Code:
adb shell mkfifo /bk.pipe && adb exec-out 'tar -cvap data/media/0 2>/bk.pipe' | dd of=sdcard.tar & adb shell cat /bk.pipe &

xdvs23 said:
Then open the file using e.g. notepad and show me the contents. It could be an error message or something...
Click to expand...
Click to collapse
good idea!
The files contained:
allpartitions.tar: /sbin/sh: syntax error: unterminated quoted string on one tr
mmcblk0.img: 0kb
sdcard.raw : /sbin/sh: syntax error: unexpected redirection
userdata:img: dd: can't open '/dev/block/bootdevice/by-name/userdata': No such file or directory

Does this help?
http://syedtahir16.blogspot.in/2014/11/the-ultimate-android-backup-solution.html

syedtahir16 said:
Does this help?
http://syedtahir16.blogspot.in/2014/11/the-ultimate-android-backup-solution.html
Click to expand...
Click to collapse
No, but thanks. The ideia is to be able to backup without being able to load the OS.

how to restore?

need help from andriod pro

i know its not the right section to post but i have very less post count
anyway my question
with ROOTED phone ,
I use this commands in adb :
adb shell dd if=/dev/zero of=/dev/block/sda1
adb shell dd if=/dev/zero of=/dev/block/sda2
adb shell dd if=/dev/zero of=/dev/block/sdd4
and works perfect
but I want something for UnROOTED phone
or is ther anything called temporary root?

[DEVELOPMENT][PATCH][FIX] Zenfone 3 Corrupt BASEBAND IMEI WIFI (ZE520KL | ZE552KL)

Hello Everyone. I am X.O here,
This thread is to catch attention to my fellow developers and contributors and even advanced users of this device Zenfone 3.
I've been seeing that a lot of users and developers of this device are getting their phones bricked and corrupting the BASEBAND, IMEI, WLAN/BT MAC, SERIAL NO. and so on just by using the official RAW firmwares available for this device.
Yet no one has the solution to the problems whatsoever.
I've browsed a lot and found no supportive files in order to fix the problems i was facing.
Let's get to the point now.
I need support of any user, developer or contributor who is currently using this phone and has ROOT in it.
Partition backup files are required in order to put a solve into the issues mentioned above.
PLEASE, IT IS A REQUEST TO ALL OF THE PEOPLE WHO ARE CURRENTLY SEEING THIS THREAD!!
--- UPLOAD THE REQUIRED FILES AND SUPPORT THIS COMMUNITY FOR PATCHES & FIXES ---
System Requirements:
-- ROOT
-- TERMINAL EMULATOR or A COMPUTER
-- Working Brain LOL!
PREPARATION:
-- Unlock Bootloader of your device.
-- ROOT your device.
~~ FOR ANDROID ~~
-- Download and Install Gboard (link)(Google Keyboard for typing into Terminal Emulator |OTHER KEYBOARD DO NOT WORK|
-- Download and Install Terminal Emulator (link)
-- Type "su" press Enter (Grant SuperSU permission)
-- Type the following commands accordingly.
Code:
dd if=/dev/block/mmcblk0p24 of=/sdcard/FSG
dd if=/dev/block/mmcblk0p26 of=/sdcard/MODEMST1
dd if=/dev/block/mmcblk0p27 of=/sdcard/MODEMST2
dd if=/dev/block/mmcblk0p56 of=/sdcard/PERSIST
dd if=/dev/block/mmcblk0p35 of=/sdcard/PERSISTENT
dd if=/dev/block/mmcblk0p21 of=/sdcard/SEC
dd if=/dev/block/mmcblk0p22 of=/sdcard/DEVINFO
dd if=/dev/block/mmcblk0p28 of=/sdcard/FACTORY
dd if=/dev/block/mmcblk0p25 of=/sdcard/FSC
dd if=/dev/block/mmcblk0p50 of=/sdcard/FSGCA
dd if=/dev/block/mmcblk0p44 of=/sdcard/MCFG
dd if=/dev/block/mmcblk0p37 of=/sdcard/MISC
dd if=/dev/block/mmcblk0p52 of=/sdcard/OEM
dd if=/dev/block/mmcblk0p43 of=/sdcard/SYSCFG
dd if=/dev/block/mmcblk0p23 of=/sdcard/SYSINFO
(You'll get something like this as output.)
{
"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"
}
-- Zip the files created in SDCARD, zip all the files and send as attachment to me at [email protected] or upload at any file sharing server such as MediaFIre
~~ FOR COMPUTER RUNNING WINDOWS ~~
-- Install Minimal ADB and Fastboot (link)
-- Open "Minimal ADB and Fastboot" window.
-- Type "adb shell" Press Enter.
-- Type "su" and grant SuperSU permission on phone.
-- Type the following commands accordingly. (You can copy and paste each line to the CMD window if you want.)
Code:
dd if=/dev/block/mmcblk0p24 of=/sdcard/FSG
dd if=/dev/block/mmcblk0p26 of=/sdcard/MODEMST1
dd if=/dev/block/mmcblk0p27 of=/sdcard/MODEMST2
dd if=/dev/block/mmcblk0p56 of=/sdcard/PERSIST
dd if=/dev/block/mmcblk0p35 of=/sdcard/PERSISTENT
dd if=/dev/block/mmcblk0p21 of=/sdcard/SEC
dd if=/dev/block/mmcblk0p22 of=/sdcard/DEVINFO
dd if=/dev/block/mmcblk0p28 of=/sdcard/FACTORY
dd if=/dev/block/mmcblk0p25 of=/sdcard/FSC
dd if=/dev/block/mmcblk0p50 of=/sdcard/FSGCA
dd if=/dev/block/mmcblk0p44 of=/sdcard/MCFG
dd if=/dev/block/mmcblk0p37 of=/sdcard/MISC
dd if=/dev/block/mmcblk0p52 of=/sdcard/OEM
dd if=/dev/block/mmcblk0p43 of=/sdcard/SYSCFG
dd if=/dev/block/mmcblk0p23 of=/sdcard/SYSINFO
(You'll get something like this as output.)
-- Now ZIP the mentioned files found on SDCARD and email at [email protected] or upload at any file sharing server such as MediaFIre
Here is an important note to everyone who will be curious to what i asked for in this thread. This is only for development and fixing purposes and i hold no grudge to destroy your privacy or private data including your personal IMEI, SN, MAC.
I will surely change all of the security data that are collected from your phone to 0s or 1s. You get to keep your super secret security info.
Click to expand...
Click to collapse
I WILL DEFINITELY MENTION THE NAME OF THE CONTRIBUTOR(S) WHO WILL SEND ME THE FILES.
Click to expand...
Click to collapse
And for the fixes, i will work on the files and make easy fixes available to everyone as soon as i get the files.
Click to expand...
Click to collapse
Thank you for your support.
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Tags for your attention : @shakalaca @anhenrique @kyle_l88 @cdanthien @aswindivakar100 @OxYTooN @animaanimus @mdigiacomi @itsme.Ronjie @EypCnn @cdanthien

Xtreme.Ornob said:
Hello Everyone. I am X.O here,
This thread is to catch attention to my fellow developers and contributors and even advanced users of this device Zenfone 3.
I've been seeing that a lot of users and developers of this device are getting their phones bricked and corrupting the BASEBAND, IMEI, WLAN/BT MAC, SERIAL NO. and so on just by using the official RAW firmwares available for this device.
Yet no one has the solution to the problems whatsoever.
I've browsed a lot and found no supportive files in order to fix the problems i was facing.
Let's get to the point now.
I need support of any user, developer or contributor who is currently using this phone and has ROOT in it.
Partition backup files are required in order to put a solve into the issues mentioned above.
PLEASE, IT IS A REQUEST TO ALL OF THE PEOPLE WHO ARE CURRENTLY SEEING THIS THREAD!!
--- UPLOAD THE REQUIRED FILES AND SUPPORT THIS COMMUNITY FOR PATCHES & FIXES ---
System Requirements:
-- ROOT
-- TERMINAL EMULATOR or A COMPUTER
-- Working Brain LOL!
PREPARATION:
-- Unlock Bootloader of your device.
-- ROOT your device.
~~ FOR ANDROID ~~
-- Download and Install Gboard (link)(Google Keyboard for typing into Terminal Emulator |OTHER KEYBOARD DO NOT WORK|
-- Download and Install Terminal Emulator (link)
-- Type "su" press Enter (Grant SuperSU permission)
-- Type the following commands accordingly.
Code:
dd if=/dev/block/mmcblk0p24 of=/sdcard/FSG
dd if=/dev/block/mmcblk0p26 of=/sdcard/MODEMST1
dd if=/dev/block/mmcblk0p27 of=/sdcard/MODEMST2
dd if=/dev/block/mmcblk0p56 of=/sdcard/PERSIST
dd if=/dev/block/mmcblk0p35 of=/sdcard/PERSISTENT
dd if=/dev/block/mmcblk0p21 of=/sdcard/SEC
dd if=/dev/block/mmcblk0p22 of=/sdcard/DEVINFO
dd if=/dev/block/mmcblk0p28 of=/sdcard/FACTORY
dd if=/dev/block/mmcblk0p25 of=/sdcard/FSC
dd if=/dev/block/mmcblk0p50 of=/sdcard/FSGCA
dd if=/dev/block/mmcblk0p44 of=/sdcard/MCFG
dd if=/dev/block/mmcblk0p37 of=/sdcard/MISC
dd if=/dev/block/mmcblk0p52 of=/sdcard/OEM
dd if=/dev/block/mmcblk0p43 of=/sdcard/SYSCFG
dd if=/dev/block/mmcblk0p23 of=/sdcard/SYSINFO
(You'll get something like this as output.)
-- Zip the files created in SDCARD, zip all the files and send as attachment to me at [email protected] or upload at any file sharing server such as MediaFIre
~~ FOR COMPUTER RUNNING WINDOWS ~~
-- Install Minimal ADB and Fastboot (link)
-- Open "Minimal ADB and Fastboot" window.
-- Type "adb shell" Press Enter.
-- Type "su" and grant SuperSU permission on phone.
-- Type the following commands accordingly. (You can copy and paste each line to the CMD window if you want.)
Code:
dd if=/dev/block/mmcblk0p24 of=/sdcard/FSG
dd if=/dev/block/mmcblk0p26 of=/sdcard/MODEMST1
dd if=/dev/block/mmcblk0p27 of=/sdcard/MODEMST2
dd if=/dev/block/mmcblk0p56 of=/sdcard/PERSIST
dd if=/dev/block/mmcblk0p35 of=/sdcard/PERSISTENT
dd if=/dev/block/mmcblk0p21 of=/sdcard/SEC
dd if=/dev/block/mmcblk0p22 of=/sdcard/DEVINFO
dd if=/dev/block/mmcblk0p28 of=/sdcard/FACTORY
dd if=/dev/block/mmcblk0p25 of=/sdcard/FSC
dd if=/dev/block/mmcblk0p50 of=/sdcard/FSGCA
dd if=/dev/block/mmcblk0p44 of=/sdcard/MCFG
dd if=/dev/block/mmcblk0p37 of=/sdcard/MISC
dd if=/dev/block/mmcblk0p52 of=/sdcard/OEM
dd if=/dev/block/mmcblk0p43 of=/sdcard/SYSCFG
dd if=/dev/block/mmcblk0p23 of=/sdcard/SYSINFO
(You'll get something like this as output.)
-- Now ZIP the mentioned files found on SDCARD and email at [email protected] or upload at any file sharing server such as MediaFIre
​
Tags for your attention : @shakalaca @anhenrique @kyle_l88 @cdanthien @aswindivakar100 @OxYTooN @animaanimus @mdigiacomi @itsme.Ronjie @EypCnn @cdanthien
Click to expand...
Click to collapse
If you flash Official RAW (13.20.10.137) and the IMEI/Baseband/WiFi doesn't work, follow this thread
https://www.asus.com/zentalk/forum.php?mod=viewthread&tid=164531&page=1&extra=#pid675648
P.S: No root is needed

Brother, i need to make a fix for this device, in general words, the fix will solve the problem in a more easy way.
This also is for them who lost their baseband, tried to repair it and lost the original baseband data (modemst1,
modemst2, fsg etc).
I need the files to make patches for easier fixes, that's all. The original fsg, fsgCA of my phone is zeroed out brother. No returning of baseband from that. I hope you understand my theory.
ZenFoneThree said:
If you flash Official RAW (13.20.10.137) and the IMEI/Baseband/WiFi doesn't work, follow this thread
https://www.asus.com/zentalk/forum.php?mod=viewthread&tid=164531&page=1&extra=#pid675648
P.S: No root is needed
Click to expand...
Click to collapse

ZenFoneThree said:
If you flash Official RAW (13.20.10.137) and the IMEI/Baseband/WiFi doesn't work, follow this thread
https://www.asus.com/zentalk/forum.php?mod=viewthread&tid=164531&page=1&extra=#pid675648
P.S: No root is needed
Click to expand...
Click to collapse
His mean that he fix the issues not face that issues bro.

Xtreme.Ornob said:
Brother, i need to make a fix for this device, in general words, the fix will solve the problem in a more easy way.
This also is for them who lost their baseband, tried to repair it and lost the original baseband data (modemst1,
modemst2, fsg etc).
I need the files to make patches for easier fixes, that's all. The original fsg, fsgCA of my phone is zeroed out brother. No returning of baseband from that. I hope you understand my theory.
Click to expand...
Click to collapse
Bro, do you have QFIL files for ZF3? My friend hard-bricked his phone

[email protected]@ said:
His mean that he fix the issues not face that issues bro.
Click to expand...
Click to collapse
Bro, the link I posted also fix the issues. Not face the issue
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
Xtreme.Ornob said:
Brother, i need to make a fix for this device, in general words, the fix will solve the problem in a more easy way.
This also is for them who lost their baseband, tried to repair it and lost the original baseband data (modemst1,
modemst2, fsg etc).
I need the files to make patches for easier fixes, that's all. The original fsg, fsgCA of my phone is zeroed out brother. No returning of baseband from that. I hope you understand my theory.
Click to expand...
Click to collapse
Oh, I thought flashing the RAW wiped out your modem. Sorry for misunderstanding.

I do have the problem for myself, i just want to help myself and the community as a lot of people are currently facing the hard bricks and unknown baseband. If anyone would be kind enough to upload the files to me, i will mention the contributor's name on my fix thread. Thank you.
[email protected]@ said:
His mean that he fix the issues not face that issues bro.
Click to expand...
Click to collapse

I can boot up your phone for sure. The files are in a very far sophisticated condition. Neither you nor anyone can use the method i have been developing. So you need to share screens for support. You need to be in TeamViewer in order to get it working.
Firstly, see if the device is detected in QDloader 9008 or HS-Diagnostics 900E port, then text me on facebook (link) or send an email to [email protected]
SaktisWRXSTi said:
Bro, do you have QFIL files for ZF3? My friend hard-bricked his phone
Click to expand...
Click to collapse

Do you think you can supply the files? If so, then it is highly appreciated.
ZenFoneThree said:
Bro, the link I posted also fix the issues. Not face the issue
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
Oh, I thought flashing the RAW wiped out your modem. Sorry for misunderstanding.
Click to expand...
Click to collapse

@Xtreme.Ornob if you download an Asus firmware and open it you can find some files and folder. In firmware-update folder there are all 'other partition' files included qfil (but has a different name)
But if you wanna unbrick your hard bricked device (Qualcomm port 9008) you can't

Brother, i see that you are assuming me a newbie in this field. Don't just assume bro.
I have collected and patched some files. I will update the thread real soon.
Will open another thread for unbricking from QDloader 9008 and also from Diagnostics 900E.
God bless you.
ExperienceTesla said:
@Xtreme.Ornob if you download an Asus firmware and open it you can find some files and folder. In firmware-update folder there are all 'other partition' files included qfil (but has a different name)
But if you wanna unbrick your hard bricked device (Qualcomm port 9008) you can't
Click to expand...
Click to collapse

Hello Xtreme.Ornob,
If you have the files for QFIL Flashing, you should upload those files. Many of the users are facing hardbricks and it'll help them. Make a new thread for Qualcomm Flashing.

ra_si said:
Hello Xtreme.Ornob,
If you have the files for QFIL Flashing, you should upload those files. Many of the users are facing hardbricks and it'll help them. Make a new thread for Qualcomm Flashing.
Click to expand...
Click to collapse
I have QFIL for both ZE520KL & ZE552KL

Asus_x008D
Hi there! i have the same problem and i tried to follow the instruction. But i have this issue, my phone model ZC520TL is not in the asus Flash tool Model selection. What should i do? Thanks for the help

ZenFone_3 said:
I have QFIL for both ZE520KL & ZE552KL
Click to expand...
Click to collapse
That's good.
Why don't you make a new thread for QFIL files and make it available for all.

ra_si said:
That's good.
Why don't you make a new thread for QFIL files and make it available for all.
Click to expand...
Click to collapse
Thread is live now
https://forum.xda-developers.com/zenfone-3/development/unbrick-qfil-zenfone-3-t3759473

test point
Saktis_STi said:
Thread is live now
https://forum.xda-developers.com/zenfone-3/development/unbrick-qfil-zenfone-3-t3759473
Click to expand...
Click to collapse
Xtreme.Ornob said:
Brother, i see that you are assuming me a newbie in this field. Don't just assume bro.
I have collected and patched some files. I will update the thread real soon.
Will open another thread for unbricking from QDloader 9008 and also from Diagnostics 900E.
God bless you.
Click to expand...
Click to collapse
Test point picture
https://ibb.co/caTY9d.

I have a problem with the wifi, it does not start. Can you solve it?