Yesterday, after installing the 2.2 update (maybe related?) I plugged it in to charge and couldn't get it to wake up after charging for some time. When it eventually did come up, it came up to the boot loader screen (small text with a list of options) choosing Continue or Recovery from the list gives me small text that disappears quickly that reads "boot failed" (along with other things I couldn't read).
Fastboot seems to be working, but any command to reflash partitions is met by a notice that it failed because my boot loader is locked, and if I try to fastboot OEM unlock, it prompts me on the tablet, I choose yes, and it promptly fails (fastboot returns unknown error). Perhaps the emmc is toast or is it still recoverable via APX or something like that? I couldn't find anyone who had used APX on the shield tablet.
This morning the battery appears to be dead (I let it discharge overnight, hoping that doing so would clear some state and get things working again) and when I plug it in to charge the display does power on (backlight lit with black screen) but I don't see the charging animation come up.
I spent hours searching into the night last night and couldn't find someone who couldn't even unlock the tablet. I'd really like to fix it myself and not have to RMA because I wanted to use the tablet to play Ingress at an event this weekend. It's the LTE model and I bought it for playing Ingress.
Any ideas for how to bring this tablet back?
Related
Hello,
I’ve got a One S (S4 version) that’s driving me crazy. Can you help me please?
I bought this phone second hand – hoping that I could fix it up and give it to my mum for her birthday. It looks immaculate, but it was sold because the previous owner couldn’t get it out of a boot loop.
When I received the phone, the first thing I did was to hook it up to the charger. As soon as the charger was connected, the charging LED came on, but then after about 5 seconds (without pressing the power button), the device turned its self on and begin rebooting at the “Quietly Brilliant” screen. It wasn’t the usual “Quietly Brilliant” screen though… There was a progress bar in the top right hand corner, indicating that it was trying to flash something. The progress bar went from 0-100% twice, then after a pause of about 20 seconds – it rebooted again. This process would repeat endlessly
After a lot of messing around, I managed to get into the bootloader. The status was “Tampered – Relocked”. At this point, I downloaded and flash the latest RUU (2.31). However, even though the RUU flashed successfully, it still boot loops. The only difference is that the “Quietly Brilliant” screen no longer has the progress bar in the top right corner (it’s just the normal boot screen now).
After this, I unlocked the bootloader via HTCDev and flashed CWM recovery. The flash was successful , but trying to access recovery also fails. It just sits on a screen with the “for development purposes only” warning for a few seconds, then reboots and follows the same boot loop sequence as before.
Does anyone know whether I’m wasting my time on the phone? At this point I’m very worried about flashing things, because I never know how much juice is left in the battery. If I hook up the charger, the charging LED does come on, but only for a matter of seconds. After 5-10 seconds, the charge LED goes out and the device automatically fires up into a boot loop. It’s impossible to power down the device when it’s connected to the charger. It will turn its self back on again! The best I can do is to leave the phone sat in the bootloader, but there is no indication that it’s charging (no LED).
:crying:
I've just read over my last message and I think the clue is in the way this thing turns on by its self when connected to power. I bet some water has got into the phone and caused a mess inside. I think it might be time to get the screwdrivers out.
Come across a strange problem on my TF300. The battery completely drained one night and thereafter it's become unresponsive. It charges, boots to the lock screen, but the battery is shown at 0% and I'm unable to interact with anything other than using the hardware keys. It freezes when attempting a cold boot or attempting to go to recovery. Had TWRP 2.8 on Katkiss 4.4, anyone got any ideas?
Just to update this, the dock just doesn't work with the tablet currently.. Despite being on charge for a number of hours there's been no progress. Both charging lights do go green eventually though, but still on 0%. It connects to my PC, and I can even view the files on it, but the tablet itself is unusable. Device manager shows it but I couldn't get it to appear in Adb for fastboot commands
Anyone know how to get it to show in Adb?
Bump on this since I'm out of ideas and would appreciate any help
Fixed this now, thanks to those who had a look. Somewhat simple solution, connected a mouse via USB, which allowed me to navigate the tablet. After that it was just a simple selection of rebooting to recovery from the power menu, which got me into TWRP and let me do a wipe and flash a new ROM.
Sent from my TF300T using XDA Free mobile app
I have read several threads on similar problems but none that are the same as mine.
I bought my shield tablet (16gb wifi) off Amazon so I can't really tell you much about it's exact specs. All I know is that I was told that only early manufacturer runs had rooting and OTG issues, and that newer runs had OTG out of the box.
Mine doesn't have OTG enabled, and it would not root with most of the common self installing root apps. So I believe it is an older version.
I have been installing all Nvidia updates as the update notification comes up on my tablet except for the latest one released a couple days ago. (waiting for WiFi to down load)
I was running marvel future fight at the time my tablet did a forced shutdown for a low battery.
Later I plugged it in to charge for a few minutes. When I first plugged it in I got the normal warning image of an empty battery telling me I could not boot yet.
I waited several minutes and tried to boot, but the boot process took an extensive amount of time.
But the real issue is that now I have read several threads on similar problems but none that are the same as mine.
I bought my shield tablet (16gb wifi) off Amazon so I can't really tell you much about it's exact specs. All I know is that I was told that only early manufacturer runs had rooting and OTG issues, and that newer runs had OTG out of the box.
Mine doesn't have OTG enabled, and it would not root with most of the common self installing root apps. So I believe it is an older version.
I have been installing all Nvidia updates as the update notification comes up on my tablet except for the latest one released a couple days ago. (waiting for WiFi to down load)
I was running marvel future fight at the time my tablet did a forced shutdown for a dead battery.
Later I plugged it in to charge for a few minutes. When I first plugged it in I got the normal warning image of an empty battery telling me I could not boot yet.
I waited several minutes and tried to boot, but the boot process took an extensive amount of time.
But the real issue is that now, every time I boot it up, once the Nvidia logo disappears instantly before the lock screen or anything else can come up, the notification that one of two processes have stopped comes up. Those being System UI, and Cellular Data.
This would normally be no problem but the instant I click OK the same warning pops back up. It is just stuck in the same loop, process stops, I hit OK and repeat for as long as my patients lasts and I try rebooting...
(why a 16gb WiFi only model even needs the cellular data process is beyond me or why it would prevent a complete boot... )
Any way I started research and found the power + volume down bootloader option.
It took me several tries to figure out how to even get the timing right for that to work. But once there it was no help.
First option for Factbook gave this result :
Cold booting Linux
Then the Nvidia logo, and the same system UI has stopped warningtI have read several threads on similar problems but none that are the same as mine.
I bought my shield tablet (16gb wifi) off Amazon so I can't really tell you much about it's exact specs. All I know is that I was told that only early manufacturer runs had rooting and OTG issues, and that newer runs had OTG out of the box.
Mine doesn't have OTG enabled, and it would not root with most of the common self installing root apps. So I believe it is an older version.
I have been installing all Nvidia updates as the update notification comes up on my tablet except for the latest one released a couple days ago. (waiting for WiFi to down load)
I was running marvel future fight at the time my tablet did a forced shutdown for a dead battery.
Later I plugged it in to charge for a few minutes. When I first plugged it in I got the normal warning image of an empty battery telling me I could not boot yet.
I waited several minutes and tried to boot, but the boot process took an extensive amount of time.
But the real issue is that now every time I boot it up.
Once the Nvidia logo disappears instantly before the lock screen or anything else can come up, the notification that one of two processes have stopped comes up. Those being System UI, and Cellular Data.
(why a 16gb WiFi only model even needs that process is beyond me or why it would prevent a complete boot... )
Any way I started research and found the power + volume down bootloader option.
It took me several tries to figure out how to even get the timing right for that to work. But once there it was no help.
First option for Fastboot
It says cold booting Linux the displays the Nvidia logo, but up comes the same warning of one of those stopped processes that will pop up as fast as I can click OK, for as long as I will click ok...
I tried the recovery option and that gave me the error of no command with the dead android with the warning sign popping out of his insides.
Just hit the reboot option and as of right now it did not boot... Will try holding down the power for manual reboot. As it will not power on normally now.
Manual reboot to the options again and going to try the power off option.
I am thinking that I might be able to fix this by flashing from a pic... But I wouldn't know as I have never gotten into that stuff before.
Cellular data stopped is still coming up on boot attempt... Only other option I know to try is open the menu back up and try the recovery again or maybe on the of chance hitting continue might do something different that changes things up and let's it finish booting.
I assume it is not actually completing the boot cycle as I cannot bring up the soft keys nor does the lock screen come up.
(don't get me started on the evils of soft keys. )
Anyway any help anyone can give would be great!
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
bigblkyj said:
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
Click to expand...
Click to collapse
If what you've described is correct, all of the solutions involve flashing the stock firmware which will of course wipe the device.
Were your photos not stored in a folder on the SD card?
There is a chance you can recover the device using Samsung Kies with the emergency recover option but if you've encountered the "no command" screen it's not looking good.
Unfortunately I did have an SD card installed, but I normally kept my camera pics on the phone's memory, since I have had an SD card fail as well and lost everything on there.
So this took an unexpected turn yesterday pretty much right after posting this... I've been messing with the phone, unplugging the battery each time, and have managed to get into different menus which kept making me think that something still had to be working if I could do that. Well, after leaving the No Command message on the screen it magically booted into the Recovery menu with (finally) the option to wipe the cache partition, which I did and rebooted normally. Believe it or not, it booted normally and into the OS like nothing ever happened?!
I instantly plugged it into my PC and ran Smart Switch which started taking a backup! About 25% though the device restarted again and was really warm to the touch on the RF covers inside. Bummer...
So I figured heat was now the issue for some reason... I waited for it to cool and then reinstalled the SD card and figured, if I could get it to boot long enough, the SD card is a quicker transfer and I'd just use ES File Explorer to try and do a photo dump to the SD card and see how far it would get. It actually made it all the way through and gave me enough time to grab some other stuff before getting hot and restarting again.
I believe the overheating is being caused by my opening of the device though... Currently I have the antennas removed and the speaker so that I'm able to quickly access the battery connector (which BTW seems to be the trick here to this working) But inadvertently, without the larger wireless charging coil in place, it relieved the pressure on the motherboard and broke the thermal paste connection between the chipset and the copper heatsink (I didn't tear it down further to check, but I can hear the 'sticking and peeling' when you press down on it).
I think what I'm going to do is apply pressure with a chip clip or something similar (non conductive) and see if I can grab a backup again before it restarts. After the cache wipe the phone seems to understand that it's plugged in and charging now which is a new thing as well...
Sorry for the long winded posts, but if this at all helps even one person with the same situation as I have, maybe that'll be worth getting lost in here
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! )