Here is a Splash Screen i wanted to share with the community, It's simple just the original with inverted colors
Please enjoy.
As always please backup before trying, I won't be responsible for anything that may go wrong if this fails
and mods if this is posted in the wrong place please move thanks
{
"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"
}
To apply just unzip the contents of the package below into the tools folder of the android sdk
How-to Enter fastboot mode .... While the phone is off hold down "Volume down key" and then "power button" hold both till you get a white screen with the androids and skateboards
to confirm your device is seen by adb use this command
Code:
fastboot devices
you should see your phone listed under the command you just typed. After that type the next command to flash the splash image
Code:
fastboot flash splash1 splash1.nb
Then you should see that it was successful and rebbot the phone and preview your new image by typing
Code:
fastboot reboot
Please Thank and post comments as needed, if there is any trouble i'll try to help if i can i'm rather busy lately...lol
There was a huge thread on how to change splash with win 7 and I am stuck in osx thanks for a tut on how to to it in fastboot
Thanks! I followed the instructions and applied it no problem. Makes booting up look seamless with Fresh's bootscreen
So I have been having nothing but problems with Sync, so have rooted, flashed and changed boot image by using a root file manager (which all have worked fine).
Where on the EVO is the splash screen logo located, so I can just manually apply it?
Thank you
Criim
Criimson said:
So I have been having nothing but problems with Sync, so have rooted, flashed and changed boot image by using a root file manager (which all have worked fine).
Where on the EVO is the splash screen logo located, so I can just manually apply it?
Thank you
Criim
Click to expand...
Click to collapse
I'm 99.9% sure that this image cannot be simply replaced in a folder but must be flashed, at least that's how it was for winmo
If you think about it this is where the carrier brands the phone the most, im pretty positive this is flashed to a specific partition
Am I missing something? I do everything step by step and it won't find fastboot command in the terminal (using OS X). I can't do anything.
JSZESZE said:
I'm 99.9% sure that this image cannot be simply replaced in a folder but must be flashed, at least that's how it was for winmo
If you think about it this is where the carrier brands the phone the most, im pretty positive this is flashed to a specific partition
Click to expand...
Click to collapse
Hmm that's too bad. My Vista sees my EVO, but it has an exclamation mark and the driver won't initialize no matter what I try.
Guess I'll wait till some other time then
Criim
Is there a way to flash from the EVO itself? I can copy files with no problem if I connect as a HDD.
add this file to the tools folder of android sdk or i think in OS x anywhere works as long as you direct the command line to it
Criimson said:
Hmm that's too bad. My Vista sees my EVO, but it has an exclamation mark and the driver won't initialize no matter what I try.
Guess I'll wait till some other time then
Criim
Click to expand...
Click to collapse
sounds like your in recovery and not fastboot
you should see the white screen with the androids riding skateboards once its there don't press anything on the phone
I can't connect to fastboot.
Code:
ERROR: could not get pipe properties
ideas?
JSZESZE said:
add this file to the tools folder of android sdk or i think in OS x anywhere works as long as you direct the command line to it
Click to expand...
Click to collapse
Awesome! Thanks man, I appreciate it. Looks great.
beautiful! thank you VERY much for this
JSZESZE said:
sounds like your in recovery and not fastboot
you should see the white screen with the androids riding skateboards once its there don't press anything on the phone
Click to expand...
Click to collapse
No it is in fastboot
From what I gather a lot of people have this issue with Vista 32bit and HTC Sync. I haven't been able to track down a solution. Even when trying to use Sync..it always just errors and says:
Unable to find HTC Sync on your PC. Please make sure.....
Kind of a pain, but so far I have been able to do everyting I want just doing it from the phone with files copied over. Using the terminal emu or file manager
Criim
imaxreed said:
I can't connect to fastboot.
Code:
ERROR: could not get pipe properties
ideas?
Click to expand...
Click to collapse
sounds like a permission issue... are you rooted and nand unlocked?
JSZESZE said:
sounds like a permission issue... are you rooted and nand unlocked?
Click to expand...
Click to collapse
should be. running caulkins rom custom recovery (amons) i have actually used fastboot before. any quick way for me to verify?
imaxreed said:
should be. running caulkins rom custom recovery (amons) i have actually used fastboot before. any quick way for me to verify?
Click to expand...
Click to collapse
in adb type
Code:
adb shell
then you should see
Code:
#
A $ prompt is the prompt for normal terminal ...
whereas:
a # prompt is the prompt for root (super user)
i am running osx and can access adb shell
http://imgur.com/t8MKg.jpg
does this look like the error?
$ fastboot devices
ERROR: could not get pipe properties
HTXXXXXXXXXX fastboot
i found a few things while googling the problem
most pointed to root issues
JSZESZE said:
does this look like the error?
$ fastboot devices
ERROR: could not get pipe properties
HTXXXXXXXXXX fastboot
i found a few things while googling the problem
most pointed to root issues
Click to expand...
Click to collapse
yes exactly. I haven't had a problem before this is strange.
Works great for me, no problems. This is a great way to save battery!
haha.
Related
I can't be the only one who likes Halo and can't wait for Reach to come out.
Here's a couple of splash screens I created with that in mind.
They are similar, but the second has one of my favorite quotes from Halo 3 and any one who has read the books knows what it means.
Let me know what you think. (Be gentle though, these are my first ones)
{
"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"
}
They look great, the only change I would make would be the quote on the second one. I would use a quote about Noble 6, like "There's only one other spartan with that rating" -Dr. Halsey
Sent from my PC36100 using XDA App
The reason I used that quote was because of the references in the halo: the fall of reach (the book). But if anyone wants a specific quote let me know and I'd be happy to include it.
Sent from my Fresh'd out Evo 4g
using XDA App
blkswanpres said:
They look great, the only change I would make would be the quote on the second one. I would use a quote about Noble 6, like "There's only one other spartan with that rating" -Dr. Halsey
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Here ya go.
Hi, was hoping you could help me with this. I followed instructions on how to flash this and the actual sending of it worked but when it tried to write it, it said FAILED (remote: not allowed). Any ideas on what that would mean? Thanks!
You need to have ADB enabled. Put the evosplash1.rgb into your sdk/tools folder. Plug your USB into phone, then boot your phone into the bootloader. Click on fastboot. Underneath the date it should say FASTBOOT USB. Then open a command prompt and CD to your sdk/tools (or whatever you named it) once there type this:
Code:
fastboot flash splash1 evosplash1.rgb565
fastboot reboot
FattySparks said:
You need to have ADB enabled. Plug your USB into phone, then boot your phone into the bootloader. Click on fastboot. Underneath the date it should say FASTBOOT USB. Then open a command prompt and CD to your sdk/tools (or whatever you named it) once there type this:
Code:
adb remount
fastboot flash splash1 evosplash1.rgb565
fastboot reboot
Click to expand...
Click to collapse
First, thank you for replying to my post! You are the first one to state the "adb remount" part. I did that but it is saying device not found now. My phone does show the red fastboot usb so do you any further suggestions because it still failed on the writing part. The sending part went fine but I guess it is failing since it cannot find my phone. Might I have the sdk set up incorrectly?
One more thing...when I type adb devices...nothing shows up but when I type fastboot devices....my phone does show up.
eaglenest608 said:
One more thing...when I type adb devices...nothing shows up but when I type fastboot devices....my phone does show up.
Click to expand...
Click to collapse
when you're in fastboot it shouldn't show up in adb devices. I also forgot to mention to put the rgb565 file into your sdk/tools folder. Other than that it sounds like your setup properly.
Edit: Also the adb remount code isn't needed. I was so used to using it from messing around with bootscreens, I forgot it isn't needed for fastboot.
Yes, it seems I am setup correctly from what I have read. Maybe I should flash to a different rom and see if that helps me. My wireless tether app is giving me problems as well so not sure what has happened but it may be time to give something else a go. Unless you can think of anything new that is, lol. Thanks a bunch though for you help...really appreciate it.
Well, for those that actually care I have now resolved this issue. It turns out that the HBOOT version that I had did not allow me to perform this flash. I had to actually downgrade it to a different one and it worked perfectly. I wish to thank those that actually took the time to reply to my post...it was greatly appreciated!!
Realize I posted the screen of the new quote, but didn't attach the file... duh
Halo Reach Boot animation
http://forum.xda-developers.com/showthread.php?p=8419483#post8419483
PLEASE
Can you do one that says
"Halo:Reach>MW2"
That would be epic
Sorry for the delay, got married last weekend.
Here ya go.
Ohhh this is Perfect the delay is no problem but seriously thanks alot and congrats on the marriage
I was unlocking the bootloader so i could root the phone. I was successful but now my phone is stuck on the google screen with the unlocked pad at the bottom.
Through the forum i found that i'm missing the boot image so i found that.
I pulled in my phone to the computer and typed "fastboot flash boot test_boot.img". it comes up with "error: cannot load test_boot"
The same thing happened when i tried to "fastboot flash recovery recovery.img" aswell to try and fix it that way but the same error came up.
I made sure the file names were correct.
Please help!!
bozo089 said:
I was unlocking the bootloader so i could root the phone. I was successful but now my phone is stuck on the google screen with the unlocked pad at the bottom.
Through the forum i found that i'm missing the boot image so i found that.
I pulled in my phone to the computer and typed "fastboot flash boot test_boot.img". it comes up with "error: cannot load test_boot"
The same thing happened when i tried to "fastboot flash recovery recovery.img" aswell to try and fix it that way but the same error came up.
I made sure the file names were correct.
Please help!!
Click to expand...
Click to collapse
fastboot clockwork recovery then flash a rom.
I would flash clockwork but when i put the file into my SDK tools folder and then use CMD to try and flash it but i got an error. Details are in my first post.
Please help!
bozo089 said:
I would flash clockwork but when i put the file into my SDK tools folder and then use CMD to try and flash it but i got an error. Details are in my first post.
Please help!
Click to expand...
Click to collapse
do you have the recovery.img file in the same folder as fastboot?
simms22 said:
do you have the recovery.img file in the same folder as fastboot?
Click to expand...
Click to collapse
Yeah its in there.
Also, when i typed adb devices it only says "see devices attached" not the serial number.
bozo089 said:
Yeah its in there.
Also, when i typed adb devices it only says "see devices attached" not the serial number.
Click to expand...
Click to collapse
do you have the proper drivers installed? if not, go directly to PdaNets website http://junefabrics.com/android/ and have it install the proper drivers onto your computer. this way is by far the easiest way to install the drivers. download and install the free program then just follow the directions on the screen.
simms22 said:
do you have the proper drivers installed? if not, go directly to PdaNets website http://junefabrics.com/android/ and have it install the proper drivers onto your computer. this way is by far the easiest way to install the drivers. download and install the free program then just follow the directions on the screen.
Click to expand...
Click to collapse
I do have that installed. I used it to unlock the bootloader. Im trying to reinstall it using the link you provided but the phone doesn't turn on so i dont think it will work. Now in the fastboot screen on my phone it says fastboot status -FAILinvalid command
bozo089 said:
I do have that installed. I used it to unlock the bootloader. Im trying to reinstall it using the link you provided but the phone doesn't turn on so i dont think it will work. Now in the fastboot screen on my phone it says fastboot status -FAILinvalid command
Click to expand...
Click to collapse
Update: the FAILinvalid part went away but i think i might have uninstalled the pdaNet when trying to reinstall it.
bozo089 said:
Update: the FAILinvalid part went away but i think i might have uninstalled the pdaNet when trying to reinstall it.
Click to expand...
Click to collapse
OK, i did a system restore and now i have pdaNet back. I have no idea how to use it or what to do next.
Please help!
EDIT: when i typed "fastboot devices" into CMD, it shows my device!
take a screenshot of your /sdk/tools folder.
(seriously do it).
OR if you don't want to.. does fastboot appear as "fastboot" or "fastboot.exe" ?
Uploaded with ImageShack.us
There you go
bozo089 said:
Uploaded with ImageShack.us
There you go
Click to expand...
Click to collapse
Okay, yeah. I see the problem, your extensions are hidden "recovery.img" is actually "recovery.img.img" so you're fastbooting a invalid file. What I want you to do is on the top left of a Windows explorer, it says Organize. Press that and go to folder options -> view -> hide extensions for known file types (UNCHECK THIS). Rename recovery.img.img so it appears as recovery.img not recovery.img.img
Put your phone in bootloader mode if it isn't already with USB plugged in.
The phone needs to be in bootloader mode in order for it to recognize the fastboot command.
{
"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"
}
^ appears as that.
through command prompt
cd C:\android-sdk-windows\tools\
(optional -- do this if your phone isnt in bootloader mode) adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
and you're set. click on "thanks" if this helped you!
wow, ok so it says writing and sending went "OKAY". I assume that means it worked.
I really don't know what to do now. How do i access the clockwork menu and how do i install a ROM?
bozo089 said:
wow, ok so it says writing and sending went "OKAY". I assume that means it worked.
I really don't know what to do now. How do i access the clockwork menu and how do i install a ROM?
Click to expand...
Click to collapse
yeah that meant it worked. you can access clockwork menu by going down to RECOVERY in the menu or "adb reboot recovery"
you install a ROM by...
1. Shop around the Dev forums and look for what ROM you want to use. I personally use CM7.
2. Use netarchy's kernel (its worth it).
Steps:
1. Put ROM onto your sdcard
2. Boot into Clockwork Recovery (told you above on how to do it)
3. Wipe Factory, Dalvik, Cache
4. Flash ROM (Proceed to flash CM7 Gapps afterwards if you decide to go with CM7)
5. Flash Kernel (Optional)
6. Reboot!
Ahhh, i updated without looking at your post first. Can i put the kernal on now that ive rebooted?
thank you for your help and time
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
quantum94 said:
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
Click to expand...
Click to collapse
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
root-expert said:
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
Click to expand...
Click to collapse
nopes...on typing "fastboot code", it redirects me to the current directory:
{
"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"
}
what to do?
Are you sure you are in fastboot mode?
root-expert said:
Are you sure you are in fastboot mode?
Click to expand...
Click to collapse
pretty sure...u can see the pic at:
What now!? :crying:
quantum94 said:
pretty sure...u can see the pic at:
What now!? :crying:
Click to expand...
Click to collapse
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
root-expert said:
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
Click to expand...
Click to collapse
sorry for the late reply....
I tried the same thing on different pc and it worked!
But i have another problem!
I installed cm11 nightly for my on my x plus from here:
http://get.cm/get/qG0
After that my imei has gone blank along with the baseband version.
I did a bit of research and found that by using ruu, u can get the imei back.
So for that i needed turn my s-on to s-off by the foll commands:
adb reboot
if i am not mistaken, while the phone is rebooting i am supposed to put the 2nd command:
adb wait-for-device push firewater /data/local/tmp
The problem here that I think is the phone reboots so fast that i guess the command fails to execute and i get an error saying :
error protocol fault (no status)
So, how to turn off fastboot or quickboot in cm11? There is absolutely no option in the phone. I tried battery settings,power settings, everything!
is there a way to disable fastboot/quickboot in bootloader mode?
plz help!
Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Bencaill said:
Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Click to expand...
Click to collapse
Hello, are you sure you have the boot.img also in the direcotry?
DallasCZ said:
Hello, are you sure you have the boot.img also in the direcotry?
Click to expand...
Click to collapse
yes, I am sure I have it
Bencaill said:
yes, I am sure I have it
Click to expand...
Click to collapse
i tried it again and it works well for me.
can you post a creen of the folder where you extracted the files?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you have to run the root.bat file, you cannot dir the boot.img
I know I have to run the bat file but you asked me a screen of the folder
I have this message:
strange... idunno for me its working well (windows 7 pro) and the boot.img is in the same directory... do you have some antivirus, anti spam apps running?
A other member of Frandroid forum has exactly the same issue. But he is running W8.1
That is really strange.
I am running win 8.1 as well
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
The problem seems to be resolved by using Windows 7 instead.
http://forum.frandroid.com/topic/223905-tuto-root-de-l-idol-3-55/?p=3417628
using win 7 is not a solution... there have to be a way how to do it, because there are thousands of users with win 8.1 who using fastboot and adb commands...
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
is your bootloader unlocked?
And I take it you've enabled Developer Options and USB Debugging?
After all my talk about the ease of communicating with Android devices from a Mac, I'm now unable to successfully issue fastboot commands when in the bootloader. I've tried using sudo, making sure to include arguments that address the device, etc. I can execute adb commands when the phone's system is booted, though. But fastboot commands either get me a "waiting for device" or nothing at all. I thought I was able to do this successfully yesterday, when I was just testing it out. Today, I was going to root by booting into TWRP and flashing SuperSU.
maigre said:
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
Click to expand...
Click to collapse
If it was a driver issue, my phone would not restart with the command, every drivers are OK
ractar28 said:
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
Click to expand...
Click to collapse
Your method worked !!!!!!!!!!!!!!! THX !!!!!
Good morning,
I'm new here, and i hope you can help me with my problem.
I have a mi MJJGYY02FM projector and i did a update with USB stick with files from Xiaomi.
Now after the update the projector start with MI logo and than shuts down, after that he start up with no screen and do nothing.
Can someone help me how to fix this. i can't get the projector in a boot menu with the remote, maybe he dont recognize the remote.
Kind Regards,
Bas
Reflash projector's Stock ROM.
jwoegerbauer said:
Reflash projector's Stock ROM.
Click to expand...
Click to collapse
I have the stock ROM on USB now, but hè will not install it. When i press the home and enter button and plug the power cable. Hè start up with the MI logo and shuts down, then start up with no screen.
Are there other ways to install the stock ROM?
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Thanks
Im gonna search out and try that option.
I let it know when it works. maybe i have some questions.
jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Im trying something, but do you have a discription how to make that USB with the Stock Rom?
I got your files on my pc. I have a 16GB USB format FAT32.
What is the way to make that sideload with the ROM version?
Im sorry for the questions, but i have never done this before.
I have done thist thing
{
"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"
}
The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.
jwoegerbauer said:
The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.
Click to expand...
Click to collapse
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?
Vross46 said:
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?
Click to expand...
Click to collapse
My drive letter is :e
Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name
jwoegerbauer said:
Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name
Click to expand...
Click to collapse
ah ok. lets try.
It seems not so difficult but, for the first time is everything more difficult
What do i wrong. sorry! I do really my best
1, i have a format 16gb usb FAT32
2. i have install ADB installer.
3. i have download the stock rom (see picture)
4. my drive name is e:
5. When i zip my stock rom file, i got an another zip file, and an file of 1kb
in the next picture is what i do in CMD
anglee_full_9.0.0.1911 is my zipped stock rom downloadfile
the other 2 are the unzipped files from the first file
1st screenshot provided above shows
1. Device isn't connected via USB-cable with PC or, if, not powered on
2. The ROM's archive name you entered is without fileextension -> required :ZIP
If ROM's archive is packed as .RAR file then you have it to repack to .ZIP file
I think it will not gonna help.
When i connect my projector to the pc, the pc dont recognize him.
What i try, nothing works.
but thanks for your help anyway
Have you ever enabled "USB Debug" in Android's Settings -> Developer otions?
I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check
Vross46 said:
I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check
Click to expand...
Click to collapse
Hello Vross46, have you been able to solve your problem? I’m stuck with the logo as well