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.
I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..
Solved
Solved.
appearantly the decive announces itself slightly differently in this mode.
solution:
The aur version of adb (arch linux) handles this correctly. no drivers needed.
so for all having problems, with this device, my recommendation for now: archlinux or archbang bang live, "packer -S adb" .. "adb shell"
Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers
da root
FiltroMan said:
Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers
Click to expand...
Click to collapse
sure thing.
as always first check, that all batteries are charged. (laptop, tablet, ..)
** first you need to enable usb debugging in the menu.
** then plug it in and check on windows that it is recognized properly.
it should show up as "lenovo(or android) composite adb interface" somewhere in device manager.
otherwise tell me, and i'll try to find the proper drivers. (on archlinux it worked without drivers, so if you fail on windows for some reason, that is an option too,)
** after that you need this:
https://dl.dropbox.com/u/31794772/Root_with_Restore_by_Bin4ry_v15.rar
i don't remember where exactly i found this on xda-deverlopers. credits to whoever put that up in the first place, sry.
** choose option 1 in the script.
follow the instructions on the tool. it will ask you at some point to push restore on the tablet, no worries, this is completely intended you wont loose any data if it works right. just leave all fields blank and hit restore.
congrats, you are now rootet. the device might require a reboot and might do that from itself (dont remember)
:good:
ps: doing backup like this first is generally a good idea: http://forum.xda-developers.com/showthread.php?t=1420351
I have the a2107-F will this root process work too?
valravn said:
I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..
Click to expand...
Click to collapse
valravn,
Can you please elaborate a bit on modifying the framework.apk?
The solutions I found require flashing a whole rom which I wouldn't like to do (looks like I got the tablet with the latest FW).
Your help will be much appreciated.
Thanks.
I think i bricked my ideatab. i tried to update the CWM via ROM Manager unfortunately when i restarted the device, it got stuck on the menu showing "Press and select the Country Code". after pressing and selecting one of the choices it will just restart and return to the same menu.
Can you please help me guys? thanks in advance.
Dropped my nexus 4 yesterday and it fell right on the edge of the screen shattering it. First time I've broken a phone, and this one seems like a particularly bad one to have broken - no reasonable price screen replacement with the screen attached to the digitizer.
Anyway the phone boots up and charges fine, but I can't unlock it, which means my computer isn't connecting to it. Is there any way I can save all of my photos and other files?
Is USB debugging enabled?
Sent using xda-developers app
Chromium_ said:
Is USB debugging enabled?
Sent using xda-developers app
Click to expand...
Click to collapse
I believe so. But I have no way to check.
foofiebeast said:
I believe so. But I have no way to check.
Click to expand...
Click to collapse
To be clear, I can't check because I can't get past the lock screen. I also have no way of turning the phone off, I just have to wait until the battery runs out and then I have one chance to turn it on. I'm wondering if there is anything I can do in recovery mode that might help?
foofiebeast said:
To be clear, I can't check because I can't get past the lock screen. I also have no way of turning the phone off, I just have to wait until the battery runs out and then I have one chance to turn it on. I'm wondering if there is anything I can do in recovery mode that might help?
Click to expand...
Click to collapse
Setup adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Plug the phone in while its at the lockscreen, and run "adb devices". If the command returns the serial number of the phone let me know and I'll give you further guidance. If it doesn't it'll take a bit more work but we should still be able to get it done.
Sent using xda-developers app
Chromium_ said:
Setup adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Plug the phone in while its at the lockscreen, and run "adb devices". If the command returns the serial number of the phone let me know and I'll give you further guidance. If it doesn't it'll take a bit more work but we should still be able to get it done.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks mucho, I will try to get that set up now.
Set it up, but no devices listed
It's frustrating because it's so tantalizingly close. I have a pretty good idea that when I send it in to LG they are probably just going to send a different refurb back. I find it hard to believe that they do a 1 to 1 repair job on each phone that comes in.
foofiebeast said:
Set it up, but no devices listed
Click to expand...
Click to collapse
Alright. This is what you'll need to do: unlock the bootloader, flash cwm recovery, boot into cwm, use adb to copy the contents of your SD card to your PC.
Read this guide http://forum.xda-developers.com/showthread.php?t=2266654 . only follow the parts to unlock the boot loader and flash clockworkmod custom recovery. Make sure that you flash the recovery right after unlocking (without rebooting in between) otherwise data will get wiped. )
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone.
Sent using xda-developers app
Search for how to unlock the bootloader without wiping all your data. Would be moot otherwise...
Of course if all that's been done in the past and you already have cwm/twrp, just boot to that and you'll be able to adb in.
Also, you can hold onto the power button for 10s to force it to power down.
EDIT: restarted and tried again, making some progress now.
foofiebeast said:
Doesn't work because I can't enable usb debugging.
Click to expand...
Click to collapse
Again, that's why we go into cwm/twrp. Insecure debugging is enabled there.
Awesome, it appears to be copying everything over now!
Can't thank you enough! Just saved a years worth of pictures and videos, that pretty much chronicle the start of my current relationship up to the present.
Of course right now it is just pulling all of the EA real racing data, but I assume it will eventually get to the pictures, haha.
Chromium_ said:
Alright. This is what you'll need to do: unlock the bootloader, flash cwm recovery, boot into cwm, use adb to copy the contents of your SD card to your PC.
Read this guide http://forum.xda-developers.com/showthread.php?t=2266654 . only follow the parts to unlock the boot loader and flash clockworkmod custom recovery. Make sure that you flash the recovery right after unlocking (without rebooting in between) otherwise data will get wiped. )
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone.
Sent using xda-developers app
Click to expand...
Click to collapse
hey umm is there a way to get my contacts from the phone as well my phone is in the same situation thank you in advance
likidd said:
hey umm is there a way to get my contacts from the phone as well my phone is in the same situation thank you in advance
Click to expand...
Click to collapse
Make a nandroid backup in cwm, copy the backup to pc, then to another rooted phone, and use Nandroid Manager app to restore contacts
Sent from my Nexus 4 using Tapatalk 4
hackergnome said:
Make a nandroid backup in cwm, copy the backup to pc, then to another rooted phone, and use Nandroid Manager app to restore contacts
Sent from my Nexus 4 using Tapatalk 4
thank you but how exactly do you do that
Click to expand...
Click to collapse
likidd said:
hey umm is there a way to get my contacts from the phone as well my phone is in the same situation thank you in advance
Click to expand...
Click to collapse
you don't save as google contacts?
Hi guys, sorry to hijack a thread but i have followed the instructions above as have same issue; broken screen, no usb debugging, completely stock nexus 4. Have managed to install adb, got it working in cmd. I ran bootloader, unlocked it, DIDN'T REBOOT, just flashed my custome recovery CWM 6.0.3.6 and booted it. So now i am inside the recovery but i can't pull my media???
Any help would be greatly appreciated
Thanks
TMc1908
TMc1908 said:
Hi guys, sorry to hijack a thread but i have followed the instructions above as have same issue; broken screen, no usb debugging, completely stock nexus 4. Have managed to install adb, got it working in cmd. I ran bootloader, unlocked it, DIDN'T REBOOT, just flashed my custome recovery CWM 6.0.3.6 and booted it. So now i am inside the recovery but i can't pull my media???
Any help would be greatly appreciated
Thanks
TMc1908
Click to expand...
Click to collapse
You need to be more specific for us to help you. What do you mean by "i can't pull my media" ?
Chromium_ said:
You need to be more specific for us to help you. What do you mean by "i can't pull my media" ?
Click to expand...
Click to collapse
Apologies, i was a bit rushed. So i'm trying to get all my pics/data off my phone as my screen is smashed and i had a pattern lock on. My phone did not have usb debugging enabled. So i unlocked the bootloader, didn't do a reboot, flashed a custom recovery and then entered the recovery. However, my device isn't recognised in windows once i enter recovery and as such when i run "adb devices" no device is listed.
In the original instructions, it says:
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone
So how come once I load my recovery, when in cmd prompt, "adb pull /data/media" doesn't seem to work?
I'll be honest, i'm a little lost at this point and just really don't want to lose all my pics and thought i could get them this way before sending my phone for repair/replacement (it is insured)
Thanks for your help
TMc1908
TMc1908 said:
Apologies, i was a bit rushed. So i'm trying to get all my pics/data off my phone as my screen is smashed and i had a pattern lock on. My phone did not have usb debugging enabled. So i unlocked the bootloader, didn't do a reboot, flashed a custom recovery and then entered the recovery. However, my device isn't recognised in windows once i enter recovery and as such when i run "adb devices" no device is listed.
In the original instructions, it says:
After that boot into your newly flashed recovery and use "adb pull /data/media/" . this should copy everything on the internal sdcard of the phone
So how come once I load my recovery, when in cmd prompt, "adb pull /data/media" doesn't seem to work?
I'll be honest, i'm a little lost at this point and just really don't want to lose all my pics and thought i could get them this way before sending my phone for repair/replacement (it is insured)
Thanks for your help
TMc1908
Click to expand...
Click to collapse
Before you can run the adb pull command, you'll need to get your phone recognized by "adb devices". Try installing Koush's adb driver.
Hi,
I recently updated to the official 4.4.2 kitkat update.I then proceeded to root the phone, and then stupidly, installed CWM. I rebooted, and was greeted with an endless LG Splash screen. Now, I tried a HEAP of ways to restore to stock, all of them returning the same problem, my computer won't pick up my phone. In download mode, nothing happens, nothing in device manager, and same when I'm stuck on the LG splash screen. When I go into CWM, it then recogizes my phone, but the methods of restoring to stock won't work with CWM running in the background. CWM also won't let me mount the usb...
The methods return the same error: Phone not detected, please plug the USB cable and retry.
Ubuntu won't recognize the phone in all three modes, and another computer does the same thing. (Both Windows 8)
Methods of stock restoration tried:
-KDZ
-LGMobile support tool
-Ubuntu (This: http://forum.xda-developers.com/showthread.php?t=2582142)
Can anyone help?
MintLord said:
Hi,
I recently updated to the official 4.4.2 kitkat update.I then proceeded to root the phone, and then stupidly, installed CWM. I rebooted, and was greeted with an endless LG Splash screen. Now, I tried a HEAP of ways to restore to stock, all of them returning the same problem, my computer won't pick up my phone. In download mode, nothing happens, nothing in device manager, and same when I'm stuck on the LG splash screen. When I go into CWM, it then recogizes my phone, but the methods of restoring to stock won't work with CWM running in the background. CWM also won't let me mount the usb...
The methods return the same error: Phone not detected, please plug the USB cable and retry.
Ubuntu won't recognize the phone in all three modes, and another computer does the same thing. (Both Windows 8)
Methods of stock restoration tried:
-KDZ
-LGMobile support tool
-Ubuntu (This: http://forum.xda-developers.com/showthread.php?t=2582142)
Can anyone help?
Click to expand...
Click to collapse
Have you tried adb sideload
raahult said:
Have you tried adb sideload
Click to expand...
Click to collapse
I don't know how to do that, And no, I don't think I have. Could you give me a guide on doing that?
MintLord said:
I don't know how to do that, And no, I don't think I have. Could you give me a guide on doing that?
Click to expand...
Click to collapse
Install http://forum.xda-developers.com/showthread.php?t=2588979
then go to recovery and try adb devices on command prompt on your PC to check if your device is listed
if it shows your devices then just search any thread that tell how to push flashable rom to your device.
raahult said:
Install http://forum.xda-developers.com/showthread.php?t=2588979
then go to recovery and try adb devices on command prompt on your PC to check if your device is listed
if it shows your devices then just search any thread that tell how to push flashable rom to your device.
Click to expand...
Click to collapse
No luck...
raahult said:
Install http://forum.xda-developers.com/showthread.php?t=2588979
then go to recovery and try adb devices on command prompt on your PC to check if your device is listed
if it shows your devices then just search any thread that tell how to push flashable rom to your device.
Click to expand...
Click to collapse
Wait, I got it working!
MintLord said:
Wait, I got it working!
Click to expand...
Click to collapse
Was your phone able to connect to the PC afterwards? I have a D800 that I am unable to get any PC to recognize. I need to restore it to stock but no matter what I do it does not show up in device manager (and I have a working rom on it).
crawlgsx said:
Was your phone able to connect to the PC afterwards? I have a D800 that I am unable to get any PC to recognize. I need to restore it to stock but no matter what I do it does not show up in device manager (and I have a working rom on it).
Click to expand...
Click to collapse
Yes, it does work now. I was able to restore to stock by adb pushing phillz recovery, and then flashing that, then adb pushing the stock ROM. Everything works as it should, now.
MintLord said:
Yes, it does work now. I was able to restore to stock by adb pushing phillz recovery, and then flashing that, then adb pushing the stock ROM. Everything works as it should, now.
Click to expand...
Click to collapse
Ah nice. Unfortunately I can't get device manager to see mine at all so I can't even ADB .
crawlgsx said:
Ah nice. Unfortunately I can't get device manager to see mine at all so I can't even ADB .
Click to expand...
Click to collapse
Does it recognize your phone when it's in the custom recovery? That was the only way I could do it on my phone.
Good luck!
I tried ADB devices nothing came out.
I have the same problem as listed in this thread. Tried everything to SHort circuit the chip. Basically everything.
I think the last thing i haven't try is dump it into the bin.
MintLord said:
Does it recognize your phone when it's in the custom recovery? That was the only way I could do it on my phone.
Good luck!
Click to expand...
Click to collapse
On TWRP it's detect my phone as "LGE Android MTP device" and i can't copy anything from my PC to my phone,
I can't ADB push too, it was error Read-only system
Any ideas?
Hi, sorry to post in this 1 year old post buy mt G2 is totally dead, I can sometimes get LG Logo and the main problem is i cannot get it into QHS-USB mode or anything.
Is there any key combinaison to do that ?
Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
kjtay said:
Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
Click to expand...
Click to collapse
Under device manager, what is listed as your phone?
Ajxx16 said:
Under device manager, what is listed as your phone?
Click to expand...
Click to collapse
Unknown Device... It is worth noting that I have used Wugs Toolkit and followed every set of directions to a T. This includes a PC that that has never had my phone in it before. Followed all the steps before I even tried to connect. Also, both PC machine indicate that I have installed the most update driver.
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Ajxx16 said:
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Click to expand...
Click to collapse
I have tried all usb ports and a different usb cord. My OS is gone, so I was hoping to find some way to install a rom or stock. I am at a loss!
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Ajxx16 said:
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Click to expand...
Click to collapse
I do if I understand the term correctly. I am at the android "start" screen and underneath the android it says
Fastboot Mode
Product_Name - mako
lock state - unlocked
Now what?
Connect it to your computer, and I assume you have fastboot and adb set up correctly. In command prompt type fastboot devices and see if your phone is listed, should give the serial and say fastboot next to that
Not sure if I know how to set up adb correctly... as far as fastboot goes.. I assume that is set up correctly. Would adb work if the PC doesn't recognize my phone?
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Ajxx16 said:
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Click to expand...
Click to collapse
Don't mean to sound like an idiot (may be too late for that), but do you mean fastboot recognized on my PC when I plug in my phone? Or does is say fastboot on my phone? PC does not recognize my phone, but it does say fastboot enabled on my phone.
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Ajxx16 said:
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Click to expand...
Click to collapse
I can't get the PC to recognize the phone. The phone is in fastboot mode. It is looking mighty grim!
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Ajxx16 said:
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Click to expand...
Click to collapse
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Ajxx16 said:
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Click to expand...
Click to collapse
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
kjtay said:
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
Click to expand...
Click to collapse
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Ajxx16 said:
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Click to expand...
Click to collapse
I am pretty certain I have the proper drivers installed on 3 computers. Not a single one recognizes the device. I suppose it is possible that it is a hardware issue? If I can figure a way to the computer to recognize the phone I am certain I can save it. Right NOTHING has worked.