HTC powered by Android with new logoHey I just modified the splash stock splashscreen with the new amazing android logo vzw posted by Tigerstown to work with international models
Instructions:
connect phone to the pc, with debug
SHIFT+right click on the adb folder
open cmd prompt here
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip htc-new-splash.zip
fastboot reboot
enjoy
CREDITS: Tigerstown for providing base file
attached screenshot and .zip file
Thread closed,
This thread has been closed as there is existing threads regarding splash screens already in this forum eg: <splash,screens>collection. Please remember forum rules and use existing threads were possible.
Many thanks,
Ghost
Related
Hi everyone,
I have looked everywhere on google and have been at this for over 5 hours now. I have tried rooting my phone from 3 different PCs (XP SP3, SP2 and 7). With all of them i have managed to get the drivers for adb installed (after many problems) and got all the way to the fastboot part of the rooting.
Once i get there, i have the same problem on all 3 PCs. ADB can no longer find my phone! Following the instructions, i checked for the device before i powered it off and found it by doing abd devices in cmd prompt. The moment the device is powered off and then back on, bam! No more device!
I am at my wits end at this point and just don't know what else I could possibly do! I would be immensely grateful for ANY advice.
I did check that my device allowed USB debug so that's not it either.
Also, my phone is a Rogers phone and I have just put through the upgrade they sent this morning.
adb cant find your phone in fastboot mode but fastboot can
Try writing fastboot devices instead of adb devices
All the comands in fastboot mode start with fastboot...e.g fastboot flash xxx xxx.img
I ran into this problem as well on my attempt, I forgot to re-enable (or enable) depending on where I was at "usb debugging" which is in:
settings> applications > development > check the usb debugging box.
After that, when you do abd devices in your shell, it should surely list after that. Good luck!
edit-- woops scratch that.. sorry I just read back that you made sure of that.
Thank you for that!
Now, i see it in fastboot, but when i try typing fastboot boot recovery.img i get a "cannot load recovery.img"
Sorry, apparently i need a lot more hand holding than i though!
(this is where I am getting the instructions from HowardForums. I'd post the link but I can't do that yet on this forum...
Basically, these are the instructions i am following:
If the phone you have is an HTC Magic (no hardware keyboard), the method is pretty much the same. I modified Haykuro's zip with files that were meant for the Magic. You can grab it here:
*link*
Again, open another command prompt as steps 2, and 6-8 are entered in the command prompt.
Quote:
Originally Posted by Haykuro-ish
0. Place update.zip on SD card.
1. power off the phone and boot into fastboot (hold back and power)
2. fastboot boot recovery.img
3 [optional]. make a backup with nandroid
3. apply update. (LET IT FINISH, DO NOT TOUCH ANYTHING UNTIL YOUR PHONE IS COMPLETELY IDLE. DO NOT TOUCH AFTER FIRST REBOOT (WHEN CHIP APPEARS) UNLESS YOU LIKE A BRICK. )
4. reboot out of recovery mode.
5. power off phone, hold back button and power to boot into fastboot again
6. fastboot flash boot boot.img
7. fastboot flash recovery recovery.img
8. fastboot reboot
enjoy!
These are pretty much the Haykuro instructions for the Dream, which I modified to apply to the Magic. The boot and recovery images were made by Amon_RA. Happy Rooting!
Just like with the Dream, the first part flashes a good SPL, the second flashes a rooted boot and recovery. The easiest way to test if the device is rooted is to open another command prompt in the tools dir and type
Code:
adb root
If it returns that adb is already running in root, then you're all set.
Click to expand...
Click to collapse
Am i doing something wrong?
Thanks so much!
You need to navigate to the folder where you saved your recovery.img
For example if you put it on d:/Android dev. you will need to do (inside cmd)
d: (switches to drive d
cd d:/Android dev. (changes the folder to android dev.)
and then issue the fastboot command
without the brackets of course...
eyegor said:
You need to navigate to the folder where you saved your recovery.img
For example if you put it on d:/Android dev. you will need to do (inside cmd)
d: (switches to drive d
cd d:/Android dev. (changes the folder to android dev.)
and then issue the fastboot command
without the brackets of course...
Click to expand...
Click to collapse
Again, thank you so much! It seems I am still having issues as now I'm being told that "remote not allow".... is this a rogers thing?
Again i do apologize for all the hand-holding necessary here
yes, i am getting this <remote:not allow> message too. I was able to fix my other magic (purchased in october) via fastboot boot recovery.img but not this new one i have (purchased in Dec).
Anyone have any ideas how to bypass this block of 'remote, not allowed"?
Here is a simple splash screen I made.
1. Unzip into tools folder
2. Boot into fastboot
3. In ADB put this command
fastboot flash splash1 evosplash1.rgb565
Looking good!
Why does it keep tellimg me it cant be loaded im in fastboot i run the command as u posted i run fastboot devices and it shows my device evosplash1.rgb565 in in the sdk tools folder am i missing something plz help ?? thanks
Im trying to get my new XOOM from unlock to root and having a nightmare!
I have read and followed guides from the forum but still can't get the new recovery on?
I have done fastboot oem unlock and followed the instructions on the tab and at the end it says complete. Next once it reboots enabled usb debugging and rebooted into bootloader, all ok so far but when I try to run the command "fastboot flash recovery recovery-tiamat-r4c-100611-1150-cwm.img" it comes up with "cannot load"? I have tried with and without the. img at the end and also renamed the file "recovery" and "recovery.img" and still the same thing.
Has anyone had this same problem and can get me back on track please.
Sent from my MZ604 using xda premium
(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img
Ok, will give it a try when I get to my computer and will report back.
Thank you
Sent from my Desire HD using xda premium
Our Indian cricket team is in your country desperately need a win
rohit3192 said:
(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
nope that didnt work, same thing error: cannot load 'recovery.img
ok now im getting someware
still not working but when i do adb devices it says list of devices attached but nothing?
Just a note usb debbuging is on
Sent from my MZ604 using xda premium
rohit3192 said:
(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, it really doesn't matter if all your files that you need are in Tools or Platform tools, as long as they are all in there and your command window is operating out of that folder.
Second, you are making a good point re: the img file extension...in Windows, it sometimes is set to hide file extensions, so it is possible that someone could already have the img file extension there and not see it and add it again, making recovery.img.img which of course wouldn't work.
I don't think this is the OP's problem, but you never know.
I was one of many that were looking for a extremely long boot time fix on my M8 with (for me) the best rom - ViperONE. Just yeasterday I've found a an easy fix. If the solution was already posted... feel free to delete this post, sorry... so far I could not find it.
Please follow this simple guide > LINK
Firmware you need to install is m8.44.3.firmware.zip > LINK
ADB installer 1.3 > LINK
Directions:
"Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader"
I'm running Verizon M8 in Europe (bought in in US) and have absolutely no issues.
CREDIT TO dottat and Tigerstown.
Download
Search for TWRP recovery for LG V10 H901 (File: twrp-2.8.7.0-h901.img (31.7 MB))
Backup Apps and Data
While this process should not wipe any of your data, a backup is highly recommended. Once you install a custom recovery like TWRP, make sure you backup your system, data,etc. from the recovery. It will be helpful in case anything goes wrong.
Prerequisites
This guide is compatible with LG V10 H901 only. Do not try it on any other devices or variants.
Unlocked bootloader is required to install a custom recovery like TWRP on your device. Click here.
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
Install Motorola USB Drivers on your computer.
Open Settings> Developer options and enable USB Debugging on your device.
Go to Developer options and enable Allow oem unlock.
How to Install TWRP Recovery on LG V10 H901
Download the recovery image file. Extract if in case a zip file. Now transfer the file to your PC where you can easily locate it.
Make sure you have setup ADB and fastboot on your PC. Also accept Always allow from this computer when you plug in the device for first time to enable USB Debugging.
Now power off your device and unplug it from your PC.
Boot into the bootloader or fastboot mode. To do so, press and hold volume down and the power button simultaneously for 5-6 seconds. When you see the bootloader screen, connect your device to the PC using a USB cable.(Choose fasboot if option is available) Alternatively, you can also issue the following command through your cmd or terminal, while connected to the PC in order to boot into the bootloader.
"adb reboot bootloader"
Navigate to the location where you have placed the recovery file. Rename the recovery file to a simple one, like recovery.img. While the folder with recovery.img file is open, hold shift key on keyboard and right-click on an empty space and select “Open command window here” option to launch a cmd window.
Now issue the following command in the command prompt to check your device connectivity
"fastboot devices"
Now flash custom recovery. Issue the following command for that.
"fastboot flash recovery recovery.img"
Custom recovery will now be installed on your device. Now boot your phone in recovery mode. You can do this by turning your device off and then press and hold volume down and power keys at the same time. Or you can simply enter the following command.
"fastboot boot recovery.img"
Once into the recovery, you can backup your current ROM, data, EFS and more.
Once you have installed TWRP, you are all set to install custom packages onto the device’s system. Alternatively, while on Linux or Mac OS, you can issue “./fastboot flash recovery recovery.img” command to flash the TWRP recovery.
Root
As you already have TWRP, simply flash the SuperSU file (version 2.56) to gain root access
@TheJesus @KAsp3rd, thanks guys for everything you've done over the past few days. no shade to @joe01gun but if people are going to use these instructions make sure you search the rest of the forum for what thejesus and kasp3rd put together to get us to this point - definitely appreciated. thanks @joe01gun for putting these additional instructions together.
Your post says the following:
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
yet, there's no link to the necessary files to "unzip" them. Any suggestions?
Thank you for the help, but where do we get fastboot set up on our PCs? Yes, this is getting confusing with the steps outlined above. I followed the first step and had to take out the battery because I was stuck in fastboot screen with small tiny text in the top left that didn't respond to any manipulation with the volume keys on the back of the device and wouldn't restart any way until I took out the battery.
sanjsrik said:
Your post says the following:
Set up ADB and Fastboot on your computer. You can download the minimal ADB and fastboot tool from here (unzip it) or get the quick ADB and fastboot installer from here.
yet, there's no link to the necessary files to "unzip" them. Any suggestions?
Click to expand...
Click to collapse
I think it's cause he's not allowed to post links yet cause he's too new. I followed this guide http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
You can get twrp from the development forum.
Why
Intended to put the information condensed....
Yep....new
Links could not be uploaded.
joe01gun said:
Intended to put the information condensed....
Yep....new
Links could not be uploaded.
Click to expand...
Click to collapse
Your condensed thread is more convoluted than the actual development thread which also includes the links to everything.
I'm still wondering why you have install Motorola USB drivers for an LG phone..
Understood
Understood
The one on development is straightforward and I managed to make it done.
If you don't lock the bootloader back, you will see bootloader unlocked when starting up.
If you have root enabled file explorer, you should remove /system/priv-app/adaptclient folder to avoid annoying root request from adapt.
Please use the main dev thread for instructions on what to do, found below. Having duplicates for what is essentially the same thing can cause confusion and just takes up unnecessary space. So I have closed the thread.
[Recovery][LG-H901] Unofficial TWRP
Forum moderator,
matt4321