Being used to the back button on the right side and the recent items on the left i noticed there is no option to set that in the settings menu.
Or at least i could not find it.....
You will need ADB on the PC/Laptop and connect the phone to it.
Download of ADB can be found here: https://forum.xda-developers.com/showthread.php?t=2588979
So i found a nice post https://forum.xda-developers.com/pixel-xl/help/swap-recent-button-oreo-t3687721 that enables it.
NO ROOT required, just enable ADB in developer settings.
Then start ADB shell
Enter this command and you are done.
settings put secure sysui_nav_bar "space,recent;home;back,space"
All happy now.
Thanks !
Do you know if we can change long press action with this method ?
rqdb said:
Thanks !
Do you know if we can change long press action with this method ?
Click to expand...
Click to collapse
If we can find the command for it i suppose we can. Not sure how we can find this.
Verstuurd vanaf mijn Nokia 7 plus met Tapatalk
Thanks for sharing and one stupid question....OTA still work after ADB shell?
supremeee said:
Thanks for sharing and one stupid question....OTA still work after ADB shell?
Click to expand...
Click to collapse
It should. No modification is done to the file system.
Verstuurd vanaf mijn Nokia 7 plus met Tapatalk
Brotuck said:
Then start ADB shell
Enter this command and you are done.
settings put secure sysui_nav_bar "space,recent;home;back,space"
All happy now.
Click to expand...
Click to collapse
Doing this you'll loose the keyboard switching icon that appears when you have multiple virtual keyboards. The command including this icon is:
settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
I'm having difficulties getting ADB to work(authorization popup does not appear). Any ideas?
{
"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"
}
:edit:
Any chance this feature is hidden in the global built (albeit hidden) and can be pulled out using adb?
Answer by Nokia assistance:
Thank you for contacting Nokia Mobile Care and your interest in Nokia mobile devices.
Regarding your request, we would like to inform you that this option does not exist.
We remain at your disposal if you have other questions or need our help.
Does the switch remain after rebooting the phone ? Or do i have to do this every time i reboot ?
Inpain said:
Does the switch remain after rebooting the phone ? Or do i have to do this every time i reboot ?
Click to expand...
Click to collapse
The change remains after reboot
After put in the command through adb shell, with Nokia 7 plus attached to the pc, I got a system ui error, phone does start up, but after that I got a black screen only , had to do a hard reset, lost all data.
riseandshine32 said:
After put in the command through adb shell, with Nokia 7 plus attached to the pc, I got a system ui error, phone does start up, but after that I got a black screen only , had to do a hard reset, lost all data.
Click to expand...
Click to collapse
Same
OC-Freak said:
Same
Click to expand...
Click to collapse
Working fine here, on Build number: 00WW_2_22A (May security patch build).
Did you type in the commands correctly (semicolons and commas) ?
Just did the command again on a fresh installed version with the May patches and all is fine.
Please make sure you type exact the correct syntax.
I always do a copy / paste on my laptop from the text on a adb shell
Excellent mate. worked like a charm on my Nokia 7 plus with latest system update
Nokia 7 Plus
Hey, I got the same phone like you!
But my phone is not in the devices list (adb devices)
Please help
Hello, I tried this but I'm always getting this error in adb command line:
C:\adb>settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
'settings' is not recognized as an internal or external command, operable program or batch file.
The underlined text I copy pasted it from this xda thread. When I do adb devices I see my device in the list, its the only android device thats connected to my computer. I don't have an idea how to fix it.
After some further experimenting I've gotting it done
In the adb command line you type folllowing command
1. adb devices
2. adb shell
3. settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
4. that's all
Wuter said:
Hello, I tried this but I'm always getting this error in adb command line:
C:\adb>settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
'settings' is not recognized as an internal or external command, operable program or batch file.
The underlined text I copy pasted it from this xda thread. When I do adb devices I see my device in the list, its the only android device thats connected to my computer. I don't have an idea how to fix it.
After some further experimenting I've gotting it done
In the adb command line you type folllowing command
1. adb devices
2. adb shell
3. settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
4. that's all
Click to expand...
Click to collapse
After Step 2 press ENTER
then the command prompt should enter a shell (you will see b2n_sprout:/)
in the shell you paste the command
See attached screenshot
Its there a way to change the icons to vanilla?
Related
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.
I am trying to unlock the bootloader on my US Moto G 16 G. I have followed the instructions provided in Unlock Youe Device and Android Pit. I have followed the instructions in the FAQ as well.
After I input "$ fastboot oem get_unlock_code" i get the following reply " '$' is not recognized as an internal or external command, operable program, or batch file."
I have searched for the reply in Google, but I cannot come across another user who has documented this issue and how to resolve it. Any help would be greatly appreciated.
You are not supposed to write the $ symbol, start with "fastboot..."
Sent from my XT1032 using xda app-developers app
kafepuya said:
I am trying to unlock the bootloader on my US Moto G 16 G. I have followed the instructions provided in Unlock Youe Device and Android Pit. I have followed the instructions in the FAQ as well.
After I input "$ fastboot oem get_unlock_code" i get the following reply " '$' is not recognized as an internal or external command, operable program, or batch file."
I have searched for the reply in Google, but I cannot come across another user who has documented this issue and how to resolve it. Any help would be greatly appreciated.
Click to expand...
Click to collapse
The $`s are not to be typed bro and the correct cmd command afaik is : fastboot oem get_unlock_data
Thanks for pointing out the mistake on the command. I tried the correct way of doing it, and I still get essentially the same reply. Here is a screenshot to illustrate my situation.
{
"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"
}
I got the same, when you paste the code into the box click and delete all spaces and make sure there are no spaces at the beggining of the code also.
kieranc88 said:
I got the same, when you paste the code into the box click and delete all spaces and make sure there are no spaces at the beggining of the code also.
Click to expand...
Click to collapse
No dice bro. No matter what I type, I get back "[whatever the first word in the command I type] is not recognized as an internal or external command, operable program or batch file.
I don't even know what to try next.
Oh I get you now, have you got fastboot and adb installed? If so point it to the folder that contains fastboot and adb iI usually place it on c drive in a folder called android so in command prompt to point it adb I would type cd c:/android then execute your commands
kieranc88 said:
Oh I get you now, have you got fastboot and adb installed? If so point it to the folder that contains fastboot and adb iI usually place it on c drive in a folder called android so in command prompt to point it adb I would type cd c:/android then execute your commands
Click to expand...
Click to collapse
Well, I don't know if I have adb installed. I only downloaded and installed the 2 files mentioned in the Motorola page. Android SDK and the latest Motorola drivers. I can navigate to any folder in terminal (all I do is Shift+Right click on a folder and select open command window here...)
If you haven't got adb and fastboot installed look here http://forum.xda-developers.com/showthread.php?p=42407269
kieranc88 said:
If you haven't got adb and fastboot installed look here http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
Well, that sure is quite more than was in the Motorola website. Ill read up on that and figure out how to do it. Thanks a lot. I'll keep you posted.
You don't actually need the android SDK ,install adb and fastboot from the previous link I posted above
Install drivers point cmd to folder containing adb and fast boot type in cmd "adb devices" if your phone is recognised it will show a serial number,if so continue with the unlock process,
If its not recognised the drivers aren't installed properly if so download pdanet for windows and set it up ( its a tethering app but it installs drivers) get it here http://pdanet.co/bin/PdaNetA4126.exe
Check again if device is recognised and if so continue with rest of process
---------- Post added at 12:59 AM ---------- Previous post was at 12:51 AM ----------
For an easier way to install adb check this out http://forum.xda-developers.com/showthread.php?t=2588979
kieranc88 said:
You don't actually need the android SDK ,install adb and fastboot from the previous link I posted above
Install drivers point cmd to folder containing adb and fast boot type in cmd "adb devices" if your phone is recognised it will show a serial number,if so continue with the unlock process,
If its not recognised the drivers aren't installed properly if so download pdanet for windows and set it up ( its a tethering app but it installs drivers) get it here http://pdanet.co/bin/PdaNetA4126.exe
Check again if device is recognised and if so continue with rest of process
---------- Post added at 12:59 AM ---------- Previous post was at 12:51 AM ----------
For an easier way to install adb check this out http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I did it! Thanks for all the great help, specially kieranc88. Xposed here I come!!!
{
"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"
}
Tutorials and the tools are not my work, so I don't take any credit. However, the tutorial is come from China. I combine my experience and translate them as much as I can to english.
Instructions:
First, download the root files (at the bottom of this post) accroding to your tablet model (at the back of your tablet) and install the driver in the computer.
Please install in the following order:
1) iSocUSB-Driver-Setup-1.2.0.exe
2) IntelAndroidDrvSetup1.5.0.exe
3) PhoneFlashTool_5.3.4.0_win32.exe
Pay attention to the following points
a) you must install those driver in the above order
b) Don't change the install location of those driver
c) Close your antivirus software to avoid unknow problem
Then, go to Settings>Developer Options>USB Debugging. Enable OEM Unlock and enable USB Debugging Mode
Now, connect your X80 Plus to the computer,
Open a Command Prompt window in "Root X80 Plus H6C3" folder (To open a Command Prompt window in any folder, hold down the shift key and right-click on the folder) and enter the following command
Code:
adb reboot bootloader
Press Enter
Wait for the device to enter fastboot mode
Code:
fastboot oem unlock
Press Enter to unlock the oem and enter the following command
Code:
fastboot flash boot boot.img
Press enter to flash the kernal, then enter the following command
Code:
fastboot reboot
This command will restart your tablet.
It is normal that tablet reboot 3 to 4 times automatically, just wait for it. (turn on the tablet yourself if the tablet do not reboot automatically)
After your device is on, check that Wifi and bluetooth works or not. (Wifi and Bluetooth may not works with the replaced kernal, just perform a factory reset)
If everything is ok, enter the following command
Code:
root.bat
Wait for the Command Prompt until it stuck at this command, "adb shell su --daemon"
Now, disconnect the tablet and reboot it manuly
After the device was booted up, Supersu already become a part of system app.
Open Supersu now, it will notify that the SU binary needs to be updated. You must need to install the binary once, but you will fail at 100%(unless there is a miracle, and your tablet is root successfully, congratulations)
Close Supersu and reconnect the tablet, enter the following command again.
Code:
root.bat
Now the command prompt should run all of the command smoothly and Supersu should have no message about the SU binary update !!
Therefore, if your Supersu shows nothing (works properly), your tablet is rooted, thats amazing.
If Supersu keep notifing, please enter the following command again and wait for it to boot up automatically until Supersu have no message about the binary update.
Code:
root.bat
Note that this root method are not stable yet
Known issues:
1) Old version of Titanium Backup was unable to execute the SU command
2) LBE are not 100% compatible with this root
Post reply if you have any requires or problem.
Stock Rom for X80 Plus just in case you need them, and the instruction will be translated later
H6C3 and H5C5
Root files: H6C3 and H5C5
Sorry for my bad english
Hi and thanks for sharing.
Is there a custom recovery to install?
I would like to install xposed framework, but don't know how to install the zip file...
Thanks
thanks and your thread on teclast's forum where the link was crash, please repair.
Thanks a lot
Can someone confim that this method works?
Jeconxis said:
thanks and your thread on teclast's forum where the link was crash, please repair.
Click to expand...
Click to collapse
You can try to flash xposed using flashify!
woody4165 said:
Hi and thanks for sharing.
Is there a custom recovery to install?
I would like to install xposed framework, but don't know how to install the zip file...
Thanks
Click to expand...
Click to collapse
Working hard on it now
hahaha1111 said:
Working hard on it now
Click to expand...
Click to collapse
looking forward to this!
Thaaanks a lot @hahaha1111 !!! I tried that on my all new H6C4 received this morning with your H6C3 files and anything is working perfectly !!! Many thanks again !!!
BTW: Any way to update SuperSU binary then?
I tried your method on my H5C6 and it worked beautifully. Thank you!
where can I use the file?
I download the file named X80 plus-win10_20160108.7z from the link. what is this, and where can I use it?
hahaha1111 said:
Working hard on it now
Click to expand...
Click to collapse
Hi @hahaha1111
any news on custom recovery?
I would like to install xposed framework, but cannot be done without custom recovery, is it correct?
Thanks
woody4165 said:
Hi @hahaha1111
any news on custom recovery?
I would like to install xposed framework, but cannot be done without custom recovery, is it correct?
Thanks
Click to expand...
Click to collapse
Hiatus
H6C4
Great! It works perfectly on H6C4.
Thanks!
Regards
RoroTiti said:
Thaaanks a lot @hahaha1111 !!! I tried that on my all new H6C4 received this morning with your H6C3 files and anything is working perfectly !!! Many thanks again !!!
BTW: Any way to update SuperSU binary then?
Click to expand...
Click to collapse
It's updated from play market with no problem.
May be it is my particular problem ( kernel 3.14.37 firmware assembly ver 3.03.20161109) but.....
WARNING TO H6C4 OWNERS! SD Card becomes unusable with this rooting files. Any SD Card after rooting recognized as 0,9 Mb size and you can't access files on it. You can't use SD Card reader too.
Please report if you do not encounter this issue.
Hi.
I'm stuck on "adb push SUfiles/Superuser.apk /data/superuser" command in root.bat
I've done all the previous steps without problems.
Before executing root.bat I have set again Usb Debug and OEM Unlock, is it correct?
Sometimes I get stuck on "adb remount"
What can I check?
Thanks
Woody
I'm pretty new to stuff like rooting phones and such so I figured out that I'd be trying to see if I could manage to get my bootloader unlocked so I can once and for all install TWRP, which my dumbass has been trying to install without an unlocked bootloader.
I've got the basics going, like how should I do the unlocking (my phone's model is 5054S, yes it's an alcatel phone) and found a website which tells what commands you should do to unlock it
Well...
It just gets stuck there without further response. Amazing.
{
"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"
}
Could you guys help me on this one?
Command
Code:
fastboot reboot fastboot
is only to be used if Fastboot server is located in Android's user-space what only is case when Android OS has Dynamic Partition Layout.
jwoegerbauer said:
Command
Code:
fastboot reboot fastboot
is only to be used if Fastboot server is located in Android's user-space what only is case when Android OS has Dynamic Partition Layout.
Click to expand...
Click to collapse
Oh no, this happens with every piece of code that needs some input from a phone (with this i mean the part where the command line just gets stuck)
And this is essentially the same with every code I have to utilize in the guide for unlocking
jwoegerbauer said:
Command
Code:
fastboot reboot fastboot
is only to be used if Fastboot server is located in Android's user-space what only is case when Android OS has Dynamic Partition Layout.
Click to expand...
Click to collapse
Extra thing:
There's also this
Code:
fastboot -i 0x1bbb devices
Which when actually used, it kinda does work?? Just doesn't recognize the -i as a parameter in the programs. And yes, this happens with both CMD and PowerShell
Okay,
Code:
adb reboot-bootloader
DOES work. But it only restarts the phone.
And there's also this
Polaroid. said:
Okay,
Code:
adb reboot-bootloader
DOES work. But it only restarts the phone.
And there's also this View attachment 5348201
Click to expand...
Click to collapse
You are contradicting yourself: The applied ADB command of course DID NOT WORK, you got an error.
Reason: ADB got inproperly configured on phone.
Try this to get rid off of the error:
1. Disconnect phone from computer.
2. Revoke "USB debugging authorizations" in Android's Developer options on the phone.
3. Reconnect the phone to the computer and allow USB debugging on phone again.
4. Confirm the RSA-key in Authorization popup.
jwoegerbauer said:
You are contradicting yourself: The applied ADB command of course DID NOT WORK, you got an error.
Reason: ADB got inproperly configured on phone.
Try this to get rid off of the error:
1. Disconnect phone from computer.
2. Revoke "USB debugging authorizations" in Android's Developer options on the phone.
3. Reconnect the phone to the computer and allow USB debugging on phone again.
4. Confirm the RSA-key in Authorization popup.
Click to expand...
Click to collapse
Ah, thanks for correcting me. Didn't know about that. Gonna try if it works now
jwoegerbauer said:
You are contradicting yourself: The applied ADB command of course DID NOT WORK, you got an error.
Reason: ADB got inproperly configured on phone.
Try this to get rid off of the error:
1. Disconnect phone from computer.
2. Revoke "USB debugging authorizations" in Android's Developer options on the phone.
3. Reconnect the phone to the computer and allow USB debugging on phone again.
4. Confirm the RSA-key in Authorization popup.
Click to expand...
Click to collapse
Okay, I tried doing this and it does not resolve the problem, still restarts the phone
Yes. It is the same command and all but it still just doesn't work properly.
Q1: What is returned by command
Code:
adb devices
Q2: What is returned by command
Code:
fastboot devices
Hint: Add Alcatel 5054S to this thread's title thus mainly owners of such phone get addressed.
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