Related
Still a major noob here. I want to get cyanogenmod 10 onto my s3 but I've had issues ever since putting on UVALH3. If I want to get CM10 can someone walk me through all the steps to get there, or is it just impossible?
ambitionlessness said:
Still a major noob here. I want to get cyanogenmod 10 onto my s3 but I've had issues ever since putting on UVALH3. If I want to get CM10 can someone walk me through all the steps to get there, or is it just impossible?
Click to expand...
Click to collapse
Do you have a recovery installed like CWM or TWRP? Lets start with that.
sipple31 said:
Do you have a recovery installed like CWM or TWRP? Lets start with that.
Click to expand...
Click to collapse
Could it be I was supposed to do this before flashing CM10? Because I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
isikh said:
Could it be I was supposed to do this before flashing CM10? Because I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
Click to expand...
Click to collapse
pretty sure having a custom recovery isn't your issue if you are to the point of wiping caches and flashing kernels. The OP is asking how to wipe a stock ROM off and get CM on his/her phone i'm pretty sure.
sipple31 said:
pretty sure having a custom recovery isn't your issue if you are to the point of wiping caches and flashing kernels. The OP is asking how to wipe a stock ROM off and get CM on his/her phone i'm pretty sure.
Click to expand...
Click to collapse
I was asking about myself because I thought I had a similar problem
sipple31 said:
Do you have a recovery installed like CWM or TWRP? Lets start with that.
Click to expand...
Click to collapse
No i do not. I tried rooting my phone and it didn't take, and you need to root before CWM right? I had CWM when I was on Uvalh2 but when I went through the process of Uvalh3 I guess I lost it. Should I go ahead and do it? I have the zip file in my phone, still.
I should also mention that when I go into recovery the android dude is fallen over, dead. I'm guessing that's a bad sign.
That just means you're on stock recovery. Odin a rooted rom which you can find in the dev forums (root without tripping flash), then install twrp or cwm, then flash cm10, then flash desired radio.
Sent from my SGH-T999 using xda app-developers app
Sorry if this was posted, the SGSII is active and sort of cluttered so its hard to find which one is what.
The question: So I successfully flashed, gained root, and got a custom recovery for my friends SGSII. Whenever I try to flash a ROM, like CyanogenMod 9 or MIUI.us it get stuck at boot, and yes I am on ICS. I also heard that the CWM Recovery for this phone is messed up, so can anyone fill me on that? Is there a special thing I have to do before flashing a ROM? Do I have to use TWRP instead of CWMR?
CWM Recovery version: 5.0.2.7
Android OS: ICS 4.0.4
SGSII Version: T-Mobile
th3controller said:
Sorry if this was posted, the SGSII is active and sort of cluttered so its hard to find which one is what.
The question: So I successfully flashed, gained root, and got a custom recovery for my friends SGSII. Whenever I try to flash a ROM, like CyanogenMod 9 or MIUI.us it get stuck at boot, and yes I am on ICS. I also heard that the CWM Recovery for this phone is messed up, so can anyone fill me on that? Is there a special thing I have to do before flashing a ROM? Do I have to use TWRP instead of CWMR?
CWM Recovery version: 5.0.2.7
Android OS: ICS 4.0.4
SGSII Version: T-Mobile
Click to expand...
Click to collapse
Yes try TWRP it never let's me down... make sure you wipe too!
iNeedICS said:
make sure you wipe too!
Click to expand...
Click to collapse
Thats what my mother always says!
vassosman said:
Thats what my mother always says!
Click to expand...
Click to collapse
Yes but in real life it unnecessary
I was having some problems too until I realized that I was using an ancient version of CWM. Flashed a newer CWM Touch and all was well after that - I was able to to perform a successful wipe and flash of CM10 - everything just worked perfectly after that.
Let me get this straight...
Flash TWRP
Use TWRP to flash Super Wipe
Flash a ROM
... and enjoy ROM?
Did I get it right?
I don't understand and believe me I'm not complaining but I have cwr5027 and use dark side scripts all the time and never have problems.
Is it just a matter of time? I flash often...very often.
Sent from my SGH-T989 using xda app-developers app
Thank you guys! I cannot hold my gratitude so I have to post a thanks to those who have helped! TWRP is the best alternative recovery
I have now successfully flashed CM9.1 and my friend will be very happy indeed with the bloat gone and the pure ICS feel!
So today i have had nothing but problems with flashing roms. I was on the PAC rom nightlies, but decided to go back to touchwiz roms due to the wifi calling. I tried flashing wicked v4, booted fine but once i reboot, got stuck at the samsung boot logo. tried reflashing/wiping/flashing other roms, including PAC again, all would result in getting stuck at the samsung boot logo. so i used odin to go completely back to stock. That wouldnt boot at first, so i tried wiping data in stock recovery, luckily that got it to boot. I then re-rooted and tried to flash infamous 2.5. same thing, got stuck at the samsung boot logo. finally, i was able to get infamous google edition to boot, but isnt what i want (since it doesnt have wifi calling), but is the only thing i could get to boot.
So does anyone have any idea why my phone is being so moody, or am i just having a bad day?
edit:i will attempt to try and flash infamous 2.5 when i get out of work to see if my phone is in a better mood, but right now i just need a working phone
edit 2: if its relavent, before i used odin, i was using twrp recovery, but after odin, i used clock work mod touched
I also having the same problem, by just rebooting on jedi it goes into bootloop. My guess is either the kernel or the recovery (no expert). On my friends ATT it bootlooped only because I didn't flash the required Ktoons kernel. As for Tmobile I'm not sure of the bootloops, but to fix it i just dirty flash a rom and it works but it happens usually after i flash some add ons.
Both of the problems here are kernels, change to another kernel, should fix these problems.
Good luck
If that does not work, come back here, we will figure something else out.
just tried flashing infamous 2.5, this time with ktoonz kernel, same result, stuck at samsung.
Going to try wicked v4 this time
TheAtheistOtaku said:
just tried flashing infamous 2.5, this time with ktoonz kernel, same result, stuck at samsung.
Going to try wicked v4 this time
Click to expand...
Click to collapse
You tried infamous with it stuck kernel?
But I know what you mean been experiencing that with some Rom as of late not sure what's the deal...
Famously Infamous
mgbotoe said:
You tried infamous with it stuck kernel?
But I know what you mean been experiencing that with some Rom as of late not sure what's the deal...
Famously Infamous
Click to expand...
Click to collapse
yes i have tried it with the kernel it comes with, same result.
still downloading wicked.
What recovery are you using? I know twrp latest is very buggy for most people...also I heard its not fully cleaning people phones for a flash and what not..Im quite sure its a recovery bug for you
mgbotoe said:
What recovery are you using? I know twrp latest is very buggy for most people...also I heard its not fully cleaning people phones for a flash and what not..Im quite sure its a recovery bug for you
Click to expand...
Click to collapse
ive used twrp before i odind back to stock. but now i have been using clockwork mod touch, still having the same problem
after flashing kernal wipe cache,dalvik and fix permissions that should work
LIL_ROOKIE said:
after flashing kernal wipe cache,dalvik and fix permissions that should work
Click to expand...
Click to collapse
i have been doing that after every new flash.
anywho, wicked v4 is booting with ktoonz kernel, and after a reboot its continuing to boot, so im not going to press my luck and stay on wicked. though i still would like to know whats going on.
TheAtheistOtaku said:
i have been doing that after every new flash.
anywho, wicked v4 is booting with ktoonz kernel, and after a reboot its continuing to boot, so im not going to press my luck and stay on wicked. though i still would like to know whats going on.
Click to expand...
Click to collapse
You're not "formatting data" correct? Should only "wipe data". Not format.
norml said:
You're not "formatting data" correct? Should only "wipe data". Not format.
Click to expand...
Click to collapse
no im not formatting data lol i know the difference
TheAtheistOtaku said:
no im not formatting data lol i know the difference
Click to expand...
Click to collapse
LOL, I'm sorry, just that I have seen soooo many ppl getting bootloops or stuck samsung screens, because of that and also not knowing exactly what to wipe. Just trying to help.:victory::highfive:
norml said:
LOL, I'm sorry, just that I have seen soooo many ppl getting bootloops or stuck samsung screens, because of that and also not knowing exactly what to wipe. Just trying to help.:victory::highfive:
Click to expand...
Click to collapse
its no problem
Check SD card
I had a similar issue where my S4 just decided to go into a bootloop on the way to work. A coworker of mine's wife's S3 did the same exact thing and we were finally able to pin it down to both having a SANDISK 32GB micro sd card. Once I pulled the card (after having ODIN'd back to stock and pulling my hair out my desk =/) the phone booted right up. Since all I had on there was music I stuck it in after the phone booted, reformatted it from the stock odin restore (MDL), and I haven't had any issues since. Just figured I'd let you know what caused me to go insane for a few hours since it wouldn't boot after flashing anything at all and only occasionally boot from a clean odin restore or fresh wicked flash. After talking to another guy at work that has a note II, S3, and S4 apparently I'm not the only one that's had this issue pop up.
Since I fixed it I've been running Infamous GE (Infamous Kernel) and The leaked GE 4.3 build without issue.
Wow, SanDisk sd cards have been really sucKing lately. I'll try taking out my sd card if it ever happens again
Sent from my SGH-M919 using Tapatalk 4 Beta
31337_haxer said:
I had a similar issue where my S4 just decided to go into a bootloop on the way to work. A coworker of mine's wife's S3 did the same exact thing and we were finally able to pin it down to both having a SANDISK 32GB micro sd card. Once I pulled the card (after having ODIN'd back to stock and pulling my hair out my desk =/) the phone booted right up. Since all I had on there was music I stuck it in after the phone booted, reformatted it from the stock odin restore (MDL), and I haven't had any issues since. Just figured I'd let you know what caused me to go insane for a few hours since it wouldn't boot after flashing anything at all and only occasionally boot from a clean odin restore or fresh wicked flash. After talking to another guy at work that has a note II, S3, and S4 apparently I'm not the only one that's had this issue pop up.
Since I fixed it I've been running Infamous GE (Infamous Kernel) and The leaked GE 4.3 build without issue.
Click to expand...
Click to collapse
I'm using a PNY SD card... just flashed the 7.2 version of infamous, and out of 20 boot attempts, 2 or 3 booted past the GS4 logo.
seems to work if I go back into recovery and factory reset, boot again, and that's the only way I've gotten past the GS4 screen.
Im using TWRP
I've since figured out the problem. For whatever reason when you wipe the cache & dalvic with twrp, sometimes something happens where your internal memory fills up completly, leaving you with no space. Formating the internal from twrp fixes that, but of course you loose everything not on your sd card. Can confirm this problem in twrp 2.6.0 also, since it happend a few times for me
I now just use clock work mod touch, and haven't had the problem since. Pity though,I prefer twrp
Sent from my SGH-M919 using Tapatalk 4
I'm not new to flashing ROMs, etc. But I'm completely confused on why when I installed the Wicked V4 ROM it works fine, but when i restart my phone it stays on the logo and I have to re flash the ROM again.
Any ideas?
nayte1993 said:
I'm not new to flashing ROMs, etc. But I'm completely confused on why when I installed the Wicked V4 ROM it works fine, but when i restart my phone it stays on the logo and I have to re flash the ROM again.
Any ideas?
Click to expand...
Click to collapse
Are you talking about the Galaxy S 4 logo or the boot animation? Either way, you should restore a nandroid backup (hopefully you made one before flashing Wickid V4).
The issue could be caused by not doing a proper wipe before flashing
C.Sweat said:
Are you talking about the Galaxy S 4 logo or the boot animation? Either way, you should restore a nandroid backup (hopefully you made one before flashing Wickid V4).
The issue could be caused by not doing a proper wipe before flashing
Click to expand...
Click to collapse
Could I return to stock using Odin? If so I'll try that when I'm able too.
nayte1993 said:
Could I return to stock using Odin? If so I'll try that when I'm able too.
Click to expand...
Click to collapse
Yeah you sure can. :good: Go here for instructions and stock firmware
nayte1993 said:
Could I return to stock using Odin? If so I'll try that when I'm able too.
Click to expand...
Click to collapse
try a factory reset/wipe first, before you go to stock again
Bob Hodges said:
try a factory reset/wipe first, before you go to stock again
Click to expand...
Click to collapse
Yeah I thought that would fix it too, but it doesn't. What I've had to do is reflash the ROM after clearing the cache and all of that, along with the factory reset and it works fine, the ROM will boot up and works great,but once I restart it just stays at the Galaxy S 4 logo and I have to do it all over again. I've also tried different recoveries because TWRP always wants a password when I boot into recovery and i'm not sure why.
(I've tried various ROMs and they all do this)
So I guess the only thing I can really do at this point would go ahead and use Odin to go to stock and try it all over again.
nayte1993 said:
Yeah I thought that would fix it too, but it doesn't. What I've had to do is reflash the ROM after clearing the cache and all of that, along with the factory reset and it works fine, the ROM will boot up and works great,but once I restart it just stays at the Galaxy S 4 logo and I have to do it all over again. I've also tried different recoveries because TWRP always wants a password when I boot into recovery and i'm not sure why.
(I've tried various ROMs and they all do this)
So I guess the only thing I can really do at this point would go ahead and use Odin to go to stock and try it all over again.
Click to expand...
Click to collapse
AFTER you flash stock rom, perform factory reset wipe, and you wont get stuck. flash recovery. and then flash custom rom and you should be fine
wrong kernels...period
TheAxman said:
wrong kernels...period
Click to expand...
Click to collapse
Yeah I'm coming from the Galaxy S 4G so I got some learning to do when it comes to this phone.
And yes that makes sense, obviously a Odin flash of stock should fix the problem?
Or could I just flash a correct Kernel and maybe that will fix the problem? I'm not quite sure.
I'm thinking Odin is the way to go at this point.
nayte1993 said:
Yeah I'm coming from the Galaxy S 4G so I got some learning to do when it comes to this phone.
And yes that makes sense, obviously a Odin flash of stock should fix the problem?
Or could I just flash a correct Kernel and maybe that will fix the problem? I'm not quite sure.
I'm thinking Odin is the way to go at this point.
Click to expand...
Click to collapse
I've had success with just flashing the right kernel (and clearing dalvik/cache)...but if you're not already set up within the ROM an Odin would make sure you've got a clean base to work with.
Toleraen said:
I've had success with just flashing the right kernel (and clearing dalvik/cache)...but if you're not already set up within the ROM an Odin would make sure you've got a clean base to work with.
Click to expand...
Click to collapse
Thanks so much for your input, now with the Wicked V4 ROM, what Kernel would be best to flash?
If you don't know that fine, I'm just curious. :good:
I haven't rebooted my phone yet, so it's working fine, and it's somewhat set up in term of my contacts, texts, and so on. I'd rather not do Odin if possible, but if I have to I will.
nayte1993 said:
Thanks so much for your input, now with the Wicked V4 ROM, what Kernel would be best to flash?
If you don't know that fine, I'm just curious. :good:
I haven't rebooted my phone yet, so it's working fine, and it's somewhat set up in term of my contacts, texts, and so on. I'd rather not do Odin if possible, but if I have to I will.
Click to expand...
Click to collapse
That's a matter of preference...just make sure to pull a TW kernel. Of course, the kernel built into Wicked should work just fine as well.
I've been a fan of ktoonsez's kernel (link in my sig). 7/7 got a little crashy on me, but 7/2 has been running smooth
Problem fixed, thanks everyone.
I have a T989, not a T989D, running TWRP 2.7.1.0 and UVMC6 radio, coming from a JB 4.1.2 Slimrom.
Also I have taken out the board and inspected the power button, and everything seems okay there. I don't think it's being caused by a faulty button or some other hardware problem because I can flash my old Slimrom, and that boots up just fine.
I wanted to give Paranoid Android a whirl with the latest Wild kernel, and though I've tried 8 different PA builds, a PACman, a Slimkat, and an Alpine rom, ALL KitKat roms so far are bootlooping. [EDIT: Even PA 3.99 JB 4.3 is doing it. So it's more than just KitKat even.]
I'm doing the following:
Wipe system, data, cache, dalvik, and perhaps android secure and preload as well
Flash ROM & Gapps
Wipe cache & dalvik
Reboot
I reach the splash, and maybe it even finishes booting. But invariably, it takes about 60-90s from initialization before the screen dims, everything freezes for 2-5s, and it reboots.
I'm out of ideas.
Why won't my phone work with KitKat?
Thanks in advance
Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin.
Edit: If your phone came with 4.1.2 jellybean, you already have the newest drivers.
meekrawb said:
Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin.
Edit: If your phone came with 4.1.2 jellybean, you already have the newest drivers.
Click to expand...
Click to collapse
I read something to that effect. Haven't seen a .tar file for it, only .zip.
jaybird16 said:
I read something to that effect. Haven't seen a .tar file for it, only .zip.
Click to expand...
Click to collapse
If you sign up for an account on sammobile.com you can download from there. Just type "t989" in the search box.
meekrawb said:
If you sign up for an account on sammobile.com you can download from there. Just type "t989" in the search box.
Click to expand...
Click to collapse
Okay, I did that. Flashed the latest Paranoid Android 4.45. No dice. Same story.
jaybird16 said:
Okay, I did that. Flashed the latest Paranoid Android 4.5. No dice. Same story.
Click to expand...
Click to collapse
That was the only thing I could think of. Maybe someone else has some ideas.
I had the same problem. Turned out it had to do with the recovery. I redownloaded twrp, used flashify to install it. And that fixed the problem.
meekrawb said:
That was the only thing I could think of. Maybe someone else has some ideas.
Click to expand...
Click to collapse
Much appreciated. My phone shipped at the tail end of Gingerbread. So now I have whatever drivers from 4.1.2, and that's one more potential problem eliminated.
The stock rom ran just fine, btw, once I factory reset (the documentation was nil, but at 750mb, I knew it was more than just UVMC6 radio firmware...)
So 4.1.x seems to be okay, but not 4.3.x or 4.4.x. Next I'll have to try a flavor of 4.2.x and see how it feels about that.
Lokke9191 said:
I had the same problem. Turned out it had to do with the recovery. I redownloaded twrp, used flashify to install it. And that fixed the problem.
Click to expand...
Click to collapse
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.45. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
jaybird16 said:
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.5. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
Click to expand...
Click to collapse
Never. Ever. Rule out leprechauns!
Lokke9191 said:
Never. Ever. Rule out leprechauns!
Click to expand...
Click to collapse
LOL, good point.
w00t! TWRP 2.1.8 for the Hercules just dropped!
I was thinking maybe the MD5 wouldn't have checked out the first time you downloaded, but would have the second time. I don't usually bother unless I have a reason to think that's a problem. I can always look after the fact.
Downloaded 2.1.8 and MD5 checks out...now to flash it...
jaybird16 said:
LOL, good point.
w00t! TWRP 2.1.8 for the Hercules just dropped!
I was thinking maybe the MD5 wouldn't have checked out the first time you downloaded, but would have the second time. I don't usually bother unless I have a reason to think that's a problem. I can always look after the fact.
Downloaded 2.1.8 and MD5 checks out...now to flash it...
Click to expand...
Click to collapse
Nice. Lemme know how it works out. Oh. The new PA is awesome.
My bad. I saw the number "8" at the bottom of the page which had not been there earlier and assumed it was next after after "7". No, that's an ancient recovery from 2012.
TWRP 2.8.1 for the Hercules has NOT just dropped!
Okay, so, my first test with a newly downloaded, MD5 checked, and flashed TWRP 2.7.1 recovery, and an MD5 checked PA 4.45 has not produced any different result.
However, you've made me realize that I can't hope to troubleshoot this without being fastidious about MD5 from here on out, so, thx 4 that.
...same goes for a 2nd test with an MD5 checked PA 4.5 Alpha3...
...same goes for a 3rd test with an MD5 checked PA v3.69 (4.2)...
...But Slim-Star v4.12 (4.2) loads no problem...go figure...
Fix permissions?
I tried to install the PA 4.5 Beta, and same problem. It bootloops.
Could it have anything to do with permissions?
jaybird16 said:
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.45. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
Click to expand...
Click to collapse
when i had an issue like this i re-installed the factory original rom and started from the very beginning. if you've tried that and it doesn't work, well i'm pretty much unhelpful here. :crying:
Also note that WildKernel has a special version of v9 out for recent roms (roms released within the last two months).
Any other version of wildkernel will lead to bootloops in my experience.
If your rom is older than two months, then v8 or v9 should do fine
ayr0 said:
Also note that WildKernel has a special version of v9 out for recent roms (roms released within the last two months).
Any other version of wildkernel will lead to bootloops in my experience.
If your rom is older than two months, then v8 or v9 should do fine
Click to expand...
Click to collapse
There were problems reported of even the latest version of Wild! not working with Paranoid.
jrc2
Sent from my T-Mobile S2 using Tapatalk.
I'm having the same issues, but no one knows what's up. I've tried so many ROM's and only the older ones work.
http://forum.xda-developers.com/showpost.php?p=55050951&postcount=9
This is my post with the logs I got from the constant crash on cm11. I tried pa and had the same result.
Issue solved
After sharing some logs with Sultanxda, he pointed out this bootloop issue due to the CM kernel and helped me get it fixed.
My problem was that my phone would not boot on MOST JellyBean ROM's or ANY KitKat ROM. It would crash/kernel panic on or before the set up screen.
I do not know if the latest KitKat ROM's have the issue patched, but I asked if he could upload the patch for the kernel to source for other ROM's to use.
This thread should be solved I guess.