Hey everyone! Not a huge poster here however, I've been watching the threads in this forum for the past week or so awaiting root and attempting root myself. After days of attempts I have finally achieved root! I will lay down some of the specifics of what I was working with here and then give some helpful tips that will hopefully help others.
Computer OS - Windows 7 64bit (Installed HTC Sync previously and SDK)
Phone - Hboot .77 (Installed OTA accidently last week) w/ Kingston 2gb microsd
For days I had been trying every single method that I had come across and here is what had worked for me.
**Combined methods from other XDA forum members**
Power off phone with usb plugged in (usb debugging enabled previously)
Ran a batch file called root.bat that I made to run in command prompt consisting of the following (I ran this file before I turned on the phone)
:hello
adb shell
GOTO Hello
Click to expand...
Click to collapse
Hold the optical trackpad button while powering on
Press power once to enter fastboot
Wait for the fastboot to check the sdcard
Press volume down to highlight recovery
Press power to select recovery
Clicked the sdcard in and out
Eventually I entered the recovery screen on the incredible and the command window running my root.bat kept saying
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
I pressed control-C then Y to end the batch file and continued on with the methods listed here
androidforums.com/all-things-root-incredible/98180-prs-complete-rooting-guide.html
Click to expand...
Click to collapse
**KEY NOTES**
I had been cracking at this for the past few days and had plugged the usb from my incredible into the BACK of the computer instead of the front and the FIRST TIME I had done this I was able to obtain root and adb recovery had worked (These are usb ports that are DIRECTLY connected to the mobo and this might have been a huge impact in my success)
Also, I kept running across my drivers detecting my phone in recovery as disk drives so I used the method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
To uninstall the disk drives and the USB Mass storage device and prevent them from automatically installing everytime I uninstalled. Then I went ahead and did a "Update driver manually" and pointed it to the drivers in SDK\USB
One trick I just did that seemed to work was I booted the phone and went into recover (black screen with the red logo). At that point, Device Manager showed two HTC devices listed under 'disk drives'. I uninstalled both of those devices, pulled the battery, popped it back in and went in with down arrow+power. At that point Windows loaded the 'Android 1.0' driver unsuccessfully. Uninstalled that from Device Manager, then did the down arrow + power (and held it down) to go into the black recover screen and *poof* it loaded.
I'm using Windows 7 32bit.
quagmire0 said:
One trick I just did that seemed to work was I booted the phone and went into recover (black screen with the red logo). At that point, Device Manager showed two HTC devices listed under 'disk drives'. I uninstalled both of those devices, pulled the battery, popped it back in and went in with down arrow+power. At that point Windows loaded the 'Android 1.0' driver unsuccessfully. Uninstalled that from Device Manager, then did the down arrow + power (and held it down) to go into the black recover screen and *poof* it loaded.
I'm using Windows 7 32bit.
Click to expand...
Click to collapse
WOW. N1. Proof that worrying about drivers is pointless!
rynosaur said:
WOW. N1. Proof that worrying about drivers is pointless!
Click to expand...
Click to collapse
I think that to an extent it doesn't matter.
It seemed to refuse to work with me if the drivers were being loaded at disk drives. Therefore if the drivers weren't loaded at all and there was nothing installed it could work and if the CORRECT drivers were installed then it would work. But again, for me in my experience it was refusing to work if it had the disk drives were installed as the drivers for recovery.
kentoe said:
I think that to an extent it doesn't matter.
It seemed to refuse to work with me if the drivers were being loaded at disk drives. Therefore if the drivers weren't loaded at all and there was nothing installed it could work and if the CORRECT drivers were installed then it would work. But again, for me in my experience it was refusing to work if it had the disk drives were installed as the drivers for recovery.
Click to expand...
Click to collapse
Ok, but if you look at Unrevoked's newest DIY post, they show a logcat which starts at a card check and ends at adb starting, a five second gap. This is internal stuff, not going to the host/usb -- at least not listed in the logcat. If this exploit depended on host intervention at all, I'm guessing someone would have written a linux or windows script/program to talk to the DI. Rather, all the PC can do is try to open an adb session, it's like knocking at a door -- you can't make the person home no matter how well or correctly you knock, you just hope they'll answer.
When I obtained adb shell, had all three devices show up in Device Manager: ADB Composite (I used the API 8 driver), Generic Volume G:\ and Generic Volume H:\ -- drive letter specific to my windows install, of course. All hands were on deck. The glitch happens between the software, hardware and sdcard.
In any case, I'm glad you were successful!
rynosaur said:
Ok, but if you look at Unrevoked's newest DIY post, they show a logcat which starts at a card check and ends at adb starting, a five second gap. This is internal stuff, not going to the host/usb -- at least not listed in the logcat. If this exploit depended on host intervention at all, I'm guessing someone would have written a linux or windows script/program to talk to the DI. Rather, all the PC can do is try to open an adb session, it's like knocking at a door -- you can't make the person home no matter how well or correctly you knock, you just hope they'll answer.
When I obtained adb shell, had all three devices show up in Device Manager: ADB Composite (I used the API 8 driver), Generic Volume G:\ and Generic Volume H:\ -- drive letter specific to my windows install, of course. All hands were on deck. The glitch happens between the software, hardware and sdcard.
In any case, I'm glad you were successful!
Click to expand...
Click to collapse
Ahh, okay. Well whatevs, yeah I'm glad I'm rooted now! =D It was probably the connection with the front usb ports vs the back usb ports on my computer since the back are directly on the mobo. It worked the first time I switched it to the direct USB ports.
So glad I got lamppu, wifi tether, and removed city id along with obtaining titanium backup!
I was also trying to get root for a few days and had some issues. I eventually got in on my 4th MicroSD card try- which was a junky 1GB that wasn't even labeled for speed...
I tried a16GB Class 2, 8GB class 4, 4GB class 4 and none would stay with 'device not found'- even after trying for 20+ times on each. My next step was to buy a class 6, but a random 1GB I had laying around worked. It connected after the 1st attempt with the 1GB card.
Another note- I got the '/system/bin/sh' message about 30 seconds after it went into recovery mode- not right at the start as I see it happening in the videos.
Easiest way is to yank the battery and start over if you don't get it; I used the vol down + power start up option.
Nothing worked for me. Tried all methods with lots of cards.
Stock SanDisk 2gb C4
Lexar 8gb C4
Lexar 8gb C6
DaneElec 4gb C4 (same as PNY 4/4 and Kingston 4/4)
As I was about to put my Inc for sale on Ebay. NiX threw out a suggestion on IRC. I tried it w/ the DaneElec and it worked.
It worked first try and every try since. Tried it with the stock sandisk 2/2 and no go. Haven't tried the Lexars.
Give it a shot. Good luck.
loop shell / Vol- + Power. / Hboot / wait for 4secs / insert card / highlight recovery / hit power + count to 3 or 5 and insert usb / wait till 10secs after /!\
Thanks OP - Using the oldest/slowest card I have (old 1gb Corsair card formatted Fat32), enabling the driver local policy you mentioned, pulling the battery while phone was on, and the eject method described above - I finally got in. I have no idea if it was pure luck or if it had anything to do with the above, but yours was the last thread I read so you get a thanks.
**EDIT**
After trying to get back in after realizing I needed to remove any apps before rebooting, I once again have zero luck getting in... so I'm leaning towards the complete chance/luck idea.
seanmcd72 said:
Thanks OP - Using the oldest/slowest card I have (old 1gb Corsair card formatted Fat32), enabling the driver local policy you mentioned, pulling the battery while phone was on, and the eject method described above - I finally got in. I have no idea if it was pure luck or if it had anything to do with the above, but yours was the last thread I read so you get a thanks.
Click to expand...
Click to collapse
You're welcome! I'm glad my information has helped!
Related
TOTAL NOOB HERE.
I have already posted but everyones situation is different to mine and I really need someone to talk me through what it is I need to do I've been trying to fix this issue for the last 20hrs with no sleep!
Here is the situation:
I have an HTC Desire HD 2.3.3. It is S-ON. The issue (after doing hours of reading) appears to look like a classic USB brick. As in no matter what sdcard I place in the phone it still reads as "unavailable" with no mounting options. Same thing happens when I connect to the PC I have HTC SYNC/Charge only/USB Tethering but no Mass storage option. This is driving me F****** mad now!
I have already tried 3 different SDcards all three are class 2 and both work fine in my Galaxy S2 and have also reformatted all 3 in the PC using Fat32 and even through command line prompt. I've also tried 2 different USB cables on various usb ports. I have tried cleaning contacts and even beefing up the cover with folded paper. Bluetooth works fine and when I connect it to the PC i have all the options you would expect to see apart from mass storage. The issue is the card will not mount and everything just reads 'unavailable' inc mount - which is just greyed out.
I have managed to get ADB/Fastboot to work (at least I think) I can perform function: 'Fastboot oem enableqxdm 0' when I am in boot menu (vol down + power) and I get a msg which says OKAY. However at this moment in time I need the help of GOD! I have SDK installed with all packages installed and placed in C:/android. I also have USB debugging enabled. Should I be executing these commands from boot menu (Fastboot usb) or the phones desktop. when I try 'adb devices' while phone is in desktop it reads fine and tells me that there is a device listed. but when I try ...enableqxdm from desktop I just get 'waiting for device'. I have used PDAnet to correctly install ADB drivers. I am running Windows 7 64bit. I have factory reset soft/hard. The only thing I havent tried is to see if it appears in recovery mode and the various brick fixes which tbh just confuse the living hell out of me. Please can someone talk me through what it is I need to do I have no idea where to go from here. Like I said I am totally new to this but looking to build up a competency for next time. I have read a guide (Im sorry cant remember who it was by) but they mention to perform 'getvar cid' then follow link to website which creates mtd file...which no longer exists I have searched far and wide and I am ready to throw this piece of crap on ebay for spares/repairs. It was originally on Orange but unlocked and I have been using a tmobile sim which works fine.
PLEASE HELP ME :-(
Edit: Cards not being picked up in recovery mode
Sorry about horizantal fail.
Sent from my GT-I9100 using xda app-developers app
Phone sent to independent repair centre will post with what issue was.
Ok I have a backup of 8.0 on a usb flash drive before I upgraded to 8.1 which I loved. I am very tech savvy and have flashed lots of roms, comfortable with Reg edits and hacks. I think I went too far now...
I remember a boot speed boost tweak I read on the internet which I thought I would try on my vivo tab. I ran msconfig and went to the boot menu. I checked No GUI boot and then went to advanced options and selected in number of processors - 4 (as it's a tegra quad core) and maximum memory as 2gig, I applied, got a warning message about bitlocker which was fine as I have recovery key and rebooted.
However.... upon starting I get Preparing Automatic Repair message, then Diagnosing PC message, then Your PC did not start correctly. So I click on Advanced options and have tried every option possibly listed. I used the Windows 8 recovery image in my usb drive to refresh, repair, reset, and nothing works. Says install media and I do and says not correct media. Unless it is expecting 8.1 backup which I don't have. I thought anyone could revert to 8.0 anyway.
So matter what I try I cannot get it to start. If only I could undo those boot changes. Maybe via command prompt?
Any help greatly appreciated.
tboy2000 said:
Maybe via command prompt?
Click to expand...
Click to collapse
Yes. Boot to command prompt mode, then extract the WinRT 8.0 WIM file from USB over the drive C:\ with the "dism /apply-image /imagefile:e:\...\your_recovery.wim /index:1 /applydir:c:\"
I'd recommend to format c: before doing this. Obviously you'll lose all your data.
You may also need to edit boot options with bcdedit.
If you have the 8.0 recovery image, you'll need to actually boot from the USB stick directly. I think that this is due to the invalidation of 8.0 signatures that happened in 8.1. I only know how you do this with Surface RT: with the USB stick connected and the Surface off, hold volume down, then press and hold the power button until you see the Surface logo. It'll then take noticeably longer to boot, since it's reading off USB instead of the built-in SSD.
I don't know how different this procedure would be on an Asus Vivo Tab.
Ok I solved it by downloading a different recovery image to the one I had. Managed to install and boot by volume down button. Strange because my recovery image worked before. All running fine ?
However I then ran into another problem. All of a sudden after a reset I got an error saying "unable to reset your pc. A required hard drive partition is missing". What the heck I did nothing. Also when I tried to use bitlocker recovery key it said the hard drive is locked. Unlock the drive and try again.
So after some hours of research, I booted to command prompt and typed:
bcdboot
and then...
bcdboot c:\windows
and it said boot files copied successfully. I rebooted with fingers crossed and it WORKED!!!
?
tboy2000 said:
Strange because my recovery image worked before.
Click to expand...
Click to collapse
This may be due to you've reformatted your USB stick to NTFS, then copied there your recovery image, since UEFI can boot only from FAT32 disks.
Glad to see the joys of Windows troubleshooting isn't lost on their tablets.
I'm really considering moving from Android based tablets to Windows 8 tablets once the platform matures a little bit. They run so smoothly (tried a few out at my local Staples). The OS is basically built for touchscreen anyway.
I'm having issues with unlocking/rooting my nexus 7 2013.
I downloaded and installed the nexus root toolkit at wugfresh.com
I've followed all the instructions precisely. However, I always failt the ADB Driver test.
Here are the things I've found while trying to troubleshoot my problem:
1. When I enable usb debugging mode and plug in the nexus 7, I NEVER received the RSA Fingerprint authorization screen.
2. I've installed all the drivers and when it's plugged into the PC, it is recognized as a "google nexus ADB Interface": i.imgur.WHAT/f5Rk5qg.png
3. Inside of USBDeview it is recognized as mass storage device (color purple instead of green): i.imgur.WHAT/r4SwmVM.png
4. Under My Computer I am unable to reach the harddrive anymore.
I believe this is what is preventing me from moving forward. I know this because I've plugged this into my co-workers PC (he already had NRT installed to root his 2012 Nexus 7 awhile ago) and unlocking it on his PC works fine.
5. After uninstalling the drivers installed with NRT and uninstalling the NRT, I still can't access the drive as I could before.
Any help would be appreciated.
This is my first post so I cannot post links to the image... On #2 and #3 replace the i.imgur.WHAT with i.imgur.com
I had the same issue with Wug's toolkit. I finally went the google route using the SDK and usb drivers and it worked like a charm. I would try that method if you feel comfortable enough. Here's a guide to help with that: http://forum.xda-developers.com/showthread.php?t=2382051
railed said:
I had the same issue with Wug's toolkit. I finally went the google route using the SDK and usb drivers and it worked like a charm. I would try that method if you feel comfortable enough. Here's a guide to help with that: http://forum.xda-developers.com/showthread.php?t=2382051
Click to expand...
Click to collapse
I think my issue isn't with the toolkit but with the drivers on my computer right now. I'm not sure how to fix the driver issue i'm having. The link you provided only links to drivers I've already tried.
Laxxium said:
1. When I enable usb debugging mode and plug in the nexus 7, I NEVER received the RSA Fingerprint authorization screen.
Click to expand...
Click to collapse
This is usually because you are not running the latest adb version 1.0.31, but might be for other reasons like the adb that is running in the background is the older version and you need to adb kill-server then adb devices to restart it
Don't underestimate the power of reboot. Sometimes things get in a weird state and even though you have it set up properly, the changes won't really kick in until a reboot.
Laxxium said:
3. Inside of USBDeview it is recognized as mass storage device (color purple instead of green): i.imgur.WHAT/r4SwmVM.png
Click to expand...
Click to collapse
I didn't see mass storage device where you highlighted in red.
You shouldn't see USB mass storage device with this device. It doesn't support it. Only MTP mode. If you are seeing mass storage device, then probably some drivers are out of whack and you should use usbdeview to remove them.
Laxxium said:
4. Under My Computer I am unable to reach the harddrive anymore.
Click to expand...
Click to collapse
There could be many explanations for this. The simplest one is you have USB debugging enabled. Try disabling USB debugging. If that doesn't work, try PTP mode settings->storage->3baroptions If you see PTP mode, but not MTP, then it is a USB ID problem. If you don't see PTP mode either, you probably need to remove some drivers, reboot, and reinstall the drivers.
msellsio completely
Well... my work day ended and I figured I would simply try to do it at home.
I got the drivers to work at home. The nexus was already unlocked so I click on the root button.
After clicking on root, it looks like my tablet got stuck in Bootloader mode, IE in the videos I saw people doing it, it would restart and go into bootload and do something then restart again, mine restarted and just stayed on the bootload screen until I pushed the on/off button (for yes to start).
Now it loads into the tablet and I get about 17 error messages of
"Unfortunately, Google Play Services has stopped" and
"Unfortunately, the process com.google.process.gapps has stopped".
So now I have no idea what to do, I can't even use the damn thing anymore.
Laxxium said:
So now I have no idea what to do, I can't even use the damn thing anymore.
Click to expand...
Click to collapse
Do a factory reset
settings->backup&reset->factory data reset
If you can't get into that, power down
then press Power+VolUp until you see Google, then let go.
You'll see fallen android.
Press and Hold Power, then press/release VolUp, then release Power
Use VolDown to highlight wipe data factory reset, then Power to select.
sfhub said:
Do a factory reset
settings->backup&reset->factory data reset
If you can't get into that, power down
then press Power+VolUp until you see Google, then let go.
You'll see fallen android.
Press and Hold Power, then press/release VolUp, then release Power
Use VolDown to highlight wipe data factory reset, then Power to select.
Click to expand...
Click to collapse
Thanks for this.
I FINALLY got everything to work.
1. I did a factory reset (the 1 thing i was trying to avoid). This fixed the issues with the error messages.
2. I figured out what went wrong with the root toolkit. I decided to try and do the rooting manually, while trying to flash the recovery file, it was getting an unknown error. So the toolkit was basically getting stuck there. It took me 2 hours to figure out that this was happening simply because I was using my front USB3.0 ports. I switch to the back USB2.0 ports and the flashing worked fine.
3. Since I had already managed to flash teh recovery file, I deleted the universal adb drivers and let windows handle it, it installed the regular drivers and I finally managed to access the drive. I was able to upload the supersu file thus completing the root.
I still don't know why the ADB drivers won't let me access the drive though. Guess this mystery will have to be solved anytime.
Laxxium said:
I still don't know why the ADB drivers won't let me access the drive though. Guess this mystery will have to be solved anytime.
Click to expand...
Click to collapse
If you can access the Nexus 7 over MTP (ie as a drive) while USB debugging is disabled but not when it is enabled, that is a known issue and here is a fix.
http://forum.xda-developers.com/showthread.php?t=2391236
If you can't access MTP at all, I would also look at that link to d/l Nirsoft USBDeview and remove all the drivers for the nexus 7 (sort by date and select all the nexus 7 entries) Let the drivers reinstall from scratch.
My LG E980 is bricked. I can access download mode and that is it! I am unable to boot into recovery,
and the hard reset screen simply sits there forever. My computer only recognizes my device as an "unknown usb device."
I'm unsure what can be done about this, but I feel like this is better than the infamous QHSUB icon displayed when the device cannot be recovered.
Does anyone have a remedy for this problem?? I have GOT to fix this phone and can't afford to Jtag the device, but I'm losing hope that this is possible, PLEASE help. :crying:
Have you installed the LG drivers for your pc and tried the unbrick method?
Yeah dude there's an unbrick method. If this doesn't work just sell the phone on Ebay. http://forum.xda-developers.com/showthread.php?t=2302660
There is never a time when this device cant be recovered. even the qhusb is a fairly simple fix. ill go ahead and make a sdcard boot image tonight. do you have a 32gb sdcard? (or larger) and an sdcard reader, if you have those two things i can make an unbrick.img that you flash toi the sdcard and put in the non-booting phone and it will get you to download mode/recovery mode. ill have to check out what partitions are where as i dont wish to include my efs along with it all .
twill1987 said:
My LG E980 is bricked. I can access download mode and that is it! I am unable to boot into recovery,
and the hard reset screen simply sits there forever. My computer only recognizes my device as an "unknown usb device."
I'm unsure what can be done about this, but I feel like this is better than the infamous QHSUB icon displayed when the device cannot be recovered.
Does anyone have a remedy for this problem?? I have GOT to fix this phone and can't afford to Jtag the device, but I'm losing hope that this is possible, PLEASE help. :crying:
Click to expand...
Click to collapse
Happened to me.
1. With the phone on download mode and plugged in the computer; uninstall the unknown device on your computer using device manager. The computer should try to get the drivers for your phone.
2. If it doesn't. Repeat step one and install the drivers first.
That worked for me hopefully I'll work for you.
Sent from my LG-E980 using XDA Premium 4 mobile app
Yes
riki126 said:
Have you installed the LG drivers for your pc and tried the unbrick method?
Click to expand...
Click to collapse
Yes I tried that. The drivers won't install. I even used another windows 8 computer my roommate has and switched out
the usb cables, still came back "unknown device"
shabbypenguin said:
There is never a time when this device cant be recovered. even the qhusb is a fairly simple fix. ill go ahead and make a sdcard boot image tonight. do you have a 32gb sdcard? (or larger) and an sdcard reader, if you have those two things i can make an unbrick.img that you flash toi the sdcard and put in the non-booting phone and it will get you to download mode/recovery mode. ill have to check out what partitions are where as i dont wish to include my efs along with it all .
Click to expand...
Click to collapse
I do have a 16gb sd card, but I can pick up at 32 gb sd at my local best buy. I have an Asus laptop running windows 8 and it has an SD card reader. I am a little confused (semi-noob) as to how this will work because my phone will boot up, and the led changes colors on the home button for about 4 seconds and then the light stops flashing. The phone is stuck on the LG boot screen, and there is no way out of it but to pull the battery or to reset with power button. Of course no recovery as previously mentioned. I really just want to get back to stock, but I can't manage to get both the windows 8 computers I've tried to detect the phone in download mode. Ever since I switched to the Candykat rom 4.4 the computer wasn't able to recognize the phone, even when the phone was fully functional inside the rom.
I have tried it on my dads windows 7 laptop as well with no dice. Instaled LG drivers, uninstalled LG Drivers, uninstalled device from the Device Manager. I've done everything I could think of. I previously was in a Philz touch recovery, but every rom I tried to flash wouldn't work. I tried to flash another recovery from inside it and then the device bricked like it is now. What a head ache. If you think this method would work, I am more than willing to try it, just unfamiliar with what I need to do on my end.
Okay
stulzerl said:
Happened to me.
1. With the phone on download mode and plugged in the computer; uninstall the unknown device on your computer using device manager. The computer should try to get the drivers for your phone.
2. If it doesn't. Repeat step one and install the drivers first.
That worked for me hopefully I'll work for you.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will give your method a shot, but I have done this a lot already. The only thing I can think of is I usually unplug the phone from the computer right after deleting the drivers and uninstalling in device manager. Maybe I should just leave the phone plugged in and see if the computer automatically downloads the drivers, but I don't think it will because I've tried to update the drivers before. It gives me an error code "10" and says the device has malfunction or stopped working This phone has been undetectable via USB since flashing the candykat 4.4 rom. Every computer I've tried (3) and every USB cable (3 again) has displayed it as an "unknown device"
twill1987 said:
I will give your method a shot, but I have done this a lot already. The only thing I can think of is I usually unplug the phone from the computer right after deleting the drivers and uninstalling in device manager. Maybe I should just leave the phone plugged in and see if the computer automatically downloads the drivers, but I don't think it will because I've tried to update the drivers before. It gives me an error code "10" and says the device has malfunction or stopped working This phone has been undetectable via USB since flashing the candykat 4.4 rom. Every computer I've tried (3) and every USB cable (3 again) has displayed it as an "unknown device"
Click to expand...
Click to collapse
I've had similar issues when i had my optimus g. I had to use a pc with xp to flasht he phone, dunno why though. You could give that a shot.
twill1987 said:
I do have a 16gb sd card, but I can pick up at 32 gb sd at my local best buy. I have an Asus laptop running windows 8 and it has an SD card reader. I am a little confused (semi-noob) as to how this will work because my phone will boot up, and the led changes colors on the home button for about 4 seconds and then the light stops flashing. The phone is stuck on the LG boot screen, and there is no way out of it but to pull the battery or to reset with power button. Of course no recovery as previously mentioned. I really just want to get back to stock, but I can't manage to get both the windows 8 computers I've tried to detect the phone in download mode. Ever since I switched to the Candykat rom 4.4 the computer wasn't able to recognize the phone, even when the phone was fully functional inside the rom.
I have tried it on my dads windows 7 laptop as well with no dice. Instaled LG drivers, uninstalled LG Drivers, uninstalled device from the Device Manager. I've done everything I could think of. I previously was in a Philz touch recovery, but every rom I tried to flash wouldn't work. I tried to flash another recovery from inside it and then the device bricked like it is now. What a head ache. If you think this method would work, I am more than willing to try it, just unfamiliar with what I need to do on my end.
Click to expand...
Click to collapse
I dont know lg's download mode, kdz, tot etc all that well. im more of a samsung guy. however qualcomm since the s4 chipset has allowed for sdcards that are properly formatted to boot the os instead of the internal emmc. here is a decent guide, just need to make teh image for this device. this will let your device boot no matter how bad it gets you are welcome to try with 16gb, the rule of thumb i know of is as big as teh emmc is use that same size or larger sdcard, however some people have had sucess withs maller, just not many that i know of. http://forum.xda-developers.com/showthread.php?t=2439367
however afaik the only way to reflash teh bootloader partitions is via kdz/download mode so perhaps the sdcard will let you get into that mode and then you can flash, so long as you keep your sdcard like that it will boot fully, but in order ot get your sdcard back you need to repair teh files on your phone .
Thanks
WeActOnImpulse said:
Yeah dude there's an unbrick method. If this doesn't work just sell the phone on Ebay. http://forum.xda-developers.com/showthread.php?t=2302660
Click to expand...
Click to collapse
I have tried this and unfortunately since the USB drivers aren't detected by the computer there is no way for me to flash back to stock.
Thanks for the information though, I appreciate it.
shabbypenguin said:
I dont know lg's download mode, kdz, tot etc all that well. im more of a samsung guy. however qualcomm since the s4 chipset has allowed for sdcards that are properly formatted to boot the os instead of the internal emmc. here is a decent guide, just need to make teh image for this device. this will let your device boot no matter how bad it gets you are welcome to try with 16gb, the rule of thumb i know of is as big as teh emmc is use that same size or larger sdcard, however some people have had sucess withs maller, just not many that i know of. http://forum.xda-developers.com/showthread.php?t=2439367
however afaik the only way to reflash teh bootloader partitions is via kdz/download mode so perhaps the sdcard will let you get into that mode and then you can flash, so long as you keep your sdcard like that it will boot fully, but in order ot get your sdcard back you need to repair teh files on your phone .
Click to expand...
Click to collapse
Wow, that sounds awesome. I followed most of that. I access download mode on the device by pressing vol up and down simultaneously and plugging in the usb cable. I am more willing to try this, and if it works I will pay you from my paypal. I guess all I need now are those files to run to the sd card. I read the tutorial you posted for the samsung and downloaded the windows disk manager. I am eager to try this method, though it is admittedly very new to me.. If you can post those files, I will follow the instructions you give and pay you a little bit of money for your help!
I am a broke college student so it won't be much, but I really appreciate your response and information on this method with the qualcomm s4.
Here is the unbrick image. follow the guide for your platform (gunna guess windows) and write this to your sdcard after backing it up. from there you need to restore your partitions by flashing them .
https://mega.co.nz/#!YB5xWQ7Y!Qcnx9UmcNn-f6skfiIFN-jd0EeYxdmrQGA1zzP5hfA0
Just wrote it to sd card
shabbypenguin said:
Here is the unbrick image. follow the guide for your platform (gunna guess windows) and write this to your sdcard after backing it up. from there you need to restore your partitions by flashing them .
https://mega.co.nz/#!YB5xWQ7Y!Qcnx9UmcNn-f6skfiIFN-jd0EeYxdmrQGA1zzP5hfA0
Click to expand...
Click to collapse
Okay so I bought the 32 gb sd card. Just wrote the .img file you sent me to the sd card.
I powered on the phone and nothing happened, I got the same LG screen where the led flashes and then stops.
I followed that guide, but am I supposed to go to download mode instead of just powering on the device?
I got a little confused by the samsung jargon lol. I just want to know after I've written the unbrick.zip to the sd card
how do I get my phone to recognize the card is there? And once I am able to do that how do I "restore my partitions by flashing them?"
I do have the factory firmware set to flash through lg flashtool, but the phone can't be detected of course due to the usb issue.
Just want to say thanks for walking me through it this far, I feel like I'm close hopefully but unsure what to do next.
twill1987 said:
Okay so I bought the 32 gb sd card. Just wrote the .img file you sent me to the sd card.
I powered on the phone and nothing happened, I got the same LG screen where the led flashes and then stops.
I followed that guide, but am I supposed to go to download mode instead of just powering on the device?
I got a little confused by the samsung jargon lol. I just want to know after I've written the unbrick.zip to the sd card
how do I get my phone to recognize the card is there? And once I am able to do that how do I "restore my partitions by flashing them?"
I do have the factory firmware set to flash through lg flashtool, but the phone can't be detected of course due to the usb issue.
Just want to say thanks for walking me through it this far, I feel like I'm close hopefully but unsure what to do next.
Click to expand...
Click to collapse
you wrote the image to the sdcard? i wonder if its because you still have the low level bootloaders that it may not be booting from the sdcard, normally this is done to fix qhusb errored devices. as for restoring the partitions all you would need to do is one its booted up push the unbrick image to the phone and use rooted adb shell to write it back onto your phone.
Possible hope??
shabbypenguin said:
you wrote the image to the sdcard? i wonder if its because you still have the low level bootloaders that it may not be booting from the sdcard, normally this is done to fix qhusb errored devices. as for restoring the partitions all you would need to do is one its booted up push the unbrick image to the phone and use rooted adb shell to write it back onto your phone.
Click to expand...
Click to collapse
I meant I used the windows tool to write the debrick.img to the sd card. But no dice, the device isn't recognised.
However! I installed a driver clean up tool and now if I plug in the device it is recognized as Android Original ADB Interface.
The LG Flashtools even says the port is ready! But I get the error code "10" "device cannot start, A request for the USB device descriptor failed."
So now I am stuck on that instead lol. This just sucks.
that sucks about the sdcard, it must be because you arent "truly" bricked. sorry i thought it would help ya :/.
What is the driver repair tool you used? I know this thread is old but I'm having the same problem. I was trying to root my E980 and now my computer wont recognize my device. The phone works perfect, its just when I plug it in to the computer it isnt recognized. How can I fix this?
+1
Just wondering if anyone's come across a solution to this besides a sledge hammer... been having the same "Code 10: Device failed to start" when in Download Mode, though Windows finds a driver fine when the phone is stuck on the LG screen... doesn't help much, though, 'cause it won't receive adb commands. I manually installed the LG USB Composite Device driver, which added a modem and a COM port, both of which Windows recognized to be active, but the LG FlashTool USB Viewer showed no open pipes. I'm a relative noob, so please feel free to point out the obvious, like an alternative to adb that the phone can always receive or a way to brick it the rest of the way so the MicroSD trick will work.
I came across this problem like the OP and just wanna let everyone know that you have to use computer with USB 2.0 port then the driver issue would be fixed.
Got my USB-C to USB-A cable today, so I'd like to unlock the bootloader on my Pixel C. The problem is, when I hook it up to my PC, it does recognize it in Windows as the Pixel C - I can see it and browse through the drive and folders - but when I try to run an ADB Devices command, it does not see anything.
I think I have all the latest drivers - I grabbed the Marshmallow and USB drivers from the links on this page:
http://www.androidbeat.com/2015/10/how-to-unlock-nexus-6p-bootloader/
But I'm still not getting anything. I've tried using different USB ports on my computer, both USB 2 and USB 3 ports (although I've always had success with the USB 2 ports in the past), but still no dice. I did notice when I go to Device Manager, that there is an ADB Interface Device that is unrecognized, but I've tried updating the drivers (no luck), as well as uninstalling and then rescanning for hardware changes (just get the same unrecognized ADB device as I started with).
For reference sake, I'm using a Windows 10 Pro 64bit PC.
I'm at a loss as to what to do, so any help I can get here would be greatly appreciated.
Nevermind, I was able to get it straightened out. Used the download/instructions found on this XDA thread to get everything squared away:
http://forum.xda-developers.com/showthread.php?t=2588979
Device is now unlocked and I can go ahead and set it up properly while waiting for root access to become available.
What did you do to resolve this? I am running Windows 10 64bit, with the same issue. I followed the thread for the adb installer, with no luck.
regime2008 said:
What did you do to resolve this? I am running Windows 10 64bit, with the same issue. I followed the thread for the adb installer, with no luck.
Click to expand...
Click to collapse
I think the main issue was with getting the device recognized correctly by Windows. I believe what ultimately solved the problem was going into Device Manager and clicking on the appropriate item and then updating the driver to the correct one. I don't remember what is was exactly off-hand, but if you download the file in the link I provided, there is a help image (a number of pictures, really) which spells out exactly what steps to take to get the issue resolved in Device Manger.
Note that I had to do this twice, once when the device was first connected, and then a second time as well (I believe it was after enabling fastboot, although I could be mistaken on the second part).
The whole thing is actually a pretty simple fix once I knew the correct steps to take. Was working on it for hours though until I stumbled across the answer.
Geese1 said:
I think the main issue was with getting the device recognized correctly by Windows. I believe what ultimately solved the problem was going into Device Manager and clicking on the appropriate item and then updating the driver to the correct one. I don't remember what is was exactly off-hand, but if you download the file in the link I provided, there is a help image (a number of pictures, really) which spells out exactly what steps to take to get the issue resolved in Device Manger.
Note that I had to do this twice, once when the device was first connected, and then a second time as well (I believe it was after enabling fastboot, although I could be mistaken on the second part).
The whole thing is actually a pretty simple fix once I knew the correct steps to take. Was working on it for hours though until I stumbled across the answer.
Click to expand...
Click to collapse
Funny thing is, I have tried all of those steps, and still no luck. I have deleted all of the drivers completely. Reinstalled them, and still get code 10. It seems several people are getting this issue in the thread you linked in your second post.
My Pixel C got an invalid pin error so tried to do a factory reset through android recovery but that ended to a bootloop and the tablet is simply useless. Thought I'd try to install OS again see if that would bring it back but I can't even get it recognised in the pc. I've put it in fastboot mode and it won't even acknowledge I've connected anything. Nothing shows up on Device Manager. Am I doing something wrong here? I'm out of ideas