Related
I'm following the [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9023 and i9020A) but I get stuck after step 13, I don't see any "android bootloader interface" so I can't select it.
Also the icon for "Android 1.0" on my device manager window has a yellow/black exclamation mark. Though I should mention that.
What do I do now?
Try This
I believe the yellow exclamation mark is to alert you that the driver is not working/installed properly. After clicking "Let me pick...", do you see a button marked "Have Disk..."? If so, click that, click browse and go to where you downloaded the google usb drivers and select "android_winusb.inf".
Hope that helps.
i've had the same issue when rooting my ns, what you need is "pdanet for android"
sorry im a newb, cant give you the url..
just google ,the first one is it. installing this fixes the driver problem, though this software is for something else.
ikika87 said:
I believe the yellow exclamation mark is to alert you that the driver is not working/installed properly. After clicking "Let me pick...", do you see a button marked "Have Disk..."? If so, click that, click browse and go to where you downloaded the google usb drivers and select "android_winusb.inf".
Hope that helps.
Click to expand...
Click to collapse
Thank you! This work, but now I'm stuck on "Part 4: Root" step 6. Every time I type in adb push su-2.3.6.1-ef-signed.zip /sdcard/su-2.3.6.1-ef-signed.zip it says device not found.
Thanks for all the help so far.
Allright I got it to work somehow. I got it stuck after when I would go to recovery and I'd see the android + exclamation mark. Turns out you lose the clockwork mod when you reboot?
How do I keep it clockwork mod? I tried the cmd commands, but it returns
device not found
for example if I type adb shell, it returns device not found.
I attempted to root my friends Nexus S this weekend and I had no idea what i was setting myself up for! This is crazy how much work has to be done to root this damn phone lol. I have an epic and its literally a few seconds and you are done.
I got stuck after it asked me to download a special java package and i did but it still didnt recognize it.
Ingeminiac said:
Allright I got it to work somehow. I got it stuck after when I would go to recovery and I'd see the android + exclamation mark. Turns out you lose the clockwork mod when you reboot?
How do I keep it clockwork mod? I tried the cmd commands, but it returns
device not found
for example if I type adb shell, it returns device not found.
Click to expand...
Click to collapse
if you are on stock , then yes you will lose the recovery.
follow the instructions i posted here.
http://forum.xda-developers.com/showpost.php?p=14076068&postcount=6
keep in mind you have to rename the update-recovery.sh cause on rebooting this file will cause the stock recovery to be flashed back.
goblue30093 said:
I attempted to root my friends Nexus S this weekend and I had no idea what i was setting myself up for! This is crazy how much work has to be done to root this damn phone lol. I have an epic and its literally a few seconds and you are done.
I got stuck after it asked me to download a special java package and i did but it still didnt recognize it.
Click to expand...
Click to collapse
it is nopt as hard as it looks like. i believe this guide is quite useless and complicates stuff. an example is that it says after flashing recovery. you should use adb to push ur su file to the sdcard. why complicate stuff when u could just from recovery , mount the sdcard and drag the file there with ur mouse!
Ingeminiac said:
I'm following the [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9023 and i9020A) but I get stuck after step 13, I don't see any "android bootloader interface" so I can't select it.
Also the icon for "Android 1.0" on my device manager window has a yellow/black exclamation mark. Though I should mention that.
What do I do now?
Click to expand...
Click to collapse
Forget this crap go to Nexus S Android Dev forum a new one click root method has been applied for 2.3.4. See me there
Sent from my Nexus S 4G using XDA App
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.
This is what happens :
1. When I normally turn my N7 on , it goes throught the google logo and gets stuck on the ROM logo .
2. I can get into the bootloader when the USB is plugged off , but i cant get into recovery it just gets stuck on the google logo .
3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected . (if i get into the bootloader when the USB is allready connected it gets in the bootloader main screen but i cant move) .
So i cant flash , get into the rom or return to stock .
ANY IDEAS ?? please help me :crying::crying:
Bump
Definitely not bricked since of powers on. Fastboot flash the stock image and you should be good as new.
Sent from my Nexus 7 using Tapatalk 2
Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?
brGabriel said:
Strange, it shouldn't make a difference whether your USB is plugged or not when trying to get to the recovery.
If you get into the fast boot menu or "boot loader main screen" and you press the volume down button a few times you get no response? Sometimes it takes a few seconds for mine to switch to recovery,etc.
Also, what caused your tablet to get stuck in that state?
Click to expand...
Click to collapse
If I press the volum dowm bottom while on fast boot menu I can move around the menu if the usb is plugged off , but I can only shutdown or restart the fastboot since the start and recovery options just gets stuck on the google/rom logo if it is plugged in I just gets stuck in the menu and I cant even scroll . yea I waited about half an hour on the google logo trying to get to my recovery and nothing happened .
I JUST DONT KNOW WHAT I DID ! I really dont ! I am an experienced flahser and had been so for almost 2 years now ! I just left my N7 on the table and didnt touch it at all for a week and when I tried to turn it on after that I just got that prob . but I did nothing related to flashing or so - it just happened by staying at the table !
any help ?? PLEASE
I CANT RETURN TO STOCK , if i plugg in the usb fastboot gets stuck .
have you tried charging it on the wall charger to make sure the battery has got a full charge, don't know, just throwing out options
Hmmm, well at least you're able to boot the tablet and get to fastboot menu so its not a hard brick. Sounds like a corrupted partition of sorts if you can't get into ROM or recovery. Someone with more expertise might have a possible solution. I wouldn't lose hope yet.
yes , i did charged it to full batt .
i can get into fastboot but not rom or recovery and when i plugg in usb i have no fastboot , doesnt that mean i wont ever be able to flash ?
if i will make a vid of the prob it will help ?
Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7
Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD
i've had good luck with mskip's toolkit in a similar situation
veeman said:
Get to boot loader and do
fastboot flash recovery C:\File path to recovery on computer
Once you have a recovery installed you can push a ROM to your Nexus via adb.
Sent from my Nexus 7
Click to expand...
Click to collapse
xfrancis14 said:
Or you can always use wugfreshs toolkit and click flash back to stock option and check device won't boot, the same thing happened to me awhile ago and the bootloader problem is cause you have the old bootloader the knew 4.13 bootloader fixed that
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post
rkiller51 said:
Guys , I told you that my bootloader gets stuck when I connect the usb - so how can I possibly flash anything ? please read the whole post
Click to expand...
Click to collapse
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
veeman said:
It says you can get to the boot loader with the cable unplugged. So get to the boot loader and then plug in the USB.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
Click to expand...
Click to collapse
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?
rkiller51 said:
Are you kidding ? "3.If I plug my USB in while in the bootloader the bootloader gets stucked and i cant move around in it or flash anything , but my PC recognize that an android device is connected ."
I really appreciate any kind of help, but why even write and answer when you didnt even fully read the question ?
Click to expand...
Click to collapse
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...
TMan459 said:
Lol just calm down man we're all just trying to help you!
Now, you need to get your N7 into the bootloader, it does not matter if you can't navigate the bootloader on your N7. Once in the bootloader, connect the N7 to your computer with the USB cable.
Once you're connected, make sure you've downloaded the Android SDK and open a command prompt. Navigate your command prompt (make sure you ran that command prompt as administrator) to the "platform-tools" directory.
Once in the platform-tools directory run the following command without quotes:
"fastboot devices"
It should return the serial number for your device, indicating that fastboot sees your N7 and can work with it.
After that type
"fastboot flash recovery *.img"
You'll need to head to clockworkmod.com to download the N7 recovery image. Place the downloaded image in the platform-tools directory and replace "*.img" with the filename of the recovery image you downloaded.
That's it! Unplug your N7 and go into recovery, and sideload whatever ROM you want!
Let us know how it goes!
PS: If fastboot devices shows nothing, we have a bigger problem...
Click to expand...
Click to collapse
Its hard to be calm then you new N7 is dying :/
somthing like this ? (pic attached)
If i did everything like you said it means i do have the bigger prob help me!
OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!
TMan459 said:
OK. Next thing is to ensure your N7 is properly detected in Windows.
Just head to the device manager. You should see Original Android Interface or something along those lines.
Report back with a screenshot, those are very helpful!
Click to expand...
Click to collapse
Here you go (attached) ! you have everything you need mate ?
I really appreciate the help ! :good::good:
I had similar issues and was able to get back to stock using WugFresh's Nexus Root Toolkit. Highly recommended!
From the same command Window, in the same platform - tools directory, does adb devices show your device?
I'm not the lowest of the low, but I am the slowest of the slow.
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!
Hey everyone!
Just a few days after ordering a different phone which should get here tomorrow, I managed to drop my N4 and shatter the screen. The screen 'works' but the digitizer's broken below the crack so I can't get past the lock screen. I'm running Cyanogen mod and I honestly just want to get a few files off and update a few things onto drive so I can move to my new phone.
I was really hoping USB OTG would work, but I tried an external mouse with the right cable and the cursor wasn't showing up.
I don't think I have debugging mode enabled unless it carries forward if you update cyanogen. I do have CWM recovery 6.0.5.1. I tried mounting the drives through this, but it sadly didn't show up.
Is there any way I can enable USB OTG or get the files off without replacing the screen assembly? I tried using ADK Studio but I couldn't even get the command prompt open... If anyone has a link to a good walkthrough for this or suggestions for what I can do I'd be really grateful. Is there any way to force the USB OTG driver onto the phone? If I can use a USB keyboard/mouse combo to get everything off that would be the simplest way I think. Or if there's some way to get into the phone and have the display show up through my monitor, then that'd be great too.
Thanks a lot. I really appreciate any help.
You could try flashing twrp in place of cwm to mount the data partition.
audit13 said:
You could try flashing twrp in place of cwm to mount the data partition.
Click to expand...
Click to collapse
I can hit mount and unmount through CWM but nothing seems to happen. Nexus shows up as an empty device.
How would i flash TWRP at this point? Is there a way to push a zip into the phone if I can't get into it?
ridethecliche247 said:
I can hit mount and unmount through CWM but nothing seems to happen. Nexus shows up as an empty device.
How would i flash TWRP at this point? Is there a way to push a zip into the phone if I can't get into it?
Click to expand...
Click to collapse
If your physical buttons work then simply boot into fastboot by holding volume down and power and flash a TWRP recovery via fastboot. I've never had luck with CWM when it comes to reading files. TWRP opens up Android File Transfer right away on my Macbook when I connect it (Should do the same for Windows, not sure what OS you use)
fireball0093 said:
If your physical buttons work then simply boot into fastboot by holding volume down and power and flash a TWRP recovery via fastboot. I've never had luck with CWM when it comes to reading files. TWRP opens up Android File Transfer right away on my Macbook when I connect it (Should do the same for Windows, not sure what OS you use)
Click to expand...
Click to collapse
This seems promising, but how would I get it in via fastboot? Sorry I've never used fastboot before, but use the power+vol down command pretty often.
Would that also allow me to flash in the zip for USB otg once I'm in?
ridethecliche247 said:
This seems promising, but how would I get it in via fastboot? Sorry I've never used fastboot before, but use the power+vol down command pretty often.
Would that also allow me to flash in the zip for USB otg once I'm in?
Click to expand...
Click to collapse
Ok, you will want to be on your computer to do this. Download the latest TWRP recovery, which is here, you'll want to download the twrp-3.0.0-0-mako.img at the top of the list. You'll then have to open up fastboot in terminal/command prompt, and when you boot into your bootloader by holding volume down+power, connect your N4 and first I would type fastboot devices to make sure that your computer is recognizing that it's attached. Next type fastboot flash recovery twrp-3.0.0-0-mako.img and afterwards use the volume buttons to navigate and reboot to recovery. From there see if it connects to your computer and you can view files and if not, move forward with the USB otg. I have no experience with USB otg so I can't help you there, but hopefully this helps out at the very least!
fireball0093 said:
Ok, you will want to be on your computer to do this. Download the latest TWRP recovery, which is here, you'll want to download the twrp-3.0.0-0-mako.img at the top of the list. You'll then have to open up fastboot in terminal/command prompt, and when you boot into your bootloader by holding volume down+power, connect your N4 and first I would type fastboot devices to make sure that your computer is recognizing that it's attached. Next type fastboot flash recovery twrp-3.0.0-0-mako.img and afterwards use the volume buttons to navigate and reboot to recovery. From there see if it connects to your computer and you can view files and if not, move forward with the USB otg. I have no experience with USB otg so I can't help you there, but hopefully this helps out at the very least!
Click to expand...
Click to collapse
Ive had issues in the past trying to get the terminal to open. Do you have a link that could help?
Thanks so much!
ridethecliche247 said:
Ive had issues in the past trying to get the terminal to open. Do you have a link that could help?
Thanks so much!
Click to expand...
Click to collapse
Do you use Windows, Linux, or OS X?
fireball0093 said:
Do you use Windows, Linux, or OS X?
Click to expand...
Click to collapse
Windows.
ridethecliche247 said:
Windows.
Click to expand...
Click to collapse
Take a watch through this entire video, it's the most in depth one I can find that actually gives examples on things dealing with ADB and of course Fastboot. Make sure that the recovery .img is in the same directory that the fastboot prompts are in. If I didn't use OS X I'd walk you through it myself but I apologize there because I know the setup and way you enter commands is slightly different on Windows xD
Thank you! I'll give it a try!
ridethecliche247 said:
Thank you! I'll give it a try!
Click to expand...
Click to collapse
Just quick popping in to see how the progress is on it. Any luck at all?
fireball0093 said:
Just quick popping in to see how the progress is on it. Any luck at all?
Click to expand...
Click to collapse
I have finals next week so I was going to give it a try afterwards or if I get a study break. I'll definitely keep you posted on this thread though.
Thanks again!