What would be the Terminal Emulator command to change the splash1 image?
blackknightavalon said:
What would be the Terminal Emulator command to change the splash1 image?
Click to expand...
Click to collapse
splash1 image?
cheech01 said:
splash1 image?
Click to expand...
Click to collapse
Yeah, the picture when you first boot up your phone. If we had fastboot working I'd could just do it that way.
Bootanimation?
Or Samsung text on boot
Sent from my GT-I8190 using xda app-developers app
ppero196 said:
Bootanimation?
Or Samsung text on boot
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
The Samsung text on boot. The very first thing you see when you boot the phone is generally considered "splash1." The boot animation is bootanimation.zip.
Still rummaging through the partitions for the splash1 image...
Sent from Spaceball One.
Related
i know many of you probably know of wat my problem is and i thank everyone for their advice previously but non of the solutions given work
i keep on getting a boot.img error whenever i install a rom
i am getting so fustrated when installing any rom beside cm7 because that works but every other rom i try fails because of the boot.img
when i try it to install it through fastboot it gives me a error when ''writing'' boot.img into the phone
because i can see the fastboot screen (blue screen) it say ''writing boot: error out of space'' the system.img flashes perfectly
when i flash through recovery it always says ''error while flashing boot.img''
please help this is my last hope before going back to 2.1 again
thx in advance
have you tried
fastboot erase boot ?
Or enter recovery -> mount and storage -> format BOOT
and try to flash boot again.
pebe94 said:
have you tried
fastboot erase boot ?
Or enter recovery -> mount and storage -> format BOOT
and try to flash boot again.
Click to expand...
Click to collapse
ive done the first thing but im going to try the second one in recovery
thx
no that hasnt worked
it says this on the fastboot screen:
flash_write_image:bad block 390
flash_write_imageut of space
and it says this in cmd when i write command
sending boot OKAY
writing boot FAILED remote: flash write failure
mohnim said:
no that hasnt worked
it says this on the fastboot screen:
flash_write_image:bad block 390
flash_write_imageut of space
and it says this in cmd when i write command
sending boot OKAY
writing boot FAILED remote: flash write failure
Click to expand...
Click to collapse
Try flashing a fastboot KDZ again. (Use Mur4ik's 234 data one) Do it in CS_Emergency mode. Then go into fastboot and do the following:
fastboot erase boot
fastboot erase system
fastboot -w
fastboot flash recovery <name of recovery file>.img
fastboot reboot
Click to expand...
Click to collapse
Just a theory, not sure if it will work or not. Hope it works.
effortless. said:
Try flashing a fastboot KDZ again. (Use Mur4ik's 234 data one) Do it in CS_Emergency mode. Then go into fastboot and do the following:
Just a theory, not sure if it will work or not. Hope it works.
Click to expand...
Click to collapse
do you where i can get mur4ik's 234 data ?
mohnim said:
do you where i can get mur4ik's 234 data ?
Click to expand...
Click to collapse
Here: http://www.mediafire.com/?gxawu4ava7kt69x
(Thanks fishears for uploading)
effortless. said:
Here: http://www.mediafire.com/?gxawu4ava7kt69x
(Thanks fishears for uploading)
Click to expand...
Click to collapse
thx
i'll give it a try know
i installed mir4ik 234 data but know it's stuck on the lg logo
wat should i do?
This is normal. Flash custom rom now.
no it didnt work same problem
any other solutions
It's very strange, different devices have bad blocks in different places. For example, My GT540 has a bad block when erasing the data partition. My old, bricked, GT540 had a bad block on the system partition. It may be that the bad block ended up on your boot partition and may cause issues. Just a theory and its probably wrong, just guessing
effortless. said:
It's very strange, different devices have bad blocks in different places. For example, My GT540 has a bad block when erasing the data partition. My old, bricked, GT540 had a bad block on the system partition. It may be that the bad block ended up on your boot partition and may cause issues. Just a theory and its probably wrong, just guessing
Click to expand...
Click to collapse
do you know how to fix this bad block on boot partition
the wierd thing is that i never get this error when updating cm7 it works perfectly on that no error
another thing is that on the fastboot screen it say's
''flash write image: out of space''
how could it be out of space
where is the boot image stored inside the phone?
what size have desired boot.img ?
pebe94 said:
what size have desired boot.img ?
Click to expand...
Click to collapse
i have no idea
but i know the boot.img of cm7 works perfectly
maybe i need to be the same size as the cm7
Does the size of boot.img matter because in the fastboot screen it says ''flash write image: out of space ''
Sent from my GT540 using XDA App
What size is the boot.img?
Sent from my GT540 using XDA Premium App
eoghan2t7 said:
What size is the boot.img?
Sent from my GT540 using XDA Premium App
Click to expand...
Click to collapse
I think its 5kb
Sent from my GT540 using XDA App
I have the same problem!!
Expect I can flash through fastboot!!
anyone know a solution?
Sent from my GT540 using Tapatalk
androidboss7 said:
I have the same problem!!
Expect I can flash through fastboot!!
anyone know a solution?
Sent from my GT540 using Tapatalk
Click to expand...
Click to collapse
Have you tried
Fastboot erase boot
Fastboot flash boot boot.img
Sent from my GT540 using xda premium
I have tried several times to flash a custom recovery on my Atrix HD but after I send the "flash recovery recovery.img " command, it replies in cmd that " command restricted .failed (remote failure). What am I doing wrong. And also can I flash the recovery with Tom manager and how? Thanks
Sent from my MB886 using xda premium
penser
kwartey said:
I have tried several times to flash a custom recovery on my Atrix HD but after I send the "flash recovery recovery.img " command, it replies in cmd that " command restricted .failed (remote failure). What am I doing wrong. And also can I flash the recovery with Tom manager and how? Thanks
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Mandatory question: Is your bootloader unlocked?
You need to use the command "fastboot flash recovery recovery.img". And what is Tom manager?
penser said:
And what is Tom manager?
Click to expand...
Click to collapse
I assume a GPS software.? Lol
Edit:
I think he referred to Rom Manager which to his answer is yes he can eventhough phils recovery seen to me much stable and is more up to date then the cwm itself
penser said:
Mandatory question: Is your bootloader unlocked?
You need to use the command "fastboot flash recovery recovery.img". And what is Tom manager?
Click to expand...
Click to collapse
Yes my bootloader is unlocked. I have used that command but still the same outcome. I flashed the stock rom again. Am gonna try flashing the recovery again.
Sent from my MB886 using Tapatalk
I have the same problem. Neither installing "safetrap recovery" app.
A252 said:
I have the same problem. Neither installing "safetrap recovery" app.
Click to expand...
Click to collapse
Your trying to install safestrap? Don't.
Sent from my PACMAN MATRIX HD MAXX
[OTA] Android 4.3 Sense 5.5 CID__622 Hong Kong
http://yadi.sk/d/egZKl5cUEceWN
An69 said:
[OTA] Android 4.3 Sense 5.5 CID__622 Hong Kong
http://yadi.sk/d/egZKl5cUEceWN
Click to expand...
Click to collapse
Nice
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
An69 said:
[OTA] Android 4.3 Sense 5.5 CID__622 Hong Kong
http://yadi.sk/d/egZKl5cUEceWN
Click to expand...
Click to collapse
Flash through custom recovery?
No, only stock!
tropical cactus said:
Flash through custom recovery?
Click to expand...
Click to collapse
Have to use stock recovery lol
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
daorderdillon said:
Have to use stock recovery lol
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So after going back to stock, how to flash?
tropical cactus said:
So after going back to stock, how to flash?
Click to expand...
Click to collapse
That's a noob question u don't know how to flash and ota via stock recovery
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
daorderdillon said:
That's a noob question u don't know how to flash and ota via stock recovery
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have Super CID, you won't get an update. You need CID 622.
tsokh said:
If you have Super CID, you won't get an update. You need CID 622.
Click to expand...
Click to collapse
Lol I got my update and I have super cid
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
daorderdillon said:
That's a noob question u don't know how to flash and ota via stock recovery
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Haven't had the need to so am a noob. I'm only interested in the firmware. So if you were to write a guide, other noobs might learn as well and your thanks meter might go up further.:fingers-crossed:
tropical cactus said:
Haven't had the need to so am a noob. I'm only interested in the firmware. So if you were to write a guide, other noobs might learn as well and your thanks meter might go up further.:fingers-crossed:
Click to expand...
Click to collapse
Flash stock Rom 1.23.708 via custom recovery but don't install root wen u reboot and then use fastboot and flash stock recovery using this command fastboot flash recovery recovery.img when u boot search for updates
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
tropical cactus said:
Haven't had the need to so am a noob. I'm only interested in the firmware. So if you were to write a guide, other noobs might learn as well and your thanks meter might go up further.:fingers-crossed:
Click to expand...
Click to collapse
If you need only firmware, download it here https://www.dropbox.com/s/q1w1wm2yo4txl8e/firmware.zip
and place it in folder with android adb files.
Instructions:
1) connect phone to computer with USB debugging enabled
2) in Windows command line:
cd "path to android adb files"
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip (If you see failed message, just run this command again and wait till it finishes updating)
fastboot reboot-bootloader
fastboot reboot
tsokh said:
If you need only firmware, download it here https://www.dropbox.com/s/q1w1wm2yo4txl8e/firmware.zip
and place it in folder with android adb files.
Instructions:
1) connect phone to computer with USB debugging enabled
2) in Windows command line:
cd "path to android adb files"
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot-bootloader
fastboot reboot
Click to expand...
Click to collapse
Thanks, man. You've always been a great help.
daorderdillon said:
Lol I got my update and I have super cid
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which way did you supercid?
Sent from my HTC One using Xparent BlueTapatalk 2
daorderdillon said:
Flash stock Rom 1.23.708 via custom recovery but don't install root wen u reboot and then use fastboot and flash stock recovery using this command fastboot flash recovery recovery.img when u boot search for updates
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I followed this exactly. But It always shows me that I have modified version of android.
ebautista said:
I followed this exactly. But It always shows me that I have modified version of android.
Click to expand...
Click to collapse
I just managed to finish the process successfully, you might want to try to redownload the zip of 1.23.708.3, your copy might be broken or something.
tsokh said:
If you need only firmware, download it here https://www.dropbox.com/s/q1w1wm2yo4txl8e/firmware.zip
and place it in folder with android adb files.
Instructions:
1) connect phone to computer with USB debugging enabled
2) in Windows command line:
cd "path to android adb files"
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip (If you see failed message, just run this command again and wait till it finishes updating)
fastboot reboot-bootloader
fastboot reboot
Click to expand...
Click to collapse
For some reason, the flash zip command always seems to fail for me:
Code:
$ fastboot flash zip firmware.zip
< waiting for device >
sending 'zip' (46275 KB)...
OKAY [ 2.707s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 4.223s
Anyone have any idea? (Not that it matters that much, in the end I got the firmware update applied by applying the whole OTA update...)
firmware zip
Worked for me. I'm S-off and supercided.
tropical cactus said:
Worked for me. I'm S-off and supercided.
Click to expand...
Click to collapse
Ah, of course, I forgot that my phone's still S-ON and that this might play a factor.
ebautista said:
I followed this exactly. But It always shows me that I have modified version of android.
Click to expand...
Click to collapse
Missing some apps or your rooted
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
koniiiik said:
Ah, of course, I forgot that my phone's still S-ON and that this might play a factor.
Click to expand...
Click to collapse
Now my turn to ask you. Now I'm on hboot 1.55, is it still ok to flash stock Rom with hboot 1.54 so I can get the official update to see if it's as fast as some people claim?
Hello everybody. I'm having some problems flashing TWRP after unlocking the bootloader.
First of all, after unlocking the BL, I have flashed back the stock logo using
Code:
fastboot flash logo logo.bin
Then I tried flashing TWRP.
Code:
fastboot flash recovery recovery.img
Everything is successful, but booting to recovery from bootloader turns the phone off, and using
Code:
adb reboot recovery
brings about a 'dead android' screen with 'No command' written below it. I had to force reboot.
The phone itself works fine, and I was able to boot to TWRP, using the same .img file,
Code:
fastboot boot recovery.img
, and flash SU and whatever.
I don't really have a clue about what's going on here, can anybody point me in the right direction?
Thanks in advance
Nevermind, solved using TWRP manager app, and flashing the recovery from Android. Still don't know why I wasn't able to flash recovery from fastboot.
totalnoob34 said:
Nevermind, solved using TWRP manager app, and flashing the recovery from Android. Still don't know why I wasn't able to flash recovery from fastboot.
Click to expand...
Click to collapse
I think you should use mfastboot instead of fastboot
Sent from my XT1068 using XDA Free mobile app
ggunzio said:
I think you should use mfastboot instead of fastboot
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Mfastboot? I am using Linux, I think that it's for Windows only. Anyway, I don't think the problem is on computer side, since the commands were successful both on the pc and the phone.
ggunzio said:
I think you should use mfastboot instead of fastboot
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
I used fastboot for the same thing and it worked flawlessly.
Can anyone advise me off the fastboot command to save a copy of my recovery image before I flash the new one please.
Burtrum57 said:
Can anyone advise me off the fastboot command to save a copy of my recovery image before I flash the new one please.
Click to expand...
Click to collapse
You can't "pull" from fastboot. The protocol doesn't work like that sadly. What you can do though, is download a kernel from the forums here on xda and:
Flash recovery image to boot partition:
fastboot flash boot <recovery.img>
Battery pull (or reboot) and do a normal boot
It'll boot into recovery.
Backup recovery parition.
Reboot to fastboot
Flash kernel back:
fastboot flash boot <kernel boot.img>
Flash recovery to correct spot:
fastboot flash recovery <recovery.img>
Sent from my 0PCV1 using XDA Free mobile app
Many thanks for that. It worked and now I have CWM recovery. And the first thing I did with it was ???? Make a backup and save that on my computer for just in case!!
Something like this
Code:
dd if=/dev/block/mmcblk0p41 of=/mnt/media_rw/ext_sd/recovery.img
should do it.
Burtrum57 said:
Can anyone advise me off the fastboot command to save a copy of my recovery image before I flash the new one please.
Click to expand...
Click to collapse
Burtrum57 said:
Many thanks for that. It worked and now I have CWM recovery. And the first thing I did with it was ???? Make a backup and save that on my computer for just in case!!
Click to expand...
Click to collapse
do you have it on Desire 510 64 bit ?
how i can get it ?