Related
Hey everyone,
So this is my last ditch effort to attempt to save my device. I would really prefer not to perform another warranty exchange given that I am not under insurance, but I'm afraid I have no choice.
My phone was rooted and I was using Darkside without issues, as I had been for the past two weeks. I am always careful when I flash roms and I made sure to follow every possible protocol. That's the background information.
My battery life was running at approximately 6 percent yesterday and I sent a text message as normal, and it was stuck at sending. I tried turning wireless data off from the toggles in the pull-down and it was unresponsive. When I went to Wireless Network in the settings option, my phone rebooted. Once it started up again, my service would not come back, and the phone would continually bootloop once it got past the traditional "media scanner running", etc. My window of opportunity to do anything was really slim.
I charged my phone to see if it made a difference, but it didn't. Tried with my SIM card removed and it still bootlooped. I was able to get to CWM from the advanced power menu before it rebooted again and I fixed permissions and cleared cache and dalvik. Now the phone wouldn't even get past the boot animation before rebooting.
I put the phone into download mode and reverted back to stock using Odin. The phone now got past the boot animation in stock mode, but was unable to find service and after about 10 seconds fell into the same bootloop pattern. I tried removing the SD card but that didn't help either. Using Odin again, I reflashed recovery, followed by root and tried reinstalling a rom through CWM (I have only used regular CWM, not the touch version) with a superwipe to ensure a clean flash. Once again, it wouldn't make it past the boot animation before bootlooping. I reverted back to stock using Odin, and this is where I stand.
I have tried all traditional methods to salvage the phone and, for the life of me, I cannot understand what happened. The only thing I notice is that regardless of how long the phone stays on before rebooting, it is never able to find service. It's like the radio or modem broke and the phone has no other choice but to restart forever. But reflashing the stock UVKL1 should also reflash the proper modem and radio, right?
Has this ever happened to anyone? Any suggestions (aside from the typical reverting to stock) as to how I might be able to stop it? I searched but haven't been able to find a situation quite like this one. Thanks in advance for your help.
Really sorry to hear about your problem. Assuming the 2.3.6 stock image you flashed via Odin is the one provided by Przekret and that that didn't work, then I'd try one or both of these two longshots to try to clear possible corruption problems in either the kernel or modem spaces:
For each of the following wipe cache and Dalvik cache in CWM before flashing and again wipe Dalvik afterwards and also fix permissions:
1) Format system (do this 3x) under mounts & storage in CWM. Flash the standalone Darkside kernel X v1 final immediately after flashing, e.g., the current Darkside rom. (You'll need to wipe data, too, if not coming from a Darkside rom. Do not do any Superwipe - neither the standalone version nor using a flag.)
2) Flash the KID modem (do this 3x). Both Odin- and CWM-flashable versions are available. (You can always flash back to KL1 if the problem is fixed.)
Hope this is clear. It's late! These are both things that have helped get my phone out of troubles, though not as bad as yours. Good luck!
Sent from my SGH-T989 using XDA App
Also if u used the one from przekret then I'm almost positive that Odin package flashes the new radio too. If memory serves me right. Op let us know what happened
Thanks for your help. Unfortunately, nothing has worked. I'm on the phone with T-Mobile, I see no other solution but to get it exchanged under warranty and it's not getting here until March 15th, according to the representative. I suppose I'll just use a replacement phone in the meantime. It's just really weird and frustrating... I could understand a bad flash or something similar, but I followed every step accurately as I always have and everything was working just fine until it randomly decided to die without warning.
Well since you're getting another one anyways I would continue trying to fix this one, just in case you come up with a solution and for another worst case scenario for your new phone.
Powered by the SGSII....
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
shehrammajid said:
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Forgive me for asking, but what is the EFS folder?
I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Gzerner said:
I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Click to expand...
Click to collapse
K. The reason you aren't getting to the old version of CWM is because you flashed Codename. Codename is an AOSP ROM which has been known to cause bricks when flashing with Rogue. Because if the bricks the developers opted to but include CWM of any kind in the kernel. What you need to do is find a replacement ROM and download it. Once you've downloaded it you need to flash the EL26 stock CWM (you can find it in the OP of the link below) then use it to flash your new ROM.
http://forum.xda-developers.com/showthread.php?p=295021
Well you're at it is suggest reading the How Not To Brick Your Phone thread in general.
Good luck!
Codename rom is an AOSP rom so your external SD storage will be under /emmc and not /sdcard/externalsd. That's why it wasn't showing up. Same thing with CM9 and AOKP, not because it doesn't work. Also I wouldn't recommend flashing anything ICS related from rogue recovery, js.
And recoveries changed because with our phones, the recovery is packed into the kernel itself so when you flashed Codename, the recovery changed to the stock recovery included with the roms kernel. Hope that clears it up lol.
Sent from my SPH-D710 using Tapatalk
If you want a fresh install, the best way is to Odin the el29 kernal. From there, get into your recovery and wipe and flash away.
Sent from my SPH-D710 using XDA
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Re: [Q] Any possible ways to unbrick a softbricked SHGI747
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:
MeatwadGetTheHunniesG said:
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:
Click to expand...
Click to collapse
No problem at all =) Its pretty hard to completely brick your device unless you flash something made for a different phone lol. As long as your phone can see any signs of life (even a faint vibration), let us know and we are more than happy to help!
Sent from my SGH-I747 using xda app-developers app
I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.
S.O.S. Phone is completely wiped only dowload mode and recovery work.
Okay so I think I kind of put myself in a sticky situation. I tried to flash a custom rom onto my phone but in the process deleted my modem file everything worked fine except for the fact that I couldnt make calls or text messages. Basically a $400 dollar multimedia device. At this point I just want to put my phone back to the way it was when I got it at the AT&T store. My phone model is SGH-i747 Galaxy S3 that came with JB 4.1.1 pre installed.
I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.
Click to expand...
Click to collapse
Out of curiosity, how did you finally manage to brick it?
Sent from my Nexus 7 using xda app-developers app
solution
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
There's another thread called stuck on boot screen with same issue. Had same issue with simular Rom had to boot in recovery and clear cache and user settings. And no longer an issue
Soft bricked...
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?
kinjo1023 said:
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?
Click to expand...
Click to collapse
I think I did someting like that too nd now I cant install any ROM and TWRP complains that I have no OS inside the phone.I tried modifying the assert-script file but it then eventually ends up at STATUS 6 and not status 7 again.Pls and Pls help us
You have to be on twrp 2.7.x to install any kk ROMs.
Sent from my SGH-I747 using Tapatalk
Hi
Guys i need your help. Pleas can someone tell me for now what mods is much better for I927R (Also withe very stability and with much less bugs) ?!
I found Liquid Smooth but it have some problem so i need your guide about other mods.
Thank you
ICS Roms are the best and most stable... Stock ICS from AT&T UCLJ3 or any roms based off of it ... Dman's daily driver, Ice Pop Rom by RawRaw, LiteRom by TheGreaterGood...
Unfortunately none of those are being maintained but I had been running Dman's for the last couple months, great battery life when paired w/ JuiceDefender (20+hours of heavy use when I'm not sleeping).
Now the newest CM10.1 by Spyke seems pretty solid ... Just a couple of issues.
ICS is the only one you'll get bug free, though. Stock is hard to compete with when we're pairing up roms without a true Devdeloper.
On this subject, I've just reverted back to using IcePop ROM after (unhappily) downgrading from Spyke's latest 10.1 ROM - just mainly because of the Bluetooth headset issue, which I really need working for work purposes.
I'm just wondering if there are any ICS builds that have GPS working correctly? I tried flashing the Rogers modem (since my phone was originally a Rogers import, flashed to AT&T ICS, then played with ICS from there) and first time I ran GPS status it took 771 seconds... I'm going to keep trying just in case that was the first time only, but 12 minutes is still a very long time for an initial fix .
Also - I've found that I'm getting more and more bootloop problems even with clean installs - so wiping cache, data, dalvic, etc. Is there some way to do a *thorough* wipe without bricking the phone? I can back all my data up no worries, but next time I move to JB (in the optimism that the BT issues will be fixed soon, judging by the positive progress being made by Spyke ) I would like to do a clean build from scratch and not have to gamble being able to start the phone up again
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
I, also, had reverted to using JB Because GPS wouldn't work ... There's a thread in here (search for it) that shows the solution to the GPS fix, its editing sirgps.conf and gps.conf ... I was getting a fix on GPS in under 30 seconds.... GPS was a huge let down in the stock ICS rom, Even when using TheGreaterGoods LiteRom w/ GPS fix I found after a couple of days my gps didn't hold....
Thanks for the reply.
I was considering formatting /system this morning when I was getting stuck in a boot loop from trying to get M3 running, but decided it was a risk I'd have to check up on first . Next time I do a build from scratch (I'm going to resist until the BT stuff is working - fingers crossed!) I'll do that.
I remember having a look at the gps.conf fix but don't recall anything about sirgps.conf - so I will look it up, thanks!
As an aside, I've been checking the GPS fix a couple of times since my last post and it is coming up in under 30 seconds each time... I'm wondering if my attempt to flash the Rogers modem did in fact fix the issue... I'd do a reboot but I'm too scared I won't get the phone up again XD
EDIT:
Found the fix, I did a few of the changes (rather than all of them), and it's now picking up 8 satellites instead of 3-5, and getting a stronger signal from each... and all I did was point it to the AU ntp server, and tell it I'm not on the ATT network . I'll save the suggested settings to a text file on my SD card so next time I'm out and about and if it plays up I'll have access to the details.
yohan4ws said:
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
Click to expand...
Click to collapse
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
davidpartay said:
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
That has to be very concerning to you, I've never had an issue booting any ROM. And very strange flashing the Kernel separately would resolve your booting issues...
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
If I were in your position I would try and do a full revert back to the earliest version of gingerbread I could find on samfirmware and then use Kies to udpate - THEN I would retry flashing to a newer JB or ICS Rom.
Pretty time consuming but that is the price we pay to mod
davidpartay said:
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
yohan4ws said:
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
Click to expand...
Click to collapse
Not yet. I'll have to check which ones I have - I'm certain I have the AT&T ICS rom from November but then I'd have to go digging through my email for the unlock code again, so I'm trying to avoid doing that at this point . If i can find the stock GB Rogers rom at some point I might flash that one back on before I do any more upgrades. The phone is up and running at this point though, so I'm not too fussed. I've also noticed that it's a little quicker than before so I think the version of LiteKernel I installed was a good idea anyway.
bubor said:
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
Click to expand...
Click to collapse
I've tried pulling the battery a few times, but probably no longer than 30 seconds. Next time I'll give it a couple of minutes. I tend to do this late at night when I'm not expecting any calls (except fire brigade but I have a pager for that too) so time without a phone is no issue to me
Yesssss
After much irritation at continually getting stuck in boot loops again, I've 'Oneclicked' the phone twice, got fed up with the AT&T ICS ROM within about 5 minutes, gave up on IcePop because of buggy GAPPS...
And thought, bugger it. Format /system. Factory reset. Clear cache + Dalvik. Installed in this order:
Jellybean 4.2 ROM from 0217
Spyke's M3 update
PAC rom
GAPPS dated 0427
"Kick-ass Kernel"
and it BOOTED FIRST GO
I am pleased
Does JB need already to be installed before putting the M3 revisions on? Maybe that's where I've been going wrong all along, because my attempts at running both the standard M3 and PAC ROM (even immediately after OneClicking) resulted in boot loops or eternal boot loading.
Uhh... what do you mean by "One Clicking" ??
I know there's a "superoneclick" that will flash and root the rom all at once, but I never personally found it to work for our glides.
Using CWM and installing the ROM through the CWM boot menu is severaly key presses so ... not too sure what you're referring to.
Also, I've always downloaded to a hardwired computer then copied over USB to my phone and flashed ... sometimes the download will have errors if I grab it from my phone.
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
davidpartay said:
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
Click to expand...
Click to collapse
Interesting... for future reference, www.samfirmware.com has the stock firmwares, then there's the superUser file floating around the forums that allows you to root by flashing it. Passed that, remove bloat.
Glad you got it working! Welcome to JB
Hi everybody, I was hoping to get some help here. Be warned, this is a long story.
I was running CM10.1 fine. My phone was lagging for some reason. A quick search told me to clear my cache. I did. I flashed the Darkside cache wipe. Now my phone wouldn't boot. There would be a Samsung Splash screen, then nothing and my phone would (try to) reboot. Again and again.
My (external) SD card had been acting up a lot. It wouldn't be recognized, copies would be slow, and all sorts of problems. So I formatted it. It worked fine. I assumed my phone was back to normal.
I restored my phone to stock via ODIN. It would reboot at first, but I That worked fine. I was happy until I needed my Wifi hotspot back. I rooted via Odin. The Deleting of tethering provision no longer worked. I flashed the Darkside ICS Rom. That worked fine. I missed Jelly bean/stock android. I flashed CM10.1 along with a fresh download of the Darkside cache and data wipes.
The phone didn't boot. Same problem as before. I assumed same solution. I got a PASS! and unplugged the phone. At this point, It showed the stock splash screen (Galaxy SII, Android 4G etc.) and then an animation of the Android with some blue 3D figure spinning in his belly. The %age status bar at the bottom reached 30ish% then stopped. The animation continued and the bar remained at 30% for a very long time. I tried to reboot normally, which would result the Splash screen with a %age bar at 99%, frozen, and to enter recovery which gave me a splash screen then this:
-- Verifying internal MMC block...
Not need checksum confirmation
already executed!!...
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC
This is character to character what I read, and there seems to be a dead android with a red triangle in his belly in the back ground.
I can consistently reproduce these two situations, both of which are disturbing. I could try to restore via Odin for the third time, but I risk making things worse.
Thanks for reading the essay. Until I can somehow fix this, I'm stuck with Hercules in a coma.
Any help is appreciated.
step one, flash twrp (2.5.0.0) via odin
step two, wipe everything except external sd
step three, flash whatever rom
the end
What are you restoring your phone to...ics or jb?
Sent from my Infamous Hercules.
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
ClaireH said:
step two, wipe everything except external sd
Click to expand...
Click to collapse
Are you trying to make him wipe his internal storage as well? :sly: lol
Sent from my Infamous Hercules.
ClaireH said:
step one, flash twrp (2.5.0.0) via odin
step two, wipe everything except external sd
step three, flash whatever rom
the end
Click to expand...
Click to collapse
I did the same thing day before, actually. Only I flashed CWM via Odin. I could now access recovery, but flashing CM gave me the same no boot problem. Funnily, resetting to stock actually worked after I did this!
Obviously I'm not happy with stock. However I am hesitant to mess with my now fully functional phone.
And without starting a flame war, would using TWRP give me different results?
Oh yeah, iburnhearts, I resetted to the (I think) latest stock JB, 4.1.2. Should it matter? I heard there was a difference in where the SD card was located or something.
I will make a backup before trying TWRP this weekend.
Thanks for all your help.
sauprankul said:
I did the same thing day before, actually. Only I flashed CWM via Odin. I could now access recovery, but flashing CM gave me the same no boot problem. Funnily, resetting to stock actually worked after I did this!
Obviously I'm not happy with stock. However I am hesitant to mess with my now fully functional phone.
And without starting a flame war, would using TWRP give me different results?
Oh yeah, iburnhearts, I resetted to the (I think) latest stock JB, 4.1.2. Should it matter? I heard there was a difference in where the SD card was located or something.
I will make a backup before trying TWRP this weekend.
Thanks for all your help.
Click to expand...
Click to collapse
Glad to hear you're phone is fully functional...stock jb touchwiz isn't too bad in my experience especially now since a lot of the newer cm10.1, pacman and carbon nightlies are having SODs and RRs.
As far as twrp vs cwm...in my experience twrp has a much simpler user interface which makes it easy to wipe amd theres no need for the darkside scripts. Although if you want to flash a custom touchwiz jellybean ROM then you would need the infamous wipe scripts which are similar to dark side but they've been updated by Jamison.
Sent from my Infamous Hercules.
Hi everybody,
I flashed CWM via ODIN, then I flashed the TWRP .zip. It was easy enough. Then I flashed CM 10.1, gapps and a custom boot animation by nozerogravity (keywords CMX boot animation). All went surprisingly well, and the welcome screen alleviated my concerns.
There still remains the problem that originally worried me something was wrong with my phone: it would lag during the simplest of games. Until I tried other ROMs I didn't know that this was a known issue with CM 10.1. I simply had to lock and unlock to temp fix this problem.
TWRP is much simpler and cooler than the classic CWM. Also, why did CWM conk out on me so? That is the real question. The evidence seems to point to CWM, however, I am reluctant to blame such an established piece of software, esp. considering the fact that it's free.
Thanks everybody, for the help!
*Nota bene: No wiping scripts were needed with TWRP, neither Darkside nor Infamous (I'm not familiar with the latter)