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
Hi XDA,
So I got an Xperia PLAY just the other day. Despite its age, since its capable of running a PS emulator, given the built in controller, I think its rad.
Anyhow, went to install CM10 on it and I screwed up big time.
I actually copied the update.zip file over in USB storage mode instead of adb pushing it.
Phone is now stuck in boot loop.
Here's where I'm at:
-I CAN still access both bootloader and CWRM (I used bootloader to copy the boot.img across)
-I CAN'T get the phone to communicated with adb (no adb device shows up in device manager or "adb devices", the only thing I can see is "MTP Device" which I figure is the problem)
-I CAN'T switch it out of MTP mode (if this is even the issue) as CWRM doesn't offer that option
I have tried:
-Both with and without PC companion to get it to communicate with ADB
-The universal ADB driver.
-I have tried the PC companion "phone repair" but it refuses to help me as it realises I have modified the KERNAL.
Question is:
- Is there anything I can do to copy an update.zip ROM across. A way to make ADB work or any solution other than ADB?
- Am I right in assuming ADB is not working because its set to MTP mode?
Much thanks in advance!
Did you flashed kernel (boot.img file that you extract from zip file)?
What was your previous kernel/rom?
TehKame said:
Hi XDA,
So I got an Xperia PLAY just the other day. Despite its age, since its capable of running a PS emulator, given the built in controller, I think its rad.
Anyhow, went to install CM10 on it and I screwed up big time.
I actually copied the update.zip file over in USB storage mode instead of adb pushing it.
Phone is now stuck in boot loop.
Here's where I'm at:
-I CAN still access both bootloader and CWRM (I used bootloader to copy the boot.img across)
-I CAN'T get the phone to communicated with adb (no adb device shows up in device manager or "adb devices", the only thing I can see is "MTP Device" which I figure is the problem)
-I CAN'T switch it out of MTP mode (if this is even the issue) as CWRM doesn't offer that option
I have tried:
-Both with and without PC companion to get it to communicate with ADB
-The universal ADB driver.
-I have tried the PC companion "phone repair" but it refuses to help me as it realises I have modified the KERNAL.
Question is:
- Is there anything I can do to copy an update.zip ROM across. A way to make ADB work or any solution other than ADB?
- Am I right in assuming ADB is not working because its set to MTP mode?
Much thanks in advance!
Click to expand...
Click to collapse
Go into cwm. Go to mounts and storage. Connect phone to pc and mount the sd and you should be able to connect to adb while in cwm. Copy a rom over and flash or if it was the biktloader and kernel and all that do as per usual
Sent from my R800x using XDA Free mobile app
TehKame said:
Hi XDA,
Flash ftf in flashtool .. go back to rooted Stock !! and carry on from their onwards.
Click to expand...
Click to collapse
I everyone,
I need your help, I tried to install a new rom (AICP : this one) , and somehow forgot to do a backup.
When I boot I only get the swirling logo, never get to fully load.
The phone is not bricked, I can still access the bootloader / fastboot and my recovery, so I could simply flash another rom... but I can't figure how to get the zip file on the /sdcard.
I can't use adb sideload or push, I have HTC sync and android sdk installed, I have no problem to use fastboot commands, so I guess I don't have any driver problem, but adb devices never shows my phone (Tried while off, booted on bootloader, on fastboot, and on recovery, never shows up when I try adb devices)
On windows I get a driver error when plugging my phone while in recovery, but I don't find how to install it.
So... is there a way to mount the /sdcard/ as an external drive in windows or ubuntu ? Or do you have a workaround for adb ?
Thanks a lot !
Vincent
Sometimes it might have happened to you that you have erased your download mode while doing some fun with adb commands and enjoying android development with starter knowledge. In this process you unfortunately destroyed your download mode.
Now you want to go back to stock but your download mode is not appearing only a fastboot mode opening saying some very tensed and confusing things to understands. This is the situation where you are totally messed up and out of mind. Don't know what to do. Tried whole of internet and can't find a solution. Now method is working and you want a fix. Then this thread is gonna help you a lot. You will be very happy to read instructions here cause they are easy and also phone saving too. These instructions can even save your amount to be given to a repairing shop.
So a lot of introduction is done, let's proceed to the process. First of all read disclaimer to avoid any misunderstandings of future.
Code:
Your warranty is void now. I am not responsible for any mistake and wrong thing happens to your device. Always try if you have a good knowledge of that.
These steps are not an official LG and therefore not endorsed by LG Electronics in any way. As such, this is a 'try-at-your-own-risk' approach. Please make sure to back up your important files when trying this for the first time. I take no responsibility for any undue outcomes resulting from the use of these steps and instructions. And all the best for step.
Things you Need:
1: LG united mobile drivers here. (Skip you have already)
2: adb & Fastboot drivers from here. (To do flashing commands). Minimal Edition.
3: Make sure "USB debugging" is on for you LG G3 device. If not sure check here.
4: laf.img for your device . (Download mode image). Most important thing
Download it from here according to your device variant like as d850, d855 or etc.
Select your variant > Stock partitions > 10D > laf.img ( I prefer 10d laf.img you are welcome to try other ).
5: LG G3 device in fastboot mode by connecting to PC while phone is powered off pressing volume up(+) button.
6: And the most important thing a computer. (I tried it on Windows 10 but will work on 7,8 and others too.
Steps:
1: Install LG united mobile drivers.
2: Install "adb and fastboot mode" drivers. Copy "laf.img" to the directory where you installed them and run "MAF32.exe"
Mine is "C:\Program Files (x86)\Minimal ADB and Fastboot"
3: Connect your LG G3 device while in fastboot mode.(Make sure drivers are installed).
4: Check if connection is right by doing this command
Code:
fastboot devices
5: If you done right your device might appear. (Sometimes as a question mark too)
6: To flash download mode. Execute these commands in sequence.(Make sure "laf.img" is copied to that folder where you installed the adb and fastboot drivers and is named as "laf.img").
Code:
fastboot erase laf
fastboot flash laf laf.img
fastboot reboot
7: Pull battery of your device and reboot into download mode again if flashing is successful. Download mode might appear as original. If not then you might have not listened to instructions. (If still stuck ask in comments).
If i helped you anyhow press "Thanks"
All the best with process.
Credits:
Autoprime for the stock partitions.
shimp208 for minimal ADB and fastboot drivers.
And all others who gave some ideas, drivers and tools for that method to work.
in adb commands appears waiting for device along time and no thing happened ..... plz
dksoni411 said:
Sometimes it might have happened to you that you have erased your download mode while doing some fun with adb commands and enjoying android development with starter knowledge. In this process you unfortunately destroyed your download mode.
Now you want to go back to stock but your download mode is not appearing only a fastboot mode opening saying some very tensed and confusing things to understands. This is the situation where you are totally messed up and out of mind. Don't know what to do. Tried whole of internet and can't find a solution. Now method is working and you want a fix. Then this thread is gonna help you a lot. You will be very happy to read instructions here cause they are easy and also phone saving too. These instructions can even save your amount to be given to a repairing shop.
So a lot of introduction is done, let's proceed to the process. First of all read disclaimer to avoid any misunderstandings of future.
Code:
Your warranty is void now. I am not responsible for any mistake and wrong thing happens to your device. Always try if you have a good knowledge of that.
These steps are not an official LG and therefore not endorsed by LG Electronics in any way. As such, this is a 'try-at-your-own-risk' approach. Please make sure to back up your important files when trying this for the first time. I take no responsibility for any undue outcomes resulting from the use of these steps and instructions. And all the best for step.
Things you Need:
1: LG united mobile drivers here. (Skip you have already)
2: adb & Fastboot drivers from here. (To do flashing commands). Minimal Edition.
3: Make sure "USB debugging" is on for you LG G3 device. If not sure check here.
4: laf.img for your device . (Download mode image). Most important thing
Download it from here according to your device variant like as d850, d855 or etc.
Select your variant > Stock partitions > 10D > laf.img ( I prefer 10d laf.img you are welcome to try other ).
5: LG G3 device in fastboot mode by connecting to PC while phone is powered off pressing volume up(+) button.
6: And the most important thing a computer. (I tried it on Windows 10 but will work on 7,8 and others too.
Steps:
1: Install LG united mobile drivers.
2: Install "adb and fastboot mode" drivers. Copy "laf.img" to the directory where you installed them and run "MAF32.exe"
Mine is "C:\Program Files (x86)\Minimal ADB and Fastboot"
3: Connect your LG G3 device while in fastboot mode.(Make sure drivers are installed).
4: Check if connection is right by doing this command
Code:
fastboot devices
5: If you done right your device might appear. (Sometimes as a question mark too)
6: To flash download mode. Execute these commands in sequence.(Make sure "laf.img" is copied to that folder where you installed the adb and fastboot drivers and is named as "laf.img").
Code:
fastboot erase laf
fastboot flash laf laf.img
fastboot reboot
7: Pull battery of your device and reboot into download mode again if flashing is successful. Download mode might appear as original. If not then you might have not listened to instructions. (If still stuck ask in comments).
If i helped you anyhow press "Thanks"
All the best with process.
Credits:
Autoprime for the stock partitions.
shimp208 for minimal ADB and fastboot drivers.
And all others who gave some ideas, drivers and tools for that method to work.
Click to expand...
Click to collapse
mero_enriqi said:
Click to expand...
Click to collapse
That can happen because
1: USB debugging is off on your device
2: Drivers are not installed properly
Proper fixes
1: Turn on usb debugging.
2: Install driver again or try the procedure on some other computer
(If you can get a computer running Windows 7 32-bit that would be a good choice)
im stuck at firmware update. every time i restart my phone theres no download mode and directly go to firmware update. how can i back download mode? i cant open my phone to on the debug setting
Fastboot doesnt work
Hi there
I hardbricked my phone while reinstalling stock rom when my laptop crashed. Afterwards adb and download mode wouldn't start, only thing now is fastboot.
I tried your solution, but it doesn't seems to be working. The device is showing in CMD (fastboot devices) but further commands arent accepted, they show up at the G3 screen, but afterwards nothing happens. What can i do (I really don't want to try the "short-circut - Qualcom" method).
Drivers and so on are properly installed
Thanks in advance
Can't get to download mode!
I did everything as instructed and the flashing was successful...
But whenever I want to go to download mode, it just shows download mode icon and then goes straight to fastboot!
How can I fix this?
Lg G3 D851 10c here, trying this method after trying to flash magisk and got stuck with Fast boot mode. its been stuck on "erasing 'laf' ..." for a very very long time.
thanx..............work perfect lg d851 10c
Hi, Dev /..
Mine is lg ge d851 10f
What Shoud i flash to install recovery and boot into recovery to flash roms. kindly help me ASAP...:fingers-crossed:
hi mine is d85110f . which laf.img shoud i flash kindly help
booting to download mode
in adb type
PHP:
adb reboot bootloader
this should get you to download mode......
if you try
PHP:
adb reboot fastboot
or VOL UP+USB
you cannot enter download mode
if you are on a custom rom.
The phone will just reboot.
However
PHP:
adb reboot bootloader
seems to do the trick.
Also I am on LG G3 D858HK with mokee rom 7.1
and this works for me.
twrp working but unable to mount storage.
download mode showing but its not detect.
fastboot mode not working
tried everything change file system etc
I have a nexus 7 WIFI 2013 (Razor, Flo):
I was trying to get a copy of Nethunter or Kali linux installed on here. I was running CyanogenMod nightly's
Well during one install, I must of wiped the whole tablet clean. It only had dad/media and then subs /0, /obb folders. I'm unable to find any images on the card and nothing else is displayed. I have tried number numerous drivers for my Samsung laptop but when i use my surface it shows nexus 7 and also when i go into bootloader mode it will also show the driver.
I installed droid SDK and also minimal adb and fast boot. I'm unable to push anything to this device. When i run adb devices it shows the device but says unauthorized. I try adb kill-server and adb start-server and still no dice.
I'm looking for any input as to how I can push and image onto this device. I realize I will have to go back to factory and I have all them images. I just cant get it adb authorized yet.
this will only go into recovery mode and boot loader mode. There is no OS if I let it boot it just shows the mod logo and will sit there until the battery dies.
Does anyone have any input on how to get this authorized so I can push files to it. I'm unable to get on the screen and ok the RSA fingerprint and I think that maybe part of my hold up or why it shows unauthorized.
Thanks in advance for all or any input or ideas.
Start TWRP and it will authorize you to push any files anywhere.
I'm unable to get TWRP on this tablet. The main issue is I only have cyodgen mod recovery on the tablet. It will not boot. It will only go into recovery mode/bootloader mode. I'm unable to verify any RSA fingerprints which is causing me an issue getting the tablet authorized for ADB pushes. Does anyone know a way I can get it authorized via ADB without being able to access anything other then recovery mode? I think the RSA fingerprint is whats actually causing me an issue.
cletisvandamm said:
I'm unable to get TWRP on this tablet.
....
I think the RSA fingerprint is whats actually causing me an issue.
Click to expand...
Click to collapse
No need to flash TWRP - just start it directly from RAM:
download twrp-3.0.2-0-flo.img to your folder with fastboot and adb apps
boot the Nexus in fastboot mode (when off press power+vol.dn), connect it to your PC
on PC run: fastboot boot twrp-3.0.2-0-flo.img
when TWRP is up, ADB-push your files, no RSA concerns