Related
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
greyphox said:
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
Click to expand...
Click to collapse
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Wilks3y said:
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Click to expand...
Click to collapse
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
greyphox said:
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
Click to expand...
Click to collapse
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
nexus toolkit from dev section
ngoralph said:
nexus toolkit from dev section
Click to expand...
Click to collapse
Have you even read what hes said?
He's already tried the toolkit...
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
The first step in the full driver guide in wugs kit is to enable usb debugging which i cannot do though as it won't power on.......
I have added the environmental variabes before yes sorry, qbkings utube vids showed me how to do that
Just tried these steps
toolkit home screen, flash stock + unroot (softbricked bootloop)
then naksaki 4.2 jzo54k, auto download and extract.
it got to dos stage and i get 'Failed bootloader is locked'
??? thanks again
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
greyphox said:
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
Click to expand...
Click to collapse
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Wilks3y said:
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Click to expand...
Click to collapse
MOOOOOO!
It wrote to the system ok and now its hanging on erasing user data, googled and its happend to others.......
OK, more help please, been hanging for5 mins lol
Issue Fixed I think, he PM'd me.
Unlocked but... what do I do now?
Newbie but old or old but newbie - With the need and not just a curious want, to be able to "rename" my Nexus 7 v1 so I can see a friendly name in my old DD-WRTed Linksys GL, I finally had enough gumption to try rooting this tablet.
So, I was excited that when I used Nexus Root Toolkit v1.6.8 on my Nexus 7 v1, following the "easy and visual" steps, I actually managed to unlock this device. But when it came to the "root" part, the ADB repeatedly failed to recognize this tablet. I tried all the suggested steps and remedies, but so far, nada.
The tablet now boots past the white "Google" with an unlocked icon at the bottom, but nothing beyond thea big white "right-arrow" on the screen. I can choose a Wi-Fi signal to connect to, but that's it.
This is my first tablet and I have been playing with it for the past 3 months. I know people here are more than willing to help, so thank you in advance.
BTW, I am not that young to spend hours way past sleeping time to scour for answers and piece it together.
Wilks3y said:
Issue Fixed I think, he PM'd me.
Click to expand...
Click to collapse
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Kindred Mole said:
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Click to expand...
Click to collapse
+1
This worked for me...
Download the image file for your device which you can find at the Google Developer's site
Copy the uncompressed files from the image archive to the platform-tools folder of the Android SDK
Use the up and down volume on the device to get into bootloader mode. Connect the device to a usb port.
Open a command prompt in the platform tools folder and run the flash-all batch file to load the image to your device. After a few minutes I got the happy X logo to get me back to a blank slate.
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
voodoochild2008 said:
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
Click to expand...
Click to collapse
try to flash recovery again via fastboot...or doesnt pc recognize divice at all?
S.R
shivasrage said:
try to flash recovery again via fastboot...
S.R
Click to expand...
Click to collapse
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
voodoochild2008 said:
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
Click to expand...
Click to collapse
f****
have you tried flashing factory image from google site.with flash all-sh?
shivasrage said:
f****
have you tried flashing factory image from google site.with flash all-sh?
Click to expand...
Click to collapse
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
voodoochild2008 said:
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
Click to expand...
Click to collapse
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
shivasrage said:
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
Click to expand...
Click to collapse
Thanks....but still get waiting for device, thats the problem, nothing seems to see it so I cannot flash anything to it.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
i thought the same as you but fastboot isn recognizig N7 anymore....always wating for device....
Hemidroids said:
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
Click to expand...
Click to collapse
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
[/COLOR]
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
EXE? doh.......Windows.......sorry cant help.
shivasrage said:
[/COLOR]
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Click to expand...
Click to collapse
Tried some of that already but will try again tomorrow.
Thanks for help with this and will post tomorrow if I can sort it. cheers
I hope this instructions can help you a little bit...but if it fails don´t be angry its all I can think of ...at this time ....merry christmas
S.R.
http://forum.xda-developers.com/showthread.php?p=31931117:D
Sent from my Nexus 7 using xda premium
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
voodoochild2008 said:
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
Click to expand...
Click to collapse
How did you get it to work? I have problem getting my device to be recognized. Stuck on boot loop too..
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Quacker245 said:
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Click to expand...
Click to collapse
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
brainvision said:
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
Click to expand...
Click to collapse
Hi sorry for not being clear. Basically I am only allowed to access the bootloader and my device is soft-bricked. I'm pretty sure I tried uninstalling and reinstalling the drivers about a year ago when I originally did it, but I'll try again and let you know. Thanks!
Hi all,
I have a serious problem with my G2 which I could not solve: I used the new LG Flash Tool 2014 with stock KDZ file, everything was going just fine till I received an error message that LG server is not available, I disconnected the USB cable by mistake from my G2 and afterward I saw that it was in the middle of flashing process (12% was completed). I turned it off and tried to reach download mode again and nothing!, I'm receiving the "LG" logo and nothing- the screen goes black (it is still on).
I tried also to connect my phone to the computer- I received a list of 13 "new" local disks "H" to "T", only "H" disk is available and it's showing "image" folder with list of files.
I cannot reach "download mode", nothing is working!
I hope this is not the end for my G2..
please help me
Thank you so much!
If you could receive all those hard disks then you could maybe fix it with linux/ubuntu if you have it. Search for guides to cOpy the neccesary stuff bacK like the bootloader. I can't really help you atm as i am too sleepy.
wulsic said:
If you could receive all those hard disks then you could maybe fix it with linux/ubuntu if you have it. Search for guides to cOpy the neccesary stuff bacK like the bootloader. I can't really help you atm as i am too sleepy.
Click to expand...
Click to collapse
Thank you for your reply. I found this on the sticky threads: "[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2".
I installed ubuntu and followed the instructions. when I type the following: "gdisk -l /dev/sde" I receive an error message:
"GPT fdisk (gdisk) version 0.5.1
NOTE: Write test failed with error number 13. It will be impossible to save
changes to this disk's partition table!
Problem opening /dev/sde for reading! Error is 13
You must run this program as root or use sudo!"
My device is not rooted, is this the problem?
Please help me!!
Thanks
@NNCa It says you need to run the program as root on ubuntu.
Just use sudo in front of the commands.
You need to type once your password to use sudo, you can't see the password if you enter it for safety I guess but just click enter after you typed ykur password.
wulsic said:
@NNCa It says you need to run the program as root on ubuntu.
Just use sudo in front of the commands.
You need to type once your password to use sudo, you can't see the password if you enter it for safety I guess but just click enter after you typed ykur password.
Click to expand...
Click to collapse
Thank you so much!!
I succeeded to push all the files according to this thread, however I do not see the TWRP menu. I have just constant "LG" logo on screen.
Do I miss something?
Thanks!
NNCa said:
Thank you so much!!
I succeeded to push all the files according to this thread, however I do not see the TWRP menu. I have just constant "LG" logo on screen.
Do I miss something?
Thanks!
Click to expand...
Click to collapse
Well its good you're an step further, try to reboot to recovery using power+volume down i believe or its up idk try both it should say something about wipe data factory reset, press the power button and you are in recovery.
wulsic said:
Well its good you're an step further, try to reboot to recovery using power+volume down i believe or its up idk try both it should say something about wipe data factory reset, press the power button and you are in recovery.
Click to expand...
Click to collapse
Hi,
I powered off my phone by pressing volume down + power for a while ("LG" logo blinked once and phone was fully powered off).
I pushed volume down + power till I saw the LG logo, released it, and pushed again- and finally I reached the Factory Hard Reset screen. I have pushed 3 times the power, and I have got "Factory reset processing..." and nothing is appeared, even when I'm pushing several times on power again.
I guess this is the end of my G2 :crying:
Thank you all for your support, this is an excellent forum!:good::good:
NNCa said:
Hi,
I powered off my phone by pressing volume down + power for a while ("LG" logo blinked once and phone was fully powered off).
I pushed volume down + power till I saw the LG logo, released it, and pushed again- and finally I reached the Factory Hard Reset screen. I have pushed 3 times the power, and I have got "Factory reset processing..." and nothing is appeared, even when I'm pushing several times on power again.
I guess this is the end of my G2 :crying:
Thank you all for your support, this is an excellent forum!:good::good:
Click to expand...
Click to collapse
Nope it isn't the end try to install the recovery again or try to push the custom twrp recovery again to the right partition! Dont give up that fast when i hear your things then its still fixable! you already got the factory reset processing so try to Push the Recovery again and search for an guide about recovery maybe Then you would probably get your device fixed.
Just read my things about simplicity so think easy and you can fix it. AND STAY POSITIVE You will repair your phone today :good:
wulsic said:
Nope it isn't the end try to install the recovery again or try to push the custom twrp recovery again to the right partition! Dont give up that fast when i hear your things then its still fixable! you already got the factory reset processing so try to Push the Recovery again and search for an guide about recovery maybe Then you would probably get your device fixed.
Just read my things about simplicity so think easy and you can fix it. AND STAY POSITIVE You will repair your phone today :good:
Click to expand...
Click to collapse
Thanks, but after connecting the device to linux/windows, it seems that it is not recongized, I do not see the partitions anymore even when typing "ls /dev/sd*" through linux terminal..
NNCa said:
Thanks, but after connecting the device to linux/windows, it seems that it is not recongized, I do not see the partitions anymore even when typing "ls /dev/sd*" through linux terminal..
Click to expand...
Click to collapse
Yeah because the phone has bootloader etc again so maybe you can try this:
http://forum.xda-developers.com/showthread.php?t=2432476
wulsic said:
Yeah because the phone has bootloader etc again so maybe you can try this:
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
Hi there,
I tried to flash my phone using the lg flash tool, unfortunately it cannot recognized any connected device through USB.. I don't know what else will work for my device
NNCa said:
Hi there,
I tried to flash my phone using the lg flash tool, unfortunately it cannot recognized any connected device through USB.. I don't know what else will work for my device
Click to expand...
Click to collapse
Did you already installed the LG drivers? and checked in device manager or there is like any change when you connect and disconnect your phone?
wulsic said:
Did you already installed the LG drivers? and checked in device manager or there is like any change when you connect and disconnect your phone?
Click to expand...
Click to collapse
Yes, I checked it- no response during connecting/disconnecting the device..
Maybe I did a mistake when trying to push those image files.. I guess there is nothing I can do to fix my phone..
Do you have any other suggestions?
Can someone please help me. How can I get to the LG device- Is there another software I can use to flash files into this device?
Thanks
NNCa said:
Can someone please help me. How can I get to the LG device- Is there another software I can use to flash files into this device?
Thanks
Click to expand...
Click to collapse
Sorry for late reaction but i needed to think of something. Did you tryed to use another cable? Did you tryed to do it on another pc? Did you tryed to maybe install LG PC suite and see if it gets recognized? If you have the PC Suite you may need to turn it off in the LG flashtool idk. Can you tell us more like which windows you have?
wulsic said:
Sorry for late reaction but i needed to think of something. Did you tryed to use another cable? Did you tryed to do it on another pc? Did you tryed to maybe install LG PC suite and see if it gets recognized? If you have the PC Suite you may need to turn it off in the LG flashtool idk. Can you tell us more like which windows you have?
Click to expand...
Click to collapse
Hi,
I tried all you suggested, however my devide is not recognized. I tried to use the LG PC Suite and to flash by IMEI, however it is still saying that no device was connected.. I checked windows device manager, and nothing changed there.
There is any chnage I can see my connected device? use some tool or another software?
Thank you again for your patience and help!
NNCa said:
Hi,
I tried all you suggested, however my devide is not recognized. I tried to use the LG PC Suite and to flash by IMEI, however it is still saying that no device was connected.. I checked windows device manager, and nothing changed there.
There is any chnage I can see my connected device? use some tool or another software?
Thank you again for your patience and help!
Click to expand...
Click to collapse
Hi, sorry to say but you have unfortunately completely hardbricked your device. It happened to me too however I was able to get it replaced under warranty at no extra cost.
What happened was that when your phone was still detected by linux, you had a chance to recover by flashing the correct partitions to gain access to download mode and from there, flash a KDZ to go back to complete stock. However, the files you used were probably incompatible with your variant which has now corrupted your bootloader sequence. I suggest you read this reply by fizzy177 as well as the rest of the thread: http://forum.xda-developers.com/showpost.php?p=51522304&postcount=118
So right now, you cannot do anything as you have already found out, no computer will recognise that your phone is plugged in. Your phone fails to boot when you try enter the download mode and it just freezes on the splash screen which looks like this: http://www.lg-phones.org/wp-content/uploads/2014/03/image2.png
What's meant to happen is your phone should load past that initial splash screen into this http://www.androiddunya.com/wp-content/uploads/2014/01/LG-G2-DownloadMode.jpg which accepts KDZ flashing and warns the device has been rooted.
So it's a blessing that your phone cannot boot as LG cannot find out you have voided warranty and you will be able to get a replacement free of charge.
Issue was solved- device was fixed under warranty
Hi,
I just want to update you all that my device was fixed under warranty! (motherboard replacement)
Thank you all for help and great support, this is a great forum with great community :good::good:
Hello
From past 2 weeks i am wondering on internet for a solution . Hours and hours of surfing and articles but still
Hope some one solve this issue.
Okay. First i m using LG G2 F320 K update to lollipop . Non rooted. It was working fine . I can transfer files in MTP .
But about a month ago i get an update for my phone . And after some days i need to transfer some files to my phone , i wonder when i connected my phone to computer nothing happened . No notification on mobile for changing PTP MTP option . Also nothing happened in Computer device manager..
From that day i am unable to connect my phone with windows 10. It always charging mobile.
I uninstalled all drivers in device manager and installed from LG website. I updates windows N and NK MTP update from windows for windows 10.
I changed different data cables and different computers and different ports . All stuff i can do. Still no luck.
When ever i plug USB data cable it always put my Mobile on Charging . No notification on Mobile. Also i go in setting > storage> and there is no option in upper right corner to select USB PC connection .
I am in developer mode and debugging mode is on also. Also USB tethering option is Disabled .
Kindly some one help me regarding this.
LG G2 F320K updated to stock Koren lollipop 5.0.1 . Non root.( i updated lollipop in April 2015)
Issue i am facing is no notification for Charging/ MTP/PTP Usb Debugging on mobile notice bar when i attach my phone using USB cord with computer. Also in computer device manager nothing happen. Even i checked on windows 10 , 8.1, 8, 7 .
I remember it was working like charm 4 weeks before I can change MTP PTP or Charge only mode by selecting notification when i attach it to my laptop. I can transfer files can use LG PC suit .
Then i received an software update like 40 mb and i updated my mobile. That i remembered.
After that 2 weeks before i need to transfer some books from laptop to my mobile. When i plugged my device there no notification to select MTP mode . Also there is nothing happened in my windows 10. I looked in task manager. No yellow icon in computer task manager for driver thing.
Laptop is just silent and mobile is just on charging .
Then i go to setting in LG and looked for USB PC connection settings. I wonder there is nothing . Settings > storage > 3 dot in upper right corner.. it suppose to be there . But here is no 3 dot in storage. Then i looked into share and networks in android setting and i found that USB tethering. But its faded mean it is disabled and i am unable to use this feature also.
I tried on different computers different cables , original, but nothing. Always when i plug usb mobile went on charging and in all computers nothing happen in device manager.
USB debugging is on.. I factory reset device 2 times. but useless. Also i uninstall all drivers from my laptop and then reinstall drivers from LG website also i tried google drivers , ABD, different ports. Nothing nothing happen.
Also now if i try put mobile on download mode by turning device off and then push + vol button and then put cord in mobile . No download mode also it went on charging. Well charging from laptop or from charger is okay.
Hope i explain all.
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Daan_K said:
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Click to expand...
Click to collapse
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Choose an username... said:
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Click to expand...
Click to collapse
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Daan_K said:
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Click to expand...
Click to collapse
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Daan_K said:
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Click to expand...
Click to collapse
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Choose an username... said:
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Click to expand...
Click to collapse
Allright, thankyou so much my dude
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Daan_K said:
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Click to expand...
Click to collapse
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
RedWave31 said:
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
Click to expand...
Click to collapse
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Daan_K said:
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Click to expand...
Click to collapse
Sorry, I don't believe you for one second. Like litterally THOUSANDS of people here and here opening "bricked plz hlp" threads, you didn't even have the BASIC, LOWEST courtesy of writing more than 10 words of gibberish whining about your situation, without a single usefull element of context.
Proof of that in the NUMEROUS questions asked about ELEMENTARY elements about your situation. You're litterally the kind of person that would go to a car mechanic, drop the keys on the counter saying "my car is broken, fix it" and just leave without a single word added. That's RUDE and, yeah, I'm tired AF of people like you who can't READ THE DAMN XDA RULES and got NOT education whatsoever.
Nd writng frm a phone in T9 mde dsnt rlly bring nythng mre on the tble either.
Too bad you found somebody to help, as it's only encouraging that kind of behaviour.
//Rant off//
@Daan_K this EDL Tool can help https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Choose an username... said:
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Click to expand...
Click to collapse
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Daan_K said:
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Click to expand...
Click to collapse
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
IvI97 said:
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
Click to expand...
Click to collapse
Hey, a couple of things: one, i've updated the guide, it's around, much simpler to use. just saying. Two, this guy has the right driver. Don't confuse him with DFU while at least for now it is not.
Choose an username... said:
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
Click to expand...
Click to collapse
omg the triangle is gone, thankyousomuch, but what can I use now 2 fix it further?? is that in your guide maybe?
choose an username... said:
hey, a couple of things: One, i've updated the guide, it's around, much simpler to use. Just saying. Two, this guy has the right driver. Don't confuse him with dfu while at least for now it is not.
Click to expand...
Click to collapse
omygod it ****ing working, choose an username man, i can't thank you enough, seriously ur the best man lots of love for doing this
Hello guys. I have the x720 leeco. My problem is that i wiped all and no rom is installed and when i connect the phone to the pc i cant get it done with the drivers so i cant see the internal storage. I can boot on REcovery and Fastboot. Can anyone help me??
Thanks in advance
TrelosEisai said:
Hello guys. I have the x720 leeco. My problem is that i wiped all and no rom is installed and when i connect the phone to the pc i cant get it done with the drivers so i cant see the internal storage. I can boot on REcovery and Fastboot. Can anyone help me??
Thanks in advance
Click to expand...
Click to collapse
Put the rom on an USB stick, connect the stick to the phone with adapter, go into TWRP and flash the rom.
Easyest solution.
Okk i ll try it
Unlucky cant read otg, just putted an micro usb to typec adapter and a micro usb flash drive and cant see it
TrelosEisai said:
Unlucky cant read otg, just putted an micro usb to typec adapter and a micro usb flash drive and cant see it
Click to expand...
Click to collapse
Ok. Than try to flash a stock rom through all in one tool:
https://www.google.com/amp/s/forum....ment/tool-tool-one-mauronofrio-t3580611/amp/5
Oel said:
Ok. Than try to flash a stock rom through all in one tool:
https://www.google.com/amp/s/forum....ment/tool-tool-one-mauronofrio-t3580611/amp/5
Click to expand...
Click to collapse
Agreed,
You are not bricked.
i cant see my device thats the problem
TrelosEisai said:
i cant see my device thats the problem
Click to expand...
Click to collapse
Worst case you can use Qfil.
But first disconnect all unneeded peripherals, and try another cable if possible. Go read the unbricked tested and working. Search the thread for my name, to everything you need in 3 or four posts
Sent from my Pixel XL using XDA Labs
TrelosEisai said:
i cant see my device thats the problem
Click to expand...
Click to collapse
Yeah, but did you installed the all in one thing with the right drivers?
Oel said:
Yeah, but did you installed the all in one thing with the right drivers?
Click to expand...
Click to collapse
which drivers?? i cant do the qfil cause i cant see the phone in pc. when i open it in leeco logo when i connect the phone to pc it says windows cant recognize it.
TrelosEisai said:
which drivers?? i cant do the qfil cause i cant see the phone in pc. when i open it in leeco logo when i connect the phone to pc it says windows cant recognize it.
Click to expand...
Click to collapse
Go read the unbricking thread, it is going to take you days to read, understand, and finally unbrick it. If you are not seeing the device in the system manager of your computer ( Assuming you have a PC) then maybe you are actually bricked.
But, you own a phone that can be unbricked, no not a big deal. It can be resolved, the instructions in the unbricked tested and working thread are explicit go read it.
I create several how to's within that thread on unbricking, and have updated the links on the software tools needed. I have personally unbricked 7 leeco, and several others unbricked their phones by following the advice of everyone who contributed to the thread.
Everything you need and more is there that thread, waiting for you.
Go there get the files, read the instructions and soon you phone will work again. Do not download the qfil from the Original post...it doesn't work. I don't have the links to paste at the moment, nor the time to search for you Just use the thread search bar and type my name to get consolidated steps read through all of the posts, because its a progression.
There are three methods you can use to unbrick, the easiest method is probably Qfil, and Flash 2.0
Essentially you need the Qfil: le_zl1_qfil_ufs_fix , FlashOne2.0 files, go ahead and download prog_ufs_firehose_8996_ddr just in case. But it should download automatically. You need to follow the steps to get your computer ready to unbrick the phone...all in the thread instructions.
Once you do it once successfully, it will become easier with each try.
tsongming said:
Go read the unbricking thread, it is going to take you days to read, understand, and finally unbrick it. If you are not seeing the device in the system manager of your computer ( Assuming you have a PC) then maybe you are actually bricked.
But, you own a phone that can be unbricked, no not a big deal. It can be resolved, the instructions in the unbricked tested and working thread are explicit go read it.
I create several how to's within that thread on unbricking, and have updated the links on the software tools needed. I have personally unbricked 7 leeco, and several others unbricked their phones by following the advice of everyone who contributed to the thread.
Everything you need and more is there that thread, waiting for you.
Go there get the files, read the instructions and soon you phone will work again. Do not download the qfil from the Original post...it doesn't work. I don't have the links to paste at the moment, nor the time to search for you Just use the thread search bar and type my name to get consolidated steps read through all of the posts, because its a progression.
There are three methods you can use to unbrick, the easiest method is probably Qfil, and Flash 2.0
Essentially you need the Qfil: le_zl1_qfil_ufs_fix , FlashOne2.0 files, go ahead and download prog_ufs_firehose_8996_ddr just in case. But it should download automatically. You need to follow the steps to get your computer ready to unbrick the phone...all in the thread instructions.
Once you do it once successfully, it will become easier with each try.
Click to expand...
Click to collapse
Ok i am starting now i will come back with the results
As i understand my phone is not bricked cause i can go into fastboot and REcovery. The problem is i dont have OS installed so i stuck at Leeco image. The other problem is when i connect the phone with the Pc this happens on device manager. So how i can make it to see the internal storage and put inside the phone the rom.
TrelosEisai said:
As i understand my phone is not bricked cause i can go into fastboot and REcovery. The problem is i dont have OS installed so i stuck at Leeco image. The other problem is when i connect the phone with the Pc this happens on device manager. So how i can make it to see the internal storage and put inside the phone the rom.
Click to expand...
Click to collapse
Install Google's USB ADB and Fastboot drivers.
https://developer.android.com/studio/run/win-usb
Can you boot into download mode (I think it's volume down + power) and then connect to PC. After that, you should see the unknown device on device manager. Try to right-click on it and update drivers. On the next screen, select that you have drivers and you'd like to pick your own (not the Windows Update option!) Then select Manufacturer Google and Fastboot/ADB debugging option. Device might work in fastboot now, you can test by doing "fastboot devices". If that works, then you can install ROM via Fastboot.
If this doesn't work, you can revert changes by going into device manager and uninstalling the driver for that device.
Ascertion said:
Install Google's USB ADB and Fastboot drivers.
https://developer.android.com/studio/run/win-usb
Can you boot into download mode (I think it's volume down + power) and then connect to PC. After that, you should see the unknown device on device manager. Try to right-click on it and update drivers. On the next screen, select that you have drivers and you'd like to pick your own (not the Windows Update option!) Then select Manufacturer Google and Fastboot/ADB debugging option. Device might work in fastboot now, you can test by doing "fastboot devices". If that works, then you can install ROM via Fastboot.
If this doesn't work, you can revert changes by going into device manager and uninstalling the driver for that device.
Click to expand...
Click to collapse
I cant find the option for Manufacturer Google for the Fastboot/Adb debugging options
TrelosEisai said:
I cant find the option for Manufacturer Google for the Fastboot/Adb debugging options
Click to expand...
Click to collapse
Hi, sorry for the late reply.
Are you able to see these in screenshots? Between steps 2 and steps 3, you might need to select Android ADB or Android Device before you can see Google in the dropdown.
Maybe after these you might be able to see device in fastboot?