Database Info

Fixing a bricked Nexus S

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.

[Q] Help! My phone is in a bootloop. Unable to stay in download/ recovery mode...

I'm really stupid.
I started when I flashed Cyanogenmod from 10.1 to 10.2 and started getting random resets. After getting impatient, I stupidly tried to downgrade back to 10.1 without a factory reset which caused the bootlooping. Then I tried going going into recovery mode and tried to restore with cwm recovery but my phone just randomly shutdown.
tl;dr Now I can't enter into recovery mode at all (I can see the blue words then it shuts off), can enter download mode for maybe 4-6 sec before it shuts off, and my phone still bootloops if I try to properly turn it on.
Can anyone help me?

john2166 said:
I'm really stupid.
I started when I flashed Cyanogenmod from 10.1 to 10.2 and started getting random resets. After getting impatient, I stupidly tried to downgrade back to 10.1 without a factory reset which caused the bootlooping. Then I tried going going into recovery mode and tried to restore with cwm recovery but my phone just randomly shutdown.
tl;dr Now I can't enter into recovery mode at all (I can see the blue words then it shuts off), can enter download mode for maybe 4-6 sec before it shuts off, and my phone still bootloops if I try to properly turn it on.
Can anyone help me?
Click to expand...
Click to collapse
take out batter for couple mins .put it back in . pres hold power home vol up .. sometimes takes couple tries to get into recovery mode . factory reset flash rom correct gapps ..first boot sometimes takes couple mins . remember nightlies are betas not all play well

twistedillutions said:
take out batter for couple mins .put it back in . pres hold power home vol up .. sometimes takes couple tries to get into recovery mode . factory reset flash rom correct gapps ..first boot sometimes takes couple mins . remember nightlies are betas not all play well
Click to expand...
Click to collapse
Thanks for trying to help, but it didn't work. Tried it many times, but I did get to the "Samsung Galaxy S III" logo after recovery mode.
Also to clarify, I wasn't a nightly it was a stable version of Cyanogen. It's just that your not suppose to directly downgrade a Cyanogenmod without a factory reset or it could cause problems, which I found out later.
Edit: It's getting late so I'm going to check back in the morning. Thanks.

john2166 said:
Thanks for trying to help, but it didn't work. Tried it many times, but I did get to the "Samsung Galaxy S III" logo after recovery mode.
Also to clarify, I wasn't a nightly it was a stable version of Cyanogen. It's just that your not suppose to directly downgrade a Cyanogenmod without a factory reset or it could cause problems, which I found out later.
Edit: It's getting late so I'm going to check back in the morning. Thanks.
Click to expand...
Click to collapse
You said you could enter download mode and stay there? If so i highly suggest you go and ODIN your phone back to stock re-root, install recovery then go ahead and install CyanogenMod. This most likely ill fix your problems, but only do it if your phone can go into download mode and stay there!

Mtsprite said:
You said you could enter download mode and stay there? If so i highly suggest you go and ODIN your phone back to stock re-root, install recovery then go ahead and install CyanogenMod. This most likely ill fix your problems, but only do it if your phone can go into download mode and stay there!
Click to expand...
Click to collapse
No unfortunately my phone can't stay in download mode. At least not long enough to use odin.

john2166 said:
No unfortunately my phone can't stay in download mode. At least not long enough to use odin.
Click to expand...
Click to collapse
If you remove the battery and put it back in does it auto turn on?

I am curious to see what others here think, but in my limited experience with embedded devices, this is almost sounding like a hardware problem.
The phone was randomly rebooting before -- I don't think it was established earlier that recovery and download modes were solidly working when the conditions started. From your description, the symptoms appear sometime after the CM 10.2 upgrade, but that does not mean the upgrade or downgrade caused this issue.
It sounds odd to me that the phone would go into download mode, and then just sporadically reset. Perhaps others here can comment if this behavior in download mode has been observed with other botched software flashing.
I am just curious, and just verified on my S3. Try the following:
- boot into download mode, but leave the warning screen active. See how long that lasts or if you get reset quickly
- Plug the phone into a power source, boot into download mode, confirm, immediately remove the battery, and let the phone sit to see if it resets.
What I am looking to see is if a steady power supply here helps keeping download mode active; maybe your battery is shot and causing erratic behavior. Also, try to make a careful inspection of the phone, especially if all the screws are tight, the battery compartment doesn't have anything loose or funny looking, power button seems to be snappy and crisp (not mushy or sticking), etc.
Good luck.

ThePagel said:
If you remove the battery and put it back in does it auto turn on?
Click to expand...
Click to collapse
Kind of. It shows the Samsung logo when I put it it in. It only goes into a bootloop if I hold the power button for a few seconds.

vax1170 said:
I am curious to see what others here think, but in my limited experience with embedded devices, this is almost sounding like a hardware problem.
The phone was randomly rebooting before -- I don't think it was established earlier that recovery and download modes were solidly working when the conditions started. From your description, the symptoms appear sometime after the CM 10.2 upgrade, but that does not mean the upgrade or downgrade caused this issue.
It sounds odd to me that the phone would go into download mode, and then just sporadically reset. Perhaps others here can comment if this behavior in download mode has been observed with other botched software flashing.
I am just curious, and just verified on my S3. Try the following:
- boot into download mode, but leave the warning screen active. See how long that lasts or if you get reset quickly
- Plug the phone into a power source, boot into download mode, confirm, immediately remove the battery, and let the phone sit to see if it resets.
What I am looking to see is if a steady power supply here helps keeping download mode active; maybe your battery is shot and causing erratic behavior. Also, try to make a careful inspection of the phone, especially if all the screws are tight, the battery compartment doesn't have anything loose or funny looking, power button seems to be snappy and crisp (not mushy or sticking), etc.
Good luck.
Click to expand...
Click to collapse
Thanks. I've tried what you asked with and without the battery, and the warning screen stays on for about 3-7 secs for both circumstances. I also tried replacing my battery with another one lying in my house. The battery compartment and the power button is seemingly normal.

Doesn't help ... but this other thread sounds a little bit similar to your download mode issue ... http://forum.xda-developers.com/showthread.php?t=2608201
Sounds like you have a very small window of opportunity before the download mode reboots. Maybe try this just to see:
- make sure your windows (assuming) drivers are all set up. Hopefully if you had ODIN working already, then you are set
- get a copy of heimdall command line version
- get the command ready to execute: heimdall print-pit --no-reboot
- In the small window of opportunity you have ... enter download mode, confirm, press enter on heimdall command and see if anything interesting happens
See if you get anything. If you do you might try to quickly use up-arrow on the CMD line to recall that command and run it again. If you know anything about windows batch scripting, you might try scripting the heimdall command above in a loop.
My thought here is that if heimdall cannot initiate anything useful, then your software is probably lost. If heimdall can output the PIT data, could be that download mode software is good, but the hardware is bad. If rapidly executing heimdall keeps your device active longer than usual, that might be an interesting tid-bit to know.
I am no expert here, so please seek other's more expert advice before trying anything. If your boot mode is screwed, perhaps the thread on [GUIDE] Debrick your bricked s3! [BOOTLOADER/HARDBRICK] might work, but again unless someone else confirms this, I would not try that until you are about ready to accept total loss.

[Q] lg g2 d801 bricked, no download mode,no fast boot only stuck at lg logo

hi
i think i bricked my lg g2 d801 t-mobile by first installing stock d802(i know i messed up) after that my phone went to fast boot mode.i used adb to load img files to bring back download mode and then i tried tot method to install stock rom which failed, i then tried pushing img files from adb to get atleast custom recovery but that further bricked my phone which is basically living in this situation:
-no download mode
-no fastboot
-stuck at lg logo when i try to power it on
-no recovery
also i tried using linux to load the img files but linux wont recognize my lg g2 when i type in the commands
PLEASE PLEASE PLEASE help me i am desparate

xtremepowered said:
hi
i think i bricked my lg g2 d801 t-mobile by first installing stock d802(i know i messed up) after that my phone went to fast boot mode.i used adb to load img files to bring back download mode and then i tried tot method to install stock rom which failed, i then tried pushing img files from adb to get atleast custom recovery but that further bricked my phone which is basically living in this situation:
-no download mode
-no fastboot
-stuck at lg logo when i try to power it on
-no recovery
also i tried using linux to load the img files but linux wont recognize my lg g2 when i type in the commands
PLEASE PLEASE PLEASE help me i am desparate
Click to expand...
Click to collapse
Have you tried this method?
http://forum.xda-developers.com/showthread.php?t=2701799
Not sure if it's applicable.

pitchdarkice said:
Have you tried this method?
http://forum.xda-developers.com/showthread.php?t=2701799
Not sure if it's applicable.
Click to expand...
Click to collapse
Thanks for your reply but I don't think that works, cause the link you have me is how to root device.

It still restores the image, you can choose to root or not
Sent from my SM-P600 using Tapatalk

xtremepowered said:
hi
i think i bricked my lg g2 d801 t-mobile by first installing stock d802(i know i messed up) after that my phone went to fast boot mode.i used adb to load img files to bring back download mode and then i tried tot method to install stock rom which failed, i then tried pushing img files from adb to get atleast custom recovery but that further bricked my phone which is basically living in this situation:
-no download mode
-no fastboot
-stuck at lg logo when i try to power it on
-no recovery
also i tried using linux to load the img files but linux wont recognize my lg g2 when i type in the commands
PLEASE PLEASE PLEASE help me i am desparate
Click to expand...
Click to collapse
Any luck fixing it ?

Kdz flashtool could solve the problem or using an usb.... U could leave the phone until the battery goes off and then recharge a little bit and try download mode again... the first method should work ... press the buttons correctly and connect the usb... working in 95%

same problem
tried the mentioned comments but still nothing for me.
PLEASE PLEASE let me know if you fix the problem OP

lgg2 d801 stuck on lg logo
Nabuco76 said:
Kdz flashtool could solve the problem or using an usb.... U could leave the phone until the battery goes off and then recharge a little bit and try download mode again... the first method should work ... press the buttons correctly and connect the usb... working in 95%
Click to expand...
Click to collapse
could you please explain what you did?
my lgg2 d801 simply boots into the LG logo screen and stays there til it dies.
I do not know too many technicalities when it comes to adb or ubuntu, in fact i dont even know if those programs go on the phone or the computer through usb..
simple clarifications would make the world of difference to me as my phone is useless now.
I can enter download mode using your "let phone die then try again method" but i dont know what to do from there..
Please help me restore my phone to the 4.4.2 kitkat i had previously
thannks in advance

d801 problems
I have a D801 that was rooted on 4.4.2, and I stupidly took the OTA update. I can still use my phone to make calls, but nothing associated with google works. The phone will not boot into download mode, there is no recovery and no fast boot. I have tried everything. It will no reroot or anything . Is there anything that I can do.

zorrozeek said:
I have a D801 that was rooted on 4.4.2, and I stupidly took the OTA update. I can still use my phone to make calls, but nothing associated with google works. The phone will not boot into download mode, there is no recovery and no fast boot. I have tried everything. It will no reroot or anything . Is there anything that I can do.
Click to expand...
Click to collapse
I'm not sure if this will work for the G2 but it worked for my G Pad just last night.
http://forum.xda-developers.com/showthread.php?t=2590185

spec4 said:
I'm not sure if this will work for the G2 but it worked for my G Pad just last night.
http://forum.xda-developers.com/showthread.php?t=2590185
Click to expand...
Click to collapse
Did you see where the directions say put the device in download mode. My device will not enter download mode.

zorrozeek said:
Did you see where the directions say put the device in download mode. My device will not enter download mode.
Click to expand...
Click to collapse
I can confirm that that method worked for my G2. Make sure you press and hold volume up then plug the phone in. Hold volume up till you see the small box saying its in download mode.
The nice thing about this method it doesn't wipe your data.
Make sure you have downloaded the most current drivers first though before you plug in your phone. Then go to options and update recovery.
Sent from my LG-V500

spec4 said:
I can confirm that that method worked for my G2. Make sure you press and hold volume up then plug the phone in. Hold volume up till you see the small box saying its in download mode.
The nice thing about this method it doesn't wipe your data.
Make sure you have downloaded the most current drivers first though before you plug in your phone. Then go to options and update recovery.
Sent from my LG-V500
Click to expand...
Click to collapse
It worked for you because your partitions were not messed up. I know the procedure for getting into download mode, I tell you that it no longer works. Volume up while plugging usb in now gets me a battery charging icon . When you have a rooted phone running 4.4.2 and apply OTA update, it screws the partitions up. I can still send and receive calls, just can't sign into google or use playstore .

zorrozeek said:
It worked for you because your partitions were not messed up. I know the procedure for getting into download mode, I tell you that it no longer works. Volume up while plugging usb in now gets me a battery charging icon . When you have a rooted phone running 4.4.2 and apply OTA update, it screws the partitions up. I can still send and receive calls, just can't sign into google or use playstore .
Click to expand...
Click to collapse
Interesting.
In the other post I found this
ratchet26 said:
I had a similar problem with my T-Mobile LG G2 where I was rooted and accepted an OTA. It broke root and I couldn't get IOroot or Stumproot to work. Went to flash a downgrade and found the phone wouldn't go into download mode. It was NOT bricked. I finally tried playing around with the LG Mobile Support Tool (B2CAppSetup.exe). Of course it detected that my phone already had the latest firmware from T-Mobile, but then I clicked Options>Upgrade Recovery.
It downloaded for a while then I noticed it had put my phone into download mode (it said "Rooted" in red letters at the bottom). Then it flashed the same firmware over and I immediately tested, it entered download mode right away. But I didn't end up needing that as Stumproot was able to brute force it now after the recovery flash.
Anyway, I couldn't find an answer anywhere else. Most results also have a bricked phone, but that wasn't my issue. This solved my problem and maybe it could work for others.
Click to expand...
Click to collapse
Seems like its possible to get into download mode. I don't know, maybe yours is just different.

spec4 said:
Interesting.
In the other post I found this
Seems like its possible to get into download mode. I don't know, maybe yours is just different.
Click to expand...
Click to collapse
mine is not different, just corrupted. Even took it to a craigslist repairman. He said that he did not have the expertise to repair it. It can't be put in recovery, download or fastboot mode. It also can't be rerooted.

ill ready repaired one equal but need it "octoplus box sw" for it

Really stuck :( accidentally accepted OTA now phone is stuck in CWM

Hi, I accidentally accepted an OTA update last night without thinking. My phone rebooted and went to philz touch recovery. after much playing around i have been unable to get the phone to see my CWM backup on the external SD card. So my next plan was to flash back to the original rom. The trouble is that despite installing the correct (i think) usb adb driver the LG mobile update tool cannot detect the phone. I've tried getting the phone into download mode which for mine appears to need volume +, Volume - and usb plugging in but i just get a screen of Korean writing with 3 options. each option i choose just reboots the phone back to CWM. no matter what i have tried i cannot seem to get anything to flash on it?
Its an F350k, i'm sure it is recoverable as i can get the Lg boot logo and CWM but i simply cant get anything to install???
forgot to say i tried sideloading as well but I'm not really sure what i should sideload. i tried the stock kdz but that didnt work. my backup isnt zipped, should i zip it and try that?
any help would be really appreciated

I take it you have tried the volume up and plugging in the Usb? You can also try booting to cwm and then via ADB running adb reboot bootloader
Verstuurd vanaf mijn LG-D838 met Tapatalk

Yes, the volume up and USB doesnt work. if i press volume up, volume down and then plug the USB in I get a screen of korean writing with 3 options all of which end up taking me back to the CWM. I tried sideloading and was able to transfer files across to the phone but it wouldnt open them to flash. I've decided I am going to send it to a JTAG unbricker as its probably going to be quicker. Lesson learnt. Thanks for your help by the way

try this something happen to me before and fix my f350s , hope can help you.
http://forum.xda-developers.com/showthread.php?t=2451696

Same thing happened to me yesterday. any tips on getting this phone to work again? mydoom's solution is for twrp. unfortunately im using cwm from sphinx's app.
edit: tried adb command via adb sideload in cwm. thanks for the help mydoom!

Samsung S6 Boot Loop

Hi,
Apologies if this has been asked before, but I've done a relatively thorough search and I can't find a solution to this problem.
I have an S6 (SM-G920F), It was playing up for a few weeks before this, not charging well, and what not, thought it was a cable/hardware issue. Then it stopped working entirely. Initially when it was plugged into the wall it would say it was 91% charged, but if you tried to turn it on it would turn off, and reboot into the charging screen.
I've done quite alot of reading and I've ended up flashing it with Odin (I have a single .md5 file, which i've loaded onto the phone via AP) using the most recent FIrmware UK EE for the SM-G20F. This was successful, however now it only loads the Black screen with white text Samsung S6 powered by android screen and then goes blank and back to the white text screen.
I downloaded an alternative firmware (the one previous version), but this has had the same effect. I've tried to repartition with odin, but this fails.
1.) Is there anyway I can fix this?
2.) If not Is there anyway to remove files whilst in downlod mode?
3.) If I cannot fix it or recover my data, is there anyway to wipe the data securely from my phone so I can sell it for parts?
At present, I can't access recovery mode, only download mode. But whilst Odin communicates with the phone in download mode, I can't seem to access my files from explorer?

1. I would say you'd have to clear cache, immediately after flashing the firmware with Odin, but to do that, you'd have to get to Recovery Mode first...
Why can't you get to it? Does it just start trying to boot nornally? Because if so, it's just a matter of timing it. What I do is... hold power+home+voldown to get to the screen that asks me if I want to get into Download Mode, I press cancel, and immediately start holding power+home+volup until I see the bootsplash screen, and release the power button but keep holding home+volup, and it gets me to Recovery every time, even when I have difficulties such as this.
2. Not that I'm aware of. BUT you could flash TWRP with Odin, and if you then can manage to get to Recovery, you just need to plug your phone into a computer, and your phone will show up in the computer as a device/disk and you can freely remove stuff from it.
If... IF this were to work, I would suggest downloading a stock-based ROM and flashing it. It's far more likely to work properly and bootup without issue than the firmwares you can get, and it's far less much of a headache to do.
3. Nope. There are apps that can wipe data securely (such as Shreddit which does it according to military standards), but it can't be done from Download Mode. There may be some script that could do it in Recovery Mode, but I doubt it.
I mean... technically... you could flash TWRP, go to Recovery, move to your PC all the stuff you want to keep, select the wipe option in TWRP and then transfer randomly generated data from your PC to your phone until it's full - there are many apps that can generate such data. It's not something you could pass off as very very secure, but it should suffice.
I seem to always keep going to trying TWRP - so, you know, give it a shot.

King-V said:
1. I would say you'd have to clear cache, immediately after flashing the firmware with Odin, but to do that, you'd have to get to Recovery Mode first...
Why can't you get to it? Does it just start trying to boot nornally? Because if so, it's just a matter of timing it. What I do is... hold power+home+voldown to get to the screen that asks me if I want to get into Download Mode, I press cancel, and immediately start holding power+home+volup until I see the bootsplash screen, and release the power button but keep holding home+volup, and it gets me to Recovery every time, even when I have difficulties such as this.
2. Not that I'm aware of. BUT you could flash TWRP with Odin, and if you then can manage to get to Recovery, you just need to plug your phone into a computer, and your phone will show up in the computer as a device/disk and you can freely remove stuff from it.
If... IF this were to work, I would suggest downloading a stock-based ROM and flashing it. It's far more likely to work properly and bootup without issue than the firmwares you can get, and it's far less much of a headache to do.
3. Nope. There are apps that can wipe data securely (such as Shreddit which does it according to military standards), but it can't be done from Download Mode. There may be some script that could do it in Recovery Mode, but I doubt it.
I mean... technically... you could flash TWRP, go to Recovery, move to your PC all the stuff you want to keep, select the wipe option in TWRP and then transfer randomly generated data from your PC to your phone until it's full - there are many apps that can generate such data. It's not something you could pass off as very very secure, but it should suffice.
I seem to always keep going to trying TWRP - so, you know, give it a shot.
Click to expand...
Click to collapse
Thanks for your reply! So after flashing it goes straight back into the boot loop. Weirdly if its plugged into my laptop it spend about a second or two on the "Samsung Galaxy S6: Powered by Android" screen before plunging into darkness and shortly after repeating the same message. However if I plug it into the wall it spend over twice as long on that screen before repeating the cycle. It never goes any further.
I've tried your suggestion about perhaps its timing for recovery mode, but even if I go straight from cancelling download mode to trying the power, up and home key it doesn't go to recovery. I've tried a variety of timings both plugged into my laptop and plugged into the wall to no avail. If the phone isn't plugged in, it literally won't do anything whatsoever, won't even hint at turning on.
So Next I tried flashing it with TWRP via Odin and nothings changed, exactly the same bootloop and I still can't get into recovery mode.
I'm starting to think that sadly this phone my be beyond repair! Thanks for your help though, much appreciated.

Hi! I usually run out of my bootloops like this:
try this:
1: go to download mode, and press Power + home + volume —
2: As soon as the screen turns black, continue pressing Power and home, quickly release "volume —" and press "volume +". This will get you into recovery mode.
It always worked for me, so I wish the same for you. Good luck! (And sorry for my bad english)

vinicius_guerra said:
Hi! I usually run out of my bootloops like this:
try this:
1: go to download mode, and press Power + home + volume —
2: As soon as the screen turns black, continue pressing Power and home, quickly release "volume —" and press "volume +". This will get you into recovery mode.
It always worked for me, so I wish the same for you. Good luck! (And sorry for my bad english)
Click to expand...
Click to collapse
Hi Vinicius,
Thanks for the suggestion. Unfortunately it didn't work, I even tried flashing it back to a standard ROM from TWRP, but it still didn't do anything, just back to the Samsung logo and the loop continues ever more!

Hi, I have this problem as well.
Originally I had TWRP and root flashed into my phone but for reasons I needed to remove root.
So I followed the Odin route stated here "Mobikin how to remove root from android" (I can't post links but this should be the top result when googling)
However I didn't know if the recovery/boot should have went into AP or BL on the Odin menu and googling didn't give me any answers so I may have tried both....
Right now I tried flashing TWRP and I can't seem to boot into TWRP as well.
I was able to get into recovery mode but clearing data/cache didn't fix it for me.
EDIT: I managed to flash in another stock rom and it boots into the SAMSUNG logo but gets stuck there. I already went into recovery mode to delete data and cache partition but it still doesn't boot.

Melioetta Zyguard said:
Hi, I have this problem as well.
Originally I had TWRP and root flashed into my phone but for reasons I needed to remove root.
So I followed the Odin route stated here "Mobikin how to remove root from android" (I can't post links but this should be the top result when googling)
However I didn't know if the recovery/boot should have went into AP or BL on the Odin menu and googling didn't give me any answers so I may have tried both....
Right now I tried flashing TWRP and I can't seem to boot into TWRP as well.
I was able to get into recovery mode but clearing data/cache didn't fix it for me.
EDIT: I managed to flash in another stock rom and it boots into the SAMSUNG logo but gets stuck there. I already went into recovery mode to delete data and cache partition but it still doesn't boot.
Click to expand...
Click to collapse
Same experience. For all those 6 years that I used this device, the wifi was okay until now. It (wifi) is very buggy (turning on and off, and sometimes won't turn on at all) so I restarted the device, then bootloop happens. I flashed the stock rom via odin and clear data and cache. But it is still bootlooping. I think this is the sign that I need to replace my phone IF I couldn't find a fix to this.