Related
What happened: Samsung Galaxy S2 tmobile SGH-T989 (more info at the bottom)
Ok so I installed the usb drivers through kies and got the latest firmware from kies. Installed Odin 3.07. Backed up my stuff. Flashed recovery-cmw-hercules using Odin. Then I rooted my phone using tmobilegalaxys2rootICS (flashing with CWM recovery) and installed CWM-SuperSU v0.87. Updated root and CWM on the next boot using SuperSU app and Rom Manager to the current version (non touch for CWM). I then got cyanogenmod9.1.0-hercules (stable) and gapps-ics-20120317-signed. I wiped the internal SD card and external SD card. Went into recovery manager. Did a factory reset, cache wipe, dalvik wipe, battery stat wipe. Flashed cyanogen9, flashed gapps, fixed permissions and rebooted. Now i'm stuck in a bootloop just looking at the start up screen of cyanogenmod. I have access to the recovery menu and the odin screen so i'm not bricked as far as i know, just bootloop'd. I read somewhere of a super wipe by JDT or someone along those lines but i can't find those scrips to flash them. Any help would be great. Thanks!
Info:
Computer OS: Windows 7 Ultimate (64-bit)
Firmware Version: PDA:LH1 /PHONE:LH1 / CSC:LH1 (TMB) - (Ver. 12.07.20.02) (current)
Binary: Samsung Offical (Kernal 3.08 ICS)
Build Number: IMM76D.UVLH1
ROM: Stock T-mobile Android 4.0.4 (before i flashed cyanogenmod9)
Baseband Version: T989UVLH1
Brand: Samsung
Model: SGH-T989 (hercules)
Type: Galaxy S2 X
Carrier: T-Mobile, USA
Country Code: 1 (USA)
Access Point: epc.tmobile.com
Odin3: v3.07
Clockwork Recovery: v5.0.2.7
Root: tmobilegalaxys2rootICS -> CWM-SuperSU-v0.87 (updated can't view newer version right now)
Cyanogenmod9: cm-9.1.0-hercules
Google Apps: gapps-ics-20120317-signed
spikeguy4 said:
What happened: Samsung Galaxy S2 tmobile SGH-T989 (more info at the bottom)
Ok so I installed the usb drivers through kies and got the latest firmware from kies. Installed Odin 3.07. Backed up my stuff. Flashed recovery-cmw-hercules using Odin. Then I rooted my phone using tmobilegalaxys2rootICS (flashing with CWM recovery) and installed CWM-SuperSU v0.87. Updated root and CWM on the next boot using SuperSU app and Rom Manager to the current version (non touch for CWM). I then got cyanogenmod9.1.0-hercules (stable) and gapps-ics-20120317-signed. I wiped the internal SD card and external SD card. Went into recovery manager. Did a factory reset, cache wipe, dalvik wipe, battery stat wipe. Flashed cyanogen9, flashed gapps, fixed permissions and rebooted. Now i'm stuck in a bootloop just looking at the start up screen of cyanogenmod. I have access to the recovery menu and the odin screen so i'm not bricked as far as i know, just bootloop'd. I read somewhere of a super wipe by JDT or someone along those lines but i can't find those scrips to flash them. Any help would be great. Thanks!
Click to expand...
Click to collapse
Hey! As of I know, you are not using a TOUCH recovery. Sad to say but a lot of ROMs will only work on TOUCH recovery, because they changed something in the Cache wiping that ain't screwing up with device or something (as I understood digging up a little bit).
Here is my advice, go with this for now:
MIRROR
It's v13.1 of Sk8er's recovery. Though I want to tell you, if you try to hardboot into it (what I mean is: hold +/- volume and plug in USB) it probably won't work since it doesn't work for me for a weird reason (I'm on v13.0 so I couldn't say for v13.1).
In EXTRAS you got the cache.wipe and the super.wipe of TDJ.
And another thing I think you should know about this device is HOW TO FLASH CORRECTLY.
Here is the way:
Make a backup (optional)
SUPER WIPE (using TDJ tools)
Factory Reset (wipes data/cache/.....)
Install your rom (without GApps)
Reboot phone.
Wait for let's say 10 minutes (optional as well I don't do it but it's recommended... Just reboot, and when you see no bootloop, go back to recovery for next)
Wipe cache/dalvik (without using TDJ but only from recovery touch)
Install gapps.
Reboot.
if you just update your rom, like going from a nightly to another nightly, no need to follow this. Just wipe cache and dalvik using recovery touch, and you are good going.
Cheers!
I'll try it!
Thanks switchfoot! I'll try this today. I'll grab the cache wipe and super wipe as well as upgrade to touch-cwm however i'm a little worried when you say skaters mod made you unable to hard boot, seems risky as that's your last resort if you brick the device (as far as i know). Thank you so much for the steps on flashing, I read so many different ways I was very confused on the proper procedure. I have class today so I probably won't report back till later today but i'll let you know what happens!
spikeguy4 said:
Thanks switchfoot! I'll try this today. I'll grab the cache wipe and super wipe as well as upgrade to touch-cwm however i'm a little worried when you say skaters mod made you unable to hard boot, seems risky as that's your last resort if you brick the device (as far as i know). Thank you so much for the steps on flashing, I read so many different ways I was very confused on the proper procedure. I have class today so I probably won't report back till later today but i'll let you know what happens!
Click to expand...
Click to collapse
My friend here is a flawless recovery with 0 issues if you are worried about the one above TWRP 2.2. Also stay on one site for everything and may I suggest xda only. Do not venture off not that the other sites are issues just that you will confuse yourself although rootzwiki is just as good.
There is plenty of How To's here in xda that you do not need to be confused, confusion comes when you start asking others there opinions and take bits and pieces from all of them... Good luck and feel free to pm me if you need any further help... Just please read up before you do anything
These are the exact instructions from CM on how to install their rom: did you follow these instructions
Installing
How to INSTALL from another ROM (DO NOT SKIP ANY STEPS!):
Be sure to back up your current ROM!
Update your radio to the above recommended version if you have not already done so. (See the list below)
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the CM9 zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON NON-TOUCH CWM RECOVERY: Install darkside-wipe-cache-only.zip (which fixes bootloop due to bad /cache format)
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
Click to expand...
Click to collapse
Awesome!
Wow that's exactly what i was looking for! Thank you! I just flashed a stock rom to go back to the start. I'll begin the process over again following these steps. The only issue is that the radio update section in the guild no longer exists. Is it ok to go on without the radio update? Or will this cause issues? If so is there a mirror for them?
SOLVED!
OK! I'm all set now. I had to use the full wipe as well as the cache wipe after install and the bootloop was resolved. The bigger headache was when kies failed at updating the firmware so i had to do an emergency firmware flash. Any way i have clockwork, root with SuperSU, cyanogenmod9.1.0, and the latest google apps! Plus its backed up now! YAY! Now i just have to configure it to how i like and we'll be in business! Thanks for all your help guys! I really appericate it!
Last thing
I still need the radio update since the file no longer exists in your link. Everything is good but I don't have any wifi calling or features of that order. Which are important in keeping my usages down and getting coverage in my house and otherwise bad areas. Where do I get this and would I just install it via CWM? Thanks again!
Hey guys, I was playing around on my phone, and I downloaded something off of 4shared (just a game) and it crashed and made my phone freeze. I then held my power button and waited for it to boot but now im stuck in a bootloop with the stock telus rom... is there anything I can do that wont wipe everything on my phone? Oh and I can get into both CWM recovery and download mode.
I gave it some more time to startup and it pretty much factory reseted my phone. I get that thing to setup my phone after startup. Everytime I turn my phone off it goes back to this screen and my phone restarts. If I surf through the files of my phone, it shows I still have everything but It doesnt show any of my apps or anything.
Hey guys/gals,
I recently bought a Koodo Galaxy s2x. After a few weeks I looked online and saw that there were some JB Roms for my phone. I couldn't resist and tried to flash one after rooting. I didn't have many problems with it, but there were some glitches that started to bug me, so I decided to see about going back to stock (I should have done this first I know). So then after hours(many) of searching, the best I could find was a T-Mobile stock Rom I decided to try and flash it (both times via odin). I also read somewhere that I should use darkside superwipe to clear my cache, so I tried that, but ever since that CWM stopped working on my phone. anytime I tried to do any back up or anything it just froze, and I had to hard boot. Finally I just tried flashing T-Mobile stock ICS, and Odin said "Failed". I decided to just unplug my phone, as I thought I already screwed it up, but after rebooting, the T-mobile Rom worked. I don't understand why it works fine if the Flash Failed. Now, I can no longer connect to kies (I'm hoping official JB will be shipped soon!), and I am wondering if I can somehow return to a stock Koodo Rom, and if it will connect to Kies again, as it previously had. I have looked a lot and have not found anything that I fully understand. I'm not overly experienced, which is why I should not have flashed to begin with. This is the closest thread I have found to help me, but I don't fully understand what all I need to do:
"Haven't seen anyone shared this yet.
Here's the KOODO ICS 4.0.4 stock ROM I used CWM to flash to stock after I tried the custom ROM.
h t t p s : / / sourceforge.net/projects/koo...d.zip/download
I also flashed DARKSIDE.SUPER.WIDE before I flashed this or you can used CWM Recovery 6.0.1.2 to wipe system and cache."
Is it possible for me to get back to stock phone? and still connect to Kies? and then possibly upgrade to JB through Kies if Hercules ends up receiving it?
Thanks for any help you can give me. Here is all my current phone info incase this helps:
Model:
SGH-T989
Android Version:
4.0.3
Baseband version:
T989DTLLG2
Kernel version:
3.0.8-perf-T989UVLE1 -CL508451
[email protected] #1
SMP PREEMPT Sun May 6 15:07:07 KST 2012
Build number:
IML74K.UVLE1
Thanks.
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: https://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
arcsine said:
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: h t t p s ://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
Click to expand...
Click to collapse
That link doesn't work, it says cannot find page. Also, my phone is currently not rooted, does it have to be rooted to flash from recovery? if not what do I do to flash from recovery? I know how to get into recovery, but after that do I use 'apply update from external storage'? Do I have to wipe the cache first?
Thanks.
PS: I just want to be able to get back to stock for now. At least until I learn more about flashing Roms. There is still lots for me to learn, like kernels, radios, Nightly's for official Roms, or even how to properly flash a rom without feeling lost. If I know a way to get back to stock comfortably, It will give me more reason to try some other Roms (once I learn how).
Here is a working link to the stock Koodo ROM: http://sourceforge.net/projects/koodostock/files/KOODO_SGH-T989D_Stock_Signed.zip/download
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted: http://galaxys2root.com/t-mobile-galaxy-s2/how-to-root-icsgb-on-t-mobile-galaxy-s2-sgh-t989/. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
arcsine said:
Here is a working link to the stock Koodo ROM:
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted:. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
Click to expand...
Click to collapse
Thanks a ton... Worked perfectly! I'm hoping it will connect to Kies once again.. I'll let you know if it works.
Unfortunately, I still can't connect to Kies.. It just sits at the Loading status (for like 10-15 mins). But At least I don't have all of the T-mobile apps and stuff anymore!
Hello all just bought a new Samsung Galaxy SII from craigslist already rooted with 4.0.3 Jedi Mind Trick. After reading for what seems 4-5 hours i have been trying to put together how to properly without bricking switching it to 10.0.0 Stable as i use to use Cyanogenmod 2-3 years ago on my devices. Seem alot of things have changed and there is a cluster**** of stuff out there now. If you could direct me to a how to or show me how to do it i would greatly appreciate it!
Thanks all!
Assuming you have nothing personal to back up that you can't just download from google play or your google account again: download cyanogen 10 and it's gapps. reboot into recovery mode. factory reset, wipe data, wipe system, wipe cache, wipe dalvik. pick the install zip from sd card or so option, browse to cyanogen, then install gapps the same way. wipe dalvik again and reboot.
I was thinking of doing this myself JMT to CM10. I didn't think there was anything special to do same as flashing from any other ROM to CM10. If there is a special requirement I would think they'd post in in with the ROM post information.
Alawishis said:
I was thinking of doing this myself JMT to CM10. I didn't think there was anything special to do same as flashing from any other ROM to CM10. If there is a special requirement I would think they'd post in in with the ROM post information.
Click to expand...
Click to collapse
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
melvinator said:
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
Click to expand...
Click to collapse
honestly - i backed up everything to my external and then formatted the internal when i went from TW to AOSP for the last time. well worth it. nice folder clean up and then you can just manually take all the stuff you want back.
and you should just be able to odin on cwm or twrp - then flash the rom of your choice.
new ion? said:
honestly - i backed up everything to my external and then formatted the internal when i went from TW to AOSP for the last time. well worth it. nice folder clean up and then you can just manually take all the stuff you want back.
and you should just be able to odin on cwm or twrp - then flash the rom of your choice.
Click to expand...
Click to collapse
trying to look up how to do that now .... Searching the forum now... Might you be able to tell me real quick how? I already Downloaded the 5.2 file they suggest to use but can't find a working toturial that is just for flashing the cwm.
melvinator said:
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
Click to expand...
Click to collapse
If you get stuck at the boot logo, it's called a soft brick. You don't have to use ODIN or go back to ICS. Just make sure the ROM zip you downloaded isn't corrupt (check the size/m5d if possible), wipe everything, and reboot into recovery to try installing again.
arcsine said:
If you get stuck at the boot logo, it's called a soft brick. You don't have to use ODIN or go back to ICS. Just make sure the ROM zip you downloaded isn't corrupt (check the size/m5d if possible), wipe everything, and reboot into recovery to try installing again.
Click to expand...
Click to collapse
I already used Odin to go back to 2.3.5
Btw I appreciate the help
My woman's is waiting that I fail to say I told you so -_-
melvinator said:
I already used Odin to go back to 2.3.5
Btw I appreciate the help
My woman's is waiting that I fail to say I told you so -_-
Click to expand...
Click to collapse
You won't fail. Follow the guidelines step by step. Print it out, make notes. Anything. Read. The step by step guide works... that'll get you with cwm. Then, you can flash the zip you will put on your phone... either a SU zip or just a rooted ROM. Follow flashing instructions.
Just realized - you'll be way better off if, once you have cwm on, just format the internal ONCE YOU HAVE A ROM ON AN EXTERNAL SD CARD. then flash CM10. THEN you'll have a fresh AOSP install.
Sent from my SAMSUNG-SGH-T989 using xda premium
new ion? said:
You won't fail. Follow the guidelines step by step. Print it out, make notes. Anything. Read. The step by step guide works... that'll get you with cwm. Then, you can flash the zip you will put on your phone... either a SU zip or just a rooted ROM. Follow flashing instructions.
Just realized - you'll be way better off if, once you have cwm on, just format the internal ONCE YOU HAVE A ROM ON AN EXTERNAL SD CARD. then flash CM10. THEN you'll have a fresh AOSP install.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
melvinator said:
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
Click to expand...
Click to collapse
Go back, format system, and then reinstall.
Sent from my SAMSUNG-SGH-T989 using xda premium
Update your recovery to twrp or cwm 6+ and don't use dark side scripts
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Please excuse my harshness but this is not as hard as many make it seem. I would say if it takes you more than a couple attempts maybe it is just not for you. I only say this because I would hate to see you mess up your phone. Now if you think a bootloop is a brick then we need to do things at a slower pace with you.
If you already have your phone rooted then
1.download goomanager from the playstore and then
2.open it up and allow it to grant permission from CM
3.hit menu button while goo manager is open
4.click on install OpenRecoveryScript
5.let it do its thing
6.reboot into your new TWRP recovery
7.Wipe/Data Factory Reset
8.Flash Rom
9.Flash Gapps
10.Reboot
You can throw in a backup of files somewhere in there if you like.... Your choice
melvinator said:
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
Click to expand...
Click to collapse
I had a bootloop when using CWM v6.0.1.5. So a friend of mine told me he had success with CWM v6.0.1.5 Touch. So I switched to the touch recovery and... SUCCESS.
Here's the link to CWM touch and non-touch:
http://forum.xda-developers.com/showthread.php?t=1893464
A boot loop could mean a bad download or bad flash but it is most definitely NOT a bricked device. All you needed to do was get a fresh download and move it to your SD card by mounting it in recovery. Then, wipe EVERYTHING but the SD. EVERYTHING. Then flash the ROM, Gapps and whatever radio. I go from CM to AOKP to other random TW roms all the time and never have issues.
The 2 best recoveries are twrp or my favorite because I'm used to it is cwm 6.0.1.5. http://forum.xda-developers.com/showthread.php?t=1844637
Also if your phone boot loops don't freak out' just either reboot to see if that works out first and if not reboot into recovery. Also with these new recoveries do not use dark side scripts.
Factory reset
Format system
Format cache
Format data
Flash ROM
Flash gapps
Reboot and enjoy
Sent from my SAMSUNG-SGH-T989 using xda premium
This did it!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Sorry for the necro on the thread, but I didn't want it to be stated I didn't look around some either.
I am going from JMT to CM and want to make sure it's as seamless as possible. I use CWM and usually usually use darkside complete wipes, but I read in a previous post not to use darkside. Is there a reason for this? I can't see why this wouldn't work as it's just a wipe.
Also I use Titanium Backup. Is it possible to backup my apps and data and restore them since its not TW any longer? I want to be able to restore as much of my data as possible and make sure I don't lose it.
P.S. - If thread necroing is not appreciated, I apologize.
I have one S3 that's stock and another that's rooted, so I decided to try CM9 first on rooted S3 because CM10 didn't seem quite ready for daily use. Flashed ROM and Gapps, and things were fine until wi-fi ceased functioning. Worked, then didn't ever again. Nothing I found in searching this helped. And I couldn't get to PlayStore because there was no connection. Tried many things to reset wi-fi, but despite excellent signal, the phone wasn't connected to Internet. I reflashed CM9 (same most current release) but it didn't help.
So, having not actually done anything other than adding ROM Manager, I decided to flash latest CM10 nightly with CWM recovery via ROM Manager. Everything was fine, except of course I forgot I needed to install newer Gapps. However, when I went to do so, ROM Manager was no longer there and manually trying to get recovery only resulted in download mode, which meant I couldn't install Gapps or do much of anything.
I spent time trying to figure out how to get recovery, but having run out of options, I thought it perhaps best to flash back to stock using desktop Odin. I have the MD5 for 4.1.1 LK3. So I did this, but now once past the Samsung and AT&T animations, the phone stops with a Samsung logo. And that's where I'm at.
I know I've seen threads on fixing this, but I can't find them and I would like rectify the softbrick circumstance. What to do.
eduardo_b said:
I have one S3 that's stock and another that's rooted, so I decided to try CM9 first on rooted S3 because CM10 didn't seem quite ready for daily use. Flashed ROM and Gapps, and things were fine until wi-fi ceased functioning. Worked, then didn't ever again. Nothing I found in searching this helped. And I couldn't get to PlayStore because there was no connection. Tried many things to reset wi-fi, but despite excellent signal, the phone wasn't connected to Internet. I reflashed CM9 (same most current release) but it didn't help.
So, having not actually done anything other than adding ROM Manager, I decided to flash latest CM10 nightly with CWM recovery via ROM Manager. Everything was fine, except of course I forgot I needed to install newer Gapps. However, when I went to do so, ROM Manager was no longer there and manually trying to get recovery only resulted in download mode, which meant I couldn't install Gapps or do much of anything.
I spent time trying to figure out how to get recovery, but having run out of options, I thought it perhaps best to flash back to stock using desktop Odin. I have the MD5 for 4.1.1 LK3. So I did this, but now once past the Samsung and AT&T animations, the phone stops with a Samsung logo. And that's where I'm at.
I know I've seen threads on fixing this, but I can't find them and I would like rectify the softbrick circumstance. What to do.
Click to expand...
Click to collapse
Did you remember to factory reset (wipe /data) when flashing the stock ROM? That's the most common cause of soft-bricking in this scenario.
If not, boot into recovery (Vol Up + Home + Power) and do so, then try booting the phone again.
Do I do factory reset from desktop Odin in download mode?
That's one possibility, but if you don't want to go through the Odin process again, you can just do the reset from recovery as I outlined above.
smelenchuk said:
That's one possibility, but if you don't want to go through the Odin process again, you can just do the reset from recovery as I outlined above.
Click to expand...
Click to collapse
Ah...volume UP. But wipe data/factory reset didn't help. If I select update from external storage, would that be MD5 or...?
Okay, I wiped cache partition and I'm in business. No more softbrick. Thanks!
So building and flashing ROMs is nothing new to me. I've been doing this since the Captivate days and have done this with all of my Android devices including my new Kindle Fire 2 (which is running 4.2) but for the life of me, I cannot get a 4.2 ROM running smoothly on my GS3.
Here's the deal. When flashing any 4.2 ROM, I get the same issues. Most times, it takes several (as in at least 8) presses of the Power button or home button to wake the screen. When it finally wakes, the animation on the "unlock" button freezes. I can sometimes still swipe it to unlock but most times, the button itself doesn't move. The phone typically runs fine once unlocked.
I know there are some camera issues still but mine make it totally unusable. I can open the camera but rotating it typically screws the orientation up on screen and no other screen presses work afterward. If I tap to open settings or flash settings, the options show up on screen but then again, screen presses are no longer working. I have to exit camera and start over which typically results in a couple Gallery FCs before it finally opens again.
What I've done to no avail. I've tried multiple combinations of wiping cache, system, dalvik, internal SD card, all within TWRP as well as checking MD5 on the ROMs after they've been copied to my SDCard and am running the latest TWRP available for my phone. I have also tested this without restoring ANY data and using the packaged launchers and I get the same behavior. If I go back to a 4.1.1 ROM, everything is perfectly fine. This ONLY happens on the 4.2 ROMs available.
I'm looking for any help on getting this sorted not because it's a big deal but because it's driving me friggin' insane!
Re: [Q] ALL 4.2.2 ROMs hate my phone. Help thread.
Have you tried CWM Recovery yet? It's what I use and have literally tried every rom put there with no problems ever.
Sent from my SGH-I747 using xda premium
Jirv311 said:
I've tried multiple combinations of wiping cache, system, dalvik, internal SD card, all within TWRP
Click to expand...
Click to collapse
You don't mention it, but did you use the wipe option that is at the bottom left of the TWRP wipe menu screen? The scary looking one that says it's probably not needed?
I do that one every time.
I would restore to stock 4.1.1. Then flash TWRP's latest again and try one more time by flashing something mainstream like CyanogenMod 4.2.2.
Flashing stock ROM's has fixed a couple weird issues for me lately.
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
Jirv311 said:
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
Click to expand...
Click to collapse
Have you tried a different kernel? I run ktoonsez KT747 with Task's AOKP with awesome results. Nothing against Task's underwear kernel, but maybe the 4.2 version just doesn't like your phone.
Jirv311 said:
I just flashed stock 4.1.1 through Mobile Odin Pro, installed CWM Touch, and flashed AOKP 4.2.2 from Task650 and same behavior. In fact, now when I hit the power button to lock the phone, I cannot turn it back on without rebooting the phone by holding power.
I flashed stock through Mobile Odin to try and prevent tripping flash counter but I may just flash from Desktop Odin and try again.
EDIT: Is there an updated boot loader (ICS to JB) that gets flashed through desktop Odin?
Click to expand...
Click to collapse
yes if you flash the 4.1.1 stock file through the desktop odin you will upgrade the bootloader , with the new boot loader everythime you reboot the phone with a custom recovery like cwm or twrp it will raise the flash counter. Here is what I would do. reboot to twrp , wipe data/factory reset , wipe cache wipe dalvic and wipe system. then go to advanced and reboot into bootloader/download mode. once in downlaod mode flash the rooted ics 4.0.4 rom with desktop odin, I was going to link the thread by mrrobinson but it seems someone un-stickied it so your going to have to try and find it.either go back to stock from sammobile.com and root it or get a pre-rooted file. once your back on stock rooted ics download goomanager from the play store. inside the goomanager click install open recovery script. this will install twrp on your phone. after that put the rom you want back on your and follow the op for that rom. do it exactly as it states.I reccomend task650's rom. If you still have a problem try a different kernel. Not all phones are the same, some phones wont even boot up with certain kernel's. hope this helps
edit here is the link http://forum.xda-developers.com/showthread.php?t=1739426
Intub8 said:
yes if you flash the 4.1.1 stock file through the desktop odin you will upgrade the bootloader , with the new boot loader everythime you reboot the phone with a custom recovery like cwm or twrp it will raise the flash counter. Here is what I would do. reboot to twrp , wipe data/factory reset , wipe cache wipe dalvic and wipe system. then go to advanced and reboot into bootloader/download mode. once in downlaod mode flash the rooted ics 4.0.4 rom with desktop odin, I was going to link the thread by mrrobinson but it seems someone un-stickied it so your going to have to try and find it.either go back to stock from sammobile.com and root it or get a pre-rooted file. once your back on stock rooted ics download goomanager from the play store. inside the goomanager click install open recovery script. this will install twrp on your phone. after that put the rom you want back on your and follow the op for that rom. do it exactly as it states.I reccomend task650's rom. If you still have a problem try a different kernel. Not all phones are the same, some phones wont even boot up with certain kernel's. hope this helps
edit here is the link http://forum.xda-developers.com/showthread.php?t=1739426
Click to expand...
Click to collapse
I just did exactly this just now and the same exact symptoms occur. Even after flashing ktoonz kernel. This is the weirdest thing I've ever dealt with.
Jirv311 said:
I just did exactly this just now and the same exact symptoms occur. Even after flashing ktoonz kernel. This is the weirdest thing I've ever dealt with.
Click to expand...
Click to collapse
yes that is very odd. If it works fine on stock or 4.1 rom's then it definatly not a hardware issue with the button. Im sorry man , I have no idea what it could be.
Yeah I'm confused as well. I just flashed the last CM10.0 4.1.2 and it runs flawlessly. Definitely a head scratcher.