Develop Bugs

Need to use USB to transfer files, but have an issue with screen

Hey guys, just a few days ago I messed up my screen and can't even see anything on it. However, the phone itself works, especially since the USB detects it. However, I cannot access the files because of the "locked screen" issue. I am on a Mac running Lion with no access to a PC at this point.
I was wondering if there was anyway to get into the phone's file system without the stupid locked screen issue, since of course I can't do anything on it because it's broken haha.
It was rooted, had clockwork, and ran mmuzzy's jellybean rom.

You can get adb access while booted into a custom recovery. Is your screen totally screwed or can you see when you boot into fastoot / recovery.

3rdstring said:
You can get adb access while booted into a custom recovery. Is your screen totally screwed or can you see when you boot into fastoot / recovery.
Click to expand...
Click to collapse
I can't see anything on it, nor does the touch actually work.

USB debugging on? Do you have adb setup?

3rdstring said:
USB debugging on? Do you have adb setup?
Click to expand...
Click to collapse
USB debugging is in. I have never actually done with ADB so I'm not really sure how to work it. Any insight on that?

http://forum.xda-developers.com/showthread.php?t=1869380
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
http://forum.xda-developers.com/showpost.php?p=25804454&postcount=59
Sent from my Galaxy Nexus using Tapatalk 2

freegee g pro edition

just did the freegee unlock and phone will not power on
what happened?
i even got an popup congratulating me that i was unlocked

What version g pro you have?
Sent from my LG-E980 using Tapatalk 2

att version
e980

Clutchz said:
att version
e980
Click to expand...
Click to collapse
Try posting your issue in the actual thread in original android development
Sent from my LG-E980 using Tapatalk 2

Only your recovery and possibly boot partitions are touched, so worst case you can always get to download mode. However if the phone won't turn on at all its something not directly related. What happened before you rebooted into this state?
Sent from my LG-LS970 using xda app-developers app

i was doing the freegee thing and it had finished i went to home and hit reboot and nothing it stayed there

FreeGee has been updated and I unlocked my phone without any issues.

Clutchz said:
just did the freegee unlock and phone will not power on
what happened?
i even got an popup congratulating me that i was unlocked
Click to expand...
Click to collapse
Mine's doing it too man. Installed the app. Phone is rooted but stock recovery. Let it do its unlock thing and said yes to disable LGE security. Then tried to reboot using the volume and home keys to get to recovery and it gave a "Secure booting failed. Cause: Device Unlocked so boot success!!" message. Then LG logo again then AT&T animation and that's as far as it gets. No recovery menu, no normal boot. Just AT&T.
You get yours figured out yet? We gonna have to LGNPST back to stock?
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
wahida76 said:
FreeGee has been updated and I unlocked my phone without any issues.
Click to expand...
Click to collapse
SO how do you get to recovery then? I tried to 2 button into recovery and am now unable to boot the phone.

the computer detects something by this name: Qualcomm HS-USB QDLoader 9008 (COM17) and the screen stays black on the LG

lessthanzach said:
Mine's doing it too man. Installed the app. Phone is rooted but stock recovery. Let it do its unlock thing and said yes to disable LGE security. Then tried to reboot using the volume and home keys to get to recovery and it gave a "Secure booting failed. Cause: Device Unlocked so boot success!!" message. Then LG logo again then AT&T animation and that's as far as it gets. No recovery menu, no normal boot. Just AT&T.
You get yours figured out yet? We gonna have to LGNPST back to stock?
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
SO how do you get to recovery then? I tried to 2 button into recovery and am now unable to boot the phone.
Click to expand...
Click to collapse
I used a reboot app to boot recovery
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
Clutchz said:
the computer detects something by this name: Qualcomm HS-USB QDLoader 9008 (COM17) and the screen stays black on the LG
Click to expand...
Click to collapse
Your phone hard bricked and flashing might work

wahida76 said:
I used a reboot app to boot recovery
---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------
Your phone hard bricked and flashing might work
Click to expand...
Click to collapse
the flash tools dont detect the phone

Clutchz said:
the flash tools dont detect the phone
Click to expand...
Click to collapse
I am really sorry to say this but if that is the case then your hard brick can't be fixed your option is warranty.

oh well i'll go to att tomorrow thanks guys

Clutchz said:
oh well i'll go to att tomorrow thanks guys
Click to expand...
Click to collapse
If you bought the phone within the last 14 days then you can return it if not you can call at&t and speak to warranty and they will send you a warranty replacement your other option is to ask if they have a local warranty center they can try to flash it or exchange it.

Clutchz said:
oh well i'll go to att tomorrow thanks guys
Click to expand...
Click to collapse
Are you sure you were putting it into download mode? You take out the battery. Then put battery back in the phone. THen I believe you hold the volume down key and plug the phone into the computer. Then LGNPST should recognize the phone after you change the COM port to I believe 41 or 42
Edit: You hold BOTH volume keys while plugging the phone into the computer. It needs to be completely off when you do this.
Edit 2: Here's the guide : http://forum.xda-developers.com/showthread.php?t=2302660
Switch it under device manager to COM port 41. Now flash tools should recognize it.
I'm honestly bummed that I'm now going to have to re-setup everything again. I just had to flash my phone 2 weeks ago to get rid of 2nd Init recovery to install the value pack. Now I get to do it again, then run the update, then re-root, and put my 200+ apps back on, lol. FML. I guess this just isn't the phone the tinker with. Never had any of these issues on my S1, S2, S3, HTC One, One X, Note, etc. Oh well.

Tried it didn't work thanks for the help anyways guys i have a 90 day no questions asked with Costco so i'll take advantage of that any way to export text and call logs? Too much to ask right?

Clutchz said:
Tried it didn't work thanks for the help anyways guys i have a 90 day no questions asked with Costco so i'll take advantage of that any way to export text and call logs? Too much to ask right?
Click to expand...
Click to collapse
If you're on a windows 8 machine it will not detect your phone with them drivers, you need a win 7 os. I had same issue before
Sent from my LG-E980 using Tapatalk 2

turilo said:
If you're on a windows 8 machine it will not detect your phone with them drivers, you need a win 7 os. I had same issue before
Sent from my LG-E980 using Tapatalk 2
Click to expand...
Click to collapse
no dice tried it on both even xp i'm gonna give up on it i'll return it its easier

Clutchz said:
Tried it didn't work thanks for the help anyways guys i have a 90 day no questions asked with Costco so i'll take advantage of that any way to export text and call logs? Too much to ask right?
Click to expand...
Click to collapse
Hey do you remember what version of freegee you installed? I think somehow you might have gotten version 1.0.6 instead of 1.1.0. Ive been through everything and the only thing that could have bricked you was using and older version of freegee. I didn't post on xda till Google showed the updated 1.1.0 version was live but maybe somehow you got an older on?
Sent from my LG-LS970 using xda app-developers app

Bootloader NOT UNLOCKED
I was wrong the bootloader is still Locked the developer of the App corrected his app info and this shows that.
http://forum.xda-developers.com/showpost.php?p=43813711&postcount=14

No fastbook/recovery (NOT ROOTED)

I have been up and down all the sites and recovery methods.
ISSUE:
In an attempt to root my Zenfone 2 (2.19.40.22 Lollipop) the tool I was using seemed to get stuck looking for my device. This was after installing a fastboot, or an attempt I believe. After a minute or so I noticed the phone screen was constantly showing the USB Logo.
I can turn on my phone and use it no problem. HOWEVER, I cannot POWER + VOL UP, to enter the bootloader. It just goes back to that USB Logo with the White Bar under it. And I have to power off and ON my phone again to get back to normal operation.
As you can imagine this makes it rather difficult to flash anything or use the ADB Tools whatsoever. Is there anything I can do to get that back, or am I doomed with a phone that can never be rooted?
[The tool that started this whole issue was the TWRPRecovery-Install]

Twrp tool only installs twrp recovery which you need an unlocked boot loader to install, so it should have never been used, can you use adb from the phone in normal operation? Can you get into recovery at all? Sometimes you can boot to recovery from adb shell when phone is in normal boot. Most of the solutions I can think of requires root but if you figure out how to get to recovery you can sideload a full update file to restore everything
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 07:40 PM ---------- Previous post was at 07:36 PM ----------
And I am not sure if it will work now, but there is a one click root tool for this phone you could try it, but if you have an unusable bootloader it may not work, let me do some research for other options, may not find anything but we'll see
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 07:43 PM ---------- Previous post was at 07:40 PM ----------
Start here
https://www.mediafire.com/folder/w70w7r1a65840/Zenfone_2
Sent from my ASUS_Z00AD using Tapatalk

Thanks for the info. I clearly followed the wrong guide. I did try the One Click Tool but again it goes straight to the USB logo. Its odd, if it was broken or deleted your imagine there would be a way to fix or reinstall it.

JetPKFR said:
Thanks for the info. I clearly followed the wrong guide. I did try the One Click Tool but again it goes straight to the USB logo. Its odd, if it was broken or deleted your imagine there would be a way to fix or reinstall it.
Click to expand...
Click to collapse
That is generally considered bricked... Only ASUS can fix for now....

Please confirm this is bricked

Hi guys,
I know there are plenty of posts about bricked phones and I've read most of them. Just want to do a sanity check here. If my phone has a LOCKED bootloader and USB debugging is NOT enabled, there is nothing I can do in terms of flashing an image right? I can enter bootloader and stock recovery, but when I boot to OS it bootloops.
Just want to confirm my only option is warranty claim with Google and there's no way to enable USB debugging other than from the OS?
Thanks in advance!

piotrus22 said:
Hi guys,
I know there are plenty of posts about bricked phones and I've read most of them. Just want to do a sanity check here. If my phone has a LOCKED bootloader and USB debugging is NOT enabled, there is nothing I can do in terms of flashing an image right? I can enter bootloader and stock recovery, but when I boot to OS it bootloops.
Just want to confirm my only option is warranty claim with Google and there's no way to enable USB debugging other than from the OS?
Thanks in advance!
Click to expand...
Click to collapse
Go into the bootloader and on a PC with adb run "fastboot flashing unlock" and see what happens. I don't think you need adb enabled to do it but I could be wrong so just try
---------- Post added at 11:14 PM ---------- Previous post was at 11:10 PM ----------
@piotrus22 another option would be to go into recovery and adb sideload the latest ota package from google.

Can you side load with debugging off?
Also have you factory reset from recovery?

DR3W5K1 said:
Can you side load with debugging off?
Also have you factory reset from recovery?
Click to expand...
Click to collapse
Not sure if you can but it wouldn't hurt to try. That night work too

Try to sideload the latest ota image.
Sent from my Pixel C using Tapatalk

piotrus22 said:
Hi guys,
I know there are plenty of posts about bricked phones and I've read most of them. Just want to do a sanity check here. If my phone has a LOCKED bootloader and USB debugging is NOT enabled, there is nothing I can do in terms of flashing an image right? I can enter bootloader and stock recovery, but when I boot to OS it bootloops.
Just want to confirm my only option is warranty claim with Google and there's no way to enable USB debugging other than from the OS?
Thanks in advance!
Click to expand...
Click to collapse
im having a similar issue. my phone just started to bootloop randomly yesterday, i tried to flash stock and once i get to the setup screen it shuts down and reboots...

thanks guys. i actually tried to sideload and was successful, but still no booting up. still get the boot loop. interestingly enough when i try to sideload again, i get an error message: device '(null)' not found

piotrus22 said:
thanks guys. i actually tried to sideload and was successful, but still no booting up. still get the boot loop. interestingly enough when i try to sideload again, i get an error message: device '(null)' not found
Click to expand...
Click to collapse
What were you trying to do to get it like that?

Veid71 said:
What were you trying to do to get it like that?
Click to expand...
Click to collapse
ok i was able to try to sideload it twice. side load finishes successfully but still doesn't boot to OS....

piotrus22 said:
ok i was able to try to sideload it twice. side load finishes successfully but still doesn't boot to OS....
Click to expand...
Click to collapse
Have you tried a factory reset?

DR3W5K1 said:
Have you tried a factory reset?
Click to expand...
Click to collapse
yes of course -

piotrus22 said:
yes of course -
Click to expand...
Click to collapse
Well unfortunately you're out of things to try.
If your phone happens to be a 128gb model this is actually quite common.
---------- Post added at 12:25 PM ---------- Previous post was at 12:11 PM ----------
Further confirmation of problems with some 128 units.
https://support.google.com/pixelphone/forum/AAAAb4-OgUsZ1zs71de3Io/?hl=by

I hope your phone is under warranty because Google won't do crap if it isn't. I'm a proud owner of a POS 128GB brick thanks to their junk they sell.
Sent from my [device_name] using XDA-Developers Legacy app

Cannot connect to adb Lineage OS 16

Hey guys,
So this weekend I decided to give lineage OS 16 a try on my Xiaomi 5, the process went smoothly I think, but the battery life is really bad, so I wish to try other ROM.
Now the thing is, I cannot connect to my computer (And I could with the previous MIUI), and if I run adb devices or fastboot devices (When on fastboot) nothing shows up. I have android debug enabled.
Any ideas on what this could be?

djramrques said:
Hey guys,
So this weekend I decided to give lineage OS 16 a try on my Xiaomi 5, the process went smoothly I think, but the battery life is really bad, so I wish to try other ROM.
Now the thing is, I cannot connect to my computer (And I could with the previous MIUI), and if I run adb devices or fastboot devices (When on fastboot) nothing shows up. I have android debug enabled.
Any ideas on what this could be?
Click to expand...
Click to collapse
You have twrp installed. So you don't need adb for next ROM. Try without GApps to save battery.

kurtn said:
You have twrp installed. So you don't need adb for next ROM. Try without GApps to save battery.
Click to expand...
Click to collapse
Hey. Thanks for the answer, I am still a bit noob on this so I am not sure I completely understand. Yes indeed I have used twrp , but I used the command fastboot boot twrp.img . Before that, I also did fastboot flash recovery <recovery_filename>.img. Does this mean that I have twrp installed or that I booted directly from it from my computer? I ask this because, when I go to recovery (Hold Power + Volume Up), I dont go to TRWP menu, but rather to the Mi-Recovery 3 menu.
Thank you!

Deleted

kurtn said:
You have twrp installed. So you don't need adb for next ROM. Try without GApps to save battery.
Click to expand...
Click to collapse
I am note sure what happened but did you mean to reply twice?

djramrques said:
I am note sure what happened but did you mean to reply twice?
Click to expand...
Click to collapse
Oops. Bad data connection.
---------- Post added at 04:14 PM ---------- Previous post was at 04:11 PM ----------
djramrques said:
Hey. Thanks for the answer, I am still a bit noob on this so I am not sure I completely understand. Yes indeed I have used twrp , but I used the command fastboot boot twrp.img . Before that, I also did fastboot flash recovery <recovery_filename>.img. Does this mean that I have twrp installed or that I booted directly from it from my computer? I ask this because, when I go to recovery (Hold Power + Volume Up), I dont go to TRWP menu, but rather to the Mi-Recovery 3 menu.
Thank you!
Click to expand...
Click to collapse
Oh, I have no experience with a/b devices like yours

kurtn said:
Oops. Bad data connection.
---------- Post added at 04:14 PM ---------- Previous post was at 04:11 PM ----------
Oh, I have no experience with a/b devices like yours
Click to expand...
Click to collapse
So turns out, if I use my old cable (Which is a bit ruined at on end), it works. But if I use a new cable, that I just bought, it does not work. That is super weird right?
Thank you anyway. I am flashing Pixel Experience at the moment. ANd now I am TWRP installed.