Related
Hi guys my girlfriend bought a LG Viper 4G LTE and she told me to root it to remove the sprint crap, so I was wondering if anyone has already done this and if yes, can they tell me how to s-off + root + custom recovery + and probably custom ROM.
If anyone can help, please I'll appreciate it. Since I searched here for that phone and is not even listed.
The phone is running android 4.0.4, is this ICS or Jelly bean?
I do not know how to get into fast boot boot loader cause I don't think it is POWER + VOL DOWN.
Thanks in advanced
Have a nice day
:what::what::what::what::what::what:
Sent from my Nexus 10 using Tapatalk HD
Im trying to root mine right now and can't seem to get it to work, I've tried Root_with_Restore_by_Bin4ry_v21 and LG-Viper-ICS-Root-tool with no luck. If i get it to run all the way though and reboot it still comes up without root and with no super user. I am starting to think I may have to find a way to downgrade it and root from there.....Did you ever have any luck?
Update:
Check out post 17 here
http://forums.androidcentral.com/lg-viper-4g-lte/253022-cannot-root-viper-ics.html
here is the link for LS840ZVI :https://docs.google.com/file/d/0BzPBX7oKPGLOcno0dFVNUXByMVE/edit
I've downgraded and rooted so far and its working, I may look for a rom before i upgrade again.
Confirmed above!
jared_schaefer said:
Im trying to root mine right now and can't seem to get it to work, I've tried Root_with_Restore_by_Bin4ry_v21 and LG-Viper-ICS-Root-tool with no luck. If i get it to run all the way though and reboot it still comes up without root and with no super user. I am starting to think I may have to find a way to downgrade it and root from there.....Did you ever have any luck?
Update:
Check out post 17 here
http://forums.androidcentral.com/lg-viper-4g-lte/253022-cannot-root-viper-ics.html
here is the link for LS840ZVI :https://docs.google.com/file/d/0BzPBX7oKPGLOcno0dFVNUXByMVE/edit
I've downgraded and rooted so far and its working, I may look for a rom before i upgrade again.
Click to expand...
Click to collapse
I can confirm that the above will work. I have a refurbished Viper from Sprint that I got because my 3G radio quit sending. It would receive great, but couldn't send any MMS or upload anything while on 3G. 4G was great, just no joy on 3G. Strangest thing. Anyway, got the phone replaced, and on the replacement was of course the dreaded unrooted ZVK. Gotta have my root back...
So I decided to try all this stuff out, and It worked.
To add a little further info, if you've got a relatively bare install of Windows, especially XP, you might need BOTH the VisualC++ Runtime Redistributables from 2010 (mentioned in the above thread) AND the one from 2008! If you don't have both, the LG FlashTool will not run. You can find them on Microsoft's site.
Once the flash tool has successfully downgraded your Viper, make sure you perform a factory reset, as indicated in the instructions for the FlashTool. Then use the "Activate" app to get your 3G/4G on. After that, set up your Google account under "Accounts and Sync" in "Settings".
I did the whole operation completely on a linux system, using a virtual machine running Windows XP for the FlashTool, then the bash script from here: http://forum.xda-developers.com/showpost.php?p=43530152&postcount=3253 with the v.31 rooting tool from the original post in that thread.
I had to edit the script in a very minor way, as was pointed out by its author, so it could find my adb command. I just placed the path to that command in the line that said:
Code:
for test_adb in "adb" "stuff/adb"
in the place of the first "adb", so I got:
Code:
for test_adb in "/home/user/android-sdk-linux/platform-tools/adb" "stuff/adb"
Make sure to replace "user" with your username, without the quotes.
Then I stuck the script in the same folder as the runme.bat file. After the script and root tool had done their work, my phone had rebooted a total of three times, and I had a perfectly functional Superuser app!
Huge thanks to LoveMyAndroid2010 in the post linked above. Great script - some love for linux!
Now to get RootKeeper and upgrade back to ZVK...
The aforementioned root method worked for me. Since I've rooted, I've compiled my findings into another thread. I haven't been able to unlock the bootloader yet, unfortunately.
how to upgrade LG Viper to Jelly bean or higher
After I root as per instructions, how can I upgrade the OS?
Please help. I'm a newbie and would appreciate any help you may offer. Haven't rooted any phone before.
For the last two years I have been going back and forth between my Note 2 that was Stock Rooted on 4.1.2 and my un-Rooted Note 2 fully stock on 4.4.2. Each had their advantages
I had all but given up
Now thanks to GhettoRoot I have the best of both worlds.:highfive:
I would like to hear what is COOL about having Root on 4.4.2.
You newbies to 4.4.2 check out the Active apps widget . it only takes up one space on the home screen. It is a must have.
Because of GhettoRoot XDA will need to redo Most of the Verizon Note 2 Forum. AdamOutler's Root is obsolete, Thanks for the good times Adam
doctor-cool said:
For the last two years I have been going back and forth between my Note 2 that was Stock Rooted on 4.1.2 and my un-Rooted Note 2 fully stock on 4.4.2. Each had their advantages
I had all but given up
Now thanks to GhettoRoot I have the best of both worlds.:highfive:
I would like to hear what is COOL about having Root on 4.4.2.
You newbies to 4.4.2 check out the Active apps widget . it only takes up one space on the home screen. It is a must have.
Because of GhettoRoot XDA will need to redo Most of the Verizon Note 2 Forum. AdamOutler's Root is obsolete, Thanks for the good times Adam
Click to expand...
Click to collapse
AdamOutler's Root is obsolete, Thanks for the good times
Click to expand...
Click to collapse
Adam has done A LOT for this community especially for Samsung phone in general.. His work is NOT obsolete and he still very involved on this forum. I am not friends with him or do I know him but he was the master mind behind unlocking/exploiting Verizons bootloader.. which currently on 4.3 and 4.4.3 is still not possible. This is most likely do to him not having the phone and the phones age..
SOo I hope I got the wrong impression from your statement.. Bc that man you mentioned.. Is a LEGEND.. Hands down
Just to confirm, Ghettoroot does not work on 4.4.2 baseband ND7. Is that correct?
Sent from my Galaxy Note 2 using Tapatalk
11/9/14 Update. I successfully rooted with GhettoRoot with Note 2 running Android 4.4.2 and baseband ND7 (Verizon). Required SDK install and Note 2 Android drivers for Windows first.
jtsmall said:
11/9/14 Update. I successfully rooted with GhettoRoot with Note 2 running Android 4.4.2 and baseband ND7 (Verizon). Required SDK install and Note 2 Android drivers for Windows first.
Click to expand...
Click to collapse
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Yes, that's it. Samsung's drivers work for me.
Sent from my Galaxy Note 2 using Tapatalk
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
crossing fingers
shissler said:
crossing fingers
Click to expand...
Click to collapse
woot woot im rooted..lol now what way to go
shissler said:
woot woot im rooted..lol now what way to go
Click to expand...
Click to collapse
I used it to replace the APN config file in my wife's phone for use on other carriers (T-Mobile & international use):
http://forum.xda-developers.com/showpost.php?p=57070787&postcount=7
It worked great for up to HSDPA+ speeds, but no LTE.. ..then she left the phone on top of her car; it fell off in traffic and got run over.. maybe this will help someone else!
Before it got smashed, I had planned on trying the following thread out next (for the VZW Note 3) to see if I could get LTE working on T-Mobile:
http://forum.xda-developers.com/showthread.php?t=2530523
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
nothing works for me.
I have Verizon Note 2 with version 4.4.2 and ND7
it says "error: device not found" 6 times
samloves said:
nothing works for me.
I have Verizon Note 2 with version 4.4.2 and ND7
it says "error: device not found" 6 times
Click to expand...
Click to collapse
I followed travis's post and mine is rooted now with superuser access.
My only question now is what method do we use to install twrp or cwm on this nd7 rooted note 2 with 4.4.2?
Can we use odin and just flash the latest twrp or is there another workaround?
zbomb5610 said:
I followed travis's post and mine is rooted now with superuser access.
My only question now is what method do we use to install twrp or cwm on this nd7 rooted note 2 with 4.4.2?
Can we use odin and just flash the latest twrp or is there another workaround?
Click to expand...
Click to collapse
In order to install a custom recovery, you have to have an unlocked bootloader. At this moment, there is no do it yourself method to unlock the bootloader on factory stock 4.4.2, so you can't install CWM/PHILZ or TWRP. For about $75 I think... you can send your phone off to a company that uses special equipment to downgrade your phone to 4.1.2... then you would be able to unlock the bootloader.... Otherwise, the most you can do right now is root the device and make modifications that don't require unlocked bootloader (e.g. debloat, install Xposed modules, etc...). An XDA user named Beastmode is working on trying to get a modified version of TWRP called Safestrap working for 4.4.2 which wouldn't require an unlocked bootloader, so you may want to keep an eye on that thread here: http://forum.xda-developers.com/showthread.php?p=57190369
Thanks for the reply. I figured that was the case. I had 4.1.2 a few days ago also and figured "hey, i haven't updated in over a year" and didn't read into it enough and then upgraded to stock ota 4.4.2 so that sucks. I guess I can live with it like this for now till a fix comes out if one does.
also having trouble
I also have been having trouble rooting my note2 with 4.4.2. I followed travis' approach and I got the 6 device not found errors. Am I not installing the correct drivers? Any help or information is greatly appreciated.
UPDATE: Just got it to work. Will post soon what I was doing wrong and what I did to correct it.
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
IceCo1d said:
I also have been having trouble rooting my note2 with 4.4.2. I followed travis' approach and I got the 6 device not found errors. Am I not installing the correct drivers? Any help or information is greatly appreciated.
Click to expand...
Click to collapse
for me a message came up on my phone asking for permission and then i was able to root after installing the drivers.
I just had to accept on my phone first for it to actually work.
popdevil said:
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
Click to expand...
Click to collapse
The part you are talking about does not come up until after the command prompt finds your device. Then you get the message to accept. That message came up the very first time but now it will not find the device for me to get to that part.
zbomb5610 said:
for me a message came up on my phone asking for permission and then i was able to root after installing the drivers.
I just had to accept on my phone first for it to actually work.
Click to expand...
Click to collapse
popdevil said:
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
Click to expand...
Click to collapse
I had similar issues with some of my trials.. ...try turning developer mode off and on, plug in and then give the phone 30-90 seconds or so for installer mode to time out and verify the device is in MTP or PTP mode.
Just rooted my Note 2 running 4.4.2
Ok gang, so after about a week of trying every method to root my phone I finally got it to work. I'm going to tell you what I was doing wrong and what you can check to see where you are messing up. Hope this helps someone.
The issue I kept running into was that my device could not be found. I would run Ghettoroot and it would just tell me error device not found. This made no sense because I could get Kies to work and the bubble in the lower right corner that says installing device drivers would always succeed. However if I went into Device Manager (on the computer) there was a little yellow exclamation point next to my device. After looking in to the properties it said there were no drivers installed.
Also if you open a command prompt and type "adb devices" (with your phone plugged in) it should show you your device, if nothing comes up then the drivers are not properly installed.
So... First check that drivers are properly installed in your Device Manager (again this is on your computer), and then open a cmd window and type adb devices to see if your phone shows up. If it does then you are ready to use Ghettoroot.
I used this Ghettoroot:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
and the drivers I used were called:
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0 (I can't remember where I DLed it from, sorry)
Also, if you are interested. My method for figuring out what was wrong started by right clicking on the GhettoRoot .bat file to see the sequence cmd commands. They began with adb commands and I then googled to see how to check that the command would work. That is when I stumbled on the comman "adb devices" to make sure my phone was properly connected.
I hope this helps someone and if I can help in any other way just ask!
Heimdahl? Odin?
mattnmag said:
In order to install a custom recovery, you have to have an unlocked bootloader. At this moment, there is no do it yourself method to unlock the bootloader on factory stock 4.4.2, so you can't install CWM/PHILZ or TWRP. For about $75 I think... you can send your phone off to a company that uses special equipment to downgrade your phone to 4.1.2... then you would be able to unlock the bootloader.... Otherwise, the most you can do right now is root the device and make modifications that don't require unlocked bootloader (e.g. debloat, install Xposed modules, etc...). An XDA user named Beastmode is working on trying to get a modified version of TWRP called Safestrap working for 4.4.2 which wouldn't require an unlocked bootloader, so you may want to keep an eye on that thread here: http://forum.xda-developers.com/showthread.php?p=57190369
Click to expand...
Click to collapse
I've only had this phone a week. My vs980 fractured :crying: now I'm stuck with this "thing" which I've done nothing with as I'm still trying to figure out WHAT never mind how. There's so much bloat I'm thinking AOSP. But how?
So far, ghetto-root hasn't worked for me but have removed Kaspersky etc to see if that was the problem. Then worry abt boot loader. Am on Pageplus Carrier so there wont be any OTA updates
Is there any merrit in the "Heimdahl" (??) method shown here CYANOGENMOD
I've read some of people using Odin to load pre-rooted stock image (and have found the images... but... )
I bricked the vs980 playing too fast and not waiting for answers. (learned a thing or 2 unbricking it)
So am I correct in understanding that you can no longer "Drop" an Un****** version of the factory image into the phone? By any means?
THANKS
VW
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
PariahNine said:
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
Click to expand...
Click to collapse
Given your firmware level:
- verify device is still rooted (use towelroot if needed)
- flash twrp recovery
- update bootloader to v3.2.3.2
- unlock bootloader (try 1-click method)
- flash rom of choice (Nexus, CM 11/12/13), SlimLP)
Search through the forums for relevant threads. Ask questions along the way. You have some work ahead (hours) but a nice reward at the other end.
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
PariahNine said:
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
Click to expand...
Click to collapse
Thoughts:
- moving roms between slots (specifically stock) via backup/restore is generally a bad idea in Safestrap; consider yourself lucky if you used this technique
- if the rom in the stock slot (assuming FireOS 13.3.1.0) boots properly then you can safely remove Safestrap v3 via the uninstall option in the apk
- do not wipe anything in Safestrap nor execute a 'factory reset' from the native Kindle recovery menu (bad outcomes)
- keep WiFi off / airplane mode engaged unless you are 100% sure the OTA block is working
- snag a copy of Flashify to install twrp and the 3.2.3 bootloader update
- check MD5 checksums with ES File Explorer or another tool before flashing; especially important for bootloader update!
- backup your existing recovery with Flashify before flashing twrp; leave a copy on the device
- enable USB debugging in Kindle settings (optional but offers additional recovery options should something go wrong)
- flash twrp first and make sure it works (reboot to recovery; have a look around but don't change anything)
- reboot FireOS and then use Flashify to update bootloader. Did I mention you should check MD5?
Post when above tasks are complete or if you have questions. Cover bootloader unlock next. Be aware the above steps carry some risk including permanently bricking the device. Make sure you have a clear understand on what is suppose to happen; double/triple check everything before committing changes. Good luck.
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
PariahNine said:
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Click to expand...
Click to collapse
- use the original apk to remove (uninstall) Safestrap v3 recovery; you do not need to uninstall the apk itself
- uninstalling Safestrap will not impact root
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
PariahNine said:
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
Click to expand...
Click to collapse
The FireOS version number will not change following bootloader update. It is a separate 'component' whose version can not be independently queried or verified. Typically the system (what you see, ie: FireOS) and bootloader are updated together and share the same version identifier. In this instance are only flashing the bookloader update as FireOS will soon be replaced by a different ROM. No need to update it and assume the associated risks.
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
PariahNine said:
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
Click to expand...
Click to collapse
Hum. Best handled by @draxie who developed 1-click. Generally pretty responsive to forum posts. If 1-click doesn't do it can always try the manual approach (a LOT more involved but not risky). Let's see what shakes out.
This is what I'm getting from the batch cmd window:
VirtualBox does not appear to be installed
Downloading 'https://www.virtualbox.org/wiki/Downloads' to 'C:\Users\Pariah\Down
loads\1-Click\1-Click\dwnlds'
Download complete.
Downloading 'http://download.virtualbox.org/virtualbox/5.0.12/VirtualBox-5.0.12-
104815-Win.exe' to 'C:\Users\Pariah\Downloads\1-Click\1-Click\VirtualBox-5.0.12-
104815-Win.exe'
Download complete.
Launching the VirtualBox installer momentarily
Please complete the installation with USB support enabled
Installation complete.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Virtual machine '1-Click' is created and registered.
UUID: 6b44be97-c931-47a5-8eeb-b780f5783b78
Settings file: 'C:\Users\Pariah\VirtualBox VMs\1-Click\1-Click.vbox'
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xf
fffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\Syste
m32\acaptuser64.dll: None of the 1 path(s) have a trust anchor.: \Device\Harddis
kVolume2\Windows\System32\acaptuser64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\ac
aptuser64.dll': rcNt=0xc0000190
Oracle VM VirtualBox Headless Interface 5.0.12
(C) 2008-2015 Oracle Corporation
All rights reserved.
Click to expand...
Click to collapse
And the 1-click instance in Virtual Box is showing "Booting the kernel."
Here is the method I used to block OTA updates.
Originally Posted by berndt_toast
Yeah, I agree. Staying rooted is difficult, but doable. I am still on the rootable version (13.3.1.0) and have stayed on it even through the OTA updates that have been released. I have stopped them from auto-applying (and from even being seen as updates) by doing the following:
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I also renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
Doing those prevent OTA updates from working and if you check for updates from the device, it says none are found (at least it has worked for me).
Click to expand...
Click to collapse
Do I need to undo this before proceeding with the bootloader update and unlocking?
PariahNine said:
Here is the method I used to block OTA updates.
Do I need to undo this before proceeding with the bootloader update and unlocking?
Click to expand...
Click to collapse
No - tasks ahead have no dependence on Amazon's update engine.
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
PariahNine said:
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
EncryptedCurse said:
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
Click to expand...
Click to collapse
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Davey126 said:
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Click to expand...
Click to collapse
If you want to give manual unlocking a try:
- use these drivers; you likely need to reinstall when flipping between adb and fastboot
- detail procedure
- suggest browsing this thread for additional info/tips. Lots of noise but some diamonds in the rough too
- careful not to go down a rabbit hole; some solutions are one offs that worked great for the poster due to their familiarity with a particular too, platform or technique
- unlike almost everything else with HDX you can not harm your device with bootloader unlock attempts. It will either work or not with no adverse consequences either way
There are a few excellent posts by @Cl4ncy, @jerryl and others (possibly one of mine) in different threads; unfortunately I wasn't able to surface them in a quick search. Nature of the HDX forums. A gold mine if information that is a bxxtch to access.
Before diving in you may want to flash CM11 or Nexus v4 which can be done with a locked bootloader. Both are rock solid KitKat based roms that will expose the full capabilities of your device and offer continuity to CM13 once unlocked.
Good luck.
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
PariahNine said:
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
Click to expand...
Click to collapse
Happy to hear you were sucesfull. Thanks also for sharing your experiences and insights. Should be helpful to others as they navigate through the process. Every nugget of new information helps!
BUild Number "rct6973w43-android6.0-v20-v1.16.30-e02"
kernel version 3.14.0+
wed nov 9 13:42:37 CST 2016
android security patch level june 1, 2016
android version 6.0.1
i heard someone tried rooting using the w42 root and bricked their's, so i'm reluctant to try it. any clues??
Same problem I bought this tablet at Walmart for 50 bucks and I tried a lot of rooting apps but still can't find anything that works without a computer and I definitely don't want a bricked tablet
did you try the kingroot thing?? or is that app only??
Guys, I'm sorry to say that the RCA Voyager III model RCT6973W43 cannot be rooted at this time. I tried running OneClickRoot to do this and it said it was impossible.
If you do this
https://www.reddit.com/r/tasker/comments/4zsi0e/project_share_toggle_settings_eg_location_mobile/
you can access a lot of unavailable settings as well as use immersive mode in everything including launcher.
MTRX2010 said:
BUild Number "rct6973w43-android6.0-v20-v1.16.30-e02"
kernel version 3.14.0+
wed nov 9 13:42:37 CST 2016
android security patch level june 1, 2016
android version 6.0.1
i heard someone tried rooting using the w42 root and bricked their's, so i'm reluctant to try it. any clues??
Click to expand...
Click to collapse
which w42 method are you refering to?
I have a root method thread out for w42 rca voyager with intel cpu. I also have instructions on the thread to NOT use if the version numbers do not match.
The only thing that should be different from the files provided on my thread and what you need , is your kernel. I have instructions on my github page. At the end of the instructions for root , are instructions to pull your boot.img.
If you follow along and are able to pull your images, I could make you the test files to try.
https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Have you unlocked the bootloader?
Augustoandro said:
Have you unlocked the bootloader?
Click to expand...
Click to collapse
Yes it is this command on mine. Not confirmed on the w43 model
Code:
"fastboot flashing unlock"
mrmazak said:
Yes it is this command on mine. Not confirmed on the w43 model
Click to expand...
Click to collapse
Which tool are you using?
Can adb be used instead?
Augustoandro said:
Which tool are you using?
Can adb be used instead?
Click to expand...
Click to collapse
Must be fastboot.
Often together with adb.
First enable "oem unlock" from the developers menu, (same menu you enable "usb debugging" from)
To get into bootloader mode on tablet, use adb. Then use fastboot.
Both from same terminal window on PC.
So like this
1. open cmd window(terminal on Linux)
2. Type "adb reboot fastboot"
Once in fastboot, if not already done, you will need to install drivers.
3. Optional, but recommended if you are unfamiliar . Type "fastboot devices" to verify properly connected to tablet.
4. Type "fastboot flashing unlock"
If anyone is still looking to root this tablet. It has been done on this thread
https://forum.xda-developers.com/android/help/how-to-root-rca-voyager-iii-model-t3602102
mrmazak said:
If anyone is still looking to root this tablet. It has been done on this thread
https://forum.xda-developers.com/android/help/how-to-root-rca-voyager-iii-model-t3602102
Click to expand...
Click to collapse
doesn't look like it's been, just looks like they got the bootloader unlocked, but i'm not finding anything
on the process to root the device, or a copy of the SU binary that needs to be installed to achieve root.
MTRX2010 said:
doesn't look like it's been, just looks like they got the bootloader unlocked, but i'm not finding anything
on the process to root the device, or a copy of the SU binary that needs to be installed to achieve root.
Click to expand...
Click to collapse
No it is not laid out , like . here do this ***, then copy this ***.
But the last step people needed for confirmation was proof of unlockable bootloader, then proof the patch tool I gave to the group , would work.
these things are shown in the thread, like I said. but just one user. and he immediately bricked the device. Just proof this chip / device is difficult to manage., but it can be done. But if you haven't figured out by the clues already maybe you shouldn't.
mrmazak said:
No it is not laid out , like . here do this ***, then copy this ***.
But the last step people needed for confirmation was proof of unlockable bootloader, then proof the patch tool I gave to the group , would work.
these things are shown in the thread, like I said. but just one user. and he immediately bricked the device. Just proof this chip / device is difficult to manage., but it can be done. But if you haven't figured out by the clues already maybe you shouldn't.
Click to expand...
Click to collapse
yeah im not good at making those elaborate android hacks work. i usually wait for a stable process before i make the attempt. i can adb, shell in, copy stuff over, and that's about it. ive rooted a number of devices, but i've only been able to do it once there's a reliable, concise method. the more steps-the more likely i am to screw it up.
I gave up on this tablet a while back, because it is aweful. it's so bloated the thing constantly stalls and chokes despite being a quad core atom. my guess is the code isn't even that well optimized. i found it a few days ago, and started playing with it again, then i remembered the thread on xda and the thread i started, but i checked my email, and didn't see a lot of notifications concerning the thread. come to find out ppl been working on it after all.
I got a dual core arm on a samsung lite 3, and it's way faster and slimmer. i haven't even bothered rooting it yet. but this RCA needs a lot of work, not just on the software end, but the hardware too. i gotta get in there and straighten out the crooked camera.
I used to be a windows coder way back in the ancient era of assembly language, but i don't know squat about these androids cept it runs on a linux kernel, and java bite code for the apps. ive never compiled anything for it before, but last i recall i was fixen to attempt compile my own SU binary since i couldn't find one for the atom arch on this tablet. -but i gave up on the tablet, and that's where i left off.
Ill give it a few more reads, and see if i can narrow down the process. if it looks more doable than a stroke of luck ill go for it. apparently there's multiple versions of this tablet, and if you try to do the roots from the RISC chip version of the voyager III you'll insta-brick your tablet, with no recovery. I've already seen a couple of people push the wrong root process on the device, and it got bricked beyond repair. 8(
mrmazak said:
No it is not laid out , like . here do this ***, then copy this ***.
But the last step people needed for confirmation was proof of unlockable bootloader, then proof the patch tool I gave to the group , would work.
these things are shown in the thread, like I said. but just one user. and he immediately bricked the device. Just proof this chip / device is difficult to manage., but it can be done. But if you haven't figured out by the clues already maybe you shouldn't.
Click to expand...
Click to collapse
Looking at this thread makes no sense what so ever, ive looked at it over 3 time and read the whole thing, judging by what has been said so far, it appears it hasnt been rooted, ive followed the whole thing, booting the generic cwm, dumped boot.img, unlocked bootloader, everything! Its not rooted what so ever from what i can see, unless im missing an ESSENTIAL step. Not new to rooting and android, ive messed about with it for a while now, so im just puzzled as to why i can figure this out, or maybe it wasnt ever rooted? Why mention it was? I have no idea! Anyways if it has then id like to be pointed in the right direction, if it hasnt, id be more than willing to help (intel atom voyager III).
I've been spending a good weekend on this trying to get my phone with Magisk.
I am currently trying to install Magisk on my Sony Xperia Z3C without rooting (I've successfully rooted the phone before, but no luck on full unrooting SU) so I am trying to install TWRP with ADB so I can flash Magisk.
I've tried the bare bones SDK tools provided on this site, Android Suite, YouTube videos but I can't seem to get it work even though it looks so simple.
So I finally threw in the towel for tonight and seeking assistance so I can go at it again tomorrow.
I've attached a screenshot of what I have been encountering for the past hours.
Thanks for your time.
Scottskyes said:
I've been spending a good weekend on this trying to get my phone with Magisk.
I am currently trying to install Magisk on my Sony Xperia Z3C without rooting (I've successfully rooted the phone before, but no luck on full unrooting SU) so I am trying to install TWRP with ADB so I can flash Magisk.
I've tried the bare bones SDK tools provided on this site, Android Suite, YouTube videos but I can't seem to get it work even though it looks so simple.
So I finally threw in the towel for tonight and seeking assistance so I can go at it again tomorrow.
I've attached a screenshot of what I have been encountering for the past hours.
Thanks for your time.
Click to expand...
Click to collapse
Did you try run command from folder where "adb" is placed. May be try run from cmd not from PowerShell
Why don't you use fastboot instead of adb to flash TWRP.img? you can also try Flashify but in my opinion manually via fastboot is more reliable
AutomaticSearches said:
Did you try run command from folder where "adb" is placed. May be try run from cmd not from PowerShell
Click to expand...
Click to collapse
I did but it didn't work. I might have encountered a path issue or conflicts with all the drivers I installed trying to get it to work.
Today I just wiped my windows and installed a fresh copy and instead of putting a ";" and adding the path, I just made a new one and moved it up. So far so good.
I hope nothing else happens.
Been hitting walls after walls trying to get Magisk on my Z3C.
P.S Windows 10 has Powershell and not CMD when I shift and right click.
Might be a new thing for this OS. I never really had to use command lines but I am too, use to CMD in other Windows version.
Rayan19997 said:
Why don't you use fastboot instead of adb to flash TWRP.img? you can also try Flashify but in my opinion manually via fastboot is more reliable
Click to expand...
Click to collapse
I am a total greenhorn.
I will give that a whirl if this method I am following doesn't work. Thanks!
Alright let me know