So I've have Shostock 3.0.4 currently on my phone, and yesterday I noticed 3.0.5 was release so of course I used CWM and flashed the new version. Then I reboot and it won't load past the samsung gs2 screen. So luckily I had a backup ready and restored it back to working order, version 3.0.4. Now I didn't perform a full wipe, and thinking through it logically... I did change from Shostock's usual boot animation awhile back, which i changed to this one:
http://forum.xda-developers.com/showthread.php?t=1529499
Is that the cause of my phone not being able to boot after flashing without a full wipe? If so do I just need to put Shostock's boot animation back, and then I'll be able to successfully upgrade to 3.0.5? And if that's correct can someone upload their Shostock bootanimation.zip file for me?
If that isn't the issue, is there any other way to solve this without doing a full wipe throughout the process?
Thanks
No that's not the cause and I believe you have to do a full wipe or try re downloading it
Sent from my SGH-I777 using Tapatalk 2
I'm running a different boot animation and.it didn't stop me from flashing to .5.
I'd just try again. The usual wipe cache, davlik, fix permissions,flash....
Where are you storing the BA? System/media or Data/local?
BROKKANIC said:
I'm running a different boot animation and.it didn't stop me from flashing to .5.
I'd just try again. The usual wipe cache, davlik, fix permissions,flash....
Where are you storing the BA? System/media or Data/local?
Click to expand...
Click to collapse
system/media
wittitdew said:
system/media
Click to expand...
Click to collapse
Clicked on that link you provided. Maybe flashing that ba changed something or screwed something up.
I just push the new animation zips I have into that folder instead of flashing it with cwm
Wipe. As stated. Boot animation wouldn't stop yer phone from booting.
Sent from my SGH-I777 using Tapatalk 2
BROKKANIC said:
Clicked on that link you provided. Maybe flashing that ba changed something or screwed something up.
I just push the new animation zips I have into that folder instead of flashing it with cwm
Click to expand...
Click to collapse
Yeah I didn't flash with CWM I copied the .zip file into system/media
If I am not mistaken, deleting the bootanimation.zip will just give you a black screen till it boots.
LiLChris06 said:
If I am not mistaken, deleting the bootanimation.zip will just give you a black screen till it boots.
Click to expand...
Click to collapse
Removing the bootanimation.zip results in the built-in boot animation running. In SHOstock2 it is a stylized s, the galaxy sII logo, with samsung GalaxySII at the bottom.
creepyncrawly said:
Removing the bootanimation.zip results in the built-in boot animation running. In SHOstock2 it is a stylized s, the galaxy sII logo, with samsung GalaxySII at the bottom.
Click to expand...
Click to collapse
Depends if the .qmg was removed to save space, I know I do that myself not sure who else does.
So yea your right, you will get the stock animation.
Okay so here's some of the steps I've done today so far.
1. Gotten Shostock2 bootanimation.zip back to default, the one that comes with Shostock2.
2. Flashed Shostock2 3.0.5 via CWM 5.5.0.4, which I've had installed and used multiple times without problems even flashed Shostock2 3.0.4 itself with this... from here (under general downloads header): http://teamhacksung.org/wiki/index.php/Experimental:GT-I9100:How_to_install
3. Says it installs successfully, I reboot, shows the Samsung Galaxy SII screen, and I let it sit there for 10 mins or so, nothing.
4. Boot into download mode, flash to UCKK6 stock, rooted via Odin from my PC from here: http://forum.xda-developers.com/showthread.php?t=1286432
5. Installs fine, boot into android 2.3.6 don't do anything...
6. Flash that same CWM as above via Odin. Boot into CWM full wipe of data, cache, everything wiped. Fixed Permissions.
7. Flash Shostock2 3.0.5 directly from that UCKK6 rom, same result... no boot.
8. Use Odin again to get UCKK6, and CWM and just do a restore back to Shostock2 3.0.4... the starting a place.
So anything left to do?
Are you wiping data between all these flashes?
I'm pretty sure I was for the last few steps, just to try to get it to at least work. But not really at the beginning because I wanted to see if that way would work too.
wittitdew said:
Okay so here's some of the steps I've done today so far.
1. Gotten Shostock2 bootanimation.zip back to default, the one that comes with Shostock2.
2. Flashed Shostock2 3.0.5 via CWM 5.5.0.4, which I've had installed and used multiple times without problems even flashed Shostock2 3.0.4 itself with this... from here (under general downloads header): http://teamhacksung.org/wiki/index.php/Experimental:GT-I9100:How_to_install
3. Says it installs successfully, I reboot, shows the Samsung Galaxy SII screen, and I let it sit there for 10 mins or so, nothing.
4. Boot into download mode, flash to UCKK6 stock, rooted via Odin from my PC from here: http://forum.xda-developers.com/showthread.php?t=1286432
5. Installs fine, boot into android 2.3.6 don't do anything...
6. Flash that same CWM as above via Odin. Boot into CWM full wipe of data, cache, everything wiped. Fixed Permissions.
7. Flash Shostock2 3.0.5 directly from that UCKK6 rom, same result... no boot.
8. Use Odin again to get UCKK6, and CWM and just do a restore back to Shostock2 3.0.4... the starting a place.
So anything left to do?
Click to expand...
Click to collapse
Where are you storing the ROM zip, internal or external? Try switching it.
BROKKANIC said:
Where are you storing the ROM zip, internal or external? Try switching it.
Click to expand...
Click to collapse
Been going with the internal as the developers instruct usually
Related
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
i have the exact same problem!
InFa_ReD_1 said:
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
Click to expand...
Click to collapse
try download it again. Sound like a corrupted package
Sent from my GT-I9100 using Tapatalk
rembrandtlnx said:
try download it again. Sound like a corrupted package
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I tried and got the samething. I also tried a different cm nightly and got the same results.
InFa_ReD_1 said:
I tried and got the samething. I also tried a different cm nightly and got the same results.
Click to expand...
Click to collapse
me2 only stock roms work for me =(
I think there was an issue with the version of CWM used on the CF-roots since it's been modified by CF and because it's an older version.
After you've rooted with CF, try flashing a kernel on there with a newer version of CWM on there (I used codeworkx's kernel from the Cyanogenmod wiki I've attached below with CWM 4.0.1.4).
Once this kernel is on there, then try flashing the CM7 ROM as per this thread. I prefer flashing from recovery myself, but it's your call.
Make sure you flash it twice in a row if you're having issues.
The problem, as stated above is that cf root kernel installs a modified version of CWM that won't work with CM7. Another thing is you have to flash a stock KH3 because KI3 has the new bootloader (unless you flashed KI3 with the old bootloaders). Then, you have to flash the codeworkx kernel so you get a compatible version of CWM. Once in CWM clear data factory reset + clear cache partition + clear dalvik cache (from advanced).
THIS IS IMPORTANT: Flash the ROM from sd card and when finish do not reboot device, just flash it again without wiping anything in between, just 2 consecutives "install from sd card". When this is done you can reboot the system and then enter again to CWM to flash the google apps .zip file that you can download from the CM7 thread.
Hope this helped. When I flashed CM7 i had exactly the same problem and went back to stock cause it was a pain in the ass to flash it fr the first time. But once you get in CM7, everything becomes great and easy, and you can update the nighlies directly from ROM manager without doing any wiping. You just can't use ROM manager when getting to CM7 for the first time.
InFa_ReD_1 said:
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
Click to expand...
Click to collapse
DO NOT use cf-root to install CM7. It's stated by Codeworkx a lot of times in CM Q&A thread. Just flash his kernel to get cwm.
http://forum.xda-developers.com/showthread.php?t=1118693
Now you have the original cwm recovery (from Koush). Boot into recovery, Wipe data, cache, dalvik.
Install CM7 twice in a row without rebooting.
Then flash gapps (without rebooting) http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip.
Now reboot. Wait for a few mins since system has to build dalvik cache. And you're all good to go
Worried about yellow triangle? Get a usb jig.
Siyah kernel 2.0 supports CM7 and miui. So....have fun.....!!
droidphile said:
DO NOT use cf-root to install CM7. It's stated by Codeworkx a lot of times in CM Q&A thread. Just flash his kernel to get cwm.
http://forum.xda-developers.com/showthread.php?t=1118693
Now you have the original cwm recovery (from Koush). Boot into recovery, Wipe data, cache, dalvik.
Install CM7 twice in a row without rebooting.
Then flash gapps (without rebooting) http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip.
Now reboot. Wait for a few mins since system has to build dalvik cache. And you're all good to go
Worried about yellow triangle? Get a usb jig.
Siyah kernel 2.0 supports CM7 and miui. So....have fun.....!!
Click to expand...
Click to collapse
Thanks. Can i flash the orginal CWM over top the CF CWM?
InFa_ReD_1 said:
Thanks. Can i flash the orginal CWM over top the CF CWM?
Click to expand...
Click to collapse
I did it and didn't have any problems, just follow the steps as I posted above.
tomascunill said:
I did it and didn't have any problems, just follow the steps as I posted above.
Click to expand...
Click to collapse
Great thanks for the help it worked I'm now running CM7. One thing though I can make calls but have lost my network connection. Can someone help me with this? Sorry for all the questions I'm new to the whole smartphone business. Thanks.
Ok all fixed up thanks for all your help.
I just did the biggest F-Up of my flashing life. While following QBKing77's Rooting & CWM with unlocked, at approx 3:50, during the flashing of the root SYSTEM.img file, rather than that file, I used the wrong file to flash used an IMG file that was meant for cwm, which is a completely different task.
So now I am trying to get into fast boot and try to do it with correct SYSTEM.IMG, then to find out I never got it downloaded, the link was deadand now I can not find where to DL it from. I must've not been paying attention and got ahead of myself.
Anyone know where I can a mirror of the file found here. Its the first link in the root section labelled "moto-fastboot flashable /system image".
Am I screwed? Does anybody have a copy of that system.img file laying around. I can not find any mirrors. That is the only way I can see this getting fixed bc I can still go into fastboot mode.
ckeck this ????
http://rootzwiki.com/topic/4137-pudding-photon-pudding-bootloader-unlock-updated-8302011/
Use at own risk. ???
Can u get into rsd mode and flash 154_5 sbf
Sent from my MB855 using xda premium
Important files
Thank shabbypenguin for those
If you can get into rsd mode and connected/recognized in rsd lite you should be able to flash one of those sbf files and return to stock.
I read the instructions carefully! It said to put the oven on 350 degrees for 10mins but for some out of this world reason I put it on broil and let it cook for 20mins :/
Sent from my MB855 using XDA App
LOL no kidding Custodian. I did get a laugh out of that.
Thanks CubanLuke & ShabbyPenguin. I did use RSDLite to flash the current sbf you directed me to, I can boot into the phone again. Thanks again.
Now as to how to proceed, I will have to unlock the bootloader again, np, but when I run into that very step where I broiled it, the rooting via speedboot.... would it be okay to root using AIO instead because I can not find the SYSTEM.IMG needed to follow along w/ the video using this method.
Can I just root a different method, then proceed on with CWM recovery, then flash rom from the video?
enzyme said:
LOL no kidding Custodian. I did get a laugh out of that.
Thanks CubanLuke & ShabbyPenguin. I did use RSDLite to flash the current sbf you directed me to, I can boot into the phone again. Thanks again.
Now as to how to proceed, I will have to unlock the bootloader again, np, but when I run into that very step where I broiled it, the rooting via speedboot.... would it be okay to root using AIO instead because I can not find the SYSTEM.IMG needed to follow along w/ the video using this method.
Can I just root a different method, then proceed on with CWM recovery, then flash rom from the video?
Click to expand...
Click to collapse
- Unlock using derpunlock.sbf
- use fastboot to erase recovery and install CWM recovery
- boot into CWM
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
SOLVED!!! THANK YOU EVERYONE!
KTT16 said:
- Unlock using derpunlock.sbf
- use fastboot to erase recovery and install CWM recovery
- boot into CWM
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
Click to expand...
Click to collapse
Thanks KTT. Okay, I'm back on track now. I am unlocked again, rooted as well. but I am not sure about 2 things. This will be my very first android rom flash and just coming from a big whoopsies, I just want to be sure.....
1) Format system: in cwm recovery, which option is that? I don't see "format system" in the main or advanced menu. Maybe its worded differently?
2) Flash ROM: I can only assume its either "Apply Update from SD" or Update from SD". Not sure which one though.
enzyme said:
SOLVED!!! THANK YOU EVERYONE!
Thanks KTT. Okay, I'm back on track now. I am unlocked again, rooted as well. but I am not sure about 2 things. This will be my very first android rom flash and just coming from a big whoopsies, I just want to be sure.....
1) Format system: in cwm recovery, which option is that? I don't see "format system" in the main or advanced menu. Maybe its worded differently?
2) Flash ROM: I can only assume its either "Apply Update from SD" or Update from SD". Not sure which one though.
Click to expand...
Click to collapse
1) Format system is in the "mount" options. Although it's unneeded to flash a ROM. Personally I just wipe data/factory reset and then wipe cache and have zero issues. Others may tell you different though.
2) "Install .zip from SD Card" then select whichever .zip you're looking to install.
Sent from my MB855 using xda premium
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Flashing the 198_7 sbf unroots and relocks, so you're back to square one.
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Reboot into stock recovery, when you get the recovery logo thing push both volume up and volume down at the same time to get the recovery options. Then do a factory reset and it should boot for you. After that, root and unlock again. And you didn't have the Market because you forgot to install Gapps...
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
The reason cm7 didn't have the market is that you needed to flash gapps. Try doing a hard reset. http://www.hard-reset.com/motorola-photon-4g-hard-reset.html That should do it.
try the 154 sbf
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
i had the same problem i think and was going thru boot loops but some one told me to start into recovery when you try you get that ? android screen from there hold down volume up and down at same time then wipe phone booted up fine after that.
It worked like a charm. Thanks. I'm still very new to android and hate to admit it but will be running into problems like these again. The best way to minimize it for me is, not only follow certain directions correctly to get out of these binds, but to understand them.
- So theres an image of the stock ROM stashed away on the phone regardless? And it can be accessed only via the stock recovery? Because after I succeeded in flashing cm7.1, I did a factory reset once from settings>privacy and that restored me to a fresh CM7.1. The factory reset from settings>privacy and in CWM is the same, but both different from the factory reset via STOCK RECOVERY?
- Also what would be the correct method to go from one custom ROM to another? Would it be this? :
(in CWM)
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
Or can I just jump to install from zip ?
- Also regarding SD Storage (internal), only holds storage files? So on any fresh ROM there shouldn't be anything in that partition relating to that new ROM yet right? So I can delete things without worry?
You should not have to reboot into recovery, once your wipes are complete, normally you can just flash your ROM of choice in the same recovery session.
Before I flashed anything I would make a backup with CWM so you don't have to keep rooting and unlocking. You can just restore your backup.
Sent from my MB855 using xda premium
After flashing 198 7 sbf, all u need to do is flash derpunlock not go through oem unlocking, then reflash recovery.
Simple generic process for going between roms (assuming already unlocked + cwm recovery flashed; process may be different for some roms, always make sure to read directions, but this is the general concept)
1. Download rom (and gapps if necessary) and put on your sdcard
2. Boot into recovery and make a nandroid backup
3. You made a nandroid backup right?
4. Secure your nandroid backup (move it to your pc or something).
5. You know where your nandroid backup is right?
6. Wipe data/factory reset.
7. Install zip from sd (flash), choose the rom.
8. Reboot system.
At this point your rom should be all set. If for some reason you don't like it, simply boot into recovery and restore your nandroid backup. You can even make nandroid backups of various roms if you want to swap between them for whatever reason.
As the thread title states...I was on 7.1 and downloaded/updated it to 7.2 Now the phone doesn't boot up and all I get is the Kernel Panic Upload Mode.
Anyway I can fix this? And if so, is there a way of doing it without completely formatting my phone and losing all my apps?
Oh and if it makes any difference I had to install that Siyah Kernel or whatever it was called to get out of the bootloop issue that I had with CM7.1. I'm thinking that that may be causing the problem....? But then again what do I know
wipe cache only.
valentinrascu said:
wipe cache only.
Click to expand...
Click to collapse
How? I've been trying [Power+Volume Up+Home] and it hasn't been doing anything. Can I do it through download mode somehow?
Had this problem when i flashed Lite'ning rom. Had to go into download and flash stock with odin. Took me a few tries to actually get the rom to work. As far as I know, that'd be your only option, seeing as recovery doesn't work for you.
take a deep breath and read, there is a very small chance of bricking your phone just so you know. Flash back original with Odin and start everything again
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/2011/10/samsung-galaxy-s2-firmwares-bell-canada.html[/url
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
nubreed000 said:
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
Click to expand...
Click to collapse
If you flashed stock, you should be fine just rebooting.
Its stuck on the boot screen. I tried just rebooting, then wiping/factory reset, then both wipes...reinstalled stock a few times and nothing worked each time. I'm suck on the Samsung Galaxy SII GT-I9100 screen
:-\...when I go into recovery, I get a ton of red messages/errors
I'm gonna try somethig other than stock firmware see if that helps.
edit Ok so I rooted the phone and it got past the first boot screen and now appears to be stuck on the "animated S" boot screen...progress!!
nubreed000 said:
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/...msung and their changes to Android framework.
Click to expand...
Click to collapse
Ok everything back to somewhat normal. Stock ROM didn't work but 2.3.6 did, so I'm on that. Now do I wanna go back to CM is the question...
Either way, thanks again for all the replies and helping me out with this. Greatly appreciated!
I don't know exactly what caused the issue. Maybe some recent apps since that was all that I had installed. I was running the latest AOKP ICS 4-28-12 and Siyah 3.1x. I forget the exact kernal number but it wasn't the version that I read about phone bricking (R6?).
So I wake up this morning and unlock my screen and there are popups for everything force closing. Not just foreground running apps but everything including background running apps. Every time an app autorestarts in the background the force close error msg pops up again. It was running fine just 6 hours prior since I was using it before bed.
Reboot. Same issue. CMW Recovery. Wipe cache/dalvik. Reflash AOKP and GApps. Reboot. Same force closing issue. WTF. Attach USB to comp and try to move a different ROM to my Internal SD but no dice. Comp isnt recognizing phone now. [email protected]#K! Reboot into download mode. All the ROMS I downloaded are ZIP format instead of TAR format. So this time my dumb self uses Odin to reflash the TAR file I used to root my phone. After this I realize "that TAR doesn't have a ROM attached to it."
So now I can only boot into download mode. Can't load CMW. Sadly I had to leave for work and I'm without my phone until I get home at midnight. I FEEL SO DISCONNECTED! ='(
Will a simple file conversion program be sufficient to convert ZIP to TAR so I can use ODIN to flash them later? Or will I have to follow the unbrick instructions to return to stock and then start over? And after reading about that one version of Siyah bricking phones I think I'm going to leave the NEAK kernal that comes with AOKP.
Thanks for your assistance!
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
I found this on the i9100 forums, instructive. Instead of installing a stock samsung firmware and kernel, just download a rooted package (maybe go back to Gingerbread for i777) then go from there.
http://forum.xda-developers.com/showthread.php?t=1457458
I'm interested to know how this recovery works for you, keep us posted! Best luck!
Any idea what would randomly cause the issue of mass force closures so I can prevent this from occuring again?
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
dmnall said:
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
Click to expand...
Click to collapse
I didn't do a factory wipe. I'm thinking I'll just do a factory wipe for any new rom installs. It's a little more work but if it helps prevent this sort of error I'll do it. And after reading about the bricking with that one version of Siyah I'm going to wait a couple weeks before any new installs to make sure other people have tested it first.
creepyncrawly said:
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
Click to expand...
Click to collapse
Well the first attempt didnt work using kernel + rooted UCKH7. Odin did everything it was supposed to but the phone locks at the initial Galaxy S II I-9100 ! screen. =(
Second attempt using I777_UCKH7_OCD_Root_No_BL and I'm able to get past the Galaxy S II I-9100 screen and the original AT&T boot animation shows but after the boot animation it just continuously reboots. ='(
Third attempt I tried Kernel + cache + rooted UCKK6 and after the reboot it actually rebooted into recovery mode. I thought that was a good sign so I reboot the phone normally and same issue as above. I try to reboot into recovery mode (Vol + - and pwr) again but it doesn't come up now. ='(
Forth attempt I tried Kernel + cache + rooted UCKK6 again. It reboots into recovery mode and I select the Factory Wipe option and reboot. There's a long delay after the AT&T boot animation and finally my phone starts up as if it was stock.
What a freakin nightmare! I was so worried my phone was a goner. None of the other ROMs I tried gave the option of booting into recovery mode which would have saved me so much time. Only the stock one did. The factory wipe was the key. So I'm definitely saving that file for safe keeping.
Thank you all for your suggestions and assistance. It's much appreciated.
This entire thread could have been avoided. By wiping completely. What is a complete wipe? Well, its the /system , /cache, /data, and /dalvik partition. Each of which are easily wiped in cwm in under 30 seconds. Flashing the kernel cleaning script doesn't hurt. Keep in mind these are your phones people it wouldn't hurt to do some research.
Sent from my SGH-I777 using Tapatalk 2
Been using twrp since rooting note II. I wanted to try out 4.4 PA but they said to only use cwm. It was late so I decided to be lazy and since I used to use rom manager all the time I installed it to flash cwm recovery then booted into recovery to install touch version. It wasn't showing the touch version so selected to restart to check to see where I saved it to it would not boot past the first "note II" splash screen. Battery pull then back into recovery and went ahead and flashed PA 4.4 and now it will get past the splash screen then shows boot animation but then starts all over.
Is this a rom manager issue?
can I flash twrp from within cwm recovery?
will I have to basically reroot it?
Any suggestions on how to get back to twrp and to a usable phone?
thanks
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Nope did my standard wipe cache, wipe dalvik, and factory reset then flashed rom then gapps. Going to go back to twrp and wait for 4.4 to be more stable before I try it out again and maybe then I can use twrp to flash it.
thanks for the help
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
jdpeck said:
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
Click to expand...
Click to collapse
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
fallingup said:
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
Click to expand...
Click to collapse
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
jdpeck said:
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
Click to expand...
Click to collapse
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
fallingup said:
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
Click to expand...
Click to collapse
Finally got it. Thought using odin to flash back to root 66 and start fresh would work but after that it was still going to the splash screen then black and a battery pull had to be done. TWRP back ups would fail when trying to restore, so I reverted back to an older version of twrp and it finally let a back up be installed and it booted up just fine!!
thanks for all the suggestions
Im having a similar problem to yours, I am using twrp and flashed PA 3.99 the phone works great, but if my battery dies or i restart the phone or shut it down it automatically wont get passed the samsung logo, or sometimes the PA logo, the only work arounds ive seen to it is to wipe the cache and dalvik to boot, but when that fails i have to install the whole rom over again. any ideas?