Database Info

Need assistance/info with bricked shield tablet

Received a shield tablet through a promotion my company was doing with nvidia, decided to try it out. (pointing this out ahead of time to let the 'just return it' people know that I cant and am stuck with it.) upon finally deciding to boot it up a couple months later, it booted into the bootloader menu instead of booting like normal. then when choosing to boot would boot into a very stripped version of android with few apps, tegra services repeatadly crashing, no app store/play/etc . I wanted to have the proper out of the box experience nvidia intended, so decided to hunt down a stock factory image to flash to it to just resolve the issue and start from scratch with my new tablet. was able to flash recovery/boot/system/userdata/etc via fastboot. upon restarting, screen went black and wouldnt start. plugged in to computer, device manager says "APX" and that's it. with unknown device/driver icon. if I power it off all the way and plug it back in it just goes back to saying "APX" with a "?" in device manager.
how can I get it out of this mode and booting so I can finally try this thing out? have tried diff combos including bootloader/recovery mode button presses at boot time and nothing works, goes back to the same thing. I've also seen mention about nvflash and some other things when looking into this, but nothing solid on where I get the program, how im supposed to use it to fix my device.
Thanks

Can't find my OPO on ADB, also reboot loop on lock screen, help please?

Hey guys, I'm having a problem on my OPO after updating to Android 6.x.x (don't know the exact version, just the newest available update). I've been using 4.4.4. for a long time because of the superior battery life, but I was forced to update because my google play services started to crash every ten seconds. Anyway, after a couple days of going crazy with the insane battery drain (the phone was very hot during screen on, unlike in 4.4.4). I thought something was using power, so I went crazy with the privacy settings and privacy locked Google Play Services and a couple other apps, it asked me if it could access my contacts or something , I selected no and never ask again. The phone immediately stopped producing heat at the back and I browsed internet a couple minutes and thought everything was finally great. After this I turned the screen off. When I turned the screen on, it let me enter my lock pattern, but straight after that when it's supposed to open my home screen, it freezes and reboots after 5 to 10 seconds. The reboot loop is endless from this point forward, now it even crashes straight after I enter my SIM PIN code and goes into a reboot loop.
I had updated to 5.x.x before when it first came out, but had the same insane battery drain problem there so I went back to 4.4.4. So I have TWRP installed (I used it the last time when I went back to 4.4.4 from 5.x.x, so it should be there still?). I can access fastboot (volume up + power) and cyanogen recovery (volume down + power). I tried following this guide http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/ , but when I run the command 'adb devices' , while my OPO is connected via USB in either fastboot or recovery, my PC won't recognize my phone (OPO doesn't show up either in device manager) and just gives me 'error: no devices found'. What should I do? I haven't tried factory reset in the the Cyanogen recovery, because I read somewhere that it probably wouldn't help and I'd lose all my data. However I'm willing to try this if there are no other options. Thanks for any input you guys might have. I can also post a video if needed to troubleshoot and demonstrate the problem.

mazzuli said:
Hey guys, I'm having a problem on my OPO after updating to Android 6.x.x (don't know the exact version, just the newest available update). I've been using 4.4.4. for a long time because of the superior battery life, but I was forced to update because my google play services started to crash every ten seconds. Anyway, after a couple days of going crazy with the insane battery drain (the phone was very hot during screen on, unlike in 4.4.4). I thought something was using power, so I went crazy with the privacy settings and privacy locked Google Play Services and a couple other apps, it asked me if it could access my contacts or something , I selected no and never ask again. The phone immediately stopped producing heat at the back and I browsed internet a couple minutes and thought everything was finally great. After this I turned the screen off. When I turned the screen on, it let me enter my lock pattern, but straight after that when it's supposed to open my home screen, it freezes and reboots after 5 to 10 seconds. The reboot loop is endless from this point forward, now it even crashes straight after I enter my SIM PIN code and goes into a reboot loop.
I had updated to 5.x.x before when it first came out, but had the same insane battery drain problem there so I went back to 4.4.4. So I have TWRP installed (I used it the last time when I went back to 4.4.4 from 5.x.x, so it should be there still?). I can access fastboot (volume up + power) and cyanogen recovery (volume down + power). I tried following this guide http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/ , but when I run the command 'adb devices' , while my OPO is connected via USB in either fastboot or recovery, my PC won't recognize my phone (OPO doesn't show up either in device manager) and just gives me 'error: no devices found'. What should I do? I haven't tried factory reset in the the Cyanogen recovery, because I read somewhere that it probably wouldn't help and I'd lose all my data. However I'm willing to try this if there are no other options. Thanks for any input you guys might have. I can also post a video if needed to troubleshoot and demonstrate the problem.
Click to expand...
Click to collapse
Did you wipe your data partition when you updated frowm 4.4 to 6.0? Its most likely that all the apps are crashing due to incompatible data files.
I've once had the same problem and i managed to fix it with deleting data for every crashing app, so this might be an option.
Otherwise you might fix your phone by factory reseting from recovery.

Please Help! Stuck at boot screen...

Hello. Sorry in advance if this is the wrong thread. I own a pretty old 1 year old tablet that currently has a problem.
Important info: Android 5, No access to a computer for 2 weeks (vacation), slightly cracked screen (still works), I had to install a Play Store apk as the one I had previously was corrupt. Tablet was functioning fine until the moment of the incident (except for the play store apk, which I later fixed).
Minor detail: Once the screen turns on after a restart the pixels near the top of the screen seem to turn purple for a second when I tilt the tablet.
Here is the story:
I was watching a YouTube video and suddenly my tablet froze. I thought: "Uhh, another freeze how annoying," and waited for it to load. I did not unfreeze. I thought: "Well, I guess I'll be fine if I turn my tablet off and on. This is where I got worried. My Power key was not responding. I tried the volume keys. Nothing. I tried connecting a mouse and moving it around. Still nothing. I thought "Ok, lets try restarting it" I did that by holding the Power key down for 10 seconds. To my relief, it turned off. But when it was turning back on again, it was at the loading screen for a little to long. It usually takes 5 seconds to get past the loading screen and enter the boot screen. I decided to wait. 1 minute: nothing. 5 minutes: nothing. I got worried. I tried restarting the tablet again. I restarted successfully but was stuck at the loading screen again. The was no movement on the screen. Only the loading screen. I decided to try the restart backup button which I could activate by putting a pin in a small hole at the back. It had the same effect holding down the power key had. I decided to ue my backup plan: recovery mode. I successfully entered recovery mode. I chose the option "clear cache" and tried to boot again. No changes. I did a scan for any root errors. it said that there were 5 errors, but there was nothing I could do about that. I tried doing a factory reset, then booting up. The reset was successful, but I got the same effect as always. No changes. I gave up and tried to google a solution on my phone. Most of them told me to install a PC program, but one told me to do the same thing I already did: reset, restart. So I decided to let the tablet sit with the boot screen for 2 hours. When I came back, there was no change at all. I tried searching again for a solution. A YouTube video said that the boot time after factory resets may be long, so I decided to reset and let it sit for a bit. 20 mins later, no changes at all. Finally, I gave up and now try to ask for help here.

Norqw said:
Hello. Sorry in advance if this is the wrong thread. I own a pretty old 1 year old tablet that currently has a problem.
Important info: Android 5, No access to a computer for 2 weeks (vacation), slightly cracked screen (still works), I had to install a Play Store apk as the one I had previously was corrupt. Tablet was functioning fine until the moment of the incident (except for the play store apk, which I later fixed).
Minor detail: Once the screen turns on after a restart the pixels near the top of the screen seem to turn purple for a second when I tilt the tablet.
Here is the story:
I was watching a YouTube video and suddenly my tablet froze. I thought: "Uhh, another freeze how annoying," and waited for it to load. I did not unfreeze. I thought: "Well, I guess I'll be fine if I turn my tablet off and on. This is where I got worried. My Power key was not responding. I tried the volume keys. Nothing. I tried connecting a mouse and moving it around. Still nothing. I thought "Ok, lets try restarting it" I did that by holding the Power key down for 10 seconds. To my relief, it turned off. But when it was turning back on again, it was at the loading screen for a little to long. It usually takes 5 seconds to get past the loading screen and enter the boot screen. I decided to wait. 1 minute: nothing. 5 minutes: nothing. I got worried. I tried restarting the tablet again. I restarted successfully but was stuck at the loading screen again. The was no movement on the screen. Only the loading screen. I decided to try the restart backup button which I could activate by putting a pin in a small hole at the back. It had the same effect holding down the power key had. I decided to ue my backup plan: recovery mode. I successfully entered recovery mode. I chose the option "clear cache" and tried to boot again. No changes. I did a scan for any root errors. it said that there were 5 errors, but there was nothing I could do about that. I tried doing a factory reset, then booting up. The reset was successful, but I got the same effect as always. No changes. I gave up and tried to google a solution on my phone. Most of them told me to install a PC program, but one told me to do the same thing I already did: reset, restart. So I decided to let the tablet sit with the boot screen for 2 hours. When I came back, there was no change at all. I tried searching again for a solution. A YouTube video said that the boot time after factory resets may be long, so I decided to reset and let it sit for a bit. 20 mins later, no changes at all. Finally, I gave up and now try to ask for help here.
Click to expand...
Click to collapse
Was your device rooted? Did you have TWRP custom recovery installed? If you don't have either of these two things then your only option is to flash the stock firmware via PC.
Do a google for:
"Return to stock (your model number)"
If what you need is out there somewhere, that woll find the instructions, the tools and the file(s) you need.
Sent from my LGL84VL using Tapatalk

LG-G3 VS985 boot certification verify error (Boot loop)

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.

Force install OS on Oculus Quest 2 without developer mode

Hello,
I've a set of Oculus Quest 2 with an unusual issue.
The headset turns on, I can see the Oculus logo and I can hear the greeting sound but after this nothing happens.
when I try to change the volume I can see the volume goes up or down
and when I press the oculus button for few sec I can see on the screen the animation but nothing after this.
I tried to factory reset, and shut off and then turns on I see the logo for longer than normal hear the greeting sound and than nothing like before.
I wanted to side load the OS using ADB and FASTBOOT as I fear it got corrupted or something.
in order to do that I need to turn on developer mode
and in order to do that I have to connect to the oculus app
and in order to do that I need to be able to use the headset to complete the connection process.
and my headset doesn't show anything on screen
additionally I tried using the Oculus developer hub, but eventually i get to the same issue i have with the mobile app ....
Now because I'm not in an oculus supported country I can't RMA it.
I'd be happy to get any help.
Thanks a lot
Ofiros

he how can i force install os i have enabled devloper mode
so i have same issue like you but after couple of try i was able to boot but i got many bug and auto restart , unable to play games i tried factory restart but same thing whithin hours
can you explain me how can i install os by fastboot or adb i only found update file which not full os