Related
Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive
Hi! I need help with my tablet.
Device: Samsung Galaxy Tab 2 10.1 Tablet, model GT-P5113 TS. This model doesn't have a way to yank out the battery.
What's wrong: Touchscreen is not responding.
Current state: Attempting to drain the battery. Doesn't appear to be turned on. Factory reset apparently performed.
What happened: Sorry, this is long. It is as best as I can remember it. It may be somewhat inaccurate.
Yesterday evening, I was on my Windows laptop and logged into my Google account. I *thought* I used the Google Play Store to install Chrome to the tablet. (I had looked at the html5test website and it said Chrome had a higher HTML5 rating than the Dolphin/Jetpack browser I've been using on my tablet.)
But something went terribly wrong.
After sending Chrome to it, I unlocked the tablet and used both Chrome and Dolphin to go to html5test website. They both scored the same or nearly the same. I don't know if any of that is relevant, but I'm including it just in case.
At some point after that, I woke the tablet with the power key and used my unlock pattern on the dots lock screen.
That's when I saw what I believe was mal-ware in action. The settings menus were scrolling and sub-menus being selected, all by themselves. I couldn't say exactly what was changed because whatever program or script that was running the process was going extremely fast.
When I realized it might be trying to send out data over my Wifi network, I turned off the Wifi router in my home.
I repeatedly held down the power key to turn the system off, but doing so only rebooted back to the useless lock screen which was not responding to anything. The normal method of holding the power button for a few seconds to bring up the menu and then tapping the "Power Off" option on that menu refused to power off the system. Nothing on that menu responded to touch.
Entering my pattern on the lock screen did absolutely nothing. I didn't even see any lines traced when I ran my finger over the screen.
At some point, I pulled out the external SD card. I have no idea if whatever hacked the tablet also put a copy of itself on the SD card.
I called a friend who looked up how to restore the tablet to factory settings. I didn't understand the directions exactly, so I ended up on a screen with a Warning!! about installing a Custom OS. (Holding down the Power + Volume Up seems to get me there)
I left it on this screen, and I turned my router back on and using my laptop, contacted Live Chat at Samsung but they didn't understand my problem. They told me to reboot the device and swipe my pattern several times and then after several failed attempts I would have the chance to use my Google credentials to get into it. But the device apparently never registered that my swipe attempts were failing.
So my device was booted up with me locked out, with the WiFi router on for a little while again. I turned off the router as soon as I realized that. That disconnected the chat session, but since Samsung chat wasn't helping me anyway, I didn't bother trying to go back.
I got the device back to the "Warning!!" screen. Then turned the router back on and searched for how to do a factory reset of the device. I found a video on YouTube and followed it.
I pressed the Volume Down and Power buttons simultaneously, followed by letting go of the power button. That brought up a menu which contained several options, including an option to do a factory reset. I used the volume buttons to highlight that and pressed Power key. A second screen came up and I used the volume buttons and power button to select "Yes" to confirm the reset.
It appeared to have done a factory reset, rebooting eventually.
However, after that, when I tried to tap on the touch screen to move forward through the selections, the touch screen was still unresponsive!
So I brought back the "Warning!!" screen and ran the battery down until the screen was blank and it wouldn't start when I held the power key.
Then I charged it for about 20 minutes and rebooted it. I think when it came back it was on the Recovery menu. I think I did a second factory reset, but not 100% sure. It eventually rebooted after a lot longer than usual.
When it came up, it was saying battery was low. I tried to tap the OK button, but nothing happened. Behind the battery window was the first setting screen to set up the device for the first time after a factory reset. (I think selecting USA?)
I brought back the "Warning!!" screen and left it on overnight so that the battery would run down.
That was about 8 hours ago. When I woke up, I used clear tape to keep the power button pressed down, to ensure that the battery will continue to run down.
____________________________________________
What do I do next? How do I get the touch screen to start working again? It is not a hardware problem, unless mal-ware can break the hardware. The touchscreen had been working fine until this happened.
Should I take the tablet back to Best Buy where I bought it at least a year (maybe 2 years) ago? I don't know if it's still under warranty.
I have over 20 year of experience as a software developer, but not for Android. I am not very experienced with doing anything to hardware.
Should I try to fix it myself?
I have never rooted any Android device and I'm not sure what that means, either.
I've never re-installed the ______ ? (rom? image? Odin?)
I read on this and/or other forums that there's a way to replace something, but the instructions were beyond my level of understanding. I would need the procedures to be broken down into steps which don't assume too much about what I know.
I understand how to download a file to Windows, given a URL for it. I understand what a zip file is and how to extract it. I understand how to press hardware buttons and plug in cables, and do these steps in the order I'm told.
I don't understand what I'd use to get the downloaded whatever-they-are onto the tablet to replace whatever-the-other-thing-is so that the touchscreen works again.
As far as I know, Odin is a Norse god.
The only firmware updates I've ever done are the ones that the device does on it's own through Samsung's updates.
I'd deeply appreciate getting this device back since I have extremely limited funds and probably won't be able to buy a replacement.
Thank you,
Linda
LMurphy said:
Samsung Galaxy Tab 2 10.1 Hacked, Touchscreen unresponsive
Hi! I need help with my tablet.
Device: Samsung Galaxy Tab 2 10.1 Tablet, model GT-P5113 TS. This model doesn't have a way to yank out the battery.
What's wrong: Touchscreen is not responding.
Current state: Attempting to drain the battery. Doesn't appear to be turned on. Factory reset apparently performed.
What happened: Sorry, this is long. It is as best as I can remember it. It may be somewhat inaccurate.
Yesterday evening, I was on my Windows laptop and logged into my Google account. I *thought* I used the Google Play Store to install Chrome to the tablet. (I had looked at the html5test website and it said Chrome had a higher HTML5 rating than the Dolphin/Jetpack browser I've been using on my tablet.)
But something went terribly wrong.
After sending Chrome to it, I unlocked the tablet and used both Chrome and Dolphin to go to html5test website. They both scored the same or nearly the same. I don't know if any of that is relevant, but I'm including it just in case.
At some point after that, I woke the tablet with the power key and used my unlock pattern on the dots lock screen.
That's when I saw what I believe was mal-ware in action. The settings menus were scrolling and sub-menus being selected, all by themselves. I couldn't say exactly what was changed because whatever program or script that was running the process was going extremely fast.
When I realized it might be trying to send out data over my Wifi network, I turned off the Wifi router in my home.
I repeatedly held down the power key to turn the system off, but doing so only rebooted back to the useless lock screen which was not responding to anything. The normal method of holding the power button for a few seconds to bring up the menu and then tapping the "Power Off" option on that menu refused to power off the system. Nothing on that menu responded to touch.
Entering my pattern on the lock screen did absolutely nothing. I didn't even see any lines traced when I ran my finger over the screen.
At some point, I pulled out the external SD card. I have no idea if whatever hacked the tablet also put a copy of itself on the SD card.
I called a friend who looked up how to restore the tablet to factory settings. I didn't understand the directions exactly, so I ended up on a screen with a Warning!! about installing a Custom OS. (Holding down the Power + Volume Up seems to get me there)
I left it on this screen, and I turned my router back on and using my laptop, contacted Live Chat at Samsung but they didn't understand my problem. They told me to reboot the device and swipe my pattern several times and then after several failed attempts I would have the chance to use my Google credentials to get into it. But the device apparently never registered that my swipe attempts were failing.
So my device was booted up with me locked out, with the WiFi router on for a little while again. I turned off the router as soon as I realized that. That disconnected the chat session, but since Samsung chat wasn't helping me anyway, I didn't bother trying to go back.
I got the device back to the "Warning!!" screen. Then turned the router back on and searched for how to do a factory reset of the device. I found a video on YouTube and followed it.
I pressed the Volume Down and Power buttons simultaneously, followed by letting go of the power button. That brought up a menu which contained several options, including an option to do a factory reset. I used the volume buttons to highlight that and pressed Power key. A second screen came up and I used the volume buttons and power button to select "Yes" to confirm the reset.
It appeared to have done a factory reset, rebooting eventually.
However, after that, when I tried to tap on the touch screen to move forward through the selections, the touch screen was still unresponsive!
So I brought back the "Warning!!" screen and ran the battery down until the screen was blank and it wouldn't start when I held the power key.
Then I charged it for about 20 minutes and rebooted it. I think when it came back it was on the Recovery menu. I think I did a second factory reset, but not 100% sure. It eventually rebooted after a lot longer than usual.
When it came up, it was saying battery was low. I tried to tap the OK button, but nothing happened. Behind the battery window was the first setting screen to set up the device for the first time after a factory reset. (I think selecting USA?)
I brought back the "Warning!!" screen and left it on overnight so that the battery would run down.
That was about 8 hours ago. When I woke up, I used clear tape to keep the power button pressed down, to ensure that the battery will continue to run down.
____________________________________________
What do I do next? How do I get the touch screen to start working again? It is not a hardware problem, unless mal-ware can break the hardware. The touchscreen had been working fine until this happened.
Should I take the tablet back to Best Buy where I bought it at least a year (maybe 2 years) ago? I don't know if it's still under warranty.
I have over 20 year of experience as a software developer, but not for Android. I am not very experienced with doing anything to hardware.
Should I try to fix it myself?
I have never rooted any Android device and I'm not sure what that means, either.
I've never re-installed the ______ ? (rom? image? Odin?)
I read on this and/or other forums that there's a way to replace something, but the instructions were beyond my level of understanding. I would need the procedures to be broken down into steps which don't assume too much about what I know.
I understand how to download a file to Windows, given a URL for it. I understand what a zip file is and how to extract it. I understand how to press hardware buttons and plug in cables, and do these steps in the order I'm told.
I don't understand what I'd use to get the downloaded whatever-they-are onto the tablet to replace whatever-the-other-thing-is so that the touchscreen works again.
As far as I know, Odin is a Norse god.
The only firmware updates I've ever done are the ones that the device does on it's own through Samsung's updates.
I'd deeply appreciate getting this device back since I have extremely limited funds and probably won't be able to buy a replacement.
Thank you,
Linda
Click to expand...
Click to collapse
Definitely sounds like malware. You have two choices that I see, either root and custom rom or flash back to stock. Since you are stock you'd just be overwriting your existing install. Read this thread and decide your course of action http://forum.xda-developers.com/showthread.php?t=2203309
My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Getting the power button fixed isn't too expensive. Hopefully that's all you need. ?
whyareallusernamestaken said:
My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Click to expand...
Click to collapse
I have had this issue for the past 4 days. After many attempts of trying to bang the phone a lil onto my hand (for where the power button is located at), sometimes the phone will boot fine, for as long as you do not click the power button again it won't act up.
(I am pretty sure I didn't drop my phone when I was napping in the car, it just started out of nowhere after I have been using lollipop 5.0 with franco kernel for like 2 months without any problem).
Same sypmtoms, bootloop (looked like the power button defective / boot IC on mobo defective), can't even stay on recovery/bootloader screen/system for longer than 5 sec.
Try these :
- spam click power button, until it is able to boot into system, you will have to keep clicking, for every click you either screen on/off you will realize Power Off options may pop up, it looks like the power button has been holded for few sec to trigger the power off, but all you do was spamming the click to keep the button active, you have to click until you feel that certain point the power off doesn't pop up, then stop clicking ( remember never to touch that power button again for NOW), if after a few sec of using the phone and it doesn't force shut down (result from power button defective where it sense its being clicked and hold for like 8-15 sec). Then you are good to carry on whatever I am to tell here.
- go to about phone, click the build number for 5-10 times until you get the unlocked developer mode
- back, click on developer options, enable usb debugging mode (this will pop another message asking you if you want the device to memorise your pc's mac address) that way it is synced with your pc.
- before you proceed with any other thing, go to playstore, download power button to volume button, enable volume power, check start volume power on bootup, check screen off. This will help you greatly for not touching the power button to unlock the screen when you are working on your pc.
- if you have all the correct nexus usb driver installed onto your pc, you need to get Minimal ADB and Fastboot installed onto pc. After installing, run Minimal adb and fastboot, a command prompt windows will pop out and is automatically redirected to the minimal adb folder. key in this command
"adb devices" to see if it detects your device or not. There should be at least a device listed if you have the usb driver installed correctly
- now you can make use of adb commands to reboot into bootloader/recovery to do any flashing of system, backup all your data that you needed to PC. Download official 5.0.1 nexus 5 image and extract it into the Minimal ADB folder.
- is your bootloader unlocked? if not do adb reboot-bootloader
- fastboot oem unlock (this will wipe all your data on the phone)
- fastboot reboot after the wipe is done
After that you can actually carry on with flashing back to stock images. Look at this link http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for flashing to stock factory image.
I am not sure which step has actually solved my problem, because on my first flashing of factory image, booting into system as a brand new device (no extra softwares, yet to recover any of my data). the problem persists as long as I clicked on power button once, it'll act up again random power off and bootloop.
I actually was on a follow-up cases with google play support team from Aus as my device was bought from Aus. After the last step of factory image setting, doesn't help, I intended to ship it back for RMA as my device is still under warranty and I suspected it was the hardware issues from power button too. They will send me another refurbished device. After ending the call, they sent me link to proceed with warranty claims where I need to fill in several forms and ship the device back to them.
I decided to give it one more try, due to my phone was previously unlocked, rooted, changed to franco kernel.
By restoring to stock images made my device unroot, I was afraid of google will accuse me for unlocking bootloader voided the warranty and not willing to replace another unit for me. I locked back the bootloader, then I remembered in bootloader, fastboot oem device-info shows that a record of a phone if it has been unlocked, it will show Tampered status as True, google probably can use that to track if a device has been unlocked before. So I unlocked my bootloader again (which causing another wipe for whatever data is in the device).
So I looked up on google again and found source for changing that tampered status to False in addition to locking the bootloader again, but to change that tampered status, I need to use TWRP to run the scripted zip file, so I used fastboot boot path (it is stated in the link I gave you above) to boot into TWRP images temporarily from my desktop and ran the zip file, I always practice wiping data, cache and everything before I boot the device back into a brand new factory image.
So I went to wipe dalvik cache. Rebooted the system - it was running the Optimizing x numbers of Applications.
Upon finished with that. I was surprised that, after a few clicks of power button, the random power off issues is no longer there. I even test clicking on the power button for entire day. The symptom isn't coming back. So I emailed google play support team to cancel my warranty ticket and close the case for now.
Should there be any problem again I will probably then claim the warranty for replacement.
Its been more than 24 hours now that I am using the device without any problem of random power off and on or stuck in bootloop due to power button defective.
I suspect it is either the 5.01/5.0 lollipop with ART that is causing something wrong with the boot IC / power button defective in a long run.
Or maybe it was some settings I have changed in franco kernel ? but it was running fine for 2 months which made me doubt that it is franco kernel
Or it could be some of the apps I used to tweak my phone settings - LLama and tactile player (which I have set something condition and actions for power button) but I doubt it is caused by these either.
I will observe and see if the problem comes back after some time of using the 5.0.1 stock image now.
Oh I am also back to using franco kernel, unlocked bootloader and rooted again. Haha...
Hopefully you are able to solve the problem by trying some factory reset method + wiping cache, partition and dalvik.
If not, you probably may have the hardware issues, I have seen some other forum/websites with n5 users upon replacing the mobo, no longer encounter such problem.
Regards,
Kean
Thanks for the replies. My girlfriend was able to get the power button repaired for $80 and replaced the external button for $7 + tax, she paid $98. At least it's cheaper than a new phone.
hi my one vision every time when i unlock or lock restart device. any help?
normee66601 said:
hi my one vision every time when i unlock or lock restart device. any help?
Click to expand...
Click to collapse
I tried to use Action Launcer on my One Vision, it started doing EXACTLY that (restart after unlock).
The only way I could solve it was entering in recovery and wiping it clean. Here's how to do it:
1. Turn it off (hold Power Button for a few seconds)
2. Hold Power Button + Volume Down for some seconds
3. When you enter fastboot mode (with the android robot on screen), release the buttons
4. Use Volume Down to choose Recovery Mode and press Power Button to enter it
5. It will show the Android Robot with "No Command" on screen, when you get on this screen, hold the Power Button and press Volume Up then release the buttons, you will get into Recovery Mode screen
6. At Recovery Mode, choose Wipe data/Factory Reset and confirm when asked.
This worked on mine.
(link to procedure: https://www.hardreset.info/devices/motorola/motorola-one-vision/recovery-mode/)
It will wipe your phone clean. If after that it don't work right, you better get your phone to warranty.
Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision
I was wrong... It tried with other launchers, same problema. I've read that some phones with problem in the fingerprint sensor have this behaivor. As soon as you add fingerprint as the unlock option, It may reboot randomly or when you try to unlock.
I've wiped It again and confirmed this behavior on mine. I'm going after warranty on monday.
tys0n said:
Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision
Click to expand...
Click to collapse
I´ve got the same problem. How did you get it to factory rest?
badadam said:
I´ve got the same problem. How did you get it to factory rest?
Click to expand...
Click to collapse
I made factory reset from recovery.
Sent from motorola one vision.
tys0n said:
I made factory reset from recovery.
Sent from motorola one vision.
Click to expand...
Click to collapse
Thanks, did the same thing. Just had to google my way to finding out how to get into recovery.
tys0n said:
Same thing happened to me after changing default USB behaviour in developer settings.
Once I set it to file transfer, my phone rebooted as soon as I put the USB cable in.
It went to a bootloop a couple of times before it booted up to lock screen, but it rebooted again once I entered my lock pattern.
Only way to solve it was to factory reset
Moto is aware of the problem and working on it afaik.
Hopefully it will be fixed with the next update.
Skickat från min motorola one vision
Click to expand...
Click to collapse
I've made new tests on my Motorola One Vision... That's the problem. As soon as you set the default USB mode to file transfer, my phone starts to reboot even without plugging in the USB cable...
I've wiped it clean, started with the bare minimum, just logged on Google Play Store. I activated the default USB mode to "File Transfer" on the Dev Options.... With no lock option, it works OK. As soon as you set ANY locking method (pin, pattern, fingerprint) it reboots when you try to unlock the phone...
Seems like the only way to solve it is to keep the default USB mode unchaged.
erick.noleto said:
I've made new tests on my Motorola One Vision... That's the problem. As soon as you set the default USB mode to file transfer, my phone starts to reboot even without plugging in the USB cable...
I've wiped it clean, started with the bare minimum, just logged on Google Play Store. I activated the default USB mode to "File Transfer" on the Dev Options.... With no lock option, it works OK. As soon as you set ANY locking method (pin, pattern, fingerprint) it reboots when you try to unlock the phone...
Seems like the only way to solve it is to keep the default USB mode unchaged.
Click to expand...
Click to collapse
Yes. For now we have to change usb mode from the notification panel each time, untill they got it fixed.
https://forums.lenovo.com/t5/motorola-one-vision/Bootloop-when-Developer-options-are-enabled/td-p/4444229
I disable fingerprint, now works perfect
normee66601 said:
I disable fingerprint, now works perfect
Click to expand...
Click to collapse
You disabled only fingerprint? Are you using any other unlock method, or just swipe? Mine got into bootloop even if I add a pattern.
when device restart swipe down status bar press setings then unlock and remove fingerprint
After you have changed the default USB mode to "transfer" on the Developer Options, you cant do that. If you have any sort of lock in place that's different from "swipe to unlock", your phone will reboot on any try to unlock it, even if you try to get to settings (it will ask to unlock, then when you try, it reboots).
If you get into the "bootloop", the only way to get out of it is to enter recovery and wipe the phone. The only way to avoid the bootloop is to a) don't change default USB mode to "transfer" on Developer Option or b) only have "swipe to unlock" as the lock option.
If you set a) and anything different then b), you get stuck in bootloop.
I was sad because I'd need to make a hard reset on my phone after this bootloop but then I tried to start it connected in my PC through USB and then BAM it worked out, boots without restarting, it worked out for me, it should for yours too!
Just wanted to confirm, for all those falling foul of this little bug, that Riverm4n's previous advice does indeed work. And saves the heartache of a full system reset..
Just wanted to clarify the guidance a little..
So with the phone on, and on the lockscreen, plug into your PC.
Let Windows do it's driver install thing of it's the first time it's been plugged in..
Then type in your unlock code on the phone..
Potentially could still go into the reboot again, just leave it plugged into your PC and the next time the phone comes on typing your unlock code in should see it unlock without rebooting!!
Don't forget to disable the developer settings or change the usb thing back!!!
riverm4n said:
I was sad because I'd need to make a hard reset on my phone after this bootloop but then I tried to start it connected in my PC through USB and then BAM it worked out, boots without restarting, it worked out for me, it should for yours too!
Click to expand...
Click to collapse
tonysonyhtc said:
Just wanted to confirm, for all those falling foul of this little bug, that Riverm4n's previous advice does indeed work. And saves the heartache of a full system reset..
Just wanted to clarify the guidance a little..
So with the phone on, and on the lockscreen, plug into your PC.
Let Windows do it's driver install thing of it's the first time it's been plugged in..
Then type in your unlock code on the phone..
Potentially could still go into the reboot again, just leave it plugged into your PC and the next time the phone comes on typing your unlock code in should see it unlock without rebooting!!
Don't forget to disable the developer settings or change the usb thing back!!!
Click to expand...
Click to collapse
Yeah the problem is because is enable fingerprint and default USB configuration was changed.
Just like to thank OP for this - just received a new Vision - & while setting up I had enabled Developer mode mainly due to problem with PC not seeing phone & 1 tip I read was for 'USB Debugging' to be switched on
- while in that menu I decided to force USB file transfer over 'cos of the annoyance having to select it each time I plugged phone in to transfer some pics/doc etc over
Next time I picked up phone it was in boot-loop & I thought it was broken ... PANIC STATIONS !!!!
Factory reset fixed it
- & since being new phone I didn't lose too much of the stuff I had been reinstalling/replacing (which were mainly apps to replace missing 'functions' I had on old phone such as a 'repeat notification/flash camera LED' if unread)
Did lose some game progress on a couple of games I have/had, which is annoying (wish we had a APK Data backup that didn't need root & which isn't Helium since that seems pretty unstable for me atm but then again it's not been updated for a while) but I think I can live with that
Once again thanks
Well, happened to me. I certainly wanted to avoid factory reset. It's a known bug being reviewed by Motorola/Lenovo. Happens when you change the USB connection default action in developer mode and you have any sort of screen lock.
Here is what I did to avoid factory reset, I had fingerprint lock with code.
1. After boot you get to screen lock. I you try to unlock with the code it reboots.
2. In that code enter screen, use a finger not enrolled. You'll see a message that fingerprint was not recognized.
3. Enter now your code and the device won't reset this time.
4. Go to developer options and rollback the USB default action to "no data transfer".
or
1. Factory reset
or
1. Wait for a ROM update
or
1. Return the device to seller and get another one
Avoiding factory reset!
mauro235 said:
Here is what I did to avoid factory reset, I had fingerprint lock with code.
1. After boot you get to screen lock. I you try to unlock with the code it reboots.
2. In that code enter screen, use a finger not enrolled. You'll see a message that fingerprint was not recognized.
3. Enter now your code and the device won't reset this time.
4. Go to developer options and rollback the USB default action to "no data transfer".
Click to expand...
Click to collapse
Thank you for sharing this, it actually allowed me to fix this without wiping everything! I hope they patch this issue soon. I had just finished setting everything up and I thought I would have to start again.
tys0n said:
Yes. For now we have to change usb mode from the notification panel each time, untill they got it fixed.
https://forums.lenovo.com/t5/motorola-one-vision/Bootloop-when-Developer-options-are-enabled/td-p/4444229
Click to expand...
Click to collapse
I've have the same problem on my Motorola One ACTION XT2013-4.
3 days ago I've woken up to my "supernatural" work-out to find out the light on the side of the oculus is RED, which was funky cause it was plugged in all night.
SO, I've looked inside and saw that it's "Updating' I was all happy to get the latest version, but then it just finished, showed the logo blinking as usual and then - NOTHING!
Blank screen, after a couple of seconds - Again started up, Logo, Updating, Logo, Dead. -->> Over and over again and again!!!
I can't connect to it via the phone APP as it keeps restarting and going to update like mentioned, computer doesn't connect as well!
I tried holding down the buttons and factory reset the thing, it goes to Erasing -> Update - > Logo - DEAD! same loop, looks like the "Basic" upgrading is faulty so it can't even factory reset.
Tried to choose 'sideload' option from the "USB update menu" - no good! reboots to loop again.
I can get it to stay stiil if I pop up the 'USB UPDATE MENU' with the buttons and just leave it there, USB Connection to PC shows up 'Oculus ADB Interface' in device manager but I can't get the device to show on "Adb devices" Probaby because it's not on 'developer mode', maybe.
Tried to update drivers and to re'install adb.
PC app shows oculus as connected but I can't do anthying through there...
Contacted support 3 days ago - Nothing! they will look into it... NOTHING! sooooo angry!
EDIT>>
I have managed to pair once from the phone APP but as it "finished' the setup it went straight back into that update boot loop and can't connect again on phone.
Was hoping to manage to get it to developer mode and maybe force an update via adb.
I've been coding for most of my life, playing around with android phones software and such... so i'm not a complete idiot when it comes to these things but this one looks like there is no other choice but just sending it back for repair.
But these guys don't answer or anything... don't even know If I can send it or not, where to etc...
Boot loop:
https://photos.app.goo.gl/zsh8gws7eD8yRR4z6
Tried factory reset:
https://photos.app.goo.gl/h8GC7nurrkQnNsLe6
ANY IDEAS?
come on you guys!!! nothing?!
OK,
Found out I can make the device show in ADB Devices list if I manually load the USB Update menu (volume+power) and then choose sideload option.
However, this won't help much it disconnects from ADB as soon as it finishes loading the logo and restarts the update loop.
I tried to start the sideload as soon as it pops up in the device list, got to 4% serving and then connection was cut off...
If there was a mini update file (couple of KB\MBs) with some settings to make the oculus reset into sideload mode and stop looping i could sideloap a proper version and make it work again maybe.
Please someone help me fix the oculusssss pleaseee!
I same!!!
and oculus support said
"With that in mind, Oculus will not be able to offer warranty replacment/repair for this headset. I can only suggest that you consider purchasing a replacement device from our online store or an authorized retailer. "
fxxxk!!!!!!!!
You're great man. I didn't have such an issue, but I also didn't know the Quest had a menu like this.
Hey @Shlomikalfa - did you ever come back to this and make any progress? With the Quest 2 situation now, and FB logins required, I suspect a LOT more people are going to get interested in this idea.
Just to add, my Quest2 has being working just fine since I got it at launch from Amazon. I was playing beatsaber last night until it ran out of battery and shutdown. I plugged it in to charge and went to bed. This morning, I tried to turn it back on, and it went straight to the USB UPDATE MENU!!
I tried every single option in the USB UPDATE MENU, including factory reset, and it reboots and goes immediately back to the USB UPDATE MENU again. The only option that doesn't take you back to that menu, is POWER OFF! (LOL)
But if I power off, as soon as I power it back on, I got the same menu!
The volume buttons are not stuck at all... since I can use then to navigate the options in the menu.
So I just created a ticket at Oculus support to see what they say!
Good thing is that Amazon.ca gave me until January 31/2021 to return the headset... so if Oculus doesn't sort it out, I'll be returning to amazon for a refund!
Funny thing though. While in this "USB UPDATE MENU", I plugged it in my linux box, and it shows as a fastboot device! I can even run "fastboot reboot" and it indeed does reboot the headset!
I tried "fastboot flashing get_unlock_ability" just to see if it would say 0 or 1... but got an error: "FAILED (remote: 'unknown command')"
Does anyone want me try anything? (as long as the warranty is not voided since I'm waiting support answer! )
Hi all
My missus dropped her old s7+ edge years ago now and while the screen isnt cracked or anything whatever she did it just caught it at the wrong angle or something. The screen kinda works but its all messed up with very faint boot logos and stuff - I cant really see the android recovery comming up so cant select wipe/factory reset for example
Anyway its never been able to boot since. I was going to throw it out as not worth repairing. But Ive just connected to windows and the device is showing up in Device Manager
Just wondering if there was some kind of windows app to wipe the phone or something
Or am I best putting a hammer to it?
Thanks
kiteboy said:
Hi all
My missus dropped her old s7+ edge years ago now and while the screen isnt cracked or anything whatever she did it just caught it at the wrong angle or something. The screen kinda works but its all messed up with very faint boot logos and stuff - I cant really see the android recovery comming up so cant select wipe/factory reset for example
Anyway its never been able to boot since. I was going to throw it out as not worth repairing. But Ive just connected to windows and the device is showing up in Device Manager
Just wondering if there was some kind of windows app to wipe the phone or something
Or am I best putting a hammer to it?
Thanks
Click to expand...
Click to collapse
If USB debugging wasn't enabled in the device's system settings and if you can't unlock the lock screen, you won't be able to use a PC to wipe the device.
If you can find a screenshot of what the stock recovery screen looks like on your specific model number of S7+ edge, you can use the screenshot to see the order of the options in your stock recovery and count how far down the list the factory reset option is. Boot into your stock recovery, you may not see it but it is probably still booting into it, then you can use the volume up/down button to go up or down the list. If factory reset is the second option, in your screenshot, press volume down once to select it then press the power button to initiate the wipe, if factory reset is the 3rd option, press volume down twice then press power, if it is 4th on the list, press volume down three times then press power, and so on. If you find the correct screenshot to guide you and if you use the buttons to correctly select the factory reset option this should wipe your device whether you can see what is going on or not.
Or
If you can boot into download mode, you can flash the newest version of your stock firmware for your specific model number of S7+ Edge, there should be two CSC files in your firmware, when you flash the firmware files, use the CSC file that does not have Home in its name, it will wipe the device when you flash it, if you use the Home CSC, it will not wipe the device.