Hi, as the title says, I'm trying to unlock the bootloader of my V30 (H930, firmware 20r), and each time I try to unlock it, it hangs on the first step of the unlock process:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've gone through the 'WTF' post here, and I've done all the troubleshooting apart from trying Windows 7/another PC, and trying another USB-C cable (only have the one). It's 2nd hand, so I have no idea if it was previously Android 9/10, if that complicates things?
Any help would be great, TIA.
Irradium said:
I've done all the troubleshooting apart from trying Windows 7/another PC, and trying another USB-C cable
Click to expand...
Click to collapse
You admit you haven't tried all the Troubleshooting Tips. That's your answer and you know it.
For some people it works on the THIRD different computer they tried, or the THIRD different USB cable.
___
Any reason why you started a completely different thread, when your question is about the WTF INSTRUCTIONS? I'm going to repost your question and the answer there, where it belongs.
ChazzMatt said:
You admit you haven't tried all the Troubleshooting Tips. That's your answer and you know it.
For some people it works on the THIRD different computer they tried, or the THIRD different USB cable.
___
Any reason why you started a completely different thread, when your question is about the WTF INSTRUCTIONS? I'm going to repost your question and the answer there, where it belongs.
Click to expand...
Click to collapse
Just keep trying different cables and computers until it works, huh? That's... heuristic, to be sure.
When you put it that way, yeah, good idea to repost it.
Irradium said:
Just keep trying different cables and computers until it works, huh? That's... heuristic, to be sure.
Click to expand...
Click to collapse
If you have tried the different ADB installations, you've installed all the different Windows, Google, LG drivers mentioned in the Troubleshooting Tips, and you're on the right firmware, then the only answer is to try a different computer or a different cable. I can give example after example...
One guy had a very expensive Windows 10 GAMING computer, but it worked with his brother's very cheap Windows 10 laptop computer. He couldn't believe it.
Also, while Windows 10 will work, Intel Windows 7 with USB 2.0 ports seems to work best. Or you can order a cheap USB 2.0 hub off eBay and plug it into your computer.
Except for the right firmware (Tip #1), all the other Troubleshooting Tips deal with ADB communicating with your phone. There's 11 tips whose sole purpose is to makeh ADB communicate with with your phone to send this unlock code.
---------- Post added at 08:51 PM ---------- Previous post was at 07:55 PM ----------
See here:
NeonHD said:
Hi, just want to say that for anyone who is stuck on the Sending 'unlock' part, I HIGHLY RECOMMEND switching to another computer. I was stuck on that part and I did everything from reinstalling the drivers to using another adb package and still to no avail. Then—as it was suggested and performed by many—I finally decided to switch to another computer (my PC tablet running windows 10) and guess what?? It works!!!
I was expecting to get the same error, but nope I FINALLY unlocked my V30!!
This is my testimony to you all so hopefully more people will do this before giving up.
Click to expand...
Click to collapse
Irradium said:
Just keep trying different cables and computers until it works, huh? That's... heuristic, to be sure.
Click to expand...
Click to collapse
As ChazzMatt wrote, different cables, different USB ports, different computers.
The only thing I'd add is to run fastboot devices after entering fastboot mode, before flashing unlock.bin. If it doesn't list your phone's ID at that point, you know the connection isn't working.
Not gonna lie, I was skeptical at first too whether changing computers would actually fix anything, but it did. Perhaps ADB drivers work better on Intel than AMD devices.
NeonHD said:
Not gonna lie, I was skeptical at first too whether changing computers would actually fix anything, but it did. Perhaps ADB drivers work better on Intel than AMD devices.
Click to expand...
Click to collapse
Funnily enough, my main machine (Ryzen 1600) got as far as starting the flash, whereas my work laptop (Intel ??) didn't even list the device...
Irradium said:
Funnily enough, my main machine (Ryzen 1600) got as far as starting the flash, whereas my work laptop (Intel ??) didn't even list the device...
Click to expand...
Click to collapse
Doesn't work with AMD Ryzen whatsoever.
If you search in the WTF thread for "Ryzen" you'll see all the failures. To be honest, I'd never heard that name before V30 WTF thread. I stopped using AMD years ago because I kept being disappointed about performance vs Intel on budget laptops and desktops for family and friends.
Related
I've tried everything. IT WILL NOT recognize my phone.
When trying to install the drivers it says the Authenticode does not have permission. I got the damn drivers directly from Android.com but it still doesn't think its authentic. Because of this, o cannot get the computer to recognize it as an adb device to root the phone.
I'm going nuts now. 2 days with literally 8 to 10 hours of trying with no success.
Can someone please please PLEASE help me?
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
rk0 said:
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
Click to expand...
Click to collapse
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
uoY_redruM said:
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
Click to expand...
Click to collapse
http://www.junefabrics.com/android/driver.php
Tried USBDeview, doesn't seem to let me uninstall anything even though it says you can.
Nothing appears to work.
This is what I keep getting, no matter what I do:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and what makes no sense is when trying to manually install new hardware, it SHOWS there are authenticodes for those drivers:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
I had the same issue, turned out it was a hardware bug.
I sent it to the repair center at HTC in United Kingdom and i had it returned 5-6 days after, working and with locked bootloader
britoso said:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
Click to expand...
Click to collapse
Vista.
I've tried a few of those suggestions and non of worked. Most involved the bcedit trick but its disabled or doesn't exist in the newer security updates.
Vista 32 bits or Vista 64bits ?
in hardware management console what do you see ? yellow question mark ?
Sometimes you need to go in it and find your device to check the HID number and copy it manually in the driver *..inf files to be detect by your OS.
I remembered doing this for my G1 long time ago (years).
If you can, get your hands on another n1 or android device to see if its a hardware problem with the phone, which i doubt. Also try a diff OS.
uoY_redruM said:
I've tried everything. IT WILL NOT recognize my phone.
Click to expand...
Click to collapse
This is for windows 7 64bits : http://tinyurl.com/2548qh4
take a look @ post #4
Hope you solve your problem !
In case you have Windows 7 you can try the following.
http://www.killertechtips.com/2009/...gning-in-windows-7-using-group-policy-editor/
Are you installing the usb drivers using the utility in ADB? If not, delete the drivers in hardware manager, and try installing them with the utility.
I had no problems doing this on Vista, but I prefer to use ADB on Linux.
Sent from my Nexus One using XDA App
hey .
maybe i´ve got something for you.
download my file here
install the binaries and then reboot (i said you don't have to, but i think in your case it would be better)
EDIT: is the debug function enabled in your device?
OK, after a few hours and still no success with Vista, I went to storage and pulled out my personal PC I built that hasn't run in a few years thanks to corrupt hard drives.
I spent 4 hours repairing and fixing the hard drives and SUCCESS, I got it to detect it on my Windows XP PC.
NOW! Still not working! In the command prompt, it shows adb devices as one connected but still when I do an adb push nothing happens. Just recycles the adb menu....
Any suggestions?
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Try using a Linux distribution. Saves a lot of time and headache.
or just reinstall your windows. win7 would be better than vista.
malevolent000 said:
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The PC I'm using now IS working. It recognizes adb device but wont push the flash images or anything.
Hello xda people . i can't install anything or boot in recovery via fastboot. at the first times it worked but now i can't install anything.it stucks on "sending boot" . how can i fix this problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fastboot help
Which OS you are using ... just keep the windows update on the drivers will be downloaded automatically .. Get some more details of your computer
It seems you have driver problem.
try 'fastboot.exe -i 0x0fce getvar version'
if it returns something like 0,3 it means drivers are installed correctly.
if stucks on waiting for device, reinstall drivers =)
Ok thanks I have Windows ultimate 7 32bit
Sent from my MT11i using Tapatalk
hm... try to reinstall drivers from flashtool folder.
Or this drivers: ht tp: / /narod.ru/disk/41611663001.12211e20e6329016ba9f418a88544664/fastboot_ADB_drivers.zip.html
sorru for russian uploader
Works on my win7 x64 PC and 7 x86 notebook
I have same problem, looks like I have problem with drivers, can some1 upload drivers for 64bit Win7? I can't download drivers from this russian server don't know why.
dalany said:
It seems you have driver problem.
try 'fastboot.exe -i 0x0fce getvar version'
if it returns something like 0,3 it means drivers are installed correctly.
if stucks on waiting for device, reinstall drivers =)
Click to expand...
Click to collapse
see my friend . the first stuck and the second send it with very poor speed
Replace USB cable
May work
Qwerty123 \m/ said:
Replace USB cable
May work
Click to expand...
Click to collapse
i don't think that is the problem , because on my sis laptop it works normally. anyway i will try a format and install new windows to see.
Thanks all ppl for answers
sspoko said:
I have same problem, looks like I have problem with drivers, can some1 upload drivers for 64bit Win7? I can't download drivers from this russian server don't know why.
Click to expand...
Click to collapse
Hi buddy
Here U R
the link you want it
as I'm new I cant send link in form of Url
follow this ht tp://w w w.mediafire.com/download.php?y89fff6mc8hblia
I had a similiar problem, though not the same. It was fixed after a reboot of my Windows 7 x64. I think my computer had problems dealing with the USB being connected and disconnected an awful lot. I have no idea if this is where your problem comes from, but it might help if you're like me and prefer leaving your computer on at all times.
Also, if you're quite new to rooting and flashing, and aren't that interested in learning the ins and outs of it, I recomend using Flashtool [1] for flashing to an earlier version of stock Android, rooting your Android, easy booting in fastmode and flashing your kernel. The only use I've found for fastboot.exe is to unlock your bootloader [2] (official guide by Sony Mobile), though I might be missing out on something (while I actually do not believe I have).
Please keep us posted.
As I'm a new member, I can't link directly to outside sites, but I'm going to break that rule to try and help you even further (ie. I did the Googling for you). Replace the spaces below with periods. Links:
1: androxyde github com/Flashtool/
2: unlockbootloader sonymobile com/
Markussssss said:
I had a similiar problem, though not the same. It was fixed after a reboot of my Windows 7 x64. I think my computer had problems dealing with the USB being connected and disconnected an awful lot. I have no idea if this is where your problem comes from, but it might help if you're like me and prefer leaving your computer on at all times.
Also, if you're quite new to rooting and flashing, and aren't that interested in learning the ins and outs of it, I recomend using Flashtool [1] for flashing to an earlier version of stock Android, rooting your Android, easy booting in fastmode and flashing your kernel. The only use I've found for fastboot.exe is to unlock your bootloader [2] (official guide by Sony Mobile), though I might be missing out on something (while I actually do not believe I have).
Please keep us posted.
As I'm a new member, I can't link directly to outside sites, but I'm going to break that rule to try and help you even further (ie. I did the Googling for you). Replace the spaces below with periods. Links:
1: androxyde github com/Flashtool/
2: unlockbootloader sonymobile com/
Click to expand...
Click to collapse
thanks but actually i have unlocked bootloader.. and i have some xperience because i had x8 and i have tweaked it full
Had similar problem!
First couldn't get into fastboot, had problem installing S1 driver. Changed the USB port on my PC and it asked to install the S1 again. Chose the directory where it was and voila.
Now I have to use 2 different USB port for fast boot and flashmode. Little annoying but I got used to it.
Try it, it may work for you.
Reinstalling Windows should be your last step, especially a stable OS as Win 7!
P.s. Why don't you use Flashtool? In it's newer version there's a *.exe (under drivers folder) file that automatically install all needed drivers.
DNDimitrov said:
Had similar problem!
First couldn't get into fastboot, had problem installing S1 driver. Changed the USB port on my PC and it asked to install the S1 again. Chose the directory where it was and voila.
Now I have to use 2 different USB port for fast boot and flashmode. Little annoying but I got used to it.
Try it, it may work for you.
Reinstalling Windows should be your last step, especially a stable OS as Win 7!
P.s. Why don't you use Flashtool? In it's newer version there's a *.exe (under drivers folder) file that automatically install all needed drivers.
Click to expand...
Click to collapse
i will try
So I've been trying for quite awhile to bring my player back. I was trying to develop my kernel with it and it just plummeted to it's death eventually. I found a DD dump somewhere of another device and flashed it, which I guess might not have been exactly the right file and now here we stand.
The device doesn't turn on, I don't get any "SAMSUNG" boot logo - nothing. It comes up in windows as
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now from the research I've done, that should be the "lucky unbrickable" state. The device does nothing, but still shows up in windows. I've tried unbrickable on windows 7, windows 7 via a ubuntu VM, and went as far as to setup a dedicated desktop with ubuntu natively and a windows XP VM. I can only get my player to react on the native linux desktop, but it enters download mode really strangely -
YouTube video of it being "resurrected"-
http://youtu.be/WDclUEyoHFE?hd=1
And after that I lose USB (although the device stays on and powered up as long as I leave it connected). I tried connecting the device to my XP VM which is what everything says to do, and I get "No USB devices connected" in virtualbox. Dmesg gives me "unable to enumerate USB device on port 1, device descriptor read/8, error -71" as soon as download mode initiates.
Every time I've done this whole process before, it's worked wonderfully and you can continue on and flash your bootloaders, then reflash everything else. I've tried this whole process over and over and over and haven't had any success. I also tried a USB jig and it didn't do a single thing.
Can anyone provide ANY insight? I'm really open to anything right now, otherwise it's out for JTAGing. I'm about at whits end with it and I'm out of ideas.
THANKS!
If it "worked perfectly before" in this configuration, your pb is mostly related to Samsung win 7 drivers that are not reachable or "lost".
try to reinstall them and check their availabilty connecting another Samsung device (ask your friends);
note: For me under win 7 , I installed ubuntu as second boot with windows and I forgot the Virtual box trick, that's much simpler and I can learn linux when I have free time...
Good Luck
lolo9393 said:
If it "worked perfectly before" in this configuration, your pb is mostly related to Samsung win 7 drivers that are not reachable or "lost".
try to reinstall them and check their availabilty connecting another Samsung device (ask your friends);
note: For me under win 7 , I installed ubuntu as second boot with windows and I forgot the Virtual box trick, that's much simpler and I can learn linux when I have free time...
Good Luck
Click to expand...
Click to collapse
My windows 7 computer connects fine to my galaxy s3. I just root/recovery/rom/kernel'd it a few days ago from that computer, so everything seems to be working as it should.
Have you tried heimdall on your linux machine? Like this you would not need to disconnect your player at all and you would avoid using virtualbox.
ti-pich said:
Have you tried heimdall on your linux machine? Like this you would not need to disconnect your player at all and you would avoid using virtualbox.
Click to expand...
Click to collapse
Yeah, I actually just did that. I even went as far as trying the current and past 3 versions of heimdall and it doesn't detect any devices.
Sent from my galaxy nexus using xda app-developers app
oneclickunbrick
hey bro try this
download this program called oneclickunbrick
i done the same then when i got home i went looking and i found this
it works like a charm
ps if it doesnt work right the first few times make sure your player is using a comport of your computer and it will work like a charm
http://forum.xda-developers.com/showthread.php?p=15330252
link for the program ^
Evoium said:
hey bro try this
download this program called oneclickunbrick
i done the same then when i got home i went looking and i found this
it works like a charm
ps if it doesnt work right the first few times make sure your player is using a comport of your computer and it will work like a charm
http://forum.xda-developers.com/showthread.php?p=15330252
link for the program ^
Click to expand...
Click to collapse
Thanks, I'll try that when I get home. It looks like a precursor program to the unbrickable mod but I'm willing to try anything at this point!
Sent from my Galaxy SIII
has it worked for you ?
Have you installed the heimdall drivers? Like went into the drivers folder, ran zidag and replaced your "SAMSUNG COMPOSITE USB" or something like that with the first driver? That may make heimdall recognize it.
PairOfSocks said:
Have you installed the heimdall drivers? Like went into the drivers folder, ran zidag and replaced your "SAMSUNG COMPOSITE USB" or something like that with the first driver? That may make heimdall recognize it.
Click to expand...
Click to collapse
Yep, tried that a few times. I was using heimdall before so the drivers should be kosher for it.
It's almost like once it enters download mode the hardware isn't cooperating. I've also gone as far as trying every previous version of UnBrickable thinking one might work better, but I've gotten the same result with all the versions. Download mode shows up and then it drops all connectivity.
Hello friends of XDA, i'm here to ask you help once again! This time the problem is about a mysteriuos p760 aka LG Optimus L9. The problems in which i came across is the unlocking the bootloader and installing a custom recovery.
I tried so many ways that i'm really out of resources and ideas... Here few screenshots of the phone informations from setting app:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am using Windows 8.1U3 on an Alienware 17.
I'll try to explain as fast and clearly i can:
First i read about this thread and it simply didn't worked (wow totally unexpected thanks to my fortune (Y)).
Then i thought i could easily flash some KDZ with unlocked bootloader and a sparky CWM built in, so i've google a little around and i found this and I then tried to flash the
with this guide but here the fun begun! No matter how i installed drivers, rebooted the system, tried in recovery mode or S/W Mode, the software did not see any phone at all; on the contrary the device manager sees it clearly and install correctly the drivers.
After posting the errors i found an answer a month later in the same thread.
This guys advices to use this tool instead, but as you can guess from me writing here, it did not work.
Then googling again i found this guide where you can install a CWM without even unlocking the bootloader! So, hey, i just need the root!
So let's go finding some way to root this F device (may LG go bankrupt now)! Again i googled "root p760/l9/optimus/plslgdie" and i found few ways none of them working. The Saurik one tells me that there is no bug available to exploit, the Chinese all-in-one rooter seems not having any green button and other script based on adb simply do not find the phone!
Of course i've tried a lot of cables and computers, all of them not working (still i need to try another OS....) and i'm going crazy. Only another device drove me crazy like that (the e610 aka L5 - wow this too was totally unexpcted!) but i finally found a ways to solve.
Please help me to delete every single line of code LG compiled in this device, please!
Up! Halp pls!
Did you try to install uboot and xloader?
Rammar515 said:
Did you try to install uboot and xloader?
Click to expand...
Click to collapse
Actually not yet, but still, i prefer to flash the kdz! what if something goes wrong? how could i recover the phone?
Oh, I thought you can't run this phone, my bad, sorry. Could you show us which driver did you install?
Rammar515 said:
Oh, I thought you can't run this phone, my bad, sorry. Could you show us which driver did you install?
Click to expand...
Click to collapse
Well no need to apologize, you did not offend me i installed the latest from the site, exactly the LGUnitedMobileDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3. Furthermore i even formatted the PC to try this because i thought that some Nexus drivers could have messed up with them!
Lamba92 said:
Well no need to apologize, you did not offend me i installed the latest from the site, exactly the LGUnitedMobileDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3. Furthermore i even formatted the PC to try this because i thought that some Nexus drivers could have messed up with them!
Click to expand...
Click to collapse
@Rammar515 do not abandon me please :crying:
It's hard to say. I remember some people told me that windows 8 have problems with l9 driver. I don't want to say that you can reinstall drivers, because I'm sure you did it a few times. You can always install windows 7 but it's derp idea (of course if you want, you can do it). Did you try to run official LG recovery program and try to install from it?
Rammar515 said:
It's hard to say. I remember some people told me that windows 8 have problems with l9 driver. I don't want to say that you can reinstall drivers, because I'm sure you did it a few times. You can always install windows 7 but it's derp idea (of course if you want, you can do it). Did you try to run official LG recovery program and try to install from it?
Click to expand...
Click to collapse
Never tried from the official software, but tomorrow i will try both XP SP3 and 7! I fund an old rusty laptop with 2GB ram and a Pentium D! I'll format it until drivers will work :silly:
Ok now i even tried Windows 7 and still nothing.... What's wrong with this phone? It makes me want to kill Bon-Moo Koo...
Hi my name is Jon. I've been searching everywhere for the firmware of Rca firmware RCT6213W87M tablet Android 6.0 also I can't seem to find any drivers that work. Every time I hook it up through USB 'the PC tells me something about device not recognised drivers not installed. I've tried various way to get the drivers installed and looked everywhere for the correct firmware. I can't root' flash or install any custom recovery. I'm at my wits end with this and i would appreciate any help
JON40 said:
Hi my name is Jon. I've been searching everywhere for the firmware of Rca firmware.........
Click to expand...
Click to collapse
I don't have this device but, the following thread should give you a good start for what you are looking for that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3326341
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Ibuprophen said:
I don't have this device but, the following thread should give you a good start for what you are looking for that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3326341
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
Thanks for the reply. That thread is actually the first thing i read before i actually signed up as a member. I read through all 20 something pages and the author of the thread states close to the end of the thread that one has found a firmware for the maven pro with android 6.0. If I could manage to get the drivers installd atleast i could make some kind of leadway on doing other things, like installing a custom recovery but i cant even get my pc . .. laptop running windows 7 to recognize the tablet when I plug it in.... i dont know what else to do at this point but drop kick this tablet into another universe....
Did u find anything yet?I have the same problem
JON40 said:
Thanks for the reply. That thread is actually the first thing i read before i actually signed up as a member. I read through all 20 something pages and the author of the thread states close to the end of the thread that one has found a firmware for the maven pro with android 6.0. If I could manage to get the drivers installd atleast i could make some kind of leadway on doing other things, like installing a custom recovery but i cant even get my pc . .. laptop running windows 7 to recognize the tablet when I plug it in.... i dont know what else to do at this point but drop kick this tablet into another universe....
Click to expand...
Click to collapse
Hi, I, too, have been very frustrated with the same problem, having tried all the root apk's I could find to root my RCA Maven Pro 11.6 tablet pc rct6213w87mm to avail. This device has to be one of the most difficult, if not impossible, tablet pc's to root and I'm wondering cynically whether the manufacturer intentionally made it like that to prevent the user from deleting many frivolous bloatwares installed that cannot be uninstalled without rooting the device. I sent an email to the RCA tech support requesting the usb driver for this model, but have not gotten any response, yet, if they will ever respond, that is.
Another Jon here. No relation.
I support a bunch of these specific tablets, we use them for sheet music display. Can't find firmware, can't root them. I feel your pain. However...I also know that the #1 problem with the RCT6213W87M tablet is that it spontaneously crashes & reboots whenever the Play Store app tries to install the latest version of the Google app. Took me awhile to figure this one out, let me tell you. Google doesn't care, because Android 6.0 is yesterday's news to them. RCA doesn't care, because they want you to buy a new tablet. But all the musicians care, very much, when their sheet music display crashes in the middle of a set. I told them to stop being lazy and just memorize all the music. They didn't think that was funny.
My initial fix was to disable auto-updates in the Play Store app, but that's a maintenance headache. A better workaround is to use the instructions at https://www.maketecheasier.com/prevent-specific-android-apps-auto-updating/ -- scroll about halfway down to "Stopping One App From Updating" and do that for the Google app. You still can't root the tablet or remove the bloatware, but it will at least stop the spontaneous reboots. And the musicians will stop throwing the tablets at you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}