I'd like to start by apologizing for what is probably the 9,000th "help, I've bricked my phone!" thread. I did some searching, and while I found many, I wasn't able to find one that both dealt with my specific issue, and did so assuming a level of newbishness appropriate for me.
Months ago, I rooted my AT&T Galaxy SIII, and installed CM10. It's been all candy and rainbows since. This morning, I somewhat foolishly decided to update from a nightly I installed in October/November, to the January 7 CM 10.1 nightly, using the built-in updater I had previously used to switch to a nightly.
It worked...sort of. I guess I should have cleared my cache or something ahead of time, because almost all of my GAPPS stopped working. Woops! Figuring that I should probably stop dicking around with my phone until I learned a bit more, I just went back and told the phone to switch back to the nightly I from October/November that I was previously using.
It didn't work. My phone now reaches the CM boot animation and just...sits there. And sits there. And sits there. To complicate the issue, I cannot get the phone to boot into recovery mode (although admittedly, I'm too thick to know what I'm meant to do once I'm there anyway). I CAN get the phone into download mode, but not being sure what I should do there, I thought it best to consult you all on what to do next.
I'm happy to give any additional information needed, and I hope it goes without saying that I am extremely thankful for any help you all can offer.
Try to get it back into recovery by taking the battery out, putting it back in and then holding volume up, home, and power. If you are sure you can't get it into Recovery, but know for sure you can get it into Download, go into Download and flash stock and go from there. These aren't bricks. These are just whoops. Lol.
If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.
Actually, you should always wipe cache and dalvik when flashing the update. If it is a major update like 4.1.2 to 4.2.1, then you should wipe cache, wipe dalvik, Factory Reset, Format System then flash your ROM.
Move important files to SD using twrp file manager. Put rom on SD with gapps. Format internal, wipe caches, format system, factory reset, load ROM, load gapps. Reboot.
Sent from a Horny Pink Pony
smelenchuk said:
If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.
Click to expand...
Click to collapse
I did this, being careful to follow all the instructions provided. Odin seemed to think everything worked, and after about 10 minutes, it rebooted the phone.
However, it still gets stuck. Now, since CM is no longer installed, it just sits at the SAMSUNG logo forever.
It still boots into download mode, and will now boot into recovery as well. Any suggestions?
naporeon said:
It still boots into download mode, and will now boot into recovery as well. Any suggestions?
Click to expand...
Click to collapse
Boot to recovery and clear data and cache.
smelenchuk said:
Boot to recovery and clear data and cache.
Click to expand...
Click to collapse
Worked like a charm, thanks! Can't believe after all that trouble, I didn't think to do that myself. >.<
Related
I rooted and ran a couple diff custom ROMs: cm10.1.3 and infamous alpha, both with oc kernels (never set mhz past 2051). Began getting random reboots, alot while running the Alpha ROM, and a couple while running cm10.1.3 which I thought was weird because its a RC. should be stable, right? Anyway, got tired of RRs, so I decided to unroot and got stock, till I had some free time.to tinker with it. Well guess what, getting RRs EVEN IN UNROOTED STOCK. Any ideas?
I'm not exactly sure what steps you have taken to get back to Stock, where you're still having random reboots, but I'll let you know what I've done in the past to get to Stock which resolved the issues:
- Factory reset device from device. Save and/or move your Internal files/data prior as you'll be wiping Internal. I'd remove my extSdCard prior to Factory reset and after moving files to it.
- ODIN Samsung Stock Firmware
http://samsung-updates.com/details/9595/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUAMDL.html
- After the device boots, you'll probably get stuck on the Samsung splash boot screen. After a few minutes - -
- pull the battery, replace the battery but Don't power the device on
- Place device in Stock Recovery mode by pressing Power and Vol up buttons at the same time.
Release the buttons when you see the blue letters appear in the upper left hand corner of the screen.
- Scroll to Factory reset using the volume buttons.
(During the above process, you'll see the Android on its side with a Red X on him/her.)
- press the power button to lock in Factory reset
Let the Recovery scroll through its script
(during this process the Android will come to life )
- After the script is completed which takes less than a minute or so, scroll to reboot and select it with the power button.
- the device will now boot.
Important: while the device is booting, the screen will stay on the T-Mobilessplash screen for what will seem forever. Don't panic. The screen will show T-Mobile across the screen for about 15 or so minutes. Could be a little more or a little less. The device will then continue and complete the booting cycle.
Some notes:
1) during the above process, I have removed my extSdCard card as I didn't want tottake a chanceiit would be wiped. ODIN doesn't wipe extSdCard card but I don'tbneed it during theiprocess so I remove it in case Murphy decides to pay a visit.
2) during ROM flashes, I've experienced almost every issue youccan imagine. This occurred while using TWRP 2.5.0.2, but only when flashing ROMs with Aroma. For months prior, I had zero issues.
The problems I was experiencing were:
Random reboots, splash screen freezes, bootloops, installation of choices in Aroma which only partially installed, issues which didn't seem to havesan answer, and when you found the solution, that solution wouldn't work when the issue appeared again.
- constantly ODINing back to stock
- sometimes in Recovery, I couldn't get past the TWRP lockscreen, and only wiping Internal SD resolved the issue so I could do a Factory reset. I was doing this so often, that I left all files on my extSdCard so Iewouldn't lose my data when I had to wipe internal. It was faster this way as I didn't have to keep moving stuff back & forth.
After endless hours of troubleshooting and aggravation, I changed Recoveries.
I installed Philz Touch Recovery, and I have had Zero issues since installing it about 3 or so weeks ago, which have included multiple ROM flashes with Aroma.
I didn't want to switch Recoveries as I was very used to TWRP, but I just couldn't deal with the new found issues I was having so I made the switch and haven't looked back. Some people don't have issues with TWRP, but I wasn't one of them
Hopefully you can relate to some of my experiences which I have written above, which may help you to resolve some of the issues you're experiencing.
Yes. Thats the file I used and also the steps. I dont know what the deal is.
twatts723 said:
Yes. Thats the file I used and also the steps. I dont know what the deal is.
Click to expand...
Click to collapse
If you:
Wiped Internal SD
ODINd Stock Firmware
which flashed successfully
and are still having random rebooting.....
I can only suggest:
Check your device settings, if you haven't done so already to insure you're running:
Stock ROM
Stock modem/radio
And that all settings are stock.
If everything checks out, I can only suggest to:
Download the Samsung Stock Firmware file again
Check the md5 checksum
ODIN Samsung Stock Firmware again
And see how it goes.
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
twatts723 said:
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
Click to expand...
Click to collapse
Glad everything worked out for you.
Don't shy away from custom ROMs though, as you'll be missing out on some good stuff
As a note, there can be many thinks which can contribute to issues after the installation of a Custom ROM, Kernels, etc. such as:
Bad downloads, corrupted files, app conflicts, dirty flashes instead of Full wipes, etc., etc.
Another issue can be related to the Recovery you are using.
I had many, many issues regarding flashing ROMs which installed with Aroma.
Prior to ROMs w/Aroma, I had Zero issues.
I suggest using Philz Touch Recovery.
In case you don't have it installed and want to try it, I'll post a link to the download page.
Flash the proper file for your specific carrier.
Install the tar file with ODIN or
Flash the zip file with your Recovery......
Well, I come from sgs2. On that device, I could flash everything through cmw, and just use darkside super wipe and darkside cache wipe. No problem. Every rom from cm to amatuer custom blibbidy blobbidy, no problem. When I rooted my s4, I went straight to twrp because everyone said it was better. I flashed cm10.1.3 rc - rr. Infamous alpha v.7, which was supposed to be stable - rr. I went back to stock, rooted again, and kept stock tw, and only flashed ktoonz kernel, which is supposed to be one of the best for this device. Everything ran great, but guess what - rr. So I gave up. Went back totally stock. Working a lot of hours at work right now. We slow down after thanksgiving, so I'll probably start flashing again around that time. Thanks for thw help though
cheers.
So my phone is stuck in bootloop. and I cant get my phone to boot correctly.
To start, I was running 4.2.2 AOKP for about half a year and it started to not work as well. Force closing alot, freezing etc. So I decided it was time to update. While I was running AOKP, I experienced bootloop almost every time I turned off my phone. This became regular, but by pulling the battery and trying again (sometimes I had to do with a few times) it always got working again.
I went and found the new 4.3 Carbon ROM and decided that looked cool and would be a nice upgrade. So I downloaded it and the new 4.3 gapps. Put them on an external sd card, and put it into my phone. I then booted into CWM and did a factory reset. Then I went and installed the Carbon from the external sd, installed gapps, and rebooted immediately. I was then, and still am, stuck in a bootloop.
I can restart my phone go back into clockwork.
But I cant get the phone, despite all my efforts, to boot correctly. I have tried to wipe caches, wipe dalvik, format system. All of it. yet I cannot boot correctly.
I really need a working phone. Any help would be really great.
Thanks all
Also, I am using TWRP 2.6.3 to do the flash of the Carbon after it failed the first time
Moheemo said:
Also, I am using TWRP 2.6.3 to do the flash of the Carbon after it failed the first time
Click to expand...
Click to collapse
2.6.3.0 seems to be giving many people issues. You need to install 2.6.1.0.
And is your radio up to date? Only 2 work...the new T-Mobile and Telus radios.
After those 2 things are taken care of, you should be fine. Tho lots of things can cause boot loops, and there's many.. many posts about it. If my suggestions don't help.....Search and read up. Try some various fixes.
Maybe try a different rom too.
Sent from my cellular telephone
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
Hope you did a nandroid backup in recovery? Restore it if so. If not, you may need to start from scratch and Odin flash stock rom, flash recovery and root again.
Sent from my cellular telephone
Moheemo said:
So my phone is stuck in bootloop. and I cant get my phone to boot correctly.
To start, I was running 4.2.2 AOKP for about half a year and it started to not work as well. Force closing alot, freezing etc. So I decided it was time to update. While I was running AOKP, I experienced bootloop almost every time I turned off my phone. This became regular, but by pulling the battery and trying again (sometimes I had to do with a few times) it always got working again.
I went and found the new 4.3 Carbon ROM and decided that looked cool and would be a nice upgrade. So I downloaded it and the new 4.3 gapps. Put them on an external sd card, and put it into my phone. I then booted into CWM and did a factory reset. Then I went and installed the Carbon from the external sd, installed gapps, and rebooted immediately. I was then, and still am, stuck in a bootloop.
I can restart my phone go back into clockwork.
But I cant get the phone, despite all my efforts, to boot correctly. I have tried to wipe caches, wipe dalvik, format system. All of it. yet I cannot boot correctly.
I really need a working phone. Any help would be really great.
Thanks all
Click to expand...
Click to collapse
flash stock rom zip via odin then you should be good to root and try to flash another custom rom again:good:
I was experiencing a lot of issues within the last few days so I decided to wipe my phone and reinstall the rom. I've been on the 7/11 build of CM 10.1 since it came out. The phone has been a little wonky lately out of the and wouldn't reboot or go into recovery. I managed to get into Recovery through the ROM Manager app. The power button seemed to be a little touchy. I did a factory reset and wiped the cache. Before I could do anything further it rebooted and brought me into the Rom fresh, making me log into my google account and set up the phone from the start.
The issue now is that the phone is not showing as being rooted anymore. Is there something I can do to get root back from this point? Do I just go back into Odin and root as if I’m doing it for the first time? Any help would be greatly appreciated.
Jaypcarlson said:
I was experiencing a lot of issues within the last few days so I decided to wipe my phone and reinstall the rom. I've been on the 7/11 build of CM 10.1 since it came out. The phone has been a little wonky lately out of the and wouldn't reboot or go into recovery. I managed to get into Recovery through the ROM Manager app. The power button seemed to be a little touchy. I did a factory reset and wiped the cache. Before I could do anything further it rebooted and brought me into the Rom fresh, making me log into my google account and set up the phone from the start.
The issue now is that the phone is not showing as being rooted anymore. Is there something I can do to get root back from this point? Do I just go back into Odin and root as if I’m doing it for the first time? Any help would be greatly appreciated.
Click to expand...
Click to collapse
not sure how you could lose root on CM 10.1 but you could use odin to flash back to stock and start over, or you can just flash the .tar file for the 2.6.1.0 TWRP recovery in odin and that will root your phone with out having to go all the way back to stock.
Heres the link for TWRP 2.6.1.0 http://goo.im/devs/OpenRecovery/hercules/openrecovery-twrp-2.6.1.0-hercules.tar
hey i had the same thing happen to two t989's that i own, one i had flashed the newest chameleon os on it, the other I had revolt.Basically I tried numerous ways to fix it, even downloading and flashing superuser zip again. thing is, I still had access to custom recovery, but no root. Nothing worked, I ended up finding out that the super user program was the issue. Try downloading this one, from this link, and flashing thru the recovery, it will work. No need to reflash anything else.
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Go on dev options and set root access to apps and adb
So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Iantuition said:
So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
Click to expand...
Click to collapse
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
bellifritz said:
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
winosxbuntu said:
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
Click to expand...
Click to collapse
Okay. Which official file though? and should I clear the system and boot partitions too?
Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Okay. Which official file though? and should I clear the system and boot partitions too?
Click to expand...
Click to collapse
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
winosxbuntu said:
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
Click to expand...
Click to collapse
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Hit the power button to make the screen go to sleep. Hit the power button again to wake it up. Nothing should be crashing while you are on the lock screen so just hold the power button until the power menu appears and select power off. Once it powers off hold the volume up, home button and power button until you see the blue words in the upper left corner of the screen I believe it says loading recovery. Release the power button but continue holding the other 2 buttons until recovery loads. Now wipe data, cache and under advanced wipe dalvik cache. Reboot and everything should quit crashing but you will have to setup your account and apps again. That is the only way that I can get stock touchwiz 4.3 nandroids to work.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Iantuition said:
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Click to expand...
Click to collapse
it will work, i agree with what bell said. unless its hard bricked then no worries just keep calm and fix the damn phone
Hello all!
This is my first foray into the world of custom Android systems, and I'm having a hell of a time with it... if somebody would be able to help me out, I would greatly appreciate it.
First off, the situation:
I am on Sprint, and I recently bought a Samsung Galaxy S3 (SPH-L710) from Sprint to use as a backup phone, I used it for a while on Stock, then deactivated it so I could give it to my wife. First though, I wanted to put a custom ROM on it, and experiment/play around a bit and see what this world of options could do for me. Long story short, I ended up flashing an AICP ROM, and everything seemed to go smoothly, but when I went to activate the phone on my account again and it would not work no matter what I tried (details below). I figured maybe I could activate on the stock setup then just restore my custom setup, so I tried to revert to my stock ROM backup and I couldn't do anything because I was constantly getting messages that various programs had closed... Then I tried to wipe and restore my custom ROM backup and I get stuck in a boot loop... so I tried to flash a stock recovery and I get stuck in a boot loop... I'm out of ideas here, and now I'm stuck with a phone I can't use or do anything with, and I can't activate.
Details:
The initial rooting/install process seemed to work ok, and was fairly straightforward. I followed various guides on http://galaxys3root.com/ to get my phone rooted and backed up (Don't recall which ones now, but I've read through so much by now I don't know if it matters...).
My phone:
Samsung Galaxy S3 (Sprint) SPH-L710
Modem: L710SPRDNJ2
My Desktop:
Debian Linux
Here's the steps I performed:
Rebooted phone in Odin mode
Downloaded CWM S3 Sprint Recovery from the http://galaxys3root.com/ website (can't find the link any more)
Flashed the CWM recovery using Heimdall then rebooted phone into CWM
Installed SuperSU through CWM, then rebooted
Checked that the phone was rooted successfully (it was), then ran Titanium Backup on the whole device to my SD card, then copied the backup files to my desktop computer
Rebooted into CWM, and performed a backup through CWM, then rebooted and copied the CWM backup to my desktop.
Downloaded AICP Rom for my phone from here: http://downloadandroidrom.com/file/GalaxyS3Sprint/roms/AICP/aicp_d2spr_lp-10.0-RELEASE-20150707.zip, put it on my SD card, then installed it through CWM and rebooted
At this point, I was happy with how everything was working, so I did some minor theme customizations then made another backup through CWM, and copied it to my computer, but I did NOT run Titanium this time...
After all of this, I tried to go ahead and activate it through the Sprint web service. This process failed continuously with an unhelpful error message of "Sorry, this device can't be activated right now". I then got on Chat to see if they could activate it manually, and then the problems began. They did their thing activating the phone, but when I booted up I got no data connectivity, and couldn't make calls, and the SIM was not changing over to the new number. I was on the chat with them for over an hour trying to get the situation resolved, but that finally ended when they started asking me to punch in ## codes, because I discovered that none of them worked on my custom ROM. Some quick research told me that this was non-trivial to get around so I had them switch everything back and I started researching the issue.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1626638&highlight=sph-l710 that looked like it would let me do what I needed from the custom ROM, but I couldn't tell if it would fix my problem for sure, so I figured "I'll just restore my stock setup from that backup I took, activate it and update, then start over". This is when things got really frustrating...
First I rebooted into CWM, went to 'backup/restore', and restored my stock backup
Rebooted, and as soon as I got past the lock screen, I get inundated with messages of various apps being closed unexpectedly.
I researched a bit, discovered the issue may be caused by stale dalvik cache, so I rebooted into CWM, cleared the dalvik cache, formatted the /cache partition, then tried to restore the stock backup again, but this time I get stuck in a boot loop.
I then rebooted into CWM, tried to restore the backup of my AICP ROM, only to be stuck in a boot loop as well.
Trying to get into any usable system, I rebooted to CWM, cleared dalvik cache, then formatted /cache, /data, and /system just to be sure, and re-flashed the base AICP ROM I started with. This worked fine, and before long I had stock AICP back
Since I still couldn't get the phone to activate in the custom ROM, and my backups are apparently completely useless, I rebooted into CWM, wiped dalvik, /cache, /data, and /system again and tried to install a different stock ROM I found in the XDA forums (here: http://forum.xda-developers.com/galaxy-s3-sprint/development/stock-rom-4-4-2-t3010642) only to be greeted by another bootloop
At this point I've spent well over 24 man-hours trying to get this to work, reading, researching, flashing, etc all to no avail. Nothing I do seems to work, and it seems like every article, tutorial, or forum thread I read either has nothing to do with my device, is too old, or doesn't describe my problem.
I'm at wits end, and am so frustrated I'm ready to just give up and smash this device and buy a new one... My questions to the community are as follows:
I know I screwed up on a couple of things, but in my initial research of doing this there was no indication that these were even things I needed to watch out for... Is there any more organized sources of information for doing this sort of thing?
Does anybody else out there use Sprint on a custom ROM, and if so how you you pull this off
Where else have I screwed up, and how can I fix this situation? (My end goal is still to get the S3 onto Sprint with a custom ROM)
What can I do differently next time? I would like to figure this out and do it to other phones and devices I have, but if it's this much trouble every time, I just don't have the time to mess with it.
Thank you in advance, and I appreciate any information that the community can provide.
This sounds like a CWM problem to me. If I were you, I'd boot the phone into Odin Mode and flash TWRP ( www.twrp.me ) then try flashing the latest aicp nightly downloaded from the official site ( www.aicp-rom.com ). Check the md5sums on everything! Then maybe try flashing a touchwiz ROM and activating your phone. Remember that you need to wipe the internal storage when you go between KitKat and lollipop.
I'm fairly certain you have to do activation with the stock Touchwiz roms -- once the phone is activated you can flash a custom.
You should go into recovery and wipe everything (System/data/etc) EXCEPT for the External SD Card
Power off - pull the battery for a few - power on directly into download mode
Odin NJ2 back onto the phone and reboot and activate it (skip through most of the setup since you'll flash a custom after)
Once you know it's activated and working under the stock Touchwiz, then again power off and Odin TWRP recovery
Then you can go back into recovery, wipe everything except External SD, and flash the custom rom back on.
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
afarris01 said:
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
Click to expand...
Click to collapse
Get rid of them. TWRP can't restore CWM even if the backup is good