Related
Ok so I flashed it the first time and it was successful but noticed market was not opening so I flash the latest gapps for cyonogen mod and then everthing fc so wiped and flash and now it won't even boot it gets stuck on splash screen. Is it cause of SD card is on ext 4 or is it smellkus recovery or what?? Any help is much appreciative
Try wiping cache and dalvik then fix permissions in recovery.
Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.
Ryan_28 said:
Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.
Click to expand...
Click to collapse
Exactly...I've never heard of this rom for the evo. So I question it.
teh roxxorz said:
Exactly...I've never heard of this rom for the evo. So I question it.
Click to expand...
Click to collapse
no its for the evo its under evo general development it was just released
Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.
Ryan_28 said:
Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.[/Q
Yes I could go into recovery and I actually fixed the issue. I'm guessing it was the recovery itself that I was using because now I flashed Among RA recovery and now is booted and working fine. A great Tom overall. Thanks guys for your help
Click to expand...
Click to collapse
Not to bother anyone, but I was trying to run the droid GTRv2.0 ROM on my EVO 4G and it wont get past the first screen.
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
joshnichols189 said:
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
Click to expand...
Click to collapse
I've tried all the latest kernels. Every kernel I've tried is compatible with the ROM I've tried it on.
isikh said:
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
Click to expand...
Click to collapse
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
TheAxman said:
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
Click to expand...
Click to collapse
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
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
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
isikh said:
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
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
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
Click to expand...
Click to collapse
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
TheAxman said:
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
Click to expand...
Click to collapse
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Use this kernel it works perfectly on CM10
http://forum.xda-developers.com/showthread.php?t=1845836
EDIT: nvm use this one http://forum.xda-developers.com/showpost.php?p=31025930&postcount=1152
isikh said:
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Click to expand...
Click to collapse
Now I am a tad confused, you have UVALH2 on the phone already, and you want to flash UVALH2? or did you typo? I am no dev, but from what I have been seeing, the radio should not matter at the moment, if I am wrong, someone please set me straight, also, I will be on the web all night and tomorrow, so I will help where ever I can, I will check here for your progress. Good luck my friend.
BTW, I do not like stock roms, so to me CM10 is for sure better. Faster also.
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
joshnichols189 said:
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
Click to expand...
Click to collapse
Yeah, I know all this, but I wanted to ask in case I may have missed something. Even when you're pretty Android savvy when it comes to rooting and whatnot, you do miss things on occasion. In this instant I didn't, but I was hoping I did because a bunch of custom kernels won't work on my phone with CM10! Trinity worked well, so I'm waiting for those. It must be some specific chip related issue because I'm not the only one. Anyways, thanks everyone!
Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Flash a newer recovery prior to flashing CM10.
EdwinForTheWin said:
Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
Sent from my SGH-I747M using xda premium
such as
SaneinOne said:
Flash a newer recovery prior to flashing CM10.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Such as...
EdwinForTheWin said:
Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
I suggest that you take a look at these first before trying to root your phone:
http://forum.xda-developers.com/showthread.php?t=1739426
http://forum.xda-developers.com/showthread.php?t=1725839
Second, I have Cyanogenmod 10 and I can say that it's playing safe so far - the only disadvantages that you would have are: Samsung's gestures are not functional and CM10 is kinda unstable for games and apps. I also experienced the Status 7 error and from experience, it's caused by using an 'old' version of CWM Recovery. Download the latest one from here (Samsung Galaxy S3 AT&T): http://www.clockworkmod.com/rommanager and download the Cyanogenmod 10 M2 from the CM site.
Assuming that you know how to setup the custom recovery for your phone, delete the current recovery.img on your phone and replace it with the new one that you downloaded. Then just do what you did to setup your custom recovery. I also suggest that you follow the ROM flashing guide on this page: http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_III:_Full_Update_Guide as it is what I followed to ensure that a brick wouldn't happen on my phone. Just a reminder, also wipe the Dalvik cache just to be sure.
TL;DR Flashing and rooting is safe as long as you're patient and you thoroughly follow guides on rooting/flashing your phone.
okay
GlassRaven said:
I suggest that you take a look at these first before trying to root your phone:
http://forum.xda-developers.com/showthread.php?t=1739426
http://forum.xda-developers.com/showthread.php?t=1725839
Second, I have Cyanogenmod 10 and I can say that it's playing safe so far - the only disadvantages that you would have are: Samsung's gestures are not functional and CM10 is kinda unstable for games and apps. I also experienced the Status 7 error and from experience, it's caused by using an 'old' version of CWM Recovery. Download the latest one from here (Samsung Galaxy S3 AT&T): http://www.clockworkmod.com/rommanager and download the Cyanogenmod 10 M2 from the CM site.
Assuming that you know how to setup the custom recovery for your phone, delete the current recovery.img on your phone and replace it with the new one that you downloaded. Then just do what you did to setup your custom recovery. I also suggest that you follow the ROM flashing guide on this page: http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_III:_Full_Update_Guide as it is what I followed to ensure that a brick wouldn't happen on my phone. Just a reminder, also wipe the Dalvik cache just to be sure.
TL;DR Flashing and rooting is safe as long as you're patient and you thoroughly follow guides on rooting/flashing your phone.
Click to expand...
Click to collapse
Thanks for the response, do you recommend that I flash another ROM before flashing cyanogenmod 10?
EdwinForTheWin said:
Thanks for the response, do you recommend that I flash another ROM before flashing cyanogenmod 10?
Click to expand...
Click to collapse
I don't really recommend that as that could cause unwanted trouble. From my experience, I just followed the rooting guide that I posted, flash a custom recovery, and flashed the Cyanogenmod 10. Another tip, if you don't want to lose your contacts, make a backup of it before flashing a ROM. Preferrably you write them in a paper so it would be easier. If you have important messages, use an SMS/MMS backup tool to save them. As for applications, make a list of applications that you consider are essential for you so you could just redownload them. Starting out in a custom ROM is really hard at first but you'll get used to it.
Its safety is directly proportional to your ability to follow directions.
Your first mistake was you used the app to unlock the VERIZON S3 bootloader.
All other versions of the GS 3 have unlocked bootloaders.
You should definitely do some more research before you attempt root and custom recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Can you just use ROM Manager after rooting and flashing the stock ROM to download CWM, then CM10? And is the CM10 you're using on your Rogers phone compatible? I don't see a Rogers version on the CM site. Did you use the AT&T one?
Yes for the ROM manager, but the free version doesn't install latest touch recovery. The at&t version is compatible with all Canadian i747m. You can get the latest version here: http://get.cm/?device=d2att
tonymtl said:
Yes for the ROM manager, but the free version doesn't install latest touch recovery. The at&t version is compatible with all Canadian i747m. You can get the latest version here: http://get.cm/?device=d2att
Click to expand...
Click to collapse
What does touch recovery do? And do I have to use that link to flash it, or can I use ROM Manager? And if I were to use that link, I would DL the zip, boot my phone into download mode, plug in, open Odin, make sure auto reboot and F reset time are checked, load the .tar into the PDA, and click start? What happens to the previous ROM that was there?
And when I first root my phone, and load the stock rom, do all of my apps remain? I haven't rooted yet, for my Rogers phone.
A touch recovery lets you touch the screen as apposed to using the volume rocker.
You will keep all your data.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks for the help! Another question, if I would like to unroot my phone, and decrease the flash counter, is there a thread I should see for the I747MVLLH1? I know about triangle away, but Rogers/my model isn't supported for that.
Triangle away does support Rogers gs3
Thanks! So should I flash CM10 through ROM Manager, or through the link that was posted? I'm not exactly clear on how to flash the ROM through the link though. Does flashing a new ROM erase the previous ROM? And 'wiping cache' doesn't wipe your data/apps right, only 'wipe Data and Cache'? And I don't really need to bother with kernels too right?
If you going from stock to cm10 wipe everything: cash, data, dalvik cash. Don't flash kernels unless you want to overclock and undervolt, cm10 comes with kernel and I get pretty good battery life with it. You can flash from ROM manager, and yes it will erase your previous ROM, so do a backup before flashing.
tonymtl said:
If you going from stock to cm10 wipe everything: cash, data, dalvik cash. Don't flash kernels unless you want to overclock and undervolt, cm10 comes with kernel and I get pretty good battery life with it. You can flash from ROM manager, and yes it will erase your previous ROM, so do a backup before flashing.
Click to expand...
Click to collapse
And when I flash it through ROM Manager, it would give me the option to wipe everything right?
The backup that I would do through ROM Manager, thats just incase anything goes wrong right? It's not to get back my apps once I flash from stock to CM10? Other than manually installing them after flash, is there any way to quickly get back my apps/files?
And does the CM10 flash from ROM Manager include the GAPPS file?
Yes it will ask you if you want to wipe, if you download cm10 ROM from ROM manager it will ask you if you want the latest gapps. You can get ROM toolbox or titanium backup to backup your apps and restore them after flashing rom. Backup is just in case but you can always flash stock ROM later if anything goes wrong.
ily112 said:
And when I flash it through ROM Manager, it would give me the option to wipe everything right?
The backup that I would do through ROM Manager, thats just incase anything goes wrong right? It's not to get back my apps once I flash from stock to CM10? Other than manually installing them after flash, is there any way to quickly get back my apps/files?
And does the CM10 flash from ROM Manager include the GAPPS file?
Click to expand...
Click to collapse
You should probably flash through your cwm recovery instead of ROM Manager, but yea you can do a backup in recovery or ROM Manager, and I recommend Titanium backup it's easy to use and free.
s0ulja said:
You should probably flash through your cwm recovery instead of ROM Manager, but yea you can do a backup in recovery or ROM Manager, and I recommend Titanium backup it's easy to use and free.
Click to expand...
Click to collapse
How exactly would I flash through cwm recovery?
I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.
Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?
Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?
Hey there I know this might sound like a complete newbie question but I have honestly run out of ideas so posting here for some idea.
I have at this point decided my phone must be a lemon.
1. Day 1 received phone installed CM ran it for multiple days no problems.
2. After a few days of this wanted to try Wanams i9505 rom so wiped everything including data in recovery rebooted recovery and installed. First boot was fine setup was fine got it working but then after my first try to reboot it ot stuck at SAMSUNG GALAXY S4 second time it made it to the boot animation but crashed half way through it and reset.
3. Thinking my phone wasn't playing nice with the kernel in Wanam's rom (Adam I believe) I flashed his ROM then immediately flashed the stock m919 kernel after. Same results after first boot.
4. Then tried restoring my nandroid of complete stock. Same problem.
5. Wiped all (except SD) and restored nandroid of stock. Problem gone.
6. After my next backup of stock problem is back.
7. If I do a full odin to stock it works and reboots for days no problem.
I am using TWRP for TMO, have a m919v (Canadian Variant)
Any advice at all would be great, I could easily have overlooked something obvious. Thanks!
Should I not be wiping preload and EFS when doing a "full wipe" ?
No, if you are just flashing a rom from another carrier, which you are, wipe as usual, flash the rom, and before you boot use the tmo canadian kernel, it will boot.
TheAxman said:
No, if you are just flashing a rom from another carrier, which you are, wipe as usual, flash the rom, and before you boot use the tmo canadian kernel, it will boot.
Click to expand...
Click to collapse
Hey thanks for the response yes it does boot once, but after that it seems to not. I have even tried re-flashing the stock m919 kernel after flashing the target rom fails booting and that doesnt seem to fix it.
Idyar said:
Hey thanks for the response yes it does boot once, but after that it seems to not. I have even tried re-flashing the stock m919 kernel after flashing the target rom fails booting and that doesnt seem to fix it.
Click to expand...
Click to collapse
Where did you happen to find the kernel for your device?
TheAxman said:
Where did you happen to find the kernel for your device?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2262729
Idyar said:
http://forum.xda-developers.com/showthread.php?t=2262729
Click to expand...
Click to collapse
whoa, and that is for the 919v? Now I am really confused.
hmm, if thats the correct one, we have a problem. Let me ponder the moment. give me a few...maybe someone else could enlighten us...
is it just happening with this rom, does any of your backups restore ok?
TheAxman said:
whoa, and that is for the 919v? Now I am really confused.
hmm, if thats the correct one, we have a problem. Let me ponder the moment. give me a few...maybe someone else could enlighten us...
Click to expand...
Click to collapse
Good point they are not specifically for V variant but it is my understanding that they should be identical. I have the odin flash for it so what I will do is use that to be 100% sure thanks for the tip.
Idyar said:
Good point they are not specifically for V variant but it is my understanding that they should be identical. I have the odin flash for it so what I will do is use that to be 100% sure thanks for the tip.
Click to expand...
Click to collapse
You flashed Odin then made backup of stock right? And it still had an issue?
Seems like a recovery issue. Try CWM recovery instead
Sent from my SGH-M919 using Tapatalk 2
Yup cmw seems to have fixed all my problems thanks.