Related
Bricked your phone? You've come to the right place, if you're one of the blessed. A lot of the newer Captivates have button combinations disabled. Before you go modding your phone, make sure that you can get into download or recovery using these button combos. If you can't, your best bet is to return your phone to an AT&T store and beg for a new one.
THE BUTTON COMBOS
Power-power
Download-volume up+volume down+plug in usb cord
Recovery-volume up+volume down+power
There you have it. Thanks for reading.
What is the point of this when there are 3 methods in the Odin 3 one click thread which is a sticky? Just curious how this deserves its own thread.
When my phone was stuck at the Galaxy S logo, i was able to send the adb reboot recovery command to it to get into recovery mode.
Are bricked phones normally stuck at the logo too, or was it just me?
I wanted to link to just the button combos in the bible. Also, the one click Odin isn't a sticky anymore.
From mah fonez
Why don't you just link to a single post in a thread or post in the odin thread and link to that single post? Just a suggestion so there isn't too many threads started for just a little information like you posted. Great work on the bible though. Glad to see a lot of stuff being compiled into one thread.
How does this relate to development? With a title like this, i thought we had some button hacks.
BAH!
You should also include more than the button combinations as well if you're going to make this post useful. Simply holding the volume buttons + power will do absolutely nothing on my phone. I spent a good amount of time looking for more detailed instructions on recovery mode when the phone was new and no one posted them. There are also a lot of posts that talk about the at&t splash screen flashing and when to release the buttons but that's not terribly useful either. Download mode is a little more covered but still has lots of people giving different instructions. For those the future new people that might read this thread,
For Recovery mode:
Power off
Hold both volume buttons
Push power
Release power when you see the AT&T splash screen
Release the volume buttons a second or so later
After the splash screen goes away you should be in recovery mode
Continuing to hold all three buttons will simply cause the AT&T splash screen to flash at you. I can also continue to hold the volume buttons after releasing power but it is not needed.
For Download mode:
Power Off
Plug USB into computer
Hold both volume buttons
Plug USB into phone
The above will immediately send my phone into download mode. For flashing, most people recommend the steps below to maximize the chance of success with Odin
Power off
Remove battery, sim, microsd
Open Odin
Plug USB into computer
Hold both volume buttons
Plug USB into phone
Put battery in
You should now be in download mode and free to flash with odin.
I agree with the holding volume up and down while plugging the phone into the computer with Odin opened and configured to flash soon as it detects the phone.
All other methods only add confusion.
How do I get out of download mode?
oh nvm, I just removed battery and I could reboot it fine.
I am stuck on this screen
h ttp://img820.imageshack.us/img820/530/screenshotzz.jpg (remove space I can't post links)
I am on downloading mode but the screen looks like this I am using windows 7 64bit, I tried installing 32 bit on another partition to see if it helped but it didn't
Am I missing something or do you have to have something installed before the procedure
frozenreality44 said:
h ttp://img820.imageshack.us/img820/530/screenshotzz.jpg (remove space I can't post links)
I am on downloading mode but the screen looks like this I am using windows 7 64bit, I tried installing 32 bit on another partition to see if it helped but it didn't
Am I missing something or do you have to have something installed before the procedure
Click to expand...
Click to collapse
You have odin started before you plugged in your usb cable into your phone or computer? Does you computer recognize you phone in mass storage mode? The screen shot you provided shows the phone is not recognized by odin.
I got it now but I am stuck even further odin finished no errors and now the phone just loops on the att logo, or if I try to plug the usb both up and down volume buttons pressed to enter recovery mode again it just loops the battery charging any ideas thanks
This is all covered thoroughly in the "READ BEFORE FLASHING" sticky. Which everyone should read BEFORE flashing!!! Hey, what a coincidence.
Okay, first off, I know there are threads about this, but none of them were helpful on my problem. So if you're having the same issue and it worked, don't forget to hit the thanks button! This isn't a very well made instruction, but it'll suffice. I haven't seen this method, so I thought I should share it.
Device: LG G2 AT&T D800
- I assume this may work on all the other variants as well
Issue:- Device won't boot to Download Mode even when doing VOL Up + USB, and my android system has crashed/force closed
Solution: (Warning: this is very tedious and annoying so put up with it like I did)
1. If your phone doesn't have USB debugging already enabled, go ahead and do so
- This... I had to press quickly to get to the Software Tab and tried to simultaneously click OK while trying to turn on Developer Option.
2. Install ADB if you haven't already. Run adb as Admin, type in adb reboot fastboot
- You should then boot into fastboot with a bunch of small white text saying some fastboot and shizz
3. Go ahead and hold the power button, at the same time holding the Volume Up button
4. DOWNLOAD MODE should come up
5. You can now restore your G2, You can look up the files somewhere here in the forums to restore.
Good luck, enjoy, say thanks, click thanks.
"We build too many walls, and not enough bridges"
I have international D802 where I have installed a custom rom based on android 4.4.2. Yesterday I wanted to upgrade it to an android 5 rom and and mistakenly installed a new custom rom that was builded for F320S. After reboot only the fastboot mode was displayed. Then I’ve tried to repair the download mode by flash the img files, but as I’ve verified later they was not intended for LG G2 D802 32Gb version. So now if I try to enter either the download mode or the hard reset / recovery I see only the LG logo with security error.
I’ve tried a different button-combinations. Please correct me if it was wrong.
For power off I’ve pressed the power button for about 15 seconds, wait until the logo is displayed then hidden then shortly displayed again and then the display is black.
For hard reset / recovery I’ve pressed press volume down button and power button together until the LG logo appears on the screen. When the LG logo is displayed, un-pressed the power button, but keep pressing the volume down key and then pressed once more the power button. Then the LG logo is displayed again, and then below was the security error displayed.
For download mode, I’ve pressed and hold the volume up button and connected the USB cable. But after some seconds the security error was displayed and the device manager in windows didn’t showed any changes.
Is it possible to recover the phone from the security error state? Any help would be appreciated.
EDIT:
Solved in following steps.
1. Open the phone like described here: LG G2 is UNBRICKABLE NOW!
It was not hard and you don't need any special tools, only a small screw driver. Look first this both videos https://www.youtube.com/watch?v=15krGmydqgQ&feature=youtu.be and http://forum.xda-developers.com/show....php?t=2582142. The do the steps till you can access the processor chip. Ensure the battery is disconnected. By disconnecting the both left and right plates be sure to separate it from the surface.
2. Connect the phone to the PC with USB cable. Open the device manager.
3. Short the test pins on the chips, see the https://www.youtube.com/watch?v=FiofVOqfnxw with e.g. bent paper clip till you'll see the new QHSUSB qualcomm 9006 connection on COM port. Then you'll see a lot of windows messages about to format the new founded partitions. Close them.
4. Flash an images, like laf.img,aboot.img, boot.img from your phone model using export very partition see https://www.youtube.com/watch?v=_d5b_osUTug for details and files.
5. Now the download mode is available. Remove the usb cable, enter the download mode and flash a original stock rom for your model using the LG Flash Tool 2014.
Now your phone is unbricked!
Any questions?
What is the security error on LG G2? Is it a common way to reset some settings to reset it?
Added solution in the first post. If you have any questions, please post.
Ive done till step 3, only one window poped up, and i don't get step 4, i still got the security thing...
Help I guess?
avi57 said:
Ive done till step 3, only one window poped up, and i don't get step 4, i still got the security thing...
Help I guess?
Click to expand...
Click to collapse
You've shorted a wrong pin, please try again step 3 untill you will see the qualcomm 9006 and not 9008 or another number.
No matter how many times I have tried, the combination of Vol Down+Home+Power together does nothing, the phone just continues to load normally, I cannot access download mode.
My S5 (G900F) is on Android 6.0.1, which was the last software update for the phone, I would like to try 7(Nougat) but can't get anywhere near rooting or flashing.
The phone functions fine as it is, but for the last ?? Years I have used Windows Phones so android of quite alien to me but more preferable than apple. I would like to check out what's available in different builds.
anyone any ideas why it won't let me in, USB is enabled and it is in developer mode.
It can be a bit fiddly to do when you're starting off. What I normally do is press and hold in order volume down, home and then power. The boot wont start unless you press the power button so what this does is ensure that the other 2 are pressed by the time you press the power button. Only stop holding all 3 buttons down when it boots into download mode. Hope this helps
Eggleston11 said:
It can be a bit fiddly to do when you're starting off. What I normally do is press and hold in order volume down, home and then power. The boot wont start unless you press the power button so what this does is ensure that the other 2 are pressed by the time you press the power button. Only stop holding all 3 buttons down when it boots into download mode. Hope this helps
Click to expand...
Click to collapse
It doesn't work, That is what I have been doing, The Galaxy s5 screen appears, I keep holding, it disappears, vibrates and re-appears, I keep holding and it disappears again, vibrates and re-appears, it does this 5 times before I get fed up and release the power button and then the other 2, it then goes into the Samsung screen and continues loading, sometimes it goes to the "Optimising Apps" mode with the two spinning cogs before finishing the load sequence.
Thanks for the suggestion but it's not playing as it should.
comuscomp said:
It doesn't work, That is what I have been doing, The Galaxy s5 screen appears, I keep holding, it disappears, vibrates and re-appears, I keep holding and it disappears again, vibrates and re-appears, it does this 5 times before I get fed up and release the power button and then the other 2, it then goes into the Samsung screen and continues loading, sometimes it goes to the "Optimising Apps" mode with the two spinning cogs before finishing the load sequence.
Thanks for the suggestion but it's not playing as it should.
Click to expand...
Click to collapse
Weird...
Plan B - Do you have ADB installed on your computer? link: https://forum.xda-developers.com/showthread.php?t=2588979 (for windows install just in case you don't have it - if you have a Mac or Linux, you'll have to look for it).
Get familiar with ADB if not already: https://www.androidpit.com/how-to-install-adb-and-fastboot
Open command prompt (on windows), enter the command "adb reboot recovery" . It should boot into recovery.
The usual disclaimer is that I am not responsible in the unlikely event that something goes wrong to your phone or computer. Hope this helps
Eggleston11 said:
Weird...
Plan B - Do you have ADB installed on your computer? link: https://forum.xda-developers.com/showthread.php?t=2588979 (for windows install just in case you don't have it - if you have a Mac or Linux, you'll have to look for it).
Get familiar with ADB if not already: https://www.androidpit.com/how-to-install-adb-and-fastboot
Open command prompt (on windows), enter the command "adb reboot recovery" . It should boot into recovery.
The usual disclaimer is that I am not responsible in the unlikely event that something goes wrong to your phone or computer. Hope this helps
Click to expand...
Click to collapse
Thanks for the help, now we have a tale of woe. some things were best not touched, after following a fairly well detailed account of updating to Android 7 the screen filled with line after line of red text and froze.
I had to remove the battery to turn it off, now I have a brick that will not boot. I get the Samsung Galaxy S5 flash screen with a little yellow "Set Warranty Bit : kernel" at the top of the screen.
I think I had better post a new thread about this.
comuscomp said:
Thanks for the help, now we have a tale of woe. some things were best not touched, after following a fairly well detailed account of updating to Android 7 the screen filled with line after line of red text and froze.
I had to remove the battery to turn it off, now I have a brick that will not boot. I get the Samsung Galaxy S5 flash screen with a little yellow "Set Warranty Bit : kernel" at the top of the screen.
I think I had better post a new thread about this.
Click to expand...
Click to collapse
Questions that will help in assisting you: Can you still boot into download or recovery mode? What nougat ROM did you flash? What steps did you take to flash the nougat ROM? What happened?
If you can enter download mode, then you can reflash a stock ROM via odin to hopefully save your S5, you can find one on Sam Mobile. Without the right info, that is the best general advice I can give.
You can try posting a new thread to hopefully recruit more help. If you decide to do so, include the answers to the questions I have posted above. Otherwise, I am happy to attempt to assist you in recovering the functionality of your S5 on this thread.
Eggleston11 said:
Questions that will help in assisting you: Can you still boot into download or recovery mode? What nougat ROM did you flash? What steps did you take to flash the nougat ROM? What happened?
If you can enter download mode, then you can reflash a stock ROM via odin to hopefully save your S5, you can find one on Sam Mobile. Without the right info, that is the best general advice I can give.
You can try posting a new thread to hopefully recruit more help. If you decide to do so, include the answers to the questions I have posted above. Otherwise, I am happy to attempt to assist you in recovering the functionality of your S5 on this thread.
Click to expand...
Click to collapse
No, I can't get into download or recovery, I have tried with the 3 key combo and using ADB, the first still refuses to work and the ADB doesn't find the device.
Smart Switch won't connect nor will Odin.
Lineage 14-1. and open-gapps-arm-6.0-micro.
I had opened a new thread before I got your reply, how do I include your answers into that tread? "Bricked after attempted Update: Help".
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Conrad-007 said:
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Click to expand...
Click to collapse
Hi, Conrad-007...
This is very strange - your Nexus 7 is clearly 'bootable' (sort of), with a functioning bootloader, ie., it's not hardbricked... or you wouldn't be seeing the Google logo.
In the distant past, back when I used to experiment with custom kernels on my Nexus 7, it sometimes required the POWER BUTTON+VOL DOWN buttons be pressed and held down for a good 30 seconds or more, to generate the necessary 'interrupt', and force the device into the bootloader.
My first instinct, is to suggest you may possibly have a problem with your VOL DOWN button, and maybe it's stuck somehow or not making contact.
It also occurred to me, that you might be able to access the bootloader with...
Code:
adb reboot bootloader
...or possibly...
Code:
adb reboot fastboot
...and even...
Code:
adb reboot recovery
But unfortunately, I'm pretty sure you need to be running fully booted Android or booted into a custom recovery (eg., TWRP) before you can issue ADB commands. I haven't tinkered around in this area of Android for a couple of years now, so my memory of the specifics is a little hazy.
Anyhow, here's a fairly comprehensive listing of Nexus 7 button presses/interrupts, which maybe of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
--------------------------------
Anyway, just some thoughts that might give you some clues/ideas, that may resolve your problem.
Good luck, and I hope you find something that works.
Rgrds,
Ged.
Thanks Ged for the detailed answer.
Unfortunately it seems that my Nexus is not booting complete (not finishing the booting sequence due to corrupted bootloader?) and so I cannot send to it any adb or fastboot command...
I read in the meantime that holding the VOL up button while powering up the Nexus, it will bring it in the APX mode (whatever this mean) and indeed, my computer recognize it as "APX" device.
I hope at least that this is a good sign and a first step to bring my Nexus back to life... but I have no idea what is the APX mode and what can I do in this mode to attempt to save my device...
Do you (or somebody else) have (has) an advice or tutorial for me concerning this?
Regards,
Conrad
Hi Conrad.
I'm in exactly the same situation (I've mistakenly posted a duplicate thread here https://forum.xda-developers.com/nexus-7/general/bricked-tilapia-t4005149). Let's continue here. So:
1. I spent 4 hours trying all possible button press combinations, including VERY long presses. I didn't notice any APX device or Uknown device connected to Windows. I might have missed it, you gave me hope. I will check again.
2. APX mode enables low level access to the chipset via nVidia tool nvflash. You probably came accross these threads here on xda:
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-using-t3342364
https://forum.xda-developers.com/showthread.php?t=2564615
https://forum.xda-developers.com/showthread.php?t=2455927
https://forum.xda-developers.com/showthread.php?t=2340237
I haven't so far, as I was not aware of the visibilty of the tablet in Windows. I will check again.
Well, I must have been blind not to have seen all the posts here on xda and everywhere else. I went through the threads and now I know:
1. I can see the tablet in APX mode in Windows. Possibly I could correctly set up the driver.
2. This would be totally useless, since I hadn't backed up necessary blob.
I have a new paperweight