Develop Bugs

[Q] Phone won't boot after being off for two days, where to start?

My 15 Y-O was using my old MT3GS while waiting on parts for her iPhone 3G. Once the parts came in and her phone was back working, she turned off the MT3GS. Two days later she dropped her phone and broke her digitizer. She went back to the MT3GS but it wouldn't start. Her sim card is good, she's now using our phone of last resort, an old Samsung feature phone.
When I opened the back to pull the battery I found the sim card tray unlocked. I fixed the sim tray, pulled the battery, waited a few minutes and put the battery back. On startup it vibrated once, but nothing else happened. I assumed the battery was drained, so I stuck in on the charger overnight. When I woke up, the battery light was green indicating a full charge, but it still does the one vibrate and then a whole lot of nothing.
Any ideas or suggestions?

Is the phone stock or rooted?
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app

It's stock, but I picked it up from eBay and I've replaced all of the external hardware. (Digitizer and outer shell)
I did pull the sticker off the original shell and move it to the new shell, but it's obvious to see.

A few questions, are you running the froyo update? Do you have the sdk installed? Are you willing to root/unlock the phone?
If the answer to all these questions is yes then you can try to root/unlock the phone, install a custom recovery, do the nessasary wipes and reinstall your rom or even a custom rom of your choice. I'm not sure if its a hardware issue. Doing the above doesn't work then I would say it is a hardware issue.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app

Dvarl said:
A few questions, are you running the froyo update? Do you have the sdk installed? Are you willing to root/unlock the phone?
Click to expand...
Click to collapse
I'm running 2.2 (but not the updated release in the past week). I should, I've rooted and installed a custom ROM on my MT4GS. And I'm more than willing to root / unlock this phone.
Dvarl said:
If the answer to all these questions is yes then you can try to root/unlock the phone, install a custom recovery, do the nessasary wipes and reinstall your rom or even a custom rom of your choice. I'm not sure if its a hardware issue. Doing the above doesn't work then I would say it is a hardware issue.
Click to expand...
Click to collapse
Any suggestions on where to start?

I assume your on the 1.05 hboot? Check your hboot if it is you will need to unlock through htcdev.com. follow the instructions, and root that way. There is another thread on the forums that discuss this method. I did s-off early on so I won't be of much help with the official method.
http://forum.xda-developers.com/showthread.php?t=1500700
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app

Dvarl said:
I assume your on the 1.05 hboot? Check your hboot if it is you will need to unlock through htcdev.com. follow the instructions, and root that way. There is another thread on the forums that discuss this method. I did s-off early on so I won't be of much help with the official method.
http://forum.xda-developers.com/showthread.php?t=1500700
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
Click to expand...
Click to collapse
I can't check my hboot, since the phone won't start.
Also Windows sees an empty removable disk.
ABD and FASTBOOT command shows no devices connected.

If adb and fastboot won't read the phone then I'm at a loss. Sorry I wish I could be more helpful.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
---------- Post added at 02:42 PM ---------- Previous post was at 02:30 PM ----------
The same thing happens if you hold vol down + power? Just a single vibrate and a blank screen?
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
---------- Post added at 03:15 PM ---------- Previous post was at 02:42 PM ----------
I did some checking around and other people have had this problem too. Sounds like it is one of two things. A: it is a hardware issue. B: your yaffs partition got corrupted somehow. Neither of those can be fixed here. The phone would need to be serviced, but I would get a second opinion, I don't know all there is to know about the phone and I'm not a dev. You could try taking the phone in and have it looked at. The best of luck.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app

So what happens when you hit power is a single vibrate and then nothing. The phone won't change, won't turn on and then won't do anything until you pull the battery.
Dvarl said:
The same thing happens if you hold vol down + power? Just a single vibrate and a blank screen?
Click to expand...
Click to collapse
Interestingly enough, vol down and power does absolutely nothing. No vibrate, nothing. But after giving up, you can hit power to get the one vibrate....
---------- Post added at 02:25 PM ---------- Previous post was at 02:08 PM ----------
So I did a bit of thinking about this and wondered if the problem might be the LCD.
I pulled the battery
I hit vol down + power
I hit vol down again
I hit power
When I plugged it in via USB my PC recognized it and I was able to get the following from ADB.exe.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT06WPS10312 offline​
So now I'm fairly well convinced that the phone may be ok and it's just the LCD that's dead. But I need some assistance with validating the phone is ok before I consider spending $20 - $30 for a replacement LCD.

I had a similiar problem that turn out to be a bad battery. Wouldnt hold a charge and wouldn't boot. Is this the oem battery?
Sent from my openAOS Build of Android 2.3 (cyanogenmod edition) using xda app-developers app

[Q] Screen not working after entering recovery

Hello!
Ill just start from the beginning...
My girlfriend droped her HTC wildfire S and digitizer and LCD were broken.
Since local repair shop asked 100EUR to repair it, I decided to buy the parts
myself and give it a try (since there are alot of tutorials).
I managed to replace digitizer and lcd. I was able to start the phone, but the
touch screen didnt respond ...
I tried to find solution, but nothing really worked. I thought that maybe i could reset the phone to factory settings and that would fix the digitizer problem.
Unfortunately it didnt and I tried recovery option from that menu (that you bring up if you hold volume and that other smaller button at same time) and that just brought up some kind of picture with phone and exclamation mark. I waited for a while and nothing happened so i turned the phone off..
When I turned the phone back on, the screen was black (but there was vibration and sound, so I assume that it was able to start) and there was only light from the buttons at the bottom of the screen.
I searched everywhere for solutions, but it seems that most of them require me to have USB debugging on but I have no idea how to do this if i can't see anything and the digitizer is probably still not responding..
Long story short, I'm really confused and have no clue what to do next, if you need any further information, please ask!
Thanks in advance!

maanusav said:
Hello!
Ill just start from the beginning...
My girlfriend droped her HTC wildfire S and digitizer and LCD were broken.
Since local repair shop asked 100EUR to repair it, I decided to buy the parts
myself and give it a try (since there are alot of tutorials).
I managed to replace digitizer and lcd. I was able to start the phone, but the
touch screen didnt respond ...
I tried to find solution, but nothing really worked. I thought that maybe i could reset the phone to factory settings and that would fix the digitizer problem.
Unfortunately it didnt and I tried recovery option from that menu (that you bring up if you hold volume and that other smaller button at same time) and that just brought up some kind of picture with phone and exclamation mark. I waited for a while and nothing happened so i turned the phone off..
When I turned the phone back on, the screen was black (but there was vibration and sound, so I assume that it was able to start) and there was only light from the buttons at the bottom of the screen.
I searched everywhere for solutions, but it seems that most of them require me to have USB debugging on but I have no idea how to do this if i can't see anything and the digitizer is probably still not responding..
Long story short, I'm really confused and have no clue what to do next, if you need any further information, please ask!
Thanks in advance!
Click to expand...
Click to collapse
Hardware problem return it back to the shop

ngoralph said:
Hardware problem return it back to the shop
Click to expand...
Click to collapse
I dont think that is possible, since I already tried to fix it myself and theres no warranty.
If anyone got a clue how I could fix this problem then please let me know! : /

I'm not sure if it is so but I think you might try to clear S58 data with a gold card in order to get the screen to work.
So you need to make a gold card and boot into fastboot with the card inserted and do stuff.
But that's just a wild guess...

MrGuyFawkes said:
I'm not sure if it is so but I think you might try to clear S58 data with a gold card in order to get the screen to work.
So you need to make a gold card and boot into fastboot with the card inserted and do stuff.
But that's just a wild guess...
Click to expand...
Click to collapse
I've seen the words "gold card" few times around forums and some people have got their digitizer to work again and so on. Right now im really confused, why the hell did my lcd just shut down after entering recovery? I've read that theres some king of "Black screen bug" or something like that, I wonder if thats the case?
Is it possible to mess around with that gold card, even if I cant see anything? Because a) LCD is not working at this point b) USB debugging is not on, and I don't think I can even turn it on if LCD and digitizer are not working correctly.

hmmmm does gold card work for gsm?????? i remembered reading that its for cdma only??? not sure though
Sent from my Nexus 7 using xda premium
---------- Post added at 06:33 PM ---------- Previous post was at 06:28 PM ----------
maanusav said:
I've seen the words "gold card" few times around forums and some people have got their digitizer to work again and so on. Right now im really confused, why the hell did my lcd just shut down after entering recovery? I've read that theres some king of "Black screen bug" or something like that, I wonder if thats the case?
Is it possible to mess around with that gold card, even if I cant see anything? Because a) LCD is not working at this point b) USB debugging is not on, and I don't think I can even turn it on if LCD and digitizer are not working correctly.
Click to expand...
Click to collapse
yes,2012 wfs have this bug due to change in something in the screen but since you changed your digitizer, maybe the guy that changed your digitizer used one from a new wfs just a wild guess though look at my sig and flash the recovery given there if it works then you have the problem many users have
Sent from my Nexus 7 using xda premium

ngoralph said:
hmmmm does gold card work for gsm?????? i remembered reading that its for cdma only??? not sure though
Sent from my Nexus 7 using xda premium
---------- Post added at 06:33 PM ---------- Previous post was at 06:28 PM ----------
yes,2012 wfs have this bug due to change in something in the screen but since you changed your digitizer, maybe the guy that changed your digitizer used one from a new wfs just a wild guess though look at my sig and flash the recovery given there if it works then you have the problem many users have
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
But that means I have to unlock bootloader? But I probably need to have USB debugging enabled and I have no idea how to do this
if I can't use the phone.

maanusav said:
But that means I have to unlock bootloader? But I probably need to have USB debugging enabled and I have no idea how to do this
if I can't use the phone.
Click to expand...
Click to collapse
I don't know if you have to unlock the bootloader, but using a goldcard may work for clearing up the S58 data (which I think is for the screen and such). Works for both GSM and CDMA (it just doesn't make the phone S-OFF on GSM version).
And no USB debugging needed either, just start the phone into bootloader with the goldcard inserted and follow the instruction (don't remember really what buttons to press tough...)
Oh and btw, clearing S58 may also factory reset you ROM

[Q] Factory Reset with custom recovery

Hey guys, so recently the screen on my flo mysteriously cracked, and the touch screen is broken (does not respond to input, the digitizer is somehow broken). I had an otg cable and a mouse, so I've been able to backup my data through box.com. Now I was wondering if it was safe to wipe the tablet through settings, even though i have a custom recovery (On one of my old devices, this combination would cause a hard brick). I would do it through recovery, but i cant use the touchscreen. Thanks for any response.

Va1ha1a said:
Hey guys, so recently the screen on my flo mysteriously cracked, and the touch screen is broken (does not respond to input, the digitizer is somehow broken). I had an otg cable and a mouse, so I've been able to backup my data through box.com. Now I was wondering if it was safe to wipe the tablet through settings, even though i have a custom recovery (On one of my old devices, this combination would cause a hard brick). I would do it through recovery, but i cant use the touchscreen. Thanks for any response.
Click to expand...
Click to collapse
i would use Wug's Nexus Root Toolkit as you can wipe it completely and lock the bootloader this way its like the first day you bought it just in case they see some modding then can say it voids the return policy.
this way you can remove custom recovery also
me is new to all this maybe theres a better way let the pros answer this
---------- Post added at 03:12 PM ---------- Previous post was at 03:09 PM ----------
oh where did it crack as happened aswell to a friend he returned his last week in the uk

rocksyjj said:
i would use Wug's Nexus Root Toolkit as you can wipe it completely and lock the bootloader this way its like the first day you bought it just in case they see some modding then can say it voids the return policy.
this way you can remove custom recovery also
me is new to all this maybe theres a better way let the pros answer this
---------- Post added at 03:12 PM ---------- Previous post was at 03:09 PM ----------
oh where did it crack as happened aswell to a friend he returned his last week in the uk
Click to expand...
Click to collapse
Thanks, I'll take a look at that. it cracked in the bottom left corner. It isn't even that big a crack, i don't understand why the whole display is dead.
Edit: Unfortunatly, I can't do that because I would need to verify adb from my pc, which I can't because the screen is broken

Va1ha1a said:
Thanks, I'll take a look at that. it cracked in the bottom left corner. It isn't even that big a crack, i don't understand why the whole display is dead.
Edit: Unfortunatly, I can't do that because I would need to verify adb from my pc, which I can't because the screen is broken
Click to expand...
Click to collapse
I haven't tried on this device, but there were ways to "remote control" android devices over the USB cable that I used on past android devices when the screen was cracked.
You basically get a copy of the screen on your PC and use the mouse to control the tablet.
I forget the app but you can search or someone will chime in.
---------- Post added at 08:40 PM ---------- Previous post was at 08:35 PM ----------
Va1ha1a said:
Hey guys, so recently the screen on my flo mysteriously cracked, and the touch screen is broken (does not respond to input, the digitizer is somehow broken). I had an otg cable and a mouse, so I've been able to backup my data through box.com. Now I was wondering if it was safe to wipe the tablet through settings, even though i have a custom recovery (On one of my old devices, this combination would cause a hard brick). I would do it through recovery, but i cant use the touchscreen. Thanks for any response.
Click to expand...
Click to collapse
If you boot into bootloader using the power+voldown combo, you can flash the factory images and after it reboots go back to bootloader and relock.
Doesn't require touchscreen as far as I can remember.

sfhub said:
I haven't tried on this device, but there were ways to "remote control" android devices over the USB cable that I used on past android devices when the screen was cracked.
You basically get a copy of the screen on your PC and use the mouse to control the tablet.
I forget the app but you can search or someone will chime in.
---------- Post added at 08:40 PM ---------- Previous post was at 08:35 PM ----------
If you boot into bootloader using the power+voldown combo, you can flash the factory images and after it reboots go back to bootloader and relock.
Doesn't require touchscreen as far as I can remember.
Click to expand...
Click to collapse
Thanks for that, I've gotten all the data off of it, I just used an otg cable and a mouse. I'll have to download the factory images when I get home.
Sent from my Eee Pad Transformer Prime TF201 using Tapatalk 4

Help Needed!

Today I was in my car sitting in a parking lot, had my phone propped on my steering wheel with the txt app open when the screen when blue then shut down. I tried to power it on but it wouldn't come on, I pulled the battery hit the power button, the LG logo came up for a few seconds then shut off and the only way to turn it on again would be to pull the battery. Holding the power and volume rocker button down will turn it on to recovery. The phone is rooted so when I go to factory reset i've had 2 times it loaded to TWERP recovery but then the blue screen would come up again and I can't do anything. Most of the time it will end up in a green screen with the TC Crash, Demigod crash screen. Plugging it into my computer does load it as a device but I'm not able to access the phones storage. Has anyone ran into this issue and first question, is there anyway to recover data? Second question, is this a hardware related issue? I'm about to try and flash it back to stock since I can't get into TWERP but i'll wait for a response before I do that.

I tried to boot to download mode, I hold the volume up rocker and then plug in a USB, it shows download mode icon for a quick second but the screen goes black. I tried the LG flash tool but it doesn't get past step 1. Any one have any ideas i'm fresh out. Only new thing to report is sometimes instead of the green TZ crash i'm getting an orange RMP crash screen but with the same options as the green screen.

Need to know know a little more before I can reach my decision on where to start.
ROM
Kernel
Thermal mods
Was the phone hot?
Does it get hot upon starting?
Baseband?
I had this happen before but never to the extent that your explaining. Kind of sounds like a kernel panic.

DroidsOnRoids said:
Need to know know a little more before I can reach my decision on where to start.
ROM
Kernel
Thermal mods
Was the phone hot?
Does it get hot upon starting?
Baseband?
I had this happen before but never to the extent that your explaining. Kind of sounds like a kernel panic.
Click to expand...
Click to collapse
I can tell you what ROM it was and thats about it. Resurrection-Remix-LP-v5.5.8-20151027-vs985
Was running sold for months. Phone wasn't hot and didn't notice it getting hot at start up. Phone had 99% battery last time I checked before the blue screen.
I did some research about the LG G3 and blue screen and its a common issue from what i've found. No fix really

http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 u could try this

TheMadScientist420 said:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 u could try this
Click to expand...
Click to collapse
WOW, not sure about that. I'll see. Going to call verizon and see if they can do anything first.

Youll have to pay cause ure waranty is voided being rooted its a sure fire fix for almost all hard bricks and everything its not as bad as it looks i have had to myself on my g2 and g3
---------- Post added at 06:07 PM ---------- Previous post was at 06:02 PM ----------
Do u get the screen press up for dl mode. Try a bat pull and boot into recovery if possible

TheMadScientist420 said:
Youll have to pay cause ure waranty is voided being rooted its a sure fire fix for almost all hard bricks and everything its not as bad as it looks i have had to myself on my g2 and g3
Click to expand...
Click to collapse
Are you sure its a hard brick? From all the things i've read about this blue screen is its a hardware issue. My phone is showing up in the device manager under ports. Can I skip the first part?

Itsna kernal panick some people claim its from over heat others other issues if ure phonenshows up as qusb bulk or something like that then i believe u can the pin groung is to reset it to get it into bulk mode so from there u reflash all the primary gtp partitions then u can get to download mode to restore using stock tot. Ive nevernhad this issue happen but no its not technicly a hard brick but so far i cant find a solution but the method ive shown u usaully brings back all bricks and issues it could be a hardware issue but 9 outa 10 times its a software or firmware issue
---------- Post added at 06:20 PM ---------- Previous post was at 06:15 PM ----------
If u got usbbulk mode on com ports not step 4 but num 4 further down the page is where u start but u have to dl wilcracker and ure stock tot file

TheMadScientist420 said:
Itsna kernal panick some people claim its from over heat others other issues if ure phonenshows up as qusb bulk or something like that then i believe u can the pin groung is to reset it to get it into bulk mode so from there u reflash all the primary gtp partitions then u can get to download mode to restore using stock tot. Ive nevernhad this issue happen but no its not technicly a hard brick but so far i cant find a solution but the method ive shown u usaully brings back all bricks and issues it could be a hardware issue but 9 outa 10 times its a software or firmware issue
---------- Post added at 06:20 PM ---------- Previous post was at 06:15 PM ----------
If u got usbbulk mode on com ports not step 4 but num 4 further down the page is where u start but u have to dl wilcracker and ure stock tot file
Click to expand...
Click to collapse
OK thanks. I mean I guess I don't have anything to loose, so i'll give it a shot.

Like i said i couldnt find a solution im no developer ive just been rooting and modding since the first og moto droid ive bricked and fixed a lot of phones this may not be the proper solution i just no its work for a lot of people on a lot of diffrent bricks on both g2 and g3 i know basicly the g2 is unbri kable and sofar so has the g3 since this i wish it was a general sticky
---------- Post added at 07:07 PM ---------- Previous post was at 07:00 PM ----------
You can try calling lg but i consider there tecks dumber the crap but they get paid for what they do again 9 outa 10 times they cant help other than u sending it in for repair like i said ure rooted if they find out it is its fixed on ure dime i dont know no cell company has ever helped me out.

What do kind of wire do you suggest using?

I used acouple strands of speaker wire coiled up and a pair of tweezers to hold it end bent it to touch both so i still had a free hand

TheMadScientist420 said:
I used acouple strands of speaker wire coiled up and a pair of tweezers to hold it end bent it to touch both so i still had a free hand
Click to expand...
Click to collapse
This is impossible!

joel71 said:
This is impossible!
Click to expand...
Click to collapse
When u plug into ure pc what ports or coms. What xoez the fone shop up az

TheMadScientist420 said:
When u plug into ure pc what ports or coms. What xoez the fone shop up az
Click to expand...
Click to collapse
After trying for what felt like forever I got it kind of work once. It showed up as QCBATCH on port 6. But once I broke connection it went away and I wasn't able to get it to work again. I'll give it another try sometime today..

Sometimes it takes a bunch of trys

TheMadScientist420 said:
Sometimes it takes a bunch of trys
Click to expand...
Click to collapse
Got it working on the first try today. I used the SIM Card bay for a ground so I didn't have to hold it. Much easier, flashing now, will report back after.

joel71 said:
Got it working on the first try today. I used the SIM Card bay for a ground so I didn't have to hold it. Much easier, flashing now, will report back after.
Click to expand...
Click to collapse
Let me no how it goes

I did the steps but it still booted to a RPM CRASH screen, I couldn't get into download mode. I'm trying to flash Cache, System, Userdata, and SB1 now.

Note 10+ N975U wrong Firmware??

phone is SM-N975U
Bought a phone from 3rd party (Technically "used") got it home, did first setup, noticed it was running a bit slow, so while trying to figure out why, i found that the 512gb storage is almost HALF FULL and all I've done so far is log into Google, and install Firefox and Hangouts.... later learned that the storage is slowing growing as the phone is on, and none of the user accessible storage has any files, so my suspicion is that there's an error log being SPAMMED.
So I decided that i'll just wipe it all and install factory stock everything...
So I downloaded Odin 3.13.1, and the latest U1 firmware from Frija (read that U1 is free of bloatware and is interchangeable to this phone)
Edit: also tried Odin 3.13.3-3b to see if it would get any kind of response, but nothing...
Odin won't see the phone no matter what USB drivers i install, reboot PC, uninstall, reboot, different drivers, reboot etc etc.
on the phone:
Having issues getting into "download mode", or any other mode that resembles other people's screenshots!
If I power off, hold volume UP while plugging in USB, I get the screenshot that let's you choose between recovery, Fastboot, or normal.
1. If I choose recovery, I get the "no command" screen shot below and the phone reboots normally from here after about 60 or 90 seconds (maybe less)
2. If I choose "fastboot" (only tried once) the phone says something like "loading Fastboot" or something like that below the choices, BUT IS COMPLETELY LOCKED UP AT THIS SCREEN, it doesn't respond to ANYTHING, not even holding the power button in for 5 MINUTES will force a reboot! The only way to exit this is to let the phone run out of battery (which took all night!)
If I hold volume down and plug in USB from no power, I get something that's ALL in Korean (screenshot), but has a sizeable menu that I can move down through (but not up) and select if I want... I usually just hold the power button to power off again.
So i went back to the system that DOES boot (slowly eats storage space) and looked at the build number again (screenshot) and saw that it looks like it's a N975O build, not U or U1, so i'm thinking that someone tried to flash the wrong one, or was trying to root, etc. i just don't know.
So the question is this: how can i get it back to stock "download mode", stock android (either 9 or 10 i don't care at this point), and just get the phone back to normal?? I'm used to flashing Google Phones where you just flash the bootloader, radio, etc etc. but here i'm assuming that Odin does all of that.
In my Device Manager, under "Portable Devices" it shows as "SM-N975O" when the phone is booted to system, which is the wrong model for the phone (sticker on back says N975U)
Edit2: with phone booted into System, 'ADB devices' shows the serial number as 0123456789ABCDEF same as phone settings (see screenshot)

Looks like you got the Hong Kong firmware.
My SM-N950U Still Rooted Note 8
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Make sure device is powered off. Plug cable into computer, HOLD volume up and down at same time you connect phone to cable, should get you to download.
My SM-N950U Still Rooted Note 8

butchieboy said:
Looks like you got the Hong Kong firmware.
My SM-N950U Still Rooted Note 8
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Make sure device is powered off. Plug cable into computer, HOLD volume up and down at same time you connect phone to cable, should get you to download.
My SM-N950U Still Rooted Note 8
Click to expand...
Click to collapse
When i do that, it still went to the Korean/Chinese menu

After it goes to that screen press volume up then connect to Odin see if it recognizes your device.
Sent from my SM-N960U using Tapatalk

butchieboy said:
After it does press volume up
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
ok first THANK YOU for your help!!
so volume up on the Chinese(?) does nothing, it seems that the power button chooses the current selection, and the top one seems to cause it to do a bunch of hardware checks (still not done actually)

Hmmmm?
Sent from my SM-N975U using Tapatalk
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
Actually that screen looks like Recovery. If its same as US version then bottom should be power off
Sent from my SM-N975U using Tapatalk

butchieboy said:
Hmmmm?
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
i chose the first line on the Chinese menu that i can't read, and it is doing either Diagnostic hardware checks, or it's raw live data from some of the sensors... i don't know
ok so yes, bottom line was either reboot, or power off (went too fast to see)

Try the bottom to power off then try the download mode again
Sent from my SM-N975U using Tapatalk
---------- Post added at 09:11 AM ---------- Previous post was at 09:06 AM ----------
If you can use ADB try these commands:
adb reboot recovery
Or
adb reboot bootloader
Sent from my SM-N975U using Tapatalk

butchieboy said:
Try the bottom to power off then try the download mode again
Sent from my SM-N975U using Tapatalk
---------- Post added at 09:11 AM ---------- Previous post was at 09:06 AM ----------
If you can use ADB try these commands:
adb reboot recovery
Or
adb reboot bootloader
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
ok tried the vol+down and vol+up again, went back to the same menu (also if i JUST use Vol+down it goes to that menu also) will try adb commands after booting system
Edit: previously i've tried adb to recovery, it gave me the "dead android" screenshot above, so this time i tried the ADB reboot bootloader......
we're done testing for tonight because the phone is on the dreaded "=> FASTBOOT mode...." where not even the power button being held for 5 minutes can force the phone to reboot, and it's not responsive at all...... any fastboot commands in CMD are hung at "< waiting for device >"
so now i have to wait until the battery FULLY drains (all night) before i can try anything else.

tomorrow i'm going to take the phone to a "UBREAKIFIX' or whatever it's called that Samsung uses for official repairs, so hopefully they can either flash it proper, or just replace it.

I would have taken it to Samsung straight away, the handset is still very much in warranty so they should sort this out, instead of risking making it worse yourself. It looks like someone screwed this device up pretty good.
I noticed some other weird things from your photos, the phone doesn't look like a Note10+, the screen corner curves are way bigger than on my Note10+ and also it is still on a March 2019 build, I assume that would have been the initial release software.
In the 3rd photo it really looks like the screen is showing through the camera hole, have you tested the front camera? Kinda looks like the device is a fake.
@xeonight Infact looking at fake Note10+ makes me pretty certain this is a fake device, not an actual Note10+. RIP man.
Here is a photo of a fake (right) next to a legit Note10+:

willhemmens said:
I would have taken it to Samsung straight away, the handset is still very much in warranty so they should sort this out, instead of risking making it worse yourself. It looks like someone screwed this device up pretty good.
I noticed some other weird things from your photos, the phone doesn't look like a Note10+, the screen corner curves are way bigger than on my Note10+ and also it is still on a March 2019 build, I assume that would have been the initial release software.
In the 3rd photo it really looks like the screen is showing through the display, have you tested the front camera? Kinda looks like the device is a fake.
@xeonight Infact looking at fake Note10+ makes me pretty certain this is a fake device, not an actual Note10+. RIP man.
Here is a photo of a fake (right) next to a legit Note10+:
Click to expand...
Click to collapse
Thank you for pointing this out to me, my rage is building as this phone was not for me, my dad saved up because his Nexus 6p has been heavily malfunctioning for at least a year now.
Right now it's all I can do not to track down the one who sold this to me, and I fully have the ability (my dad lives out of town, he found it online, asked me to pick it up for when he came to town, he doesn't have much money for this crap... )

Sorry for your loss, I miss my Nexus 6P, great phone just a bit outdated now.

I was curious about the camera also and the rounded screen
Sent from my SM-N975U using Tapatalk

@xeonight you should probably make sure any accounts you signed into on that thing are secure as who knows who wrote that firmware, it wasn't Samsung.

It even looks like the camera placement is wrong. Looks to low
Sent from my SM-N960U using Tapatalk

To be honest, based on your screenshots of the menu and settings, it seems like you got a Note 10+ clone instead of a real Note 10+.
1. Note 10 shouldn't have a firmware that have March 2019 security patch.
2. Bezel to screen ratio is off.
3. Chinese recovery menu should not show up when you try to launch Download Mode.
Edit: oops, it looks like someone point this out earlier. Hope you get compensated for your loss.

As soon as he said something about the foreign language popping up I knew it was possibly a fake. MF got me on a Note 4 that did the exact same thing. If it's a fake I know exactly how he's feeling.
Sent from my SM-N975U using Tapatalk

Well. 2 thing i picked up quickly is "Moly" is Mediatek modem and Recovery style is typically Chinese fake ones. I hope you do get a quick refund

My first thought after reading your post is you got a fake Note 10+. And yes others ppl confirmed. Too bad. For cellphones, when it real cheap, it's something wrong (or at least 5 years old phones)