Related
Hi All,
Just got my S2 last week. Planning to move to CM7 this weekend. I have rooted the device and am on the Codeworkx kernel. I had a few questions:
1. Is there a problem while flashing via Odin if Debugging is not enabled (I think it is more of a OS feature which we haven't entered when in download mode, so shouldn't matter according to me.) ? I tried to disable debugging, and then went to download mode and Odin did detect the phone, but I did not try to flash anything so if anyone has tried that, your input is more than welcome.
2. The reason for above question is: What if I completely brick my phone (with debugging disabled) and no ROM .zip in the sd storage, how do I get the phone up and running ? I understand that I can flash kernels via Odin, but is it true for ROMs as well ?
3. What's the issue with ROM manager ? Is it recommended to stay away from it for S2 ? I have tried to do a Nandroid backup and it always takes me to the Android robot with a exclamation mark screen. Then I have to reboot and the backup magically restarts and completes successfully. Most people have suggested to use CWM recovery directly, so not sure if I should get rid of the ROM manager altogether.
That should be all for now. I have a jig ready by the way, so am not that worried about the process and plan to do a fair bit of reading before proceeding, however, the answers to above queries would be really great !
Thanks in advance,
Ish
I can answer some of your doubts.
I don't know if you can flash via odin in case you don't have the usb debuggin enabled so I'm not going to say anything about it.
Anyway if something happens to your phone and you dont have any ROM on your sd card but you have CWM recovery installed (which is almost everytime the case) then in CWM there is a mount usb stoage option. With it you can easily transfer .zip ROM files to flash, or even a nandroid backup you saved in your PC.
ABout ROM manager, this is what I suggest you. The first time you flash CM7 don't use ROM Manager (I even tried using it with the codeworkx kernel with no luck). Now, once you are in CM7 it works perfectly and it's really helpful to flash nightlies withouth wiping data (I flash half the nightlies as they are realeased). So the first time you flash CM7 wipe everything (do a nandroid backup first), even wipe /system, /data, cache partition, dalvik cache, so you don't have any problems. THen install zip from sd card and when it finish install the zip file again (just two installs in a row no wiping in beween, trust me, the first time I tried I didn't do that and couldn't boot the phone).
Hope it helps.
EDIT: You can flash stock ROM via odin, there is a thread by infratech were this is explained and you have a list of downloable stock ROMS you can flash with Odin, these are region and carrier specific and you probably will get the one for your carrier. I found the stock ROM for my carrier and I'm from chile, you shouldn't have any problems with that. Well, good luck, CM7 is by far the best ROM I've flashed.
Oh another thing, go for the latest nightly since the battery life is incredibly improved over the RC (or was it stable?) version.
Thanks !
tomascunill said:
Anyway if something happens to your phone and you dont have any ROM on your sd card but you have CWM recovery installed (which is almost everytime the case) then in CWM there is a mount usb stoage option. With it you can easily transfer .zip ROM files to flash, or even a nandroid backup you saved in your PC.
Click to expand...
Click to collapse
Awesome ! This is exactly what I was looking for. I haven't dived into all the options of the CWM, so didn't know that this feature existed.
Also, many thanks for explaining most of the things in a single concise post, it was very helpful. I'll have to check the ROM flash with Odin, so I will search for that thread and have a go through it later today.
Once I get a hang of CM7, I'll go in for the nightlies as well. And yes, I did read about the CM7 guys revert the status to an RC because of the bugs reported, so will give it a try once I definitely know what I'm getting into .
Thanks again,
Ish.
cheemais said:
Awesome ! This is exactly what I was looking for. I haven't dived into all the options of the CWM, so didn't know that this feature existed.
Also, many thanks for explaining most of the things in a single concise post, it was very helpful. I'll have to check the ROM flash with Odin, so I will search for that thread and have a go through it later today.
Once I get a hang of CM7, I'll go in for the nightlies as well. And yes, I did read about the CM7 guys revert the status to an RC because of the bugs reported, so will give it a try once I definitely know what I'm getting into .
Thanks again,
Ish.
Click to expand...
Click to collapse
Well good luck! Tell me if you get any problem.
Okay. Couple days ago, i got my new Samsung Galaxy S II. Fell in love with it. I previously had a Vibrant, but that met an unfortunate and violent demise. On the vibrant I hadn't been doing anything involving roms and such because i'd tried once, and completely fried the phone. LOL.
I managed to root my phone, and from what I've read, I didn't do the best method. What I did was get an unsecure kernel, and flashed that, then used a 1-click root type thing to root it. So one of my questions is, my clockwork mod isn't working, what's wrong with it? I downloaded ROM Manager, and flashed CWM. But when i reboot into recovery, i get the stock Samsung recovery screen. How can I get this to work?
And another question, is about roms such as Cyanogen mod. I really wanna get it. (I wont until I get CWM working, though.) And I'm just wondering. If I were to just go to ROM Manager, and flash cyanogen, would it work, or do i need to do more to my phone to be able to put on custom roms? I've never understood the concept of roms vs kernels vs firmware vs whatever else.
And if it matters, Samsung Galaxy S II, Android 2.3.3, rooted using SuperOneClick.
P.S Anything else that I should considering doing/putting onto my phone? And thanks in advance for halping.
Gutana said:
Okay. Couple days ago, i got my new Samsung Galaxy S II. Fell in love with it. I previously had a Vibrant, but that met an unfortunate and violent demise. On the vibrant I hadn't been doing anything involving roms and such because i'd tried once, and completely fried the phone. LOL.
I managed to root my phone, and from what I've read, I didn't do the best method. What I did was get an unsecure kernel, and flashed that, then used a 1-click root type thing to root it. So one of my questions is, my clockwork mod isn't working, what's wrong with it? I downloaded ROM Manager, and flashed CWM. But when i reboot into recovery, i get the stock Samsung recovery screen. How can I get this to work?
And another question, is about roms such as Cyanogen mod. I really wanna get it. (I wont until I get CWM working, though.) And I'm just wondering. If I were to just go to ROM Manager, and flash cyanogen, would it work, or do i need to do more to my phone to be able to put on custom roms? I've never understood the concept of roms vs kernels vs firmware vs whatever else.
And if it matters, Samsung Galaxy S II, Android 2.3.3, rooted using SuperOneClick.
P.S Anything else that I should considering doing/putting onto my phone? And thanks in advance for halping.
Click to expand...
Click to collapse
Okay, don't take this the wrong way, but it seems you're a bit lacking regarding knowledge about this phone... It'd pay to do your research beforehand in the SGS2 forum, read the FAQs, etc.
Okay, first off, all I can say is, go back to stock. Go flash a stock Samsung ROM for the device. Then, go into Chainfire's CF-Root Kernel thread, and download the appropriate kernel, and flash it using ODIN. After you've done that, you'll have ClockworkMod, and you'll be rooted. It is recommended that you flash another kernel though, after gaining root, as all the CF-Root kernel does it install ClockworkMod, and root the device. Personally, I recommend SiyahKernel.
If you need more detail or have any more questions, feel free to send me a PM.
Thanks,
screamworks.
screamworks said:
Okay, don't take this the wrong way, but it seems you're a bit lacking regarding knowledge about this phone... It'd pay to do your research beforehand in the SGS2 forum, read the FAQs, etc.
Okay, first off, all I can say is, go back to stock. Go flash a stock Samsung ROM for the device. Then, go into Chainfire's CF-Root Kernel thread, and download the appropriate kernel, and flash it using ODIN. After you've done that, you'll have ClockworkMod, and you'll be rooted. It is recommended that you flash another kernel though, after gaining root, as all the CF-Root kernel does it install ClockworkMod, and root the device. Personally, I recommend SiyahKernel.
If you need more detail or have any more questions, feel free to send me a PM.
Thanks,
screamworks.
Click to expand...
Click to collapse
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Gutana said:
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Click to expand...
Click to collapse
With a rooted device you'll be able to flash trough Odin or CMW recovery any rom you like.
Siyah kernel gives you a faster and more battery efficient phone and lets you set your own Voltage/ speed the processor has to use see this for the latest info
http://www.gokhanmoral.com/ and
http://forum.xda-developers.com/showthread.php?t=1263838
DirkTeur Velserbroncx said:
With a rooted device you'll be able to flash trough Odin or CMW recovery any rom you like.
Siyah kernel gives you a faster and more battery efficient phone and lets you set your own Voltage/ speed the processor has to use see this for the latest info
http://www.gokhanmoral.com/ and
http://forum.xda-developers.com/showthread.php?t=1263838
Click to expand...
Click to collapse
Alright, so i'm pretty much ready to go? Yayayayay.
And would you recommend any roms for me? XD
Gutana said:
Alright, I did what you said. I went to stock 2.3.4, used CF-root. And now about SiyahKernel, what are the advantages of it? And is there something wrong with just staying with the CF-Root kernel?
And as of where I am now, with just root and CWM, would i be able to switch ROMs and such?
Click to expand...
Click to collapse
SiyahKernel has a lot of advantages and improvements of CF-Root, which provides null, if I'm correct. Go check out the SiyahKernel thread in Original Development for details.
Yes, as stated, you can use CWM by itself to switch ROMs. Just remember that if you're switching ROMs (as opposed to performing a flash to a newer version of the same ROM), to perform a factor reset / wipe data, wipe cache, and wipe Dalvik cache (Advanced > wipe Dalvik cache) in ClockworkMod first.
Gutana said:
Alright, so i'm pretty much ready to go? Yayayayay.
And would you recommend any roms for me? XD
Click to expand...
Click to collapse
For a beginninger, I can't recommend MIUI highly enough. You could go with GalnetMIUI, which is a variant, but I personally prefer the official MIUI build. If you're looking for a more, 'pure' experience, go with CyanogenMod 7.1 stable.
screamworks said:
SiyahKernel has a lot of advantages and improvements of CF-Root, which provides null, if I'm correct. Go check out the SiyahKernel thread in Original Development for details.
Yes, as stated, you can use CWM by itself to switch ROMs. Just remember that if you're switching ROMs (as opposed to performing a flash to a newer version of the same ROM), to perform a factor reset / wipe data, wipe cache, and wipe Dalvik cache (Advanced > wipe Dalvik cache) in ClockworkMod first.
For a beginninger, I can't recommend MIUI highly enough. You could go with GalnetMIUI, which is a variant, but I personally prefer the official MIUI build. If you're looking for a more, 'pure' experience, go with CyanogenMod 7.1 stable.
Click to expand...
Click to collapse
Alright, one more question, sorry for the nooby-ness. Haha.
So going from my phone to for example Cyanogen, I'd backup in CWM, and Titanium backup (Or does CWM backup like, EVERYTHING?) and then factory reset, flash the rom using odin, and then use titanium backup to get my apps and settings back? orwhat.
Gutana said:
Alright, one more question, sorry for the nooby-ness. Haha.
So going from my phone to for example Cyanogen, I'd backup in CWM, and Titanium backup (Or does CWM backup like, EVERYTHING?) and then factory reset, flash the rom using odin, and then use titanium backup to get my apps and settings back? orwhat.
Click to expand...
Click to collapse
CWM backup (called a NANDroid backup), backs up everything. If you perform a NANDroid back, there's no need to perform a backup in Titanium Backup - it creates a full image of your system (the advantage to TB though, is that you can backup all your download apps and settings, then install the new ROM, and restore the backed up apps - If you restore a NANDdroid backup, it'll restore the old ROM, exactly as it was when the backup was made).
So yes, the installation process is, for CWM: copy the ROM.zip to your phone, then boot into CWM recovery. Hit the 'factory reset / wipe data' option, the 'wipe cache' option, and then go to Advanced, and hit the 'wipe Dalvik cache' option. After that, choose 'install ZIP from SDCARD', and choose your ROM.zip. After it finishes installing, just hit 'reboot system now', and you're good to go!
Usually, it's not required to use ODIN to flash a new ROM, unless there's a problem with the recovery.
All that said, it pays to read the thread for the ROM beforehand, as sometimes when moving from ROM to ROM (especially from stock), there's a few small things that may be required, like flashing the ROM twice, or whatever
screamworks said:
CWM backup (called a NANDroid backup), backs up everything. If you perform a NANDroid back, there's no need to perform a backup in Titanium Backup - it creates a full image of your system (the advantage to TB though, is that you can backup all your download apps and settings, then install the new ROM, and restore the backed up apps - If you restore a NANDdroid backup, it'll restore the old ROM, exactly as it was when the backup was made).
So yes, the installation process is, for CWM: copy the ROM.zip to your phone, then boot into CWM recovery. Hit the 'factory reset / wipe data' option, the 'wipe cache' option, and then go to Advanced, and hit the 'wipe Dalvik cache' option. After that, choose 'install ZIP from SDCARD', and choose your ROM.zip. After it finishes installing, just hit 'reboot system now', and you're good to go!
Usually, it's not required to use ODIN to flash a new ROM, unless there's a problem with the recovery.
All that said, it pays to read the thread for the ROM beforehand, as sometimes when moving from ROM to ROM (especially from stock), there's a few small things that may be required, like flashing the ROM twice, or whatever
Click to expand...
Click to collapse
Alright, i got that done. I've tried both MIUI and Cyanogen, and both are working and lookin wonderful. But the problem is I dont get data on either one. I've tried reflashing, rebooting, factory reset. Idunno what else to try. Do you know what could be causing this?
Gutana said:
Alright, i got that done. I've tried both MIUI and Cyanogen, and both are working and lookin wonderful. But the problem is I dont get data on either one. I've tried reflashing, rebooting, factory reset. Idunno what else to try. Do you know what could be causing this?
Click to expand...
Click to collapse
Check your APN settings (should be somewhere in Settings under mobile network or whatever). Look your's up online ('APN settings carrier y, country z), and if they're not correct, add them in.
screamworks said:
Check your APN settings (should be somewhere in Settings under mobile network or whatever). Look your's up online ('APN settings carrier y, country z), and if they're not correct, add them in.
Click to expand...
Click to collapse
Got everything working, thank you very much. Thanked every one of your posts
And I've asked too many questions for one person in one thread, I happen to have one more. How can I get the Android Market on Cyanogenmod? I downloaded build 115, and there wasn't a market, so i'll be using MIUI till I get that fixed. ><
Gutana said:
Got everything working, thank you very much. Thanked every one of your posts
And I've asked too many questions for one person in one thread, I happen to have one more. How can I get the Android Market on Cyanogenmod? I downloaded build 115, and there wasn't a market, so i'll be using MIUI till I get that fixed. ><
Click to expand...
Click to collapse
You're more than welcome
If you've got any other questions, feel free to PM me
With CyanogenMod, there's a bit of a story to it, but basically, they're not allowed to package Market, Gmail, Maps, etc. with the ROM, so you need to download a zip file called Gapps and flash it in CWM Recovery, you can find it here. You don't need to wipe anything when flashing this.
Also, build #115 isn't the latest, build #117 is (in fact, there's another, even more current one, but there's really nothing to it), but I don't believe there's any major changes.
screamworks said:
You're more than welcome
If you've got any other questions, feel free to PM me
With CyanogenMod, there's a bit of a story to it, but basically, they're not allowed to package Market, Gmail, Maps, etc. with the ROM, so you need to download a zip file called Gapps and flash it in CWM Recovery, you can find it here. You don't need to wipe anything when flashing this.
Also, build #115 isn't the latest, build #117 is (in fact, there's another, even more current one, but there's really nothing to it), but I don't believe there's any major changes.
Click to expand...
Click to collapse
Hey, I was having troubles messaging you, since it didn't show anything in the sent box, i assumed it didnt go through. So i guess ill be still asking you on here.
So about Cyanogen, which build is the best? And if i'm going from one build to another, like from 115, to 116, would i still have to do a complete wipe? And any other roms besides MIUI and Cyanogen you recommend? cause MIUI is giving me and couldn't generate md5 errors, and i cant restore to it, and i hate starting off without it set up how i like it. D: and yeah, thanks.
Gutana said:
Hey, I was having troubles messaging you, since it didn't show anything in the sent box, i assumed it didnt go through. So i guess ill be still asking you on here.
So about Cyanogen, which build is the best? And if i'm going from one build to another, like from 115, to 116, would i still have to do a complete wipe? And any other roms besides MIUI and Cyanogen you recommend? cause MIUI is giving me and couldn't generate md5 errors, and i cant restore to it, and i hate starting off without it set up how i like it. D: and yeah, thanks.
Click to expand...
Click to collapse
I only just the message 12 hours ago, if that helps?
Usually, your best bet is to go with the latest build, which you can get here. If it's stability you're looking for, go with the stable build, instead of nightlies.
Personally, out of all ROMs I've tried, I could only ever stand MIUI and CyanogenMod - but even then, MIUI started to annoy me with little things here and there. I think I'll be sticking with CyanogenMod for awhile. So, I'm not really the best authority on that. Just try some different ones, and see what appeals to you the most
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
drsane1984 said:
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
Click to expand...
Click to collapse
jumping from one rom to another needs a full wipe i guess... when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
First of all, thank you for your reply!
Now, to adress each step
jumping from one rom to another needs a full wipe i guess.
Click to expand...
Click to collapse
Yup, did one (factory reset+system wipe) before trying to flash AW Rom.
when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
Click to expand...
Click to collapse
After the first three unsuccessfull attempt to flash the ROM did I wipe my internal SD, so it isn't the crawling looping intro's problem. And yes, I push ROMs via Adb, and trying flashing.
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
Click to expand...
Click to collapse
That was actually the last step I tried before asking for help. Even after I typed this post, I did it again. Flashed it, pushed AW, and flashed again. No success.
*Edit: I have forgotten a primary Troubleshooting technique. Downloading AW2.1 from a different source, will update.
sorry but im not much of a help i can see... hope somebody could. don't lose hope though...
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
drsane1984 said:
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
Click to expand...
Click to collapse
Hello Everybody! Guys, sorry for my english!!!!!
First of all, I have to present myself, my name is Marco, I'm italian, 25 years old and I'm in the Android world since about 12 Years.
I started whit a Galaxy S2, and after I bought an Asus Transformer Prime.
After just two week, I decided to put in a Custom ROM, on my devices, and I understood how the system work better instead of a Stock ROM!
And after, I understood, how the XDA Developers Forum is important for me, and expecially for all the people who like to learn about the Android World.
So, I just want to Thanks with all of you for the support that i receive EVERY DAY to solve my problems!
One of these was with flashing the Androwook, weeks ago I flashed the Team EOS 2.0, that was really amazing, but after a While, I found some slowdowns in some action on the system, so i decided to try a rom based on the stock rom, but with improvement and tweaks, so what's better then the Androwook?
The problem was, the same explained on this post, after all wipes, the prime was not boot, and stuck in bootanimation!
I solved, checking the box "Install custom ROM" as drsane1984 have done, and now the ROM is booted perfectly!!
Thanks another time! I'am convinced that if you are able to seach, you'll find for sure the solution to your problems! If not, just ask!
Bye!
Hi,
I rooted my GSII, using step 2c from the guide found here: http://forum.xda-developers.com/showthread.php?t=1311081 with the UCKK6 Stock + Root package found here: http://forum.xda-developers.com/showthread.php?t=1286432
Afterwards, I used CWM to flash PhoneBricker v2.7 (http://forum.xda-developers.com/showthread.php?t=1560759). After only a few minutes of use, my phone began locking up and rebooting randomly. It didn't matter what I was doing at the time. After reading through some threads, I tried wiping cache, factory reset, and flashing only the ROM again, to no avail. I also noticed the phone would get pretty hot when it would lock up.
I thought the ROM was the issue, so I flashed Mystic's Glory ROM (v.4.9.2beta) after wiping cache, factory reset. Same behavior.
I've resorted to restoring the first nandroid backup I did, which is just stock + root.
Would anyone have any suggestions? Thank you.
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
wgoldfarb said:
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
Click to expand...
Click to collapse
wgoldfarb,
I do, in fact, have the I777 variant.
Can you please tell me what you mean by FCs?
The random lockups/reboots began even before I started installing other apps. I do not have Titanium Backup. I installed the apps from the Play store.
Yes, I made sure to do a factory reset, wipe cache, and wipe dalvik cache.
Could it be an issue with the way the ROM is handling CPU usage? Perhaps there is a preset that is on by default that may be causing lockups.
I'm also wondering rooting using the UCKK6 package was the correct way, as opposed to rooting back to the UCKH7.
I appreciate your help.
What kernel are you running? That sounds like the issue to me
jthatch12 said:
What kernel are you running? That sounds like the issue to me
Click to expand...
Click to collapse
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
wwjd3 said:
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
Click to expand...
Click to collapse
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
creepyncrawly said:
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
Click to expand...
Click to collapse
I'm sorry. I failed to mention that after rooting, I used MobileOdin to flash a custom kernel (Siyah 2.6) with CWM (step 3a in the first link I provided). From there, before flashing PhoneBricker, I did a factory reset, cache wipe, dalvik cache wipe, all from within CWM. I did NOT perform factory reset from phone settings.
I have not performed a md5 sum check. I guess that would be the next step.
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
wgoldfarb said:
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
Click to expand...
Click to collapse
Ah, I understand. What I meant by lockup is that the system freezes. The capacitive buttons no longer respond. Neither do the volume/power buttons. The screen simply freezes, and I have to force a restart by holding down the power button for a number of seconds. I hope that makes sense.
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
wwjd3 said:
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
Click to expand...
Click to collapse
1. Short answer - yes. Long answer - no (I remember a few other options floating around). For all intents and purposes, just pick one of those; either will accomplish what you need.
2. From what I remember about looking at the script, it wipes dalvik cache and deletes the contents of /etc/int.d (to prevent incompatible scripts across kernels - not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Simba501 said:
not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Click to expand...
Click to collapse
If I read correctly, Phalanx was offering up a secondary option to try out before taking the complete stock route which would make it relevant. However, if he does the return to stock... Then you're right, not gonna do much for him. (though it wouldn't hurt)
Clay
Team Pirate
Sent from my PINK SGH-I777
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
creepyncrawly said:
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
Click to expand...
Click to collapse
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
wwjd3 said:
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
Click to expand...
Click to collapse
How did you root your phone b4? which method?
Use that.
votinh said:
How did you root your phone b4? which method?
Use that.
Click to expand...
Click to collapse
I used method 2c, Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader previously. I was thinking of using a different method, since I ran into problems using Entropy512's method. Try something different.
-------------------------------------------------
EDIT:
I'm sorry, I was wrong. Since I had UCKK6 build previously I used Odin to flash the Kernel + cache + rooted UCKK6 system package found here: http://forum.xda-developers.com/showthread.php?t=1286432
So, using method 2c would, in fact, be a different method altogether. I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
wwjd3 said:
I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
Click to expand...
Click to collapse
It's as good a theory as any other... I guess.
This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.