Related
Nexus 7
Android 4.1.2 JZ054K
using Nexus Root Toolkit v1.5.5
I've done: 1. Initial setup- full drive installation
2. backup
3. Unlock
everything went as expected according to the procedure.
4. the Root, it went through it procedure until it got to:
--waiting for your device to finish booting back up...---
been waiting on this screen forever, the Nexus 7 screen shows the android w/ the "Start" tab.
done this procedure several times w/ Nexus Root Toolkit v1.5.4 and several time w/
Nexus Root Toolkit v1.5.5
nothing has changed, don't know if my Nexus 7 is unlocked or rooted.
pls help. any ideas, suggestions...
thanks in advance
Try to reset the device to factory and try again. Take it slow and make sure you're following each step.
If all else fails, Google, Google, Google...
Good luck
I had this same issue today when rooting my new 32gb Nexus 7. Wug's tool wasn't autoselecting the right version (4.1.1 when I had 4.1.2) and it was doing the same thing, hanging on the "waiting for your device to reboot" message. Make sure the firmware version on the Nexus matches the version Wug's tool is detecting.
zombiest said:
I had this same issue today when rooting my new 32gb Nexus 7. Wug's tool wasn't autoselecting the right version (4.1.1 when I had 4.1.2) and it was doing the same thing, hanging on the "waiting for your device to reboot" message. Make sure the firmware version on the Nexus matches the version Wug's tool is detecting.
Click to expand...
Click to collapse
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
HTH.
Zaphod
No success on this issue!!
zaphodmuc said:
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
HTH.
Zaphod
Click to expand...
Click to collapse
I did the same but my Nexus4 can't be booted up by the NRT v1.6.3!!
It stays on "waiting for you device to finish booting back up"
Pls somebody help..
Thank you.
Same Issue
mike_24_11 said:
I did the same but my Nexus4 can't be booted up by the NRT v1.6.3!!
It stays on "waiting for you device to finish booting back up"
Pls somebody help..
Thank you.
Click to expand...
Click to collapse
I have been trying the NRT 1.6.3. The issue of Waiting for your device to finish booting back up.... repeats.
No solution yet.
mike_24_11 said:
I did the same but my Nexus4 can't be booted up by the NRT v1.6.3!!
It stays on "waiting for you device to finish booting back up"
Pls somebody help..
Thank you.
Click to expand...
Click to collapse
So.....you come into the Nexus 7 forums to try and get help with your Nexus 4......OK
ananiah2011 said:
I have been trying the NRT 1.6.3. The issue of Waiting for your device to finish booting back up.... repeats.
No solution yet.
Click to expand...
Click to collapse
Dont use a toolkit, its that simple. In the amount of time you have wasted on that toolkit, you could have learned the manual method and realized it wasnt as hard as you thought
Booyah
zaphodmuc said:
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
HTH.
Zaphod
Click to expand...
Click to collapse
Thanks!!! worked like a charm
Bohefus said:
Thanks!!! worked like a charm
Click to expand...
Click to collapse
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
Where do I change the USB connection from MTP to PTP . I mean where do I find the dropdown on the device or on in the program?
I can't find any USB settings. I will probably feel a little stupid when I'm told where to find these settings but I'd been knocking my head against the wall long enough
ibbeebee said:
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
Where do I change the USB connection from MTP to PTP . I mean where do I find the dropdown on the device or on in the program?
I can't find any USB settings. I will probably feel a little stupid when I'm told where to find these settings but I'd been knocking my head against the wall long enough
Click to expand...
Click to collapse
kind of like the one located in Settings>storage>menu>USB Connection?
Pirateghost said:
kind of like the one located in Settings>storage>menu>USB Connection?
Click to expand...
Click to collapse
Well I probably would never have found the setting without help, I couldn't find anything called menu so I tried the 3 dots next to the search button, Bingo the jackpot!. Now to see if I can back up the device .
I may be back but let's hope not
Well I'm back!!
I have been through the driver config Guide & the new drivers seem to be installed But I can't see my tablet in explorer anymore & my Device is open in a screen I haven't seen before
A big button at the top of the screen
START
then an up & down arrow
FastBoot Mode
Variant -flo32C
HW VERSION -rev_e
BOOTLOADER VERSION - FLO-04.04
CARRIER INFO - NONE
SERIAL NUMBER -07e1eda6
SIGNING -yes
Secure BOOT - enabled (in green)
LOCK STATE - unlocked
& I'm rather nervous about touching any of it
I'm about to start the driver process again but will wait for some advice
OK I did not follow my own advice & have rebooted the device & it has loaded normally& is now viable on my computer again .
I will wait for some feedback before proceeding Thanks in advance for any assistance Regards Beebee
Hi I repeated the process & have success at last.
I have backed up the device & am about to root it.
What are the advantages & disadvantages of ticking Custom Recovery . I've done a Google search but I finish up being sidetracked for hours when I do that So will just ask you
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!
hello all, im a noob and think my phone is good enough to throw in the garbage. you tell me!!
so i use my vs980 on tmobiles network and only get at best hspa so i tried to throw a tmobile stock rom on my vs980 to try and get 4g ive seen people doing it i was hesitant but did it anyway. i had a zip for a verizon kernel now the rom installed successfully but the kernel didnt i meant to try to restore a backup but accidentally hit reboot and now every time i power on my phone i get black screen
fastboot mode started
reset
portchange
reset
portchange
fastboot processing commands
cant get into twrp with two button combo cant do a factory reset, infact that has changed looks a bit different than it used to, assuming its a tmobile factory reset screen
i tried to do the kdz and tot method to return to stock aswell phones not recognized for either method
i installed ubuntu on virtual box to try and push recovery.img, laf.img, aboot.img. boot.img. etc but phones not recognized in terminals fastboot says <waiting for device> any way to get ubuntu to recognize my device? any special drivers i need?
ive searched high and low for a solution im so exausted and could really use some veterans help please help this noob out... thanks in advance for any help from you guys!!
anyone?
pete022682 said:
hello all, im a noob and think my phone is good enough to throw in the garbage. you tell me!!
so i use my vs980 on tmobiles network and only get at best hspa so i tried to throw a tmobile stock rom on my vs980 to try and get 4g ive seen people doing it i was hesitant but did it anyway. i had a zip for a verizon kernel now the rom installed successfully but the kernel didnt i meant to try to restore a backup but accidentally hit reboot and now every time i power on my phone i get black screen
fastboot mode started
reset
portchange
reset
portchange
fastboot processing commands
cant get into twrp with two button combo cant do a factory reset, infact that has changed looks a bit different than it used to, assuming its a tmobile factory reset screen
i tried to do the kdz and tot method to return to stock aswell phones not recognized for either method
i installed ubuntu on virtual box to try and push recovery.img, laf.img, aboot.img. boot.img. etc but phones not recognized in terminals fastboot says <waiting for device> any way to get ubuntu to recognize my device? any special drivers i need?
ive searched high and low for a solution im so exausted and could really use some veterans help please help this noob out... thanks in advance for any help from you guys!!
Click to expand...
Click to collapse
thats not even close to a hard brick it is in bootloader mode do not let it die keep it plugged in because if the battery dies then you have a real big problem im not sure what to do after this but i know you dont want the battery to die
well that's reassuring
Keeping phone plugged in. Now if I can get some tips as to why I cant get it to communicate with ubuntu in this bootloader mode to push the files I need. Any help anyone? Please. Where I go from here?
link - windows
Tried putting laf.IMG in your script folder bender it brought cmd to<waiting for device> my comp won't communicate with my phone for some reason. Am I missing any special drivers?
pete022682 said:
Tried putting laf.IMG in your script folder bender it brought cmd to<waiting for device> my comp won't communicate with my phone for some reason. Am I missing any special drivers?
Click to expand...
Click to collapse
Just install lg drivers - if it doesn't work then download adb drivers..
+please see the device manager for new devices and "not installed drivers"
+ look here
I will try when I get home thanks for your help so far at work no computer access. Thanks again bender I will let you know how everything goes.
bender_007 said:
Just install lg drivers - if it doesn't work then download adb drivers..
+please see the device manager for new devices and "not installed drivers"
+ look here
Click to expand...
Click to collapse
if you manage to install the driver the rest should go easy.
It's weird, on some systems it wont install the driver properly(adb) but google nexus driver installs fine.
i was hoping so
bender_007 said:
if you manage to install the driver the rest should go easy.
It's weird, on some systems it wont install the driver properly(adb) but google nexus driver installs fine.
Click to expand...
Click to collapse
so this is where were at bender....
got drivers installed, phone is being recognized...
pushed laf.img with your script...GOT DOWNLOAD MODE BACK!!yes, progress...
went to factory restore with .TOT method.....FAILED
shows PID#, IMEI#, MODEL,D801 DLL VS980 SBUV Xdabbeb's vs98024a 1.1.1 11 SWOV Xdabbeb's vs98024a 1.1.1 11 device doesn't match
ideally i would love to just turn this vs980 into a d801 stock kitkat by pushing all nessassary d801 files would that work what would be my options here?
How do i fastboot flash open recovery twrp IMG?
Ultra brick G2 vs980! T_T
Good night lords of XDA!
I come to you after exhausting all that I could find and try, hope you can enlighten me, you would save a new G2 that is about to become a gleaming brick:
Summary: I have in hand a Verizon LG G2 vs980, with the intention of using it in Spain. After a bad flash a ROM for a different model, you could not access recovery mode or download mode, only fastboot.
Thanks to this great tutorial, I could flash by ADB and fastboot files an official ROM for this G2, but after a correct process, the G2 restarted and only shows "Security error" before shutting ...
I still do not have access to recovery or download, and now not to fastboot. Only allows me to access the screen "Factory reset", but in doing nothing changes.
How could re-flash a recovery or something like that allows me relive my G2?
Thank you very much in advance. You are my salvation. XD
PS: I apologize for any clerical error or misused term. I do not usually write in English.
Click to expand...
Click to collapse
Sorry, wrong thread. XDD
I have a Nexus 7 2012 (KOT49H, nakasi) which will only boot into fastboot, but not to Android.
I don't know what caused this - when it happened first I rebooted, and it worked again for another couple of days, then I got a "Google Play Services has stopped" message, so I tried to power off and reboot the tablet.... and it won't reboot!
At that time I was unaware that such a thing as USB debugging existed, so it's not been set... Indeed all I know about these problems now is what I've found out here... so sorry if I test your patience!
What I have done:-
I have tried a factory reset, with no effect.
Tried Wug's toolkit, which was unable to do anything (as USB debugging not set?)
(Windows 7 appears to have the drivers for this - it appears in Device Manager as Google Nexus 7 Bootloader interface)
Tried Skipsoft's Toolkit, which succeeded in unlocking the bootloader, and I have flashed images (downloaded from google) for Boot and System to the appropriate partitions... still nothing! Flashing the bootloader image failed ("An error occurred")
Is this Nexus destined for the dustbin? It is, of course, out of warranty :crying:
Apologies if I've done something daft, but I'm getting desperate...
Can anybody help?
Many thanks
hEY,
i got the same. I tried to install cm11 and i format sd card and happens that i formated the system too.
Now i can only to restart in revory "cwm v6.0.5.0" but cant start in download modus with Power+down (see only GOOGLE LOGO with open lock sign).
With wugs fresh i got the same with the f**** usb debugging enable thing, i cant get into nothing only in cwm.
I would be sooo happy to find a tool like (adb-tool) how i can put files again on my nexus 7.
thank you guys in advance!
beaquoy said:
I have a Nexus 7 2012 (KOT49H, nakasi) which will only boot into fastboot, but not to Android.
I don't know what caused this - when it happened first I rebooted, and it worked again for another couple of days, then I got a "Google Play Services has stopped" message, so I tried to power off and reboot the tablet.... and it won't reboot!
At that time I was unaware that such a thing as USB debugging existed, so it's not been set... Indeed all I know about these problems now is what I've found out here... so sorry if I test your patience!
What I have done:-
I have tried a factory reset, with no effect.
Tried Wug's toolkit, which was unable to do anything (as USB debugging not set?)
(Windows 7 appears to have the drivers for this - it appears in Device Manager as Google Nexus 7 Bootloader interface)
Tried Skipsoft's Toolkit, which succeeded in unlocking the bootloader, and I have flashed images (downloaded from google) for Boot and System to the appropriate partitions... still nothing! Flashing the bootloader image failed ("An error occurred")
Is this Nexus destined for the dustbin? It is, of course, out of warranty :crying:
Apologies if I've done something daft, but I'm getting desperate...
Can anybody help?
Many thanks
Click to expand...
Click to collapse
smoschi said:
I would be sooo happy to find a tool like (adb-tool) how i can put files again on my nexus 7.
Click to expand...
Click to collapse
If you have wugs, you already have the adb tool on your computer. Look in the wugs directory. However it sounds like your drivers are messed up. If that is the case nothing is going to work until you get that corrected.