Can't boot into CWM - Galaxy S 4 Q&A, Help & Troubleshooting

Hello there,
I'm using a vodafone bloated version of the i9505 and wanted to flash CM or a clean stock 4.3 because I don't want to wait for vodafone to release updates.
I downloaded Odin and CWM for my device and followed the instructions correctly. All went as it should. But when I tried to boot into recovery, I got the boot logo and in the upper left corner it said in small blue text "booting recovery..." but it would just give me a black screen after a while and restart into normal mode. I tried flashing different versions of CWM via Odin. My next approach was to root the phone with cf auto root which succeeded. After that, I tried all of the above again, and still didnt get any results. I even tried the Cyanogenmod desktop intsaller and after a while it said: "cant communicate with your phone"
Please help!

I believe I had the same issue once. When you flash the recovery true Odin, make sure Auto Reboot is not selected in Odin. That fixed it for me. After the flashing is done, you need to remove the battery and insert it again. Then it should probably work.

Lennyz1988 said:
I believe I had the same issue once. When you flash the recovery true Odin, make sure Auto Reboot is not selected in Odin. That fixed it for me. After the flashing is done, you need to remove the battery and insert it again. Then it should probably work.
Click to expand...
Click to collapse
I tried what you suggested, and hat the same thing as before but after the second restart I kept holding the volume up key as someone suggested on the internet and got a CM boot screen with on screen buttons like in CWM. after a brief pause I got a violet screen with nothing on it. I am now very confused and have no idea how to fix this. The phone itself can be booted normally though.
It seems to be that something remained from the failed CM installation.
Any suggestions?

What version of Odin do you use? Try version 1.85.

TWRP
Lennyz1988 said:
What version of Odin do you use? Try version 1.85.
Click to expand...
Click to collapse
Hello again, I flashed TWRP and it worked! I had to hold the volume up button even after the logo with the small blue print showed up in order to boot into recovery. Still couldnt get it to boot into CWM though. But thank God there is no need for that anymore!

Related

[Q] Bricked i9505, cannot boot into recovery [read all the threads]]

Hi guys, I realize that there are several threads about this issue, but trust me, I have read them all over and over for 2 days, and nothing seems to work.
The story:
I bought a new i9505 a few days ago, and straight away wanted to root it and flash a GPE rom (becouse touchwiz makes me vomit in my mouth, so to speek). I rooted with FC-auto root, flashed a custom recovery (TWRP) and using that, flashed the GPE rom. What I did wrong, I think (tried so many things now so it's hard to remember) was not doing all the wipes before flashing the rom. It didn't boot, so I thought I would flash a stock rom with Odin. So I just flashed it (again, without any wiping), and then... darkness!
The current situation:
Right now, I cannot boot into recovery, despite numerous recovery flashes with Odin. When I try to boot into recovery (Vol up + home + power) the phone showns the galaxy logo and a small blue text in the upper left corning sating "Recovery booting..." and then just hangs. Sometimes the phone reboots.
What I have tried:
Everything, it feels like! Thankfully, the phone can enter Download Mode without any issues, so I can flash with Odin with no problems (so it seems, anyway). As my priority is to be able to boot into recovery mode, I have tried flashing them all (TWRP, CWM, phils recovery), but whenever I try to recovery boot, the phone freezes or reboots. I have tried different versions of odin (1.85, 3.07 and 3.09) and even different usb cables (but am mostly using the white original one). Odin always says that the flashing was successfull (no error messages).
I've also made sure that there are now Kies processes running in the background.
I have tried flashing the stock rom together with a pit-file. Again, the flashing seems to go just fine, but the phone wont boot afterwards (hangs at the galaxy logo). The recovery wont start (hangs as the galaxy logo, but with the blue text saying "booting recovery).
I've tried fallowing all the different tips about how to use the buttons to enter recovery; hold them all untill the recovery starts, or release the all just when the tiny blue text appears, and even release the power button but keep holding down vol-up+home, but there is no difference. I think that as long as the blue text comes up, the phone is actually trying to boot into recovery, so I don't think my fingers being too slow or too fast is the issue.
I've tried flashing things in all kinds of orders, for example;
flash pit file alone, check only f.reset and re-partition. when it says pass, remove battery, reinsert it, boot in odin mode again, flash firmware alone as pda, check only f.reset and auto-reboot.
Click to expand...
Click to collapse
flash a stock ROM via Odin 3.07 but don't reboot, then manually power-off and reboot back into download mode and flash the CF-Auto-Root by Chainfire and then let it restart on it's own.
Click to expand...
Click to collapse
No difference. The recovery just wont boot.
So I'm pretty desperate. I have a 5000 Swedish crowns (you know what it costs in your country) paper weight right now
Is it time to give up, or is there anything more I can try?
/Daniel
which rom GPE you have flashed? in the description was reported as compatible with gt-i9505 or S4 intl?
This one:
http://forum.xda-developers.com/showthread.php?t=2348272
But the rom is not my primary concern right now, I need to get recovery (any recovery) working.
Try this: pull battery for a couple of minutes, flash stock MGA with Odin, NO PIT FILE. After flashing let the phone sit for some time (sometimes up to 10 minutes). If after 10 minutes the phone doesn't start, press and hold ONLY the power button until the phone reboots and let it try to boot on its own.
robogo1982 said:
Try this: pull battery for a couple of minutes, flash stock MGA with Odin, NO PIT FILE. After flashing let the phone sit for some time (sometimes up to 10 minutes). If after 10 minutes the phone doesn't start, press and hold ONLY the power button until the phone reboots and let it try to boot on its own.
Click to expand...
Click to collapse
So you mean I should uncheck "auto reboot" in Odin, flash the stock rom, and after the flashing is done, unplug the phone and pull out the battery, then after 10 minutes, put in the battery and turn it on like normal?
Why would it help leaving it off for 10 minutes? (Not meaning to sound sarcastic, it's a genuine question.) I have never waiting between flashing and rebooting (as most of the time, Odin auto-reboots the phone after flash).
But shouldn't I forget about roms for now, and just focus on trying to get a recovery working? As I understand it, the rom and the recovery are actually completely independent from each other, right? So shouldn't I try to somehow flash for example CWM somehow (in a way that I haven't tried already, I guess)?
robogo1982 said:
Try this: pull battery for a couple of minutes, flash stock MGA with Odin, NO PIT FILE. After flashing let the phone sit for some time (sometimes up to 10 minutes). If after 10 minutes the phone doesn't start, press and hold ONLY the power button until the phone reboots and let it try to boot on its own.
Click to expand...
Click to collapse
I think missunderstood you before, this is what I did now:
The phone was unplugged and without the battery since yesterday. I put in the battery and booted it into download mode. Flashed a stock rom (I9505XXUBMF8_I9505VDSBMF1_VDS) and after Odin said "PASS!" and rebooted, I let it hang at the samsung logo for about 10 minutes, no effect. Rebooted manually using just the power button and let it hang for a few minutes more, nothing
s.c.s.i. said:
I think missunderstood you before, this is what I did now:
The phone was unplugged and without the battery since yesterday. I put in the battery and booted it into download mode. Flashed a stock rom (I9505XXUBMF8_I9505VDSBMF1_VDS) and after Odin said "PASS!" and rebooted, I let it hang at the samsung logo for about 10 minutes, no effect. Rebooted manually using just the power button and let it hang for a few minutes more, nothing
Click to expand...
Click to collapse
i have the international galaxy s4 GT I9505 with stock firmware MF8 when purchased and same happened when i flashed android 4.3 by jamal. what i did was just flashed again the rom 3 times then it booted normally. prior to that, i have rooted my phone and installed the philz touch recovery.
ayongkot said:
i have the international galaxy s4 GT I9505 with stock firmware MF8 when purchased and same happened when i flashed android 4.3 by jamal. what i did was just flashed again the rom 3 times then it booted normally. prior to that, i have rooted my phone and installed the philz touch recovery.
Click to expand...
Click to collapse
I don't know how many times I've flashed it by now, but it simply wont boot
How exactly did you flash it?
I'll try flashing with another computer tonight, that's the only thing I have left to try.
s.c.s.i. said:
I don't know how many times I've flashed it by now, but it simply wont boot
How exactly did you flash it?
I'll try flashing with another computer tonight, that's the only thing I have left to try.
Click to expand...
Click to collapse
before installing android 4.3, i flashed advance philz touch recovery then flashed 4.3, i already have flashed 2 android 4.3 both by jamal and omega but after 2-3 days of used, the phone just shut down and won't boot. it just keeps on booting up to samsung galaxy s 4 then shuts down so i had to flash back world premiere odex xxubgma pre rooted. i'll stick to this because omega v9 gives me a lot of fc's.
---------- Post added at 08:03 PM ---------- Previous post was at 07:54 PM ----------
[QUOTE I have tried flashing the stock rom together with a pit-file. Again, the flashing seems to go just fine, but the phone wont boot afterwards (hangs at the galaxy logo). The recovery wont start (hangs as the galaxy logo, but with the blue text saying "booting recovery).
/Daniel[/QUOTE]
have you tried flashing the stock recovery?
ayongkot said:
have you tried flashing the stock recovery?
Click to expand...
Click to collapse
I thought the only way to flash the stock recovery was by flashing a stock rom! Is it availible somewhere for download?
I really cant do anything at all without being able to boot into recovery.
s.c.s.i. said:
I thought the only way to flash the stock recovery was by flashing a stock rom! Is it availible somewhere for download?
I really cant do anything at all without being able to boot into recovery.
Click to expand...
Click to collapse
I had trouble getting into recovery when I first had my S4.
Try holding power+volume up+home and as soon as you see the blue writing let go of the power button but keep volume up and home pressed. That's how I always boot into recovery now.
You can also try without home button. So just hold volume up+power, that's worked for some people.
Again if this doesn't work try releasing power butto as soon as blue writing appears so your only holding power up.
And if all this fails try flashing the latest .tar.md5 version of Philz recovery in PDA section of Odin and try again
Obagleyfreer said:
I had trouble getting into recovery when I first had my S4.
Try holding power+volume up+home and as soon as you see the blue writing let go of the power button but keep volume up and home pressed. That's how I always boot into recovery now.
You can also try without home button. So just hold volume up+power, that's worked for some people.
Again if this doesn't work try releasing power butto as soon as blue writing appears so your only holding power up.
And if all this fails try flashing the latest .tar.md5 version of Philz recovery in PDA section of Odin and try again
Click to expand...
Click to collapse
Thanks Obagleyfreer, I tried all the different button combinations, including the ones you mentioned, but the phone behaves the same, shows the blue text, and after a few secons, reboots. I't actually started booting Phils recovery once or twice, I could see the CWM logo, but it hubg there for a while, and then rebooted.
Yesterday, I even tried flashing from another computer, just to be sure, but no difference. If no other tips turn up today, I'll send to a service center.
Flash Factory Firmware to clean-up bad sector on your device.then re-flash with the stock rom that you have.
cz4r3n said:
Flash Factory Firmware to clean-up bad sector on your device.then re-flash with the stock rom that you have.
Click to expand...
Click to collapse
thanks so much, will give it a go!
So I should flash the factory firmware, then reboot the phone into download mode again, and flash the stock rom?
Edit: Do I even need to flash the stock rom afterwards? The file you linked to is 1599.2 MB, so I assume it contains a stock rom aswell.
My plan is to flash CM10.2 if I manage to get the phone working, so it doesn't matter if the stock rom that is provided is good or not.
after flashing the factory firmware it should boot normally, because it is a factory firmware, you need to re-flash your stock rom.
EDIT:the main point now is to unbrick your device, so try to fix the issue first, after you can do whatever you want to flash, either a custom or a stock rom.
cz4r3n said:
after flashing the factory firmware it should boot normally, because it is a factory firmware, you need to re-flash your stock rom.
Click to expand...
Click to collapse
Thank you! This gave me some badly needed hope! Will try as soon as I get home from work today!
cz4r3n said:
after flashing the factory firmware it should boot normally, because it is a factory firmware, you need to re-flash your stock rom.
EDIT:the main point now is to unbrick your device, so try to fix the issue first, after you can do whatever you want to flash, either a custom or a stock rom.
Click to expand...
Click to collapse
i've flashed original fw in particular the mh8 because is the lastest that includes knox, but i can't turn on the phone if it isn't charging
and while i'm using without the charger, it turn off randomly... please help me, what i've to do?
had exact same problem with this guy, but on 4.4.2 firmware
http://forum.xda-developers.com/galaxy-s4/help/help-stuck-samsung-galaxy-s4-gt-i9505-t3030575
Note: my i9505 also came from Sweden ( im from PH )

How to WIPE without CWM / NO recovery / only download

Hey guys.
I have been doing a lot of researches before creating this new thread.
Here is my problem with a Samsung Galaxy s3 I9300T (Australia - Vodafone build). I was given the phone, since it was stuck in a boot loop after a software update issue with Kies (I think from memory 4.2 or something).
The phone boots up, displays the Vodafone logo, and is stuck on the Samsung logo. The phone doesn't restart but stays idle there.
It is impossible to reach the download mode with the use of the 3 buttons, but a USB JIB I bought on ebay does the trick.
Odin recognizes the phone, I can flash a stock Kernel from Samsmobile or root/install the CWM.
BUT, there is no way (so far?) to reach the recovery mode.
I tried to flash a new boot loader, tried to check any physical issue with the buttons, but nothing seems wrong.
I have been looking for tools such a android toolbox/toolkit etc, in the hope one would be able to wipe/flash the nand or even unbrick or whatsoever, from a download mode and not ADB, since I there no fast boot available.
I am ready to try anything, since there's nothing to loose here.
I'm running windows 7 from Parallel desktop.
Thanks mates.
Anthony
tonythrash69 said:
Hey guys.
I have been doing a lot of researches before creating this new thread.
Here is my problem with a Samsung Galaxy s3 I9300T (Australia - Vodafone build). I was given the phone, since it was stuck in a boot loop after a software update issue with Kies (I think from memory 4.2 or something).
The phone boots up, displays the Vodafone logo, and is stuck on the Samsung logo. The phone doesn't restart but stays idle there.
It is impossible to reach the download mode with the use of the 3 buttons, but a USB JIB I bought on ebay does the trick.
Odin recognizes the phone, I can flash a stock Kernel from Samsmobile or root/install the CWM.
BUT, there is no way (so far?) to reach the recovery mode.
I tried to flash a new boot loader, tried to check any physical issue with the buttons, but nothing seems wrong.
I have been looking for tools such a android toolbox/toolkit etc, in the hope one would be able to wipe/flash the nand or even unbrick or whatsoever, from a download mode and not ADB, since I there no fast boot available.
I am ready to try anything, since there's nothing to loose here.
I'm running windows 7 from Parallel desktop.
Thanks mates.
Anthony
Click to expand...
Click to collapse
after flashing newfirmware using download mode+odin the phone cant reboot?have you tried diff version firmware from sammobile .
nainaabd said:
after flashing newfirmware using download mode+odin the phone cant reboot?have you tried diff version firmware from sammobile .
Click to expand...
Click to collapse
I tried 2 different firmware from SAMSmobile, after flashing in Odin, nothing changes. The phone reboots (if the case is ticked) and stays stuck on the samsung logo, after the vodafone splash screen.
tonythrash69 said:
I tried 2 different firmware from SAMSmobile, after flashing in Odin, nothing changes. The phone reboots (if the case is ticked) and stays stuck on the samsung logo, after the vodafone splash screen.
Click to expand...
Click to collapse
maybe something went wrong in partition table during kies upgrade, do you tried a full system reinstall comprensive of pit image?
myabe this get phone back to life but i think you will lose efs.
Well normaly after flashing your right Firmware you should be able to acces recovery...
franco853 said:
maybe something went wrong in partition table during kies upgrade, do you tried a full system reinstall comprensive of pit image?
myabe this get phone back to life but i think you will lose efs.
Click to expand...
Click to collapse
How can I perform what you call a "full system reinstall comprehensive of PIT image"?
I have stock firmware, but no PIT file or CSC or whatsoever.
what do you mean by losing EFS? (encryption ??)
Any help is much appreciated.
tonythrash69 said:
How can I perform what you call a "full system reinstall comprehensive of PIT image"?
I have stock firmware, but no PIT file or CSC or whatsoever.
what do you mean by losing EFS? (encryption ??)
Any help is much appreciated.
Click to expand...
Click to collapse
efs is a system partition wich contains your phone's hardware serial numbers, such as imei, wi-fi mac ecc... losing this means you can't connect to phone network until you restore it(i'm not sure you lose it)
i found this guide here on the forum to restore from brick's or similiar, i think you can try this if normal flashing don't work:
http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
When you flash full firmware from Samsung (.tar.md5), it includes things such as bootloader, tz, modem, system, cache, preload and the recovery. Just make sure to download it from site such as sammobile, and you can check yourself if your .tar.md5 you're about to flash includes these things using i.e. 7zip.
Untick "auto reboot" option and flash it. After it's done, it won't auto reboot but Odin will change text to "RESET!", this is a signal for you that it's finished.
Hold on Vol-Up+Home+Power for about 7 seconds, until you see Samsung Galaxy S3 logo. It MUST enter stock recovery you've just flashed, unless your hardware is broken. From there you can select Wipe data / factory reset.
Good luck.
JustArchi said:
When you flash full firmware from Samsung (.tar.md5), it includes things such as bootloader, tz, modem, system, cache, preload and the recovery. Just make sure to download it from site such as sammobile, and you can check yourself if your .tar.md5 you're about to flash includes these things using i.e. 7zip.
Untick "auto reboot" option and flash it. After it's done, it won't auto reboot but Odin will change text to "RESET!", this is a signal for you that it's finished.
Hold on Vol-Up+Home+Power for about 7 seconds, until you see Samsung Galaxy S3 logo. It MUST enter stock recovery you've just flashed, unless your hardware is broken. From there you can select Wipe data / factory reset.
Good luck.
Click to expand...
Click to collapse
Yes this is what I did.
But after "RESET" doing it, holding the buttons won't let me reach the recovery.
Is there a way to access it ? like for instance a USB JIG allowed me to access the DOWNLOAD mode; whereas holding the buttons never let me.
tonythrash69 said:
Yes this is what I did.
But after "RESET" doing it, holding the buttons won't let me reach the recovery.
Is there a way to access it ? like for instance a USB JIG allowed me to access the DOWNLOAD mode; whereas holding the buttons never let me.
Click to expand...
Click to collapse
I don't think so. Probably your buttons are broken then.
JustArchi said:
I don't think so. Probably your buttons are broken then.
Click to expand...
Click to collapse
I still do not understand that NO software is able to address the phone, like the recovery mode does.
We can flash from a computer, how come not to wipe from a computer.
assuming that someone has no screen or broken buttons, i'm sure there's a way to access wipe and/or access the recovery to flash a stock rom.
Thanks
tonythrash69 said:
I still do not understand that NO software is able to address the phone, like the recovery mode does.
We can flash from a computer, how come not to wipe from a computer.
assuming that someone has no screen or broken buttons, i'm sure there's a way to access wipe and/or access the recovery to flash a stock rom.
Thanks
Click to expand...
Click to collapse
do you tried the guide i linked some post ago? the one with the repartition file?
franco853 said:
do you tried the guide i linked some post ago? the one with the repartition file?
Click to expand...
Click to collapse
Hey, yes I tried the link, but again I cannot access the recovery to flash the .zip file.
When I hold the buttons as soon as the logo "galaxy s III GTI9300" appears, the screen goes black and the logo comes back again.
If I release one button, the vodafone splash screen appears, and the boot is stuck on the samsung logo.
I assume, the buttons are working because of what I just explained.
But again, I cannot access the recovery.
Last week, for some reason, after flashing I has a "setup wizard" from appeared, and crashed. that was the only time. I could see the lights under the touch buttons coming on. After the crash, I tried to reinstall and couldn't do it.
I am still sure there should be a way to wipe the nand completely or install from the SD card via the download mode.
Any help is welcome
tonythrash69 said:
Hey, yes I tried the link, but again I cannot access the recovery to flash the .zip file.
When I hold the buttons as soon as the logo "galaxy s III GTI9300" appears, the screen goes black and the logo comes back again.
If I release one button, the vodafone splash screen appears, and the boot is stuck on the samsung logo.
I assume, the buttons are working because of what I just explained.
But again, I cannot access the recovery.
Last week, for some reason, after flashing I has a "setup wizard" from appeared, and crashed. that was the only time. I could see the lights under the touch buttons coming on. After the crash, I tried to reinstall and couldn't do it.
I am still sure there should be a way to wipe the nand completely or install from the SD card via the download mode.
Any help is welcome
Click to expand...
Click to collapse
I get same thing(galaxy s3 logo, black screen then normal boot when try accessing recovery) some time ago after installing philz reco, i flashed another recovery and now runs well, it sounds so strange that you still cant get at least stock recovery after a repartition and a full system reinstall... Maybe something get broke in the hardware...

S4 stuck at RECOVERY BOOTING..... loop

I seem to be another victim of this issue. I was attempting to update my recovery (TWRP 2.6 installed) on my Verizon S4 via TWRP's app. It failed, so I figured I might try it from recovery. I attempted to boot into recovery, but it is stuck at the Samsung "custom" screen and the blue "RECOVERY BOOTING......" text is in the top left corner. I can leave the device alone for several minutes and it never goes into recovery. It does get very hot though, and occasionally it will reboot on its own. If I hook it up to my PC and then put in the battery, it will vibrate as if it is going to boot, then it vibrates again in 3 seconds and does this endlessly with nothing coming up on the screen. Without being able to get into recovery or have my desktop recognize the device, I'm not sure what to do. Any ideas before I chuck this brick?
Are you able to get into download mode (volume down, home button, power)? If you're able to, the device is not bricked and, using Odin, you can update TWRP to 2.8.4.
I've found that the app isn't working all that well. For the last few updates I've had to use Odin to update TWRP.
Strephon Alkhalikoi said:
Are you able to get into download mode (volume down, home button, power)? If you're able to, the device is not bricked and, using Odin, you can update TWRP to 2.8.4.
I've found that the app isn't working all that well. For the last few updates I've had to use Odin to update TWRP.
Click to expand...
Click to collapse
Ah ha, you are correct. I actually tried a variation of this (I think with volume up?) but it just attempted to go into recovery again. At the download screen I just told the phone to boot into the OS and all seems well. I'll look into updating TWRP via Odin and see if I have any joy, but at least I have a working phone again. Thanks for the help.:good:
When you update, do NOT try to use TWRP 2.8.5.0. It's bugged on the S4. Use 2.8.4.0 instead.
Thanks, good advice!
Looks like my recovery is toast. Doing some research, I never used Odin as my phone had the old MDK baseband. Sites tell me not to use Odin, so I followed the instructions on TWRP's site using Terminal Emulator and 2.8.4.0: http://teamw.in/project/twrp2/181 Everything seemed to go well, so I attempted to reboot into recovery, but now I get some warning/error about unauthorized software, turn off your phone and take it to Verizon, etc.
Sounds like I need to try again, but I'm not sure what my options are now.
I didn't even see you had a Verizon S4 until you mentioned it. Verizon encrypts the bootloader as a matter of course, and thus installing TWRP is not possible. You should however be able to restore the official firmware with Odin, and from there, follow the root guides at http://forum.xda-developers.com/galaxy-s4-verizon to get yourself back up and running.
mine get to the point where i select volume up, i see the android bot and message do not turn off target, and it shuts down. what do i do?

S5 G900F - Infinite Bootloop, can't access bootloader, flashed with stock roms.. HELP

Hi,
**Long Story**
I'm new here - I refrained from posting as I know a repeat post can p*** people off but I can't find my problem or fix it.
My own Sony was stolen a week ago - My brother in law kindly gave me his old S5 as a back up phone.
He has never had any problems with it EVER. I did a factory reset (from the settings menu) to clear his data and straight away I was in a boot loop (Handset vibrates, Samsung logo displays, blue LED, vibrates, handset switches off.. over and over again) the only way to stop this is to remove the battery. I cannot enter recovery mode but I CAN enter download mode. According to the settings the handset was running the latest version of lollipop.
I took the phone home anyway, thinking I could fix it - leaving the battery out in my pocket.
When I got home, I put the battery in and the phone turned on, unfortunately I forgot to put the sim card in - so I removed the battery, put in the sim card and... Boot Loop!
At this point I was really frustrated so I left the battery out and went to sleep. I woke up in the morning, put the battery in and it worked fine, all day, then all of a sudden the phone switched itself off and now I'm back in a boot loop and this time it isn't wanting to work again.
I have:
- Flashed with stock roms using Odin (5.0 & 4.4.2) - Yes, I used the correct firmware for my handset.
- Flashed with Kies to the latest firmware
- In desperation, tried the "Bash your power button against a hard, flat surface" trick
- Shouted at the handset
None of these have worked and every post I have found says to put the phone in recovery mode, I CANT. When I try, the blue "Recovery Booting" text is displayed, but just restarts anyway...
Weirdly and at random times, twice, the phone has powered on while plugged into my laptop, but the screen is blank, I get message sounds and the soft keys below the screen light up, but the screen is blank.
Any body have any idea?!?!! I'm vaguely techy, however not with this kind of thing. Any help would be much appreciated. What confuses me is there was no problem before I did the factory reset.
didscub said:
Hi,
**Long Story**
I'm new here - I refrained from posting as I know a repeat post can p*** people off but I can't find my problem or fix it.
My own Sony was stolen a week ago - My brother in law kindly gave me his old S5 as a back up phone.
He has never had any problems with it EVER. I did a factory reset (from the settings menu) to clear his data and straight away I was in a boot loop (Handset vibrates, Samsung logo displays, blue LED, vibrates, handset switches off.. over and over again) the only way to stop this is to remove the battery. I cannot enter recovery mode but I CAN enter download mode. According to the settings the handset was running the latest version of lollipop.
I took the phone home anyway, thinking I could fix it - leaving the battery out in my pocket.
When I got home, I put the battery in and the phone turned on, unfortunately I forgot to put the sim card in - so I removed the battery, put in the sim card and... Boot Loop!
At this point I was really frustrated so I left the battery out and went to sleep. I woke up in the morning, put the battery in and it worked fine, all day, then all of a sudden the phone switched itself off and now I'm back in a boot loop and this time it isn't wanting to work again.
I have:
- Flashed with stock roms using Odin (5.0 & 4.4.2) - Yes, I used the correct firmware for my handset.
- Flashed with Kies to the latest firmware
- In desperation, tried the "Bash your power button against a hard, flat surface" trick
- Shouted at the handset
None of these have worked and every post I have found says to put the phone in recovery mode, I CANT. When I try, the blue "Recovery Booting" text is displayed, but just restarts anyway...
Weirdly and at random times, twice, the phone has powered on while plugged into my laptop, but the screen is blank, I get message sounds and the soft keys below the screen light up, but the screen is blank.
Any body have any idea?!?!! I'm vaguely techy, however not with this kind of thing. Any help would be much appreciated. What confuses me is there was no problem before I did the factory reset.
Click to expand...
Click to collapse
Who is your service provider? Is the phone unlocked? Where did you get the stock firmware from?
Cryceratops said:
Who is your service provider? Is the phone unlocked? Where did you get the stock firmware from?
Click to expand...
Click to collapse
Thanks for the reply!
Service Provider - o2 UK
Stock from sanmmob
Phone is not unlocked
I did my best to try & get the firmware for my particular service provider but sammob and a few of the other sites use those awful restricted speed file sharing sites.
didscub said:
Thanks for the reply!
Service Provider - o2 UK
Stock from sanmmob
Phone is not unlocked
I did my best to try & get the firmware for my particular service provider but sammob and a few of the other sites use those awful restricted speed file sharing sites.
Click to expand...
Click to collapse
Did you try the one I linked to you or a different one?
Cryceratops said:
Did you try the one I linked to you or a different one?
Click to expand...
Click to collapse
Only just saw that - I didnt - thank you.
I will try now but may take a while to get back to you while I wait to download.
Try flashing the PIT file along with the stock ROM in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit - add to PIT section in ODIN, add ROM to AP or PDA section, flash them both at the same time
*Detection* said:
Try flashing the PIT file along with the stock ROM in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit - add to PIT section in ODIN, add ROM to AP or PDA section, flash them both at the same time
Click to expand...
Click to collapse
Thanks, did that, now the phone has started but it stuck at the first "Powered by Android" screen, not restarting but can't go any further and still cant get into recovery.
didscub said:
Thanks, did that, now the phone has started but it stuck at the first "Powered by Android" screen, not restarting but can't go any further and still cant get into recovery.
Click to expand...
Click to collapse
Try flashing just the ROM again, and then try booting into recovery, and factory reset
Or try flashing TWRP 2.8.7.0 with ODIN, and then boot into recovery and factory reset
Use this guide (Don't worry about the SuperSU part if you don't need root, and ignore the reactivation part as you can't boot the phone yet - start at No.3)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Are you flashing the latest Lollipop ROM too?
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
*Detection* said:
Try flashing just the ROM again, and then try booting into recovery, and factory reset
Or try flashing TWRP 2.8.7.0 with ODIN, and then boot into recovery and factory reset
Use this guide (Don't worry about the SuperSU part if you don't need root, and ignore the reactivation part as you can't boot the phone yet - start at No.3)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Are you flashing the latest Lollipop ROM too?
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Click to expand...
Click to collapse
flashed TWRP 2.8.7.0 - Doesn't go into revovery:
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
I was flashing with G900FXXU1BOJ1_G900FOXA1BOJ1_G900FXXU1BOJ1_HOME.tar.md5
didscub said:
flashed TWRP 2.8.7.0 - Doesn't go into revovery:
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
I was flashing with G900FXXU1BOJ1_G900FOXA1BOJ1_G900FXXU1BOJ1_HOME.tar.md5
Click to expand...
Click to collapse
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
*Detection* said:
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
Click to expand...
Click to collapse
Pulled as soon as it said Pass.
This is so confusing, is the Stock firmware that you've linked to in Mega the same as the one I have downloaded?
Will retry with TWRP again. BRB
didscub said:
Pulled as soon as it said Pass.
This is so confusing, is the Stock firmware that you've linked to in Mega the same as the one I have downloaded?
Will retry with TWRP again. BRB
Click to expand...
Click to collapse
BOJ1 yea, same one
Try different versions of ODIN, 3.09 up to 3.10.7 (Maybe even 3.07)
*Detection* said:
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
Click to expand...
Click to collapse
Definitely didt let it reboot & pulled the battery. Tried it twice to make sure.
I am downloading the Stock firmware that you have linked and will try that, is there any reason why it started to reboot constantly after I factory reset? It can't be hardware because there was never a HW problem before I reset it. I don't suppose you want to pop down from Durham and fix it?! lol
didscub said:
Definitely didt let it reboot & pulled the battery. Tried it twice to make sure.
I am downloading the Stock firmware that you have linked and will try that, is there any reason why it started to reboot constantly after I factory reset? It can't be hardware because there was never a HW problem before I reset it. I don't suppose you want to pop down from Durham and fix it?! lol
Click to expand...
Click to collapse
To London? wanna pay the plane fare? lol
If you got that firmware from Sammobile, the one I linked you to is the same one, that's where I got it from, you could try some different droid versions, try a KitKat ROM too
Not sure why it would boot loop after you factory reset it, if reactivation lock was left on, you should still have managed to get to the welcome screen, but then be locked out of the phone until you entered his samsung account login
Sounds like something bugged out during the reset, and didn't reset properly, or corrupted one of the partitions, which the PIT file should have fixed
Stock recovery is cr4p though, I've ended up with a bootloop just clearing caches from it before, and had to flash TWRP to clear them properly, then flash stock on top again just to get it to boot
*Detection* said:
To London? wanna pay the plane fare? lol
If you got that firmware from Sammobile, the one I linked you to is the same one, that's where I got it from, you could try some different droid versions, try a KitKat ROM too
Not sure why it would boot loop after you factory reset it, if reactivation lock was left on, you should still have managed to get to the welcome screen, but then be locked out of the phone until you entered his samsung account login
Sounds like something bugged out during the reset, and didn't reset properly, or corrupted one of the partitions, which the PIT file should have fixed
Stock recovery is cr4p though, I've ended up with a bootloop just clearing caches from it before, and had to flash TWRP to clear them properly, then flash stock on top again just to get it to boot
Click to expand...
Click to collapse
OK - Sorry for the delay but unfortunately I had to do stuff - I would have happily sat and tried to fix it all day.
So, I did spend some time on it earlier and a few things happened.
I reinstalled different firmwares, and also tried TWRP 2.8.7.0 a few times with different versions of Odin but nothing would work.
I reinstalled the firmware BOJ1, nothing
Tried PIT again, nothing
Then, after trying PIT I got the Firmware error and connected to Kies... It worked, but now I just have a blank screen (another seemingly common issue with these paperweights) - Unsure what to do now, the phone is on, i can call it, find it with device manager but the screen is just blank. FML.
didscub said:
OK - Sorry for the delay but unfortunately I had to do stuff - I would have happily sat and tried to fix it all day.
So, I did spend some time on it earlier and a few things happened.
I reinstalled different firmwares, and also tried TWRP 2.8.7.0 a few times with different versions of Odin but nothing would work.
I reinstalled the firmware BOJ1, nothing
Tried PIT again, nothing
Then, after trying PIT I got the Firmware error and connected to Kies... It worked, but now I just have a blank screen (another seemingly common issue with these paperweights) - Unsure what to do now, the phone is on, i can call it, find it with device manager but the screen is just blank. FML.
Click to expand...
Click to collapse
OK, so they phone is working, there's just no display...
OK, try resetting the phone remotely from here first
https://www.google.com/android/devicemanager
If it's not connected to the network - try this
http://forums.androidcentral.com/sa...ory-reset-galaxy-s5-computer.html#post4365754
If that still fails, try flashing a stock KitKat ROM from Sammobile, see if downgrading the OS is a big enough change for it to overwrite whatever is causing the problem
Wondering if TWRP has flashed, but the no screen thing is stopping you from knowing one way or another - if we could get into TWRP, we'd have a lot more options, including custom ROMs
---------- Post added at 10:00 ---------- Previous post was at 09:44 ----------
Uploaded the latest KitKat ROM
Code:
https://mega.nz/#!eIQEAQ6a!ztOhVwFuI2MpD6OBhxC-TtgwUJQCxtwnfDQvFOl3g40
*Detection* said:
OK, so they phone is working, there's just no display...
OK, try resetting the phone remotely from here first
https://www.google.com/android/devicemanager
If it's not connected to the network - try this
http://forums.androidcentral.com/sa...ory-reset-galaxy-s5-computer.html#post4365754
If that still fails, try flashing a stock KitKat ROM from Sammobile, see if downgrading the OS is a big enough change for it to overwrite whatever is causing the problem
Wondering if TWRP has flashed, but the no screen thing is stopping you from knowing one way or another - if we could get into TWRP, we'd have a lot more options, including custom ROMs
---------- Post added at 10:00 ---------- Previous post was at 09:44 ----------
Uploaded the latest KitKat ROM
Code:
https://mega.nz/#!eIQEAQ6a!ztOhVwFuI2MpD6OBhxC-TtgwUJQCxtwnfDQvFOl3g40
Click to expand...
Click to collapse
Thanks,
I'll wait for that to download and try.
So - I used accessibility mode to get into settings and do a factory reset... It was difficult, I even thought that the Dark Screen setting might have mysteriously have been turned on but nope.
Rebooted and got the Bootloader screen with the Samsung logo and Recovery Booting text, after a few minutes the screen went blank and the phone vibrated and then nothing!!! :crying::crying::crying:
I have just put it into download mode (I only know this because the many hours I've spent doing this I noticed that the battery and device goes cool when its in download mode) and will try the KitKat flash once its downloaded - Thank you for that btw.
Its so strange - it cant be an issue with the actual screen because it *sometimes* displays the logo.. What can it be?? Its also odd that from when I originally reset it, it could'nt boot into recovery. I'm worried that everything I have done has screwed it up more? Can the Recovery/Bootloader be "Broken"? Its so confusing, I hate tech that doesn't behave.
didscub said:
Thanks,
I'll wait for that to download and try.
So - I used accessibility mode to get into settings and do a factory reset... It was difficult, I even thought that the Dark Screen setting might have mysteriously have been turned on but nope.
Rebooted and got the Bootloader screen with the Samsung logo and Recovery Booting text, after a few minutes the screen went blank and the phone vibrated and then nothing!!! :crying::crying::crying:
I have just put it into download mode (I only know this because the many hours I've spent doing this I noticed that the battery and device goes cool when its in download mode) and will try the KitKat flash once its downloaded - Thank you for that btw.
Its so strange - it cant be an issue with the actual screen because it *sometimes* displays the logo.. What can it be?? Its also odd that from when I originally reset it, it could'nt boot into recovery. I'm worried that everything I have done has screwed it up more? Can the Recovery/Bootloader be "Broken"? Its so confusing, I hate tech that doesn't behave.
Click to expand...
Click to collapse
Does sound like a possible hardware problem, but unlikely or a huge coincidence that it all started after resetting, so I'd be more inclined to think otherwise
Just remembered about this unbrick image / tutorial
http://forum.xda-developers.com/galaxy-s5/general/g900f-debrick-img-lollipop-t3240626
Might be worth giving that a shot
*Detection* said:
Does sound like a possible hardware problem, but unlikely or a huge coincidence that it all started after resetting, so I'd be more inclined to think otherwise
Just remembered about this unbrick image / tutorial
http://forum.xda-developers.com/galaxy-s5/general/g900f-debrick-img-lollipop-t3240626
Might be worth giving that a shot
Click to expand...
Click to collapse
OK - might be a massive chore rooting and installing busybox.. Worth a shot though. Can I not use it with Odin??
didscub said:
OK - might be a massive chore rooting and installing busybox.. Worth a shot though. Can I not use it with Odin??
Click to expand...
Click to collapse
You don't need busybox, that's for creating your own debrick image, the tutorial stops here:
Flash this Debrick file to your 16GB Micro SD card with Win32DiskImager
*Insert your Micro SD card into your computer (backup any information you may have on it we are going to ERASE, FORMAT it to ex FAT
*Open win32DiskImager
*Navigate to the location where you downloaded the correct Debrick file
*Select your Debrick file by double clicking on it
*In the upper right corner of Win32DiskImager you should make sure that the drive letter assigned to your sd card is selected.
***Which ever drive that is listed will be erased, formatted
*Click write in the bottom right hand side
put the Debrick SD card in the Phone, Pull and Replace the Battery
Plug phone in usb and boot into download mode
yout phone should boot into download mode then flash stock firmware via odin
Download link : https://drive.google.com/file/d/0ByA...ew?usp=sharing
You're saying you can't see anything on screen in download mode, just guessing it's there because it cools down - but that could also mean it's not in any mode
With this method, you might get a display to use, then you can flash normally with ODIN with download mode visible on screen

SM-G360T1

Hello, I keep flashing TWRP with Odin but it resets when it's done and recovery does not change. I have tried several different versions of Odin and TWRP from their website and from here. Any idea what to do?
Which TWRP are you flashing? I recommend using version 3.0.1-0 from here, as version 3.0.2-0 has been known to have some problems in the past.
https://forum.xda-developers.com/showthread.php?p=66266209
Maybe try making sure Allow OEM unlock is switched on in Settings-->Developer Options before you flash it too. Obviously make sure your device is being recognized properly by ODIN as well. You should see a little blue box light up in the top left of the ODIN window when you connect the device. Make sure you're flashing it in the AP slot and no other. Also, make sure you have the current Samsung drivers installed for the SM-G360T1 from here:
http://www.samsung.com/us/support/owners/product/galaxy-core-prime-metro-pcs
Hope this helps! Have a good day.
I've honestly tried just about every version here and on the website. Started with 2.8.7 as a ROM I was interested in recommended it, however I am willing to use any that will work at this point I really only wanted my device rooted for one simple task.
My drivers appear up to date -
USB debugging and Boot unlock are both enabled -
Odin shows PASS and reboots my phone on flash -
Everything seems like it's working right, but it's not replacing my recovery. When I reboot it just takes me back to the warning/download screen. Is it possible I might need to downgrade to the original Lollipop that came with this phone first?
Edit -> I tried TrapKernel as well, that disabled my wifi entirely (on/off button would not stay in on position)
Edit -> Tried downgrading to the original Lollipop that came with my phone and it reboots itself as soon as it gets in to Android. Gonna try flashing it again before returning to current Android. :/
OutlawStarX said:
Hello, I keep flashing TWRP with Odin but it resets when it's done and recovery does not change. I have tried several different versions of Odin and TWRP from their website and from here. Any idea what to do?
Click to expand...
Click to collapse
Pull out the battery after the phone comes up on the boot logo when the flash is complete. After that put it back in and press VOL UP + HOME + POWER and it should take you to the TWRP recovery. You do this because the phone will recognize that is not a original recovery, so it replaces with the original one. Make sure to put a custom rom with root in it so it doesn’t replace the recovery again.

Categories

Resources