Related
Please help me root this device. I have only ever done my Gs2 a few times with flashing etc, so am basically a complete noob.
I have tried for the last couple of hours and am wanting to go mad. I have followed all the lines about unlocking the device and the fastbook oem unlock, But all it ever tells me is waiting for device. Im guessing im missing drivers, but I have dont the samsung drivers a couple of times, and unzipped and followed the instructions.
Any easier to follow guides or info out there that can help me?
When I plug the phone in to unlock it, i dont get the usual ding from windows, i just get a little thre dings like it doesnt know what it is.
please help. Thanks....
Ps, sorry if I am being stupid or cluttering the forum. cheers..
No help out there at all???
If any one can I will be so grateful, Or if anyone is near to welwyn garden / st albans maybe youd fancy rooting 2 of these nexus' for me and il give you a drink?
Thanks..
Look in the development forum:
http://forum.xda-developers.com/showthread.php?t=1352413
Install the android version of pdanet on your PC... it will uninstall but will leave the drivers you need.
kravevr6 said:
No help out there at all???
If any one can I will be so grateful, Or if anyone is near to welwyn garden / st albans maybe youd fancy rooting 2 of these nexus' for me and il give you a drink?
Thanks..
Click to expand...
Click to collapse
Haven't rooted mine yet, I'll be doing it at the weekend. Had loads of issues with the drivers when I rooted my Nexus S. In the end I installed PDA net on my PC - the drivers installed with that worked fine (you don't actually use PDA net thereafter) Not sure if this works with the GN but you will not do any harm trying it.
Sent from my Galaxy Nexus using XDA App
jaketurbo said:
Look in the development forum:
http://forum.xda-developers.com/showthread.php?t=1352413
Install the android version of pdanet on your PC... it will uninstall but will leave the drivers you need.
Click to expand...
Click to collapse
Beat me to it
Sent from my Galaxy Nexus using XDA App
Cheers guys, Im so new to this, its so frustrating. Its got to be a driver issue. My comp reconises the phone when its on, but when its in bootloader mode, windows is giving me three dull bells when connecting the device....
will have a look at the other thread, Have already read that one I think, and looked so foreign to me!!! lol
I cant pst in the other thread, but have downloaded and installed pda net for android, and when it gets to installing the drivers from the phone, it does it all, ie galaxy nexus , the other driver that i cant remember and the galaxy driver is not installing. Even gone two miles down the road and got a different laptop. no matter what I download or ty and install it just dnt do it.
can some one either make a real simple idiots guide for me the idot, or locally please let me pay you a small fee to root these two phones. Im almost in tears after 5.5 hours of constant crap and pathetiness.
Wishing right now i had not bthered with these phones. At least my s2 and flashing was simple.
It says "waiting for device" because for some crazy reason when you are in fastboot mode Windows (which is what I'm using) uses a different USB driver than when you are in "normal" usb connect mode.
What you need do to sort it out is to go to Device Manager and change the driver to use the Samsung instead of whatever crazy one Windows has decided to use. Then you can carry on with doing the bootloader unlocking.
kravevr6 said:
I cant pst in the other thread, but have downloaded and installed pda net for android, and when it gets to installing the drivers from the phone, it does it all, ie galaxy nexus , the other driver that i cant remember and the galaxy driver is not installing. Even gone two miles down the road and got a different laptop. no matter what I download or ty and install it just dnt do it.
can some one either make a real simple idiots guide for me the idot, or locally please let me pay you a small fee to root these two phones. Im almost in tears after 5.5 hours of constant crap and pathetiness.
Wishing right now i had not bthered with these phones. At least my s2 and flashing was simple.
Click to expand...
Click to collapse
Ok so what have you done so far?
You have the pdanet drivers installed on your pc?
You need to boot into fastboot mode to install the driver you need to root your phone.
*THIS* guide will explain what adb and fastboot are exactly.
*THIS* guide will show you how to set up adb and fastboot.
When unlocking the bootloader you will need the file fastboot.exe which you can put in the root of your c drive for easy access. The atteached file needs to be renamed from .zip to .exe as you cant attach .exe files in xda.
If you have any more questions then just ask .
Mark.
ok..... having gone through similar a few minutes ago.
The drivers kept saying that they had failed to install. kept trying over and over.
then i twigged:
1) made sure debugging mode was on
2) Rebooted the unit into bootloader mode - suddenly the adb driver installed successfully doh !
wonder if this is the same issue you are having ... the adb drivers only install successfully once the nexus is connected via usb and in bootloader mode
of course you may know all that already but it had me stumped for a while
Thank you guys, some good info and detailed posts, which is what I was hoping for! I'm in bed now, but will give this a blast and report back tomorrow!
Really appreciated!
Thanks .......
Sent from my Galaxy Nexus using Tapatalk
Big thanks to everyone. Woke up with a clearer head and proceeded to try again. Done as wilbur said and installed drivers in recovery mode. And perfect.......
after so many problems all was sorted. Then used superboot, and all was ok. 2 galaxy nexus's rooted. think the lesson learnt is to walk away instead of furiously trying things.
Cheers for all the input. What a easy methd ONCE all the drivers are there!!
Cheers people
Glad you got it sorted
I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer
Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.
I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app
Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little
Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT
Hello Everyone,
new member and first time poster here! What a community!
I've run into some serious battery drainage after installing 4.1.2 on my AT&T Note II; the battery will sometimes drain 15-20% an hour in standby mode, sometimes less but still drastically worse than before the updates when I'd get a solid day and a half. It seems to think that the SD card is constantly ejecting and so it will remount periodically-- this, I'm sure, is the chief issue. After browsing around here and googling for a couple hours last night, I've seen various "fixes" involving my external microSD card, but none of them seem to help.
Anyway, I've been wanting to root and flash a custom ROM for a while now, but have been lazy; alas, I am finally compelled to do it today. This all brings me to my question:
Why won't Win 7 recognize my note II? I know there have been many posts here at XDA regarding the terrible samsung drivers etc., yet everyone seems to be rooting their noteII, sIII etc. just fine! I've installed the correct drivers, rebooted a couple time-- nothing! I'm hoping this issue has been resolved and I'm just overlooking the thread... can anyone provide any insight? Can't wait to root my first phone!
Thanks in advance
20% per hour on standby is a ridiculous amount. .
Did you take an OTA to update the device ??
Either way. ..
That level of drainage needs a fresh start. ..for sure. .
I would consider pushing a rooted stock build via Odin first. ..to confirm your device is okay.
Verify your driver package and download Odin for the test. ..
You need to track the battery drain issue first. ..imho
gregsarg said:
20% per hour on standby is a ridiculous amount. .
Did you take an OTA to update the device ??
Either way. ..
That level of drainage needs a fresh start. ..for sure. .
I would consider pushing a rooted stock build via Odin first. ..to confirm your device is okay.
Verify your driver package and download Odin for the test. ..
You need to track the battery drain issue first. ..imho
Click to expand...
Click to collapse
solid-- that's exactly what I'll do.
Btw, maybe 15-20% is a bit inflated; that is how it feels though, I haven't really kept track or checked. I just noticed a big difference and, one morning after having snoozed my alarm on the phone, unplugging it and gone back to sleep, my fully charged note was at 80% when I opened my eyes, maybe a couple hours later. I do have odin installed but how am I to do any of that if the phone isn't recognizable?
sorry for the silly questions; I'm brand new to odin and all of this mind you-- am i missing something here?
oh, and yes- the update was OTA
With Odin...be sure you have the drivers installed and your phone is in download mode.
wahbob said:
With Odin...be sure you have the drivers installed and your phone is in download mode.
Click to expand...
Click to collapse
my phone was definitely in download mode (held vol down, power, and home).
I guess im just not sure how to install drivers with odin. I just downloaded the samsung mobile device usb drivers .exe and ran it... thanks for the reply.
Yes...download mode on the device...
If your PC drivers are set up properly....you wont have any trouble with the device being recognized.
It sounds like the drivers are messed up still....g
Edit :
Pull the drivers from the development section under the "everything" thread...and not from the general internet or kies..
and if you have kies installed....dump it....g
gregsarg said:
Yes...download mode on the device...
If your PC drivers are set up properly....you wont have any trouble with the device being recognized.
It sounds like the drivers are messed up still....g
Edit :
Pull the drivers from the development section under the "everything" thread...and not from the general internet or kies..
and if you have kies installed....dump it....g
Click to expand...
Click to collapse
went to the development board and found this thread http://forum.xda-developers.com/showthread.php?t=1987541 which just links to samsung's official site from which i downloaded my presumably faulty drivers.
hexagondun said:
went to the development board and found this thread http://forum.xda-developers.com/showthread.php?t=1987541 which just links to samsung's official site from which i downloaded my presumably faulty drivers.
Click to expand...
Click to collapse
Are you running an anti-virus program on your PC ?? I assume yes, and depending on the maker of the AV package, the program may interfere with the drivers being installed properly.
AV programs often bind critical steps in the function of drivers and views them as unsafe...
Try disabling the AV program while downloading and installing the Drivers from samsung.....g
gregsarg said:
Are you running an anti-virus program on your PC ?? I assume yes, and depending on the maker of the AV package, the program may interfere with the drivers being installed properly.
AV programs often bind critical steps in the function of drivers and views them as unsafe...
Try disabling the AV program while downloading and installing the Drivers from samsung.....g
Click to expand...
Click to collapse
well, rather than disabling, I completely uninstalled my antivirus software, then uninstalled the drivers, rebooted, reinstalled the drivers, rebooted again, and still the pc wont recognize the phone. tried it on my father's windows machine with the same results. I have never had such a hard time with drivers in my entire life. What a frustrating process!
any other suggestions?
Odublica singularly
Try a different cable.
hexagondun said:
well, rather than disabling, I completely uninstalled my antivirus software, then uninstalled the drivers, rebooted, reinstalled the drivers, rebooted again, and still the pc wont recognize the phone. tried it on my father's windows machine with the same results. I have never had such a hard time with drivers in my entire life. What a frustrating process!
any other suggestions?
Click to expand...
Click to collapse
SXBB said:
Try a different cable.
Click to expand...
Click to collapse
Agreed......
The OEM cable is preferred....g
SXBB said:
Try a different cable.
Click to expand...
Click to collapse
+1
And also what he said^^^^^^
I'll add this, if still not working then try another usb port or another computer...
It may help!
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
BACARDILIMON said:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
etawful said:
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
Click to expand...
Click to collapse
I wasn't initially, but I did switch to it last night. Still no go.
I suspect it's either the phone itself (see above: re suspected hw failure), or the PC in question (nVidia chipset on this old motherboard, and I've had more than a few problems with adb talking to phones on nVidia motherboards). I'm going to try Bacardilimon's suggestion tonight, on a PC that has *nothing* nVidia-related in it, before I throw in the towel. As it is, the failing phone needs to be back to TMO by the middle of next week, so I'm all but out of time to resolve this.
Drake Maijstral said:
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
Click to expand...
Click to collapse
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
BACARDILIMON said:
httx://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Toneman07 said:
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
Click to expand...
Click to collapse
I'd consider doing that, except as I mentioned, the G3 in question disconnected during a run of Flashtool, rendering it without a working OS to boot to. The phone now boots straight to download mode. The good news is, it's now officially unrooted. The bad news is, it's also officially bricked until I can get an OS flash to work.
Drake Maijstral said:
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Click to expand...
Click to collapse
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
BACARDILIMON said:
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
Click to expand...
Click to collapse
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Drake Maijstral said:
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Click to expand...
Click to collapse
See we agree.
NOTE 4
BACARDILIMON said:
See we agree.
NOTE 4
Click to expand...
Click to collapse
Not likely.
In any case, it failed again. The video he did gave me the exact same steps I followed elsewhere, and unsurprisingly, it failed with 'We can't communicate with Phone', after beginning the flash process. There is something else wrong here, though I'm not certain if the failing phone is at fault or the PC in question is causing the issue. To be crystal clear, the flash process starts, and then, at a random point during the flash, it completely stops, and Flashtool eventually gives up and throws the aforementioned error.
Any other ideas? If not, I'm going to have to try another PC to rule that out as the culprit. Sigh.
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Toneman07 said:
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Click to expand...
Click to collapse
Nope, the phone is definitely not doing anything - the usb animation on the G3 completely stops before Flashtool throws the error.
And damnit, quit reading while driving. You can do that later.
Moved the hdd Windows is installed on to another PC with a different chipset. After it updated drivers, I tried again. Flash proceeded partway, then died. Reset phone, Flashtool reststarted flash from scratch, flash died at 15%.
15% is interesting. While I've seen the flash die at various points, 15% is the one that was most often repeated. This tells me the failure follows the phone, not the PC - which makes sense, as the phone has a suspected RAM failure.
At this point, it appears that flashing this phone is impossible due to faulty hw. Hopefully TMO (and eventually, LG) will accept the faulty phone back with no OS, because there's no way an OS is being written to this device ever again.
Thank you for answering
yanowman said:
Thank you for answering
Click to expand...
Click to collapse
No problem. There's nothing I hate more than stumbling across a thread where the OP has the same problem I have, only to find it was never updated with the solution.
Good luck man let us know what tmobile says
So I created this topic because there is hardly anything on the internet regarding this tablet. I just recently purchased it from Best Buy and it took me quite some time to find something that would help me root it. Finally, I tried vroot ( a rooting application) and I succeeded in rooting my tablet. I don't have the exact link I used to get vroot but a simple Google search should suffice. Anyway, I figured I'd start this topic for anyone and everyone who uses this tablet or knows of this tablet to discuss any other developments. For now, if anyone needs help rooting their tablet and getting superuser running, I'm here to help.~
For now, I hope you all can figure out how to use vroot (yes, I know it's in Chinese. I can not read Chinese but it was pretty simple to get through the process of rooting.) Anyway, I don't remember the specifics but if anyone else gets through it, I ask that you please post some details on how you did it for everyone else to get through it as well. Hopefully, with time, we can get some good stuff going with this tablet. Could anyone figure out how to get CWM Recovery running on it? I'm a bit new to this and I don't want to screw anything up.
Thanks for the heads up! I also bought this tablet about a month ago. I was impressed with how thin and light it was, and how nice and bright the (IPS) screen was, especially for a cheaper "no-name" tablet. I've since found virtually no online support for this. D2 didn't even seem to list it on their own website. Although, finally today, I found this thread, and this site: http://www.d2pad.info/index.php?option=com_content&view=frontpage&Itemid=585. Seem the model is exclusive to Best Buy.
The only problem I've had with this tablet is that on rare occasions, if the screen is left on too long, the touch controls go a bit haywire, detecting random touches all over the place, and not really responding. Simply turning the screen off and back on fixes the problem. (Also, the camera is kind of ****ty, but I don't really care about that)
Anyhow, I'll definitely be trying to root this tomorrow. I take it you didn't need any special drivers? I came across this (http://scottyzone.com/2014/03/17/connect-the-d2-961g-to-adb-using-google-usb-drivers/), which I'll try if I can't get the tablet connected to my computer properly to run Vroot.
Thanks!
arpitp said:
Thanks for the heads up! I also bought this tablet about a month ago. I was impressed with how thin and light it was, and how nice and bright the (IPS) screen was, especially for a cheaper "no-name" tablet. I've since found virtually no online support for this. D2 didn't even seem to list it on their own website. Although, finally today, I found this thread, and this site: http://www.d2pad.info/index.php?option=com_content&view=frontpage&Itemid=585. Seem the model is exclusive to Best Buy.
The only problem I've had with this tablet is that on rare occasions, if the screen is left on too long, the touch controls go a bit haywire, detecting random touches all over the place, and not really responding. Simply turning the screen off and back on fixes the problem. (Also, the camera is kind of ****ty, but I don't really care about that)
Anyhow, I'll definitely be trying to root this tomorrow. I take it you didn't need any special drivers? I came across this (http://scottyzone.com/2014/03/17/connect-the-d2-961g-to-adb-using-google-usb-drivers/), which I'll try if I can't get the tablet connected to my computer properly to run Vroot.
Thanks!
Click to expand...
Click to collapse
Thank you for bringing some needed attention to this topic! I actually used the Vroot application, rather than the software. It took a few tries but I got it to work. If you want to try the software, however, I've connected it to my computer numerous times without the need for any special drivers. Only thing I can suggest is the generic google drivers. By the way, I reverse searched the tablet's hardware and kernel and came across a duplicate device from China. It is exactly identical right down to the appearance, hardware and software to our tablet. It is called the Chuwi VX8 and the only difference is that it comes in white rather than black.
After making this discovery I came across a nice little development topic for the clone device (http://www.freaktab.com/showthread.php?16025-Chuwi-VX8-RileyROM-1-1) and it seems they've founded good amount of research into the tablet. They've come up with a rom (I've yet to test), CWM Recovery (Unable to flash. If anyone else can try, that'd be dandy.), root methods (with links), among other things. It seems that anything that would work with the Chuwi tablet SHOULD work with the Digital2 Platinum Pad 8. The same rooting method was required and everything about the two tablets is perfectly identical so I'm led to believe they're going to be able to use identical roms or recoveries. I'll look more into flashing CWM Recovery tonight and get back to you on my results.
Josh8550 said:
Thank you for bringing some needed attention to this topic! I actually used the Vroot application, rather than the software. It took a few tries but I got it to work.
Click to expand...
Click to collapse
Which app exactly are you referring to. I thought it was something in the Play Store, but no luck finding what you're referring to.
arpitp said:
Which app exactly are you referring to. I thought it was something in the Play Store, but no luck finding what you're referring to.
Click to expand...
Click to collapse
Found this link (http://products.mgyun.com/api/downjump?id=846) just for you. It should work but let me now whether or not it does. It's the exe for computers but if it doesn't work Google "vroot apk" for the app.
Josh8550 said:
Found this link (http://products.mgyun.com/api/downjump?id=846) just for you. It should work but let me now whether or not it does. It's the exe for computers but if it doesn't work Google "vroot apk" for the app.
Click to expand...
Click to collapse
As you mentioned, the link was for the (Windows) software. It requires ADB connection to a computer (usually requires special drivers).
When you said you used the application instead of the software, I assumed you used an APK. However, there is no apk of (the official) Vroot (it was designed to work through Windows). That makes me think the root app you used was something else. So I have to ask... what did you use to root this device?
vRoot is now iRoot
First off, I'd like to thank you for starting this topic. I've searched all over since I bought this tablet a couple of months ago but couldn't find any information. When I did a google search for vroot, i found http://www.mgyun.com/en/getvroot and the software is now called iRoot, and is in english. The main link on the page is for the windows ADB version, and there's a link further down the page for "iRoot for Mobile", which will give you the APK. Now that I've got root, I'll keep trying to get CWM recovery to work, and maybe we can start seeing some ROMs come out for this great device!
UPDATE: (IMPORTANT, please read): The APK does not work. or at least, I couldn't get it to work on my device. It tells you that you've got root, but doesn't really give it to you. Download the computer based exe from the link that Josh8550 posted earlier.
You will need developer permissions (Settings -> About Tablet -> tap Build Number until it tells you you're a developer).
Install ADB and Drivers on windows PC (http://forum.xda-developers.com/showthread.php?t=2588979)
Connect tablet to PC with USB cable.
Run vRoot (iRoot) on PC. Program will connect to tablet and check for root.
Click the "Get Root" button.
Wait...
Tablet will reboot.
Wait...
Program will connect to tablet and check for root.
Program should verify that you have root.
Download and Install SuperSU from the Play Store.
Open SuperSU and Update SU Binary. You will have to give SuperSU root permissions from the chinese interface (choose the box on the right, don't mark the check box).
Reboot.
Congratulations! You now have root access. Enjoy!
More info to come later...
nahrwoldinternet said:
First off, I'd like to thank you for starting this topic. I've searched all over since I bought this tablet a couple of months ago but couldn't find any information. When I did a google search for vroot, i found http://www.mgyun.com/en/getvroot and the software is now called iRoot, and is in english. The main link on the page is for the windows ADB version, and there's a link further down the page for "iRoot for Mobile", which will give you the APK. Now that I've got root, I'll keep trying to get CWM recovery to work, and maybe we can start seeing some ROMs come out for this great device!
Click to expand...
Click to collapse
Thanks man. I couldn't find the link to the apk again so that's a huge help for everyone here. I'll try to get CWM recovery working soon then I'll see about getting Cyanogenmod 11 ported over.
Rooting Digital 2 tablets
Hey everyone.
I successfully rooted with Kingo ROOT using my PC, however now Im stuck. Cant seem to find ROMs or Mods compatible with this tablet.
Any info out there would be great. Im running a 4.1.1 Jelly Bean.
Rooted now what?
Did you ever try the cwmr or cyanogen ROM you had mentioned above?
[email protected] said:
Did you ever try the cwmr or cyanogen ROM you had mentioned above?
Click to expand...
Click to collapse
I did, and ended up hard bricking it for months until I finally got it back out, fixed it and gave up.
I also have the D2-861G and ended up bricking it but have been unable to fix it, would you mind telling me how you got it back up and running.