Related
Sometimes my I5500 won't turn on.
This has already happened 2 times (with two different firmwares I5500XWJPL and I5503TTLPJP9). The phone shows absolutely no signs of life - screen is black, no sounds, nothing.
I tried everything: pressing VolumeDown+Center+Power, VolumeDown+Home+Power, with or without battery/SIM/charger/SD. Tried removing battery for 30 minutes, charging battery in external charger.
Sometimes when charger is connected, it shows green battery on the screen, but still won't boot.
Last times I spent several hours fiddling with it until it finally turned on..
Can someone tell my if there is a fast way to revive the phone next time this happens?
Maybe your arm11boot is damaged, but still partly working. You need replace that partition. I saw arm11boot partition image in one Russian FW. I can't remember actual name. You can try that, but caution. You might brick your phone compleatly!
sorry for reviving this thread.
but I got the same problem now. Tried to use ROM Manager to install CWM Recovery (following a blogpost explaining how to install a Custom ROM on the SG5). Might have accidentally clicked a different CWM Rec. version than I thought I did. However, ROM manager showed a message, telling me that CWMR was installed correctly.
So I wanted to boot into CWMR up to flash my device with the latest CyanogenMod 7 port from MADTeam. Used the "boot into recovery" option from ROM manager for that purpose. The next thing I know is my phone not reacting to anything.
Tried all methods mentioned afore (Vol- + Home + Power / Vol- + Center + Power, with/w.o. SD card and/or battery inserted). Screen keeps being off, no sign of life, phone wont even do anything when plugged to my PC or a charger.
The phone has been rooted properly before and was running Stock 2.1. Houston, we've got a problem.
Rigardi said:
sorry for reviving this thread.
but I got the same problem now. Tried to use ROM Manager to install CWM Recovery (following a blogpost explaining how to install a Custom ROM on the SG5). Might have accidentally clicked a different CWM Rec. version than I thought I did. However, ROM manager showed a message, telling me that CWMR was installed correctly.
So I wanted to boot into CWMR up to flash my device with the latest CyanogenMod 7 port from MADTeam. Used the "boot into recovery" option from ROM manager for that purpose. The next thing I know is my phone not reacting to anything.
Tried all methods mentioned afore (Vol- + Home + Power / Vol- + Center + Power, with/w.o. SD card and/or battery inserted). Screen keeps being off, no sign of life, phone wont even do anything when plugged to my PC or a charger.
The phone has been rooted properly before and was running Stock 2.1. Houston, we've got a problem.
Click to expand...
Click to collapse
Take your battery out, put it back in and turn your phone on, then it will boot up into recovery mode. I also have this problem from time to time, sometimes it boots into recovery, sometimes not and i have to remove/replace the battery.
I actually thought that this might be a useful feature for say - if you wanted to upgrade a friends phone to cyanogenmod in the pub, for example.
did try that. now even had the battery removed for about an hour. put it back in. still no reaction on pressing the power button or one of the combinations that should put it into recovery or download mode. no sign of life when plugging the phone to my computer or the charger.
I do fear the worst, though I dont know how ROM manager was actually able to brick the phone that badly.
Rigardi said:
did try that. now even had the battery removed for about an hour. put it back in. still no reaction on pressing the power button or one of the combinations that should put it into recovery or download mode. no sign of life when plugging the phone to my computer or the charger.
I do fear the worst, though I dont know how ROM manager was actually able to brick the phone that badly.
Click to expand...
Click to collapse
In that case then this also happened to me - While exploring the rom manager application after first ever flashing my phone i accidentally selected the wrong phone model from the 'flash clockworkmod recovery' option and my phone was gone forever. Perhaps your problem is similar.
(Luckily it was under warranty and they replaced it. The method worked so well in fact it happened 'accidentally' a second time i acquired a 3rd i5500 out of the box )
bought mine already used, so no chance for a warranty replacement :/
gonna give it a shot with a usb jig now, maybe i can get the thing into d/l mode with that, so I can revive it with odin.
Rigardi said:
bought mine already used, so no chance for a warranty replacement :/
gonna give it a shot with a usb jig now, maybe i can get the thing into d/l mode with that, so I can revive it with odin.
Click to expand...
Click to collapse
what about the Emergency DLoad Mode, which is not the Download Mode? Did you try it?
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
how do I access emergency d/l mode?
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Rigardi said:
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Click to expand...
Click to collapse
ops, sorry: I miss your previous message!!
Now I got it and read this last post.. let some time to think about it, I'll replay soon.. but, generally speaking, at this point there's not so much you can do..
If you can get it into Download or Recovery mode, then you should be fine.
Sent from my GT-I5500 using XDA App
Rigardi said:
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Click to expand...
Click to collapse
download mode is Vol - / Central Button / Power..
Im aware of that. However, Vol- + Menu + Power is the only key combination that the phone will react upon.
Anyway. Brought it to a mobile phone shop on friday, called them on monday and according to them, the phone should be fixed by tomorrow, wednesday. Seems like ROM manager has done damage that cant be undone without knowing how to handle a JTAG device. But at least its not completely broken. Learning that will cost me 25 Euros, though.
One final update to this: Got the phone back today, they were indeed able to fix it.
Conclusion:
While installing a non-fitting CWM-Recovery through ROM Manager will make your Galaxy 5 unfixable via Odin, it still can be saved by making proper use of a JTAG.
Rigardi said:
One final update to this: Got the phone back today, they were indeed able to fix it.
Conclusion:
While installing a non-fitting CWM-Recovery through ROM Manager will make your Galaxy 5 unfixable via Odin, it still can be saved by making proper use of a JTAG.
Click to expand...
Click to collapse
... for only 25 €!!!
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
Hello.
I recently got a galaxy s2 that had been water damaged and wouldn't start.
I disassembled the phone and cleaned it thoroughly with isopropyl.
After putting the phone back together, everything works perfectly, except for the front camera and... whenever the phone goes into standby/ sleep mode for more than 5 seconds, the phone will not come back on and I have to replace the battery in order to turn the phone back on. This happens every time the phone goes to sleep mode for more than 5 seconds. If I turn the screen back on before 5 seconds have passed, the screen comes right back on.
However, if I have the charger attached to the phone, nothing wrong happens and the phone works perfectly (except for the front camera).
I would
A factory reset the phone .
B flash firmware to rule in a hardware problem .
jje
Thanks for the reply.
I have tried resetting the phone but that didn't solve it.
I also tried to update the firmware, but I'm not able to, because when the phone restarts during the flashing proccess, the phone just stays off and won't power back on. I then have to re-insert the battery to power up the phone again, but then the flashing proccess is interrupted.
By the way. I don't have any experience with rooting android phones and don't know of another way to flash the phone, other than throught the "KIES" software or through the update function on the phone itself.
I'm not sure if the phone is rooted or has a custom firmware, but when I press vol up + home button when powering on the phone, I am presented with a menu that says ODIN, so not sure if that means the phone is rooted or not.
I'm not sure if the phone is rooted or has a custom firmware, but when I press vol up + home button when powering on the phone, I am presented with a menu that says ODIN, so not sure if that means the phone is rooted or not.
Odd that and i would guess it is custom firmware .
Recovery factory reset is
Vol Up + Power + Home Button held down and released at splash screen
Download mode is Vol Down + Power + Home Button
Can you get to either of the above .
jje
Oleq83 said:
Thanks for the reply.
I have tried resetting the phone but that didn't solve it.
I also tried to update the firmware, but I'm not able to, because when the phone restarts during the flashing proccess, the phone just stays off and won't power back on. I then have to re-insert the battery to power up the phone again, but then the flashing proccess is interrupted.
By the way. I don't have any experience with rooting android phones and don't know of another way to flash the phone, other than throught the "KIES" software or through the update function on the phone itself.
I'm not sure if the phone is rooted or has a custom firmware, but when I press vol up + home button when powering on the phone, I am presented with a menu that says ODIN, so not sure if that means the phone is rooted or not.
Click to expand...
Click to collapse
You have a lot of information you need.
Odin is the utility used to flash firmwares/kernels/modems/etc to your phone. If that screen that says "Odin" says custom binary: no (or something similar) then it is LIKELY that it is not rooted, but you can root and reset this display with a few different techniques.
I've found Kies unreliable at best when attempting to update firmware, and have only used Odin. (since Kies never fully updated my firmware even once)
Read FAQs and stickies here.
Ok. Thanks for the help to both of you.
Tried to flash a stock firmware with the odin software, but after the phone powers off during the flashing proccess, it wont power back on.
So I have to re-insert the battery again, which interupts the flashing proccess.
So the water has propably done too much damage to the phone then and it's propably not a software fault.
I've ordered a new battery in case that is the cultprit, but if it's not, then I'll propably just sell the phone for spares.
At least the screen is in pretty good condition
Oleq83 said:
Ok. Thanks for the help to both of you.
Tried to flash a stock firmware with the odin software, but after the phone powers off during the flashing proccess, it wont power back on.
So I have to re-insert the battery again, which interupts the flashing proccess.
So the water has propably done too much damage to the phone then and it's propably not a software fault.
I've ordered a new battery in case that is the cultprit, but if it's not, then I'll propably just sell the phone for spares.
At least the screen is in pretty good condition
Click to expand...
Click to collapse
Don't forget to press thanks the guys who helped you
My galaxy s3 has been stuck in safe mode for two days now which is frustrating as only the stock apps can be used. I have tried different solutions, which I list below.
How it happened.
I was initially on 4.1.1 and when I woke up I saw a notification to upgrade to 4.1.2, after that it did its thing and rebooted into safe mode.
solutions tried
1. Reboot - didnt work
2. take out battery for few minutes and reboot - didnt work
3. boot into stock recovery to try to factory reset phone, Volume button not working so cant select other option apart from reboot. - didnt work
4. Download stock rom from samfirmware and flash using odin - didnt work
5. Flash CWM using odin, didnt factory reset and flashed custom rom (omega). It boots into safe mode as well
6. Downloaded stock ics firmware, flashed using odin . it boots but stuck on samsung logo.
I dont know what else to do. Although am thinking downgrade the bootloader to one meant for ICS the try to flash to ICS stock rom again, would try this later in the day.
p.s Ignore more signature I own a galaxy s3 as well.
Switch off your phone..
Press the power button..
Once you see the logo screen press and hold the left capacitive button..
Sent from my GT-I9300 using Tapatalk 2
zoot1 said:
Switch off your phone..
Press the power button..
Once you see the logo screen press and hold the left capacitive button..
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I already did that....still stuck in safe boot.
alphaola said:
I already did that....still stuck in safe boot.
Click to expand...
Click to collapse
I think its:
Switch off your phone..
Press the back or cancel(left) button..
Once you see the logo screen press and hold the left capacitive button..
Hey,
I'm having the exact same issue with my note 2. Wondering if you found a solution.
Anybody can help with this? I am having the same issue
use search, asked and answered too many times
I did search..
I tried everything.
full wipe, cache, dalvik, factory reset and it keeps saying safe mode.
so please help
EDIT:
i just installed slim rom, and it keeps saying safe mode...
s3 safe mode
one way work for me..
1-turn off the phone
2- remove battery
3- short + and - in battery connector for few minute
4-insert battery and turn it on
alphaola said:
My galaxy s3 has been stuck in safe mode for two days now which is frustrating as only the stock apps can be used. I have tried different solutions, which I list below.
How it happened.
I was initially on 4.1.1 and when I woke up I saw a notification to upgrade to 4.1.2, after that it did its thing and rebooted into safe mode.
solutions tried
1. Reboot - didnt work
2. take out battery for few minutes and reboot - didnt work
3. boot into stock recovery to try to factory reset phone, Volume button not working so cant select other option apart from reboot. - didnt work
4. Download stock rom from samfirmware and flash using odin - didnt work
5. Flash CWM using odin, didnt factory reset and flashed custom rom (omega). It boots into safe mode as well
6. Downloaded stock ics firmware, flashed using odin . it boots but stuck on samsung logo.
I dont know what else to do. Although am thinking downgrade the bootloader to one meant for ICS the try to flash to ICS stock rom again, would try this later in the day.
p.s Ignore more signature I own a galaxy s3 as well.
Click to expand...
Click to collapse
It's Volume button work fine??
The problem has nothing to do with reboot. As you can see have already mentioned reboot as part of the solutions I tried.
My device is fine with ICS firmwares but has issues with Jellybean (stock and modded rom including CM10.1). Currently am running ICS on it as thats the only way the phone works properly.
I installed 4.0.4 (XAALF2) via Odin, but it got stuck on samsung logo. Then turned it off and flashed CWM to do factory reset as the volume key doesnt work on stock recovery. After that everything worked fine. I was able to update to the latest 4.0.4 via OTA.
The problem is hardware, so you might want to contact Samsung.
I found some information about "Safe Mode".
It seems that every Android phone has a safemode.
"On Samsung’s devices, almost all users will be able to access Safe Mode with by pressing and holding the menu button during start up. If it’s a capacitive menu key, make sure to release and press again each time the LED under the key comes back on. You don’t want to miss the catch for Safe Mode because the button released itself."
Here is the link where i get the information: http://www.tested.com/tech/android/...ds-safe-mode-to-save-a-phone-from-boot-loops/
You can try it this way, maybe it will work.
Good luck.
Ic3y83 said:
I found some information about "Safe Mode".
It seems that every Android phone has a safemode.
"On Samsung’s devices, almost all users will be able to access Safe Mode with by pressing and holding the menu button during start up. If it’s a capacitive menu key, make sure to release and press again each time the LED under the key comes back on. You don’t want to miss the catch for Safe Mode because the button released itself."
Here is the link where i get the information: http://www.tested.com/tech/android/...ds-safe-mode-to-save-a-phone-from-boot-loops/
You can try it this way, maybe it will work.
Good luck.
Click to expand...
Click to collapse
I think u missing the point, the phone works fine with 4.0.4 firrmwares, it only get stuck in safe mode when updated to Jellybean 4.1.1 and above. No amount of key combination, factory reset or even custom rom was able to fix the safe boot.
The best option is to send it back to samsung, its definitely hardware issue.
alphaola said:
I think u missing the point, the phone works fine with 4.0.4 firrmwares, it only get stuck in safe mode when updated to Jellybean 4.1.1 and above. No amount of key combination, factory reset or even custom rom was able to fix the safe boot.
The best option is to send it back to samsung, its definitely hardware issue.
Click to expand...
Click to collapse
I'am sorry for misunderstanding u. I think you could be right. Maybe it is a hardware issue.
Don't forget to "unroot" and reset the "flash counters".
Greetz.
alphaola said:
My galaxy s3 has been stuck in safe mode for two days now which is frustrating as only the stock apps can be used. I have tried different solutions, which I list below.
How it happened.
I was initially on 4.1.1 and when I woke up I saw a notification to upgrade to 4.1.2, after that it did its thing and rebooted into safe mode.
solutions tried
1. Reboot - didnt work
2. take out battery for few minutes and reboot - didnt work
3. boot into stock recovery to try to factory reset phone, Volume button not working so cant select other option apart from reboot. - didnt work
4. Download stock rom from samfirmware and flash using odin - didnt work
5. Flash CWM using odin, didnt factory reset and flashed custom rom (omega). It boots into safe mode as well
6. Downloaded stock ics firmware, flashed using odin . it boots but stuck on samsung logo.
I dont know what else to do. Although am thinking downgrade the bootloader to one meant for ICS the try to flash to ICS stock rom again, would try this later in the day.
p.s Ignore more signature I own a galaxy s3 as well.
Click to expand...
Click to collapse
i did a reboot and it removed the safe mode :good:
My personal experience, i overclocked my SGS3 with Boeffla kernel on ARHD then i got freeze screen and phone reebot into safe mode, I entered into recovery and reebot then everithing was fine again.
Safe mode occurs when something in the phone is not working properly , could be hardware or software, however, stuck on it is not a good signal.
my advice is to send the device to service.
Do not forget to reset flash counter via Triangle Away and flash stock factory firmware.
Good Luck! :good:
note 3 stuck in save mode window
This problem occurs after changing to a new simcard not already installed before in the device.
1. Power off the galaxy note 3.
2. Remove the micro simcard from the slot by sliding.
3. Power on the device without the simcard.
4. It will run in a normal mode, if so, this will actually diagnosed that there is a simcard defined by the administrator as default. In the security setting in setting menu and for protection against theft, the original simcard must be insert to unlock this choice of detection of any change in new simcard. New simcard is defined as strange and theft suspected.
I hope this make you reach some solution for your trouble.
S3 SAFE MODE issue
Plz help....
On my s3 i9300, its always on safe mode. Tried FACTORY DATA RESET. Still on safe mode. Other issue is that on power on and off, back LED turns on for few seconds. Also volume down not working. These issues started after s3 went on safe mode. Any sloution??
shoeb_v said:
Plz help....
On my s3 i9300, its always on safe mode. Tried FACTORY DATA RESET. Still on safe mode. Other issue is that on power on and off, back LED turns on for few seconds. Also volume down not working. These issues started after s3 went on safe mode. Any sloution??
Click to expand...
Click to collapse
Same issue here, it is hardware
I went through a lot of threads and not one had a solution. So I will post here what worked for me.
Customer came to my store with Galaxy S3 (SPH-L710T) that was stuck in safe mode. I tried everything on this thread, nothing worked. Luckily I had a older Galaxy S3 (SPH-L710) with a broken screen, so I switched over the motherboard from the customer's phone to the old one - I did connect the customer's original LCD to the motherboard since my old phone had its LCD broken. Powered it on, no safe mode.
So at this point I just transferred the volume buttons flex cable to the customer's phone. Powered it on, no safe mode again.
Hope it helps someone!
How the problem occurred
So a year or two ago I bought a Jiayu G4A/T/Whatever they're calling it and safely got it here. I've used the stock ROM for a bit but I wanted to get rid of the bloatware that was still on it, so I eventually ended up with a properly rooted phone with a ROM from Jiayu.es (Everything worked, have ClockworkMod as recovery, accessible via Mobileuncle Tools), which was essentially a stock Kitkat rom made to work for the phone. Now I got sick of the ROM and recently saw the new EMUI version on Huawei's P8 Lite, so I figured I'd look around for a tailored ROM running that, and ended up at "jiayu-emui-3-0-stable" from Needrom.
What I did
1. I downloaded a ROM from Needrom with identifier "jiayu-emui-3-0-stable" (I can't post external links)
2. Backed up my important files following a guide from androidcentral titled "[Guide] How to Backup and Restore Apps and Data when installing new ROMs" that I can't link,and did a full backup using CWM
3. Placed the ZIP on my internal SD card, went into recovery, wiped data/cache (not dalvik, since it wasn't described in the instructions, I think this might be a probable cause) and installed the new ROM from ZIP
4. Rebooted the phone and now it's stuck in the boot loop I mentioned.
What the problem is
Bootloops aren't that much of a problem usually, except this one is... I can't get into recovery mode. From there on it'd be cake, since I made the right preparations, but I can't get into it. While connected to my PC it keeps powering on, showing a splash screen from Jiayu.es briefly (which shouldn't be present anymore) and powering off after 10 seconds, only to come back to the splash screen.
What I've tried
I've unplugged it, removed the battery, waited to get a full power cycle and tried to hold my buttons in these combinations: [power button + volume up], [power button + volume down] - but neither work. It just keeps going with the boot loop. I can succesfully power it down, and when I plug it in from there it shows the low battery image. At the moment of seeing that I thought I could connect to it using ADB / Fastboot, but no luck there either. It keeps saying no devices found, and with fastboot it keeps on <waiting for device>.
My questions
What exactly can I do if there is no way for me to get into recovery mode? Are there any alternatives? How can I get my device to be recognized by ADB? Is that even possible? Why is this bootloop any different from others?
Update from the massive Q&A thread:
ZipAddict said:
Is it booting up on its own too after being off? This happened to wifes phone and it turned out the power button was stuck. I took a pencil and hit the power button with the eraser a few times and it worked then. Her case mustve dislogded it. I will keep my fingers crossed for u. If not send me a private message and i will look for an answer tomorrow and get back with u
Click to expand...
Click to collapse
Thank you for the reply!
Yes, it does. I took the battery out and let it lay disassembled for a night, after which I cleaned it a little and re-inserted the battery. With the case back on, nothing happened, so the power button wasn't stuck for sure. When I powered it back on with the power button (no USB attached) it showed the emblem for ~8 seconds and powered off. It then buzzes to show it's powered on again and up comes the splash screen again. Could it be that the ROM was just a rebooting falsehood? Why would it disallow me getting into recovery mode? I really hope there is something that can still force the device into recovery mode / interact with it somehow while in this state.
Oh, I also tried to see if the volume down button was broken but all the contacts seem intact, plus, they worked an hour before I started switching roms.
Hello,
New to the forum and all of this, so please go easy on me.
I have a Samsung Galaxy S9+ (SM-G960F).
On Thursday evening, I went to the device and it was completely dead. It wouldn't turn on and I attempted to do power key/volume down and various other button combinations I found online that would normally boot the device. Obviously, I attempted to charge the phone, but the charging light did not come on yet the phone did warm up slightly as if it was charging. After leaving it plugged in for so long, a 'Downloading... Do Not Turn Target Off' screen appeared. It also states I can restart the phone by holding volume down/power button for seven seconds. However, when I do this the phone just goes dead and doesn't boot up. After plugging in the charger again trying various buttons, I eventually end up back at the same download screen.
I've read about recovery mode, safe mode etc but I am unable to access them using the instructions I've read.
Any help would be appreciated. Ideally I'd like to be able to access my photos/videos/messages on the device and be able to use it again.
Jamfocus said:
Hello,
New to the forum and all of this, so please go easy on me.
I have a Samsung Galaxy S9+ (SM-G960F).
On Thursday evening, I went to the device and it was completely dead. It wouldn't turn on and I attempted to do power key/volume down and various other button combinations I found online that would normally boot the device. Obviously, I attempted to charge the phone, but the charging light did not come on yet the phone did warm up slightly as if it was charging. After leaving it plugged in for so long, a 'Downloading... Do Not Turn Target Off' screen appeared. It also states I can restart the phone by holding volume down/power button for seven seconds. However, when I do this the phone just goes dead and doesn't boot up. After plugging in the charger again trying various buttons, I eventually end up back at the same download screen.
I've read about recovery mode, safe mode etc but I am unable to access them using the instructions I've read.
Any help would be appreciated. Ideally I'd like to be able to access my photos/videos/messages on the device and be able to use it again.
Click to expand...
Click to collapse
-Download odin
-Download firmware for your phone
-unrar firmware file
-open odin
-flash AP , BL , CP , HOME_CSC (HOME_CSC goes on USERDATA) if you haven t formated your phone by mistake your files will be there and your phone working.