Hi guys,
I'm having issues with my SGS2 and I would appreciate very much if you guys could lend me a hand.
I had VillainRom 2.4.2, Ninphetamine 2.0.5 and modem KG6.
I tried to install this Dark theme but something went terribly wrong and I had processes crashing, couldn't see any links to the phone dialer, messaging, etc.
I'm trying to wipe the phone back to full stock but I can't for some reason.
I tried booting into recovery mode, wiping cache and all information but when the phone boots I'm back to a black skin with several crashing warnings.
I tried to reflash KG6 with odin and selecting repartitioning but when I boot again I'm back to the same black skin missing functions and receiving some crashing alerts.
I tried to factory default through Settings -> Security -> Factory Default to no avail.
All the guides I was able to find on the net to put the phone 100% back to stock failed as I always boot to a non-working dark theme.
Can someone please provide me some help?
Would appreciate very much any pointers.
EDIT: After I boot into this dark theme, I'm getting messages like process android.process.acore has stopped unexpectedly for example.
Factory reset does not mean that it removes all your custom rom stuff and all that. That's a nice thought, but that's not how it works
You need to flash a different rom on your phone after having wiped everything. This will fix your problem. And if you so very much want to go back to stock, you could always flash a stock rom through ODIN which you can get from one of the available threads.
Boot to recovery mounts and storage format system data and sd card ,
Power off boot to download mode flash stock firmware via Odin .
jje
I don't know if I'm understanding.
I did reflash the phone with samsfirmware Europe KG6 after a complete wipe of data through the recovery menu (vol.up+power+home).
That didnt work.
Am I missing some steps in my procedure?
I noticed that my default dialer apk, contacts apk, etc are not working. Which method will also replace all my original APKs?
Thanks once again for your time and attention.
Boot to recovery mounts and storage format system data and sd card ,
Power off boot to download mode flash stock firmware via Odin .
Nothing more to add.
jje
Just wanna thank you for your help. For some reason I wasn't getting the expected behavior by flashing KG6. Went with KG5 and now I'm back on stock.
Cheers. Thanks button went your way btw.
Related
Hi guys, I got a SGS2 just over a week ago, on Bell/Virgin network in Canada. Suffered from the battery drain issue due to being stuck with crappy UGKG2 firmware which my provider still hasn't updated.
I decided to update it myself, and did a ton of research. I successfully got Root tonight by flashing CF-Root-SGS2_ZS-OZS_KG2-v4.1-CWM4 kernel with Odin. In case it matters, I did NOT flash back my stock Kernel, so I still had the insecure kernel installed. From there, I backed up my apps with Titanium.
Went into CWM and selected boot into CWM Recovery. I followed the steps on the wiki, including creating a backup file. My only hint of what I might have done wrong was I originally selected to flash update.zip, and that process failed. I then went to the directory in which cyanogenmod is stored on my SD card, and selected that, then it installed ok. I had downloaded update-cm-7.10-GalaxyS2-signed and that's what I put on the phone. I then also installed the Google Apps.
I then hit reboot, and it only goes to the Samsung screen with the yellow triangle and just hangs there for a few minutes. Not knowing what else to do, I popped the battery out. I have since learned that I can turn it on and off, but it never goes past that screen. Wouldn't go into the recovery or download modes, always that screen. Luckily, I saw somewhere to do the 3 button thing WHILE in that screen, and that works. So I can get to recover, and download modes. So, I think I'm ok. I checked, and it does connect to Odin still.
I just want to know EXACTLY what I should do at this point. I don't want to fully brick it. There are actually two recovery files on the phone... not sure why... Or which one to pick. Should I just flash stock firmware back with Odin? One of my main goals is to get off 2.3.3 so I can have more than 8 hours of battery...
Thanks,
Rob
Boot into tecovery, do a full wipe again. (Wipe data/factory reset, wipe cache partition, advanced>wipe dalvik cache).
Now install CM7 zip twice in a row without reboot. It may take a few minutes for reboot since system is rebuilding dalvik cache. Be patient. After you see the home screen, reboot again.
Sometimes, CM won't install properly with CF root recovery. In that case reboot into download mode, flash codeworkx cwm kernel via ODIN.
http://forum.xda-developers.com/showthread.php?t=1118693
Now reboot into recovery and do full wipe and twice-install !
Ok, working now with the flash twice thing. Well that's weird, would be great if it was in the wiki page...
Thanks!
Rob
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
Hello,
Before flashing a new kernel today, I kept getting random reboots and and I thought the kernel might be playing up (I didnt install any new apps or modify anything before hand). So I installed the latest Siyah kernel (Siyah-v3.2-CWM) and now when I load up my phone, I go past the lock screen and I just keep getting multiple closed messages for different applications. I also cant open any of them as I get a message saying "Unfortunately, [app name] has stopped".
I cant open Titanium Backup so Im screwed
Please help.
I have also tried wiping both caches but it hasnt worked / reset init.d file (if that helps?)
Flash back your old kernel, at least you'll be back where you started.
oinkylicious said:
Flash back your old kernel, at least you'll be back where you started.
Click to expand...
Click to collapse
That didnt work
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Still problems use usb jig to set rom counter to zero .
Return to service centre .
jje
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
You can either odin stock. It's about a 1.8gb file.
Or you can get a known working ROM on your sd card, factory reset wipe, wipe preload, wipe system, install known working rom+gapps+whatever, wipe cache and wipe dalvik. Reboot. If it sticks at the samsung logo pull the battery and then try to reboot again. Sometimes first boot can take a while. I'd give it 10 minutes before throwing in the towel lol
I bricked my phone by updating Hyperdrive (which I will never (curse words... lots of them) use again. Can someone tell me where to find this stock file? I've been searching long enough to get frustrated and delete several less diplomatic posts, settling with this one.
hey guys, I am a little confused. I just came to the S4 from a galaxy nexus, and I previously used CWM as my recovery option when doing clean install of new ROMS.
When I rooted my S4, I installed TWRP (via goomananger, version 2.5.0.2) because of people saying its much better (on the galaxy nexus forums). However, I keep reading issues of people being stuck in bootloops for TWRP when wiping data.
My question is -- what is this issue? Are you not supposed to clean flash with TWRP?? Or do you only do "factory reset" option in TWRP and not wipe the data?
As I am a little confused on this issue, is it more safe to just install most recent CWM and use that as recovery instead?
Thanks alot
No worries
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
cidorov said:
Try using odin to flash to stock. Then re-root and install custom recovery and whichever rom. I had a similar problem posted here with no help from the big brains. Had to trial and error with caution on my own. Kinda disappointing since the answer is quite simple once you connect all the dots. Flashing in odin will fix yer internal storage problem because it redefines everything.
Click to expand...
Click to collapse
uberpippi said:
I accidentally formatted my internal SD card with TWRP instead of factory reseting. I can get into recovery, but loading any ROM hangs at the loading screen. For awhile, TWRP was asking for a password, and then somehow I hit the magic combination of things to make that stop happening. I adb pushed an updated TWRP and reinstalling various ROMs.
All this started from trying to install Hyperdrive RLS8. I was running RLS7 fine, went for a clean install, spaced out and formatted the phone, flashed the ROM, and had a whole slew of stability problems. Things would randomly crash instantly, booted only 50% of the time, when it did, installing things would break it, tried various things to fix it, fixing permissions and wiping cache's and such, and results were unpredictable. Kept re-formatting and reflashing with different options until I finally realized that I was formatting it and that's probably what the whole problem was.
Currently I can't boot into a ROM, it hangs on the boot animation. I tried another clean install with RLS7, and the same thing happens. I'm assuming that I need to get back to stock somehow, but I'm not sure how. Odin has always confused me. I used the all in one tool to root awhile back, and I only used odin to send a kernel tar file. If I download a stock build, it's a zip file... so how can I odin it? Is that what I need to do? I'm imagining at this point that the file structure is messed up and I need to rebuild it somehow. I don't have my nandroid backup on this computer, so I haven't tried that yet.
Click to expand...
Click to collapse
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Surge1223 said:
Yes this would probably be your best bet. I wouldn't say the answer "is quite simple when you connect the dots" though, because with that logic there would be no PC problems, you would just connect the dots and format the harddrive and Windows will redefine everything else for you!
But back to seriousness, you have to download a stock factory image and its actually a tar.md5 file and not a .zip because you cant flash zips through odin. The stock factory images can be found in the development section, and they are usually quite large files (2gb+ when extracted!) and you will have to download odin and make sure you have the latest usb drivers from samsung. Then its pretty straight forward, The threads in the development section have guides for how to use odin. The stock image contains all the partitions within in it and will effectively repartition your device when you flash it so no need to use a pit file.
Click to expand...
Click to collapse
Just to follow up, that's what I ended up doing. I used the "No-wipe" factory image, odin'd it, re-rooted (I don't know if I had to do that step, but I did), and then loaded my ROM of choice and it works perfectly now. Thanks!
Hi all,
Sigh. So it looks like I bricked my Samsung Tab E Verizon. I rooted it with King root and when I removed it, it is now in a endless boot loop. I've tried all sorts of things to try and recover it.
I used SkipSoft to set it up to be flashed but odin fails everytime. I was using the new ROMS found on this Forum. I've tried putting it into download mode and manually flash it and that didn't work. I can't Re-Root it as it won't stay on long enough to Root and they always fail. Right now I'm at a loss.
Can anyone help?
Thanks.
Do you have custom recovery or default? if you have default you can hold the home button and vol up button then the power button to get into recovery, once your done with that you can wipe cache and reboot, if that STILL does not work then factory reset your phone and re wipe cache, i know losing data sucks but its better then a brick. (this will work 99% of the time because the default recovery automatically re-installs stock rom)
If you have a custom recovery, then i recommend wiping everything including dalvik cache etc, making sure EVERYTHING is squeakly clean (execpt recovery obviously) , and find the driver for your samsung phone and download it on your computer and install, once you are done with that, put your phone into download mode, find your original STOCK rom for your phone, download it and flash it with odin, from there IF successfull you should have a fresh boot of your stock rom, then you can re-root and go on with your day.
Also make sure once you re-gain root access backup your rom so you will always have a plan b if everything goes bad. i cannot recommend this enough, even if you are an expert with flashing, there is always that small percentage things will go wrong and you should always have that backup ready.
Hi!
Thank you very much for the reply. You know, that was one of the things i tried initially when it happened. When I tried it, it wouldn't go into recovery mode. I then went on the odyssey of hell in trying to recover it.
When I read your post I was thinking; "Yeah I tried that", but then I thought I would give it another shot. I went into Factory Reset, it then actually went into the recovery menu. I deleted the cache and set it to data/factory reset and it's still looping. I get an error saying; "E:failed to mount /preload (no such directory)". I then tried to run update from external storage and it's telling me that it's disabled. I tried to update from ADB and it's disabled. I tried to apply from cache and it says; "APPLY_CACHE is depreciated". It's still looping.
Urghhhhhhhhh.......