Related
Howdy Folks.
Here is where i am with my Gtab experience. Reviewed the dummies site a few times...guess i am dumber than dumb when it comes to this stuff.
I have been on stock 1.1 3588 since day one. All i have ever been able to do was load CWM - which ended up not helping becuase now over a year later Viewsonic finally releases an OTA update - which does not work for me since i have CWM.
So i wanted to either get to 1.2 or at least back to stock w/out CWM so i can use the OTA update.
In the process of trying to load/flash something i got stuck on teh birds screen. Unable to boot up or go into CWM. Read the code reads on the dummies site and waited for battery drain. Today i try again and press power while holding + to get into CWM - Still get message: Detect a recovery key pressed Booting recovery image - NOTHING at all so battery drain did not work.
Look obviously a year later and i've got zero use out of this tablet, so it's never gonna happen for me.
If anyone lives in teh south Florida, WPB area and is willing to help - let me know. If someone is willing to help and i can ship this to them - almost as good.
I would like to get ICS loaded on this so i can use it, or stock loaded back so it can be sold. I paid over $300 so hate the idea of the waste but whatver im not techy at all and i guess this is just over me abilities - sucks to admit but i have spent hours.
Let me know. Thanks
Hendge said:
Howdy Folks.
Here is where i am with my Gtab experience. Reviewed the dummies site a few times...guess i am dumber than dumb when it comes to this stuff.
I have been on stock 1.1 3588 since day one. All i have ever been able to do was load CWM - which ended up not helping becuase now over a year later Viewsonic finally releases an OTA update - which does not work for me since i have CWM.
So i wanted to either get to 1.2 or at least back to stock w/out CWM so i can use the OTA update.
In the process of trying to load/flash something i got stuck on teh birds screen. Unable to boot up or go into CWM. Read the code reads on the dummies site and waited for battery drain. Today i try again and press power while holding + to get into CWM - Still get message: Detect a recovery key pressed Booting recovery image - NOTHING at all so battery drain did not work.
Look obviously a year later and i've got zero use out of this tablet, so it's never gonna happen for me.
If anyone lives in teh south Florida, WPB area and is willing to help - let me know. If someone is willing to help and i can ship this to them - almost as good.
I would like to get ICS loaded on this so i can use it, or stock loaded back so it can be sold. I paid over $300 so hate the idea of the waste but whatver im not techy at all and i guess this is just over me abilities - sucks to admit but i have spent hours.
Let me know. Thanks
Click to expand...
Click to collapse
Firstly this should not be too bad of an issue for you. Download this file http://www.mediafire.com/?0rgkcd0k4v30z4u
and connect your tablet in APX mode making sure the APX drivers are installed. Then just run the .bat file and watch the magic happen. It should let you boot back to 1.2 stock without much issue. If this does not work or you need more help just reply back. Someone should be able to help out.
I have found that you can pretty much self tutor through youtube. Search for the earliest gtab links. You can learn everything you need to know with step by step instructions. I knew nothing at first but have updated my gtab with every rom from gingerbread to the current ICS over the months. Give it a try, you be surprise how easy it is to do. All credit goes to the fine devs and experts on this site for making it so.
@Hendge..... I live in Vero Beach..... If all else you try fails and you have nothing else to try and you are out of options then PM me in this forum. I should be able to copy some of my "fixit tools" programs over to my laptop and meet you to work on the problem.
I must emphasize that I agree with the previous posts and irrespective of your level of computer knowledge in the end it will be far better for you to be able to work it out for yourself and thereby help you in the future should a similar occurrence re-occur.
Thanks a bundle for the replies everyone!
It must be a learning block is all i can think of...Same thing happened to me with Algebra!
Anyway, i would like to figure it out:
So in APX mode i should see teh Gtab as a drive/device right? I think i did did before i messed everything up last week - so drivers were installed etc..
Now i do not.
Shoudl i take it apart and hit the reset button like the other thread shows?
Is there another way?
BTW i was on stock 1.1 3588 previously, so if i do get into APX mode and download the mediafire link posted, is that the correct download for someone still on 1.1?
@Hendge..... I don't want to pre-empt any reply or advice by fosser2 who is far more knowledgeable than I am. But as I read your reply it seems to me that you are uncertain as to what exactly "APX" mode is. You get into APX mode from a "powered off" tab by holding down the "Power Button" at the same time holding down the "Volume Down" rocker (as you look at the tab from the front in landscape mode then the "Volume Down" is the LEFT hand side of the rocker).
(1) With tab "off" connect with mini usb to your PC
(2) Perform the above operation i.e. power and volume down depressed, keep both pressed until you see the blank screen mentioned in (4)
(3) You should now get the "splash" screen which if you haven't altered anything will be the 3 birds
(4) After about 2 seconds the screen will go blank and you are now in APX mode
(5) I am taking you at your word that you have already installed the usb drivers on your PC
(6) Now we will accept that you have already downloaded fosser2's zip file and on your PC have unzipped it to a folder (let's call it FOSSER2 or whatever you want)
(7) If you look in that folder at the files you will see a file named something like ... nvflash_gtablet.bat... It might or might not be that exact name but it will be the only file in that folder with a ... .bat extension.
(8) Now with your tab connected and in APX mode, on your PC run the .bat file.
(9) A DOS Type command prompt box will open on your PC and you will see a lot of lines of text telling you what is happening.
(10) When all is finished it will say "Press Enter to continue....."
(11) Press "Enter" and the box will disappear and on your tab screen you should see a line of white text at the top left hand corner.
(12) Turn off your tab by pressing the power button, disconnect from PC and re-boot tab. If all has gone ok it should re-boot.
I have to tell you that not everything I've said above may work out because I've had to guess as to fosser2's intentions.
If you follow what I have said you may well brick your tab ..... I can't accept blame if you do as my only intention is to attempt to help you BUT there is that risk.
Good Luck
metpolds said:
@Hendge..... I don't want to pre-empt any reply or advice by fosser2 who is far more knowledgeable than I am. But as I read your reply it seems to me that you are uncertain as to what exactly "APX" mode is. You get into APX mode from a "powered off" tab by holding down the "Power Button" at the same time holding down the "Volume Down" rocker (as you look at the tab from the front in landscape mode then the "Volume Down" is the LEFT hand side of the rocker).
(1) With tab "off" connect with mini usb to your PC
(2) Perform the above operation i.e. power and volume down depressed
(3) You should now get the "splash" screen which if you haven't altered anything will be the 3 birds
(4) After about 2 seconds the screen will go blank and you are now in APX mode
(5) I am taking you at your word that you have already installed the usb drivers on your PC
(6) Now we will accept that you have already downloaded fosser2's zip file and on your PC have unzipped it to a folder (let's call it FOSSER2 or whatever you want)
(7) If you look in that folder at the files you will see a file named something like ... nvflash_gtablet.bat... It might or might not be that exact name but it will be the only file in that folder with a ... .bat extension.
(8) Now with your tab connected and in APX mode, on your PC run the .bat file.
(9) A DOS Type command prompt box will open on your PC and you will see a lot of lines of text telling you what is happening.
(10) When all is finished it will say "Press Enter to continue....."
(11) Press "Enter" and the box will disappear and on your tab screen you should see a line of white text at the top left hand corner.
(12) Turn off your tab by pressing the power button, disconnect from PC and re-boot tab. If all has gone ok it should re-boot.
I have to tell you that not everything I've said above may work out because I've had to guess as to fosser2's intentions.
If you follow what I have said you may well brick your tab ..... I can't accept blame if you do as my only intention is to attempt to help you BUT there is that risk.
Good Luck
Click to expand...
Click to collapse
Do this and you will be fine
Hi all - my TF700 has been solid for about 9 months, but this past weekend the touchscreen started getting wonky and now it will work for 5-10 seconds and then not register any touches, until the power button is toggled to put it to sleep and then wake up and go through the process again. In my research, it appears as if this can be addressed through recalibration of the Touchscreen.
However, I don't even know if that's possible with my current stock/rooted setup. I did try booting into recovery, but I saw the RCK/Android/Wipe Data prompts, and didn't want to go anywhere without knowing what each would do. I'm guessing maybe the Android button, but I'm not sure.
Is there an easier way to recalibrate the touchscreen without doing a factory reset, or going to a new ROM yet?
Thanks!
This may be a hardware problem with the digitizer going bad. I would contact Asus, they probably will recommend a factory reset and you should try that anyway.
But a custom rom will not take care of this problem - at least I do not think this is software related....
Good that you are still under warranty!
FYI:
RCK will boot into the stock recovery which will not do anything unless you have an update file downloaded somewhere on your storage - it'll just show you an Android falling over with it's belly open a ! triangle. Scary if you don't know what it is! LOL
Android will boot you back into your system. This is a so called 'cold boot' and you could try that. I doubt it'll help, but it won't hurt either.
Wipe Data does exactly what it says. You better have everything you care about backed up before you execute that command.
You use the Volume Down button to navigate between the icons and the Volume Up to execute.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Hmmm. after enabling Developer mode (so I could d a Titanium backup), I decided to enable the touch sensing, and what I've found is that it appears as if there is a spot in the northeast quadrant (while holding vertically, with buttons on the right/dock connector on the left) that gets stuck in the 'touched' sense (the little dot sticks, and in the kindle reader, it acts like the text is selected).
Sometimes it gets unstuck when pressing the power button to sleep, and then re-logging in via the lockscreen code I have set. Sometimes it doesn't. I guess I'll contact support and see if I can capture it on video with my phone.
Pyperkub said:
Hmmm. after enabling Developer mode (so I could d a Titanium backup), I decided to enable the touch sensing, and what I've found is that it appears as if there is a spot in the northeast quadrant (while holding vertically, with buttons on the right/dock connector on the left) that gets stuck in the 'touched' sense (the little dot sticks, and in the kindle reader, it acts like the text is selected).
Sometimes it gets unstuck when pressing the power button to sleep, and then re-logging in via the lockscreen code I have set. Sometimes it doesn't. I guess I'll contact support and see if I can capture it on video with my phone.
Click to expand...
Click to collapse
Pyperkup,
Did you ever resolve this issue? I'm experiencing the Very same issue on my TF700T.
Thanks
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
calvinb1 said:
Pyperkup,
Did you ever resolve this issue? I'm experiencing the Very same issue on my TF700T.
Thanks
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Had to send it in on warranty.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
just wont boot, it won't do anything when i power up my asus transformer tf101 it just get stuck on the first thing you see when you start you asus eeepad and it wont go any further when i power u p and press volume up it just wont go into apx mode so that i can do a easyflash so any suggestion guys plzz??? i really need this it's for my bro.
That's pretty vague. Do you know of it has a custom rom, a custom recovery?
Did you do anything before it reached that state?
xvls said:
just wont boot, it won't do anything when i power up my asus transformer tf101 it just get stuck on the first thing you see when you start you asus eeepad and it wont go any further when i power u p and press volume up it just wont go into apx mode so that i can do a easyflash so any suggestion guys plzz??? i really need this it's for my bro.
Click to expand...
Click to collapse
yea i did everything i could it just wont load up anything i try anything possible but it wouldnt let me in plus i think is not brick it have something to do with the software.
I am having the same symptoms
Model:
TF101 B70 rooted with CWM, custom kernel, and custom ROM.
Symptoms:
Stuck at Eee Pad ASUS logo screen with no progress indicators
Cannot turn tablet off. I can reboot by holding down the power button or let its battery run down.
Cannot boot into APX mode. I have tried holding down Vol+, Vol-, and both buttons before, during, and after power button depressed for reboot. I have tried holding them down for 6, 15, 30, and many seconds.
Cannot boot into recovery
Possible causes:
First had trouble with a bad pre-flash wipe script which took me to where I am now
Troubleshooting steps tried:
Attempts at APX mode and recovery using methods above.
Removed bezel to rule out Vol or power button external switch problems
Stock charger died, so I spliced a 12V 1.5A line into the stock USB cable just in case the TF101 needed something higher voltage to function properly
Bought a new cable
Installed Universal Naked Drivers 0.72 into my Windows 8.1 box
Searched XDA, Transformer forums, and with Google across many other domains with very few hits on this symptom.
I have several computers running and any OS one could want for the USB side of the 40pin cable.
search tags: bricked, can't boot into APX, eeepad logo, eee pad logo, asus logo, tf101, transformer tf101, b70
Just making sure, you guys are aware that the screen stays off in apx right? Have you tried to put it into apx while plugged in to the computer? Plug it in, and then hold volume up and power until the computer recognizes a new device.
jortony, what did you right when this started?
samdudelinxman said:
Just making sure, you guys are aware that the screen stays off in apx right? Have you tried to put it into apx while plugged in to the computer? Plug it in, and then hold volume up and power until the computer recognizes a new device.
jortony, what did you right when this started?
Click to expand...
Click to collapse
I was installing a new ROM which necessitated a wipe. I don't remember the name of the script I used, but I remember selecting the wrong option and rebooting mid wipe to try and prevent the wipe from starting. I wasn't able to recover it then and so I put it on my project shelf until I could get back to it. It's been there for a couple years and I am making one last attempt before I try something drastic like transplanting the flash from a broken TF101 or breaking it down for components... It would be such a waste..
I would love to be able to boot to APX mode, but I just can't get there. If you're near Chicago I'll buy you lunch and you can try your luck. =)
jortony said:
I was installing a new ROM which necessitated a wipe. I don't remember the name of the script I used, but I remember selecting the wrong option and rebooting mid wipe to try and prevent the wipe from starting. I wasn't able to recover it then and so I put it on my project shelf until I could get back to it. It's been there for a couple years and I am making one last attempt before I try something drastic like transplanting the flash from a broken TF101 or breaking it down for components... It would be such a waste..
I would love to be able to boot to APX mode, but I just can't get there. If you're near Chicago I'll buy you lunch and you can try your luck. =)
Click to expand...
Click to collapse
I'd love to take you up on that, but I'm in Alabama at the moment. What was the script supposed to wipe? Just a general prepare-for-new-rom wipe?
samdudelinxman said:
I'd love to take you up on that, but I'm in Alabama at the moment. What was the script supposed to wipe? Just a general prepare-for-new-rom wipe?
Click to expand...
Click to collapse
I'll be in Spanish Fort around Christmas. =)
The script had multiple options, I chose the wrong one in haste..
jortony said:
I'll be in Spanish Fort around Christmas. =)
The script had multiple options, I chose the wrong one in haste..
Click to expand...
Click to collapse
That's odd that it won't go into apx as the result of a wipe script. I was under the impression that apx was so deep in the system that it was pretty much untouchable. I would especially think some wipe script wouldn't be messing with apx. Are you absolutely sure you remember trying just plugging it into a computer and holding down power and vol + continuously? When you do this your computer didn't sense a device?
samdudelinxman said:
That's odd that it won't go into apx as the result of a wipe script. I was under the impression that apx was so deep in the system that it was pretty much untouchable. I would especially think some wipe script wouldn't be messing with apx. Are you absolutely sure you remember trying just plugging it into a computer and holding down power and vol + continuously? When you do this your computer didn't sense a device?
Click to expand...
Click to collapse
That, and also, do you have the APX drivers installed? I don't think UND covers that.
Duchman said:
That, and also, do you have the APX drivers installed? I don't think UND covers that.
Click to expand...
Click to collapse
UND is supposed to cover apx. It did for me, but hey, what do I know. My TF101's essentially bricked right now!
samdudelinxman said:
UND is supposed to cover apx. It did for me, but hey, what do I know. My TF101's essentially bricked right now!
Click to expand...
Click to collapse
Hey, I just want to thank everyone for troubleshooting this with me.
Just to start, isn't it possible to boot into APX mode without any computer attached? If this is the case, then I should be able to reach APX mode with or without the drivers correctly installed and configured. If it does require the computer to be set up properly, I am going to test this on a couple other machines in two days (hosting family Thanksgiving) with all the drivers I can find.
As for the wipe script, I would be surprised if that would be possible too, but if it didn't directly cause the problem it was coincidental and exceedingly likely to be a cause.
Though there are a couple other vectors for my woes: Incorrect power supply (i'm trickle charging on USB) to allow the tf101 to overcome some very low-level programmed switch enabling normal/debug functions; or, incorrect wiring for the my DIY power supply along my troubleshooting escapades which fried something, though I don't see evidence of internal power transformer death within the tf101 which would probably be characterized by periodic reboots, or just plain inky black death.
APX mode works without a PC, it's all on the TF101 (Vol up & power from a powered off state) nothing appears on the TF screen, only sign is the USB connect sound if you have it connected to the PC
UND are specifically for APX mode, but are not signed, so if you are running an OS later than Win 7, or a 64bit OS, you will need to disable driver signing from the F8 safemode boot options (Advanced boot, Win 8.x)
Or use Win 7 32bit
My bad, for some reason I remembered UND not working for me.
I'm guessing you are having trouble with APX mode because you are not able to turn off the tablet completely. Try this: when your tablet is stuck on the logo, press and hold down Volume Up and Power buttons until you see a black screen (release the buttons in 2-3 seconds after that), then connect it to your PC. You should see Asus Transformer APX Interface registered
If the tablet stays on the black screen but nothing is happening on the PC, follow *Detection*'s advice about driver signing.
I successfully disabled driver signing on my Windows 8.1 machine to install UND, but the APX mode is still my sticking point. I tried rebooting with Vol+ before, during, and after the screen turns off and the same with the power button, but that's not getting me into a black screen. I even tried discharging the battery completely to fully shut it down which did something new and interesting: The tablet booted to logo as usual, then the logo quickly disappeared leaving a blank screen but then rebooted again. This might have been the elusive APX mode coupled with an accidental reboot, but I only get to try it once every complete discharge, recharge, and first boot cycle. I am discharging again now to test this again.
Hello,
Yesterday, while my phone was in idle, it turned off and rebooted on the classic red writing on black screen error.
I realize that there are many bootloader exception topics, but I searched and the only one topic I found was on a polish android forum, which I had to translate and that could not help me.
That because the exceptions may be many but I found that error only once.
The error is:
Code:
Bootloader exception
[RST_STAT = 0x1000000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
pc: 0x8f0221b4 lr:0x8f022170 sp:0x8f10fe60
Phone is stuck in that screen until the battery dies.
I tried to get into download mode (to flash a new bootloader) but every combination doesn't work, it just turn off the screen and then after 30 seconds - 1 minute it reappears.
I read online that may be a mobo issue.
Is there any way to recover the phone, put it in download mode or at least recover the data there's inside?
Thanks for the support
Also having same issue
Have you managed to find a solution to this? I am having the same issue, and this is the only thread I can find which matches what my phone is doing.
Same as you, I haven't recently done anything to modify the firmware, I woke up this morning to find the exception text, and when rebooting via the Home + Power + Volume Down combination it jumps me straight to the same exception screen with no boot logo.
Hopefully there's some information around that can resolve this, but unfortunately I currently can't find it
Strongo said:
Have you managed to find a solution to this? I am having the same issue, and this is the only thread I can find which matches what my phone is doing.
Same as you, I haven't recently done anything to modify the firmware, I woke up this morning to find the exception text, and when rebooting via the Home + Power + Volume Down combination it jumps me straight to the same exception screen with no boot logo.
Hopefully there's some information around that can resolve this, but unfortunately I currently can't find it
Click to expand...
Click to collapse
No, unfortunately my phone is still stuck on that exception red text (not a single green one like the one i found online).
I bought a cheap USB Jig, trying to force the phone in the download mode but it doesn't work, my guess is that since the phone doesn't actually turn off, it can't "jump-start" on that mode (with the Jig).
Online I found that people just kept pressing the Vol Down + Power + Home and "eventually" (after 100+ tries) the download mode happens, but I doubt that's in my case.
The only solution I could find that could help me in the future is that 1. Phone is dead, eMMC and motherboard cannot start. 2. Since the phone could be (difficultly) tore down, the best bet is that you find a data recovery center (not Samsung since as I found out they don't do data recovery, but they simply change everything giving you a new phone basically or they change the motherboard, so deleting everything) or a data recovery specialist so that you could disassemble the phone, remove the memory, and read the content on a chip reader.
In this case maybe there's a chance to recover the simple data you have (photo, video, music, documents and something else that has a recognizable header) but probably everything else is lost.
I would be more than happy to be proven wrong since I'm not an expert but it's been 2 weeks and I received no answers.
Iztooi said:
Hello,
Yesterday, while my phone was in idle, it turned off and rebooted on the classic red writing on black screen error.
I realize that there are many bootloader exception topics, but I searched and the only one topic I found was on a polish android forum, which I had to translate and that could not help me.
That because the exceptions may be many but I found that error only once.
The error is:
Code:
Bootloader exception
[RST_STAT = 0x1000000]
Exception: do_handler_sync: DABT_EL1(esr: 0x96000010)
pc: 0x8f0221b4 lr:0x8f022170 sp:0x8f10fe60
Phone is stuck in that screen until the battery dies.
I tried to get into download mode (to flash a new bootloader) but every combination doesn't work, it just turn off the screen and then after 30 seconds - 1 minute it reappears.
I read online that may be a mobo issue.
Is there any way to recover the phone, put it in download mode or at least recover the data there's inside?
Thanks for the support
Click to expand...
Click to collapse
Morning.
The way out of this is to flash either the firmware that is on your phone or just the bootloader file (BL) from that firmware. Both options are done via Odin with your phone in download mode. So just to be clear, Download Mode is availble before the phone looks at the boot partition.
So, hold volumedown+home+power (press and hold the power button last in this sequence).
You may notice that your phone won't go into downlaod first time but it should not take more than 3/4 attempts. Do Not release the buttons until Downlaod Mode appears, no matter how many attempts it takes. Keep them pressed the whole time even when it's powering off and on, this is the part people do wrong.
cooltt said:
Morning.
The way out of this is to flash either the firmware that is on your phone or just the bootloader file (BL) from that firmware. Both options are done via Odin with your phone in download mode. So just to be clear, Download Mode is availble before the phone looks at the boot partition.
Click to expand...
Click to collapse
Hello,
The idea was to flash something on my phone to restore it, but download mode isn't available for me
So, hold volumedown+home+power (press and hold the power button last in this sequence).
You may notice that your phone won't go into downlaod first time but it should not take more than 3/4 attempts. Do Not release the buttons until Downlaod Mode appears, no matter how many attempts it takes.
Click to expand...
Click to collapse
That's it.
But even if I keep the combination pressed the phone doesn't enter in download mode. Usually (and I've seen a good amount of videos) if you keep volume down + home + power pressed, the phone boots up, then goes into the bootloader exception, then it reboots, then it goes into the exception and so on until it gets to download mode. That's not my case. I tried to keep them pressed for 10-15 minutes while it was showing the error and there was no more than one "attempt" (it doesn't restart more than one time per combination).
Keep them pressed the whole time even when it's powering off and on, this is the part people do wrong.
Click to expand...
Click to collapse
The fact is that it doesn't power off and on multiple times, but just one time.
Iztooi said:
Hello,
The idea was to flash something on my phone to restore it, but download mode isn't available for me
That's it.
But even if I keep the combination pressed the phone doesn't enter in download mode. Usually (and I've seen a good amount of videos) if you keep volume down + home + power pressed, the phone boots up, then goes into the bootloader exception, then it reboots, then it goes into the exception and so on until it gets to download mode. That's not my case. I tried to keep them pressed for 10-15 minutes while it was showing the error and there was no more than one "attempt" (it doesn't restart more than one time per combination).
The fact is that it doesn't power off and on multiple times, but just one time.
Click to expand...
Click to collapse
I'm this case you'll need to use ADB and side load to flash a new bootloader.
cooltt said:
I'm this case you'll need to use ADB and side load to flash a new bootloader.
Click to expand...
Click to collapse
But how can I use ADB and sideload if 1. the device doesn't go in recovery mode and 2. it's not even recognized with "adb devices" maybe because of the fact that it doesn't go on recovery mode?
Iztooi said:
But how can I use ADB and sideload if 1. the device doesn't go in recovery mode and 2. it's not even recognized with "adb devices" maybe because of the fact that it doesn't go on recovery mode?
Click to expand...
Click to collapse
Ok forget that one for now.
Try the following.
Boot phone so the error appears.
Then just press and hold the Home button only until the Android robot appears on screen.
Now press volume down+home+power and it should after a few seconds reboot into downlaod mode, if it does just repeat the process from the start.
cooltt said:
Ok forget that one for now.
Try the following.
Boot phone so the error appears.
Then just press and hold the Home button only until the Android robot appears on screen.
Now press volume down+home+power and it should after a few seconds reboot into downlaod mode, if it does just repeat the process from the start.
Click to expand...
Click to collapse
I'm guessing my phone is one of the older version. Pressing repeatedly the Home button or holding it should trigger the "forced upload by key pressing" with the android logo (as i've seen in videos and images), but mine doesn't.
Iztooi said:
I'm guessing my phone is one of the older version. Pressing repeatedly the Home button or holding it should trigger the "forced upload by key pressing" with the android logo (as i've seen in videos and images), but mine doesn't.
Click to expand...
Click to collapse
OK, the only sensible conclusion is that your phone has suffered some sort of hardware failure, its isn't unheard of. It'll likely cost you more to diagnose and repair than to buy a new S7 since their really cheap now.
It may be worth just looking to get your data recovered, which will be cheaper.
I'm not a fan of changing the mother board it's messy and the phone will never look perfect.
What country are you in?
cooltt said:
OK, the only sensible conclusion is that your phone has suffered some sort of hardware failure, its isn't unheard of. It'll likely cost you more to diagnose and repair than to buy a new S7 since their really cheap now.
It may be worth just looking to get your data recovered, which will be cheaper.
I'm not a fan of changing the mother board it's messy and the phone will never look perfect.
What country are you in?
Click to expand...
Click to collapse
Italy.
I honestly don't care about the phone, it has not sentimental value or something. Since I read here, on reddit, youtube and online that there were method like keeping pressed the combination, pressing the home button repeatedly or holding, using a jig, and others maybe someone knew what could I do to restore it. The weird thing was that I wasn't flashing anything nor using the phone, so the hardware failure option may be plausible.
The recovery of data (and I tried when I wrote my last post to re-use adb, maybe i was missing something but the phone is "recognized" by the computer but not with "adb devices") is the only solution I can think of, and there's the chip-off method that could at least recover the major data (photos, videos, documents). If there's anything else I'm all ears.
Iztooi said:
Italy.
I honestly don't care about the phone, it has not sentimental value or something. Since I read here, on reddit, youtube and online that there were method like keeping pressed the combination, pressing the home button repeatedly or holding, using a jig, and others maybe someone knew what could I do to restore it. The weird thing was that I wasn't flashing anything nor using the phone, so the hardware failure option may be plausible.
The recovery of data (and I tried when I wrote my last post to re-use adb, maybe i was missing something but the phone is "recognized" by the computer but not with "adb devices") is the only solution I can think of, and there's the chip-off method that could at least recover the major data (photos, videos, documents). If there's anything else I'm all ears.
Click to expand...
Click to collapse
I assume youre in upload mode. Press only power button for 20 seconds
kpwnApps said:
I assume youre in upload mode. Press only power button for 20 seconds
Click to expand...
Click to collapse
Pressing the power button for even a minute doesn't trigger anything. I assume that you're talking about the upload mode activated by holding the home button or pressing it repeatedly, showing the android logo and having adb recognize the device to then flash something or recover something. That is not my case, it doesn't happen to me unfortunately.
Iztooi said:
Pressing the power button for even a minute doesn't trigger anything. I assume that you're talking about the upload mode activated by holding the home button or pressing it repeatedly, showing the android logo and having adb recognize the device to then flash something or recover something. That is not my case, it doesn't happen to me unfortunately.
Click to expand...
Click to collapse
Buy an usb jig they still work for galaxy s7. It might get you out and they are 3-5$ so you got nothing to lose
Iztooi said:
I bought a cheap USB Jig, trying to force the phone in the download mode but it doesn't work, my guess is that since the phone doesn't actually turn off, it can't "jump-start" on that mode (with the Jig).
Online I found that people just kept pressing the Vol Down + Power + Home and "eventually" (after 100+ tries) the download mode happens, but I doubt that's in my case.
Click to expand...
Click to collapse
kpwnApps said:
Buy an usb jig they still work for galaxy s7. It might get you out and they are 3-5$ so you got nothing to lose
Click to expand...
Click to collapse
I already did that, but sadly it didn't work.
Iztooi said:
I already did that, but sadly it didn't work.
Click to expand...
Click to collapse
Then it might be an UFS hardware fault
kpwnApps said:
Then it might be an UFS hardware fault
Click to expand...
Click to collapse
I have the exact same problem. This is the closest thing I could find on the internet I could find regarding diagnosing it. Had to make an account just to reply. I was thinking it was a OS problem for the longest time, but I suspect that it may be a hardware problem after all. My s7 did this to me the morning of Jan 9. Set it down and came back to it, reboot with bootloader error, red text only, no combinations of buttons work etc. I see that two others in the thread had theirs fail around the same time as well.
Just wanted to update, not sure if anyone is still reading this thread. I plugged my s7 onto my old laptop (windows 7). My laptop recognized it and installed 2 drivers. They are:
"SAMSUNG Mobile USB CDC Composite Device"
"SAMSUNG Mobile USB Modem #2"
I've plugged into this old laptop before and transferred files around, so it doesn't seem to make sense to me why it would install these drivers now. It still doesn't show up in "My computer" at all. I believe normally it shows up in "My computer" as an empty folder when charging although I don't recall 100%. Hopefully this might help with diagnosing this problem.
draco18 said:
Just wanted to update, not sure if anyone is still reading this thread. I plugged my s7 onto my old laptop (windows 7). My laptop recognized it and installed 2 drivers. They are:
"SAMSUNG Mobile USB CDC Composite Device"
"SAMSUNG Mobile USB Modem #2"
I've plugged into this old laptop before and transferred files around, so it doesn't seem to make sense to me why it would install these drivers now. It still doesn't show up in "My computer" at all. I believe normally it shows up in "My computer" as an empty folder when charging although I don't recall 100%. Hopefully this might help with diagnosing this problem.
Click to expand...
Click to collapse
Probably it's because when it's in recovery mode, in download mode or this (bootloader) "error mode" it's recognized differently by the computer, to be recognized by ADB and Odin to flash roms and others. Instead when you plug it in when it's on, it's recognized to transfer data, and I believe when you swap MTP (for normal data transfer) and PTP (using the camera) you should also installing different drivers.
Anyway, I noticed too that the device is recognized differently than usual, and differently when rebooting it with the cable plugged in. (Also the name of the device is different when using the 300k tool, in fact my device is recognized as a "Modem")
Iztooi said:
Probably it's because when it's in recovery mode, in download mode or this (bootloader) "error mode" it's recognized differently by the computer, to be recognized by ADB and Odin to flash roms and others. Instead when you plug it in when it's on, it's recognized to transfer data, and I believe when you swap MTP (for normal data transfer) and PTP (using the camera) you should also installing different drivers.
Anyway, I noticed too that the device is recognized differently than usual, and differently when rebooting it with the cable plugged in. (Also the name of the device is different when using the 300k tool, in fact my device is recognized as a "Modem")
Click to expand...
Click to collapse
I was wondering if you installed any apps recently and how full your internal memory was. I believe my phone was around 90% full of the 32GB, had no warning symbol about how full my memory was though. Friend was saying I should of got a warning if my memory was getting near capacity. I installed F-droid recently and used it to download Adaway app. Deleted F-droid and deleted Adaway since I couldn't get Adaway to work. Never rooted my phone. I was curious if you also did anything similar to what my phone did since we're in the same boat. Otherwise the only things we share in common is we set it down and it reboot with this bootloader error.
So my Note 10+ screen broke so that I can only see the top 15% and only touch the bottom 60%. I booted into TWRP to backup everything, and now I'm in a situation where I can't turn the thing off. I am unable to press the shutdown button, only the download mode and recovery mode buttons. I am also unable to press the ADB side load button to send a shutdown command. It will be quite some time before I am able to fix the screen, so I don't want the phone battery to be sitting dead and degrading for a month or more. I already tried draining the battery and then plugging it in to charge, but the phone automatically booted into TWRP.... hardware key combos only reboot, they won't shut down...
Does anybody have an idea how to power off my device? Or to reboot into system or gain ADB access without being able to use the touchscreen? Thanks for the help
Humm, after reading the "how do we make XDA a better place thread", and the "this place is just not as good as it use to be" thread, I thought I would try to help. But I suppose that if you were on the forum since 2010 you have probably already thought of this. Also, I don't have a "Note 10+", so this is just guessing based on general Android behavior.
My screen is also unresponsive and I was able to reboot/power off by just by holding down the power button for half-a-minute. Sometimes I would have to "pull the battery", as soon as the phone started to reboot. I've done it a few times and haven't bricked the phone yet. So it is not something you do not want to do all the time. But then again this response will probably not be helpful because your phone does not have a removable battery. (whether or not a battery is pull-able is not something generally listed in the phone specks unless you do lots of digging).
TheLexx said:
Humm, after reading the "how do we make XDA a better place thread", and the "this place is just not as good as it use to be" thread, I thought I would try to help. But I suppose that if you were on the forum since 2010 you have probably already thought of this. Also, I don't have a "Note 10+", so this is just guessing based on general Android behavior.
My screen is also unresponsive and I was able to reboot/power off by just by holding down the power button for half-a-minute. Sometimes I would have to "pull the battery", as soon as the phone started to reboot. I've done it a few times and haven't bricked the phone yet. So it is not something you do not want to do all the time. But then again this response will probably not be helpful because your phone does not have a removable battery. (whether or not a battery is pull-able is not something generally listed in the phone specks unless you do lots of digging).
Click to expand...
Click to collapse
Yeah unfortunately battery is sealed inside and holding the power button yields no result
@TheLexx
Take phone to authorized service center and let them fix it.