Related
I just installed Synergy RC1 and had been running CM7. I just tried to update profile and prl because since I have been using asop for 7 months I haven't updated anything but I get error 1012 could not be completed when trying to update either profile or prl. My signal has been weaker in last couple weeks so I decided to try sense rom so I could update. Whats the easiest way to update? Any help for a noob? Thanks Again!
That's the only way I know of, I think there may be flashable versions of the probably. Maybe try flashing a stock rooted rom and try to update
We're comin from a pure power source.
You know, a really good idea is to run the RUU on your phone, restore it to stock, root it, flash recovery and do a nandroid, so you have a stock, rooted nandroid you can flash back to whenever you need to update your PRL, etc.....
Good call on that
We're comin from a pure power source.
I do have a stock backup but was trying to avoid restoring and thats one of the reasons I came back to Sense so I could update. Are most people able to update their profile and prl while running Synergy RC1? Maybe it's a server issue in my area I'll try again later and if no go I'll restore stok rom. Are you able to update while using sense roms? Thanks Again!
As I recall that ROM supports all the EPST codes. Can you not do a ##775# in the dialer and enter your MSL? Someone correct me if I'm wrong but I thought you could update PRL that way...
Sent from my PC36100 using Tapatalk
I and a couple of friends cannot do updates with synergy. As the post above mention...do a backup of stock rooted..I use sprint lovers...restore and update then restore synergy back. No more time than to drink a cup of coffee...
I was able to perform the PRL and PRI updates after rebooting into recovery (AmonRA) and clearing Cache and Dalvik again. Also, make sure you're using wireless network, not WIFI. Also, this was addressed in the Synergy threads.
robhep3 said:
I was able to perform the PRL and PRI updates after rebooting into recovery (AmonRA) and clearing Cache and Dalvik again. Also, make sure you're using wireless network, not WIFI. Also, this was addressed in the Synergy threads.
Click to expand...
Click to collapse
Just did what you told...no dice....are you using rc1 or a nightly?
It works with MikG 2.2 Sense 2.1 ROM. Great ROM by the way
Make sure you are not Roaming when you update Profile or PRL.
I had this problem the first time I flashed synergy. I ended up rewiping everything 3 times, then used format all 3 times, partitioned sd card to ext3 then flashed rom along with the carousel and widget zip. Rom now works flawlessly and updates work fine!
This worked for me too, thankfully, just got everything set up like I want and its running great didnt want to have to wipe and reflash. (until my new sd card gets here and I can do a backup - out of space on my current card )
If you guys are having trouble on synergy, go into ##3282# choose edit then enter you msl. Goto data profile, and hit menu, then restore, then commit changes, then reboot. Worked for me every time!
Active_Matrix said:
If you guys are having trouble on synergy, go into ##3282# choose edit then enter you msl. Goto data profile, and hit menu, then restore, then commit changes, then reboot. Worked for me every time!
Click to expand...
Click to collapse
So I did this, and then it after reboot it tried to do hands free OTA, failed, and left me without data connection. In phone update, I still recieved 1012 error on both profile and prl under both wifi on and wifi off.
I'm at present doing a nand restore.
So after nand restore, hard reboot, cache and dalvik wipe and reboot, error still occurs. I now have no 3g service. Anyone have any idea how to fix this sans calling sprint?
savannahmick said:
I just installed Synergy RC1 and had been running CM7. I just tried to update profile and prl because since I have been using asop for 7 months I haven't updated anything but I get error 1012 could not be completed when trying to update either profile or prl. My signal has been weaker in last couple weeks so I decided to try sense rom so I could update. Whats the easiest way to update? Any help for a noob? Thanks Again!
Click to expand...
Click to collapse
I ran into this issue when attempting to update my profile and it was due to the fact that I was hooked up to my WIFI. Once I disabled my WIFI, I ran the update profile and it took less then a minute to complete.
As for the prl, I switched over to amon-ra because clockwork gave me problems. Hopefully this helps you out. Don't forget to hit the Thanks button.
Sent from my PC36100
Hi xda,
I ran into a problem I've never faced today. Before you start assuming, I've done my research. I've searched all over the forums, tried multiple solutions (none worked) and... potentially permabricked it?
Rooted for 7 months, running Jedi Mind Tricks v5.1 Android 4.0.3
How it happened: Today I noticed my phone running really wierdly. It would crash apps constantly, which didn't happen yesterday. So I put it on *close all apps after exiting* on developer options and limited it to run 2 background apps. Throughout the day, my phone would just restart out of absolutely nowhere: in the middle of a text, after unlocking my phone. Each time progressively got shorter between the restarts. It would also freeze a lot of the time. This never happened before today. Maybe a freeze or two, but not this bad.
Did a few battery pulls, no dice. Then this is where it gets worse. The time between boot loops were from 1-2 minutes now. I was getting pissed, so I decided I needed to wipe it and install a new rom. I enter recovery mode CMW 5.0 and do an initial factory reset. Half way through, it crashes again. Now all it does is vibrate constantly until I turned it back on into recovery. Launches recovery. I try to super wipe it. Half way through, crashes again. I try this several times in conjunction with battery pulls. Doesn't work.
I pull sim card, SD card and battery out, let it rest before I reset it.
Then I tried to Odin its ass. I bricked it into the yellow warning screen about a updated system error because I fail with Odin. I searched around to find a solution. I redid Odin to stock kernel it. When it revived, it went into the loading screen. Yes! Progress! It was 99% done with loading when it froze on it. Fml. Battery pull, reboot, and it goes back into its habitual boot loop pattern. I can still access CMW, but it still crashes when I try to super wipe/wipe it.
I have to fix this because, well I bought this from someone with no warranty and using a no contract provider.
Help?
UPDATE: I was able to successfully superwipe my phone, then reinstall Mind Tricks as the rom of choice onto it. It doesn't freeze. Simply bootloops again and again. I don't know what to do.
eaudexs said:
UPDATE: I was able to successfully superwipe my phone, then reinstall Mind Tricks as the rom of choice onto it. It doesn't freeze. Simply bootloops again and again. I don't know what to do.
Click to expand...
Click to collapse
Firstly I suggest upgrading your recovery to 6.x via odin. Then superwipe. Redownload mind trick fresh, flash mind trick, wipe data/factory reset via recovery and try to boot letting it settle for about five minutes. If this fails, flash back to stock via Odin to rule out hardware faults.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Firstly I suggest upgrading your recovery to 6.x via odin. Then superwipe. Redownload mind trick fresh, flash mind trick, wipe data/factory reset via recovery and try to boot letting it settle for about five minutes. If this fails, flash back to stock via Odin to rule out hardware faults.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I've been looking through some how-to's but I can't seem to find how to upgrade recovery using odin. I can only find the .img file and instructions on how to do it via command lines. Any advice?
Thanks
Good suggestion but better yet ...... I had the same issue on cwm.... get twrp 2.2 look for the flashable download....... 2.3 has a few bugs so stick wit .2
Sent from my SGH-T989 using xda app-developers app
Definitely get twrp on it. Flashing twrp solved 99% of my problems running cm10. Zero rr in weeks. If I were you I would go back to stock for your device. After confident its running like it should. Then root and and go nuts.
I've personally never really had to pull the battery, very rarely. I'm worried about your ram. Could it b corrupted? A short somewhere? All unrecoverable.
I wonder if you could somehow mount your device using Linux. And run memory tests or drive diagnostics.(just thinking out loud).
Twrp is definitely a must. Good luck
Sent from my cm_tenderloin using xda app-developers app
Try doing complete wipes and reflashing a different more stable rom and see if it happens again. There are scripts to do complete and total wipes just to make sure you get a clean install (kind of like the others suggested) atleast yours can turn on so your not hard-bricked.
That's great how you guys are saying twrp solved your issues! It's really funny when cm10 supports cwm recovery. But op, let me see if I still have mine.
Sent from my SGH-T999 using Tapatalk 2
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
eaudexs said:
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
Click to expand...
Click to collapse
my sgs2 did this last month i did the same you did. after no fix i installed a cwmtouch through odin just to be able to restore a back up and worked flawlessly. After that i switched to TWRP again flashed it with no problem through odin and my s2 has been working fine ever since, but fyi i updated twrp to its 2.3.1.1 version and now i get errors can still restore but cant flash jb roms and can only do dirty flashes of ics roms
I'm currently in the process of trying to flash twrp. Is it uncommon that when I went into recovery, it also boot looped on me several time?
eaudexs said:
I'm currently in the process of trying to flash twrp. Is it uncommon that when I went into recovery, it also boot looped on me several time?
Click to expand...
Click to collapse
what version of TWRP are you trying to use? NO it does not bootloop
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
eaudexs said:
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
Click to expand...
Click to collapse
Nah my man you do not use the script with CWM6 thats your problem right there
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
eaudexs said:
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
Click to expand...
Click to collapse
Come on now the flashable version is in the thread...tisk tisk tisk also there are a few version in flashable form in there as well my friend. Got to get your hands dirty sometimes.... LOL Good luck
http://forum.xda-developers.com/showpost.php?p=32984410&postcount=380
Thank you my friend. I was able to finally find a 2.2 TWRP and I flashed it via odin. Did full wipes, full cache wipes, flashed a rom. Fixed permission and all that good stuff. Left it off for 10 minutes. Came back, it started running through initialization. About 4 minutes in, it crashes again. I'm starting to think this could be hardware problem.
eaudexs said:
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
Click to expand...
Click to collapse
Do not use scripts with the new CWM 6 as it will cause this. Manually wipe everything and do not use scripts. You can use scripts with twrp but not the latest cwm
Sent from my SAMSUNG-SGH-T989 using xda premium
When the update file downloads then it verifies but when it goes to install, it errors out and stops [see attached image]. There is also mention of Gmail.apk but when I go and look for it, it's not there. I have deleted the file and downloaded several time but wind up with the same result. I have put a copy in the ext sd card and tried from there but it will not install. Any ideas on how to do the upgrade?
Thanks, Dave
Correct me if I'm wrong, but it sounds like you're trying to do an ota when you're rooted (with a custom recovery). This won't work. Please read through this thread by CNexus about otas:
http://forum.xda-developers.com/showthread.php?t=2209418
It should give you everything you need to know.
Sent from my SPH-L710 using xda app-developers app
topherk said:
Correct me if I'm wrong, but it sounds like you're trying to do an ota when you're rooted (with a custom recovery). This won't work. Please read through this thread by CNexus about otas:
http://forum.xda-developers.com/showthread.php?t=2209418
It should give you everything you need to know.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Wow! I went through over 30 pages looking for a step by step and am quite confused as to the proper process. I am currently on 4.1.1 with LJ7 and have downloaded MD4 both DeOdex and Odex plus the MD4 kernal. The only thing I did when I got the phone was root it enough to make the hot spot app work.
JOB Dave said:
Wow! I went through over 30 pages looking for a step by step and am quite confused as to the proper process. I am currently on 4.1.1 with LJ7 and have downloaded MD4 both DeOdex and Odex plus the MD4 kernal. The only thing I did when I got the phone was root it enough to make the hot spot app work.
Click to expand...
Click to collapse
Thanks for reading all of it. Most people would just look at the first page and the last page and say "Oh, it's not there!" That being said, I hope you have a better understanding of what's going on when you get an OTA notification.
Now that's been said, I had written a post on another thread that covers the steps A-Z. I've linked it and quoted it below.
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, it should have gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
JOB Dave said:
The only thing I did when I got the phone was root it enough to make the hot spot app work.
Click to expand...
Click to collapse
I don't think there's a way to be "just a little rooted"
:silly:
Follow topherk's directions to a tee, and you'll be fine.
As a noob, I was scared to death knowing that I was rooted and I was going to get an OTA!
xda-developers has everything you need. The files, the guides, the support from senior members.
Relax and have fun...
---------- Post added at 06:11 PM ---------- Previous post was at 05:54 PM ----------
BTW, I flashed freeza's md4 odexd rom (cause a stock sg is odex), the md4 firmware, and the optimized kernel. Flashed (installed) them in that order. Just download them from the site onto your phone, and boot into recovery to flash each. Probably too paranoid, but i rebooted after each flash *just* to be sure). Cleared dalvik cache after installing the rom. Ummm, and ran checksum on my files before I installed them (I use md5 checker app).
Thanks, that got me started. now I have to figure out which rom and kernal I want to install.
ROMs come with kernels already, so if you're unsure ATM, just flash a ROM and then later you can check out kernel switching. Just make sure that the kernel you are flashing is for your ROM version (4.1.2, 4.2.2, etc) and for your type (AOSP, Touchwiz).
Since you are just starting out, I would suggest TPR (The Peoples ROM) or MOAR (Mother of All ROMs). Both in Android Dev section (as opposed to Original Android Dev).
TPR also has AROMA installer, so it lets you pick what apps, kernel, and other goodies you want to flash and basically on-the-spot customization.
Downloaded the file MD4_update_FULL_Odex.zip and followed the instructions above and got zip signature failure, see photo. I am wondering if it worth doing the upgrade.
~Dave
In twrp, under settings, you can uncheck the zip file verification option. Most of the time it gives you that error, even though the zip is fine.
Sent from my SPH-L710 using xda app-developers app
topherk said:
In twrp, under settings, you can uncheck the zip file verification option. Most of the time it gives you that error, even though the zip is fine.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That worked!! Thanks for all your help.
Am looking at the About screen and the build says I'm on MD4 but the Baseband is still LJ7, do I need to be concerned about that?
JOB Dave said:
That worked!! Thanks for all your help.
Am looking at the About screen and the build says I'm on MD4 but the Baseband is still LJ7, do I need to be concerned about that?
Click to expand...
Click to collapse
Baseband has to do with what modem/radio you are on. This is independent of your ROM, so the two can be different version numbers.
The modem impacts your mobile data coverage and speeds. What you wanna do (if you wanna find the best modem for your area) is to switch modems and run each one for a week. Then switch. After you've gone through a couple modems, single out the ones that qork best and test those out till hou find the best and/or fastest one for your area and the places you frequent.
Hi i want to apply the OTA (MD4) and keep my root acces, so my question is, if is possible to use voodoo root keeper app to apply this update. thanks in advance
juancaperez2000 said:
Hi i want to apply the OTA (MD4) and keep my root acces, so my question is, if is possible to use voodoo root keeper app to apply this update. thanks in advance
Click to expand...
Click to collapse
Hey Juan,
I'm assuming you just got the notification for the OTA. You actually don't have to apply it to get the latest and greatest for our phone. All you have to do is flash Freeza's Stock Rooted Rom (You'll want the DeOdex MD4 Rom). It'll give you the most up-to-date Stock Rom with Root. I've linked and quoted a previous post I made which will give you directions to flash it. Also, CNexus has done a great guide about OTAs over in the general sub-forum. I suggest giving that a look-through.
Also, just a note on the flashing sequence below: In step 4 below, if you're coming from a stock Rom and you're going to a stock Rom, all you have to do is wipe Cache and Dalvik Cache. If you're going to a different Rom, it's best to do a full wipe (in my opinion).
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
topherk said:
Hey Juan,
I'm assuming you just got the notification for the OTA. You actually don't have to apply it to get the latest and greatest for our phone. All you have to do is flash Freeza's Stock Rooted Rom (You'll want the DeOdex MD4 Rom). It'll give you the most up-to-date Stock Rom with Root. I've linked and quoted a previous post I made which will give you directions to flash it. Also, CNexus has done a great guide about OTAs over in the general sub-forum. I suggest giving that a look-through.
Also, just a note on the flashing sequence below: In step 4 below, if you're coming from a stock Rom and you're going to a stock Rom, all you have to do is wipe Cache and Dalvik Cache. If you're going to a different Rom, it's best to do a full wipe (in my opinion).
Click to expand...
Click to collapse
thanks!!! i tought that i need do like qbking77 did on his videos using oding for i can keep my data but you'r right dirty flash can work too (stock to stock)
juancaperez2000 said:
thanks!!! i tought that i need do like qbking77 did on his videos using oding for i can keep my data but you'r right dirty flash can work too (stock to stock)
Click to expand...
Click to collapse
That's right, dirty flashing should work fine. If you're noticing any major issues (FCs, reboots, etc), you might want to use Titanium Backup to back up your important stuff and do a clean flash. But hopefully the dirty flash will be good.
I saw this post earlier, and was going to reply pretty much the same thing. Then I said to myself nope im going to leave it alone Topherk will come by soon enough with a way better reply and exact instructions!! :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Keep up the great work
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
I saw this post earlier, and was going to reply pretty much the same thing. Then I said to myself nope im going to leave it alone Topherk will come by soon enough with a way better reply and exact instructions!! :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Keep up the great work
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks Ed, I appreciate the feedback.
Thankfully, I put the hard work in a while ago, so now (for most questions) all I have to do is paste that one post and I'm good to go.
As an aside: yesterday I helped a friend root his GS3 and realized I'm much better at explaining things here on XDA than I am in real life. I kept jumping ahead of myself and trying to explain about wiping /system before I even explained what a custom Recovery is. I should've just asked him to post a question "how do I root" and I could've done a better job explaining it, haha.
Sorry for my total noobness. I've just recently started this whole root awesomeness and I've hit a snag...... I'm sure there are many threads about my problem but I can't find one. I had CM 10.2 on my AT&T galaxy s3 and things were smooth and stable. Decided to try the "Collective" 4.3 ROM and SixShooter kernel. I put the zips in the phone (used the same gapps zip that was in there because I believe the Collective ROM is based off of the CM 10 ROM). Did a backup, then wiped chache, dalvick cache, system, and data (using TWRP recovery). Then did a multiple install of all three files in one action because TWRP lets you. so why not do it?
Rebooted, and I get the samsung logo, then sixshooter, then blank screen, vibration, pause, another vibration, then it starts all over. I can go into odin mode, or pull the battery to get it to stop.
Tried using odin to flash the .tar file, but it says PASS! and then the phone just automatically starts the loop again.
Was installing all 3 files (ROM, KERNEL, and Gapps zip files) at the same time a bad move?
I tried going back into recovery and it gives me the CWM recovery. Do I have TWRP AND CWM at the same time? Wierd. Tried wiping cache, and dalvik cache again and then rebooting, it still loops.
I'm at a a loss. I've watched a ton of videos and they all pretty much just say to find the right .tar and use odin to get back to stock. Like I said I've tried this and it just starts the loop again. Please help!! (I don't know a thing about ADB/terminal commands so if thats the fix I'll need my hand held) If theres a link to a thread that tells me how to get out of this I'd sure appreciate it. I greatly appreciate anyone who can take the time to explain to me what to do......
I would suggest booting into recovery and do the full wipe. Then just flash the ROM and gapps. If you're still bootlooping it could be a bad download of the ROM so if youve still got cm10.2 sitting around flash it instead. If that works I would look at downloading collective again. If not well maybe someone else has some input.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Ok, I just read the op again, and isn't the sixx shooter kernel packaged with the ROM? Also it states to factory data reset, wipe dalvik, install ROM, and the phone should reboot by itself do to a script, let phone settle, THEN boot back into recovery, flash gapps, wipe cache, reboot, enjoy! Maybe u shouldn't have flashed everything at once?
Yep, I'm a total tool. I installed everything in one action. ROM, gapps, kernel. Guessing I didn't need the kernel. And I should have read more closely the collective thread as it says to do the ROM. let it reboot, settle, etc. So the install all of them in one step is where I forked it up. I got it though. Pulled my head out and got the newest TWRP .img file and updated my recovery with odin. ROM is loaded and sweet as all get out!!
Crisis averted. Don't know what I would have done at work tomorrow without my podcasts and pandora! Thx for the help though. Love this forum.
Hmm. Okay, guess I don't have it completely sorted. I have gotten it to boot into the OS, let it sit a few. turned it off and tried to boot into recovery with vol+/home/power but it just starts it back up to the OS? Does the collective ROM change the way you get into recovery?
LilHoov said:
Hmm. Okay, guess I don't have it completely sorted. I have gotten it to boot into the OS, let it sit a few. turned it off and tried to boot into recovery with vol+/home/power but it just starts it back up to the OS? Does the collective ROM change the way you get into recovery?
Click to expand...
Click to collapse
Should have the four way reboot in the power menu. Long press the power button, while the phone is on, select reboot recovery. See if that helps...
Nevermind, I got it. lol
Gotta let go of that power button after vibration......man it's late