My phone is putting up a fight not wanting to be unlocked.
In order to even get Mi Unlock to work at all I had to.
A) Disable Windows driver updates automatically downloading
B) Rename Mi Unlocks driver folder so it does not try to install drivers that prevent fastboot from working
C) Manually tell it to install the Android Bootloader Drivers in device manager
That took me the entire afternoon to even figure out where it was going wrong and why. Apparently Windows (10) version of the driver does not work as after doing a lot of uninstalling and reinstalling I noticed that very briefly after a boot fastboot devices listed a device but when I ran it a second time right after that it listed ??????? and the third time it didn't list anything.
Telling windows not to mess with drivers I still couldn't do anything in Mi Unlock and checking fastboot devices it come up blank every time after running Mi Unlock. I ended up renaming the driver folder of Mi Unlock so it too stopped messing with drivers, this finally allowed me to run Mi Unlock but now it's getting stuck at 50% of "Verifying device".
What is up with that? Is it because my account is still in the waiting period of being approved for unlocking by Xiaomi? I had to delete my old account and make a new one as the text wasn't coming in, I signed out of the old account on the phone properly/signed into the new one and have USB debugging etc enabled.
https://imgur.com/y7fpCh5
I could really use some help with this
Having read somewhere at some point that the Mi Unlock tool plays nicer on Intel systems than AMD I figured I'd give that a try and I had better luck there.
I am locked out for another 2 weeks it seems.
I don't know if this is literally an AMD vs Intel thing as it sounds extremely unlikely to me that is the cause. Worth a shot though if anyone else is running into the same problem and it doesn't need to be a recent system as my laptop has a 3rd Gen i5 CPU (we're on the 13th Gen now)
Axeia said:
Having read somewhere at some point that the Mi Unlock tool plays nicer on Intel systems than AMD I figured I'd give that a try and I had better luck there.
Click to expand...
Click to collapse
I ran into this problem and came to that point and bought a mini PC with an Intel CPU.
I did the same work on the new PC and everything worked fine!
I really don't know if the AMD CPU is the cause, but it is one of the success samples.
I do wonder if it's just because it's Intel or just because it's a different system.
I don't have enough systems around to figure it out.
The ancient laptop did fully complete the unlock (my wait time is up ) so that's great, I am running Pixel Experience Plus now. Although likely not for long as the 'recent apps' view in it is terrible and cannot be customized - on to SparkOS.
Related
http://www.mobiletechworld.com/2011/01/25/enable-tethering-on-htc-windows-phone-7-devices/
Trying this now.
eduncan911 said:
http://www.mobiletechworld.com/2011/01/25/enable-tethering-on-htc-windows-phone-7-devices/
Trying this now.
Click to expand...
Click to collapse
It says you need to have a developer unlocked phone and also have chevron.
Either a developer account, OR Chevron. Chevron only works on the older OS, and not the newer.
A $99 investment for a developer account is a small price to pay to load any application you want onto the phone (including c++ code to get to that Bluetooth radio!). You even get a nice little XAP deployment tool.
-E
eduncan911 said:
Either a developer account, OR Chevron. Chevron only works on the older OS, and not the newer.
A $99 investment for a developer account is a small price to pay to load any application you want onto the phone (including c++ code to get to that Bluetooth radio!). You even get a nice little XAP deployment tool.
-E
Click to expand...
Click to collapse
well you try it? and how is it working?
Has anyone got this to work? My Arrive is developer unlocked but I can't get the driver to show up in Device Manager on Windows 7 64bit. It seems to connect to my laptop but then no internet connection on the laptop from my arrive.
Thanks for any help,
Peacock93
eduncan911 said:
Either a developer account, OR Chevron. Chevron only works on the older OS, and not the newer.
A $99 investment for a developer account is a small price to pay to load any application you want onto the phone (including c++ code to get to that Bluetooth radio!). You even get a nice little XAP deployment tool.
-E
Click to expand...
Click to collapse
i am a student, and i got a free developer account via dreamspark. how can i do this?
I can't wait until tethering is an easier process for WP7
peacock93 said:
Has anyone got this to work? My Arrive is developer unlocked but I can't get the driver to show up in Device Manager on Windows 7 64bit. It seems to connect to my laptop but then no internet connection on the laptop from my arrive.
Thanks for any help,
Peacock93
Click to expand...
Click to collapse
Same here. has anyone got this to work?
I can't make it work.
Anyone have any new info on tethering the Sprint HTC Arrive?
I spent about 3 hrs on this today. Sprint arrive developer unlocked tried on my windows xp 32bit. It appears the drivers dont want to take. It says not recognized or something along those lines. Its a fairly common problem on the other thread but i have some ideas hopefully ill get to try in the upcoming days.
I have had some success. If you read the dfrouter thread than you are familiar with the process. 2 drivers must be installed on the pc first for it to work. I have the usb modem driver installed after messing around with the file. If i can get the other driver to go i believe ill be able to tether.
This modified driver is running on windows xp and appears to be ready. If anyone has a xp 32bit pc and please pm and we'll see if the driver works for you as well.
If I get the other driver to go ill tether and upload everything.
progress
I spent a few hours on trying to get the vcom driver working last night to no avail.
-on my first attempt i was able to get the driver to be recognized by the pc as the htc diagnostic tool but at the last screen it always said failed.
-on my second attempt i was able to get the driver installed but i dont think it was done properly because it was not recognized as the htc diagnostic tool.
I pm'd a few members on here so we'll see if one of them comes to the rescue, otherwise i'll try again this weekend.
after i get the xp drivers working i believe the windows 7 drivers will be easier.
To get the usbmodem driver to work i only had to change the device id to match the arrive's. the vcom doesnt appear to be that easy, df wrote that it has to be installed as its some kind of qualcom security check.
The weird thing was that i got the 6xx error that others reported when dialing out but it would only dial out in "zune mode" and not "router mode". I dont know if that is because of the vcom driver or not but that behavior was not mentioned at all in the other thread.
Driver?
I posted this in the "Update" thread, too....but figured it was relevant to this discussion....
So, I got the update a couple of days ago, daughter yesterday, wife this morning. I've got two more Arrives to go.
One thing I noticed was that when the phone was put into update mode, my Win7 gave the "found new hardware" dialog and I have a HTC 9#### (I don't remember the number but it was something like 96300 or so -- and a quick google the other day revealed it to be the right model number) driver show up when I clicked on the details. When I plug it in now, it just goes to Zune software again and I can't see the number.....but a driver got loaded.
Did MS push a driver or did whatever flashing mode cause Win7 to recognize it? This might go alonEg with the tethering work being carried out......
EDIT: 93100. Looked through history.
Thats good to know. ive yet to update but i seen it was available so i will do so tomorrow.
Does this driver remain when shown under device manager with the phone plugged in? I will upload the xp 32 htc usb modem driver tomorrow to this post. perhaps this driver can help.
After getting the update, when I plug in the phone, it shows up as "Windows Phone USB" (or was it USB Windows Phone) and not as the 91300. It only showed up in that mode when the phone screen was in a different mode....so, I guess similar to the HTC USB Modem driver screen shot shown above.
EDIT: Found a picture of what the screen looked like when the "New Hardware" was found.... http://www.wp7connect.com/tag/ssl/
success
I'll be updating this afternoon
Here's both the vcom and usbmodem drivers
I was able to get it to work after wahwka helped me
They should install 1st time when you manually force the drivers
here's the thread which I found very useful
http://forum.xda-developers.com/showthread.php?t=922000
Now here's what's really interesting
The modem ONLY dials out in "Zune Mode" not "Router Mode" which is the opposite of what everyone says on that thread.
So it would seem the dfrouter app is not needed at all on the arrive.
Like the modem can be used right out the box if the PC had drivers.
More people need to test what I've found.
I have not been able to connect yet I get error 692 but it may be just a setting is wrong as people have posted in that thread.
I will get working on some windows 7 drivers and see what happens on that PC
I believe the pc I have at my disposal is windows 7 64 so thats what I'll get working on next.
ALSO this app may be dangerous if you're only chevron unlocked read the thread
theres a possibility you may not be able to sync with zune.
I'm developer unlocked so I don't worry about this.
The developer took a lot of heat for this program and he was only trying to help the community so read first.
Id recommend making a backup first. Ill post the win 7 32 bit drivers here tomorrow. I'm still getting error 692 on this [email protected] computer too. I'm begining to wonder if something needs to be changed/tweaked in the phone program to get it to work. Ive just started learning silverlight so maybe ill ask dfvn.
Windows 7 32 Drivers attached.
I'll begin working on windows 7 64 next.
W7 64 Drivers
Windows 7 64 Drivers
This one seemed to be a b&%$h to install
Here's how I got them to install
I plug in the phone via usb
A bubble appears in the bottom right corner saying windows update is looking for drivers
click it
when the next window pops up click the cancel installing drivers
(These steps have to be done quickly or drivers will install and you will have 2 devices portable device HTC T7575 and windows usb device)
If done quick enough you will have two unknown devices _MI01 and _MI00
Force the drivers to install as previously written and ignore the MS warnings and they will install.
From here I notice the same things in all 3 PC setups
The drivers only appear to install in "Zune Mode"
In "Router Mode" I can only get one device to show up
"HTC" MI_00 and MI_01
If I uninstall, click usb sync, htc modem, no matter what I do I cannot get 2 unknown devices unless its in "Zune Mode"
--This needs to be tested by others--
If others come up with the same results
Then this tells us 2 things
1. Our phone or the way it interacts with dfrouter is different than the other wp7 phones that dfrouter works on
2. There is a chance that the htc arrive can be used as a modem without dfrouter and anybody will be able to use it as a modem
Has anyone called Sprint to see when they will offer tethering?
I have been using the APN "internet.com"
If this is not right it could be the reason I have'nt been able to connect
because the modem does appear to dial out
I might be wrong, but I think the APN is supposed to be blank for CDMA carriers. I can't post links but Google "tcp_apn_etc_for_sprint" and see the pinstack thread.
I have already been having problems with my Arrive's EVDO modem getting stuck in "null state" (kills all wireless data until RTN wipe) so I will probably wait for a more stable tethering solution.
For what it's worth I am running WinXP 32bit and using the attached drivers when playing around in QPST/QXDM and in USB Storage Mode. Hope some of this helps you!
My work just purchased window 8 RT tablets for us. (ASUS TF600T). I tried to jailbreak the tablet using the tool on this site. when I run the tool, it asks me to push the volume down button, the tablet says it detected an error and needs to restart. Sorry, no error code. Id like to able to install some small programs, like keepass, end eventually even a full version of office if it becomes available. Anyone know why it keeps failing and what I can do to jailbreak this thing.
try posting the the windows 8 section of the forum, they probably have tutorials for jailbreaking windows rt
http://forum.xda-developers.com/forumdisplay.php?f=1286
click thanks on the bottom part of the post if helped
Make sure it's got all of the updates installed. I have the same device - once all of the updates were installed on it, the worst I've found is that I have to wait for the system to settle (open Task Manager, wait until most of the usage is by Task Manager itself and not the system, about a minute) before the jailbreak will work, but then it works every time.
Most of the reason for failure that I've seen after startup looks to be because the kernel location that the jailbreak is tweaking isn't at the right location (which is why you need to be fully patched), though it will fail all the time if its done too soon after startup.
Meratiogerr said:
My work just purchased window 8 RT tablets for us. (ASUS TF600T). I tried to jailbreak the tablet using the tool on this site. when I run the tool, it asks me to push the volume down button, the tablet says it detected an error and needs to restart. Sorry, no error code. Id like to able to install some small programs, like keepass, end eventually even a full version of office if it becomes available. Anyone know why it keeps failing and what I can do to jailbreak this thing.
Click to expand...
Click to collapse
irony_delerium said:
Make sure it's got all of the updates installed. I have the same device - once all of the updates were installed on it, the worst I've found is that I have to wait for the system to settle (open Task Manager, wait until most of the usage is by Task Manager itself and not the system, about a minute) before the jailbreak will work, but then it works every time.
Most of the reason for failure that I've seen after startup looks to be because the kernel location that the jailbreak is tweaking isn't at the right location (which is why you need to be fully patched), though it will fail all the time if its done too soon after startup.
Click to expand...
Click to collapse
I did updates as soon as I took it out of the box. apparently it missed a couple, so I had to do It again. worked after all of the updates had been done. Unfortunately more research and it doesn't look like I'm ever going to be able to load access on this thing, which for my work makes it pretty much useless.
Hi
I have a samsung ativ tab.
I ended up downloading all the versions of the RT Jailbreak tool but still haven't succeeded to jailbreak windows RT on my Samsung Ativ Tab.
Any idea what could be the problem?
When I press volume down, it crashes and displays the blue screen with the REFERENCE_BY_POINTER error.
I installed all the updates, gave it about one to two minutes each time I ran it but still couldn't jailbreak.
any idea?
irony_delerium said:
Make sure it's got all of the updates installed. I have the same device - once all of the updates were installed on it, the worst I've found is that I have to wait for the system to settle (open Task Manager, wait until most of the usage is by Task Manager itself and not the system, about a minute) before the jailbreak will work, but then it works every time.
Most of the reason for failure that I've seen after startup looks to be because the kernel location that the jailbreak is tweaking isn't at the right location (which is why you need to be fully patched), though it will fail all the time if its done too soon after startup.
Click to expand...
Click to collapse
crackero said:
Hi
I have a samsung ativ tab.
I ended up downloading all the versions of the RT Jailbreak tool but still haven't succeeded to jailbreak windows RT on my Samsung Ativ Tab.
Any idea what could be the problem?
When I press volume down, it crashes and displays the blue screen with the REFERENCE_BY_POINTER error.
I installed all the updates, gave it about one to two minutes each time I ran it but still couldn't jailbreak.
any idea?
Click to expand...
Click to collapse
I can't get mine to go either. No matter how long I wait after boot. no matter how little resources are using the cpu/ram. I've tried different versions. I've tried different download links. but all I get is a registry key error and it saying I didn't wait the 2 minutes even if I waited 30 min. ASUS TF600T Win8.1 RT.
If ANYONE has any idea. I would greatly appreciate the help.
EDIT: Just realized the pics are blurry. The error syas "ERROR: The system was unable to find the specified registry key or value. Waiting for uptime to reach two minutes." (This was after waiting 10 minutes)
My device just got bricked. It was part of the recall and I had removed TegraOTA long ago. Today, after a few weeks of testing out CM13, I decided to go back to stock, remembered to flash the NoMoreOTA zip file but for some reason, it didn't stick. My device started downloading an update which I failed to get suspicious at, then shut down and hasn't come back online since.
This is far more than the frustration of losing a device and its data. It's a scary thought that NVidia has the ability to so utterly control our devices from a distance, with very little that can be done to prevent it if you're an average user. Remember that fuss when Amazon used DRM in their EBooks to remotely delete them from the computers of customers that legally purchased and should've had full rights to the content? This is inexcusable, and we must work to find a fix and pressure NVidia into giving up this disturbing practice.
Here are a basic list of resources I'm researching that have potential, I'll be posting as stream-of-consciousness and these links will also be here for reference when I reboot into Linux for some of the more advanced stuff. I can't make any promises, but stay tuned, this might just work!
Resources
Main XDA discussion RE kill switch
An old method that worked on the first variation of the kill switch (doesn't help anymore, since now the kill switch directly attacks the bootloader)
More discussion on the topic:
https://forum.xda-developers.com/shield-tablet/help/shield-tablet-stuck-apx-mode-black-t3074446
So far:
Bootloader is corrupted. Device is showing as APX.
Step one, therefore: Download APX drivers.
I found these for the Note 7, weren't easy to come across.
Slight issue with signature verification. You need to reboot into advanced settings and disable device driver signature verification.
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/​
To use NVFlash, we need the device's SKB. Most forum members seem to agree that's virtually impossible without a leak from NVidia themselves, but those same people also claim the same issue with getting an APX driver for the Shield, so maybe it can be done. A hopeful post on the matter:
[GUIDE] Recovering Recovery/Obtaining SKB
Below link looks promising, need to obtain blob from stock rom. Guy claims he has the blob file, but we still need the SBK:
https://www.reddit.com/r/theNvidiaS...shield_tablet_bricked_at_1114_pm_est/cu2kudk/
This might help:
SBCalc - Generate your SBK (v1.1)
https://forum.xda-developers.com/showthread.php?t=1927818
What is NVFlash and what are SBKs?
http://www.androidroot.mobi/pages/the-inner-workings-of-secure-boot-key-and-nvflash/
More unresolved threads on this topic:
https://forum.xda-developers.com/shield-tablet/help/shield-tablet-stuck-apx-mode-black-t3074446
https://forum.xda-developers.com/shield-tablet/general/recover-y01-battery-shield-tablet-t3199153/
Lives Updates To Come
You cant repair kill switched NST, because tegraOta attack bootloader at low level and btld is pernamently corrupted.
Also Since Nvidia Tegra Note 7 SBK key is not used its an ODM key system. So they are heading into the wrong bush. only Nvidia knows the ODM key. But good luck.
Hey ReckoningForce,
Really hope you find a way, been searching for hours myself.
Driving me mad as i was bloody stupid enough to turn my should have been recalled device one without turning off the WiFi first, so unfortunately in the same boat as yourself.
Please update this thread if you get anything working!
Thanks again mate
hI, I HAVE A SHIELD 2017 with boot unlocked , but after downgrade from 9.1 to 8 (7.2.3) are in permanent loop:
1 message about risk unlock
2 logo nvidia
3 coloured cirlcle of anroid running
After get print on display "android" it loop into nvidia logo and repeat again infinitely those steps: HDMI recognize them as "Shield"
if i put a keyboard on usb port and i try to boot into fastboot/recovery ( A+B+PWRON) dont
do anymore loop but are stucked into run coloured cirvcles on screen : HDMI recognize them as "PB1"
Also un usb service port it recognize it as MTP USB device
does exist any possibility to get recovery or fastboot mode or i need to throw it out?
I have a AudioVox T852 tablet that is stuck on logo, there's no button combo to enter recovery only thing it has is a reset pin hole tried numerous times and nothing my computer recognizes the tablet but can't find driver.. I reached out to the company and asked for the USB drivers and firmware if possible.. There reply was "Sorry to hear your having trouble but this tablet is no longer supported" to which I replied " No longer supported so **** me right" so how can I or what drivers can I install so I can try and fix it.. Thanks
xOwNx said:
I have a AudioVox T852 tablet that is stuck on logo,.........
Click to expand...
Click to collapse
I don't have this device and I personally can't locate any real threads for this as well...
The best thing I can do is to provide you with the following links that will, hopefully, be helpful to you.
https://voxxintl.zendesk.com/hc/en-...the-Audiovox-Tablets-T752-T852-T852SBK-T852PK
http://www.fixya.com/support/t26488427-audiovox_tablet_model_t_852_stuck
The following is a Google Search link that's specific for searching the fixya website that seems to have allot of results as well.
https://www.google.com/search?q="Audiovox T852" site:www.fixya.com
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
Yeah ive been up and down those links every link but cant do anything without the drivers i tried force installing drivers that come close but nothing. I was even thinking of writing my own usb drivers for the heck of it but ill check every other option before heading down that road ...thanks anyways
xOwNx said:
Yeah ive been up and down those links every link but cant do anything without the drivers i tried force installing drivers that come close but nothing. I was even thinking of writing my own usb drivers for the heck of it but ill check every other option before heading down that road ...thanks anyways
Click to expand...
Click to collapse
When you say that you tried force installing the drivers and came close but nothing, what do you mean "came close" exactly?
Do you have the driver install .exe to install them? When you install them, does it say they were successfully installed but you still get nothing? If so, you may have to manually configure the driver through device manager. I've had to do this with a couple of tablets to get PC to recognize the device while in fastboot.
Sent from my LGL84VL using Tapatalk
Just to be clear theres no drivers for Audiovox T852 tablet at all, even the damm company that makes them refuse to hand it over. They said since its not supported anymore anything and everything for the Audiovox T852 is deleted out there system (when does anyone actually completely delete anything?Right?) Now when i say close i mean i did force install a USB MTP Driver but with a error 10 something along service or drivers could not start. My pc reconized it T852 but with a ? But anytype of commands or software i use to try and anything just wont work without The Damm drivers.. o 1 more thing the T852 also has no fastboot mode or recovery to get into..
xOwNx said:
Just to be clear theres no drivers for Audiovox T852 tablet at all, even the damm company that makes them refuse to hand it over. They said since its not supported anymore anything and everything for the Audiovox T852 is deleted out there system (when does anyone actually completely delete anything?Right[emoji19]) Now when i say close i mean i did force install a USB MTP Driver but with a error 10 something along service or drivers could not start. My pc reconized it T852 but with a ? But anytype of commands or software i use to try and anything just wont work without The Damm drivers.. o 1 more thing the T852 also has no fastboot mode or recovery to get into..
Click to expand...
Click to collapse
It's hard to believe that the drivers haven't been stored/posted somewhere else by someone using some kind of online file sharing site or forum, even if they weren't kept by the manufacturer.
I looked up the specs for your device, the specs say that you have an Amlogic Cortex A9 CPU architecture, have you tried drivers for other devices that use Amlogic Cortex A9 processor?
Also, when in device manager, try selecting the device on the list then right click then select "properties" then select the "details" tab then click on the drop down menu under "property" that shows "device description" by default then select "hardware IDs", write down the ID values, it will be more than one line of ID codes, then do some Google searches to find drivers for those ID codes? Sometimes that will find drivers that work for those hardware IDs, even if the drivers weren't specifically built or offered by the manufacturer of your hardware. Sometimes installing a driver that matches the hardware ID gets that particular hardware ID to work and gets it recognized by the system but then the system detects another "layer" of hardware with its own hardware ID that also needs a driver. Sometimes, if you go layer by layer installing drivers for each new hardware ID that gets exposed by the last driver that you installed, you can eventually get to where each "layer" is recognized, if you are lucky enough to find drivers for each hardware ID layer, you get to where the device is completely recognized correctly. I've done this before to get hardware recognized when I had nothing to go by to identify the device or component.
Sent from my LGL84VL using Tapatalk
Dude when I'm telling you I did it all even the darn hardware id's get 0 zero nothing nada in google search results.. That's why I said I'm down to writing creating my OWN drivers I've litterly did the ins and outs and then some.. I just decided to post my problems to see what comes about if I get some sorta guidance it's a plus if I don't no biggy. Ive been at it since the first flip phones came out changing blacklisted imei with cdma workshop qpst fixing tablets computers cracking software but every so often I come across these Chinese tablets that have little to no support and I just put them aside, but nope not this time I'm seeing this issue all the way through hopefully with the help of second to none XDA COMMUNITY.... ?
xOwNx said:
Dude when I'm telling you I did it all even the darn hardware id's get 0 zero nothing nada in google search results.. That's why I said I'm down to writing creating my OWN drivers I've litterly did the ins and outs and then some.. I just decided to post my problems to see what comes about if I get some sorta guidance it's a plus if I don't no biggy. Ive been at it since the first flip phones came out changing blacklisted imei with cdma workshop qpst fixing tablets computers cracking software but every so often I come across these Chinese tablets that have little to no support and I just put them aside, but nope not this time I'm seeing this issue all the way through hopefully with the help of second to none XDA COMMUNITY.... [emoji108]
Click to expand...
Click to collapse
I know it's frustrating, I can't stand the crap that comes with messing with Chinese devices. You asked, I posted everything I could think of.
Also, I wouldn't brag about changing a blacklisted IMEI and cracking software here at XDA. That kind of thing isn't tolerated here because it's illegal in most places. Guys that do that kind of thing around here get banned from the site.
Sent from my LGL84VL using Tapatalk
I wasn't bragging is was intended so that time isn't wasted with noobish, common sense, or beginners replys that's all, but my fault going over what I said i definitely missed the point I wanted to get across..
Have you done with this site? Happy new year by the way...
Dont expect people to post in relevant sections when the section links point to bloatads.... btw, where are the relevant sections now?
Ok I'll try here... got a lenovo TB-X103F, repairing it for an old woman next door, but hey, guess what, seems lenovo have killed it in every way... for instance...
I deduced at first the battery was the problem, but after removing battery packs and applying power direct to battery terminals, it was not JUST the battery... she could not even click her account to login!, so she buys a new one, and tells me to keep this one. So I fire it up intending to root it, only adb wont recognise device.. fastboot wont recognise it, so try the qualcomm drivers, the qpst drivers etc, nothing, all it shows is unknown device in my win 7 x64 machine.
I factory restored it, but cant even login to wifi, strange, because it is going through my cmts and network switch, and doing some data transfer, yet all it does on screen is say either saved, or wlan connection failure, proving lenovo ****ed this poor old woman over as I guessed, in order to make her buy a new tablet, which she did, and it was not a lenovo, haha, so in a nutshell, I'm trying to bring some kind of life back to this device, but the skip is greyed out at the choose wifi screen, and without adb or fastboot showing...? Any hints?