Related
Before I get ravaged, I have wandered from thread to thread to thread trying to find answers and unfortunately, everyone's got a different situation, so I'll try and sum it up here.
I have an Epic 4G that I threw the Samsung/Sprint Froyo ROM on as soon as it as available, after which I rooted it, installed CWM 2.5 and called it a day. I've been wanting to upgrade to Gingerbread, but the official EI22 ROM is obviously giving me issues because of root, so I decide, hey, I can try adding on some other ROMs and finally get into this thing.
Now somewhere amongst all this, I have CWM 5.0 installed and my phone is running both older and newer versions and only 5.0 is letting me restore in case I screw up.
So I grab the Gingerbread restore and after wiping my data, restore it. Gets stuck on Samsung logo. Try this a few times, give up, reload my original Froyo image (only after coaxing CWM to load up 5.0 instead of 2.5). Try again tonight with ACS ICS ROM and 2.5, still stuck at Samsung logo. Wipe and try again, same thing.
So my question is: A) would it be better to go back to Odin and try again despite a stable Froyo image, B) how can I eliminate one of these CWMs, C) has anyone else had these issues?
seems like you did a whole bunch of things... probably best to start clean.. odin to stock froyo. then you probably want to root it from there. after that, you can flash the latest cwm, then latest gingerbread rom
when you installed cwm5, did u flash through rom manager or through recovery?
I honestly just downloaded CWM from Marketplace and I found out how I was able to access it: it's a zip in my Clockwork folder. Once I "install" that, it loads into 5.0 and that's how I've been able to work, but it never updates CWM, I have to keep having to boot into it from the zip.
well u have cwm2,5 u said... try booting into cw, (three fingers) and flash the zip. but maybe you can try downloading cwm from the official cwm thread and flash that zip just to be sure
http://forum.xda-developers.com/showthread.php?t=1357655
Yeah, every time I try to flash that ZIP, it just opens up 5.0 instead. I'll have to try doing it from scratch.
isnt that what u want??? 5.x.x.x??
EpicNewb4g said:
isnt that what u want??? 5.x.x.x??
Click to expand...
Click to collapse
Yeah, definitely.
Okay, Odin'ed back to stock Froyo and rooted, loaded on ACS Recovery. This whole process has killed my battery, so I'm going to recharge before trying to load up a new ROM. It seems like it should be easy from here on out...
You should just start over with a fresh install.
Here are the steps. I made this list before CWM 5 was released, but you can get the CWM 5 ODIN .tar file from that thread which was linked a few posts up.
http://forum.xda-developers.com/showpost.php?p=19444784&postcount=93
Yeah I ODINed back with ACS Recovery and now I'm running ACS ICS, which is sooooooo awesome. I think I was afraid about having to ODIN back to stock and losing everything. Now I should still have the Froyo image on there, can't I just run between this new one and that?
Thanks, all!
What do you mean by you have acs ics and still have the froyo image?? are you dual booting
Acs ics = rom.
EpicNewb4g said:
What do you mean by you have acs ics and still have the froyo image?? are you dual booting
Click to expand...
Click to collapse
Does he mean the wallpaper?
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!
Hey, not sure why i can't update to jb leak ota 4.1.1 . I had no issues doing it on my GF's sgs3 t999. I am on uvalh2 stock, i renamed it to update.zip on the external sdcard, i put usb debugging on, and after i applied update from external sdcard it said "emmc/dev/block/mcbl####". My phone is rooted but not sure if that's the problem. If anyone can help me that would be awesome. Thanks in advance,
Jake
Before you go down that road....
themadzionist said:
Hey, not sure why i can't update to jb leak ota 4.1.1 . I had no issues doing it on my GF's sgs3 t999. I am on uvalh2 stock, i renamed it to update.zip on the external sdcard, i put usb debugging on, and after i applied update from external sdcard it said "emmc/dev/block/mcbl####". My phone is rooted but not sure if that's the problem. If anyone can help me that would be awesome. Thanks in advance,
Jake
Click to expand...
Click to collapse
See my thread below- It can be done if you return to unrooted stock, but then the fun really begins as I cannot now root. On the plus side the ROM is awesome and runs perfectly- SMS and Calls over WIFI work. I think they are VERY close to release.
I am reflashing 4.04 to get Root back
My thread: http://forum.xda-developers.com/showthread.php?t=1883359
Fonz said:
See my thread below- It can be done if you return to unrooted stock, but then the fun really begins as I cannot now root. On the plus side the ROM is awesome and runs perfectly- SMS and Calls over WIFI work. I think they are VERY close to release.
I am reflashing 4.04 to get Root back
My thread: http://forum.xda-developers.com/showthread.php?t=1883359
Click to expand...
Click to collapse
Thanks fonz, I'm going to try that. But if i have to unroot with i update to JB. Can i access CWM to restore nandroid backup? I wonder if the issue you are having is the same that i had. When i flashed cwm with odin, i had to make sure auto reboot was not checked, and after it passes, pull the battery and go straight into cwm. If it restarts it goes back to Android stock. I had that issue With uvlah2. I'm not sure if that's an issue with 4.1.1 too. But if i can't access cwm after updating to JB i think ill wait till the update, because i just wanted to test it and then restore nandroid B. i wish there was an exact date for JB release, I'm getting kinda antsy. Every JB custom rom I've flashed had too many bugs to stick with. thanks again
Jake
themadzionist said:
Thanks fonz, I'm going to try that. But if i have to unroot with i update to JB. Can i access CWM to restore nandroid backup? I wonder if the issue you are having is the same that i had. When i flashed cwm with odin, i had to make sure auto reboot was not checked, and after it passes, pull the battery and go straight into cwm. If it restarts it goes back to Android stock. I had that issue With uvlah2. I'm not sure if that's an issue with 4.1.1 too. But if i can't access cwm after updating to JB i think ill wait till the update, because i just wanted to test it and then restore nandroid B. i wish there was an exact date for JB release, I'm getting kinda antsy. Every JB custom rom I've flashed had too many bugs to stick with. thanks again
Jake
Click to expand...
Click to collapse
That may be it! I will try that next. I had auto reboot on and it went to stock as you say. I have reverted the phone twice today so if you want to play you can. The ROM is really excellent. I think I will try one more time and then wait for release or at least for an Odin compatible ROM (tar.md5)
Just make certain to have Titanium Backups- I could not easily restore from Nandroid, but Titanium worked well. I restored by reflashing stock and then rooting again. Then restore from Titanium...
Fonz said:
That may be it! I will try that next. I had auto reboot on and it went to stock as you say. I have reverted the phone twice today so if you want to play you can. The ROM is really excellent. I think I will try one more time and then wait for release or at least for an Odin compatible ROM (tar.md5)
Just make certain to have Titanium Backups- I could not easily restore from Nandroid, but Titanium worked well. I restored by reflashing stock and then rooting again. Then restore from Titanium...
Click to expand...
Click to collapse
Oh yeah that's a great idea. I didn't think of that, so basically flash stock back through odin and then after rerooting, restore nandroid backup. I'm going to try it now. And yeah, uncheck the auto reboot, after it passes, exit odin and just pull the battery out or just power off, and then vol up + home + power and you should go straight to cwm, don't let it start up or else you lose cwm and will have to reflash. And what sucks is that every time it boots up you lose cwm but i just flash CWM thru rom manager everytime and after it flashed i just hit reboot into recovery. Thanks again Fonz
So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.
Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.
To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.
Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement
GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)
My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.
You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.
Hi, I am sending my HTC One in for service, so reactivated my Sprint Epic 4G. It is running CM 10.1 (10.1.3.1). To get data working, I need to update the profile. Any way to do that in CM?
If not, what ROM do I need to flash that supports updating the profile?
Other than rooting the phone and installing CM10.1, I have no messed with other settings. It should still be stock radio/whatever else people mess with. Voice works fine.
Just reflash any stock firmwares, update the profiles and flash back to CM again. Alternatively, there seems to be a multiboot solution that lets you temporaily boot a stock firmware from SD card, though I'm not sure if it works with your ROM...
Sent from Google Nexus 4 @ CM11
Thanks. I think I need to ODIN back to stock right, as CM10.1 uses different partitioning? (Might not be the correct word)
shawndoc said:
Thanks. I think I need to ODIN back to stock right, as CM10.1 uses different partitioning? (Might not be the correct word)
Click to expand...
Click to collapse
You on CM10.1? Good thing - if you have a flashable stock zip, just flashing it will revert the partition layout.
Sent from Google Nexus 4 @ CM11
shawndoc said:
what ROM do I need to flash that supports updating the profile?
Click to expand...
Click to collapse
Put this Samsung FC09 installation onto your SD card to temporarily boot into and perform PRL/Profile update functions.
Thanks