Related
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.
I was copying a movie onto my H950 when it started to take a long time. I was in a rush so I canceled the file transfer and waited for the computer to finish prompting me about the cancellation. I then unplugged the phone from my computer and noticed that the charging light was still on. I then noticed the phone wouldn't wake up when I pressed the power button. I held the power button and the volume down button to do a hard reset but after the LG start up screen all I got were some random numbers in brackets and "Fastboot mode started" in small text at the upper left hand corner of the screen. The numbers tend to change from time to time.
I have done multiple resets, let the battery die all of the way, recharged all of the way, factory data reset and nothing has changed a thing. When I boot it into download mode it sits there for a minute and by the time the computer sees that it has been plugged in the phone goes back to the black screen with the "Fastboot mode started" text. The computer also only recognizes it as Android Bootloader Interface in the device manager.
It is recognized by the "fastboot devices" command but thats about all I have been able to get out of it. It wouldn't accept flashing a new system image on it either. Please tell me there is still hope. I cant wrap my head around how something so normal could have caused this to happen. It has been rooted for around 6 months and I haven't done anything to the phone sense. I cant even remember what version I was running. I would greatly appreciate any help or advice.
somehow corrupted the laf partition maybe !!
try :
1. fastboot continue
2. fastboot reboot
if it does not work contact LG
i have the same problem with the same variant . tried everything but the kitchen sink .
took it to LG Romania but because its an US device they could not help .
I did search my terms and didn't come up with anything close to my situation, which is this: I got this phone in 2013, rooted it successfully, but was never able to get TWRP flashed properly, but I was happy with the root, so I sort of ignored the TWRP thing. Now I am getting a replacement phone, LG-V20 VS995 next week, so I decided yesterday to tinker around again with TWRP, as I wanted to put this on the V20.
On the G3 when I flashed(Or so I thought) TWRP and rebooted to recovery, I would get an error message (Very small) in the top left of the screen, then would disappear and I would have to pull the battery to reset and then it would boot fine back to the OS, but not to TWRP.
I made sure I had/have the updated Windows LG drivers, ADB, etc.... and I could see my G3 in Windows properly, the internal device and the microSD, I even pulled up the terminal emulator on the G3 while attached to the PC and ran an ID command I think, successfully. I pulled up a CLI in Windows in my ADB directory and my G3 device showed up as well. Then I tried flashing TWRP, first using Flashify; I started with an older version, like 2.8.6, but it didn't seem to work, so I started going towards the newer versions, but still, Flashify kept saying they failed to flash. So I tried the official TWRP app, and it seemed to be doing the same thing. So I went back to review what I had already done, then disconnected my phone from the PC, rebooted normally and tried again with the TWRP app. I think I was successful with one of the newer versions, 3.1.x so I did the reboot after it said it was successful, but I got that boot error message again, then blank screen and red/blue flashing lights; removed battery and replaced, powered on for normal boot and back in the phone OS again. I checked some YT videos on flashing TWRP on VS985 and it appeared I was doing everything correctly, but then I saw this one video that stated to use the Vol+ and Pwr button (I guess I thought when I selected "boot to recovery" the phone was going to do that automatically), then once you see the LG logo, release the Pwr button, then continue to press the Pwr button all while still holding the Vol+ button down, and then you would go into Recovery mode.
His next words sort of came as a shock - you had to select the option to reset your phone to factory defaults, and THEN, and IF you were successful flashing TWRP, it would take you to TWRP. I thought about this and and decided to do another TWRP flash, and if successful, would try this method. I did and I was able to get into the stock recovery menu, and I did see the option to "Reset phone to factory defaults", but decided just to cancel and went back to the phone OS, and that worked. Later on, I decided to try the "Reset" option on another phone boot, but I've now run into a different issue/error. When I boot the phone, I immediately get the error message (The boot certification verify error), and no matter how many times I remove the battery or for how long, each time the phone boots, I get this error message. The only thing I have been able to do is get into the Hardware Key Control Mode using Vol+Vol-Pwr and just continuing to press them. No matter what option I choose, either Cancel, Mode On, or Mode Off, the phone immediately reboots to the error message; it's like it's stuck in the Recovery boot mode somehow. I'm not sweating it too badly, as I've got a V20 coming next week and I have a work cell I can use for important things, but has anyone run into this type of thing? The way it is now, I cannot view the phone on my PC and cannot seem to get past this boot certification verify error.
EDIT: I am now able to consistently boot into the System Recovery by way of Vol+Pwr button held down until the SR menu shows. HOWEVER, no matter what choice I select, phone reboots and I get the "Boot certification verify" error................ oh well, at least I got an email that my V20 is coming this Thursday.
EDIT: I must be somewhat dyslexic, as the method to get to the SR menu is VOL- (Not Vol+) and Pwr button held down until SR menu entry. Sorry about that
EDIT: I've also seen the "fix" where you remove the back cover, battery, and then remove the top plastic cover over the battery/power/volume, then also remove the metal shield. This is the point where it gets confusing; the author(s) want you to "ground" 2 of the contacts, but it's not clear which ones they are referring to, even with the screenshot, and I'm not electrical engineer, so not exactly sure what they mean by grounding. As I'm getting a replacement tomorrow, I decided not to even explore this technique, although I did dissassemble the phone down to removing the metal plate, so I could try and see if I could figure out what they were talking about (I couldn't). Gotta say, I've had my G3 for over 7 years and for the most part, really loved it; it came in handy during home power outages when the Internet (Cable) went out.
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.
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! )