ClockworkMod ROM Manager now supports Verizon S4 - Verizon Samsung Galaxy S 4

Just thought I'd let you all know. It's an old dog new tricks thing but I'm more comfortable with Koush.
6.0.3.2 both versions.
http://www.clockworkmod.com/rommanager

I saw this and was excited to see it since CWM/Rom Manager is what I am most comfortable with. The only concern I have is the "loki" issue that is used to get past the locked boot loader since they don't really say thet are using the loki method or not. Just wondering what the status of that is.
Also still squimish about flashing custom roms since my first try on this phone lead to a soft brick "custom unlocked" screen when i used TWRP.

They are using Loki.
Sent from my SCH-I545 using xda app-developers app

I just attempted this from my rooted s4 which had twrp on it.. and it worked!!! YAY!!

nice

Its awesome this is available for the S4 now. Always great to have options, but I think I will stick with TWRP for now. :fingers-crossed:

It's been so long since I have used CWM I don't know what the interface looks like now, lol. TWRP got so far ahead of them interface wise there was never a reason to go back on any of my other devices (TBolt, N7, KF). I may try it now just to try it. Plus I guess ROM control has a poor man's version of 4EXT's kernel control if I am not mistaken.

worked like a champ for me

Going to be tough to leave twrp
Sent from my SCH-I545 using Tapatalk 2

twp works with my 64gb microsd where cw I would have had to format to a fat32. Sticking with twp for sure.

balaams_ass said:
Just thought I'd let you all know. It's an old dog new tricks thing but I'm more comfortable with Koush.
6.0.3.2 both versions.
http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
How are you guys installing the touch .IMG? I assume we can't boot fastboot and install from there..
Sent from my SCH-I545 using xda premium

zeroxg4 said:
How are you guys installing the touch .IMG? I assume we can't boot fastboot and install from there..
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
You install it from within ROM manager...it's an in app purchase
Sent from my Nexus 7 using xda premium

brizey said:
You install it from within ROM manager...it's an in app purchase
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Its offered as either and in app purchase or download from the link / post that I quoted...
Sent from my SCH-I545 using xda premium

Is that the same one as the in app purchase?
Sent from my SCH-I545 using Tapatalk 2

I had to leave twrp, I rebooted into recovery from touchwiz to install beans2 and I went into a boot loop. I made a backup, wiped everything and the install failed. So I tried to restore my backup and that failed. So I tried another backup and that too failed. I ended up having to Odin to stock so I installed CWR and so far so good. It was weird. I've been flashing since the of droid and I've had 15 different android phones since then and I've never had that happen. Oh well, I had titanium backups of everything and a backup of all mg text so I'm good now....
Sent from my SCH-I545 using Tapatalk 2

smalltownbird said:
I had to leave twrp, I rebooted into recovery from touchwiz to install beans2 and I went into a boot loop. I made a backup, wiped everything and the install failed. So I tried to restore my backup and that failed. So I tried another backup and that too failed. I ended up having to Odin to stock so I installed CWR and so far so good. It was weird. I've been flashing since the of droid and I've had 15 different android phones since then and I've never had that happen. Oh well, I had titanium backups of everything and a backup of all mg text so I'm good now....
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I played out this almost IDENTICAL SCENARIO Friday on my S4 using TWRP. searching forums while trying to get back up and running led me to believe that TW had some issues in this regard....
Went to CWM and have been flashing without problem since. It's a shame, the interface on TW was STELLAR....

bkrickles said:
Is that the same one as the in app purchase?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Yeah

I've just read somewhere in the last day or so that there was an issue with TWRP 2.5.0.3. that was causing issues. They were saying to go back to 2.5.0.2. and that will fix any issues you are having. I didn't update to .3, been on .2 since root & LOKI bypass without any problems at all. Just thought I'd throw that out there for anyone who hasn't heard about it.
Sent from my SCH-I545 using xda app-developers app

gsxcorey said:
twp works with my 64gb microsd where cw I would have had to format to a fat32. Sticking with twp for sure.
Click to expand...
Click to collapse
In the change log for version 2.4.4.0 it says "Update exFAT to latest commits". Does this mean you can Backup to extFat 64GB MicroSDXC memory cards?

DarkMenace said:
In the change log for version 2.4.4.0 it says "Update exFAT to latest commits". Does this mean you can Backup to extFat 64GB MicroSDXC memory cards?
Click to expand...
Click to collapse
I think so...not sure how they got the proprietary binaries.
You can use 64 GB cards in CWM if you format to fat32. I just formatted my card to fat32 and rest easy that pretty much anything ever made can read it.
Everyone has this thing where fat32 can't do 64 GB cards and that is simply not true. Windows won't do it natively but there are other format tools that will. The 32 in fat32 is not 32 GB, its 32 bits as in able to address 4 GB. So files are limited to 4 GB. That's why all the recoveries are breaking up the big repositories into volumes, so they don't exceed 4 GB. That 4 GB limitation is an issue for recording HD video...and that's about it.
edit: by the way, not saying you did not realize that...I got your question...just wanted to get that out there.

Related

[Q] How to get CM7 running on SGS

I can't seem to flash CM7 on my Fascinate. I've downloaded the right recovery, and wiped data and dalvik, but it keeps looping to a new recovery screen and getting stuck at "waiting for SD card to mount" and counts down then reboots and tries it again. I've odined several times back to stock but to no avail.
time for a new sd card...class 6 or higher preferably.
droidstyle said:
time for a new sd card...class 6 or higher preferably.
Click to expand...
Click to collapse
Lol I'm using a class 10
Sent from my SCH-I500 using Tapatalk 2
swbf2lord said:
Lol I'm using a class 10
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
LOL... if you would post more information with your questions then you would get better answers
fwiw you dont need to wipe dalvik if you wipe data...the data wipe does all three
also sometimes you need to flash cm7 twice for it to stick
and there is a guide in the general section for flashing instructions...refer to section 3
droidstyle said:
LOL... if you would post more information with your questions then you would get better answers
fwiw you dont need to wipe dalvik if you wipe data...the data wipe does all three
also sometimes you need to flash cm7 twice for it to stick
and there is a guide in the general section for flashing instructions...refer to section 3
Click to expand...
Click to collapse
Honestly I didn't think it was important. I can't flash it twice though because it automatically goes to the boot logo after I flash.
Sent from my SCH-I500 using Tapatalk 2
swbf2lord said:
Honestly I didn't think it was important. I can't flash it twice though because it automatically goes to the boot logo after I flash.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
cm7 has known to be finicky with certain sd cards. Normally anything class 6 or higher has no known issues, but that does not mean much. Fwiw I had a stock 16gb that always gave me fits trying to flash cm7...Sometimes it would take 15 tries before it would boot up.
You might try reformatting the sdcard or swapping in a different one aswell.
droidstyle said:
cm7 has known to be finicky with certain sd cards. Normally anything class 6 or higher has no known issues, but that does not mean much. Fwiw I had a stock 16gb that always gave me fits trying to flash cm7...Sometimes it would take 15 tries before it would boot up.
You might try reformatting the sdcard or swapping in a different one aswell.
Click to expand...
Click to collapse
Okay, thanks, I'll try another one
Argh! I got it to flash CM7, and it goes to the Cyanogenmod Galaxy S screen, but then it loops to the SD card screen, and says something about a file not being found, reboots, then starts the process all over again.
I also could not get CM7 to flash. I would restore to stock if I were you. And format SD card.
MultipleMonomials said:
I also could not get CM7 to flash. I would restore to stock if I were you. And format SD card.
Click to expand...
Click to collapse
I did both, even tried a new sd
Sent from my SCH-I500 using Tapatalk 2
did you try flashing THS build 1?
MultipleMonomials said:
did you try flashing THS build 1?
Click to expand...
Click to collapse
For CM7? No. Can you link me?
Sent from my SCH-I500 using Tapatalk 2
It may make no difference, but I've had various makes of microsd cards over the years and have had issues with all of some kind. Bought a Samsung class 6 16gb and have had zero, absolutely zero issues.
Look in Droidstyle's guide.
I can't seem to find it.
EDIT: Nvm, I found it, but the THS build isn't for CM7 according to the guide.
No, THS is a CM9 build. I would go with CM9 as I have had far fewer problems with it and ICS is better in general.
MultipleMonomials said:
No, THS is a CM9 build. I would go with CM9 as I have had far fewer problems with it and ICS is better in general.
Click to expand...
Click to collapse
Yeah I'm running AOKP right now. I want to run CM7 though, not ICS. That's the whole point of the thread.
Sent from my SCH-I500 using Tapatalk 2
Oh. Sorry. I thought you were coming from stock.
MultipleMonomials said:
Oh. Sorry. I thought you were coming from stock.
Click to expand...
Click to collapse
It's okay, thanks though.
Sent from my SCH-I500 using Tapatalk 2

Clockwork Recovery not reading new 32GB microSD

I just bought a new 32GB MicroSD from Amazon. I format using Cloockwork recovery. After copying all my ROM's to the SD card everytime I try to flash a ROM it always say "no files found". All other app can read my microsd except clockwork recovery.
I am currently using Team Objection UCLE5 (If it matters)
ClockworkMod Recovery 5.8.4.8
Thanks
I just updated the same version of CWM that you did with the same results so that you know you are not alone my friend Hopefully, we can get this sorted out soon. I was stock rooted when I noticed the issue.
Its this version of CWM...
It will only see your internal SD.
PITA.
so your card is fine.
Yup, happened to me last night. There's something wrong with the newest CWM Recovery, but as soon as I flashed the Touch CWM everything was back to normal.:good:
Thank you all. i will try the new touch recovery.
Sent from my Note using Tapatalk 2
ceqman said:
Thank you all. i will try the new touch recovery.
Sent from my Note using Tapatalk 2
Click to expand...
Click to collapse
I bought the Touch Recovery using in App purchase in ROM Manager. Everything is running great. Do not mind paying some money for a great app. Thank you all:good:

i forgot to flash the GB bootloader

when i was doing my things in odin i forgot to flash the GBBootloaders.tar but CWM and Helly Bean flashed just fine. Am i going to need it? Should i flash it? Will flashing it cause a data wipe or bootloop?
skepticmisfit said:
when i was doing my things in odin i forgot to flash the GBBootloaders.tar but CWM and Helly Bean flashed just fine. Am i going to need it? Should i flash it? Will flashing it cause a data wipe or bootloop?
Click to expand...
Click to collapse
Sure u can do it now, should not cause any problems,,, no it won't wipe any data as far as i know.
hhp_211 said:
Sure u can do it now, should not cause any problems,,, no it won't wipe any data as far as i know.
Click to expand...
Click to collapse
but do i really need it?
skepticmisfit said:
but do i really need it?
Click to expand...
Click to collapse
Yes
BL - Bootloader - a.k.a. Boot Loader - This is the rudimentary software that kicks in when a phone is first powered up. Its only real goal is to get the operating system up and running. Some phones, like those from Motorola, have a "locked" bootloader, making it more difficult to use custom kernels. The Fascinate's bootloader was never locked. Here's where it gets complicated: bootloaders are broken down by Android version. There are Eclair bootloaders, Froyo bootloaders, and GB bootloaders. Just being on one version of Android, though, does not mean that you have the corresponding bootloader. It seems that stock Gingerbread phones don't use a Gingerbread bootloader. In fact, to put a GB bootloader on your phone (highly recommended for modern ROMs) you will need to flash a GB bootloader file.
skepticmisfit said:
but do i really need it?
Click to expand...
Click to collapse
These guys may know more than I do. But I've had my fascinates since we got the gingerbread OTA. And ive never flashed bootloader to it. I've been on damn near every android version except 4.3 and never had any issues
Sent from my VS920 4G using Tapatalk
bones420la said:
These guys may know more than I do. But I've had my fascinates since we got the gingerbread OTA. And ive never flashed bootloader to it. I've been on damn near every android version except 4.3 and never had any issues
Sent from my VS920 4G using Tapatalk
Click to expand...
Click to collapse
i ended up doing it. the only difference is the second boot logo shows up (the one after the first samsung logo).
my verdict is, if you forget to flash it initially with JT's CWM, you should be fine. flash it with JT's CWM image for best results.
I'm happy with my setup. Geewiz runs beautiful for me. Would love to try 4.3 but SD card won't let me. Just flashed bootloader on my bad cracked fassy and still no luck with the SD card. So. Its useless for me
Sent from my VS920 4G using Tapatalk
bones420la said:
I'm happy with my setup. Geewiz runs beautiful for me. Would love to try 4.3 but SD card won't let me. Just flashed bootloader on my bad cracked fassy and still no luck with the SD card. So. Its useless for me
Sent from my VS920 4G using Tapatalk
Click to expand...
Click to collapse
what kind of SD card is it?
Sandisk 16gb class 4. I've formatted it every way possible. And any mtd ROM puts me in a recovery loop. "Waiting for SD to mount"
Sent from my VS920 4G using Tapatalk
bones420la said:
Sandisk 16gb class 4. I've formatted it every way possible. And any mtd ROM puts me in a recovery loop. "Waiting for SD to mount"
Sent from my VS920 4G using Tapatalk
Click to expand...
Click to collapse
you tried a different SD card to make sure it's not the phone?
Yeah stock Samsung 16gb worked perfect. But someone stole it out my spare phone.
Sent from my VS920 4G using Tapatalk
---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------
I've got 3 of the 16gb class 4 sandisks. And they all do the same. Unfortunately I believe its a fascinate problem. All the cards work perfect in lg spectrum, droid eris, and HTC touch pro 2 with nand android
Sent from my VS920 4G using Tapatalk

[Q] Internal bug or Hardware issue

So the problem started when I flashed a 4.3 rom last friday. I formatted my internal memory in recovery mode because for some reason I only had 4 gigs of space and had moved everything over to the sd card. Once that was done phone said like 8 gigs available and thought everything was fixed. Well now if I turn off my phone it gets stuck in some kind of bootloop but it's not looping. It's just sits at the Samsung unlock symbol and custom screen. Doesn't loop just sits there. So one day I decided to format the internal memory again and the phone boots up like normal, but I can't power off the phone without going into recovery and formatting the internal memory every time. Any ideas on what is causing it or how I can make the Samsung custom boot stock instead so I can send it out.
I also have tried flashing another 4.3 rom and it doesn't seem to go away either.
I'm not an expert on how they have to make this stuff work with the mdk bootloader but I'm sure it's not hardware related. Have you tried flashing back to a 4.2 rom?
Sent from my SCH-I545 using Tapatalk 2
Downloading one now hopefully it will fix it.
Which recovery are you using? Make sure to wipe data, cache, and dalvik 3x each, then flash your rom
Sent from my SCH-I545 using Tapatalk 2
TWRP and I flashed hyperdrive still no luck still freezing in the same spot and have to actually format to get past it.
Anyone else have any idea on what else I can try?
BlackDynomitr said:
Anyone else have any idea on what else I can try?
Click to expand...
Click to collapse
What version of TWRP are you using?
Sent from my SCH-I545 using Tapatalk
I believe 2.5 I'm guessing only way to check is to go into recovery again.
BlackDynomitr said:
I believe 2.5 I'm guessing only way to check is to go into recovery again.
Click to expand...
Click to collapse
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
​
heath2805 said:
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
BlackDynomitr said:
​
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
Click to expand...
Click to collapse
Well if it doesn't turn on after flashing stock firmware via Odin, you'll know its a hardware issue with it and your warranty should cover a new replacement.
Sent from my SCH-I545 using Tapatalk
I had this issue when I first got my phone. I bought it off Swappa, it was already running TWRP 2.5.0.2, giving me nothing but problems. I switch to Philz Touch and no longer have the issue.

What are my options for booting multiple rom slots like safestrap on a mdk build with

Can I use safestrap even though I have unlocked bootloader?
Sent from my SCH-I545 using Tapatalk
bart77 said:
Can I use safestrap even though I have unlocked bootloader?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Just store different ROMs on an Sd card and make nandroid backups and flash at will.
Why even bother with Safestrap??
I have a daily driver that is ~4gig for system and data partition. Do you know how long it takes to back that up and restore every time I want to try a different rom? With safestrap slots it's a matter of seconds to boot a second slot.
Sent from my SCH-I545 using Tapatalk
bart77 said:
I have a daily driver that is ~4gig for system and data partition. Do you know how long it takes to back that up and restore every time I want to try a different rom? With safestrap slots it's a matter of seconds to boot a second slot.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yea but what you gain in speed you lose in space. Nothing is free.
But to specifically answer your original question. I don't know.
I'd imagine you'd have to have multi boot but I think that would require a fully unlocked bootloader
Your best bet to gain more space on the 2nd and 3rd slot is to not download any apps on the stock slot. I had a problem with running out of space before.
Sent from my SCH-I545 using XDA Premium 4 mobile app
bart77 said:
Can I use safestrap even though I have unlocked bootloader?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I wouldn't see why you couldn't use it. Make a nandroid of your current rom, and try it. Worst case scenario, you have to Odin back to mdk. The only thing I would do is make sure your running the right SS for the android version your running. it's pretty nice having a dual boot phone. I think how it would work is your stock rom would be the custom rom you flashed in your custom recovery. Then SS would work off that rom. Be careful though, as I really do believe you won't have any issues because it doesn't touch your bootloader, I could be wrong....
Sent from my SCH-I545 using Tapatalk
Look for an app in the play store. I can't remember the exact name now, but it let you multiboot
Sent from my GT-I9505 using Tapatalk

Categories

Resources