I built myself my own computer with an NVIDIA GTX 970 for it's graphics card, i5-4690k processor and the motherboard is an Asus that has USB 3.0 ports.
I was using an old 16GB Sandisk that's USB 2.0. Guest mode boots fine and there are no graphical issues it boots up fine and normal on my end..
However booting into Resident Mode I have issues. There is an infinite boot loop on the Remix OS screen, when I reboot to try again there is an initial loading screen in Mandarin (Or at least I believe it's Mandarin, sorry) but then I get stuck on the Remix OS screen once again. I even tried deleting data.img to try again and that didn't work.
I let my computer run it all night and still haven't managed to boot up.
I even managed to run Guest Mode on a 4 GB USB Stick that is on 2.0, which leads me to think there isn't anything wrong with the OS itself but with creating a permanent partition on the USB Stick for the OS and the data you want to store on it. Does anyone have an idea to fix this? Haven't found a solution and searched everywhere for one.
Thanks in advanced. :good:
MisterCoolBeans said:
I built myself my own computer with an NVIDIA GTX 970 for it's graphics card, i5-4690k processor and the motherboard is an Asus that has USB 3.0 ports.
I was using an old 16GB Sandisk that's USB 2.0. Guest mode boots fine and there are no graphical issues it boots up fine and normal on my end..
However booting into Resident Mode I have issues. There is an infinite boot loop on the Remix OS screen, when I reboot to try again there is an initial loading screen in Mandarin (Or at least I believe it's Mandarin, sorry) but then I get stuck on the Remix OS screen once again. I even tried deleting data.img to try again and that didn't work.
I let my computer run it all night and still haven't managed to boot up.
I even managed to run Guest Mode on a 4 GB USB Stick that is on 2.0, which leads me to think there isn't anything wrong with the OS itself but with creating a permanent partition on the USB Stick for the OS and the data you want to store on it. Does anyone have an idea to fix this? Haven't found a solution and searched everywhere for one.
Thanks in advanced. :good:
Click to expand...
Click to collapse
Does not run on nvidia cards. Probably will be added in the future updates.
TheBasterd said:
Does not run on nvidia cards. Probably will be added in the future updates.
Click to expand...
Click to collapse
That's strange though it booted up on Guest Mode, is Resident Mode more dependent on the GPU I suppose?
I'll try running resident mode once again but on my integrated graphics. Wish there was a seamless was of booting Remix OS then to windows easily though.
Thanks for the response!
Sent from my SM-T800 using Tapatalk
@TheBasterd
Does anyone happen to know what nouveau.modeset=1 i915. modeset=0 means? I found this to be a solution for NVIDIA Graphic Cards?
Sent from my iPod Touch 6th Generation using Tapatalk
You'd include that line
Sent from my iPod Touch 6th Generation using Tapatalk
{
"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"
}
Using integrated graphics and on resident mode to see if I can boot up.
Sent from my iPod Touch 6th Generation using Tapatalk
Yeah, can't seem to boot up on my desktop but no big deal. Hopefully I can boot up on my laptop in resident mode. Only Guest Mode works but eh.
Sent from my iPod Touch 6th Generation using Tapatalk
** THEORY **
Not going to post anymore since I realize i've been spamming my own thread with micro-updates.
I'm going to theorize that you CAN'T run Resident Mode if your USB Stick goes under 10 (Which the OS does warn you about this). Unless anyone else has been able to run Resident Mode on a 2.0 Stick please do post here. I order this from amazon, hopefully it'll work. ALSO, from my findings I do believe that even if the USB port is 2.0 it'll still run well because USB 2.0 ports are capable of writing up to at least 15 - 50 MBps assuming your USB Stick is USB 3.0.
TL;DR
USB 2.0 can't run Resident Mode
USB 3.0 is fast on a 2.0 port which should be able to run Resident Mode
Only a guess/theory from observations.
Guest Mode works on USB 2.0 <= 5MBps
This link goes to a possible solution regarding NVIDIA Cards!
I have the same trouble with an ASUS F200-CA intel celeron. I run quite well guest mode but resident mode has your same issue. I've installed Remix OS on a 2.0 usb stick.
The only difference between me and you is that the first time i booted it war working also with resident mode (for example i installed Google Play Services). I don't know why but after a reboot it stopped working. I tried to format and flash many time the usb stick trying to make it work.
Related
So I've been trying for quite awhile to bring my player back. I was trying to develop my kernel with it and it just plummeted to it's death eventually. I found a DD dump somewhere of another device and flashed it, which I guess might not have been exactly the right file and now here we stand.
The device doesn't turn on, I don't get any "SAMSUNG" boot logo - nothing. It comes up in windows as
{
"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"
}
Now from the research I've done, that should be the "lucky unbrickable" state. The device does nothing, but still shows up in windows. I've tried unbrickable on windows 7, windows 7 via a ubuntu VM, and went as far as to setup a dedicated desktop with ubuntu natively and a windows XP VM. I can only get my player to react on the native linux desktop, but it enters download mode really strangely -
YouTube video of it being "resurrected"-
http://youtu.be/WDclUEyoHFE?hd=1
And after that I lose USB (although the device stays on and powered up as long as I leave it connected). I tried connecting the device to my XP VM which is what everything says to do, and I get "No USB devices connected" in virtualbox. Dmesg gives me "unable to enumerate USB device on port 1, device descriptor read/8, error -71" as soon as download mode initiates.
Every time I've done this whole process before, it's worked wonderfully and you can continue on and flash your bootloaders, then reflash everything else. I've tried this whole process over and over and over and haven't had any success. I also tried a USB jig and it didn't do a single thing.
Can anyone provide ANY insight? I'm really open to anything right now, otherwise it's out for JTAGing. I'm about at whits end with it and I'm out of ideas.
THANKS!
If it "worked perfectly before" in this configuration, your pb is mostly related to Samsung win 7 drivers that are not reachable or "lost".
try to reinstall them and check their availabilty connecting another Samsung device (ask your friends);
note: For me under win 7 , I installed ubuntu as second boot with windows and I forgot the Virtual box trick, that's much simpler and I can learn linux when I have free time...
Good Luck
lolo9393 said:
If it "worked perfectly before" in this configuration, your pb is mostly related to Samsung win 7 drivers that are not reachable or "lost".
try to reinstall them and check their availabilty connecting another Samsung device (ask your friends);
note: For me under win 7 , I installed ubuntu as second boot with windows and I forgot the Virtual box trick, that's much simpler and I can learn linux when I have free time...
Good Luck
Click to expand...
Click to collapse
My windows 7 computer connects fine to my galaxy s3. I just root/recovery/rom/kernel'd it a few days ago from that computer, so everything seems to be working as it should.
Have you tried heimdall on your linux machine? Like this you would not need to disconnect your player at all and you would avoid using virtualbox.
ti-pich said:
Have you tried heimdall on your linux machine? Like this you would not need to disconnect your player at all and you would avoid using virtualbox.
Click to expand...
Click to collapse
Yeah, I actually just did that. I even went as far as trying the current and past 3 versions of heimdall and it doesn't detect any devices.
Sent from my galaxy nexus using xda app-developers app
oneclickunbrick
hey bro try this
download this program called oneclickunbrick
i done the same then when i got home i went looking and i found this
it works like a charm
ps if it doesnt work right the first few times make sure your player is using a comport of your computer and it will work like a charm
http://forum.xda-developers.com/showthread.php?p=15330252
link for the program ^
Evoium said:
hey bro try this
download this program called oneclickunbrick
i done the same then when i got home i went looking and i found this
it works like a charm
ps if it doesnt work right the first few times make sure your player is using a comport of your computer and it will work like a charm
http://forum.xda-developers.com/showthread.php?p=15330252
link for the program ^
Click to expand...
Click to collapse
Thanks, I'll try that when I get home. It looks like a precursor program to the unbrickable mod but I'm willing to try anything at this point!
Sent from my Galaxy SIII
has it worked for you ?
Have you installed the heimdall drivers? Like went into the drivers folder, ran zidag and replaced your "SAMSUNG COMPOSITE USB" or something like that with the first driver? That may make heimdall recognize it.
PairOfSocks said:
Have you installed the heimdall drivers? Like went into the drivers folder, ran zidag and replaced your "SAMSUNG COMPOSITE USB" or something like that with the first driver? That may make heimdall recognize it.
Click to expand...
Click to collapse
Yep, tried that a few times. I was using heimdall before so the drivers should be kosher for it.
It's almost like once it enters download mode the hardware isn't cooperating. I've also gone as far as trying every previous version of UnBrickable thinking one might work better, but I've gotten the same result with all the versions. Download mode shows up and then it drops all connectivity.
Hi everyone,
I have a Windows 10 computer and i would really like to get Remix OS, so I have been on the official website in order to download the Legacy version. I obtain this
{
"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"
}
After that I reboot my computer and boot on my USB. Everything is good but a the end the computer just reboot and I can't go on the program.
Can you help me please ?
I hope you understand what I mean because english is not my native laguage
Fraway
I also have this issue. When I boot up, it goes through the grub menu fine, and I can proceed from the USB write speed test (I have to "press enter to continue"), but after it does that, my machine resets. As in, the power goes off for about five seconds before starting up again.
Anybody have any ideas?
My system specs:
CPU: AMD FX-8350
RAM: 32GB
M/B: Asus M5A99FX-PRO-R2
Video: nVidia GeForce GTX 970
Sound: Creative X-Fi
I tryed to install an other version of Remix OS (1.5) but it also don't work. At the begining a thought that thé image "system.img" was missing but nothing else hapenned. I am starting to think that the problem is coming from the version and that we do have to wait for à better version. So I think they are not solutions yet.
unfnknblvbl said:
I also have this issue. When I boot up, it goes through the grub menu fine, and I can proceed from the USB write speed test (I have to "press enter to continue"), but after it does that, my machine resets. As in, the power goes off for about five seconds before starting up again.
Anybody have any ideas?
My system specs:
CPU: AMD FX-8350
RAM: 32GB
M/B: Asus M5A99FX-PRO-R2
Video: nVidia GeForce GTX 970
Sound: Creative X-Fi
Click to expand...
Click to collapse
I guess that with AMD CPU will not boot. I'm with AMD CPU too and not boot but my wife's laptop is with intel CPU and boot.
sechko said:
I guess that with AMD CPU will not boot. I'm with AMD CPU too and not boot but my wife's laptop is with intel CPU and boot.
Click to expand...
Click to collapse
I'm having similar problem. I boot from usb installation begin. And then when is come to initialization data partition system reboot after few minutes then when start up reboot again at checking data partition. I tryed with tab selection and replace few lines to get android x86 like installation and the end up with faild to create data.img so is all about data image...
Pc is pentium 4 ht 630
Mbo is intel 915gux and im using intergrated gpu
Ram 3gb
sechko said:
I guess that with AMD CPU will not boot. I'm with AMD CPU too and not boot but my wife's laptop is with intel CPU and boot.
Click to expand...
Click to collapse
I have an Intel Core 2 Duo but it doesn't work for me
sechko said:
I guess that with AMD CPU will not boot. I'm with AMD CPU too and not boot but my wife's laptop is with intel CPU and boot.
Click to expand...
Click to collapse
Iam using AMD cpu and running and boot fine no problemo [emoji4]
well, going by their FAQ thingie, it's likely to be nVidia graphics cards causing the issue.
https://groups.google.com/forum/#!topic/remix-os-for-pc/oNEbamQR1v8[1-25]
unfnknblvbl said:
well, going by their FAQ thingie, it's likely to be nVidia graphics cards causing the issue.
https://groups.google.com/forum/#!topic/remix-os-for-pc/oNEbamQR1v8[1-25]
Click to expand...
Click to collapse
Hey,
Thank you. Somebody knows if Remix OS could work with NVIDIA in yhe futur ?
By pressing tab and typing "nomodeset" at one of the boot options, it boots successfully for me, but it's ugly as all hell, and there's am unsightly blinking text cursor in the middle of the screen
So we just have to write this command when they ask us which mode (resident/guest) we want ?
Fraway said:
So we just have to write this command when they ask us which mode (resident/guest) we want ?
Click to expand...
Click to collapse
Yes. highlight "Resident" or "Guest" and press Tab. Then, add "nomodeset" to the end of the command and press Enter. It works for me, but it's not pretty. Not by a long shot.
unfnknblvbl said:
Yes. highlight "Resident" or "Guest" and press Tab. Then, add "nomodeset" to the end of the command and press Enter. It works for me, but it's not pretty. Not by a long shot.
Click to expand...
Click to collapse
Thank you à lot
I tried it but it doesn't worked
Fraway said:
Thank you à lot
I tried it but it doesn't worked
Click to expand...
Click to collapse
It is not generaly solutio for "Remix does not boot" comonly problem. "nomodeset" is just one of various parameters which you can add to your GRUB kernel line. Here in second post (post with green check mark aka accepted answer) you have nice explanation what "nomodeset" does. Remix is in alpha stage and wont run on all hardware. If someone succsesfuly booted Remix on his own hardware with "nomodeset" parameter, it doesn't be case that you will also, on your hardware. I also can't bott Remix on my Toshiba Satellite L775D, and I was try many of kernel line parameters. From other side, I succesfully run Remix on other laptop (Acer Aspire something) without editing anything.
Hey Remixers! We are happy to announce that Remix OS for PC Beta version has been released! Please go to http://www.jide.com/en/remixos-for-pc for free download. Don't forget to subscribe to our newsletter for future update releases! #RemixOn
Version Number: 2.0.102
Release Time: 3/1/2016
Package Type: 64-bit version for Legacy BIOS & EFI boot / 32-bit version for Legacy boot
Update:
1) Installation on hard disk
2) Supports over-the-air (OTA) system updates
3) Release for 32-bit ROM
4) Better compatibility on new Intel CPUs (Update to Linux kernel 4.4）
5) New Installation tool that supports hard disk and USB flash drive
6) Larger data space (up to 8GB for hard disk and up to 64GB for USB flash drive)
7) Faster USB boot-up
8) Battery display bug fixed
9) Supports 1080p display on YouTube and Netflix apps.
10) Terminal app pre-installed for developers
11) Image file supports both EFI and Legacy mode
Wow, Downloading
cool!!
but, they links in the site it is still the alpha version...
eager to test rsrsrsrsrs
p.s.: sorry, my english is poor.
HoangTuBot said:
Wow, Hopefully it will online soon. Still Alpha
Click to expand...
Click to collapse
Hi there, it is up!
RemixOS_Joshua said:
Hi there, it is up!
Click to expand...
Click to collapse
It most certainly is not. Direct torrent link?
EDIT: Finally just showed up for me, here's direct link: https://otacdn.jide.com/release/Remix_OS_for_PC_64_B2016030106.zip
All links are fine/fixed now.....
Not workingon ufi. Says boot failed
Sent from my SM-N920T using Tapatalk
@RemixOS_Joshua Its posibble to upgrade from Alpha to BETA directly?
Ufi i get this error..
{
"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 managed to get it to boot via legacy but i preffer to keep my system as ufi
Sent from my SM-N920T using Tapatalk
]Download the Remix OS for PC package, which contains the Remix OS for PC ROM & Installation Tool.
Open the Remix OS Installation Tool and follow the instructions to install Remix OS for PC on your hard disk.
Reboot your PC.
Select Remix OS in Windows Boot Menu.
Click to expand...
Click to collapse
what's with the Windows Boot Menu? a windows OS installed is a prerequisite?
64bit version didn't work for me on my ASUS TP500L. I got the following error:
tsg2513 said:
64bit version didn't work for me on my ASUS TP500L. I got the following error:
Click to expand...
Click to collapse
Try legacy boot i was unable to get ufi to boot
Sent from my SM-N920T using Tapatalk
Up and running on 64bit verson on a Lenovo with i7 and 16gb ram , looks good
Can the torrent be peered on torbox.net? It gives fastest speed of upto 14MB/s (for me) on torrents
I got this message. "Failed to find cpu0 device node" i dont know what it means
Sent from my MotoE2(4G-LTE) using Tapatalk
Installed x64 successfully, start to install Google Play services and bang.. it freezes. Reboot -> installing second time - works fine. Went to Play Store, start downloading Google Chrome, installation finished and bang.. another freeze. I want to notice it is happening on my machine at work. Will give another shot when back home. Hope it will work fine.
egren58 said:
Try legacy boot i was unable to get ufi to boot
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion. I'm not having much luck switching to Legacy Boot (tried F2, Ec, Del, F9, F12, Etc....but none of them get me into the BIOS Settings Screen).
Cristian Dante said:
I got this message. "Failed to find cpu0 device node" i dont know what it means
Sent from my MotoE2(4G-LTE) using Tapatalk
Click to expand...
Click to collapse
Same issue here on a Dell.
I have tried Legacy and it has no boot devices at all.
Won't boot even selection menu on Toshiba encore, alpha did, wont recognise this as boot device
Sent from my HTC One M8 using XDA Free mobile app
Uefi bios only !
Hey Guys,
So i have download the beta on the Remix OS (32BIT) although for the life of me cannot get it working. I have a linx Tablet which doesn't seem to have legacy support within the BIOS. As far as i am aware the 32BIT version of the OS is Legacy only so how am i meant to install the OS? Here's what i have tried so far.
- Used the beta software to install Remix OS on the same drive, installs fine but when i restart the tablet it boots straight into windows 10. Also when looking at the boot manager there's nothing there to boot from.
Installed the 64 BIT version which also doesn't boot although if i go into my boot manager it appears but when selecting the screen goes black. Most likely due to the fact I'm trying to boot 64 BIT on a 32BIT tablet.
Now this seems like its going to be an issue for many people with 32BIT systems with no legacy option available.
Has anyone had luck getting this working ???
I purchased a new Macbook Pro (Late 2016) which only has Thunderbolt (USB-C) ports and no standard USB ports.
I downloaded the Android SDK and setup ADB/Fastboot commands on the new mac, just like I did on my previous macs. However, I could not get the computer to recognize my phone with the USB-C to USB-C cable that came with my Google Pixel. I also tried using the USB-C to USB-C cable that came with my Nexus 6P, but that didn't solve the problem either.
So I went and bought a Thunderbolt to standard USB adapter and plugged it into the USB to USB-C cable that came with my Pixel and Voila! the computer recognizes the phone perfectly now with ADB and Fastboot commands.
{
"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"
}
It's super annoying that we need an additional adapter for this (thanks, Apple). But I wanted to share this so others can save themselves the time of pulling their hair out trying to figure out why their new mac won't recognize their Android phone.
I also have a late 2016 Macbook Pro and have noticed weird behavior using ADB and Fastboot. For me, my usb c cable that came with my nexus 6p seems to work fine for adb when I choose 'File transfers' from the "Use USB for" menu in the notification drawer. Using the latest version of fastboot (installed via brew), seems to cause my macbook to freeze, regardless of whether i have and android device attached to the computer.
michaelmab88 said:
I also have a late 2016 Macbook Pro and have noticed weird behavior using ADB and Fastboot. For me, my usb c cable that came with my nexus 6p seems to work fine for adb when I choose 'File transfers' from the "Use USB for" menu in the notification drawer. Using the latest version of fastboot (installed via brew), seems to cause my macbook to freeze, regardless of whether i have and android device attached to the computer.
View attachment 3964773
Click to expand...
Click to collapse
Same here, ADB works fine with my Nexus 5x and Nexus 6p, but I can't get fastboot to work... tried different adapters and cables and also other terminal software on the Macbook, but nothing helped. Any news anyone?
thal said:
Same here, ADB works fine with my Nexus 5x and Nexus 6p, but I can't get fastboot to work... tried different adapters and cables and also other terminal software on the Macbook, but nothing helped. Any news anyone?
Click to expand...
Click to collapse
Bump. Any updates on this? I am also having problems with fastboot with my nexus 6p. I enter the command and nothing happens. It just goes to the next line and hangs there.
Filed bug with Google
There is a filed bug on: code.google.com with id 231129
Please upvote that bug, its a show stopper for many Android / iOS devs (like me)
ta1onn said:
There is a filed bug on: code.google.com with id 231129
Click to expand...
Click to collapse
cputoaster said:
Please upvote that bug, its a show stopper for many Android / iOS devs (like me)
Click to expand...
Click to collapse
It looks like they're working on it, here's the patch comments: android-review.googlesource.com with id 328620
ta1onn said:
It looks like they're working on it, here's the patch comments: android-review.googlesource.com with id 328620
Click to expand...
Click to collapse
Any update on this fix? My Windows partition no longer recognizes my Pixel anymore either. I'm getting extremely frustrated.
Workaround: Install VirtualBox
sn0warmy said:
Any update on this fix? My Windows partition no longer recognizes my Pixel anymore either. I'm getting extremely frustrated.
Click to expand...
Click to collapse
It's really annoying that you have to do this, but the workaround is to use Ubuntu/Linux on a virtual machine. It worked on my Nexus 5X + MacBook Pro 2016.
Here's the steps to do it:
Install VirtualBox
Install Ubuntu or other Linux distro
Install fastboot/adb with `sudo apt-get install adb fastboot`
Attach Nexus 5x to VirtualBox
Done!
Shameless advertising:
https://jameswarp.com/2017/fix-fastboot-macbook-pro-2016/
Hi,
I am experiencing issues with my Poco M4 Pro 4G and trying to unlock the bootloader. What I am currently doing is the following;
I enabled developer options, enabled usb debugging and OEM unlocking. I went to unlock status hit agree and hit pair and have waited 7 days for the timer to run out
I shut down the phone and then enter fastboot by holding the volume down button and the power button at the same time.
I downloaded the mi flash unlock tool from here and I logged in using the same account as on the phone, and got up to this screen.
{
"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 then connect the phone which currently has the fastboot logo on to the computer but the button stays grey.
The following is what I have done;
I have installed adb tools. When the phone is booted and is connected to my computer I can see it via "adb devices" in CMD as admin. I can even send it to fastboot mode by "adb reboot fastboot"
I have installed the qualcomm drivers but I am unsure if they are the correct ones.
I have tried with different cables.
I have tried with different PCs.
The computer that I am using mainly to try and unlock the bootloader is a laptop and the specs are as follows;
Model: GP72 2QE Leopard Pro
Intel Core i7 5700HQ
16GB RAM
The other systems that I have tried are almost identifically specced both are AMD based on X570 Mobo and a Ryzen 7 3700X
There does seem to be a known problem with the Mi Unlock tool not being able to communicate properly with the system drivers. There are some tips for getting it working on this thread:
https://forum.xda-developers.com/t/...ol-cannot-detect-phone.3663139/#post-73566526
If that post doesn't solve the problem then try reading through the later posts in that thread.
Sorry for the late reply, I did the suggestion and it worked! Thank you for the help.
My goal was to flash the indonsian rom of the device onto and I had a bit of a problem last night I ended up sending it into a bootloop because the connection wasn't stable from the computer to the phone, I just woke up today and tried it again on a different computer and a brand new cable and the connection wasn't cutting out at all. I put it in fastboot and succesfulyl flashed it. I can't thank you enough for the help.
I just need to know if I need to close this thread or something now that my issue is complete. I'm new around here so I don't know if I shoudl do that.
The Spike Man said:
I just need to know if I need to close this thread or something now that my issue is complete. I'm new around here so I don't know if I shoudl do that.
Click to expand...
Click to collapse
No need, your experience may be shared by others in which case it will be useful to have somewhere to talk about it
The Spike Man said:
Hi,
I am experiencing issues with my Poco M4 Pro 4G and trying to unlock the bootloader. What I am currently doing is the following;
I enabled developer options, enabled usb debugging and OEM unlocking. I went to unlock status hit agree and hit pair and have waited 7 days for the timer to run out
I shut down the phone and then enter fastboot by holding the volume down button and the power button at the same time.
I downloaded the mi flash unlock tool from here and I logged in using the same account as on the phone, and got up to this screen.
View attachment 5681651
I then connect the phone which currently has the fastboot logo on to the computer but the button stays grey.
The following is what I have done;
I have installed adb tools. When the phone is booted and is connected to my computer I can see it via "adb devices" in CMD as admin. I can even send it to fastboot mode by "adb reboot fastboot"
I have installed the qualcomm drivers but I am unsure if they are the correct ones.
I have tried with different cables.
I have tried with different PCs.
The computer that I am using mainly to try and unlock the bootloader is a laptop and the specs are as follows;
Model: GP72 2QE Leopard Pro
Intel Core i7 5700HQ
16GB RAM
The other systems that I have tried are almost identifically specced both are AMD based on X570 Mobo and a Ryzen 7 3700X
Click to expand...
Click to collapse
Are u sure m4 pro 4g is qualcom ?
Thought is mediatek
aariss said:
Are u sure m4 pro 4g is qualcom ?
Thought is mediatek
Click to expand...
Click to collapse
It is mediatek.