i9505 always booting into recovery/download mode - Galaxy S 4 Q&A, Help & Troubleshooting

I downloaded Imperium ROM from a thread on xda and installed it. I wiped data, wiped cache and dalvik and installed zip. Then I rebooted and it showed a downloading screen, after a little bit of research it's called download mode or ODIN mode. Now what's happening is whenever I try to reboot, it shows the S4 i9505 screen (i think it's called a splash screen, thats what someone called it) and freezes. After about 10-15 seconds, reboots into recovery. I've got CWM installed and I've ran out of ideas. The volume buttons are not being touched and for some reason recovery and download mode are always being booted into, never the OS.
I'm also new so anything I've done wrong, I'd love to know.

CWM recovery is outdated and should not be used anymore. Instead only use TWRP. Flash it trough Odin in the same way you flashed CWM.
You say that you only wiped data, cache and dalvik. You also HAVE to wipe /system. Otherwise the rom will probably not boot.

Lennyz1988 said:
CWM recovery is outdated and should not be used anymore. Instead only use TWRP. Flash it trough Odin in the same way you flashed CWM.
You say that you only wiped data, cache and dalvik. You also HAVE to wipe /system. Otherwise the rom will probably not boot.
Click to expand...
Click to collapse
Update I tried to install albe95's s6 port. I've noticed something and it's that both ended up with Statuc 7 or some word that started with "S" and had the number 7. Googled that and turns out it's bad. I formatted /System and installed the ROM, it worked!
I guess there was just no OS to boot into. Going to try installing Imperium now.

Status 7 errors can occur if the recovery is outdated. What recovery is on the phone?

Related

[Q] Please help! Stuck on boot screen!

I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
danlk2 said:
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
Click to expand...
Click to collapse
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
irishrally said:
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
Click to expand...
Click to collapse
Wow, that didn't even cross my mind, I did this and I've got the rom up and running now. Thanks a lot.

[Q] [Wind] I tried flashing FoxHound ROM, and soft-bricked my phone. Any fixes?

Alright... where to begin? Lets start at what happened around yesterday. Prior to the whole weekend, I had CyanogenMod 10.1 installed on my rooted S4. Come Friday, I start to miss some of the stock Samsung features such as Air Gestures, Smart Stay, the stock Samsung camera, and all that. So, I install WanamLite (a custom rom) on my phone. It's good and all but for some reason, the Smart Stay isn't working. To fix this, I go online and start digging; I find people saying "yo, revert back to the original firmware and re-install the Rom, that should fix your LTE problem." I think to myself, "maybe this could help me too." And that's exactly what I do. I go online to SamMobile and download this ROM (http://www.sammobile.com/firmwares/?page=1&model=SGH-M919V&pcode=0#firmware). It installs with Odin and I was able to get back to the Stock Samsung firmware. I then proceed with my plan and install WanamLite; that also worked. So I'm all happy and stuff 'cause Smart Stay finally works but, shortly after fiddling with the re-stocked device, I get bored again. So, I start searching the forums for another rom to replace WanamLite (it was a good rom, but I wanted to try something else before settling down on it).
I find this ROM in the XDA-Developers S4 forum: http://forum.xda-developers.com/showthread.php?t=2303239. I try installing it; it works fine. But then, I notice that half my SD card is used up. So, I go into TWRP and click on Format Data (I'm not too sure about the name, I had CWM prior to the re-installation of Samsung stock firmware). After resetting the Data, I boot back into the phone and notice that the default layout is Easy Mode. (On the bright side, I freed 4 GB from my SD card). Easy Mode's incredibly annoying, so I wrestle with the phone for a while to change the launcher to Nova launcher, but to no avail. In the end, I decide to reflash the FoxHound ROM. I place the rom on my phone and boot into TWRP. That's where the problem comes. I selected: wipe cache, wipe delvic cache, wipe data. Then I wiped the cache and data, flashed the rom and, after that is when the phone started refusing boot up. From then on, it just displayed Samsung Galaxy S4 logo on the screen whenever I tried to start it.
What I tried to fix the issue: Re-installing the stock samsung firmware. (I think I ended up screwing up the phone even more with this. Before, I had TWRP installed but I couldn't boot into it, now I don't have any custom recovery installed and I still can't boot into the phone).
I can access the Download Mode and use Odin. I cannot boot into the recovery. When I hold Volume Up + Power + Home, it just says recovery in blue above the logo, and then, the phone reboots.
So, any ideas on how to fix it?
TL;DR: Tried installing FoxHound Rom. I wiped Delvic Cache, Cache, and Data, and after flashing the rom, the phone refused to boot up; it gets stuck on the Samsung logo. Before flashing, I did Format Data. After being unable to boot into the phone, I tried to flash the Stock Samsung Firmware on my S4. Nothing worked. Any ideas on how I should proceed?
splitinferno said:
So, any ideas on how to fix it?
Click to expand...
Click to collapse
Try using Odin mode to install Stock Samsung Firmware...
If it doesn't work,
Install Samsung Kies, put Phone into Odin mode, connect the USB and let KIES reinstall the whole firmware... Go to "Tools" -> "Emergency Firmware Recovery"
psycovirus said:
Try using Odin mode to install Stock Samsung Firmware...
If it doesn't work,
Install Samsung Kies, put Phone into Odin mode, connect the USB and let KIES reinstall the whole firmware... Go to "Tools" -> "Emergency Firmware Recovery"
Click to expand...
Click to collapse
I've already tried flashing the Stock Samsung Firmware using Odin, it didn't work. Also, I'm having no luck with Kies; it won't connect. Any other suggestions? :/
EDIT 1: Okay, so here's the deal right now: I was able to flash TWRP using ODIN. This granted me access to my recovery, somehow. So right now, I have the FoxHound_GearEngine0.2 ROM installation files on my SD card and I am booted into the recovery. What should I do? Should I try flashing again? For now, I'll just wait for a response.
EDIT 2: Out of curiosity and impatience, I tried flashing FoxHound but got an error:
Updating Partition Details
E: unable to mount data
E: unable to mount internal storage
TWRP v. 2.5.0.3
Go into the advanced menu in TWRP and try to mount data / internal storage. If you can't, then you're back to odin unless someone can find out something else
maazali said:
Go into the advanced menu in TWRP and try to mount data / internal storage. If you can't, then you're back to odin unless someone can find out something else
Click to expand...
Click to collapse
I tried to; it didn't work. I also tried clockworkmod recovery. That recovery said it said that the data was already mounted. For some reason, now the phone is stuck in a bootloop. On the bright side, I can freely access my recovery (although I can't do much in it). Should I try flashing other stock roms?
EDIT: Flashing the stock rom brought it back to the state it was in earlier. So now, it just hangs on the Samsung Galaxy S4 screen and no longer reboots continuously. I'm thinking of downloading other stock roms and flashing those.
UNBRICKED
splitinferno said:
I tried to; it didn't work. I also tried clockworkmod recovery. That recovery said it said that the data was already mounted. For some reason, now the phone is stuck in a bootloop. On the bright side, I can freely access my recovery (although I can't do much in it). Should I try flashing other stock roms?
EDIT: Flashing the stock rom brought it back to the state it was in earlier. So now, it just hangs on the Samsung Galaxy S4 screen and no longer reboots continuously. I'm thinking of downloading other stock roms and flashing those.
Click to expand...
Click to collapse
Alright, after struggling around with the device, I was able to unbrick it. I downloaded the stock ROM from samfirmware and flashed it using odin. After flashing it, it would stay on the Samsung Galaxy S4 logo and that's it and I wasn't able to boot into the recovery either. So, I flashed TWRP using odin and download mode, and found I was able to boot into recovery again. Screwing around with the recovery, I couldn't manage to do much so I decided to re-flash the stock firmware. After re-flashing, I had the same problem. This time, I tried accessing the stock recovery. I got access, which was something I couldn't get before. After getting access, I did Factory Reset/Data (it was something along those lines) and did a wipe cache. After wiping cache, the phone rebooted and, much to my delight, it was unbricked. After going through this, I think I might just like chill for like a month, or a year now with stock... .__.
Hahah nice job
Sent from my GT-I9505 using xda premium
splitinferno said:
Alright, after struggling around with the device, I was able to unbrick it. I downloaded the stock ROM from samfirmware and flashed it using odin. After flashing it, it would stay on the Samsung Galaxy S4 logo and that's it and I wasn't able to boot into the recovery either. So, I flashed TWRP using odin and download mode, and found I was able to boot into recovery again. Screwing around with the recovery, I couldn't manage to do much so I decided to re-flash the stock firmware. After re-flashing, I had the same problem. This time, I tried accessing the stock recovery. I got access, which was something I couldn't get before. After getting access, I did Factory Reset/Data (it was something along those lines) and did a wipe cache. After wiping cache, the phone rebooted and, much to my delight, it was unbricked. After going through this, I think I might just like chill for like a month, or a year now with stock... .__.
Click to expand...
Click to collapse
Next time don't wipe data in custom recovery because it will corrupt your data which would most probably end with not booting past the Samsung logo, if you want to wipe in a custom recovery for now you have to manually wipe system, cache and dalvik cache located in mounts in cwm recovery (not sure where to find it in twrp).
You should read a little before messing with things in recovery.
Ahahah that's funny because something similar happened to me. And I was going to suggest doing a factory reset via recovery because that's how I resolved my problem, then I see you did just that! (Y)
Sent from my GT-I9500

Reboots cause loops, TWRP cant mount data

ive tried a whole bunch of roms and the behavior seems to be very consistent.
Here's the scenario, same for every rom:
-boot into TWRP, advanced wipe -> wipe everything
-flash rom over adb sideload
-reboot system
-rom comes up just fine the first time, log into google, restore apps
-any time i reboot after, it sits on "Galaxy s4" boot screen, if I then reboot into recovery, TWRP asks for password because it can't mount partitions.
-only way ive found to get out of this is to format data, then reflash.. only until the first reboot again.
stock rom works flawless, the only custom rom that also worked flawless was task650's AOKP 4.2 rom, which was strange but i used it for couple months. now since i i updated to his latest 4.3 release the same issue came up, so i tried again a number of different roms.. no luck
ive exausted my google-fu and these forums, can someone please help... is this a kernel issue? bad hardware? am i just doing something very simple very wrong?
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
jd1639 said:
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
Click to expand...
Click to collapse
same thing, except this time it didnt even boot once, stuck on "galaxy s4" logo, then rebooting back into TWRP prompted a password coz it couldnt mount anything...
i think it gets stuck on boot logo because it cant mount partition same way TWRP cant, but i have no idea why it wouldnt be able to after a reboot or what could be screwing it up
Why don't you try flashing a new recovery?

[Q] Xt907 Freezes at bootloader unlock screen on 4.3 Roms

Hi guys I've been searching and cant seem to find an answer. My xt907 is rooted and my boot loader is unlocked I'm running CWM. If i install any 4.3 roms they work great for initial boot but as soon as i reboot it hangs at the warning boot loader unlocked screen. And the only way i can get the phone working again is to get to ap fastboot and use the DROID_RAZR_M_Utility_1.20 to factory reset everything. If i flash a 4.2.2 rom i don't have any problems. Any ideas guys ? Ive searched and cant seem to find an answer anywhere. Thanks in advance!
My first flash of 4.3 did this... after that I used twrp and haven't had it happen since...
Sent from my XT907 using xda app-developers app
The latest TWRP+mounting system prior to data/system wipes will probably solve your problems. Also, if you have a backup stored, you shouldn't need to fastboot every time.
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Ryan F said:
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Click to expand...
Click to collapse
twrp 2323???
You need twrp 2630
see my goodies.
aviwdoowks said:
twrp 2323???
You need twrp 2630
see my goodies.
Click to expand...
Click to collapse
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
Fastboot!
Extract the recovery.img from the zip.
But why do that, just flash the zip from your twrp you now have installed
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
I believe the one that Avi has is a .zip, not a .xml, so it needs to be flashed in recovery. Load it up on your SD, boot into the recovery you have now, flash the new recovery, and then reboot recovery.
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
aviwdoowks said:
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Click to expand...
Click to collapse
Okay, I downloaded the zips again to make sure. This freezing at bootloader screen has happened with every of the dozen or so roms I've tried installing over the past 6 months since I unlocked the bootloader.
RikRong said:
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
Click to expand...
Click to collapse
Could you clarify a little bit?
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
What's the FDR option?
---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------
Ryan F said:
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
Click to expand...
Click to collapse
Following the above steps didn't solve it The rom installs fine, boots up for first time normally, but still freezes on the bootloader screen after a restart.
Try geting to the bootloader options & choose normal pwr up.
The new twrp will stick at the big M sometimes.
Then the file is bad or you are missing the install steps. FDR (Factory Data Reset) is the first option you get when you go into the wipe menu, before you go into advanced options. Make sure you're wiping system too, after you mount. If it doesn't work, then it's a bad file or you're still doing something wrong. Upgrading to the most current TWRP and mounting system fixed the issues for 99% of the people. The other 1% just have one of those phones that is "quirky."
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
beady1 said:
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
Click to expand...
Click to collapse
Part of your problem is because you are using SS. If you're BL is unlocked, get rid of SS and use CWM or TWRP. SS is not a real recovery replacement, your stock recovery is still there. That's probably part of the reason you had issues.
possibly but i have 0 issues now so its not a big deal.
I have the stable Cyanogenmod 10.1 installed on my phone now. I'm able to restart my phone without any consequences finally. Yay.
I also tried the cm-11-20131221-NIGHTLY-xt907.zip build. That one would initially start up fine, but a restart gave me the frozen bootloader screen. I tried it twice, redownloading it, too. Gah, it's frustrating not being able to try out different roms, but at least I have one that works!
Well, thanks for the help guys. I'd still like to be able to install other roms, so if anyone else has something I can try, I'll do it!

Recovery can't mount /system S5 bricked

TWRP can't mount /system. Phone is a SM-G900T 16GB
- Running the latest version of TWRP I tried:
- Wiping, repairing, and reformatting from TWRP, also tried formatting data. I get a unable to mount '/system' error message every time.
- Using Odin and Heimdall to reformat using a downloaded .pit, neither works. I ran Heimdall in Windows and Linux (ran as sudo and admin). I re-downloaded the .pit multiple times and tried a couple different sources.
- Installing CWM using Heimdall, and ADB. In ADB and Heimdall I still have TWRP and in Odin it removes the recovery completely.
- Fix permissions gives the unable to mount '/system' error message.
- Installing ROM from Heimdall and TWRM
- Mounting /system with or without MTP
How it happened:
I was running Cyanogenmod 11 with encryption and updated to 12. CM12 was running great, flashed GApps, still running good. I signed in to my Google account and downloaded IPcamera. While running IPcamera I got an email, the screen started going crazy flashing between the alert and IPcamera screen, I couldn't do anything so I pulled the battery. When I rebooted it was stuck in a boot loop. I booted into recovery, it asked for my encryption password as usual. The password didn't work. I tried several times. I rebooted and tried again, still nothing. I rebooted again and this time hit cancel when asked for the password. I wiped everything and got the can't mount /system error. I tried everything above, nothing works.
I can't download my .pit so there is more wrong than just the data partition.
Any ideas? I would love this thing to no longer be a really expensive paperweight. I really can't afford to replace this thing right now
Thanks for your help.
Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.
Commodore 64 said:
Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.
Click to expand...
Click to collapse
That worked!! I don't know why the stock recovery can fix it when TWRM couldn't. It worked though. Thanks a ton!!
Commodore 64 said:
Odin back to factory stock and use Samsung's stock recovery to do a couple of wipes.
Click to expand...
Click to collapse
This didn't work for me every time I wipe in TWRP it just never installs the packages, or upon restart it just doesn't mount system. Wipe repair on TWRP doesnt work either
egyptshun said:
This didn't work for me every time I wipe in TWRP it just never installs the packages, or upon restart it just doesn't mount system. Wipe repair on TWRP doesnt work either
Click to expand...
Click to collapse
I'm totally with you on wipes and package installs randomly failing on TWRP, but I have no idea why. Sometime in December, I made the switch to Philz CWM, and I haven't looked back since.
At any rate, it is always good practice to odin back to stock, use the stock recovery to do wipes (factory reset and wipe cache), and then odin Philz CWM or any recovery program of your choice.
If you're planning on loading Lollipop, then you might just download the latest from Sammobile, odin the stock and wipe, and then load your custom recovery.
Best of luck,
Commodore 64 said:
I'm totally with you on wipes and package installs randomly failing on TWRP, but I have no idea why. Sometime in December, I made the switch to Philz CWM, and I haven't looked back since.
At any rate, it is always good practice to odin back to stock, use the stock recovery to do wipes (factory reset and wipe cache), and then odin Philz CWM or any recovery program of your choice.
If you're planning on loading Lollipop, then you might just download the latest from Sammobile, odin the stock and wipe, and then load your custom recovery.
Best of luck,
Click to expand...
Click to collapse
I have a G900W8, there's no lollipop version for me. What phone FW can I flash and retain phone signals etc.
Captian Double post Double post here.
I'm going to snap my phone in half, it's been over 13 hours of trying to fix this. How does no one else have this problem?
EDIT: YAAAAAAAAAAAAAAAAAAAASSSSS I FINALLY GOT IT TO WORK > I HAVE NO CLUE HOW <

Categories

Resources