Related
I had a Vibrant before and flashed it constantly. I soft bricked it several time and it was easy just to Odin back to stock and try again. Before I begin to flash Roms on this phone I would like to know how one would fix a bricked Nexus S. I searched "bricked Nexus S" and didn't come up with much.
Sent from my Nexus S using XDA App
Flash a stock img thru fastboot/adb. Just as painless as Odin was if not easier.
Sent from my Nexus S
Yeah I figured that much but I have never used ADB before. What are the commands to flash a stock img and where can I get a stock img? I already have ADB set up, serial # comes up when I enter - adb devices. I'm ready to root and flash but I want to be prepared for anything. I don't want to panic for ten minutes like I did the first time I bricked my Vibrant.
Sent from my Nexus S using XDA App
You should be able to snag a stock image from the development section. As far as what adb commands to use check out any of the root tutorials in development.
Sent from my Nexus S
bricking the phone is not easy... everything can be wiped and reinstalled with ease. Recovery is your friend.
leyvatron said:
bricking the phone is not easy... everything can be wiped and reinstalled with ease. Recovery is your friend.
Click to expand...
Click to collapse
That's why I love this phone. When I first rooted my wife's phone she was a nervous wreck about me ruining it. Now, she jokingly cheers when it boot loops or hangs on the google splash screen.
kenvan19 said:
That's why I love this phone. When I first rooted my wife's phone she was a nervous wreck about me ruining it. Now, she jokingly cheers when it boot loops or hangs on the google splash screen.
Click to expand...
Click to collapse
Coolest wife ever? haha
risegeek said:
Coolest wife ever? haha
Click to expand...
Click to collapse
hehe why'd'ya think I married her
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Van_Dyke said:
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Click to expand...
Click to collapse
not enough information is present. you can attempt to get into bootloader / recovery, plug USB to the computer. When plugged, does the computer make a plugged in noise? if it does.. try turning it on, try using adb on it, etc.
as a last resort: if its not rooted or modified in any way, you can go back to best buy and exchange it since you said you've only had it for 3 days
Van_Dyke said:
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Click to expand...
Click to collapse
First thing to do is pull the battery, let it sit a minute or two, then put the battery back in and try to boot.
Also, try booting into recovery or fastboot. With power off, press and hold volume up button, then press/hold power on switch. You should enter fastboot mode. From fastboot menu, select boot to recovery. The phone will reboot and you'll get to a screen with an "!" and an android robot on it. At that point you press hold power, then press/hold volume up (make note that this is the reverse of what you did earlier).
Once in Recovery, try wiping cache from the menu.
Reboot.
If still no good, then repeat the process but pick factory reset/wipe from the menu in recovery. Note that this will wipe all personal data and apps off the phone but it won't touch your sdcard contents.
The case with pull battery - not working.
I can't enter fastmode using 2 keys combination.
Computer don't recognize the phone. It's brick...
Van_Dyke said:
The case with pull battery - not working.
I can't enter fastmode using 2 keys combination.
Computer don't recognize the phone. It's brick...
Click to expand...
Click to collapse
Last option is to try to trick it into Samsung's Download Mode (see the Odin thread in Development section), but if the keys aren't recognized you can't soft boot into it so you'll need a dongle with a resistor to get there.
Sounds like it's truly a brick at this point. You'll probably have to return it, but I'm concerned about returning a phone that has your personal data on it without being able to wipe it. Doesn't seem like much way around that at this point if you can't get fastboot or download.
get the 301k resistor JIG and then you can go into the download mode even without the 2 keys + usb plug
you can always make your own JIG if you have the materials at home or a nearby Radio shack
Thx for all Your advices
Problem was with the dead battery. The battery died during the night - i don't know why. I think the system waren't able to boot up ant start charging process.
My solution:
I took 9V battery, 2 wires and charged dead battery for a while from 9V battery. Then a put it into phone and plug in to wall charger. Charging process started
Now everything is ok
That's pretty scary that it wouldnt take a charge if run down completelty. But hey handy to know incase it happens to any of us,
If you get any repeat i would take it back to get a fresh battery of course (only right to do so).
here's hoping you never need to though
Van_Dyke said:
Thx for all Your advices
Problem was with the dead battery. The battery died during the night - i don't know why. I think the system waren't able to boot up ant start charging process.
My solution:
I took 9V battery, 2 wires and charged dead battery for a while from 9V battery. Then a put it into phone and plug in to wall charger. Charging process started
Now everything is ok
Click to expand...
Click to collapse
That is scary......
Sent from my Nexus S using XDA App
Bricked
Tried unlocking nexus s last night, now it appears bricked. Cannot connect to computer to reflash as it seems to have wiped the driver. Any ideas on how to bring it back from the dead? thanks
I have managed to see the phone with fastboot. I was hoping that fastboot update, would re-image the brick. Can anyone let me know the correct syntax. I am not able to copy an image onto the phone. Thanks again
Noob {MAC User}... Please be gentle
Greetings Everyone,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I reboot.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamara
warrenb said:
Tried unlocking nexus s last night, now it appears bricked. Cannot connect to computer to reflash as it seems to have wiped the driver. Any ideas on how to bring it back from the dead? thanks
I have managed to see the phone with fastboot. I was hoping that fastboot update, would re-image the brick. Can anyone let me know the correct syntax. I am not able to copy an image onto the phone. Thanks again
Click to expand...
Click to collapse
It would be easier to help you if we knew exactly what you did that caused the problem. You said you tried to unlock it...you mean fastboot oem unlock or something else?
If you can get into fastboot, you're not totally lost, but the computer needs to see the phone to do it.
I'm working in a vacuum here on what your real problem is, but without further details, the things you can try are boot into recovery (from the fastboot mode select boot recovery)...if you're stock recovery, press/hold power, then volume up once you see the android "!". From there wipe cache and whatever else it will let you wipe. Try rebooting. IF that didn't work go back to recovery and try a factory reset of the phone (will delete all your apps and stuff on the phone, but not on the sdcard (pics and stuff).
If none of that works, you can still try getting Clockwork recovery on the phone via fastboot. Boot phone to fastboot and then on computer type the command "fastboot flash recovery <put file name of recovery version you're flashing here>"
Once in clockwork, you should have access to adb via the computer. On your computer go to the Development section here and download any of the various nandroid images posted there. Now you use clockwork mounts and storage menu to mount the sdcard. Then use adb to "adb push <insert path and filename of your nandroid image here> /sdcard"
Unmount the sdcard with the clockwork mounts and storage menu. Now go to the backup menu, select advanced restore and find the nandroid image and restore it.
With any luck, you should be able to boot into a fresh phone.
Went to sleep, phone was working just fine.
Woke up in the middle of the night and saw phone was sitting at the OnePlus boot screen.
Powered it off and back on multiple times, same issue.
Booted into TWRP and it shows it cannot mount /system and says no os installed!
How does this happen?
I was not doing any modding, config changes, etc prior to going to sleep.
I unlocked and rooted a week ago when I got the phone, but have not done anything since and phone has been awesome!
I can get into fastboot and TWRP.
I dont have any backups, etc.
This is exactly why you should keep a backup on your phone at all times, hopefully this is a lesson learned? Anyway, you can still get into fastboot mode so use fastboot to flash the fastboot images and you should be fine.
Transmitted via Bacon
timmaaa said:
This is exactly why you should keep a backup on your phone at all times, hopefully this is a lesson learned? Anyway, you can still get into fastboot mode so use fastboot to flash the fastboot images and you should be fine.
Transmitted via Bacon
Click to expand...
Click to collapse
But what would cause the OS to disappear?
I have seem many posts where this happens when people were messing with the phone, but i was asleep and the phone was working fine all week.
ktskas said:
But what would cause the OS to disappear?
I have seem many posts where this happens when people were messing with the phone, but i was asleep and the phone was working fine all week.
Click to expand...
Click to collapse
I have no idea, and I highly doubt anyone could actually tell you. The only thing to do now is fix your phone.
Transmitted via Bacon
The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.
voxoph said:
The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.
Click to expand...
Click to collapse
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?
cmulk said:
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?
Click to expand...
Click to collapse
Thanks for responding. I am going to try ADB again but I can't get into recovery mode at the time being.
A similar thing just happened to me, except I got right out of it. Device was completely unresponsive, no download mode, adb nothing, indicative of a hard brick. Scared the **** out of me as I've had it less than 6 hours... Started holding buttons, and it came to life after ~1 minute of power button + volume down. Related? Well maybe not, thought I'd post it here. (TWRP 2.8.5 + Rooted CM12)
True Hard Brick, No OS!
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.
TSF14 said:
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.
Click to expand...
Click to collapse
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089
hyelton said:
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.
TSF14 said:
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.
Click to expand...
Click to collapse
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 plug using the OEM LG cable while holding volup and then plugging in the USB cable?
hyelton said:
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 CCCC?
Click to expand...
Click to collapse
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.
TSF14 said:
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.
Click to expand...
Click to collapse
Are you sure your battery is not dead??
hyelton said:
Are you sure your battery is not dead??
Click to expand...
Click to collapse
Yes, if only it was that easy.
There are a few things you can try :
1.) Press the Powerbutton for a longer time
If you have a responce like the LG Logo or something like that, you might want to try and plug it to the computer and use the managing software
with which you can emergency reinstall the firmware.
2.) Press Power + Volume Down
If it restarts into the recovery menu, try to find a way to load a flashable stock rom of your handy onto the memory of your phone in order to "reflash" it.
(I don't know how you can do that )
3.) Go to the shop where you bought it and explain your problem, since rooting a LG device is not really easy to detect the chances that your warranty will cover for it are pretty high.
Sent from my LG-D955 using XDA Free mobile app
http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Read this.
http://forum.xda-developers.com/att-lg-g3/help/bricked-d850-help-t3064874
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Atomschlumpf said:
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Click to expand...
Click to collapse
how old is the device?
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Atomschlumpf said:
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Click to expand...
Click to collapse
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Atomschlumpf said:
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Click to expand...
Click to collapse
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Mr.Ak said:
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Click to expand...
Click to collapse
No, I didn't. I tried the USB Drivers I had already installed, the drivers that came in the package and the QPST Tool suggested in the thread on both my and my girlfriends laptop. But if it doesn't work on ADB/fastboot I probably can't use it anyway since my only two options are having the phone on the fastboot screen or having it constantly reboot....
At this point I'm just really, really frustrated and have sorta accepted it's very likely a hardware issue
I'm with the same problem. In my case, the tool does recognize and shows green after the end but when i try to boot, it only shows the boot logo.
I can enter in fastboot and trying the command "fastboot continue" the brightness goes up, but nothing else
already tried various tools, back to stock, qualcomm , and none worked, so can i throw it out of the window?
Edit: can't enter in recovery, and unlike the op, my phone doesn't reboot (at least i didn't notice it)
I was attempting to downgrade my moto g stylus 2021 from android 11 to 10. Something when wrong during my flash attempt and now I am stuck with a rapid bootloop where a motorolo logo will briefly flash on the screen and then go to back.
I can't seem to get back to fastboot although if I hold the down volume and power button the logo stops flashing and I just get a black screen.
Is there any possible path out of this I can try or did I hard brick my phone?
im having same thing downgrade issue i plug cord in just blink light no fastboot or recovery either.
So if you find a way let me know and ill do the same.
travy said:
im having same thing downgrade issue i plug cord in just blink light no fastboot or recovery either.
So if you find a way let me know and ill do the same.
Click to expand...
Click to collapse
Same boat as you two. Used "fastboot set_active b" after flashing stock firmware and ignored the bootloader warning. Now im stuck hardbricked with no success blankflashing. Including info for EDL Mode and log from one of my blankflash attempts as well as the correct firehose programmer for this device.
ezril said:
I was attempting to downgrade my moto g stylus 2021 from android 11 to 10. Something when wrong during my flash attempt and now I am stuck with a rapid bootloop where a motorolo logo will briefly flash on the screen and then go to back.
I can't seem to get back to fastboot although if I hold the down volume and power button the logo stops flashing and I just get a black screen.
Is there any possible path out of this I can try or did I hard brick my phone?
Click to expand...
Click to collapse
Seems to be a few of us in the same situation. I downloaded Motorola's program for, supposedly, diagnosing and fixing their phones. I'm hesitant to use it because the only place I have Windows is a VM and I've found that the connection between the phone and the computer can get a little sketchy on reboots because the USB forwarding.
Linux_SF said:
Seems to be a few of us in the same situation. I downloaded Motorola's program for, supposedly, diagnosing and fixing their phones. I'm hesitant to use it because the only place I have Windows is a VM and I've found that the connection between the phone and the computer can get a little sketchy on reboots because the USB forwarding.
Click to expand...
Click to collapse
I have had no luck whatsoever. Originally I thought I was successful using a blankflash although it was not. I've pretty much given up on that device for now although if you have anything that may help, I have no problem being the guinea pig, lol.
Keith