Database Info

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.

Rooting & Other issues.

Hi all,
This is my first post to XDA and before I go any further I must say that i'm quite the idiot when it comes to android terminology and general modification of android as a whole. So if i'm in the wrong place, sorry!
I've got myself a One SV on t-mobile and have had it approaching 2 years now. I came to this phone from my previous HTC Desire (wish i kept it).
Back when i got my desire and started looking into customisation, performance etc i learnt a little about rooting and the pro's and cons surrounding it. "How hard can it be" so I went ahead and somehow installed CM on my desire. All was well and I never ran into too many problems. Now I've tried to do the same with my one sv (after having poor battery life, lack of storage and just all round lack of options) and i'm a little stuck.
I've tried to follow this guide > http://forum.xda-developers.com/showthread.php?t=2113671 and various others. The wording, however and process just seems beyond me. I've managed previously to unlock the bootloader via HTC however that's where i'm stuck (the easy bit).
BASICALLY what i'm asking, is for some kind hearted, patient soul to walk me through this, in dummies terms.
I'm almost certain i've soft bricked the device (don't ask me how) as there's some major issue now surrounding the dialer, contacts and sync. I receive the message "'android.process.acore has stopped" repeatedly, rendering my phone useless at the moment. I'm at a loss now and i need some help! any advice would be greatly appreciated.
Luke.

Ok, your bootloader is unlocked.
Do you have a working fastboot command? And what version of One SV do you have (k2u, k2ul,...)

A working Fastboot command... you've stumped me already im afraid. As i said i really haven't got a clue... i don't want to mislead you. How could i find out which version of the device i have? i've taken a peek behind the battery and i can't see anything.

From what i've just read i'd presume it's the k2_ul due to me being in England. If you know otherwise though, i can check?

You had to flash the unlock token with fastboot, right?
If that worked, you should have a working fastboot.
To know your version, connect your phone to pc, boot into bootloader (look if there is fastboot usb written on the phone screen) and open your cmd window on pc in the same foldrr, where yourfastboot.exe is.
Type into cmd window:
fastboot getvar all
Put the output here, without your serial and imei.

When starting the phone in "hboot" i recieve the following
UNLOCKED
k2-UL PVT SHIP S-ON RL
HBOOT-2.21 0000
Including various bits of other info. Then going on to read;
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
SHOW BARCODE
If i connect the phone to my PC in hboot it won't detect or anything to be honest. Should i first connect the phone to the PC normally? as if to transfer files etc and then turn off the phone and boot in hboot? or am i doing something wrong.
Thanks for all the help by the way!

When trying to select FASTBOOT and then selecting BOOTLOADER from the following menu I receive a list of "no gift file" "no image" etc.
So from what you're saying, it's likely i haven't followed the flashing procedure correctly?

Bootloader has two modes: the one you have described "scanning for files" is the bootloader mode. The other is fastboot mode.
But i know enough.
With the command
fastboot devices
you can check if your device is recognised.
Try to check this:
connect your phone to pc, boot into bootloader/fastboot mode (look if there is fastboot usb written on the phone screen) and open your cmd window on pc in the same folder, where your fastboot.exe is and run the cmd above. Look, what output you get in cmd window.
Maybe you need to install htc sync on your pc to get the latest drivers.

Hi, first off sorry for the late reply. Work has been mega busy. Bad news is that this hasn't miraculously solved its self over night. i've had a brick for nearly a month now with no way to call my contacts etc.
When starting the phone in fast boot (vol down and power on) and connecting to the PC i have no option for "fastboot usb" as you've described. I've tried to update HTC Sync manager. I've also tried various USB ports on the PC (i've had the issue before, whereby some of the ports haven't got the required power) and it's still not available. Is there any easy method to solve this?

Fastboot USB is not an option to choose, its only written on the screen, that you can see you are connected.
Take a look at this picture:
{
"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"
}
Connect your phone to pc, go to the folder where your fastboot.exe is and open a cmd window there.
Type into that cmd:
fastboot devices
The output should be your serial number.
---------- Post added at 12:33 PM ---------- Previous post was at 12:29 PM ----------
As you are unlocked, you should be able to flash TWRP recovery (if your fastboot is working). From TWRP you can backup whats left and flash stock rom.
All under tbe aspect, the device is not screwed up.

As you can see, these are the only options i'm getting. The phone is plugged in via USB 2.0 and isnt being picked up by the PC at all. I've updated the HTC Sync Manager in hope of solving it that way but still no luck. Any other advice?

Is your phone booting and stable enought to get S-off (rumrunner.us would be your choice)?
Maybe try another pc or cable, you need either S-off or a working fastboot.

I can use the phone. The only real problem is inability to access contacts and the message " Unfortunately, the process android.process.acore has stopped." appears every 5 seconds or so.
Sometimes the message stops appearing and the phone works normally. This is what confuses me. Why is it only happening most of the time, not all of the time?
I dont really understand S-OFF either. I'm sorry i'm so useless with all of the terminology but i can't seem to manage without a very basic explanation of how to do these things. I'm totally to blame for this. I shouldn't have messed with the phone in the first place. Leaving it to the experts like yourself is best.

Have you tried a factory reset to solve this?

yes twice, im really out of options now so i may end up having to buy a new phone or take it to an expert

If your phone boots and it is fine sometimes, than you should be able to "rescue" it.
When the phone is in the state of the picture you have posted today, connected to pc with usb, then you need to hit the power button once to access fastboot USB.
Look at your picture: you are in Hboot mode, Fastboot is highlighted.

Hey, I've since managed to get the phone to this state with the USB plugged into my computer. Where am i going from here? It seems the cables i'd been using were faulty. Only one works!

Yeah, that is what we need!
Now you should try to do 2 things:
- try to backup your data with a app like Titanium Backup (if there is anything left, after your factory reset)
- Connect your phone to pc in this fastboot usb state, go (on your pc) to the folder where your fastboot.exe is and open a cmd window there.
Type into that cmd:
fastboot devices
The output should be your serial number.

yes! am i on the right track?

Yes, you are!
Remove the picture, it don't need to be public.
Download this recovery: http://d-h.st/m7F
Rename the file to recovery.img and copy it into the folder where your fastboot.exe is.
Then, in the cmd window type the command:
fastboot flash recovery recovery.img
You should see the progress on the phone screen in the corner of the upper right side.

Accidentally wiped phone system OS using TWRP; how can I fix this?

I have basic to medium experience relating to rooting, fastboot, Odin, flashing, etc.
I accidentally wiped my phone's OS. My phone is a Samsung S5 Neo SM-903W with no root and no unlocked bootloader but with TWRP installed. My OS was Android 6.0.1
I tried downloading the stock firmware of Android 6 and flashing it using an SD card; TWRP said it was an invalid zip file and did not find an md5 ( even though it was the only file in the zip)
When I am in TWRP, my laptop recognizes me as "Samsung Mobile MTP Device" but when I am in download mode, my phone is not recognized at all. I think that I need to flash drivers on my phone, but I have no idea how to do so, and if so, how can I flash an "invalid zip file" onto my phone?
Please help me, or at least give me some advice.
Thanks (I'm an idiot for experimenting with advanced wipe )

MCMarsBoyee said:
I have basic to medium experience relating to rooting, fastboot, Odin, flashing, etc.
I accidentally wiped my phone's OS. My phone is a Samsung S5 Neo SM-903W with no root and no unlocked bootloader but with TWRP installed. My OS was Android 6.0.1
I tried downloading the stock firmware of Android 6 and flashing it using an SD card; TWRP said it was an invalid zip file and did not find an md5 ( even though it was the only file in the zip)
When I am in TWRP, my laptop recognizes me as "Samsung Mobile MTP Device" but when I am in download mode, my phone is not recognized at all. I think that I need to flash drivers on my phone, but I have no idea how to do so, and if so, how can I flash an "invalid zip file" onto my phone?
Please help me, or at least give me some advice.
Thanks (I'm an idiot for experimenting with advanced wipe [emoji14] )
Click to expand...
Click to collapse
The stock firmware cannot be flashed with TWRP. It is built to be flashed with Odin.
If there is a stock firmware that has been converted into a custom recovery flashable zip, you can flash that in TWRP, it has to be converted from the Odin flashable firmware though, it can't be the actual downloaded firmware, it isn't compatible with recovery. This is only if such a file is available or if you learn to convert the firmware yourself.
The easiest thing would be to get your device recognized with Odin while in download mode so you can flash the firmware, this should restore your device. Try installing the USB drivers for Samsung phones from here:
http://www.samsungusbdrivers.net/2016/12/samsung-galaxy-s5-neo-usb-driver-for.html?m=1
Flashing the stock firmware via Odin will also remove TWRP and replace it with stock recovery, you'll have to flash TWRP again.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

The thing is, I installed TWRP via Odin, so I know there was (or is) nothing wrong with the drivers on my laptop, but after the system wipe, my phone could only be recognized by Odin if it was charging through it or if I was at TWRP. (the 0:COM indicator was pink, not green) I will try the method you mentioned, but if I have any difficulties I will come back here.
Thanks.

MCMarsBoyee said:
The thing is, I installed TWRP via Odin, so I know there was (or is) nothing wrong with the drivers on my laptop, but after the system wipe, my phone could only be recognized by Odin if it was charging through it or if I was at TWRP. (the 0:COM indicator was pink, not green) I will try the method you mentioned, but if I have any difficulties I will come back here.
Thanks.
Click to expand...
Click to collapse
When you are in download mode, connect to PC then open device manager and see if it at least detects the device, even if it isn't recognizing it correctly. Does it show anything in device manager? What does it show?
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

I have a problem.
Since Samsung Drivers were already installed, I re-installed it by running the installer and prompting it to install it again. The problem is, when I try updating my "Samsung Mobile MTP Device"'s drivers, they say that the drivers installed are already at the latest version. I tried this several times, with a different type of drivers like ADB, and it still said that they were the latest (which is Samsung Mobile MTP Device).
Here is a screenshot to make sense of 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"
}
(If the screenshot doesn't show just tell me and I will try again)
Please help! I am in no situation of getting a new phone anytime soon!

MCMarsBoyee said:
I have a problem.
Since Samsung Drivers were already installed, I re-installed it by running the installer and prompting it to install it again. The problem is, when I try updating my "Samsung Mobile MTP Device"'s drivers, they say that the drivers installed are already at the latest version. I tried this several times, with a different type of drivers like ADB, and it still said that they were the latest (which is Samsung Mobile MTP Device).
Here is a screenshot to make sense of it
(If the screenshot doesn't show just tell me and I will try again)
Please help! I am in no situation of getting a new phone anytime soon!
Click to expand...
Click to collapse
Try installing Kies, it automatically installs Samsung drivers correctly.
But make sure kies is completely closed and not running in the background when using Odin, it interferes.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

MCMarsBoyee said:
I have a problem.
Since Samsung Drivers were already installed, I re-installed it by running the installer and prompting it to install it again. The problem is, when I try updating my "Samsung Mobile MTP Device"'s drivers, they say that the drivers installed are already at the latest version. I tried this several times, with a different type of drivers like ADB, and it still said that they were the latest (which is Samsung Mobile MTP Device).
Here is a screenshot to make sense of it
(If the screenshot doesn't show just tell me and I will try again)
Please help! I am in no situation of getting a new phone anytime soon!
Click to expand...
Click to collapse
Thank you! It works perfectly! Marking as solved.

MCMarsBoyee said:
Thank you! It works perfectly! Marking as solved.
Click to expand...
Click to collapse
Which parts of what I posted solved it for you? It will help others understand if they read this thread.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Samsung Galaxy S6 Edge Plus(SM-G928C) “Invalid Kernel Lenght” issue

Hi,
My S6 Edge Plus 32GB was functioning properly when i left it in a box for a while. After then, when i tried to boot it, it just showed a white screen and said “Could not do normal boot. Invalid Kernel Lenght!”. I tried to go to recovery mode yet it was not possible. Only i can do is to open download mode, but neither pc nor odin didn’t detect the phone at all. Plus, it was saying “FRP LOCK: on” I downloaded up to date Samsung Usb Drivers from the original source, but didn’t fix the issue either. Now I have a phone which i can not do any further action. What should i do friends?
(Battery was replaced with a replica one before. It opens up as i plug it and stays open without cable for a while then dies. Nothing changed other than original battery, and haven’t rooted before.)
Thank you!
{
"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"
}

Today it just showed up new alerts. I ordered a new cable and I will try to make odin to detect the phone. But then? I need help folks.

Emreturkmenoglu said:
Hi,
My S6 Edge Plus 32GB was functioning properly when i left it in a box for a while. After then, when i tried to boot it, it just showed a white screen and said “Could not do normal boot. Invalid Kernel Lenght!”. I tried to go to recovery mode yet it was not possible. Only i can do is to open download mode, but neither pc nor odin didn’t detect the phone at all. Plus, it was saying “FRP LOCK: on” I downloaded up to date Samsung Usb Drivers from the original source, but didn’t fix the issue either. Now I have a phone which i can not do any further action. What should i do friends?
(Battery was replaced with a replica one before. It opens up as i plug it and stays open without cable for a while then dies. Nothing changed other than original battery, and haven’t rooted before.)
Thank you!
View attachment 5306065View attachment 5306067
Click to expand...
Click to collapse
First of all I need to say: I'm no expert for your phone.
I just stumbled over this thread.
more to read for FRP:
OEM vs Bootloader lock.
The guide to unlocking the bootloader on the newer Samsung tablets seems to cause confunsion about what the OEM Enable switch does. First of all, the OEM switch has no direct bearing on the Bootloader lock. That switch has been around for quite...
forum.xda-developers.com
looking at your first photo from comment #1:
current binary: Custom
system status: official
sounds somewhat curious to me (but as I said: I'm no expert)
What *I* would suggest: "get the phone in a sane state"
1.
- read about "developer Mode"
- I'm unsure if debug mode is needed to flash stock or that the phone is seen by the PC
2.
- fix your PC, so that the phone is seen by PC
lastest USB Driver:
Android USB Driver for Windows | Samsung Developers
The world runs on you.
developer.samsung.com
if that doesn't work try to set up a *clean* windows VM with VBox
Oracle VM VirtualBox
www.virtualbox.org
don't forget to install "VM Virtual Extension Pack" so that USB (Guest <=> Host) is okay
3.
reset your phone *after* you deleted your google account on phone, see above "FRP"
WARNING: ALL DATA will be lost, if you have no backup (at google or somewhere else)
4.
flash lastest stock with ODIN
you need an Odin Version which corresponds to the stock Android Version
see:
Odin Device Compatibility List | Odin Android Version Compatibility
Check out what Odin version you should use! Here's a list of Odin device compatibility. Odin Android version compatibility with Nougat Oreo and Pie firmware
www.droidviews.com
and
Download Odin Tool for Samsung Devices (All Versions) | DroidViews
Download Odin Tool for Samsung Devices. Samsung Odin download is available for free for Windows PC. The Latest Odin version is Odin3_v3.14.1.
www.droidviews.com
last stock is Android 7, if I got it right:
Download Samsung Galaxy S6 edge+ SM-G928F firmware
Download the latest Samsung firmware for Galaxy S6 edge+ with model code SM-G928F. Check out our free download or super fast premium options.
www.sammobile.com
5.
do what you initial want to do ( custom Rom flash or what-so-ever) now on the clean state of the phone.
good luck

rw_on_xda said:
First of all I need to say: I'm no expert for your phone.
I just stumbled over this thread.
more to read for FRP:
OEM vs Bootloader lock.
The guide to unlocking the bootloader on the newer Samsung tablets seems to cause confunsion about what the OEM Enable switch does. First of all, the OEM switch has no direct bearing on the Bootloader lock. That switch has been around for quite...
forum.xda-developers.com
looking at your first photo:
Click to expand...
Click to collapse
Hi,
The issue is, i can not boot the phone. If i were able to do it, of course i would sign in to my Google account and remove the lock with the help of the guide you attached. So, there is an endless loop unfortunately.
Thank you.

Emreturkmenoglu said:
Hi,
The issue is, i can not boot the phone. If i were able to do it, of course i would sign in to my Google account and remove the lock with the help of the guide you attached. So, there is an endless loop unfortunately.
Thank you.
Click to expand...
Click to collapse
Okay, I missed that.
But you're able to boot to download mode.
if so, try to flash TWRP recovery and with that format the partitions and flash stock
don't know if that helps regarding FRP, but maybe for the boot problem

rw_on_xda said:
Okay, I missed that.
But you're able to boot to download mode.
if so, try to flash TWRP recovery and with that format the partitions and flash stock
don't know if that helps regarding FRP, but maybe for the boot problem
Click to expand...
Click to collapse
So here is the update
I got a new cable. Odin detected my phone. But it got stuck at system.img with stock firmware. I tried many other odin versions. I tried different USB ports. Nothing changed. It gets stuck at something and can’t fix unfortunately. It showed a partition error as well. I tried a 4part repair firmware with a pit file, didn’t work. I tried a pit file with official firmware, didn’t work. I tried a boot_recovery file, didn’t work. I tried to load TWRP, didn’t work.
Here are the list of options I tried:
1-Stock firmware
2-TWRP firmware
3-Pit files
4-Repair firmware
5-Boot_recovery file
Here are the list of stuck positions at trials(mixed):
1-System.img
2-Nand Write Start!!
3-There is no pit partition
4-Re-partition operation failed.
5- Complete(Write) operation failed.
I think I’ve seen every error code can ever be seen through odin
Smart Switch didn’t helped either. Detects the phone but don’t list it on emergency list.
So now, for me, I ran out of options… Odin variable tested. Cable is working properly. Pc is running properly.
From now on I don’t care if it dies, so don’t hesitate, it’s dead already for me, why not to try other things huh. Any further suggestions for me to give it a try?
By the way, a repairguy said it’s bricked and he might try to fix it with JTAG, yet if EMMC chip is dead there is nothing left he can do.

Emreturkmenoglu said:
So here is the update
I got a new cable. Odin detected my phone. But it got stuck at system.img with stock firmware. I tried many other odin versions. I tried different USB ports. Nothing changed. It gets stuck at something and can’t fix unfortunately. It showed a partition error as well. I tried a 4part repair firmware with a pit file, didn’t work. I tried a pit file with official firmware, didn’t work. I tried a boot_recovery file, didn’t work. I tried to load TWRP, didn’t work.
Here are the list of options I tried:
1-Stock firmware
2-TWRP firmware
3-Pit files
4-Repair firmware
5-Boot_recovery file
Here are the list of stuck positions at trials(mixed):
1-System.img
2-Nand Write Start!!
3-There is no pit partition
4-Re-partition operation failed.
5- Complete(Write) operation failed.
I think I’ve seen every error code can ever be seen through odin
Smart Switch didn’t helped either. Detects the phone but don’t list it on emergency list.
So now, for me, I ran out of options… Odin variable tested. Cable is working properly. Pc is running properly.
From now on I don’t care if it dies, so don’t hesitate, it’s dead already for me, why not to try other things huh. Any further suggestions for me to give it a try?
By the way, a repairguy said it’s bricked and he might try to fix it with JTAG, yet if EMMC chip is dead there is nothing left he can do.
Click to expand...
Click to collapse
disable FRP lock first

ineedroot69 said:
disable FRP lock first
Click to expand...
Click to collapse
How? I would love to disable it, but as I cannot even boot it, I can’t.

maybe fastboot might help (I haven't played with it enough though)
=> format, erase, flash ???
Fastboot (Tool)
www.droidwiki.org

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