Today i left my g5 in service for screen in screen effect. After few hours man from service call me and he told me that he cant repair my phone because phone is rooted. Wtf? I buy brand new in store and i didnt root. He show me lg server and it write that my phone is rooted. I take my phone and install 3 apps and it shows that my phone is NOT rooted. And i didnt unlock bootloader. What can i do?
{
"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"
}
Have you requested a bootloader unlock key from LG Developer website?
No. I find on hidden menu by rtc that my phone is triger like root one by instaling app superuser. To me that is too funny. Installing app like superuser lose waranty
Can i find out are the bootloader unlocked or locked?
BrunoSlivar said:
Can i find out are the bootloader unlocked or locked?
Click to expand...
Click to collapse
Get the adb tool from here install and do the following:
1. Enable USB-Debugging on your phone. USB-Debugging is required for the commands “adb” and “fastboot” to work. To enable USB-Debugging, go to Settings >> About phone >> Software info and tap Build number 7 times. Return to the previous screen, select Developer options and enable USB-Debugging.
2. Open CommandPrompt or Terminal and enter the following ADB command to reboot into the bootloader:
Code:
adb reboot bootloader
If ADB is not detecting your device try switching your phone's USB mode from Charging to MTP or PTP.
3. Type and see you you get info on the device:
Code:
fastboot oem device-info
4. Reboot device
Code:
fastboot reboot
I find this:
I would uninstall the root app and get the phone to warranty again. Did they cancel it?
I dont have that app. I delete app after instal. Same day
BrunoSlivar said:
I dont have that app. I delete app after instal. Same day
Click to expand...
Click to collapse
Then do factory reset just to be sure and make the trip again to service.
He do factory reset in service. Phone was triger like root one on lg server after installing superuser app.
BrunoSlivar said:
He do factory reset in service. Phone was triger like root one on lg server after installing superuser app.
Click to expand...
Click to collapse
So you actually got your device repaired on warranty?
P.S. The command to check for bootloader status is fastboot getvar unlocked not fastboot oem device-info
No. He give me phone with problem that i left it. He connect my phone on lg server and there write that my phone is rooted. And my phone have locked bootloader and cant be rooted without unlock bootloader. He cant repair my phone under the waranty because my phone are triger like rooted.
BrunoSlivar said:
No. He give me phone with problem that i left it. He connect my phone on lg server and there write that my phone is rooted. And my phone have locked bootloader and cant be rooted without unlock bootloader. He cant repair my phone under the waranty because my phone are triger like rooted.
Click to expand...
Click to collapse
Try to go to LG service if you went to your carrier service/third party seller and the other way around, if you went to LG service in the first place.
I contact other lg service that i have and they told me if the lg server triger phone like rooted that is rooted.
It may be possible that your phone got flagged as "rooted" when it was checked in the service because of that app you had installed. I suppose the verification software that they have and use checks for certain files that are known to be installed on rooted phones and flags the verified device as "rooted" even though it doesn't really have root capabilities. This is bad news.
To verify what i said you could go to a different LG service shop and see if your device is flagged as "rooted". Maybe you can try and convince someone over at the LG shop that you installed, for whatever reason that app (fool a buddy of yours that you have root on your phone etc.), and you have not obtained root capabilities because you have not unlocked bootloader which is mandatory for obtaining root. Maybe you can find a reasonable person that can remove the "rooted" flag and accept the display repair on warranty.
Found another user with this kind of problem here but it's a different variant of the phone (T-mobile H830)
Something bad is with LG
Hope i will get something from them. New phone without this or to fix mine. For me is same because my phone is like new one.
On monday i will contact them because i get phone numb. from lg and i will post what they told me.
[emoji120]
Good luck!
They send me that i leave phone in service and they will fix it under the waranty
???
Great news! I'm happy for you and i hope your get your device repaired as soon as possible Cheers!
Related
Hi,
I have an Samsung Galaxy S3 I9300, unfortunately it is carrier locked to Telenor, and I have accidentally updated it to android 4.3, where the EFS version has changed.
I have already rooted it with Odin and CF-Auto-Root, but can't find any damn way to unlock it (don't even mention the "pay for code" sites, i'd rather crush this phone in my hand than pay a cent for unlocking it, free way is the only one to go)
Do you have any ideas? If you need any more information then just ask, I will tell anything you need.
Better crush it now and save yourself some time. Samsung changed the efs for a reason, that reason stops you unlocking it.
boomboomer said:
Better crush it now and save yourself some time. Samsung changed the efs for a reason, that reason stops you unlocking it.
Click to expand...
Click to collapse
Hmm, I think I can make it, maybe not by unlocking it "illegally" but by asking the carrier (I know the person who has bought the phone locked, will ask him to call the carrier and ask for unlock code because he needs to go to another country where he cannot use his SIM card, these bastards need to respect their clients.
I still need to downgrade it to 4.1.2 tho, version 4.3 just sucks and i need to charge the phone 3 times a day if i want to use it normally, also everything is laggy and launching a few apps causes a crash to the menu very often.
I read that it is kinda troubled, because the bootloader changed and now wont allow to flash an older one, but I can flash stock 4.1.2 ROM which supports EFSv2 and that only the LTE version of SGS3 cannot be downgraded, is it right?
I attach a screen from Phone Info app, let me know if it is possible to safely downgrade to 4.1.2 and where should I head in order to do it.
{
"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 unlock code (NCK) from the carrier, but after trying it i got an "Network unlock unsuccessful" message...the phone is still locked and I have already tried unlocking it 2 times (first because I thought it was asking for SIM PIN lock, and now with that code which I'm 100% sure is correct but the phone is acting weird) and I'm kinda scared to try it again because it may get locked permanently (i think?) and I will need to pay for some defreeze code..
I searched a bit and found out that other people also had this problem, and they fixed it by doing this:
In order to successfully unlock the phone, this had to be done firstly:
1. Make sure that wifi and flight mode is turned off
2. Go to the Dial pad and dial *#197328640#
3. Click on number [1] UMTS > [1] Debug screen > [8] Phone Control > [6] NETWORK LOCK
4. You will see 3 options
5. Please click on number [1] Perso Sha256 INFO, the screen will change slightly
6. Please hit the MENU button then when the menu pops up please carefully hit BACK to return to the previous screen
7. Please click on number [2] Perso Sha256 ON, the screen will change again to a one line message
8. Restart the phone on the screen by holding the power button and click RESTART
9. Reattempt to enter the code
10. Now the phone is supposed to accept the unlock code.
Click to expand...
Click to collapse
but the problem is that after dialing that code, all I get is "Not registered on network" error. I'm running stock ROM updated to 4.3 (from phone) but the phone is rooted, may this be the cause?
I will try calling that carrier later but im 100% sure they will just tell me to try again, and im also 100% sure that the code I entered was correct.
I am doing it the "legal" way and it also doesn't work, so is this damn phone just unlockable, even the carrier who locked it cannot do anything?
Edit
If nothing will work with that code then I will maybe try doing this:
http://forum.xda-developers.com/showpost.php?p=50463614&postcount=7
however I'm not really positive about it, it will very likely fail. It's a complete bull**** that this phone cannot be unlocked even by the carrier who locked it...
Guys i have no idea, i've flashed stock 4.3 ROM from Telenor to unroot it and factory formatted the phone (from android recovery) but still after entering the code it says unsuccessful...Any damn ideas about this? I managed to get into the Network Lock menu from *#0011# and Key Input->Q0 but it just says MENU NOT EXIST current command is 186. Not even the legal way to do it works, so I'm just supposed to throw this phone away?...
Hello Everyone!
I need urgent help from you all because I am currently stuck in a very bad situation. Please please please!! Help me to get out of this. Let me start from the beginning of whatever I did. This is going to be a very long post so please bear with me.
Why did I try to root my device?
I have Realme 1 which works on Android 9 and does not support internal screen recording. So I thought rooting would help me and I would be able to create gaming videos.
1st Phase:
I researched about how to root my device.
I came to know that first I’ll have to unlock my bootloader.
I tried to unlock my bootloader and when I was running the necessary commands like fastboot reboot, it simply showed, “Waiting for device…..”
Now confused, I went to the Device Manager and uninstalled Android and its drivers from the category of other devices by mistake. Now, my problem was that, how to pass commands to my device?
Next, I deleted everything, and started from scratch. This time, I connected my device (via the same USB cable) and I did something (I don't exactly remember what I did, but ultimately it lead me to Windows Update, where I clicked on View Optional Updates and updated the driver. I am attaching a screenshot of what I had installed.
Next, I downloaded platform tools, extracted them and in the address bar typed cmd and did the following checks to ensure that my device can receive commands.
When device was powered on:
adb devices
Returned: _________ device
Next command:
adb fastboot (Something like that which took it to the fastboot mode)
Next Command:
fastboot devices
Returned: _________ fastboot
Satisfied that I was going on well, I unlocked the bootloader using the respective commands.
2nd Phase:
Now I knew, my bootloader was unlocked, so I did the next step.
I switched to fastboot mode.
Downloaded boot_patched.img for Realme 1 C.50
Next, I pasted it into the platform tools folder.
Next, booted my device into the fastboot mode, and gave the flashing command.
Confirmed it on my device using volume up key.
Gave fastboot reboot command to reboot my device.
Downloaded Magisk Manager and rooted my device successfully.
Downloaded RootChecker app to be sure and got the positive result.
I downloaded the apps I needed.
Problem Phase:
I had downloaded a banking app but it didn’t work because my device was rooted, so I searched, “How to hide root from banking apps?”
I came to know that the solution for this was on Magisk Manager itself. Magisk Hide
So, I opened the Magisk Manager and I was shown a prompt to download something (Or maybe I downloaded something from the settings? It was something like system host module or something like that) Now I don’t exactly remember whether my device rebooted or not, but let me continue.
So, I went to settings, enabled Magisk Hide, selected the app from which I had to hide root and opened the app. It didn’t work.
I searched the internet and saw that I had to reboot my device as well.
After I did that I faced a more serious problem. The app was still not working and my sim cards were disabled.
Now I panicked, I did the ultimate thing for which I had rooted my phone, I downloaded the game and the screen recorder. I chose the internal sound recording option, it told me to download some Magisk Module for it to work. So I did it.But it still didn’t work.
Now I was sad, I didn’t know what to do. Then ultimately I opened my RootChecker app and check the root status of my device and you guys won’t believe what I saw.
" No proper root access granted "
Super Problem Phase:
I decide that I’ll unroot my device. So, I set down to work.
I got to know that I had to uninstall the Magisk Manager completely. I did so and my device rebooted.
There came a wave of relief, my sim cards started to work.
I thought that my device was unrooted now, so I opened my banking app and it showed: “Your device is rooted! You can not proceed further.”
I was confused, I checked the rootChecker and it clearly said the same thing. No root access.
So, I searched the web again and I was told that if I remove some files like su and one more file (I don’t exactly remember the name) then my device will be unrooted. I donloaded the es file explorer but didn’t find those files.
I searched the internet again and found something new. If I reset my device, then the root will go away. I was very happy. I did a factory reset of my device and this time I didn’t check the banking app, I did one more thing which I was not supposed to.
Ultra problem phase:
I got to the fastboot mode using the same commands in the adb terminal and decided to lock the bootloader. I thought that the app had detected that my bootloader was locked so that may be the reason it was not working. I gave the command:
fastboot flash lock
(it was something like this, I don't quite remember)
I confirmed that I wanted to lock my bootloader.
And that led me to my doom.
I rebooted my device using the command.
My device never started.
After the logo, or to say while booting I was shown this error:
"The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer care to fix it."
Then I though maybe I could just download the original boot and recovery file again then it would be all fine. I have those files and everything, when now I try to give those commands, they just show "Waiting for device...." Moreover the computer doesn't detect my device. The only thing I can do is just go to recovery mode.
Guys, I told you all everything that I knew please give me a detailed solution to the problem. I am also attaching some images so that you can see what exactly has happened.
Thanks in advance.
{
"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"
}
Sorry to say, but ... flashing unofficial/custom firmware and rooting has risk of bricking your device. And locking the bootloader was not the right/, best option
Maybe you have a chance to get it working again by flashing a complete firmware to it. Hopefully it will be successful after locking the bootloader
I have a Unlocked version bought from Amazon. I have not inserted a SIM card, just connected to WIFI. My goal is to root the phone. I have enabled developer options and USB debugging. I ran the entire debloat script and just the single "adb shell pm uninstall --user 0 com.qualcomm.qti.uim" , and the OEM unlocking option is still greyed out. I have restarted the phone several times and when I ran the entire debloat script, the google keyboard was removed (so I know there wasn't a connection issue with the phone) . Is there something I am missing? I am very new to this and it could be something stupid. Here is what I get when running the single 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"
}
121821 said:
I have a Unlocked version bought from Amazon. I have not inserted a SIM card, just connected to WIFI. My goal is to root the phone. I have enabled developer options and USB debugging. I ran the entire debloat script and just the single "adb shell pm uninstall --user 0 com.qualcomm.qti.uim" , and the OEM unlocking option is still greyed out. I have restarted the phone several times and when I ran the entire debloat script, the google keyboard was removed (so I know there wasn't a connection issue with the phone) . Is there something I am missing? I am very new to this and it could be something stupid. Here is what I get when running the single commandView attachment 5486991
Click to expand...
Click to collapse
Your problem is you have the unlocked variant, and you're going through steps for the T-Mobile variant.
You shouldn't need to jump through any hoops to bootloader unlock the unlocked variant.
Before anything you'll probably want to to a factory restore to fix anything that may have been messed up from the unneeded debloat script.
edale1 said:
Your problem is you have the unlocked variant, and you're going through steps for the T-Mobile variant.
You shouldn't need to jump through any hoops to bootloader unlock the unlocked variant.
Before anything you'll probably want to to a factory restore to fix anything that may have been messed up from the unneeded debloat script.
Click to expand...
Click to collapse
lol.. I don't think his issue is that he is following steps for the tmo variant (although might be unnecessary if he does in fact have an unlockable variant) more so his issue is that OEM unlock is greyed out preventing him from unlocking the BL.
If he does have an unlockable variant and shouldn't have to "jump through hoops" I tend to think maybe he doesn't have the variant he says he does and possibly has a locked tmo variant. Wouldn't be the first time someone has ordered a supposedly unlocked model from Amazon and got a carrier model instead but who knows.. need more information really to help such as the device model, the firmware it's on etc. to check and make sure it is an actual unlockable variant.. also what it says where it is greyed out such as if it says its carrier locked etc.
My issue is that OEM unlocking is greyed out, preventing my from unlocking the bootloader. I suspect that maybe I don't have an unlocked version. Here is pictures of the screen. Also, I have not inserted a SIM card into the phone, but it is connected to the internet via WiFi.
In order to unlock the bootloader, Android software requires a check made to Google for permission. Google will check the device hardware ID's against lists for permission. They blacklist carrier locked models, and probably blacklist stolen phones, unpaid phones, etc.
You have to allow Google Play Services to run with internet access in order to do this one time check (which will have to be redone if you fully restore the device back to factory state, such as using the MSM tool).
This is why the message says to connect to the internet (to allow the check) or to contact your carrier (to get your ID's removed from the blacklist).
oCAPTCHA said:
In order to unlock the bootloader, Android software requires a check made to Google for permission. Google will check the device hardware ID's against lists for permission. They blacklist carrier locked models, and probably blacklist stolen phones, unpaid phones, etc.
You have to allow Google Play services to run with internet access in order to do this one time check (which will have to be redone if you fully restore the device back to factory state, such as using the MSM tool).
That is why the message says to connect to the internet.
Click to expand...
Click to collapse
The phone was connected to the internet via WiFi, but I did not setup a Google account on it at the time. I've since returned the phone to Amazon, for a different model.
A Google account is not required, as it is only checking hardware IDs.
Google Play Services must be allowed to run with internet access. Did you confirm that had happened?
I believe the message changes once Google gets a negative response.
oCAPTCHA said:
A Google account is not required, as it is only checking hardware IDs.
Google Play Services must be allowed to run with internet access. Did you confirm that had happened?
I believe the message changes once Google gets a negative response.
Click to expand...
Click to collapse
I'm not sure if Google play services did run. I didn't stop it from doing so, that I know of.
So I tried installing a custom ROM on my Realme 6 a while ago and it didn't work out so I had to flash my phone with the stock ROM, after doing so, after every restart I get a boot message:
Orange State: Your device has been unlocked and can’t be trusted…Your device will boot in 5 seconds
The phone still boots alright but I cannot use google pay or specific services as it says that the phone cant be trusted.
Does anyone know of this and how to fix it? quite a frustration not being able to use my phone for paying anymore.
edit: i read that relocking the phone fixes it but i also read that you may hardbrick your phone. kinda lost.
soler37 said:
So I tried installing a custom ROM on my Realme 6 a while ago and it didn't work out so I had to flash my phone with the stock ROM, after doing so, after every restart I get a boot message:
Orange State: Your device has been unlocked and can’t be trusted…Your device will boot in 5 seconds
The phone still boots alright but I cannot use google pay or specific services as it says that the phone cant be trusted.
Does anyone know of this and how to fix it? quite a frustration not being able to use my phone for paying anymore.
edit: i read that relocking the phone fixes it but i also read that you may hardbrick your phone. kinda lost.
Click to expand...
Click to collapse
You unlocked the bootloader, you need to re-lock the bootloader, that is what the "device can't be trusted" message means.
Find a guide on the internet or a thread here that discusses unlocking/locking the bootloader on your specific model number, if other people with your exact model have re-locked their bootloader without bricking their device, follow the same instructions/steps exactly the way they did and you shouldn't have to worry about bricking the device if you carefully follow instructions to the letter.
If you already searched and found the solution, why did you come here to ask? It isn't like their is an alternative solution that can be found here. Lock your bootloader, that's it.
I found guides but wanted to make sure, anyway, I typed reboot bootloader command, and my phone restarts and is stuck with a message
{
"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"
}
soler37 said:
I found guides but wanted to make sure, anyway, I typed reboot bootloader command, and my phone restarts and is stuck with a message
Click to expand...
Click to collapse
Same happened with me brother...but in my case my twrp recovery got removed and now am stuck with this msg as in your post..and now i am little bit uneasy as i can get stuck on bootloop..what did you do after this?..did you flashed it again? Did it work?
Inevitable007 said:
Same happened with me brother...but in my case my twrp recovery got removed and now am stuck with this msg as in your post..and now i am little bit uneasy as i can get stuck on bootloop..what did you do after this?..did you flashed it again? Did it work?
Click to expand...
Click to collapse
Press and hold power + vol up and down, should turn on.
Anyway, I fixed my bootloader by flashing my phone with an older update.
I used this guide:
soler37 said:
Press and hold power + vol up and down, should turn on.
Anyway, I fixed my bootloader by flashing my phone with an older update.
I used this guide:
Click to expand...
Click to collapse
ya i know that process but i meant to ask that flashing twrp again caused any problem? or does the device even goes to stock recovery?
Inevitable007 said:
ya i know that process but i meant to ask that flashing twrp again caused any problem? or does the device even goes to stock recovery?
Click to expand...
Click to collapse
I didn't flash using twrp, I used SPFLASH tool and then after the process finished, my phone back to first update, I was then able to relock the bootloader using the normal commands.
soler37 said:
I didn't flash using twrp, I used SPFLASH tool and then after the process finished, my phone back to first update, I was then able to relock the bootloader using the normal commands.
Click to expand...
Click to collapse
ok thanks
Hi there! I need some help, I am trying to root my device and need a boot.img, but I cannot find a Rom for the x9 anywhere online.
This is my first time doing this, I got this phone just to mess around with rooting. But maybe I bought a bad phone for it.
If there are no Flash Roms online, what are the next steps? Can I use a Rom for the e9 which released alongside this phone? Sounds like it wouldnt work.. but IDK.
Looking for help from the experts ^^
Any help is appreciated.
Finally found one! Took over 2 hours to download a 2gb file O,O but it's finally done.
Now I am having problems getting into bootloader mode.
In developer mode with both OEM unlocking and USB debugging enabled.
Used the correct cmd prompt (adb reboot bootloader) but the phone just restarts.
I've tried restarting while holding the volume buttons.
VOL Down = Factory Test Mode, nothing works as expected there.
VOL UP = A boot menu letting me select from ~10 options, one of them is Boot to Bootloader. Selecting that simply boots normal, nothing special.
I have followed three guides:
How TO Root Vodafone Smart X9 Magisk without TWRP Recovery
If your Smart X9 is rooted using Magisk without TWRP Recovery. You can control a lot of features such as you can remove unwanted software.
www.getdroidpro.com
Vodafone Smart E9 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Vodafone with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
All seem logical enough, many similarities between them. I just cannot get into fastboot mode.
I've seen LOADS of threads with this same problem on this forum. And none of them have any solutions. So I think this is the end of the road. If nobody has figured it out .. then I am just out of luck I guess?
HalpNeeded said:
Forget, your phone have only 3 buttons
Click to expand...
Click to collapse
Hi @joke19 !
I havnt seen any of the guides mentioning needing a certain amount of buttons :O
How does that factor in - does that mean it cannot be rooted for some reason?
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
{
"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"
}
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
HalpNeeded said:
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
View attachment 5671635
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
Click to expand...
Click to collapse
did you manage to get this working?