Hi My Galaxy Nexus seems to be Bricked.(PHONE NOT BOOTING)
Problem:
1. Power button doesn't work- Phone not booting
2. I connected through a USB cable then phone started charging, Then i tried to boot which didn't work
2.1 Then i tried to go into Recovery (TWRP) which somehow worked for a while and then rebooted.
2.2 After trying more i finally managed to get TWRP working and i re-flashed the same version of Paranoid Android(@BigBrother) 4.3 Beta 2 that was installed - DIDN'T WORK
3. Then i trying to take the backup and succeeded using ADB from TWRP.
3.1 Then i flashed an old version of PA - didn't work
3.2 Then i tried installing the Stock ROM (4.3) - Installed successfully- But didn't work on restart. After Restarting the Google screen came up and then the Battery Charging indicator started flashing. The phone didn't boot up.
Initially i used Trickster MOD to overclock the phone to 1.5 Ghz, but I did it in Morning and the phone was fine till night So i am still not sure of the reason.
Anyone Please Help :'(
can you get into download mode?
if yes then reflash the stock google image using terminal and not toolkit.
if you successfully flashed 4.3, then go to recovery mode and wipe data/cache. it should boot up correctly.
run stock firmware for a week and see if the phone is stable.
hp13 said:
can you get into download mode?
if yes then reflash the stock google image using terminal and not toolkit.
if you successfully flashed 4.3, then go to recovery mode and wipe data/cache. it should boot up correctly.
run stock firmware for a week and see if the phone is stable.
Click to expand...
Click to collapse
Yes i Did get into Download Mode, and i Had successfully flashed stock 4.3 using terminal. I never used toolkit.
Didn't Boot yet
NOT BOOTING AT ALL
dk_india_world said:
Yes i Did get into Download Mode, and i Had successfully flashed stock 4.3 using terminal. I never used toolkit.
Didn't Boot yet
NOT BOOTING AT ALL
Click to expand...
Click to collapse
remove battery and put it back.
go into stock recovery and reset data
hp13 said:
remove battery and put it back.
go into stock recovery and reset data
Click to expand...
Click to collapse
Removed battery for half an hour.
Data already gone due to stock installation.
Power button not working at all.
Still needs to power up using a charger and then at least i could see the google logo
Guys Any Help.. :|
Related
Xperia Arc LT15i, last installed was FXP150 - CyanogenMod 10 Android 4.1.2
- which I was using for almost 2 weeks without any reboots or crashes nor any setting tweaks.
Yes, I have tried checking through a lot of searches and googling, haven't found any solution so far.
I had initially rebooted my phone to recovery using the option within the OS. It went on and loaded CWM, there I just looked around the menu, and clicked "reboot system now". After that the phone started booting, but after the FreeXperia screen, just displays a blank screen and gets stuck there. I re-entered CWM, and tried rebooting, still won't boot the regular OS. I tried re-installing FXP from sd-card (the same one that I had installed 2 weeks back) but now it won't install that release either. I tried toggling signature and re-installing, it still doesn't install.
I tried connecting the phone as mass storage through CWM, but my laptop won't detect it. The adb drivers don't work despite being installed correctly. Fastboot is the only thing that seems to detect my phone. But I cannot install new ROM using fastboot.
Please help.
Switch off your phone (if you can't try battery pull)
Use flash tools and install stock firmware and follow onscreen instructions
(Search and download ics stock firmware
Connect phone in flash mode by pressing back button and connecting)
sakthi444 said:
Switch off your phone (if you can't try battery pull)
Use flash tools and install stock firmware and follow onscreen instructions
(Search and download ics stock firmware
Connect phone in flash mode by pressing back button and connecting)
Click to expand...
Click to collapse
Cant I use the tool SONY has launched for this purpose ?
Ya it'll install stock firmware... Then you have to start all over again
Sent from my Ultimate Arc S
sakthi444 said:
Ya it'll install stock firmware... Then you have to start all over again
Sent from my Ultimate Arc S
Click to expand...
Click to collapse
Is there no way to make it work on FXP from this point itself ?
I was kinda hoping I could get it to run FXP directly....
If you can access Cwm get a complete back up and then after installing stock after installing Cwm you can restore...
But the best way is to flash stock and install fresh to avoid problems
Sent from my Ultimate Arc S
sakthi444 said:
If you can access Cwm get a complete back up and then after installing stock after installing Cwm you can restore...
But the best way is to flash stock and install fresh to avoid problems
Sent from my Ultimate Arc S
Click to expand...
Click to collapse
yes, will do that ofcourse. But was wondering if there was any way to get it to work as it is.
CWM is already working, and the sd-card already contains the package too.....
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
I just went back to stock after having CWM Recovery and BeanStalk 4.4.2. I used the recovery to wipe cache/data and flash the UCUCNE5 image ([ROM][4.4.2][Jul-2014] AT&T I317-UCUCNE5/MJ4 *Stock* Odex). I'd like to root the device and install the bootloader so WiFi will work now but I'm running into issues.
I can connect to the phone in MTP mode just fine, but Windows/Odin doesn't detect the phone in download mode. Not only that, but I can't turn the phone off while it's connected to the PC - it just reboots. I can get the phone to power down if it's not connected.
I've installed all of the updated Samsung drivers and Google ADB drivers. Anyone have any ideas?
NebraskaJ said:
I just went back to stock after having CWM Recovery and BeanStalk 4.4.2. I used the recovery to wipe cache/data and flash the UCUCNE5 image ([ROM][4.4.2][Jul-2014] AT&T I317-UCUCNE5/MJ4 *Stock* Odex). I'd like to root the device and install the bootloader so WiFi will work now but I'm running into issues.
I can connect to the phone in MTP mode just fine, but Windows/Odin doesn't detect the phone in download mode. Not only that, but I can't turn the phone off while it's connected to the PC - it just reboots. I can get the phone to power down if it's not connected.
I've installed all of the updated Samsung drivers and Google ADB drivers. Anyone have any ideas?
Click to expand...
Click to collapse
Take a screen shot of your settings in the about tab
Sent from my GT-N7105 using XDA Premium 4 mobile app
Here's the screenshot.
NebraskaJ said:
Here's the screenshot.
Click to expand...
Click to collapse
If you flashed the rom without doing the update you should already be rooted tho if anything get the newest supersu 2.0 then flash that in recovery and see what happens
Sent from my GT-N7105 using XDA Premium 4 mobile app
NebraskaJ said:
I just went back to stock after having CWM Recovery and BeanStalk 4.4.2. I used the recovery to wipe cache/data and flash the UCUCNE5 image ([ROM][4.4.2][Jul-2014] AT&T I317-UCUCNE5/MJ4 *Stock* Odex). I'd like to root the device and install the bootloader so WiFi will work now but I'm running into issues.
I can connect to the phone in MTP mode just fine, but Windows/Odin doesn't detect the phone in download mode. Not only that, but I can't turn the phone off while it's connected to the PC - it just reboots. I can get the phone to power down if it's not connected.
I've installed all of the updated Samsung drivers and Google ADB drivers. Anyone have any ideas?
Click to expand...
Click to collapse
take the battery out and try going into recovery mode and reflash the rom?
I can't seem to get recovery to work at all. The phone is connected and detected by Windows when powered on. When in download(stock recovery), the PC doesn't detect it. USB debugging is enabled, the computer security permissions are set for the PC.
Without access to recovery, am I able to do anything? Can I use ADB to force-flash the phone without it being in recovery?
Also, a wierd issue I mentioned before - the phone will NOT power down when connected to the PC, it just reboots. In addition, the phone, if powered down, will boot automatically when the USB cable is connected.
You may be looking at a Kies emergency restore if Odin can't see the device. ..
Hopefully Kies does...
But I'm with puffin on this one. ..
Place a clean rooted rom to your external sd card by removing it from the device and using a pc card adapter. ..then put the card with the rom back into the device while it's still powered down. ..
Then boot the device to recovery if possible. ..and fully wipe. ..then flash the new rom from sd....
Once booted...you should be good to move forward. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
wondering
hey.. So i am running 4.3 stock rooted deoxed with twrp. i am wondering if there is a way to truly go back to stock so i can ota the 4.4.2 update. i have already tried flashing 4.1.1 and going all the way up from there and i get the update to download and install and it just hangs up on the att logo screen on boot. Is it possibly because the knox counter is tripped. someone help. im not a noob to custom roms or flashing i just cant figure out what is stopping it....
Ajc61290 said:
hey.. So i am running 4.3 stock rooted deoxed with twrp. i am wondering if there is a way to truly go back to stock so i can ota the 4.4.2 update. i have already tried flashing 4.1.1 and going all the way up from there and i get the update to download and install and it just hangs up on the att logo screen on boot. Is it possibly because the knox counter is tripped. someone help. im not a noob to custom roms or flashing i just cant figure out what is stopping it....
Click to expand...
Click to collapse
Boot to the stock recovery and wipe data then cache. ..
It should boot fine after that. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
So today i was gonna try to install a custom rom, more specifically Cyanogenmod 10.2. for my Tmobile Galaxy S3 (SGH-T999). When i went to boot into recovery, i saw the screen that is displayed right before you enter recovery, but then after that it just stayed on a black screen. I took out the battery for a few seconds and powered on my phone. Then i tried entering recovery directly through ROM Manager. I got the same black screen, but now if i try to power on my phone without entering CWM, it automatically tries to go into CWM recovery regardless. . I tried a few battery pulls and nothing has worked yet. Luckily i am able to enter download mode so i can flash the stock rom via odin and then restore my backup from the SD card later. I just wanted to know if there is a simpler fix than this so i don't have to go through the trouble of flashing stock rom again. Btw i am still on the stock rom running android 4.3 jelly bean.
Try flashing custom recovery again and make sure it's the newest.
serio22 said:
Try flashing custom recovery again and make sure it's the newest.
Click to expand...
Click to collapse
The problem was i couldn't boot up my phone in the first place because it would automatically go into recovery. I actually fixed it by going it to download mode and then pressing the down button which rebooted the phone properly. I used rom toolbox and now im just gonna stick with TWRP.
RootNoob1299 said:
The problem was i couldn't boot up my phone in the first place because it would automatically go into recovery. I actually fixed it by going it to download mode and then pressing the down button which rebooted the phone properly. I used rom toolbox and now im just gonna stick with TWRP.
Click to expand...
Click to collapse
That's what I meant, you can flash recovery in download mode but as long as you got it working its all good. And yes I highly suggest using twrp over cwm
Thanks anyway man! TWR FTW!!
Hi everybody,
some time ago I flashed my ace II with cm 11 build 20141118 by ace2nutzer. Installation was ok and it worked properly. However, it had some minor problems, one of which was that battery wouldn't charge while booting the phone. One day it happened that my phone arrived at 0% battery and shut down. I couldn't find a way to turn it on because of the too-low battery, so I tried to see if during recovery mode maybe the battery would charge... but, instead of going to recovery, I pressed the wrong buttons and entered into download mode. There, the phone wouldn't charge and at one point it shut down. After some days I discovered that I could charge the phone by simply connecting it to a computer... But now it won't start. It gets bootloop (more precisely it keeps restarting) at the samsung logo. I tried to reflash the build I had before, but I keep getting status 7 error (even after deleting asserts).
Soo, is my phone bricked? Is there anything I could do to make it work?
Thanks to anyone that will help me
tl;dr: phone shut down during download mode, now bootloops and gives Status 7 error (even after deleting asserts) while trying to flash the same ROM it had before.
Anyone?
I forgot to say that I had a nandroid backup, but I can't restore it: it says "error while restoring /system!".
Ascan said:
I forgot to say that I had a nandroid backup, but I can't restore it: it says "error while restoring /system!".
Click to expand...
Click to collapse
Just install the stock firmware using ODIN and start from scratch
LS.xD said:
Just install the stock firmware using ODIN and start from scratch
Click to expand...
Click to collapse
Doesn't work. Odin doesn't give any error, but the phone keeps bootlooping.
Ascan said:
Doesn't work. Odin doesn't give any error, but the phone keeps bootlooping.
Click to expand...
Click to collapse
Try to enter stock recovery and clear cache + perform factory reset .
LS.xD said:
Try to enter stock recovery and clear cache + perform factory reset .
Click to expand...
Click to collapse
CWM recovery is the same? Btw still bootloop...
Ascan said:
CWM recovery is the same? Btw still bootloop...
Click to expand...
Click to collapse
CWM is a custom recovery. stock recovery is the one you have installed with the stock firmware.
LS.xD said:
CWM is a custom recovery. stock recovery is the one you have installed with the stock firmware.
Click to expand...
Click to collapse
Ok, how to access it then? If I press volume up + power + home, CWM starts.