Develop Bugs

[Q] Stuck in "demo" mode. NEED help please

Hello all,
I should start off by saying that I am not an expert in rooting and such. I can follow instructions easily, but I am by no means an expert with android. I recently purchased my Galaxy Note 10.1 off eBay. Unfortunately, to my surprise (though I probably should have known better) it is stuck in what I can only assume is the Samsung demo mode. The settings "app" does not exist and the WiFi is locked off, in the current state.
Here's what I've tried so far:
Factory reset via settings (had to do a work around using the S-Pen to actually get into the settings).
Hard reset via Power + Volume Up
Downloaded Kies, but it doesn't want to recognize/connect to the tablet.
Attempted to install via Odin, but got confused and it still didn't fix anything.
As well, every time I disconnect my tablet from my computer it powers off immediately.
What can I do? Any help would be very much appreciated, as I'm feeling extremely lost and discouraged.
EDIT 1: From what I've read thus far, it appears to be stuck in a sort of retail mode. Apparently demo mode is something different. Regardless I am still stuck
EDIT 2: FIXED!! I got it to work, and fixed/restored the tablet. I went to sammobile .com/firmwares and downloaded the current firmware, then installed via Odin.

[Q] Bricked my SM-G925T while attempting to root. PC doesn't detect it anymore.

My phone was on stock rom, 5.1.1, and I tried to root it using zedomax's guide (found on youtube here: /watch?v=G5HDG6caoog) but I ended up bricking it.
When attempting to flash the root kernel provided in that guide, Odin gave me a FAIL result, and after that I've been stuck in a blue screen with a message that says: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
So I downloaded both Smart Switch and Kies 3.0 and both have unable to detect my device, and Odin as well.
Can anyone tell me how to proceed from here? I cannot even turn off my phone, with either holding the power button. Holding volume down, home, and power button resets the screen into the same error above

I tried 4 different cables on different USB ports on my laptop, the phone is still not getting recognized. The phone is still stuck on the same blue error screen.
Device manager looks like this:
imgur.com/XhsQf3B

update:
upon reinstalling Samsung USB drivers and rebooting the laptop, it's now recognized in the device manager and Odin, but not Smart Switch or Kies.

Try flashing the stock firmware from Samsung several times, you may get lucky and return to stock. If you do and need your phone in order to make/receive calls/messages, leave it stock, root is not safe for this phone anymore.
Pp.

I managed to flash it back to stock firmware, however it has triggered the knox count by 1. It's working fine now.
So is it not possible to root this phone at this point?

sssiriusly said:
I managed to flash it back to stock firmware, however it has triggered the knox count by 1. It's working fine now.
So is it not possible to root this phone at this point?
Click to expand...
Click to collapse
This root method works just fine --> Here
Except I use the newest Unikernel --> Here

Find 7a won't boot to recovery, not recognised in USB at all

Hi all,
I'm turning to forums now because I'm desperately in need of help.
I have an Oppo Find 7a which I bought about 9 months ago. When I first got it I tried flashing Cyanogenmod to it (unsuccessfully), and then tried rooting the phone. I have since unrooted the phone, and am running Color OS v 1.2.5i and really really need to update. Problem is, I cannot seem to update the operating system. Here's what happens:
Phone fails to boot to recovery
In my attempts to install Cyanogenmod, I installed a custom recovery. However I couldn't get Cyanogenmod to flash properly, so I tried reverting to the stock recovery. Did that, which seemed to work fine. However, since rooting and unrooting my phone, I cannot boot into reocovery at all. When turning off the phone and then pressing power+volume down to try and boot in, the "OPPO" logo comes up as if trying to boot into recovery, then the phone just turns off and boots into normal OS. Have tried many things but can't seem to get into recovery at all. This means that when an OS update is detected (which it is), the phone tries to reboot into recovery to install the update and cannot. So I'm stuck on a very buggy OS and can't do anything to update. Before you suggest adb+fastboot solutions, please read below:
Phone not recognised in PC at all
When plugging the phone into a PC via usb cable literally nothing happens (aside from the phone detecting it is charging). The phone does not mount as a volume in Windows, the phone is not detected as a device in device manager, as far as the computer is concerned, the phone is not even there. I have tried having the phone plugged in and installing all the proper adb drivers, but this has still yielded no results. And yes USB debugging is definitely enabled on the phone. I don't know why, but for some reason I literally cannot plug my phone into a PC anymore which limits me a LOT in terms of fixing the problem above.
Basically I really need to update the OS on this phone and am compeltely stuck: nothing seems to work. Can anyone help me out here. What do I need to do?? Any help is greatly appreciated.

seem adb device in windows device manager when the phone plug USB at bootloader?
if yes, you can use adb+fastboot solution

Device descriptor failed after bootloader update

Hi all, learning fast, not there yet, so forgive me if I ask something less than brilliant here
I can't connect my Tab S 8.4 wifi to any pc anymore (tried 4 different PCs and 4 different cables) after upgrading bootloader with Odin last year.
I keep getting "device descriptor failed" in Device Manager (both win7 and win10).
My son did drop and break the usb/power port which I replaced myself. Could be a hardware error, but everything worked before and after my repair, just not after bootloader upgrade. Forgive me, I don't know which bootloader is currently installed, in any case one which works with android 5.1 and not with 7.1, which I unsuccessfully tried to flash.
COderbear was so kind as to direct me towards the bootloader, which I thought TWRP was.
Since I cannot connect to a PC, I cannot update the bootloader....catch 22...
Thx for ur input.
Ps Hardware failure is a possibility, but not conclusive guys. Tablet is working fine.

In what way have you been flashing stuff have you been doing anything on trwp or oden......

stinka318 said:
In what way have you been flashing stuff have you been doing anything on trwp or oden......
Click to expand...
Click to collapse
I used ODIN to update bootloader 1-2 years ago to flash an original Samsung ROM which was already rooted. After the bootloader flash I cannot connect to a PC anymore.
I n the mean time I have learned about TWRP and used it to flash a custom ROM, all via SD card, as I cannot connect to a PC.
The only one which did not get me stuck at the black Galaxy TAB S screen is the cm12.1 custom ROM with android 5.1.
All others (see above) with android 7.1 have gotten stuck.
I thought TWRP was the bootloader, but it isn't, kindly pointed out by COderbear in another thread. :good:
As I understand it, the only way to update the bootloader to a current version to successfully upgrade to a custom 7.1 ROM.
Since I cannot connect to any PC => "device descriptor failed", I cannot update the bootloader with ODIN.
So I cannot upgrade to an android version above 5.1. That's the problem.

Mace73 said:
I used ODIN to update bootloader 1-2 years ago to flash an original Samsung ROM which was already rooted. After the bootloader flash I cannot connect to a PC anymore.
I n the mean time I have learned about TWRP and used it to flash a custom ROM, all via SD card, as I cannot connect to a PC.
The only one which did not get me stuck at the black Galaxy TAB S screen is the cm12.1 custom ROM with android 5.1.
All others (see above) with android 7.1 have gotten stuck.
I thought TWRP was the bootloader, but it isn't, kindly pointed out by COderbear in another thread. :good:
As I understand it, the only way to update the bootloader to a current version to successfully upgrade to a custom 7.1 ROM.
Since I cannot connect to any PC => "device descriptor failed", I cannot update the bootloader with ODIN.
So I cannot upgrade to an android version above 5.1. That's the problem.
Click to expand...
Click to collapse
I have had a lot of Samsung device and this is a first i have heard of this i have flashed the wrong stuff and soft bricked things but never heard of having issues with the bootloader up date........

stinka318 said:
I have had a lot of Samsung device and this is a first i have heard of this i have flashed the wrong stuff and soft bricked things but never heard of having issues with the bootloader up date........
Click to expand...
Click to collapse
Yeah, but ur not me

I have a sneaky suspicion that it's the usb port which I've swapped.
I've found two threads somewhere on Google relating to using another cable, must be a hardware failure or substandard part.
Can't explain it otherwise.
There is no way to update a bootloader via SD, right?
Logical, the bootloader's the first thing it reads to start up.....
Anyway, thought it was worth a try to post a thread, u never know what crazy solutions come to pass in android world.... (iOS too for that matter)

Mace73 said:
I have a sneaky suspicion that it's the usb port which I've swapped.
I've found two threads somewhere on Google relating to using another cable, must be a hardware failure or substandard part.
Can't explain it otherwise.
There is no way to update a bootloader via SD, right?
Logical, the bootloader's the first thing it reads to start up.....
Anyway, thought it was worth a try to post a thread, u never know what crazy solutions come to pass in android world.... (iOS too for that matter)
Click to expand...
Click to collapse
Bootloader can only be updated with oden only any thing else won't work.......

It is not issue of fleshed software. I have this issue during last 2 months. Official service center didn't find any clue during 2 weeks so i get back my Tab. All story starts, i suspect, after 1 month using magnet cable. Then suddenly charging current start to be lower then usual (Galaxy Charging Current App) and i decide to check different chargers and PC. I found that tablet cannot connect to any PC - "device descriptor failed". During playing with "USB debug" on/off and USB modes i connected tablet to PC once. But during Odin flash it stuck in "Getting PIT file..." and i still didn't update anything.
I suspect that it is some hardware issue in part that responsible for USB communication.

Issue solved. Tried on different ports with combination USB-hub. On some ports it completely invisible, on some "usb device not recognized". But after two weeks once i get connected and Tab was detected - then immediately flash stock CQB1 with TWRP 3.1.0. Now it still detected by PC.
I suspect micro-crack in motherboard or some HW issue on some SW combination (modem SW).

Stuck in bootloader

Hello,
I have a Pixel 2XL that I had rooted and was working fine. I went to do an update to Android. Apparently it went through and did an update, and than somehow it became locked again, even though I had unlocked the bootloader fine. Now it is showing locked, even though I never locked it. Thoughts?
Update: I was unable to unlock it again, but it's not responding via USB despite showing up on Flashboot Devices.

Can you boot TWRP? If so put a factory ota or lineage on a thumb drive and flash it

Hello,
I have tried but the phone keeps rebooting when I try it. I've read that using non powered USB ports can cause that behavior, so I bought a powered USB 2.0 Hub and I am going to try that, even though I did the initial root using my desktop with non powered ports.