Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!
Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.
RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks
I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.
To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!
To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)
The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.
To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)
Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed
cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!
To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!
What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.
To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?
To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?
What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App
Related
Hey guys, first time on here and im kinda a noob when it comes to the rooting stuff (ive done a few things but nothing hardcore) and i need some help getting onto this (IMM76K) update (and not sure if this is the right thread to put this in). A few weeks ago i unlocked my bootloader and (after some of the same issues im having now) temp booted into CWM and installed the 4.0.4 IMM30B update. Now with this new update, i wanted to get it installed or flash back to get the OTA (not sure if i can get the OTA on the leak update)
But, everytime i try to boot into CWM again (using this toolkit: http://forum.xda-developers.com/show....php?t=1614827) i constantly get fail messages. And it happens if i try to boot into CWM or try to flash the factory 4.0.2 update.
With the phone on and trying to use these (http://www.droid-life.com/2011/12/16...factory-state/) instructions, i constantly get the error "sending 'bootloader'... FAILED (remote: Invalid Command)". Im already in the fastboot bootloader.
With the toolkit, it wont start the factory img flash if the phone is on, and if im in the fastboot bootloader, it says it "fails" to boot into the bootloader (which, again, im already in) and fails to install all the img files and then just boots back into the older 4.0.4 leak.
I havent rooted my phone (but i tried that to get past this problem but i get the same error messages), only unlocked the bootloader. Sorry for the long post and if it seems like a block of text. This is just starting to really frustrate me. Thanks
Do you have ADB installed on your computer? It's hard to troubleshoot your problem if you don't.
Yea, i do. Im in school for programming and have installed all the android SDK stuff and eclipse since i want to make android apps/games (hopefully). I downloaded the fastboot.exe file and have it in the platform-tools folder with the adb.exe file
Go here (https://developers.google.com/android/nexus/images) and download mysid for Gnex.
It's gzipped so you will need to extract those files using 3rd party software (winzip works nicely).
Boot your phone normally. Connect to your computer and open a command prompt.
Type 'adb devices' and note the result.
Type 'adb reboot bootloader' and wait for the phone to enter the bootloader.
Once there type 'fastboot devices'.
If you don't get a response you have a driver problem. You need to DL the samsung driver.
If you do, flash each zip file in that package you DL'ed from google.
Start with 'fastboot flash bootloader <location of bootloader zip>'
Then, 'fastboot flash radio <file>'
ect. until you've flashed all the zip files. (Exactly like the instructions in your link but replace the files they gave you with the ones from google.)
Post here if you get an error message.
Ok, everything is fine until i get to flashing the bootloader, heres what i get (sorry it isnt an image)
D:\Android\android-sdk\platform-tools>adb devices
List of devices attached
0146A5B30300B014 device
D:\Android\android-sdk\platform-tools>adb reboot bootloader
D:\Android\android-sdk\platform-tools>fastboot devices
0146A5B30300B014 fastboot
D:\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-toro-
primekk15.img
sending 'bootloader' (2308 KB)... FAILED (remote: Invalid Command)
finished. total time: 0.001s
D:\Android\android-sdk\platform-tools>
This is what happens even when i use a toolkit to do it for me. Ive used the toolkit to reinstall the drivers a bunch of times and it still happens
Did you relock the bootloader? Type 'fastboot oem unlock'
---------- Post added at 09:07 AM ---------- Previous post was at 08:57 AM ----------
If that's not it then it's a driver issue.
Uninstall the ones you have (Control Panel -> Device Manager) and go to http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW? and install the samsung ones.
If you have problems with that I can walk you though it.
The only thing i was able to do from the toolkits was lock/unlock the bootloader (tried that last night using the toolkit to see if it fixed any problems). ill try installing the drivers and see what happens, thanks
edit: *I locked the bootloader last night and unlocked it again right after
blipp said:
The only thing i was able to do from the toolkits was lock/unlock the bootloader (tried that last night using the toolkit to see if it fixed any problems). ill try installing the drivers and see what happens, thanks
edit: *I locked the bootloader last night and unlocked it again right after
Click to expand...
Click to collapse
1) Throw away the toolkit;
2) Uninstall all drivers;
3) Install these drivers;
4) Make sure your bootloader is unlocked;
5) Open a command prompt in the directory where your both your fastboot file and CWM are located;
6) Reboot your device into fastboot mode (vol+ & vol- & power), and plug into your PC;
7) Make sure your device is recognized by your PC: fastboot devices
8) Flash or boot CWM
a) Flash by typing: fastboot flash recovery cwm.img
b) Boot by typing: fastboot boot cwm.img
sorry for being a noob at this, but where do i put the Universal Naked Driver stuff? Do i have to extract them to a specific folder? Im trying to install the drivers from the samsung website first though
Im not using the toolkits anymore and am trying to follow your instructions for the command prompt
blipp said:
sorry for being a noob at this, but where do i put the Universal Naked Driver stuff? Do i have to extract them to a specific folder? Im trying to install the drivers from the samsung website first though
Im not using the toolkits anymore and am trying to follow your instructions for the command prompt
Click to expand...
Click to collapse
Extract the zip to a directory. Plug your device in fastboot mode to your PC. Open device manager and find the phone. Right-click on it and select update driver. Select install yourself or whatever the option is, and navigate to the folder where you extracted the zip. I've found that those drivers are better than the Samsung-packaged drivers.
Also, do one or the other, but not both. Make sure you remove the old driver before you start the new.
In windows 7 you're gonna want to go to (install Universal Naked Driver)...
Control Panel -> Hardware and Sound -> Device Manager
In the list click the driver for your phone. It will either be in the USB list or listed as some kind of phone. Right-click and uninstall the driver. Reboot. Go back to device manager. Plug in device. Click update driver software when your device shows up. Then 'Browse my computer'. Then 'Let me pick from a list'. Then 'Have Disk'. Find the .inf files and windows will install the driver.
ok, i extracted the Universal zip into its own folder on the desktop, after i uninstalled the drivers and rebooted my PC, i plugged in the phone, waited for it to show up, and went to update the drivers. I got to the "Have Disk" and selected both of the .inf files that were in the extracted folder. Both of them caused a popup that said that folder didnt contain the drivers for my device.
When im in the fastboot bootloader the phone doesnt show up in my Device Manager. Is that a problem?
Thanks for helping me through this, my last phone was a Droid X and all i ever had to do was hold vol down and power and it got me to a recovery screen like CWM and i could install an update.zip.
blipp said:
ok, i extracted the Universal zip into its own folder on the desktop, after i uninstalled the drivers and rebooted my PC, i plugged in the phone, waited for it to show up, and went to update the drivers. I got to the "Have Disk" and selected both of the .inf files that were in the extracted folder. Both of them caused a popup that said that folder didnt contain the drivers for my device.
When im in the fastboot bootloader the phone doesnt show up in my Device Manager. Is that a problem?
Thanks for helping me through this, my last phone was a Droid X and all i ever had to do was hold vol down and power and it got me to a recovery screen like CWM and i could install an update.zip.
Click to expand...
Click to collapse
What OS are you running on your PC?
Windows 7
blipp said:
Windows 7
Click to expand...
Click to collapse
Ok, try this: go into the directory where you unzipped the drivers. Right-click on android_winusb.inf and select install.
Get an error popup - "The INF file you selected does not support this method of installation"
blipp said:
Get an error popup - "The INF file you selected does not support this method of installation"
Click to expand...
Click to collapse
Hmm. Not sure what is going on.
Let's try this step-by-step:
Boot your device into fastboot mode, plug into your PC, and open up device manager. Does your PC recognize your device? What does it show in task manager?
Nothing Shows up in device manager. The "imaging devices" section is opened by default. In the "devices and printers" window, however, there is an "unspecified" device, Android 1.0. Usually the galaxy nexus shows up in the "portable devices" section in device manager. Coins "scan for hardware changes" doesn't cause it to appear either
Sent from my Transformer using XDA
blipp said:
Nothing Shows up in device manager. The "imaging devices" section is opened by default. In the "devices and printers" window, however, there is an "unspecified" device, Android 1.0. Usually the galaxy nexus shows up in the "portable devices" section in device manager. Coins "scan for hardware changes" doesn't cause it to appear either
Sent from my Transformer using XDA
Click to expand...
Click to collapse
Ok, good. Now right click on the Android 1.0 and select "update driver software". Then click on "browse my computer for driver software", then click on the "Browse" button and make sure "include subfolders" has a check.
Now navigate to where you unzipped the drivers and click ok.
Its not giving me that option. Its not in device manager, its only showing in control panel->hardware and sound->devices and printers. Right clicking only gives me Eject, Create shortcut, troubleshoot, and properties. Properties only has General and Hardware. I even went into device manager and checked "show hidden devices" and its still not there. It only shows up now when its actually booted into android
Sent from my Transformer using XDA
Hey everyone,
Alright so I have been trying to root my phone for the past 4 hours. I have unlocked it and flashed a custom recovery using adb. Or at least I thought I did. I tried flashing the clockworks recovery and when I would reboot it into the recovery, I would get an icon of a phone and an exclimation point. I assumed a bricked the phone and freaked out. A minute later the phone rebooted out of recovery and works fine afterwards. So I assume that the problem is the recovery. Something went wrong and I am not sure what.
Here are the steps I followed:
I was fine up until step four when I was trying to flash superuser.
No idea what to do from here.
HTC Unlocked = Bootloader is unlocked?
Not to take away from the OP, but i created a guide for a guy here at work and thought others might benefit from it.
Unlock Bootloader and Root
Unlocking your bootloader will wipe all data from your phone. Meaning you will loose everything make a backup.
Step 1: ADB Installation Instructions. NOTE:You must have ADB installed on your PC even if you use method 2b to unlock the bootloader. You will need adb to install recovery in Step 4.
1. Go to http://developer.android.com/sdk/index.html and download the sdk.
2. Follow installation instructions found here. Note: This is not a forum for this device DO NOT do anything but the adb installation on your system.
Step 2a: Download software from HTC to allow your bootloader to be unlocked.
1. Go to http://www.htcdev.com/
2. Login to the website. NOTE: Register for an account if you haven’t already. You must provide a valid email address.
3. Select “All Other Supported Models” from the drop down list and click “Begin Unlock Bootloader”
4. Follow online instructions.
1. SuperUser http://androidfiles.org/securekey.ph.../superuser.zip - Copy this file you phone. Special thanks to jmztaylor his link.
2. Recovery of your choice TWRP Recovery http://forum.xda-developers.com/show....php?t=2161702 or CWM Recovery http://forum.xda-developers.com/show....php?t=2161706. Put this file in the ADB Tools folder. NOTE: You must type the name of this file perfectly when using adb to flash it in step 4.
Step 4: Using ADB to install recovery
1. Open command prompt ( shift + right click, then choose “Open command window here”) and type “ADB devices” you should see you phone listed, if you do not start over at Step 1. NOTE: Phone must be plugged in and USB Debugging must be checked in settings.
2. Type “ADB flash recovery recovery.img” without the quotes. NOTE: the red is actually the title of the recovery file that you copied in step 3. If it’s different substitute your files name instead.
3. Once complete type “ABD reboot recovery”.
4. You should at this point backup your device
5. Once you create a backup, Choose install and navigate to the SuperUser file you put on your phone in Step 3.
6. If all goes well you are now rooted. Select reboot system to restart phone.
There is some very good information here but its spread out pretty thin. Guides IMHO are very usefull to fill the gap between devs/powerusers and the newbs.Most people that come here have a hard time with the things we take for granted such as adb commands, or adb its self (most will be setting it up for the first time). I tried my best to put it in a knowledge base that everyone can understand if for some reason you do not understand what i was trying to say please ask. I don't own this phone, just helped a friend root his, but if you need to get ahold of me pm me. I'll get back to you as soon as possible.
Any help? Just trying to get rid of the bloatware -_-
Did you copy superuser to your phone? And are you sure you are using the correct file location for adb in the command prompt? You must make sure you are and that all files you want to flash are also in the same folder as adb. Please respond if you have superuser on your phone and if you are positive you are using the correct adb folder location for the command prompt. I'm not the best at this however, I read up a lot on it just to root my phone. Took me 4 hours about as well, but that was before the recoverys came out. I suggest trying to flash twrp recovery, it's a bit buggy (for me) but I find it easier to use.
Sent from my HTC One VX using xda app-developers app
Code:
ADB flash recovery recovery.img
that is your problem to start with its not "ADB flash"
boot your phone into bootloader with usb connected to PC, Phone should read "fastboot"
Go the your adb directory in command prompt.
ex.
Code:
C:\PcUser\Master\Androidsdk\adb\
Make sure all drivers are installed, from CMD prompt window type "fastboot devices" to check your phone is showing.
if you see your device then you can type
fastboot flash recovery [drag your recovery image into cmd window] and hit enter and it should flash
once recovery is flashed you can either "fastboot Reboot" or on the phone use the Vol rockers to navigate to menu and hit bootloader then from there choose recovery
Hi,
I have the same issue about 2 days, I install TWRP Recovery and all it's ok, and flash in fastboot mode with adb like ilostchild tolds You.
It seems that I met the same problem.
My issue is the phone only boot into CMW mode, although I tried to restart it many times. When connect to usb cable, lappy did not recognize the phone so I can use adb command.
Please help me.
I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.
zeratos said:
I can't make ADB recognize the device, I already installed the SDK the HTC Sync program but the device appears either as "My HTC" or "Android 1.0" and won't appear under "adb devices", any help? I have been googling for 3 days for a solution but I haven't found anything so far.
Click to expand...
Click to collapse
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img
spooky_ghosty said:
Try using another computer!!! Install all neded drivers, searxh google and let windows automaticly install some. Connect via fastboot and it should say
Fastboot usb.
Also....dont search for adb devices, just enter commands starting with fastboot like... Fastboot install recovery cwmrecovery.img
Click to expand...
Click to collapse
I already tried all those things you mentioned, I have been looking for 3 days for a solution for this problem on google without any luck, the device doesn't recognize any command either and I already set up a virtual machine and tried on that machine as well. u_u
Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.
Johann12911 said:
Uninstall HTC sync then try adb devices be possitive you are using the correct location for adb. Usb debugging MUST be on as well. Copy paste the commands into the prompt to make sure you are entering them right. Be sure you have the downloaded files in the same folder you are using with adb.
Click to expand...
Click to collapse
Already tried uninstalling HTC Sync, after that I deleted every trace of it. USB Debugging WAS ON before the phone crashed but I can't activate it now because the phone keeps looping between reboots.
Try to flash it via htc sync. Download the update and rewrite everything!
Sent from my HTC One VX using xda app-developers app
Hi All,
I have spent this afternoon rooting stock 4.3 yakju and thought that I'd share the latest on how to go about doing this manually for the maguro GT-I9250. This is a complete guide which brings all the information you will need under the one thread which doesn't seem to have been done before except as separate guides and scattered information all over the internet.
NOTE: Unlocking and Rooting your device will void your warranty and can in some instances if not performed properly brick the phone. This process will also wipe your phone back to factory defaults so any personal files and applications will be lost. You should backup the device using the backup options in the recovery environment or by saving any personal files off the device via the USB cable, prior to unlocking your device. You follow this procedure at your own risk!!
With that disclaimer out the way there, We can begin.
NB: I ran all linux commands in this tutorial as root, I am not able to say if running as a standard user may cause issues, although one forum suggested to run as root or sudo up if you have a bootloop issue so I did this to avoid problems. This tutorial assumes that you have some experience with using basic Linux commands including but not limited to copying and moving files, changing directories, listing files, running scripts and executables using './' and using the console
So Firstly I am running Fedora 19 x64 with the latest kernel. It's a lot easier than trying to muck around with Windows 7 drivers and there are tutorials for installing these. To update on that tutorial you can use the official samsung drivers to install the adb and mtp drivers (may already be noted in the thread, but I might as well state it here also.) and the best place to get the official samsung drivers is by installing the Samsung Kies application.
You need to enable 'USB debugging' in order for ADB to work, you do this from 'settings --> developer options' if you can't see 'developer options' you may need to enable them, to do this, select 'settings --> about phone' and tap 'build number' until it says 'you are now a developer' which takes around 7 taps. In 'developer options', you may need to turn them on by clicking the 'on' button at the top. Once you have turned them on, select 'usb debugging' and this will then tell you that 'this may make your device less secure', agree/accept this, and continue. You can always turn it off later if you need to. Once you enable this, within linux you may get prompted when running adb to authorize (e.g. you are not authorized, check the device screen). You need to authorise from the phone, so allow the connection and select 'remember this computer' to save having to do it again.
Now for the bootloader driver it's a bit trickier to install. You need to reboot into the bootloader, by powering off the device and then powering back on again while holding the volume + and volume - keys at the same time. You will then probably get a failed driver install for 'Android 1.0'. At this point, you will need the universal Naked driver from this thread. Download and extract it to your 'Downloads' folder. Now go to device manager, right click on the 'Android 1.0' device and select 'update driver...' and then select 'browse my computer for driver software' and then select 'let me pick from a list of drivers'. Click 'have disk' and you will be able to install from the folder you extracted the 'Universal Naked Driver' into. You will now be able to use the fastboot command in Windows.
Ok. Now we have the windows users covered. In Linux, All I needed to do was download the android sdk adt tools. I'm using the 64 bit version, so I downloaded the 64 bit version from the adt bundle section here. Once I had downloaded and extracted these into a folder in my Downloads folder under my user profile, I copied the adb and fastboot files to a separate folder as these are the only things I needed in the bundle. you do this by typing
Code:
cp /home/<your_username>/Downloads/Androidadt/adb /home/<your_username>/Downloads/Nexusroot/
cp /home/<your_username>/Downloads/Androidadt/fastboot /home/<your_username>/Downloads/Nexusroot/
From here on you will want to be working from the 'Nexusroot' folder, so type
Code:
cd /home/<your_username>/Downloads/Nexusroot
.
From here, you need to obtain the recovery you wish you use, I chose to use the CWM v6.0.4.3 touch recovery which can be obtained from here. Once it's saved to your downloads folder you should copy it to your previously created 'Nexusroot' folder where we saved adb and fastboot.
The next item on the list is something I did because I was running the yakjuxw firmware and is the reason I did everything in Linux for this tutorial, as the firmware files are tarballed and opening the tar in 7zip shows 'unix filesystem' as the base folder. I installed the stock 4.3 firmware from google. I used the extracted files for the firmware as my 'Nexusroot' folder and copied fastboot and adb into this folder as well as the recovery image. I then ran ./flash-all.sh with the device in fastboot mode (you will need to have unlocked the bootloader prior to doing this, instructions are below in the next paragraph. The script basically just flashes the firmware with the fastboot command, if you want to flash the CWM recovery at the same time, you will need to rename the recovery file to the same name as the recovery image in the tarball and replace or rename the one that came with the tar file from google), If you have setup your environment in Windows 7 as described above, there is also a batch file that will do the same thing ensure the device is in fastboot before running the batch file/script or it will sit there and say 'waiting for device' and make sure the fastboot application is in the same folder as the script. Once the flash is complete your device will be running the stock 4.3 firmware. (edit: I have since extracted the entire image out of the tar with 7zip from Windows 7, you will be able to flash the base once you extract it all to a folder but you need to open the secondary container file in 7zip separately)
The next step is to flash the recovery. To do this, put the device into fastboot mode and unlock the bootloader using the command
Code:
fastboot oem unlock
select 'Yes' at the prompt, your device will now reboot twice and perform a factory reset which will wipe all data, at this point you may need to re-enable 'usb debugging' from your settings (see above for instructions), re-enter fastboot mode by typing
Code:
adb reboot bootloader
next type in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-maguro.img
Your device will now install the touch recovery we downloaded earlier. Once done, type the command
Code:
fastboot reboot-bootloader
.
Now to root the device, download the SuperSU zip file from the link and copy it to your 'Nexusroot' folder. Now boot into your recovery environment by using your 'Volume -' key to select 'boot recovery' and allow the device to boot into the recovery environment. This will allow you to use the adb command. Change directory into your 'Nexusroot' folder if not already in it, and type
Code:
adb push UPDATE-SuperSU-v1.43.zip /sdcard/0
This will copy the zip file to the internal memory card. From the recovery environment on the phone, select 'install file from sdcard' and then 'choose zip from sd card'. Select '0' and then select the 'UPDATE-SuperSU-v1.43.zip' file and select 'yes - install...' and the zip file will install the SuperSU application and binaries. Your device is now rooted, however you will need to run the SuperSU app to update the binary again. We will discuss this further after the next step.
Now we should lock the bootloader again to prevent tampering with our recovery and other firmware images however if you wish to flash other ROMS you will want to leave this unlocked, or you will need to unlock it again next time you want to flash a rom. To lock the bootloader, with the phone in fastboot mode, you simply type
Code:
fastboot oem lock
and this will re-lock the bootloader. Note you will not be able to flash any radios, kernels, or other .img files while this is locked. Now reboot your phone back into Android.
Now that you know how to unlock your phone, it's rooted, and has a recovery environment installed, you need to activate your SuperUser install. To do this, open the SuperSU app, and when prompted to update, click 'continue'. You will at this point be asked how you want to install it, select 'CWM/TWRP Recovery' and your phone will reboot, you will see an update occur on the screen and SuperSU will now be correctly installed.
You can now begin experiencing the freedom to use whatever ROM you want, customise your device how you want, and even change which applications you want installed regardless of whether they are system apps or otherwise.
I hope this guide is helpful.
References:
http://forum.xda-developers.com/showthread.php?t=1379875
http://forum.xda-developers.com/showthread.php?t=1830108
http://forum.xda-developers.com/showthread.php?t=2117822
http://forum.xda-developers.com/showthread.php?t=2065470
http://www.ibtimes.com/how-root-galaxy-nexus-i9250-nexus-4-android-43-jelly-bean-official-firmware-tutorial-1362063
http://www.clockworkmod.com/rommanager
https://developer.android.com/sdk/index.html
http://www.ubuntu.com/phone/install
https://developers.google.com/android/nexus/images
Thanks:
@1wayjonny
@TECK
@samersh72
Without your guides I wouldn't have been able to do this.
Was running MMuzzy, tried Omni, decided to go back (no statement on Omni, just didn't want to deal with new, setting up and such) and the only backup I have is in TWRP... but I switched to CM to install Omni... and like an over eager cleaner, I deleted the install files for everything last time I was in Omni... then I went into recovery, wiped and realized I need TWRP to restore my backup (no files found in CW)
All I can do is boot into recovery and I cannot figure out how to set up windows so I can put an install file on there to run so I can get back to TWRP and clean this mess up. I tried installing the Samsung drivers on an XP workstation but the computer doesn't find drivers when plugging in the phone... I pointed to the samsung/drivers folder in programs but no luck.
Bail a ding bat out?
Bump
Can anybody explain how to get this thing viewable in windows? (With no phone control)
Please.... and thank you in advance!!!
I am ready to pay someone for help on this
Help me get this back to life... name a reasonable price
Use efrant's guide in the stickys to flash the factory image and use his link for Windows drivers. It always works and his fastboot tutorial has saved my device more than once.
Link:
http://forum.xda-developers.com/showthread.php?t=1626895
For my instructions, download these, you will end up using them:
1. Android drivers for windows, I would prefer Universal Naked Driver (UND):
http://forum.xda-developers.com/showthread.php?t=1766220
2. Android debugging tools (ADB), I would prefer minimal ADB:
http://forum.xda-developers.com/showthread.php?p=42407269
3. TWRP recovery image: http://www.teamw.in/project/twrp2/90 download the last version you remembered using or just use the latest openrecovery-twrp-2.6.3.2-maguro.img
Install 1 & 2 in order. You may need to have the phone boot to recovery to install #1. Installing the drivers in Windows XP/7 will be easier, Windows 8/8.1 requires an advanced step to disable unknown driver enforcement.
For #2, if you have ADB/Fastboot already, skip this step. If you don't, then you may need to install it while in recovery too. Install it to a folder you are familiar with, I would choose C:\ and make an Android folder.
After you have both installed, boot your phone to bootloader mode. When it is shut off, hold VOL + and - at the same time then press the power button for all 3 simultaneously. It will boot into bootloader mode, where you see the android and your Galaxy Nexus revision/software details.
Move the TWRP recovery img file to the location of your ADB folder. For my example, I will assume #2 (adb tools) are installed in Local Disk (C and the android folder, so C:\Android
From here you would use the command prompt/terminal start > run > cmd or start, find program Command Prompt.
In the terminal type cd\foldertoTWRPimgfile\ or in my example, cd\android\
Next, type fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
my example would look like:
C:\android\ fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
it will show a progress indicator, then OK'd when it is finished.
You can then manually boot to recovery in fastboot, hit a volume button on your phone a few times until you see RECOVERY, then hit the power button to load it. You should now be in TWRP and be able to restore your backup, hope it is still there. Since it is likely that you were last using an older version of TWRP for MMuzzy, you might notice differences if you flash a newer version of TWRP.
kaijura said:
For my instructions, download these, you will end up using them:
1. Android drivers for windows, I would prefer Universal Naked Driver (UND):
http://forum.xda-developers.com/showthread.php?t=1766220
2. Android debugging tools (ADB), I would prefer minimal ADB:
http://forum.xda-developers.com/showthread.php?p=42407269
3. TWRP recovery image: http://www.teamw.in/project/twrp2/90 download the last version you remembered using or just use the latest openrecovery-twrp-2.6.3.2-maguro.img
Install 1 & 2 in order. You may need to have the phone boot to recovery to install #1. Installing the drivers in Windows XP/7 will be easier, Windows 8/8.1 requires an advanced step to disable unknown driver enforcement.
For #2, if you have ADB/Fastboot already, skip this step. If you don't, then you may need to install it while in recovery too. Install it to a folder you are familiar with, I would choose C:\ and make an Android folder.
After you have both installed, boot your phone to bootloader mode. When it is shut off, hold VOL + and - at the same time then press the power button for all 3 simultaneously. It will boot into bootloader mode, where you see the android and your Galaxy Nexus revision/software details.
Move the TWRP recovery img file to the location of your ADB folder. For my example, I will assume #2 (adb tools) are installed in Local Disk (C and the android folder, so C:\Android
From here you would use the command prompt/terminal start > run > cmd or start, find program Command Prompt.
In the terminal type cd\foldertoTWRPimgfile\ or in my example, cd\android\
Next, type fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
my example would look like:
C:\android\ fastboot flash recovery openrecovery-twrp-2.6.3.2-maguro.img
it will show a progress indicator, then OK'd when it is finished.
You can then manually boot to recovery in fastboot, hit a volume button on your phone a few times until you see RECOVERY, then hit the power button to load it. You should now be in TWRP and be able to restore your backup, hope it is still there. Since it is likely that you were last using an older version of TWRP for MMuzzy, you might notice differences if you flash a newer version of TWRP.
Click to expand...
Click to collapse
Wow... I really do not know where to begin to thank you... that REALLY saved my bacon as it is my work phone as well as personal cell too. Please send me a PM with a donation addy and an amount if you have one or I would be happy to send you a Christmas present...
Merry CHRISTmas everyone!!!!
A few months ago I decided to try and root my Nexus 7 (2013) tablet. At this time I simply cannot remember what process I used but all I know is that everytime I try to power it on the system start screen comes on where it asks what country you're in and so forth. But I also get the following Pop Up Error message "Unfortunately, Google Keyboard Has Stopped" and an "OK" button. When I click on OK the error message simply pops back up in a never ending loop. It stops at the SELECT WI-FI screen and won't let me input the access code because of the Pop Up Error message.
Does anyone have any idea how to completely wipe the system and bring it back to stock or just to the point I can do "anything"?
Thank you in advance for your assistance!
Boot into fastboot by holding volume down and power while the tablet is off. Scroll through the options with volume keys. When you see the option recovery mode at the top of the screen, press power. This will boot you into recovery. From there, there will be several option. One of which should be a hard reset. navigate using the volume keys. You should be OK from here.
sent from my nex7
Thank you for your reply but unfortunately this doesn't work. It puts me right back to where I always end up and still get the Error Message stated above.
I've been working on this for a few hours now and nothing! It basically says I don't have a Keyboard installed after I do anything. If I Factory reset it I get the same Error Message about no keyboard.
Any ideas? PLEASE HELP!
That is really weird. Do you have a custom recovery installed? Custom ROM? Does the computer find it? because flashing a stock image may be the way to go from here.
sent from my nex7
mugzylol said:
That is really weird. Do you have a custom recovery installed? Custom ROM? Does the computer find it? because flashing a stock image may be the way to go from here.
sent from my nex7
Click to expand...
Click to collapse
Thank you for your reply. I greatly appreciate you taking the time. I am at wits end at this point and simply need it to run again. Can you talk me through loading whatever to get it back to new? I'll take anything at this point. Everything is backed up so I have nothing to lose. How can I load the original image? (non rooted)
Thank you!
I AM NOT RESPONSIBLE FOR ANYTHING IF IT GOES WRONG (it should not go wrong though)
First you will need an image. Search for a stock 2013 nexus 7 image. Than you will need to download google USB drivers :
http://developer.android.com/sdk/win-usb.html
Than install them by opening the device manager program which is installed by default on any windows computer. Plug your tablet in, right click it in device manager and press update driver software and browse for the driver you downloaded. Than install it.
Now that that is done download the android SDK.
http://developer.android.com/sdk/index.html
Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on
"open new command window here"
Now put your tablet into fastboot mode. Type
"fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Now type "fastboot OEM unlock" in the command window. Select yes on your tablet with volume keys and click power on your tablet. Than it will run through the unlock bootloader practice. This will erase all content on the tablet. It may take a bit.
Once that is done, put your image in the tablets internal storage.
Now download the latest twrp for your device.
http://teamw.in/project/twrp2/193
Press download latest .img
Now, put your twrp image in the platform tools folder and name it something easy to type. Now, in the command window type:
Fastboot boot (name of your twrp here).IMG
This will boot into twrp. It will not install it.
Now, in twrp press install and browse for your image (must be a .zip file) and flash it. If all goes well than reboot your system. If there is a problem try another image.
You do not need to unlock bootloader or install drivers again. Just boot back in to twrp and flash another image (if it goes wrong)
Stuck
mugzylol said:
I AM NOT RESPONSIBLE FOR ANYTHING IF IT GOES WRONG (it should not go wrong though)
First you will need an image. Search for a stock 2013 nexus 7 image. Than you will need to download google USB drivers :
http://developer.android.com/sdk/win-usb.html
Than install them by opening the device manager program which is installed by default on any windows computer. Plug your tablet in, right click it in device manager and press update driver software and browse for the driver you downloaded. Than install it.
Now that that is done download the android SDK.
http://developer.android.com/sdk/index.html
Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on
"open new command window here"
Now put your tablet into fastboot mode. Type
"fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Now type "fastboot OEM unlock" in the command window. Select yes on your tablet with volume keys and click power on your tablet. Than it will run through the unlock bootloader practice. This will erase all content on the tablet. It may take a bit.
Once that is done, put your image in the tablets internal storage.
Now download the latest twrp for your device.
http://teamw.in/project/twrp2/193
Press download latest .img
Now, put your twrp image in the platform tools folder and name it something easy to type. Now, in the command window type:
Fastboot boot (name of your twrp here).IMG
This will boot into twrp. It will not install it.
Now, in twrp press install and browse for your image (must be a .zip file) and flash it. If all goes well than reboot your system. If there is a problem try another image.
You do not need to unlock bootloader or install drivers again. Just boot back in to twrp and flash another image (if it goes wrong)
Click to expand...
Click to collapse
OK, a couple of things;
1. I'm using a MacBook Pro. Does this make any difference? (It says I don't have to download any drivers using a Mac but other than that is there any differences?)
2. I'm stuck at ..... Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on "open new command window here". Now put your tablet into fastboot mode. Type "fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Everything I do doesn't work. When I hold down Shift and Right-Click on the Platform Tools Folder I do not see "open new command window here". Is this the "platform-tools folder under the SDK folder?
Do you have any windows computers because this will not work without one
sent from my nex7
---------- Post added at 08:27 AM ---------- Previous post was at 08:25 AM ----------
This is because Mac computers do not execute batch scripts and the fastboot commands are made to execute through a command prompt rather than a Linux terminal
sent from my nex7
I honestly made this way too complicated. Just run through setup without using the keyboard. Find an unprotected network (like McDonald's) that works and find a way to get your hands on an apk of any keyboard and install it. I'm not quite sure how you can get a download link to a keyboard with no account (yet) and no keyboard but there must be a way. Its a simple issue that causes so many problems. So in a nutshell, if you can find a way to install an apk of any keyboard, your good
sent from my nex7