Database Info

Need help rooting g2x 2.3.3

I just bought this phone off of eBay, and I'm trying to root it. From what I read I have to install CWM recovery then flash a rooted stock 2.3.3. So I try to install cwm recovery. http://forum.xda-developers.com/showthread.php?t=1056847 but I am stuck at step 4 after I plug in the usb to my phone while holding the volume bottoms... nothing pops up, no window saying detects a new APX device. Please help this noob.
Sent from my LG-P999 using Tapatalk

http://forum.xda-developers.com/showthread.php?t=1056847
Try this.. Your battery must be out. Double check in device manager that apx is not there. Sometimes it won't show an error or pop up Windows stating "apx device found". Also reboot your computer and try again. My computer for some reason doesn't recognize usb sometimes. Oh and use same usb port
Sent from my LG-P999 using XDA

Thank you but I have tried that post also. Just can't get the apx error to pop up so I can browse the apx folder. I tried just connect my phone to the PC with the phone on but it just doesn't connect....I wonder if my phones usb port is messed up...it charges just fine though.
Sent from my LG-P999 using Tapatalk

Try another one. Reboot both phone and computer. Try a different usb port. It should pick it up. Then continue with your steps. Try installing lg drivers. 1st
Sent from my LG-P999 using XDA

I think did install LG drivers....if you mean that one .exe file call lgdriver...well I guess I'll keep trying hopefully it works.
Sent from my LG-P999 using Tapatalk

It should work then. Try a different usb cable and computer if possible.
Sent from my LG-P999 using XDA

Oh BTW is there any easier way?
Sent from my LG-P999 using Tapatalk

What version windows r u using? Vista have dat problem

I was using window 7. Going to go home later and try another cable with another laptop
Sent from my LG-P999 using Tapatalk

okay, so i tried 4 different types of usb cables and 3 different computers...2 are windows 7 and 1 is windows xp...still stuck at step 4...i dont understand...

There is no easier way. This is the simplest way. I just don't understand why your computer is not recognizing the phone. Maybe it's hardware problems? Did you check under device manager and didn't see apx???
Sent from my LG-P999 using XDA

No I don't see apx anywhere
Sent from my LG-P999 using Tapatalk

lilviet93 said:
No I don't see apx anywhere
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Ok, humor us for a sec (or maybe just me) open up your device manager, with battery out, proper button combo (power+both volume buttons?), phone plugged in and hit print screen on your computer keyboard, then open paint and hit paste. Save that as a JPEG and upload it here.
Sent from my LG-P999 using xda premium

{
"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"
}
[/IMG]
There...I even did power+volume bottons. I think there is something wrong with the usb of the phone. I plugged it in the pc with power on and nothing pop up dont even ask me to mount my sd card.

Did you click to open usb controllers. Apx should be in there
Sent from my LG-P999 using XDA

yeah i did, the phone just seem to won't connect at all my nokia phone connects just fine

lilviet93 said:
There...I even did power+volume bottons. I think there is something wrong with the usb of the phone. I plugged it in the pc with power on and nothing pop up dont even ask me to mount my sd card.
Click to expand...
Click to collapse
Weird... I am not seeing any LG drivers in your image? On my PC I have one LG driver under modem (this computer isn't set-up for flashing this phone, my laptop is)
I also used NVFlash (as One click wasn't working at that time due to having 2.3.4 from TMo) and I remembered that I had to install the LG updater tool first to get the latest drivers installed before I used NVFlasher and got everything to work.
I remember it was a real pain at the time due to having GB 2.3.4 from factory, I know you have 2.3.3 but try that step out as it might help.

so how would I use NVFlash to root my phone? If you could please explain the steps thank you

lilviet93 said:
so how would I use NVFlash to root my phone? If you could please explain the steps thank you
Click to expand...
Click to collapse
Wow...it's been so long...
I know I used the LG Updater tool to install the latest LG drivers on the computer
Then I DL'd and used the NVFlasher, following the directions for it (with out the drivers the computer won't see your phone, so you can't update/root it)
This is where it get fuzzy.. I'm sure this loaded CWM recovery on the phone, so all I had to do was boot into it and make a back-up recovery of the phone. Rebooted the phone as normal. Still had phone connected to PC.
From there I loaded the update.zip (of Eagle's Blood current file) to the mem card
Rebooted to recovery, wiped cache, etc.. as in the instructions. Updated zip from mem card. when done, rebooted. Went thru Googles setup. Rebooted again and phone was rooted.
I had all the treads subscribed on my old account, but I lost the log-in info and had to create a new one :-(

well this bring me back to being stuck at step 4 at the beginning of the post. when i try to install cwm via nvflasher my phone won't connect to the pc at all to install apx drivers

Photon Q not recognized by RSD lite in fastboot

Ive flashed many photon Q's before using RSD lite but for some reason now they wont even show up in AP Fastboot. IM not sure why but im wondering if it has anything to do with installing PDAnet a few weeks ago for htc drivers. RSD does however recognize my photon q booted normally. I can choose the file to flash and hit start, but where RSD used to reboot the phone into fastboot and start flashing, it says "The phone failed to switch to fastboot mode". Any help would be appreciated. I used to use RSD 6.1.4 and now use 6.1.5. This is happening with both versions. ive updated drivers, uninstalled and reinstalled drivers, uninstalled PDAnet.....

Have you tried forcing the device into fastboot mode yourself?
Code:
adb reboot bootloader

arrrghhh said:
Have you tried forcing the device into fastboot mode yourself?
Code:
adb reboot bootloader
Click to expand...
Click to collapse
the phone goes into fastboot mode. I can get it by holding vol up and down and power. The problem is that when in fastboot, it isnt recognized by RSD. where in the past it has been. it just stopped one day. the drivers fail and i go to device manager and cant find a driver that needs updating to get the phone to connect. if you know of a driver i need to install manually please let me know what it is cause nothing is jumping out as needing updating. thank you.

wbbjason said:
the phone goes into fastboot mode. I can get it by holding vol up and down and power. The problem is that when in fastboot, it isnt recognized by RSD. where in the past it has been. it just stopped one day. the drivers fail and i go to device manager and cant find a driver that needs updating to get the phone to connect. if you know of a driver i need to install manually please let me know what it is cause nothing is jumping out as needing updating. thank you.
Click to expand...
Click to collapse
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.

arrrghhh said:
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.
Click to expand...
Click to collapse
already had that. most recent version. uninstalled and reinstalled that as well. i have no idea why none of the photon Qs will connect now.

Try usbdeview uninstall and delete! all moto drivers and reinstall.
Photon Q &/or Note 3 on ting.com

arrrghhh said:
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.
Click to expand...
Click to collapse
rbeavers said:
Try usbdeview uninstall and delete! all moto drivers and reinstall.
Photon Q &/or Note 3 on ting.com
Click to expand...
Click to collapse
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.

wbbjason said:
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.
Click to expand...
Click to collapse
Did you try the Moto Device Manager? That's all I recall needing for Windows.

wbbjason said:
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.
Click to expand...
Click to collapse
If you haven't already, you can try putting the USB cable into a different USB slot. I didn't notice it before, but I had mine plugged in to a USB 3.0 slot. It worked for ADB, FASTBOOT and file transfers, so I thought nothing of it. Still the damn thing wouldn't be recognized in RSD Lite 6.5
I just switched it over to another usb slot(USB 2.0 port) and voila, works like a champ every time. You've probably already done this, but I thought I would just throw it out there.

arrrghhh said:
Did you try the Moto Device Manager? That's all I recall needing for Windows.
Click to expand...
Click to collapse
KoolBurnX8 said:
If you haven't already, you can try putting the USB cable into a different USB slot. I didn't notice it before, but I had mine plugged in to a USB 3.0 slot. It worked for ADB, FASTBOOT and file transfers, so I thought nothing of it. Still the damn thing wouldn't be recognized in RSD Lite 6.5
I just switched it over to another usb slot(USB 2.0 port) and voila, works like a champ every time. You've probably already done this, but I thought I would just throw it out there.
Click to expand...
Click to collapse
yeah i tried the device manager. uninstalled and reinstalled. and changing ports doesnt work. i have motorola drivers. like ADB QC Diag that i can install but im not sure its the right one. does anyone know the name of the driver that shows up in device manager when you plug in a photon q in AP fastboot?

wbbjason said:
yeah i tried the device manager. uninstalled and reinstalled. and changing ports doesnt work. i have motorola drivers. like ADB QC Diag that i can install but im not sure its the right one. does anyone know the name of the driver that shows up in device manager when you plug in a photon q in AP fastboot?
Click to expand...
Click to collapse
Not sure if this will help you, but here's a screenshot of Device Manager when I rebooted to bootloader (fastboot) mode.
{
"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"
}

When I was having trouble, i've also read that RSDLite can be picky about the USB cable you use sometimes. If you have extras or have the one your phone came with, you might wanna give it a shot.

Please Help me Fastboot AC

hi guys my friend gave me this one x with one problem, phone is rooted. The issue is there is no OS on the phone. It will only boot into TWRP. he accidentally deleted everything and now I cannot get a rom copied back to it. When plugged up to a PC via USB, I always get "Unknown device" error from PC. Tried ADB but cannot get the phone to go to Fastboot USB
Bootloader says Fastboot AC look the pictures
Thank u very much for ur help
{
"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"
}
[/URL][/IMG]

Download min adb fastboot and let PC see the device. Then run a ruu via fastboot
Sent from my One X using Tapatalk
---------- Post added at 01:50 AM ---------- Previous post was at 01:44 AM ----------
Follow this thread.
http://forum.xda-developers.com/showthread.php?t=2593037
Sent from my One X using Tapatalk

Exactly what I would have said, good advice.
Sent from my Evita

marknoll said:
Download min adb fastboot and let PC see the device. Then run a ruu via fastboot
Sent from my One X using Tapatalk
---------- Post added at 01:50 AM ---------- Previous post was at 01:44 AM ----------
Follow this thread.
http://forum.xda-developers.com/showthread.php?t=2593037
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
Hi., thanks for ur help
I do not understand that I do, i have the Minimal ADB and Fastboot and my phone dont show fastboot USB
just fastboot or fastboot AC and i type fastbooot devices and nothing appears

Open cmd window inside min adb.. On open field,hold shift right click and chose "open cmd here" in that cmd prompt type fastboot devices. See if it sees it now. More than likely drivers will install once u open cmd in min adb. Try that
Sent from my One X using Tapatalk

Have you actually installed any drivers? If you don't have drivers installed no amount of messing around with fastboot is going to work. You can get the drivers by installing HTC Sync Manager, then connecting the phone in fastboot mode, and the drivers should install.
Sent from my Evita

timmaaa said:
Have you actually installed any drivers? If you don't have drivers installed no amount of messing around with fastboot is going to work. You can get the drivers by installing HTC Sync Manager, then connecting the phone in fastboot mode, and the drivers should install.
Sent from my Evita
Click to expand...
Click to collapse
nothing happen
i have installed HTC Sync Manager and htc Driver when i plug the phone show fastboot ac and the computer show unknown device
and sometimes when i plug says Fastboot Never Fastboot USB the pc never recognized

marknoll said:
Open cmd window inside min adb.. On open field,hold shift right click and chose "open cmd here" in that cmd prompt type fastboot devices. See if it sees it now. More than likely drivers will install once u open cmd in min adb. Try that
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
fastboot devices doesnt show anything

It's possible that you have a faulty usb port on the phone, it shouldn't usually say fastboot ac on the screen while connected to a usb outlet. Are you using a usb 2.0 port?
Sent from my Evita

timmaaa said:
It's possible that you have a faulty usb port on the phone, it shouldn't usually say fastboot ac on the screen while connected to a usb outlet. Are you using a usb 2.0 port?
Sent from my Evita
Click to expand...
Click to collapse
i think is the usb charge port
yes 2.0

What do you mean usb charge port?
Sent from my Evita

timmaaa said:
What do you mean usb charge port?
Sent from my Evita
Click to expand...
Click to collapse

I'll open it right now to see, i tell u later

juan0089 said:
fastboot devices doesnt show anything
Click to expand...
Click to collapse
Tim is right in the ports..maybe corrupt. But u opened a cmd prompt in ADT. Do so in min adb fastboot program. I had to do that when my drivers didn't properly install. When I opened cmd in min adb, drivers installed for me
P.s. make sure your device is in fastboot mode when opening cmd in min adb
Sent from my One X using Tapatalk

What was the outcome Juan?
Sent from my One X using Tapatalk

Did you fix this?

marknoll said:
What was the outcome Juan?
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I bought the charger ports and they sent me wrong, I'm waiting for the new wing for repair

Be very careful opening it up, LCD is VERY sensitive. I learned the hard way. ?

SOLVED - Unlocking 8T Problem Getting Unlock Code

Hello,
I am trying to get the unlock_token to nrequest my bootloader to be unlocked from OnePlus.
I downloaded the oneplus android drivers and ADB drivers and installed them. But when I try and run fastboot oem get_unlock_code it says waiting for device. Seems like a driver issue. Can anyone please help.
Thanks!

Have you rebooted your device to bootloader first?
Either with advanced bootmenu on the phone or by adb reboot bootloader ? it is supposed to look like 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"
}

Qnorsten said:
Have you rebooted your device to bootloader first?
Either with advanced bootmenu on the phone or by adb reboot bootloader ? it is supposed to look like this.
View attachment 5180271
Click to expand...
Click to collapse
Thanks for replying!
Yes, I rebooted to the bootloader with both volume buttons + power and via adb reboot bootloader.
I have oem unlocking and usb debugging on in dev settings too.
I can get adb to see the device but not fastboot.

Im having this same issue. I just reloaded Windows on ALL my computers... Now I cant get fast boot drivers to work. I never have had an issue like this. I think Windows 20H2 broke the drivers, lol. I'm frustrated because I am SIM unlocked but cant get the drivers to recognize the device. Can you link to the drivers you used?

Scott said:
Im having this same issue. I just reloaded Windows on ALL my computers... Now I cant get fast boot drivers to work. I never have had an issue like this. I think Windows 20H2 broke the drivers, lol. I'm frustrated because I am SIM unlocked but cant get the drivers to recognize the device. Can you link to the drivers you used?
Click to expand...
Click to collapse
I will post the links when I get back to my pc.
On another note I tried installing fastboot in linux to avoid the hassle.. Apparently it's broke there too (Debian/ubuntu).

.oODeRPLyfeOo. said:
I will post the links when I get back to my pc.
On another note I tried installing fastboot in linux to avoid the hassle.. Apparently it's broke there too (Debian/ubuntu).
Click to expand...
Click to collapse
What version of fastboot are you using in linux? I'm running Linux Mint 20.1 (based on Ubuntu Focal) and I had no issues getting my unlock code with fastboot. My fastboot version is 1:8.1.0+r23-5ubuntu2.

Lost Dog said:
What version of fastboot are you using in linux? I'm running Linux Mint 20.1 (based on Ubuntu Focal) and I had no issues getting my unlock code with fastboot. My fastboot version is 1:8.1.0+r23-5ubuntu2.
Click to expand...
Click to collapse
My bad I was using Kali on a VM when I had that issue. I was able to run it in WSL - 1:8.1.0+r23-5ubuntu2. Although I continue to have issues.

Scott said:
Im having this same issue. I just reloaded Windows on ALL my computers... Now I cant get fast boot drivers to work. I never have had an issue like this. I think Windows 20H2 broke the drivers, lol. I'm frustrated because I am SIM unlocked but cant get the drivers to recognize the device. Can you link to the drivers you used?
Click to expand...
Click to collapse
I downloaded fastboot from oneplus here. I uninstalled the one plus drivers i found in the one plus forum because one plus says that you dont need to download any driver win10 will run your phone automatically. But here is the link to the community post and driver.
I also tried Minimal ADB and Fastboot to no avail. I disabled secure boot to disable driver signing which reminds me... Ran it as Admin on a USB 2.0 port etc. etc.

Have you check in device manager (when on windows) or similar for your linux dist. What your device is being detected as when you plug it in while in fastboot mode?

It has a question mark when the phone is in bootloader mode while plugged into pc.
I tried to install the drivers through device manager. Win did not like that so I disabled driver signing to bypass. but it said all the drivers I had downloaded where no good.

.oODeRPLyfeOo. said:
It has a question mark when the phone is in bootloader mode while plugged into pc.
I tried to install the drivers through device manager. Win did not like that so I disabled driver signing to bypass. but it said all the drivers I had downloaded where no good.
Click to expand...
Click to collapse
Have you tried the drivers that come with the phone that show up when you plug in the phone without usb debugging turned on?

.oODeRPLyfeOo. said:
It has a question mark when the phone is in bootloader mode while plugged into pc.
I tried to install the drivers through device manager. Win did not like that so I disabled driver signing to bypass. but it said all the drivers I had downloaded where no good.
Click to expand...
Click to collapse
Wait... You're using WSL or VM's? I can imagine there would be some headaches going from several layers of windows hardware control to linux udev rules... Try either the native windows fastboot or go to pure linux. You might even be able to get it working booting from a USB drive so you don't need a permanent install.
Linux Mint 20.1 was just released. Download the .iso and burn that to USB and boot from there. You can apt install software even after booting from USB. Install fastboot and give it a go (that's the version I used to get my unlock code).

I ended up forcing the google stock adb and fastboot drives from here: Get the Google USB Driver | Android Developers
This allowed me to get ADB and Fastboot to recognize it. Now I tried another set of drivers linked in a blog post but Windows gave warning and erros about not being certified or tampered. I will try the ones listed about and see what happens. I still do not have the EDL Mode drivers working. I need those too
EDIT: The drivers listed above are the same as the ones I cant get to work.

Found the EDL mode drivers. They are linked in the MSM Tool thread. On the same note, you can force windows to install the driver if you go to the Additional Updates link in the Updates screen. I could anyways.

Scott said:
I ended up forcing the google stock adb and fastboot drives from here: Get the Google USB Driver | Android Developers
This allowed me to get ADB and Fastboot to recognize it. Now I tried another set of drivers linked in a blog post but Windows gave warning and erros about not being certified or tampered. I will try the ones listed about and see what happens. I still do not have the EDL Mode drivers working. I need those too
EDIT: The drivers listed above are the same as the ones I cant get to work.
Click to expand...
Click to collapse
I am going to give it shot now! Congrats on getting your code and thank you for keeping us up to date on your progress.

Lost Dog said:
Wait... You're using WSL or VM's? I can imagine there would be some headaches going from several layers of windows hardware control to linux udev rules... Try either the native windows fastboot or go to pure linux. You might even be able to get it working booting from a USB drive so you don't need a permanent install.
Linux Mint 20.1 was just released. Download the .iso and burn that to USB and boot from there. You can apt install software even after booting from USB. Install fastboot and give it a go (that's the version I used to get my unlock code).
Click to expand...
Click to collapse
Lol, so I ssh into my VM thru WSL on my Win10 box. That should work right.
No I tried each separately, first windows then I thought maybe linux would work so I booted up oracle VM. That was a no go then I remembered I had WSL and that might work better since it's more apart of the OS than Kali.
I'm going to try what Scott did. If that doesn't work I'm going to buy a usb card and boot up linux as you did.
Thanks!

Solved! Thank you all for your help. Scott your tidbit of information on forcing the drivers was what I needed.
After downloading the drivers from google and trying to install them through device manager and browsing to the folder where they where it said the best driver was already installed. So I clicked on search for updated drivers through windows update on the same screen.
Under check for updates on the windows update page I clicked on view optional updates. Low and behold the android driver from google was there. I installed it, rebooted went into bootloader and ran fastboot. It worked!
C:\fastboot_windows> fastboot.exe oem get_unlock_code
...
(bootloader) Serial Number:
(bootloader) ====================================
(bootloader) 0x00
(bootloader) ====================================
(bootloader) Unlock code:
(bootloader) ====================================
(bootloader) 0x00
(bootloader) 0x00
(bootloader) ====================================
OKAY [ 0.042s]
finished. total time: 0.042s

You can force the Qualcomm EDL mode drivers that way as well. It was not like this in earlier builds of Windows.
Im just waiting on the unlock code. I have an 8 to play with in the meantime.

Scott said:
You can force the Qualcomm EDL mode drivers that way as well. It was not like this in earlier builds of Windows.
Im just waiting on the unlock code. I have an 8 to play with in the meantime.
Click to expand...
Click to collapse
I'm waiting on the code from OnePlus as well... Submitted my unlock request a week ago.
Edit... Just showed up!

Scott said:
You can force the Qualcomm EDL mode drivers that way as well. It was not like this in earlier builds of Windows.
Im just waiting on the unlock code. I have an 8 to play with in the meantime.
Click to expand...
Click to collapse
Yes thats correct, I forgot to mention that I had already downloaded and it didnt take as well but it did show up as one of the drivers that I could install along with the ADB Drivers.

My phone is locked

My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+

karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
Do you have ADB? is so do
Code:
adb reboot

karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
are you using windows? if so have you installed the usb driver? In device manager when you add a device, it will show as an unknown or fastboot device then you just need to add the driver to be able to send probably a fastboot request.
Code:
fastboot reboot
Spoiler: DRIVER STEPS IF YOU NEED
{
"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"
}
All you need is the usb driver, you can get from android studio, your manufacturer, or you can try this one from nvidia for the shield, I use it on my phone and it works fine to be able to send fastboot requests
Shield Drivers.zip
drive.google.com

jenneh said:
are you using windows? if so have you installed the usb driver? In device manager when you add a device, it will show as an unknown or fastboot device then you just need to add the driver to be able to send probably a fastboot request.
Code:
fastboot reboot
Spoiler: DRIVER STEPS IF YOU NEED
View attachment 5756167View attachment 5756169View attachment 5756171View attachment 5756173View attachment 5756175
All you need is the usb driver, you can get from android studio, your manufacturer, or you can try this one from nvidia for the shield, I use it on my phone and it works fine to be able to send fastboot requests
Shield Drivers.zip
drive.google.com
Click to expand...
Click to collapse
Does ADB work too?

Arealhooman said:
Does ADB work too?
Click to expand...
Click to collapse
Not in this case bc the user's phone is stuck in recovery, adb is an option we can access only when the device is posted into the actual system, and we have enabled developer options, then usb or wireless debugging, then lastly adb connect. Fastboot skips everything and lets us run commands when the device is not completely online or loaded into the system

jenneh said:
Not in this case bc the user's phone is stuck in recovery, adb is an option we can access only when the device is posted into the actual system, and we have enabled developer options, then usb or wireless debugging, then lastly adb connect. Fastboot skips everything and lets us run commands when the device is not completely online or loaded into the system
Click to expand...
Click to collapse
Ah, i get it now, but doesnt samsung not have fastboot

Arealhooman said:
Ah, i get it now, but doesnt samsung not have fastboot
Click to expand...
Click to collapse
I honestly don't know, haha. I just saw this post, remembered myself in the same boat last year for a different device, and wanted to share what worked for me.

jenneh said:
I honestly don't know, haha. I just saw this post, remembered myself in the same boat last year for a different device, and wanted to share what worked for me.
Click to expand...
Click to collapse
Well, it was a good idea, but I do not think samsung supports fastboot

Arealhooman said:
Well, it was a good idea, but I do not think samsung supports fastboot
Click to expand...
Click to collapse
That's Super interesting knowledge. Thank you for sharing that with me. All the tricky ways samsung likes to use to keep things "safe". Almost makes me want to get one to play cat and mouse too but I already have an awful phone with it's own dastardly tricks. A "Nokia" mtk device with a Preloader instead of a bootloader. A "1 second handshake process" to be able to access or communicate with the preloader, no recovery, no bootloader menu, no fastboot oem commands. Haha. Terrible!

jenneh said:
That's Super interesting knowledge. Thank you for sharing that with me. All the tricky ways samsung likes to use to keep things "safe". Almost makes me want to get one to play cat and mouse too but I already have an awful phone with it's own dastardly tricks. A "Nokia" mtk device with a Preloader instead of a bootloader. A "1 second handshake process" to be able to access or communicate with the preloader, no recovery, no bootloader menu, no fastboot oem commands. Haha. Terrible!
Click to expand...
Click to collapse
I don’t even know what a preloader is could we continut talking and you can explain in dms? And a ”1 second handshake process”….

Arealhooman said:
I don’t even know what a preloader is could we continut talking and you can explain in dms? And a ”1 second handshake process”….
Click to expand...
Click to collapse
Spoiler: SHOW
Since I haven't messed with a samsung phone in almost a decade, I may be wrong, but if I had to guess, I would think that Samsungs come with a Preloader too, which is why there is a need for an external program like Odin.
But what a preloader is, is a layer below the Bootloader, it is what allows certain MTK or Qualcom devices to even be able to access the Bootloader.
I am a Nooby Cake and don't know much about anything, I just read a lot but if you are interested in what I have already read I started writing down the links for preloader knowledge on the last comment on this page of this thread and it continues into the next with nerdy rambling bs.
https://forum.xda-developers.com/t/mapping-out-the-g20s-internals.4416907/page-2
You can pm any questions just know I don't know much more than what I share on my threads haha. But I try to learn more everyday

karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
Go to a service centre. Repair or replace the power button. That's the best thing you can do.
ADB or FASTBOOT won't work at that situation.

.

Goddamn_srilankan said:
Go to a service centre. Repair or replace the power button. That's the best thing you can do.
ADB or FASTBOOT won't work at that situation.
Click to expand...
Click to collapse
You are telling the truth. Unfortunately, the charge does not end. lol

The first thing that came to my mind was adb, but the computer definitely does not see the device.
If I had a chance to reboot. Maybe it can see it, but it doesn't charge or I can't reboot with any key combination.
I guess the only thing to do is to repair the power button.
thanks everyone <3

karmastir said:
The first thing that came to my mind was adb, but the computer definitely does not see the device.
If I had a chance to reboot. Maybe it can see it, but it doesn't charge or I can't reboot with any key combination.
I guess the only thing to do is to repair the power button.
thanks everyone <3
Click to expand...
Click to collapse
<3