CWM for the Galaxy S5 Sport SM-G860P
This is a source built CWM recovery for the Sprint Galaxy S5 Sport. This has not been tested on any other variant.
Things that have been tested
Making a backup
Flashing to /system and /data
Mounting partitions
Things that need tested
Restoring a backup
Wiping device
Flashing a Kernel
Flashing a Recovery
Known issues
None
Installation Instructions
Download and open odin.
Put your phone into download mode.
Add the downloaded tar.md5 file into the PDA section
Make sure nothing other than Auto Reboot and F. Reset Time are the only things that are checked.
Click start - the phone will reboot after the install is done.
XDA:DevDB Information
[RECOVERY] CWM S5 Sport SM-G860P, Tool/Utility for the Sprint Samsung Galaxy S 5
Contributors
rujelus22
Version Information
Status: Beta
Current Beta Version: 1.0.0.0
Beta Release Date: 2014-10-16
Created 2014-10-16
Last Updated 2014-10-16
Reserved
Reserved
S5 Recovery!
Thank you!!! I'm trying this out right now - did notice one thing that may help others searching - believe it should be sm-g860p rather than sm-g680p
:good:
wolverinexc said:
Thank you!!! I'm trying this out right now - did notice one thing that may help others searching - believe it should be sm-g860p rather than sm-g680p
:good:
Click to expand...
Click to collapse
Changed now. Typo Thanks
When flashing the recovery zip, I get the following errors:
"E:footer is wrong"
"E:signature verification failed"
I flashed using the flashify app - is this possibly the issue? if so, how should I properly flash the zip having only stock recovery?
Thanks!
Since you don't mention it, I'm going to guess that we should flash with ODIN?
rujelus22 said:
CWM for the Galaxy S5 Sport SM-G860P
This is a source built CWM recovery for the Sprint Galaxy S5 Sport. This has not been tested on any other variant.
Things that have been tested
Making a backup
Flashing to /system and /data
Mounting partitions
Things that need tested
Restoring a backup
Wiping device
Flashing a Kernel
Flashing a Recovery
Known issues
None
XDA:DevDB Information
[RECOVERY] CWM S5 Sport SM-G860P, Tool/Utility for the Sprint Samsung Galaxy S 5
Contributors
rujelus22
Version Information
Status: Beta
Current Beta Version: 1.0.0.0
Beta Release Date: 2014-10-16
Created 2014-10-16
Last Updated 2014-10-16
Click to expand...
Click to collapse
wolverinexc said:
When flashing the recovery zip, I get the following errors:
"E:footer is wrong"
"E:signature verification failed"
I flashed using the flashify app - is this possibly the issue? if so, how should I properly flash the zip having only stock recovery?
Thanks!
Click to expand...
Click to collapse
It's a Tar. I'd assume it's flashed with Odin, buddy.
Sent from my SM-G860P using Tapatalk Pro
VicFreeze said:
It's a Tar. I'd assume it's flashed with Odin, buddy.
Sent from my SM-G860P using Tapatalk Pro
Click to expand...
Click to collapse
Thanks, the version I downloaded was a zip - no tar inside. I'll check out the tar.
installed the recovery this morning with odin went perfect backing up system now will report back with results. im running stock now not to sure if there is a kernel to flash or the other things to test out .
---------- Post added at 10:51 AM ---------- Previous post was at 10:46 AM ----------
seems like backing up system is taking a long time to back up. backed up boot image and backed up recovery image seems like its hung on system. wonder now if i should of backed up to internal. backing up system completed backing up data now everything working great generating md5 checksums. was wondering if i wipe system and restore doesn't work how can i get my system back up again.
---------- Post added at 11:18 AM ---------- Previous post was at 10:51 AM ----------
recovery worked great just waiting for a response for my above question if restore doesnt work how would i go about getting my system back up again, if i wipe it
bbrita said:
recovery worked great just waiting for a response for my above question if restore doesnt work how would i go about getting my system back up again, if i wipe it
Click to expand...
Click to collapse
You need to download the stock NG2 tar. If something goes wrong with the restore (or something went wrong with the backup), you obviously won't get THAT system back. Get the stock tar to get the stock system back (then just re-root & what have you).
Sent from my SM-G860P using Tapatalk Pro
VicFreeze said:
You need to download the stock NG2 tar. If something goes wrong with the restore (or something went wrong with the backup), you obviously won't get THAT system back. Get the stock tar to get the stock system back (then just re-root & what have you).
Sent from my SM-G860P using Tapatalk Pro
Click to expand...
Click to collapse
isnt the ng2 tar for the s4? i looked it up and said it was for galaxy s4
bbrita said:
isnt the ng2 tar for the s4? i looked it up and said it was for galaxy s4
Click to expand...
Click to collapse
Samsung often shares build increments across many devices. There is an NG2 build for several models, so I am not exactly sure what or how you were looking for with regard to a stock image for this particular device. There are NG2 and NG3 firmware Tars out there easily accessible from the main Samsung firmware databases. One is here: http://samsung-updates.com/device/?id=SM-G860P (either one is fine, but NG3 will put you back to the latest OTA, of course).
VicFreeze said:
Samsung often shares build increments across many devices. There is an NG2 build for several models, so I am not exactly sure what or how you were looking for with regard to a stock image for this particular device. There are NG2 and NG3 firmware Tars out there easily accessible from the main Samsung firmware databases. One is here: http://samsung-updates.com/device/?id=SM-G860P (either one is fine, but NG3 will put you back to the latest OTA, of course).
Click to expand...
Click to collapse
Thanks for the link. Going to flash the recovery and run a backup in a few minutes.
Hello
Hello all,
I just put a request in to get our own thread. I request everyone do the same. Hopefully this is possible. I havent been in xda since the S2 Skyrocket..... I'm hopeful we can get some more devs in here to get this started!!
Here is a link to the request thread....
http://forum.xda-developers.com/showthread.php?t=1660354
I haven't done a restore yet, but in making the backups, one to internal storage and one to external (a 64GB class 10 uSD), both took quite a bit of time creating the MD5, and backing up to external took quite a bit longer than backing up to internal.
Sent from my SM-G860P using Tapatalk
s5 sport
remove this
I tried the MOAR ROM, will post link when I get to work tomorrow. ROM installed fine but wouldn't boot. Good news is my backup made with this recovery worked 99%. I was on ART and it said I was using more space than I actually was after restoring. Just had to change back to dalvik
Sent from my SM-G860P using XDA Free mobile app
I was about to try MOAR...Thanks for being a guinea pig for us Sport users.
Sent from my SM-G860P using Tapatalk
wolverinexc said:
I tried the MOAR ROM, will post link when I get to work tomorrow. ROM installed fine but wouldn't boot. Good news is my backup made with this recovery worked 99%. I was on ART and it said I was using more space than I actually was after restoring. Just had to change back to dalvik
Sent from my SM-G860P using XDA Free mobile app
Click to expand...
Click to collapse
I try the MOAR ROM also got the same just kept rebooting
Related
I noticed that the clock in TWRP 2.5.0.2 is reporting the incorrect time. Is anyone else seeing this? Any work around? For now I am entering the file names manually.
I would also love a way to kick off a NANDROID from an Android application that could launch TWRP. I used to do this with ROM Manager and CWM. Anyone know if this is possible with TWRP?
I moved to TWRP because CWM did not support my 64 GB SD card unless I formatted it to EXT4.
Thanks,
Scott
EDIT: I just checked my phone while it is backing up. TWRP is reporting the time as 7:51 pm. Its 11:37 am in Boston!
swieder711 said:
I noticed that the clock in TWRP 2.5.0.2 is reporting the incorrect time. Is anyone else seeing this? Any work around? For now I am entering the file names manually.
I would also love a way to kick off a NANDROID from an Android application that could launch TWRP. I used to do this with ROM Manager and CWM. Anyone know if this is possible with TWRP?
I moved to TWRP because CWM did not support my 64 GB SD card unless I formatted it to EXT4.
Thanks,
Scott
EDIT: I just checked my phone while it is backing up. TWRP is reporting the time as 7:51 pm. Its 11:37 am in Boston!
Click to expand...
Click to collapse
I too have noticed this. It also says the year is 1970 on my phone! Now if we only had something as sweet as the S4 in 1970.......I'm entering it manually too.
Reinstall TWRP using GooManager. It'll work itself out eventually. I always install TWRP, boot into recovery, reboot system, reinstall TWRP again and let it be. Corrects itself by the next ROM flash. Always worked for me anyway.
Delakit said:
Reinstall TWRP using GooManager. It'll work itself out eventually. I always install TWRP, boot into recovery, reboot system, reinstall TWRP again and let it be. Corrects itself by the next ROM flash. Always worked for me anyway.
Click to expand...
Click to collapse
I have GooManager 2.12 installed, but am not that familiar with using it. I Looked in Setting and Browse all files for anything related to TWRP and could not find it. Can you provide me a bit more guidance on using GooManager to reinstall TWRP such as where to look?
thanks
Scott
EDIT: Never mind I found a tutorial, http://galaxys4root.com/galaxy-s4-root/how-to-install-twrp-on-rooted-galaxy-s4-using-goo-manager/
Do I get to pick what version of TWRP gets installed. I am okay with 2.5.0.2
swieder711 said:
I have GooManager 2.12 installed, but am not that familiar with using it. I Looked in Setting and Browse all files for anything related to TWRP and could not find it. Can you provide me a bit more guidance on using GooManager to reinstall TWRP such as where to look?
thanks
Scott
EDIT: Never mind I found a tutorial, http://galaxys4root.com/galaxy-s4-root/how-to-install-twrp-on-rooted-galaxy-s4-using-goo-manager/
Do I get to pick what version of TWRP gets installed. I am okay with 2.5.0.2
Click to expand...
Click to collapse
Last I checked 2.6.0.0 is out and that's what I have installed as of 10 minutes ago. I have yet to have any issues with it. There are places you can look to find the older versions and flash those but I don't remember where those are located exactly. I know it's affiliated with the TWRP website.
I installed TWRP 2.6.0. 0 via GooManager and the date and time are still incorrect.
I have tried backing up multiple NANDROIDs and the date/times are all wrong.
Now what?
Sent from my Nexus 7 using Tapatalk 2
swieder711 said:
I installed TWRP 2.6.0. 0 via GooManager and the date and time are still incorrect.
I have tried backing up multiple NANDROIDs and the date/times are all wrong.
Now what?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Whenever I install twrp I install it twice in a row and if works out fine for me...
Sent from my SCH-I545 using xda app-developers app
Delakit said:
Whenever I install twrp I install it twice in a row and if works out fine for me...
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I just reinstalled TWRP 2.6 twice in a row via GooManager. Upon a reboot to recovery the time is still incorrect. Do you reboot in between the double install of TWRP? How are you installing TWRP?
I would really like to fine a way for TWRP to report the correct date and time. All suggestion are welcome.
Delakit said:
Whenever I install twrp I install it twice in a row and if works out fine for me...
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I found a work around which is to install the application ROM toolbox. This lets me create a NANDROID from an Android application. It picks up the correct date and time and feeds that information to TWRP! Yeah.
EDIT: ROM Toolbox picks up the correct date and time for the NANDROID file name. The date and time stamp on the file itself is still wrong.
did anyone found solution for this?
Goomanager, reboot in to recovery, setting, and change the time zone. Every time when I do a nandroid back I rename the backup like HDRLS 14 2-20-14. This is the way I rename the backup...
Hello, i know that post is pretty old, but to fix that : boot in TWRP, settings, time zone, select your time zone and it fixed
ptl4ever said:
did anyone found solution for this?
Click to expand...
Click to collapse
I had the same problem, but I guess it starts when flashing TWRP on a device that has not the right date/time set before flashing TWRP. (I was too eager to change ROM on my device, so I never bothered to set time/date on the device's initial system before flashing TWRP - That's why many other users do not have any problem at all with time/date of TWRP, they simply used their device already with the right time set before flashing TWRP).
So after flashing TWRP I noticed that the time was wrong (and when making a backup I saw that even the date was wrong). It showed that it was the 1st January of 2014 (default date when not seting date on this specific device).
So, after some time I found out, that you have to FISRT SET TIME/DATE on your device's system and THEN flash TWRP. TWRP will then get the (right) time/date of the system on your device.
Another thing that was interesting though, is that TWRP's wrong date/time would even show in the system of the device, if the device was set to get time/date from the network but couldn't connect to it.
So it seems that TWRP get's its time/date setting from the device's system when it's initially flashed, but then the system of the device takes the date/time from TWRP, as it is like a layer "before" the system.
So to cut things short, if you have TWRP flashed and it shows wrong time, try flashing another recovery (CWM) or a stock ROM (over Odin), set the right time on your device and then finally flash TWRP again. (TWRP is much smoother than CWM in my opinion and worth the hussle).
All the above were executed on a Galaxy S5 SM-900F and by system I mean the android version installed on the device.
Good luck!
As listed above in twrp settings and change timezone. Profit.
Travisdroidx2 said:
As listed above in twrp settings and change timezone. Profit.
Click to expand...
Click to collapse
And how many time-zones are required to change the year from 1971 to 2015? I don't think that option exists on TWRP menu...
jaibar said:
And how many time-zones are required to change the year from 1971 to 2015? I don't think that option exists on TWRP menu...
Click to expand...
Click to collapse
Sorry thread title says clock is wrong. That is what I answered.The 70's I hear was good times. 2015 is so overrated lol
Just download the Offical TWRP App, find the Next older version of TWRP Recovery Image you have and Install that version, of course make sure time is correct and date first! Profit!!
Than you could re-flash next version as you had it
Pretty sure you can change it TWRP's settings. I think there's an option for "Time Daemon"
Travisdroidx2 said:
Sorry thread title says clock is wrong. That is what I answered.The 70's I hear was good times. 2015 is so overrated lol
Click to expand...
Click to collapse
If you think 2015 is overrated, try 2021 lol.
Hi,
I'm using only stock rom, rooted and with xposed mods on my Nexus devices. Because of trying some things out, I want to have a stock rom update.zip from the latest Factory Image on my device to have the security to flash it back to stock without a computer.
So, I've managed with some help this update.zip. It's absolutely pure stock. Not rooted, not deodexed or anything else (to root, there is a link below)
I think, some of you are thinking the same and so I want to share this update zip. I hope you have fun with it.
It works with CWM and TWRP Recovery!
Romversion
KOT49H Hammerhead
Tweaks / Changes
Nothing
Download
Stock ROM KOT49H Hammerhead
MD5 Checksum: 864626c54510b0c0eb3dac8a23e66f45
Thanks to
vetzki
caho
for their kindly help!
Infos
- You want root, you only have to flash, this file here, too: SuperSU Download
- the install process is slow. Please wait, it really installs. It takes about 5 Minutes. If someone has the ability to show me how to make it faster: Please, please!!!
Have Fun!
So, do you recommend a full wipe and cache clear when installing this?
Let's say I want to go stock in anticipation of a new update to android. I would go to Recovery (I use twrp), wipe data/erase everything from my previous rom, and then flash update.zip (and supersu at the same time), and I'll be set with stock everything including kernel, etc?
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
Click to expand...
Click to collapse
Well, question still stands. I still want to ensure this thing catches kernels and everything else provided I do a full wipe, and I assumed a full wipe is recommended (as with most things on this site). I wanted to get clarification before hand.
xybur said:
Well, question still stands. I still want to ensure this thing catches kernels and everything else provided I do a full wipe, and I assumed a full wipe is recommended (as with most things on this site). I wanted to get clarification before hand.
Click to expand...
Click to collapse
Yes if you want to flash the ROM you should do a full wipe just in case there are any mods left over from the previous ROM/kernel.
What the previous poster was informing you of is that flashing this ROM won't give you the update directly from Google itself. You will need to flash the new update manually as the md5 sum gets checked when they send out updates.
It's nothing to worry about just flash the new update when it comes. Most of the time you can flash the new update before Google would send it out to your phone anyways.
Mo'HAWK said:
Yes if you want to flash the ROM you should do a full wipe just in case there are any mods left over from the previous ROM/kernel.
What the previous poster was informing you of is that flashing this ROM won't give you the update directly from Google itself. You will need to flash the new update manually as the md5 sum gets checked when they send out updates.
It's nothing to worry about just flash the new update when it comes. Most of the time you can flash the new update before Google would send it out to your phone anyways.
Click to expand...
Click to collapse
Gotcha, thanks for the help/clarification.
As far as I know, google send updates to rooted devices, too.
But I don't want to swear
A full wipe is indeed better if you come from another rom.
But with a nandroid backup, you can try.
Sent from my IPhone 7s
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Click to expand...
Click to collapse
FormelLMS said:
As far as I know, google send updates to rooted devices, too.
But I don't want to swear
Click to expand...
Click to collapse
Hello,
All is here about OTA and root: [INFO] Nexus 5 OTA Help-Desk...
Thanks!
So it's right.
Flash this rom, don't delete or change a file. No new Kernel and you can receive the update.
Sent from my IPhone 7s
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
Click to expand...
Click to collapse
very wrong. first off, Google does not check. secondly, you can get an update while having root, as long as you do not change system files. why do you think we get so many "i updated ota and lost root" threads?
I'm just curious, I thought that the recovery was supposed to be stock to receive ota updates? Tia
Sent from my Nexus 5 using JellyBombed Tapatalk 2
Would you care to share how did you make flashable stock room?
Sent from my Nexus 5 using Tapatalk
Hey,
this thread here shows the most:
http://forum.xda-developers.com/showthread.php?t=2285831
You have to know, that you need the extracted system.img as the system folder in your update.zip.
Then you need the boot.img unextracted.
This is a all easy. A bit complicated is the meta-inf folder.
I've used this folder from other aosp roms.
I have to learn that now, too.
Sent from my IPhone 7s
Download link not working????
Sent from my Nexus 5 using XDA Free mobile app
Hi Folks,
I have just installed CWM recovery V 6.0.4.6 using ROM Manager app in my Galaxy S3 I9300 running on stock android 4.3 . I rebooted the device to check it and it was successfully installed. While I tried to reboot device through an option in the recovery, it showed up two messages as follows,
Message 1:
ROM may flash stock recovery on boot. Fix? THIS CAN'T BE UNDONE
1.No
2.Yes - Disable recovery flash
Message 2:
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. No
2. Yes - Fix root (/system/xbin/su)
I selected option "2.Yes - Disable recovery flash" from Message 1 and again option "2. YES fix root (/system/xbin/su)" from Message 2.
Why these messages are getting displayed? Is there any problem now?
Also please let me know whether it will revert to Stock Android Recovery by selecting Option "1.No" from Message 1. If so again I have to flash CWM recovery?
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks. So shall I revert back to stock recovery by selecting 1.No from message 1 and then flash cwm using odin?. Will it be fine?
I have also read that many folks facing same kinda issue even they flashed CWM recovery using odin.
Please advice that will there be any issues if I flash Cynogenmod 10.2 now?.
Any help on this? Please.
mpadhu said:
Any help on this? Please.
Click to expand...
Click to collapse
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
---------- Post added at 09:30 AM ---------- Previous post was at 09:22 AM ----------
boomboomer said:
Don't use rom manager on the s3.
Click to expand...
Click to collapse
I have seen this a couple of times on this forum... I have recently switched from TWRP to CWM recovery. The reason that I switched was due to TWRP having updates that bork major parts of the phone. I used TWRP for over a year on this phone. Now that I use CWM, the only thing that I have noticed different is that the updates seem to be more quality controlled for CWM than TWRP...
With that said, do you care to elaborate on your advice to use TWRP over CWM?
Do you have any further reasoning on your advice?
Thanks!
Edit: As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. I chalked it up to bad programming... *Shrug* Not really an issue for me, but it tells me a thing or two about quality control...
t1n0m3n said:
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
---------- Post added at 09:30 AM ---------- Previous post was at 09:22 AM ----------
I have seen this a couple of times on this forum... I have recently switched from TWRP to CWM recovery. The reason that I switched was due to TWRP having updates that bork major parts of the phone. I used TWRP for over a year on this phone. Now that I use CWM, the only thing that I have noticed different is that the updates seem to be more quality controlled for CWM than TWRP...
With that said, do you care to elaborate on your advice to use TWRP over CWM?
Do you have any further reasoning on your advice?
Thanks!
Edit: As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. I chalked it up to bad programming... *Shrug* Not really an issue for me, but it tells me a thing or two about quality control...
Click to expand...
Click to collapse
Rom manager isn't cwm recovery, they're 2 different things. It's better to install cwm recovery through means other than rom manager to avoid problems. The advice wasn't against using cwm recovery.
dxppxd said:
Rom manager isn't cwm recovery, they're 2 different things. It's better to install cwm recovery through means other than rom manager to avoid problems. The advice wasn't against using cwm recovery.
Click to expand...
Click to collapse
Hence the statement:
"As far as the APK component to each recovery, Rom Manager updates CWM without issue. I could never get goomanager to update twrp properly. "
dxppxd said:
It's better to install cwm recovery through means other than rom manager to avoid problems.
Click to expand...
Click to collapse
My point is that of the two, Rom Manager is the one that works. I have never had issues using Rom Manager to install recoveries. Although, I always install the first time using fastboot... So my anecdotal impressions may not apply here.
Care to explain your statement? (Which is the intent of my original message. Why the Koushik XDA witchhunt?)
I would search, but XDA search is borderline unusable.
Thanks!
boomboomer said:
Stock firmware will restore stock recovery on next boot, suggest you read and understand the basics before you damage your phone.
Don't use rom manager on the s3.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
None of the stock roms I've used have ever tried to restore stock recovery, it's just left there from other devices that do it.
t1n0m3n said:
Unless you are trying to unroot your phone it is fairly safe to say Yes to both.
If you already have the custom rom of your choice able to be flashed, then you should just go ahead and flash it instead of rebooting and this message should not be seen again.
Click to expand...
Click to collapse
Thank you. I am planning to flash Cynogenmod 10.2. Hope everything goes fine. I have taken a backup of my ROM. Attached file is the pic of the backup messages. Please let me know if the backup was fine.
When asked those i always select "no" to both. Never had an issue.
mpadhu said:
Thank you. I am planning to flash Cynogenmod 10.2. Hope everything goes fine. I have taken a backup of my ROM. Attached file is the pic of the backup messages. Please let me know if the backup was fine.
Click to expand...
Click to collapse
Looks like a successful backup to me.
t1n0m3n said:
Looks like a successful backup to me.
Click to expand...
Click to collapse
Thank you. I have successfully flashed Cynogenmod 10.2.
I can see my old android files still present in the internal memory. I did wipe data/factory reset, wipe cache partition and wipe dalvik cache but still the files are present. Will it cause any problem if I remove those files? If No will a factory reset work to remove those files?
[SOLVED]
Turns out CMW 6.0.4.7 will not flash to this device - solution was to use the app "Flashify" from the play store which simply and easily installed TWRP
Thanks joshm.1219!
[SOLVED]
I am at a complete loss for a fix. Short story is: I wasn't receiving any MMS, so I finally decided to ODIN back to stock and used this method so I could keep my data. Here's what happened next:
- ODIN passed but I couldn't get past the Verizon logo
- Tried several suggested fixes but the last resort one worked; I wiped data & factory reset (thus defeating the purpose of the no-wipe ODIN... w/e)
- Everything loads fine, TouchWiz works but I get a Factory Mode popup and can't lock my screen. (still can't lock my phone even now but will use this method if I think I'm stuck with TouchWiz)
- I use this method to unlock bootloader and root - root confirmed.
- Try to install CWM recovery or TWRP (btw, where the hell did GooManager go and why is it so hard to find now) and they say successful but I simply can't boot into them, just keep getting the factory recovery screen which won't let me flash any roms or any non-signed .zips
- MMS Still doesn't work!
- I call VZW in desperation and somehow they magically reset my account services and MMS works again! (I probably could have done this in the first place and not lost my ROM/Data and sanity if I'd known)
I have looked high and low for a solution but have found none. I also have been unable to find a REGULAR stock MDK file to flash on this phone - I can only find the NO-WIPE version which doesn't even allow you to keep your data. I'm confused and frustrated and would love some active help, I just can't find the right threads/posts/ect.
Thank you kindly for any advice.. I love my S4 and have been using PA, PAC, CM and other ROMS since the day I got it - I need that back! TouchWiz is just... I just don't like it.
Try this one.
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
FernBch said:
Try this one.
link
Click to expand...
Click to collapse
Thanks for the original stock.. sadly I am still ending up with the Android System Recovery and despite installing CWM Recovery, I just can't get to it. I also still get the ridiculous Factory Mode popup.
Any ideas? I'm so sad :'(
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
FernBch said:
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
Click to expand...
Click to collapse
Thanks for the effort but I'm well aware of that. As I said in the OP, I've been using custom ROMs on this since day one - the issue is that I cannot boot into CMW Recover, despite having a successful install via the app.
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
877
FernBch said:
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
Click to expand...
Click to collapse
I'm using ROM Manager but it won't work. I'd love to try ODIN flashing the CWM Recovery if you have the file for my MDK build.
I may have it on my PC at home. When I get there (60-90 min) I'll look. If I do I'll post up to Dropbox and give you a link.
Ok, I've searched my HDD and I don't have the CWM file. What I do have is the MDK all-in-one root+recovery tool for the I545. I can put it up and upload it if the file isn't too large but I don't know if that'll help you.
CWM 6.0.5.0 flashable zip is in the CM11 thread but I don't know if the recovery image in the file is good for you, either
Just use Flashify to get TWRP
joshm.1219 said:
Just use Flashify to get TWRP
Click to expand...
Click to collapse
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
voice.lex said:
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
Click to expand...
Click to collapse
As far as I know, the latest CWM doesn't work on our devices.
joshm.1219 said:
As far as I know, the latest CWM doesn't work on our devices.
Click to expand...
Click to collapse
Well, that explains it - Thank you so much!
voice.lex said:
Well, that explains it - Thank you so much!
Click to expand...
Click to collapse
No problem :thumb:
This thread might be dead, but rather than starting a new one for what is probably a stupid question, I'll ask it here and see what happens. I've been having major trouble flashing any 5.0 rom on my MDK VZW S4....Seems like every ROM fails when flashing. I have a feeling my issue is an outdated version of TWRP (2.5.0.2), but I am very hesitant to update because it seems like everyone has been having issues with 2.8.1.0. With this being said, are you guys currently running the most current version of TWRP and would you mind advising which .img file worked via Flashify? Not sure whether to use the jfltexxx or jfltevzw...or if it even matters.
I'm sure I've left out pertinent information, but let me know what I'm missing and I'll update accordingly.
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
760hacker said:
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
Click to expand...
Click to collapse
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
swh969 said:
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
Click to expand...
Click to collapse
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
760hacker said:
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm going to give it a shot! Thanks again for your help.
Worked like a charm. Thanks @760hacker
Downloads:
- G900P_PCA_Stock_Deodexed_Rooted_ROM.zip
- G900P_PCA_Stock_Modem+Bootloader.tar.md5 (Required!)
- G900P_PCA_Stock_Recovery.tar.md5 (Optional)
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Flash with TWRP.
3. Completely turn off device (important!) then boot into Download Mode and Odin flash the Modem and Bootloader. The ROM will not boot without them!
4. After a reboot the device will remain on the Sprint splash screen for 10 - 15 minutes before completely rebooting.
Tip: For faster speed turn off animations from Developer Options!
Optional:
- G900P_PCA_Batch_Debloater (Customizable)
Kernel:
- Stock kernel with chainfire's sepolicy patch and BETA SuperSu v2.74.
Notes:
- Your knox warranty bit will be tripped!
- No need to wipe prior to flashing, the ROM will automatically wipe system and userdata.
Thanks for making this dude! Any bugs you know of?
Thanks man! I've been waiting for something like this that makes the update worth trying. Can't wait to update after work.
chippinganimal said:
Thanks for making this dude! Any bugs you know of?
Click to expand...
Click to collapse
It's untouched stock, other than deodexed and root, so it should be solid.
@muniz_ri I'm happy to meet you on the s5. I'm grateful
Is the SD Card corrupted issue fixed and if so how did you do it?
pyromayniyak said:
Is the SD Card corrupted issue fixed and if so how did you do it?
Click to expand...
Click to collapse
That issue was only in the other rom by @malbert16442. This one is workjng fine.
can i go from stock rooted NK4 directly to this? is a factory reset required (or just "highly recommended")?
dmolavi said:
can i go from stock rooted NK4 directly to this? is a factory reset required (or just "highly recommended")?
Click to expand...
Click to collapse
I would recommend reseting unless your flashing a rom on the same android version.
chippinganimal said:
I would recommend reseting unless your flashing a rom on the same android version.
Click to expand...
Click to collapse
Thanks....will do. But no problems going from NK4 to PCA? Will backups from Titanium work across from 4.4.4 to 6.0.1?
dmolavi said:
Thanks....will do. But no problems going from NK4 to PCA? Will backups from Titanium work across from 4.4.4 to 6.0.1?
Click to expand...
Click to collapse
Yeah there should be no issues as long as you follw the instructions in the OP. Sorry but i dont really have experiece with using titanium backup, so i wouldnt know how that would work...
Copy that. Fingers crossed (and nandroid backup, here i come)
dmolavi said:
Copy that. Fingers crossed (and nandroid backup, here i come)
Click to expand...
Click to collapse
Your only issue maybe Applications versions. You are jumping from KK to MM. Download the newest Apps and restore only Data.
Sent from my SM-G900P using Tapatalk
hmmm i'm getting a corrupt zip file notice in TWRP when trying to flash this from internal memory.
dmolavi said:
hmmm i'm getting a corrupt zip file notice in TWRP when trying to flash this from internal memory.
Click to expand...
Click to collapse
booted up for me, at the setup screen now. Try redownloading it... maybe a corrupt download
---------- Post added at 11:56 PM ---------- Previous post was at 11:55 PM ----------
@muniz_ri maybe you could create another version of the rom that is more debloated of most of the sprint crap that is preinstalled other than that thanks for making this rom bro!
I tried 4 different downloads. Does it need to be in the root of the internal memory? Or renamed? It keeps saying it's failing validation...twrp 3.0.2.0.
dmolavi said:
I tried 4 different downloads. Does it need to be in the root of the internal memory? Or renamed? It keeps saying it's failing validation...twrp 3.0.2.0.
Click to expand...
Click to collapse
i just downloaded it through the internet app on my phone which placed it in the downloads folder and flashed twrp, same version you are running, wiped everything, and selected the zip, and it installed. I dunno whats going on with your phone though :/
chippinganimal said:
i just downloaded it through the internet app on my phone which placed it in the downloads folder and flashed twrp, same version you are running, wiped everything, and selected the zip, and it installed. I dunno whats going on with your phone though :/
Click to expand...
Click to collapse
I didn't do a wipe...but that shouldn't impact the validation.
Will not load into Odin after flashing...
Downloaded, flashed, and tried to Odin the bootloader and modem, but phone will not be recognized by Odin. Sugesstions?
what slot do i put the modem/bootloader in? BL or CP? and do i need to get rid of the .md5 extension first?
Edit - put it in BL, odin said pass. Now i'm sitting at the "Sprint" (white background) splash screen. I'll let it simmer for a while. Fingers crossed again
Edit 2 - Hot sh!t...I'm up and running. 10 minutes on the Sprint splash screen. Now to redownload my apps and restore all the data. Ten thumbs up