Related
Ok so I got my AT&T S4 successfully rooted using the guide I found on here that uses the Motochopper tool. Root Checker verified I am indeed rooted. But that's it. I'm only rooted to the stock ROM. Nothing custom. Now how to I go about getting a CWM recovery thing on my phone, while still maintaining the stock ROM?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
On the play store, download goo manager (for twrp) or rom manager (for cwm) to install a custom recovery. Don't use either app to do anything but just install the recovery. Once it's installed, boot into recovery and make a backup, even if you're planning on staying stock. Cheers
Step 1. Go to the development forum and read about how to do it.
Step 2. Know how to do it.
Step 3. Do it.
I need more basic. I mean I know CWM means ClockWorkMod, but I don't know what that means. I also know that CWM is more popular than TWRP (I don't know what TWRP stands for) because the rom manager app has tons more downloads in the play store than the goo one does. What is a recovery mode and why do you need one? I mean if I screw up I can just use Odin to flash the AT&T stock ROM back. I wish someone would post a link to a ROMS for Dummies page.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
If I were you I'd be happy that your rooted and now find out what that means to you and what you want to do with a rooted phone. You don't need a custom recovery if all you're interested in is being rooted. And if you mess up, Odin back to stock may not be an option. You may permanently hard brick your phone. So really decide what you want to do with the phone before you proceed any further.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
feetr2c said:
I need more basic. I mean I know CWM means ClockWorkMod, but I don't know what that means. I also know that CWM is more popular than TWRP (I don't know what TWRP stands for) because the rom manager app has tons more downloads in the play store than the goo one does. What is a recovery mode and why do you need one? I mean if I screw up I can just use Odin to flash the AT&T stock ROM back. I wish someone would post a link to a ROMS for Dummies page.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
you really should have read and understood this first: http://forum.xda-developers.com/showthread.php?t=2301762
These guys are correct and trying to help you avoid a brick. If you are not aware of the basics start reading. Even if you are experienced at flashing on another device.
I had extensive experience on HTC phones and feel like a noob here, but getting better. But I have read over a thousand posts, at least, and dozens of how to videos since early may. And only feel comfortable now to flash a custom rom. Not ready yet as phone stock is pretty good for me atm. And would prefer an unlocked bootloader first. I only rooted and flashed a recovery about a week ago. May be a little slower than some, but never got into a problem I couldn't get out of on my HTC phones using the same learning process.
If you come back with specific questions where they know you have researched things they will gladly help. Googling some of the terminology is a good idea too. Had to do that when I first started flashing roms. A different language for sure.
Good luck and enjoy the phone and the rooted world.
In my experience with the S4 CWM does not work as well as TWRP. I had many issues installing a few custom ROMS with CWM, but as soon as i loaded TWRP those ROMS which wouldn't install would install properly. TWRP also was able to read my ext SD when it was formatted in exFat.
As you can see my dates are a bit off. Ive done some searching and found others who have had the same issue. No definite solutions or explanations have been provided. This is super frustrating. Not sure why its happening or how to fix it. Im running the latest twrp, before that I was running cwm with the same results. I just did a backup about an hour ago and i couldnt tell you which one it is. Any help would be much appreciated.
Idk it was like this on the sprint gs3 also with twrp. So I just name the backups myself with the date I backed up.
Sent from my SPH-L720 using Tapatalk 4 Beta
The TWRP source is messed up and no one cares to dig in and fix it. Just manually name your backups.
I'm using philztouch and have not noticed the problem. Also a cool feature of that recovery is that it says what rom it is in the title, so even if the date happens to be off, the file name will give away what backup it is.
Sent from my SPH-L720 using xda premium
That has been an issue for over a year I believe. All CWM and TWRP versions that I am aware of have it. One of the Android updates broke the date function from what I recall. Might have been Jellybean. Since you can just rename the backups to whatever you want I guess the priority is at the very bottom of the list.
Sent from my SPH-L720 using Tapatalk 4 Beta
I use twrp 2.5.0.2 on this device and do all my nands to external and name them what they are.
Sent from my SPH-L720 using xda premium
Much appreciated fellas!
Sent from my Nexus 7 using Tapatalk HD
try this
BiffTirkle said:
As you can see my dates are a bit off. Ive done some searching and found others who have had the same issue. No definite solutions or explanations have been provided. This is super frustrating. Not sure why its happening or how to fix it. Im running the latest twrp, before that I was running cwm with the same results. I just did a backup about an hour ago and i couldnt tell you which one it is. Any help would be much appreciated.
Click to expand...
Click to collapse
Try Dream TWRP I installed it and my BU dates have been correct.
Yeah. Some have said there's a setting that you can change to fix that. I've yet to find it.
I've been reading through other threads here on XDA about a common boot loop issue that N900T users are experiencing, but nowhere was it mentioned that the Canadian variant users had a similar problem, but I do.
I was wondering if there were any other SM-N90028 users out there that were stuck in a boot loop?
Here is my situation:
I have a Canadian SM-N900W8 (it is, also a Qualcomm LTE version) and I'm in a boot loop... it all started when I tried to restore a Stock-Rooted Rom with TWRP.
I can't, however get it out, and I've tried all of the versions of TWRP, I've also used odin like 30 times... nothing.
I successfully restored a Rooted stock ROM through TWRP, but it wasn't until I re-installed a factory un-rooted one that things got ugly..
So I was thinking about this and perhaps the cause of this is KNOX... since the first thing I did when I rooted my phone initially was uninstall KNOX and all of its files. I know these didn't carry over when I did a TWRP backup, which is perhaps why my restore of that backup worked the first time. The second time, I just went and downloaded everything stock and used Odin, and that's when the bootloop occurred.
if anyone knows of a way to solve this, I'd be forever grateful!
I really hope I will be able to fix this...
Not to sound.to xdaish...but dude seriously this topic.is all.over the n3 forums. Have a.look and you will find tons of info.
Also...good idea to.read prior to flashing..if you had you would have know not to restore with twrp since it causes bootloops.
Just trying to you some friendly advice.
Sent from my SM-N900W8 using xda premium
force70 said:
Not to sound.to xdaish...but dude seriously this topic.is all.over the n3 forums. Have a.look and you will find tons of info.
Also...good idea to.read prior to flashing..if you had you would have know not to restore with twrp since it causes bootloops.
Just trying to you some friendly advice.
Sent from my SM-N900W8 using xda premium
Click to expand...
Click to collapse
Thank you, but I've read them all and most are regarding the n900t, I felt it appropriate to ask about the n900w8 variant.
Also, I know that would have been better, but it's too late for that now. I just thought I'd share my experiences here with this issue so that others will know better.
So I tried a different stock ROM, and with the latest version of Odin, but it still is in a boot loop.
However there is one difference; this time it will boot past the Samsung logo and into android, but then a window will pop up saying "Process system isn't responding" and ask me to wait for it to respond or close it. Regardless of what I select, it will end up rebooting seconds later.
In the very short time that everything stays booted for, I can access the two pull-down menus from the top, but selecting anything will yield me no results.
Perhaps this can tell us more about this issue?
Did you have a read.through this....a few.guys have revived their n900w8s here
http://forum.xda-developers.com/showthread.php?p=46450690
Sent from my SM-N900W8 using xda premium
force70 said:
Did you have a read.through this....a few.guys have revived their n900w8s here
http://forum.xda-developers.com/showthread.php?p=46450690
Sent from my SM-N900W8 using xda premium
Click to expand...
Click to collapse
Thanks! I checked it out and my phone is already set to those settings, so it didn't work, but I'm still trying!
c_est_la_vie said:
Thanks! I checked it out and my phone is already set to those settings, so it didn't work, but I'm still trying!
Click to expand...
Click to collapse
Check post #350 in this thread and read forward. http://forum.xda-developers.com/showthread.php?t=2467001&page=46
this worked!
Hey guys, I'm not sure if anyone's checked this out yet, but I managed to get myself out of the boot loop!
here is the solution:
http://forum.xda-developers.com/showthread.php?t=2471421
Glad your back up and running!
Sent from my SM-N900W8 using xda premium
Thanks!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Has anyone been able to successfully flash OctOS with CWM? I know in the thread they say they only support TWRP but I would really prefer not to switch to that recovery if possible. I've tried 4 seperate times now and every time it doesn't even make it to the boot animation, it just hangs at the galaxy s4 screen and I eventually have to reboot and restore. And yes, I give it enough time, I let it sit on that screen for about 20 mins before I reboot and try again.
P0stM0rtal said:
Has anyone been able to successfully flash OctOS with CWM? I know in the thread they say they only support TWRP but I would really prefer not to switch to that recovery if possible. I've tried 4 seperate times now and every time it doesn't even make it to the boot animation, it just hangs at the galaxy s4 screen and I eventually have to reboot and restore. And yes, I give it enough time, I let it sit on that screen for about 20 mins before I reboot and try again.
Click to expand...
Click to collapse
I have flashed OctOS numerous times with CWM. what version of OctOS? I am using 10/22 currently because of issues with the 10/31. Did you check the MD5 hash? Might be a bad download. I hope you can get it running. You will not be disappointed, it really is the best AOSP going right now. Good luck!
Sent from my SPH-L720 using Tapatalk
Interesting, I was trying the 10/31 build, I'll go dl the 10/22 build now and give it a shot. And yes, I checked the md5's and they were correct, that was one of the first things I did. Thanks for the suggestion, I hope it works, really wanna check out this ROM.
edit: Also, what cwm are you using? Touch or regular?
I was using regular 6.0.3.0 I think. I am trying TWRP right now since I took the plunge to MJA. I am thinking about going back to CWM probably the touch version. It really turned me off to TWRP when the first backup I made with it failed to restore. I have never had backup/restore issues with CWM.
Sent from my SPH-L720 using Tapatalk
Yea that's why I don't really wanna use TWRP if I don't have too, I've heard of people having issues with it and I've never had problems with CWM, been using it for a long time now. I'm also thinking about upgrading to CWM Touch, but for now, the dl just finished so I'm gonna try flashing the 10/22 version. Here goes nothing!
Highway 55 said:
I have flashed OctOS numerous times with CWM. what version of OctOS? I am using 10/22 currently because of issues with the 10/31. Did you check the MD5 hash? Might be a bad download. I hope you can get it running. You will not be disappointed, it really is the best AOSP going right now. Good luck!
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Mind leading me to it? 0.0
Sent from my SPH-L720 using XDA Premium 4 mobile app
Jellybeanteeker said:
Mind leading me to it? 0.0
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=46113397
It's in the Verizon forums. Don't worry it is for sprint as well. It is one aroma package that supports every carrier.
Sent from my SPH-L720 using Tapatalk
Awesome, got it up and running and so far I'm liking what I see. Gonna run it through the paces over the next couple days and see how it goes. Thanks again for the help, much appreciated!
I was able to install with TWRP 2.5.0.2
Sent from my SPH-L720 using Tapatalk
Hey guys just thought is let you know cm11 nearly bricked my phone, the update downloads fine and restarts but fails half way through install. Unfortunately I didn't write theberror code down as I was concentrating on getting it all running. The dates of the nightlies were the 14th and 16th on my i9300 rooted using clockworkmod recovery. I tried also downloading the 16th nightly with my PC and transferring it. Same result. Ended up with bootloop and even Odin failed several times. Ended up working after try 4
Note if you want to flash firmware its your risk and the risk gets higher if you don't read .
This is a developers forum and we all accept the risk of a brick.
Without the error we can't say for certain what the issue is, you are sure the rom was for the i9300 and not another device weren't you?
No problem here
I flashed both 14th and 16th nightly and did not have any kind of installation problem. All worked fine. Are you sure you are using latest recovery? (CWM 6.0.4.3+ are ok, don't know for older versions)
Was close to sending my phone into repair as well.
Installed CM11, GoogyMax kernel and Gapps package, phone froze on entering sim unlock code.
Afterwards my PIT/partition table was corrupted, no way of reflashing using Odin.
I've tried Kies as my last resort and luckily the emergency recovery fixed my phone.
Awful feeling, have never been as close to 'bricking' my phone :\
Been running CM11 nightly since start of December without issue. Check your CWM version before flashing.
Sent from my GT-I9300 using Tapatalk
That's a typical case of PEBCAK. Bricking a phone with CM is nearly impossible(chance is probably lower than using odin to flash stock), but there are always people that can do that. Good job.
Moster2 said:
That's a typical case of PEBCAK. Bricking a phone with CM is nearly impossible(chance is probably lower than using odin to flash stock), but there are always people that can do that. Good job.
Click to expand...
Click to collapse
It's not like I've never flashed stuff before, I'm doing things like this regularly since the days of my good old SGS1.
I've never encountered such a thing and I also didn't say it was CM11's fault. CM10 has been installed for months on my phone, flashing dailys when they came out - and I never had any problems even remotely similar to this.
I'm not sure how it's even possible for the partition table to gay haywire shortly after booting up but that's what happened. For me the problem seems to be related to Googymax, as I've been booting fine without and had problems after changing the kernel.
Cy4n1d3 said:
It's not like I've never flashed stuff before, I'm doing things like this regularly since the days of my good old SGS1.
I've never encountered such a thing and I also didn't say it was CM11's fault. CM10 has been installed for months on my phone, flashing dailys when they came out - and I never had any problems even remotely similar to this.
I'm not sure how it's even possible for the partition table to gay haywire shortly after booting up but that's what happened. For me the problem seems to be related to Googymax, as I've been booting fine without and had problems after changing the kernel.
Click to expand...
Click to collapse
I wasnt refering to you. You seem to have knowledge about the stuff and fixed it, but to the guy in the first post. Opens a thread, useless and wrong section, no error message etc. He just more or less rants about his failure
Sent from my GT-I9300 using XDA Premium 4 mobile app
Alright, must have misinterpreted your post then
In the OPs' case, it seems like there was something wrong with his recovery, as others have already hinted.
TWRP 2.6.3.0 was giving me similar problems, 2.6.3.1 fixed those for me.
Really, pathetic thread.
Checking md5sum of downloaded zip, few simple adb and standardblinux command like ls, flashing newer and/or other recovery, and the most important; understand what being read, will never brick your phone. Even if it did, softbrick is child's play.
Sent from my GT-I9300 using xda app-developers app
I using CM11 since the first Version with no real Problems.
Gesendet von meinem GT-I9300 mit Tapatalk 2
This should be closed. We know the risks.
Threads like this just put new android flashers off flashing customs roms because of someones bad experience.
Sent from my GT-I9300 using xda app-developers app