recently i entered the android world and already want to make some changes...
i want to change boot image... not boot animation... boot image! the image that apears right after LG logo... on my case it says "SWIFTDROID SECOND LIFE" or something like that... and i want to change it to a custom image that i pick... how can i do it?
thanks
flash new boot.img
I think the only way is flash new boot .img (which is in rom).
Do this: copy that boot.img which you want in your computer C: drive.
2.put your phone into fastboot and put it your computer,you need
also fastboot.exe in your C drive
3. Run cmd and type: cd :C/fastboot.exe flash boot boot.img
Reboot.
You can change it by editing the boot.img.
You change initlogo in boot.img
KuaQ said:
You change initlogo in boot.img
Click to expand...
Click to collapse
I have done that. But the initlogo is on .rle file extension and i cant open it. Ive replaced that image for a .png image and repacked boot.img and then reflashed. Phone got stuck on lg logo.
and in some roms there's not an initlogo... :S what file should i replace? and how? i've used this tut http://forum.xda-developers.com/showthread.php?t=1630130
and i've managed to do everything right but now i dont know what file to replace... :S
What i did wrong?
Sent from my GT540 using Tapatalk 2
carequinhasebas said:
I have done that. But the initlogo is on .rle file extension and i cant open it. Ive replaced that image for a .png image and repacked boot.img and then reflashed. Phone got stuck on lg logo.
and in some roms there's not an initlogo... :S what file should i replace? and how? i've used this tut http://forum.xda-developers.com/showthread.php?t=1630130
and i've managed to do everything right but now i dont know what file to replace... :S
What i did wrong?
Sent from my GT540 using Tapatalk 2
Click to expand...
Click to collapse
i've manage to successufly change boot image, but now my doubt lies on , if a boot.img doesnt have a initlogo, i can just put one in there and repack? would that work?
thanks
Your png file must be converted to rle
Niquel97 said:
I think the only way is flash new boot .img (which is in rom).
Do this: copy that boot.img which you want in your computer C: drive.
2.put your phone into fastboot and put it your computer,you need
also fastboot.exe in your C drive
3. Run cmd and type: cd :C/fastboot.exe flash boot boot.img
Reboot.
Click to expand...
Click to collapse
Na, That would replace the kernel
Sent from my Sony Tablet S using xda premium
Related
Good day,
I unlocked my bootloader just a second ago and i downloaded FX114 , CM9 anzu
After this i did fastboot -i 0xfce flash boot boot.img
i got the boot.img file from the CM9 zip but now i can only enter fastboot mode , how can i get this working ? because i'm kinda stuck now
haydar100 said:
Good day,
I unlocked my bootloader just a second ago and i downloaded FX114 , CM9 anzu
After this i did fastboot -i 0xfce flash boot boot.img
i got the boot.img file from the CM9 zip but now i can only enter fastboot mode , how can i get this working ? because i'm kinda stuck now
Click to expand...
Click to collapse
When you flash the CM kernel, use this command:
fastboot flash boot boot.img
And then flash the rom and gapps via recovery
And please use Q&A forum next time
zangetsu2188 said:
When you flash the CM kernel, use this command:
fastboot flash boot boot.img
And then flash the rom and gapps via recovery
And please use Q&A forum next time
Click to expand...
Click to collapse
Sorry, my bad but i just downloaded this zip file "update-cm-9.0.0-anzu-Unofficial-signed2.zip inside the zip file there is a file called boot.img i flashed this one with the fastboot. But i cant do anything i just get a grey screen nothing more. however i can enter fastboot.
Ty for helping me out <3
haydar100 said:
Sorry, my bad but i just downloaded this zip file "update-cm-9.0.0-anzu-Unofficial-signed2.zip inside the zip file there is a file called boot.img i flashed this one with the fastboot. But i cant do anything i just get a grey screen nothing more. however i can enter fastboot.
Ty for helping me out <3
Click to expand...
Click to collapse
Extract the file you downloaded. Copy the .zip inside it and paste it to you sd card. Did you manage to flash the kernel? I.e. phone already boots woth fxp kernel logo.
Sent from my LT15i using XDA
haydar100 said:
Sorry, my bad but i just downloaded this zip file "update-cm-9.0.0-anzu-Unofficial-signed2.zip inside the zip file there is a file called boot.img i flashed this one with the fastboot. But i cant do anything i just get a grey screen nothing more. however i can enter fastboot.
Ty for helping me out <3
Click to expand...
Click to collapse
I got recovery etc working but now i'm trying to flash acronium etc but it just hangs hangs after the "DoomKernel" logo
zangetsu2188 said:
Extract the file you downloaded. Copy the .zip inside it and paste it to you sd card. Did you manage to flash the kernel? I.e. phone already boots woth fxp kernel logo.
Sent from my LT15i using XDA
Click to expand...
Click to collapse
I just flashed doomkernel on it, and also after that i flashed with CWM acronium and mooded ICS but nothing works. I can still enter recovery etc, i also followed the instructions 100% guess i'm missing something crucial :S
Hi guys! I downloaded the "A500BootLogo_105_v8plus_win" tool that changes the boot logo of the bootloader, opened the "bootloader_v8_blue.bin" and changed the splash screen and some colors, saved it and flashed through the fastboot, but when I restart my A500, nothing happens. Any guess?
If you want to update bootloader using fastboot you need to modify and use the blob file instead of bin.
Bin file can be successfully flashed only by downloading it to tablet with nvflash in APX mode.
I tried to update as *.blob but still nothing happend.
Do I have to put a specific name to flash? (I named it custombootloader.blob)
I'm using the command "fastboot flash recovery custombootloader.blob"
Is that right?
Why are you flashing recovery partition with bootloader? The update command is: fastboot flash bootloader custombootloader.blob . The tablet will automatically reboot after the flashing finishes.
verzzolla said:
I tried to update as *.blob but still nothing happend.
Do I have to put a specific name to flash? (I named it custombootloader.blob)
I'm using the command "fastboot flash recovery custombootloader.blob"
Is that right?
Click to expand...
Click to collapse
You can't just "re-name" a file to xxxxxxxxxx.blob. Won't work (at least I wouldn't do it that way). You have to save the file as a true "blob". Surprised you didn't fubar the tab
In the bootloader app., ckick the dropdown at the bottom, and you can save it as a "blob" file instead of "bin"
MD
Thanks very much Skrilax_CZ, it worked!
That was the problem.
@Moscow Desire
That's what I did... saved it as *.blob.
The rename which I was referring was to the name of the file.
verzzolla said:
Thanks very much Skrilax_CZ, it worked!
That was the problem.
@Moscow Desire
That's what I did... saved it as *.blob.
The rename which I was referring was to the name of the file.
Click to expand...
Click to collapse
Great! Glad it's running.
Yeah, everytime somebody says "rename",,,,, ohhhhhhh....
I love the ones "update.zip.zip"
I have a new rooted and unlocked Nexus 7. I flashed a kernel and can't get past the nexus boot screen. My battery is about dead. What do I need to do! I have the tookkit, but I can't get it to do anything! Please help! My battery is almost gone!
Infuser86 said:
I have a new rooted and unlocked Nexus 7. I flashed a kernel and can't get past the nexus boot screen. My battery is about dead. What do I need to do! I have the tookkit, but I can't get it to do anything! Please help! My battery is almost gone!
Click to expand...
Click to collapse
And I don't have any backup ROMS or kernels to flash...
Infuser86 said:
And I don't have any backup ROMS or kernels to flash...
Click to expand...
Click to collapse
Battery just died. I could not turn it off. Everytime I tried to, it booted right back up. I was in recovery, but as I said, I have no roms or kernels to flash. I tried to mount the device, but was unsuccessful. I clicked mount system and nothing showed up on computer. Couldn't click mount sd card.
Someone please help me.
Always make a back up... we'll starting now
Let it charge, try again to get the proper kernel and flash in recovery. If it won't let you mount SD to transfer, extract the boot.img from the ROM you were using and flash via fastboot.
fastboot flash boot boot.img
fastboot reboot
See what happens
Sent from my Nexus 7 using xda premium
Can you please explain how to do that? I am new to the Nexus. I can get into Fastboot and then recovery. But how would I flash via flashboot. I do not see that option.
Edit
I do suggest reading up a bit on android or you are bound to find yourself in these situations. Also try and stay away from toolkits, you would already know what to do if you weren't using them
Download rom of choice to computer
Extract the boot.img from the .zip
After you charge nexus a bit, plug into computer and boot into bootloader
Open command/terminal on computer in the same location the boot.img is and type
fastboot devices
If you get 'waiting for device' you need to download the proper drivers, and or need to change directories to where fastboot.exe is located on PC, or just make sure you download everything from the platform-tools in the sdk and I recommend changing the path in environmental variables to include adb/fastboot
If you see your serial number proceed
fastboot flash boot boot.img
fastboot reboot
this should replace the kernel causing your boot loop with and all is well
Sent from my Nexus 7 using xda premium
demkantor said:
I do suggest reading up a bit on android or you are bound to find yourself in these situations. Also try and stay away from toolkits, you would already know what to do if you weren't using them
Download rom of choice to computer
Extract the boot.img from the .zip
After you charge nexus a bit, plug into computer and boot into bootloader
Open command/terminal on computer in the same location the boot.img is and type
fastboot devices
If you get 'waiting for device' you need to download the proper drivers, and or need to change directories to where fastboot.exe is located on PC, or just make sure you download everything from the platform-tools in the sdk and I recommend changing the path in environmental variables to include adb/fastboot
If you see your serial number proceed
fastboot flash boot boot.img
fastboot reboot
this should replace the kernel causing your boot loop with and all is well
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Learned that the hard way! So if I download the ParanoidAndroid ROM, just extract it and get the IMG file?
Infuser86 said:
Learned that the hard way! So if I download the ParanoidAndroid ROM, just extract it and get the IMG file?
Click to expand...
Click to collapse
Took the img from the ROM and fastbooted it and it wrote, but tablet won't load past Google screen...
So the only thing you did to cause it to get stuck originally was flash a kernel? If that was it and then Fashing the right kernel doesn't work and recovery won't let you Mount to put a ROM on SD, I would flash one of the official full ROM updates through fastboot.
There are a bunch of them posted here just grab one and flash it and she what happens
Sent from my Nexus 7 using xda premium
(SOLVED) Hello, today i decided to root my phone( Galaxy Grand Prime SM-G530F)using odin but i guess i used the wrong file. Odin said ''Restart'' and nothing happened, then i unplugged my phone. I wish I hadnt done this
When i try to turn my phone on, I only can see download mode and i guess it is called ''bootloop''. It says ''could not do normal boot''. I couldnt solve this problem using Odin because Odin doesnt see/recognise/find my phone. I checked the USB port drivers and my wire but i still cant fix the problem. Please help me, I am so desperate and cant afford a new phone :crying:
Does your Phone have fastboot and is your phone recognized by fastboot?
If yes Download your Firmware from sammobile.com (Registration needed) and unpack it
At this point I want to state, that I'm not Responible for any Hard- or Software-Damage. I'm just trying to help, because I think, that it can't get any worse
Windows:
Open up cmd as Administrator
Go into the Folder where fastboot is installed
Copy all the extracted .img files into the fastboot-folder
Run the following commands:
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img
fastboot.exe flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Linux:
Open up terminal as root (or use sudo before every command)
Go into the folder, where all the img files are stored
Run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Sent from my SM-G350 using XDA-Developers mobile app
TimSchumi said:
Does your Phone have fastboot and is your phone recognized by fastboot?
If yes Download your Firmware from sammobile.com (Registration needed) and unpack it
At this point I want to state, that I'm not Responible for any Hard- or Software-Damage. I'm just trying to help, because I think, that it can't get any worse
Windows:
Open up cmd as Administrator
Go into the Folder where fastboot is installed
Copy all the extracted .img files into the fastboot-folder
Run the following commands:
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img
fastboot.exe flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Linux:
Open up terminal as root (or use sudo before every command)
Go into the folder, where all the img files are stored
Run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Sent from my SM-G350 using XDA-Developers mobile app
Click to expand...
Click to collapse
Wot? Samsung phones don't have fastboot lol
Anyway try to remove the battery and enter ODIN mode normally, this should do it.
Oh, crap, i forgot
Sent from my SM-G350 using XDA-Developers mobile app
fabiossilva21 said:
Wot? Samsung phones don't have fastboot lol
Anyway try to remove the battery and enter ODIN mode normally, this should do it.
Click to expand...
Click to collapse
I tried to remove the battery but it didnt work
tunasdf said:
I tried to remove the battery but it didnt work
Click to expand...
Click to collapse
OMG IT WORKED AFTER TRYİNG THOUSAND TİMES thank you so much
tunasdf said:
OMG IT WORKED AFTER TRYİNG THOUSAND TİMES thank you so much
Click to expand...
Click to collapse
No problem! Glad you managed to fix it! Now remember to flash the right file
I accidentally wiped off everything with TWRP.
I have no backups.
I'm really having trouble finding ANY rom for this phone,custom or stock.
I've only found firmware that can update my OS not install it completely.
Could anyone find the correct ROM for me?
Anything will do.
Please help!
If you have a second device, donwload Huawei firmware finder from Play store. Enter your model number and donwload a full package. Doesn't really matter which one. Then just flash it in TWRP without extracting.
Vinnipinni said:
If you have a second device, donwload Huawei firmware finder from Play store. Enter your model number and donwload a full package. Doesn't really matter which one. Then just flash it in TWRP without extracting.
Click to expand...
Click to collapse
Is there any way to know my exact phone model number without having access to the OS?
Using the pc version I have to enter some kind of G and F values,what should i put in there?
EDIT:I've narrowed it down to WAS-LX1 and WAS LX1A,any way of distinguishing between those?
EDIT 2 : I seem to fail to flash literally any ROM,I get a zip verification error if i try to check that,if not I just get:
Updater process edned with ERROR : 9,and E: unknown command [errno] before that
Justkill43 said:
Is there any way to know my exact phone model number without having access to the OS?
Using the pc version I have to enter some kind of G and F values,what should i put in there?
EDIT:I've narrowed it down to WAS-LX1 and WAS LX1A,any way of distinguishing between those?
Click to expand...
Click to collapse
Shouldn't your phone model number be beneath the battery?
Michael24884 said:
Shouldn't your phone model number be beneath the battery?
Click to expand...
Click to collapse
Well yeah,it should.
But this is one of those phones that can't really be opened with special tools that I don't really have,and even if i did have them I wouldn't mess with the phone's insides because it's one of those types of phone....
Update:It may have something to do with the roms i have downloaded,I've tried 3 of them and none of them had ANY .img files
No boot.img no recovery.img etc,what am I doing wrong?
Justkill43 said:
Update:It may have something to do with the roms i have downloaded,I've tried 3 of them and none of them had ANY .img files
No boot.img no recovery.img etc,what am I doing wrong?
Click to expand...
Click to collapse
Huawei uses some special archiving, there should be an UPDATE.APP inside the downloaded files. You need a tool called Huawei Update Extractor to get the .img files.
Vinnipinni said:
Huawei uses some special archiving, there should be an UPDATE.APP inside the downloaded files. You need a tool called Huawei Update Extractor to get the .img files.
Click to expand...
Click to collapse
Oh I see,and should I just get the .imgs out of the update.app and then flash the rom?
Because so far I can't flash any of them,I get these errors:
E: unknown command [errno]
And
Updater process ended with ERROR : 9
Justkill43 said:
Oh I see,and should I just get the .imgs out of the update.app and then flash the rom?
Because so far I can't flash any of them,I get these errors:
E: unknown command [errno]
And
Updater process ended with ERROR : 9
Click to expand...
Click to collapse
What did you type?
Ohh and where are you from?
Vinnipinni said:
What did you type?
Ohh and where are you from?
Click to expand...
Click to collapse
What did i type??
Serbia.
Justkill43 said:
What did i type??
Serbia.
Click to expand...
Click to collapse
Yeah, mean the fastboot command you used
Vinnipinni said:
Yeah, mean the fastboot command you used
Click to expand...
Click to collapse
Kinda confused now,as I don't think I've used any fastboot commands at all.
Justkill43 said:
Kinda confused now,as I don't think I've used any fastboot commands at all.
Click to expand...
Click to collapse
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img
Vinnipinni said:
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Oh so I should just flash those 3 imgs instead of the whole zip?
Also there is no cust.img
I'll list all the imgs here so you can see what i should be able to flash:
-Boot
-Crc.img
-Curver.img
-DTS.img
-EFI.img
-FASTBOOT.img
-FW_HIFI.img
-FW_LPM3.img
-MODEM_FW.img
-PACKAGE_TYPE.img
-PRODUCT.img
-RECOVERY.img
-RECOVERY2.img
-SENSORHUNB.img
-SHA256RSA.img
-SYSTEM.img
-TEEOS.img
-TRUSTFIRMWARE.img
-VENDOR.img
-VERLIST.img
-XLOADER.img
Justkill43 said:
Oh so I should just flash those 3 imgs instead of the whole zip?
Also there is no cust.img
I'll list all the imgs here so you can see what i should be able to flash:
-Boot
-Crc.img
-Curver.img
-DTS.img
-EFI.img
-FASTBOOT.img
-FW_HIFI.img
-FW_LPM3.img
-MODEM_FW.img
-PACKAGE_TYPE.img
-PRODUCT.img
-RECOVERY.img
-RECOVERY2.img
-SENSORHUNB.img
-SHA256RSA.img
-SYSTEM.img
-TEEOS.img
-TRUSTFIRMWARE.img
-VENDOR.img
-VERLIST.img
-XLOADER.img
Click to expand...
Click to collapse
Yes! You can't flash most of it, it's not possible.
Flash Boot, Recovery, System and Vendor. Of that doesn't work, Put the UPDATE.APP into the dload folder on your SD and hold Power, Volume + and Volume -. That should force the flash of the update.
And if that still doesn't work, ask for a TWRP update on the P10 Forums. Then Restore everything except Data.
Vinnipinni said:
If you want to flash the .img files, you have to enter your Bootloader. Do this by booting TWRP and type adb reboot bootloader. Then, out the .img files into the adb/ fastboot folder and type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cust cust.img
Instead of system.img you need to use the exact filename of the system.img file. I think you need to only use these three commands, but I'll have another look.
Edit: you could also replace your current recovery and then try to flash the update file with the stock recovery. Do this by typing fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Alright,I'm getting the hang of this.
But what did you mean with the exact filename of system.img?How do i find that out?
Justkill43 said:
Alright,I'm getting the hang of this.
But what did you mean with the exact filename of system.img?How do i find that out?
Click to expand...
Click to collapse
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG
Vinnipinni said:
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG
Click to expand...
Click to collapse
Got it,flashed system,recovery and boot
Trying to flash vendor I get an error when it's trying to write vendor:
FAILED (remote:Command not allowed)
Still stuck in a boot loop.
I'm gonna put the update.app in the sdcard.
I just create a dload folder in the sd card,put it in,wipe off everything I've flashed and do the 3 button thing,right?
Vinnipinni said:
Just the name of the file. Don't know if it's sytsem.img or SYSTEM.IMG
Click to expand...
Click to collapse
UPDATE: Failed the 3 button thing,maybe I got the wrong ROM,i'll try it with another one,I have a question though
My friend has the same phone as me(p10 lite) and when he goes to about phone and checks out the model number he only sees WAS-LX1
I'm pretty sure i have that same model number now but I can't find a ROM that's specifically WAS-LX1,it's always WAS-LX1 And something added on there like WAS-LX1C02,should I even worry about that?
Vinnipinni said:
Yes! You can't flash most of it, it's not possible.
Flash Boot, Recovery, System and Vendor. Of that doesn't work, Put the UPDATE.APP into the dload folder on your SD and hold Power, Volume + and Volume -. That should force the flash of the update.
And if that still doesn't work, ask for a TWRP update on the P10 Forums. Then Restore everything except Data.
Click to expand...
Click to collapse
After trying the first 2 methods I can't even boot into twrp anymore,I'm super screwed...