Develop Bugs

[Q] AlpharevX, not working... [SOLVED]

Ok I'm a HTC noob so please bear with me. I setup adb-sdk environment and windows environment variable. After that I obtained Alpharevx and ran it. Everything went fine and I entered the beta key. But then after
'Beta key accepted - thank you for participating!'
, nothing happens. It just stops. Any idea how to get this thing going?

Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/

JWhetstone02 said:
Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/
Click to expand...
Click to collapse
Thanks
Yes my phone is frogyo.
Yes it's in USB debugging mode.
Yes ran as an admin because I disabled the protection so basically all apps as admin on my windows 7.

I've read in the AlphaRevX thread where some people have had to do it multiple times before it Roots their phone. Maybe try that?

Thank you. I will try more :O I hope this won't brick my phone. I heard HTC devices can't recover from brick. With SGS you could just odin back from whatever mess you are in.

Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk

Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement

4GivenByChrist said:
Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.

Hey, so I am new to this board. I myself have a Dinc2 arriving soon. My brother just got his. We are both former fascinate owners. After researching and following some how to's, my brother was rooting his phone and he got stuck while attempting to get recovery after S-off. He cannot post, but here is what stated happened:
Hey I'm having a problem with my incredible 2.
Before activating the phone (avoiding the 2.3 update) I tried rooting my phone.
1) I downloaded alpharedex and generated the code
2) downloaded the recovery mode application onto the phone
3) and placed the SU zip folder onto my phone
I was stopped at step 3 because the volume down power button procedure was not working. Instead the phone powered on normally. I attempted it many more times and it would not work.
After spending some time on it, I said screw it, I just want to use the phone. So i activated it and OK'd the 2.3 update. It shut down my phone and began to download the file but it was stopped with a exclamation point in a red triangle. I tried doing a hard reset (volume up and power button) but that did not work. So i was forced to take out the battery. When I powered up the phone again, it continued the download: the phone shut down, it began to download and froze up like last time.
Click to expand...
Click to collapse
Okay, so yes I know he shouldn't have done this. After consulting with me, I was able to get him into recovery by attempting the volume down + power procedure about a dozen more times.
Should he install the super user package and reboot? Or should he do something now to fix the OTA auto reboot problem while he still has recovery?
Edit: Because he is in recovery, could he just factory reset and flash a new rom? Apparently, when he boots the phone normally it gets to the home screen and then instantaneously reboots and attempts to install the OTA. That is where it locks up.

If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.

k_nivesout said:
If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.
Click to expand...
Click to collapse
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk

deaffob said:
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.
Click to expand...
Click to collapse
You have it working yet? If not I would uninstall the drivers you got and then download and install HTC sync. Then uninstall just htc sync leaving your drivers. Then try again. That wokred for me when I was unlocking a friends phone.
Sent from my Incredible 2 using Tapatalk

deaffob, you seem to be pretty computer literate, if it keeps giving you issues, boot ubuntu from a flash drive and do it that way. I messed with windows for a couple hours, and it took me all of 20 minutes to install ubuntu to my flash drive, boot into it and root.

bik2101 said:
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.

I fixed it by going to alpharev IRC and got a great help from attn1! He was very helpful late at night.
To those of who'd like to know, this was my situation:
-Windows 7 64bit with admin control turned off=everything has admin rights.
-Fastboot off(tried on too)
-installed HTC Sync's driver.
-tried HTC driver that's posted on AlpharevX's website.
-HTC Sync was uninstalled.
-It was froyo
-Correct HBOOT(obvious because the whole point of getting the beta key was to prevent someone using the hack with the wrong version of HBOOT)
-Tried 3 different USB ports.
-ADB SDK was installed
-JDK was installed
-environment variable path for ADB SDK was set.
-tried reinstalling the HTC Driver twice, each time uninstalling with Revo Uninstaller to clean up registry.
So even after all these, the hack still did not work. So attn1 suggested that I should try it different computer or download the flash version of Ubuntu and try it in there. I tried it on my old lap with Windows 7 64 installed. I haven't used the laptop that much so the Windows was pretty clean and new.
It worked on that laptop. The lesson is, no matter how much you take care of your windows system, I practically baby my computer and do everything to keep the optimum performance, it will get screwed up after some time. I would've never thought that it'd be my desktop Windows that was the problem.
So if you are having a problem, please try Ubuntu as that's probably the best bet.

PeterGunz said:
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.
Click to expand...
Click to collapse
but there's still the problem of not being able to turn fast boot off, which i think is needed to be able to get into recovery..

get into recovery
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.

JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
+1
Yep! And I'm happy I made the switch, the SLCD screen is not bad and has more accurate color reproduction and plus who uses the SAMOLED at 100% brightness anyways..-nobody really lol.
Also HTC sense imho is waay more useable with good functionalities like the ever so good integration of Facebook compared to TW. I still can't get over that since I was conned into thinking that the Fascinate had in-app pictures but atlas it was a link to the website.. whereas HTC has that and more plus notifications!
Sorry I'm just thoroughly impressed especially since this is my first HTC Device. ^__^
Plus the rotating capacitive buttons is just super cool... :3 Now to make it work when using the camera app... >.> Anybody know if this mod exists yet?
Sent from my ADR6350 using XDA App-Dinc2 switched from a Fascinate.. :3

michaelbsheldon said:
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.
Click to expand...
Click to collapse
You can download a program from the Market called quickboot It allows you to reboot into recovery without doing a battery pull. this is what I use right now in replace of the 4-in-1 reboot menu

I just got su on mine. I am an Android beginner so my experience may help. My system is a laptop running Win 7. I had installed synch and then following advice removed it with all drivers. I installed the htc USB drivers, and plugged in the phone in the proper mode. AlphaRevX will not work. So (this may be vital) reinstalled synch with drivers. Then removed synch. Got AlphaRevX to do its thing at once. So the other drivers must be there!

Trying to Root - Driver install issue

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

[Q] [x-post from LG G3] D851 unroot / restore to stock

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

[Q] Rooting Help? USB Not Working In Download Mode

I have a Sprint Samsun Galaxy Note 4, in the USA. I'm trying to root my device - I've read online tutorials, watched videos, and it doesn't seem to be working. Here's what happens:
1. Downloaded CF Auto Root for my device, unzipped it.
2. Set up ODIN.
3. Set phone to download mode, plugged in to PC.
4. Did not see the blue light, figured I didn't have the right drivers.
5. Turned phone back on, and noticed that ODIN light now works (as do file transfers), but downloaded new drivers anyway.
6. Uninstalled old drivers, rebooted.
7. Installed new drivers, rebooted.
8. Placed phone in download mode again, same issue.
Any ideas?

Did you wait a couple of minutes between steps 3 and 4 before giving up. I just re-did this last night; I didn't time it but my PC must have taken a minute to show COM to be ready to start Odin on the stock tar.
I was also having USB driver issues and reinstalled. My PC has been having USB issues in general with Windows 8.1 updates; had to uninstall and reinstall the same PC generic USB driver. Circa 2009 era PC needs an overhaul or replacement.
BTW, if you're using an older CF Auto root, CF went back to Odin 3.07 and updated to superSU v2.45

I did, because I was unsure what was going on. This is only the second time I've rooted a phone, so I was unsure what would happen if I pulled the battery. I think I waited about 20 minutes while looking online to figure out what was going on.
I'm not sure what you mean by an older version. I downloaded the version for my phone from chainfire.eu

http://redirect.disqus.com/url?url=...&thread=3459253652&zone=thread&area=discovery
http://redirect.disqus.com/url?url=...&thread=3443914612&zone=thread&area=discovery
Some questions I should have asked earlier: USB debugging enabled? Using USB 2.0? Tried different USB cables?

Yes, device debugging is enabled. First thing I did on my phone after activation =)
I'm not sure how to tell if I'm using USB 2.0 or 3.0.
I did try a different cable. I don't think the cable would be the issue since it works when the phone is on normally, though?
I'm going to follow the troubleshooting guide in the links you posted, see if that helps =)

Yes, device debugging is enabled. First thing I did on my phone after activation =)
I'm not sure how to tell if I'm using USB 2.0 or 3.0.
I did try a different cable. I don't think the cable would be the issue since it works when the phone is on normally, though?
I'm going to follow the troubleshooting guide in the links you posted, see if that helps =)
PS. Did you use Kingo to root your note 4? I might give it a try.

No, I just posted links for the thoroughness of checks. I used CF Auto root. Good luck.

Did not work either. It DOES say I'm connected, went through the reboot, but then just starts over again. /sigh

I'm thinking the MTP might be the issue, but I don't seem to have a MSD option on my note 4?

Any more ideas?

What Windows version are using? If it's 8.1, has it been updated? There was a USB 2.0 update that fixed some devices reporting as compatible greater than 2.0 but not handled correctly by Windows 8.1 but was OK with Windows 8.0 and below. Windows 8.1 got an update July, 2014, that should have fixed that but not all were fixed; there's a link for reporting exceptions with a log but I'm not sure that applies to you.
Have you tried using the USB port on test of PC case?
Maybe being more specific about your PC and what you've tried would help.
From there, if anyone else has some suggestions, please advise.

faile486 said:
I have a Sprint Samsun Galaxy Note 4, in the USA. I'm trying to root my device - I've read online tutorials, watched videos, and it doesn't seem to be working. Here's what happens:
1. Downloaded CF Auto Root for my device, unzipped it.
2. Set up ODIN.
3. Set phone to download mode, plugged in to PC.
4. Did not see the blue light, figured I didn't have the right drivers.
5. Turned phone back on, and noticed that ODIN light now works (as do file transfers), but downloaded new drivers anyway.
6. Uninstalled old drivers, rebooted.
7. Installed new drivers, rebooted.
8. Placed phone in download mode again, same issue.
Any ideas?
Click to expand...
Click to collapse
Press volume up to confirm download mode?

rawintellect said:
Press volume up to confirm download mode?
Click to expand...
Click to collapse
Yes, that has to be done to get to download mode? I'm at the screen where it says 'Downloading...Do not turn of the target!!'

faile486 said:
Did not work either. It DOES say I'm connected, went through the reboot, but then just starts over again. /sigh
Click to expand...
Click to collapse
I'm sorry but I don't recall seeing this reply because I don't understand it now. I may have overlooked it?
Are you saying the phone appears to download but boot loops? You should see success and 0 failures prior to auto boot. Is that the CF Auto root flash in Odin or another Odin flash like recovery or stock tar? If that's happening, did you try to pull battery and delete cache and dalvik cache in recovery? Is the phone semi bricked or just not rooted? Can you Odin the recovery tar for TWRP recovery? If so, you could just flash the superSU zip file in TWRP.
http://download.chainfire.eu/supersu
Another suggestion, if you're getting anywhere with Odin, you should close and reopen Odin if doing multiple flashes. Close after each flash; i.e., power down, flash stock tar, close Odin, open Odin, flash CF Auto root, close Odin, flash recovery (download mode steps omitted since you know that already).
Again, someone might could help with detailed setup details and steps taken. Sorry if I'm not following well; I'd like to help, if possible.

samep said:
What Windows version are using? If it's 8.1, has it been updated? There was a USB 2.0 update that fixed some devices reporting as compatible greater than 2.0 but not handled correctly by Windows 8.1 but was OK with Windows 8.0 and below. Windows 8.1 got an update July, 2014, that should have fixed that but not all were fixed; there's a link for reporting exceptions with a log but I'm not sure that applies to you.
Have you tried using the USB port on test of PC case?
Maybe being more specific about your PC and what you've tried would help.
From there, if anyone else has some suggestions, please advise.
Click to expand...
Click to collapse
I'm using Windows 7. Using another PC is a good idea, I'll try that.

faile486 said:
I'm using Windows 7. Using another PC is a good idea, I'll try that.
Click to expand...
Click to collapse
Didn't realize the auto correct suggested wrong word. I meant rear USB of PC case but trying another PC is also suggested.
Windows 7 means most of my suggestions regarding the drivers may not apply to you. Off topic: upgrading to Windows 8 from Windows Vista had me searching for needed applications and tools omitted from Windows 8. Windows 7 is more developer ready than Windows 8. Simply rooting should be OK with either version as long as drivers and Windows updates are up to date and not broken.
Try those ideas; if still no success, consider the suggestions and questions I gave in the reply earlier today.

samep said:
Didn't realize the auto correct suggested wrong word. I meant rear USB of PC case but trying another PC is also suggested.
Windows 7 means most of my suggestions regarding the drivers may not apply to you. Off topic: upgrading to Windows 8 from Windows Vista had me searching for needed applications and tools omitted from Windows 8. Windows 7 is more developer ready than Windows 8. Simply rooting should be OK with either version as long as drivers and Windows updates are up to date and not broken.
Try those ideas; if still no success, consider the suggestions and questions I gave in the reply earlier today.
Click to expand...
Click to collapse
I don't know what I did differently on the 18 ****ING TIME but it finally worked! Your thanks meter has been duly increased =)

faile486 said:
I don't know what I did differently on the 18 ****ING TIME but it finally worked! Your thanks meter has been duly increased =)
Click to expand...
Click to collapse
Glad to see you among the rooted in Sprint Note 4 XDA. Hopefully your solution can be repeated for future updates. Lollipop well be here some day.

Does Kingo root Trip Knox?
Sent from my SM-N910P using XDA Free mobile app

Need To Obtain Procedure As To How To Get Into Recovery Mode

Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David

Davy49 said:
Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David
Click to expand...
Click to collapse
Hi David!
Holy cow, you've installed the entire studio? That's way more than you need. Just get the Platform Tools here: https://developer.android.com/studio/releases/platform-tools
At a user level, all you'll ever need are ADB and fastboot. Then enable developer settings, enable USB debugging and use the command 'adb reboot recovery'. You sure power + volume down don't work? Or power + volume up for fastboot (to get custom recovery installed)? Note that I have made zero research on this device so it may deviate (I'm on mobile right now). If any of those steps seem difficult or you're unsure how to proceed, just let me know where exactly you're stuck.
Oh and when you send an adb command to your device for the first time (like 'adb devices') it will likely show a trust notification on your screen, asking you to allow this computer to send adb commands. Make sure the remember checkbox is on.
Good luck!
Wrapped with delicious Fajita [emoji896]

Hi Timmy,
Thanks for being nice and explaining the process to me, that sounds pretty easy. Today my biggest problem is getting vanced to install on my amazon fire 7 tablet (2019 Edition). I've had it running normally on there previously, but a couple of day's ago I started the vanced app and noticed that I wasn't signed into my google account anymore. And when I attempted to sign in I received the now famous notice that said google server's were busy, please try again later. But knowing I had it running before, motivates me to get it running again. In the interim, I'm using the Web Tube app.
David

That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]

Timmmmaaahh said:
That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David

Davy49 said:
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David
Click to expand...
Click to collapse
Proper reboots in between? I don't see how web view would be related but it's always a good exercise to remove recent installations one by one, retrying Vanced in between. Be sure to share your findings if you encounter a potential culprit. It's important for the community to learn from that.

Hi Timmy (I guess it's okay to use this name),
I think before I do anything else, I'll go back and re-read the instructions on how to properly install it. Unless google has done something on their end, I should be able to get it functioning properly. It was installed previously, that's why I don't know what happened.
Thanks,
David