chainfire app just completely damaged my 500$ samsung Galaxy s when I installed the DRIVERS and when I started the reboot so the drivers take effect and it got stock on doot logo. And I got to Recovery menu and I had a old backup but when I was restoring , the phone canceled and switched off and it got stock on the Vibrant logo. No recovery menu, no flashback. Nothing!!! I send the phone to experts and they told me that the phone is total wasted... if you know how to fix it ,tell me how. Its an Gallaxy s vibrant t959 t-mobile
On the list of soported android phones it was my gallaxy s and it was an lie!
If ther eny way to demand the app on playstore.... answer that to...
THANKS
Betfoyet said:
chainfire app just completely damaged my 500$ samsung Galaxy s when I installed the DRIVERS and when I started the reboot so the drivers take effect and it got stock on doot logo. And I got to Recovery menu and I had a old backup but when I was restoring , the phone canceled and switched off and it got stock on the Vibrant logo. No recovery menu, no flashback. Nothing!!! I send the phone to experts and they told me that the phone is total wasted... if you know how to fix it ,tell me how. Its an Gallaxy s vibrant t959 t-mobile
On the list of soported android phones it was my gallaxy s and it was an lie!
If ther eny way to demand the app on playstore.... answer that to...
THANKS
Click to expand...
Click to collapse
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
Odin back to stock.
If you're on jb, I bet it doesn't work. If on older rom, try an ics one.
Sent from my Galaxy S III
500$ Samsung Galaxy S eh? If you paid for $500 for your vibrant anytime within the last year or so, then I think you have bigger problems to worry about than a brick.
Also, you really shouldn't house any animosity towards Chainfire. He is an excellent developer who has done so much for the modding community.
As for Chainfire3D, I can tell you from first hand experience that it does, in fact, work for the Vibrant. Please keep in mind that with anything involving modding your device, you accept the risk onto yourself willingly.Chainfire did not force you to do anything, that was your choice - you ought to think about these things before suggesting that he lied in regards to the supported devices, you just did not read the directions properly. How do I know this? Because in the description of the app clearly says, and I quote,
"!! For Froyo and Gingerbread ONLY. NOT COMPATIBLE with Honeycomb/ Ice Cream Sandwhich/Jelly Bean !!"
Guess what CM10 is. That's right, not Froyo or Gingerbread.
I used cf3d with ics perfectly fine, actually.
Sent from my SGH-T999 using xda app-developers app
iKoolkid said:
I used cf3d with ics perfectly fine, actually.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I did too actually... But that isn't the point ^^ when I used chainfire on ICS I had already talked with enough people to know that it worked... but I was still accepting the potential risk that it would not work since chainfire didn't recommend using it on anything above gingerbread. I never used it on jb because I heard stories that it didn't work and could really damage the phone... I did my research and read before doing things, this person just jumped in blind and is blaming a respected dev for his own inability to read.
Sent from my Galaxy S3
Xenoism said:
I did too actually... But that isn't the point ^^ when I used chainfire on ICS I had already talked with enough people to know that it worked... but I was still accepting the potential risk that it would not work since chainfire didn't recommend using it on anything above gingerbread. I never used it on jb because I heard stories that it didn't work and could really damage the phone... I did my research and read before doing things, this person just jumped in blind and is blaming a respected dev for his own inability to read.
Sent from my Galaxy S3
Click to expand...
Click to collapse
True, true. Well maybe my vibe got damaged from the soft brick cf3d used. But yes, from both of us, OP, READ. Search before you post and right now, odin to stock and you have to start from stock, then ics, then jb. Do not restore a backup of a jb rom from an ics, froyo, or anything non jb. Same with other versions, because you can bootloop or soft brick the phone. You're lucky it is just soft bricked.
EDIT: If you have read...
1. Sending the phone to the experts (whom probably have specific knowledge of vibrant rooting and bricks) would've been off your list.
2. You would've known NOT to restore that backup.
And now, as many have said, we or any other devs are not responsible of your flashing even if it should've worked and we are also not responsible for things leading:
Bricks
Dead sd cards
Eu bug
Death of a loved one from brick rage
A hole in your wall from above reason
Thermo-nuclear war
Or catz poppings ups frum ur screenz afdur downroading rom asking fur cheezbergers.
Or a phone repairer finding pr0n on your phone when checking it out. We all know how bad that is.
Sent from my SGH-T999 using xda app-developers app
we have the same situation.. in my case it just boot loop.. i try to restore, but it keep restarting..
so back to stock, GB, and to cm10.1 again.. (do I need to flash GB if my stock rom is eclair before flasing to JB?) good thing to have a titanium backup! my phone usable again after more or less 20mins.
Yes. Flash cm7 first.
Sent from my Galaxy S3
Xenoism said:
Yes. Flash cm7 first.
Sent from my Galaxy S3
Click to expand...
Click to collapse
thanks! now I dont install chainfire anymore..
iKoolkid said:
If you're on jb, I bet it doesn't work. If on older rom, try an ics one.
Sent from my Galaxy S III
Click to expand...
Click to collapse
Noooo my problem is not the Rom... my problem is that my sgs vibrant. It's stock on vibrant logo. First boot picture, not boot loop.
It doesn't open recovery!
You enabled chainfire drivers on jb (first mistake) and then you tried to restore a stock backup of eclair while you were still on jb (second mistake). You can't jump from jb down to stock like that, only from jb to ics and some later versions of gingerbread. What you want to do is boot into download mode and revert to stock the correct way. The moral of the story is when messing with your phone, read, read, read before doing anything ever. You're lucky, because it sounds like your phone will be just fine if you properly Odin back to stock via download mode. However, I warn you...if you Odin wrong, there is a good chance of ruining your phone, so read this time and make sure to do it correctly.
Sent from my Galaxy S3
Related
hey guys,
i just bought a samsung galaxy s2, rooted it with odin/superoneclick... works fine but i need to go back to a regular, vanilla galaxy s
i used super one click to unroot the phone, but i still get that yellow warning triangle every time i start up my phone. so i think it has something to do with that odin thing or whatever... again, super illiterate... i just really need to go back to a normal, no root, nothing regular old galaxy s 2! i'd really appreciate it guys. thanks so much!
There is (currently) no way to return to stock Bell i9100m. The firmware just hasn't been released. For future reference, do a little more reading before you flash anything as this has been mentioned in almost any thread flashing a Bell Galaxy S2 is mentioned.
Why do you want to go back anyway? Are you having some sort of problem? Is it for warranty service? If it's just the yellow triangle that's bothering you there are ways to get rid of that, use the search. Since you're still on the original firmware, at this time you will be able to get everything back to stock except the kernel.
Yep, as the poster above me mentioned theres no way to completely go back to "bell stock." Though if you just want unrooted samsung stock, flash any of the plethora of official samsung odin updates out there (kg3,kg6 etc) imo they are better anyway, no bloat and they perform better. Plus they will get rid of that pesky triangle thats bothering you so much.
Regards
could you provide a link please?
avneetsidhu said:
could you provide a link please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1194550&highlight=xxkg6
thats the thread for one of the MANY updates available for the SGS II, look around you'll find tons of roms. Research how to work odin before you flash though (if thats what you are going to do) odin can easily brick your phone if you don't know what you are doing.
while i have you here... i did the odin thing, i figured, **** it, might as well just use these custom kernel things.. i have no idea what they are or do. i just flashed ninphetamine or something... what exactly does it do? also, how come titanium back up etc say that it is not rooted. do i need to do the superoneclick?
Before you continue i would suggest you start reading before flashing/doing anything more. Its scary when people flash stuff without gaining the minimum knowledge to understand whats involved and the consequences. We could hold your hand and tell ya this and that but its been said many times before in this very forums.
Sent from my GT-I9100M using XDA Premium App
Hey folks,
I just bought the white international SGS II and i'm loving it!
I previously had an Infuse 4g, so I am pretty experienced with flashing/backing up/ restoring...but I have questions/concerns regarding the I9100.
I am about to try out the CM9 Unstable, so I backed my current stock ROM up using CWM Manager 3.0 (I am on CF-Root 5.0) onto my Internal SD, as I do not have an external SD card.
Now, I have had bad experiences with CM7 with Infuse and ended up not being able to restore due to many problems like MD5 mismatch, different CWM version, and problems while restoring ( I think it said something like devblock??)
So I'm pretty worried about not being able to restore back to the backup i just made.
So correct me if I'm wrong folks,
1) Go into CWM, flash CM9(once? twice?), Gapps, Faceunlock,
2) Data wipe/factory reset
3) Reboot
and should I choose to restore back to the stock Rom backup,
just go into CM9's recovery and restore..?
will this method give me problems restoring? will I have different versions of CWM recovery from the one I have currently? Is there any way to check if my back up was made properly?
Thanks a lot folks! Appreciate it!
Edit: "Make sure you're already running ICS bootloader (if not, go to SamMobiles and flash XXKP2 bootloader)". Is this necessary? Cus I have seen some folks say that they've not and was fine installing CM9.
First the procedure:
1. Wipe
2. Install CyanogenMod 9
3. Reboot
4. Install CyanogenMod again
5. Install gapps and face-unlock
Worked for me every time.
Your backups should work unless there were errors while creating them.
If you want some more safety, you can create a new backup after flashing the Siyah-kernel. The latest version uses the same version of ClockWorkMod as CyanogenMod 9.
Whether you need to flash the bootloader or not, depends on whether you already have it or not. I'm running galnet-MIUI and already had the bootloader installed. I don't know how to tell if you have it.
Sent from my GT-I9100 using XDA App
Ok...
I did further research and found out that Nandroid backup backs up everything EXCEPT the kernel.
I'm pretty sure that CM has its own kernel...but will it be CWM 5.0.2.7(the one i made backup in.)?
If it's not, the correct steps for me to restore my nandroid back up is to
1)boot into download mode from CM9,
2) put the cf-root kernel that i used in the ODIN PDA, flash,
3) turn off phone, reboot into CWM, then restore my nandroid back up right??
Can anyone please confirm this method??
I only have this phone and I cannot risk soft-bricking or hard-bricking this beautiful device.
Thanks in advance!
Also, i made a back up in blue recovery of CWM 5.0.2.7..does that matter?
TheSniperFan said:
First the procedure:
1. Wipe
2. Install CyanogenMod 9
3. Reboot
4. Install CyanogenMod again
5. Install gapps and face-unlock
Worked for me every time.
Your backups should work unless there were errors while creating them.
If you want some more safety, you can create a new backup after flashing the Siyah-kernel. The latest version uses the same version of ClockWorkMod as CyanogenMod 9.
Whether you need to flash the bootloader or not, depends on whether you already have it or not. I'm running galnet-MIUI and already had the bootloader installed. I don't know how to tell if you have it.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
thanks for the reply,
so I must have the ICS bootloaders in order for CM9 to work?
ooo siyah kernel method... that makes it easier! haha thanks so much!
I will proceed to do that!
btw, how is CM9 working for you?
do you think you'll be able to use it as a daily driver now that NITZ is gone??
1. Afaik cwm backs the kernel up and restores it too. (afaik = 99.9% sure, in this case)
2. CyanogenMod ships with its own kernel.
3. The kernel is not cwm. ClockWorkMod is just the recovery that is integrated into the kernel. CyanogenMod 9 has cwm-recovery 5.5 (Siyah too btw)
4. You don't need to use download-mode to restore.
Sent from my GT-I9100 using XDA App
You must have ICS-bootleggers. He did not say that for fun xD.
Is it suitable as daily driver for me?
Nope.avi
Why?
Accelerometer is unresponsive, so it takes forever to flip your screen.
Battery drainage is horrible.
Camera isn't working properly.
And the biggest no-go for me:
The device gets way to hot when using it.
Sent from my GT-I9100 using XDA App
TheSniperFan said:
You must have ICS-bootleggers. He did not say that for fun xD.
Is it suitable as daily driver for me?
Nope.avi
Why?
Accelerometer is unresponsive, so it takes forever to flip your screen.
Battery drainage is horrible.
Camera isn't working properly.
And the biggest no-go for me:
The device gets way to hot when using it.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
alright,
thanks for the information!
I'll flash the Siyah kernel
Btw,
Flashing CM9 Zip does not flash the ICS bootloader right?
so then if I want to restore to my GB 2.3.5, would I need to flash GB bootloaders before restoring via Odin??
If the zip would flash the loaders, he wouldn't have mentioned it.
They're backwards-compatible.
Sent from my GT-I9100 using XDA App
If you need to make a post in the Q&A forums about flashing CM9, then you are definitely not the sort of person who should be flashing it. It is in very much a beta stage and there is a very high possibility it will **** your phone up even if you have done nothing wrong. If that happens you need to be the sort of person with enough experience to solve the problem by themselves. If you are asking questions before you've even flashed it then really, it's not for you. Use CM7, at the moment it's better than CM9 in every single way.
postfatal said:
If you need to make a post in the Q&A forums about flashing CM9, then you are definitely not the sort of person who should be flashing it. It is in very much a beta stage and there is a very high possibility it will **** your phone up even if you have done nothing wrong. If that happens you need to be the sort of person with enough experience to solve the problem by themselves. If you are asking questions before you've even flashed it then really, it's not for you. Use CM7, at the moment it's better than CM9 in every single way.
Click to expand...
Click to collapse
It's not thaaaaaaaaat bad. I mean, he won't be able to brick the device through cwm.
If he doesn't ask, he will never learn and it's always better to ask twice than to break something.
Sent from my GT-I9100 using XDA App
Thank you sniper =) really appreciate the support.
Ive been flashing and restoring before with my infuse 4g. Just sometimes ran into problems with restoring with diff CWM versions and stuff. This phone is very precious(expensive) so i thought i would learn it for sure before i attempted anything.. thanks anyways for sharing your opinion!
Sent from my GT-I9100 using XDA App
TheSniperFan said:
It's not thaaaaaaaaat bad. I mean, he won't be able to brick the device through cwm.
If he doesn't ask, he will never learn and it's always better to ask twice than to break something.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I couldnt agree more... i think people here on XDA need to stop trying to be all hot **** saying Oh you asked a question your a noob... in reality most ppl here want to ask the same question but dont because afraid of getting *****ed out... and when someone else asks... try to be badass and put the person down...
Iv used a Galaxy S and a Moto Atrix and now a S2... flashed the life out of each phone along with all kinds of stuff and mods... yet i would have wanted to ask these same questions before flashing hence googled and found this thread... So thanks to those that replied as well... i was about to flash ics till i read this and guess imma hold back now even more...
But again i think people here need to calm the hell down... a person asks a question in the thread and you call them a 'noob' and what not... a person asks a question in the Q&A section and again you tell them off... stop being such anal retentive trolls...
DrunkFuX666 said:
I couldnt agree more... i think people here on XDA need to stop trying to be all hot **** saying Oh you asked a question your a noob... in reality most ppl here want to ask the same question but dont because afraid of getting *****ed out... and when someone else asks... try to be badass and put the person down...
Iv used a Galaxy S and a Moto Atrix and now a S2... flashed the life out of each phone along with all kinds of stuff and mods... yet i would have wanted to ask these same questions before flashing hence googled and found this thread... So thanks to those that replied as well... i was about to flash ics till i read this and guess imma hold back now even more...
But again i think people here need to calm the hell down... a person asks a question in the thread and you call them a 'noob' and what not... a person asks a question in the Q&A section and again you tell them off... stop being such anal retentive trolls...
Click to expand...
Click to collapse
Most people should not flame some one as long as they show they have at least tried to look for an answer first. Yes we were all new at one time but we all learned.
Like you said you Googled and found your answer. Not that hard.
Think it's bad now. Should have seen it a few years ago. Lol clutter up the threads with questions that the answers were found with a search. You got warned. Do it twice and you went on vacation for a few days to learn how to search. So the next time you think people are being too hard. Remember it is not as hlbad as it was.
When I search for the answer, I ended up here.
are these considered ICS bootloaders? If not, when would you flash them, because they are completely unmentioned in any of the instructions or FAQs
CWM flashable Modems:
XXKP8 Modem: http://www.multiupload.com/64J2P1MZL6
XXKP4 Modem: http://www.multiupload.com/NYUYFOT1ST
hello all,
i have followed entropy512's thread here to get my at&t samsung galaxy s2 rooted with stock settings...i then wanted clockworkmod recovery so i went to this and followed directions to get everything installed...everything was ok and working until a few weeks ago when the 'Check Update' option under Setting stopped working...
basically what happens is when i goto Settings-> Software Update->Check for updates->Hit OK (Check the AT&T server for new software update?) a dialog comes up that says 'Checking for software updates...' and nothing happens...i have left the phone over night with device management app checking for software updates... when this used to work, it took less than 1 minute to check...
finally, the only way for me to stop this is to go and force stop Device Manager under Applications->All, so before i restore the phone to factory, i was wondering if anyone knows what might be the issue here?
Thanks,
FI
fastindy said:
hello all,
i have followed entropy512's thread here to get my at&t samsung galaxy s2 rooted with stock settings...i then wanted clockworkmod recovery so i went to this and followed directions to get everything installed...everything was ok and working until a few weeks ago when the 'Check Update' option under Setting stopped working...
basically what happens is when i goto Settings-> Software Update->Check for updates->Hit OK (Check the AT&T server for new software update?) a dialog comes up that says 'Checking for software updates...' and nothing happens...i have left the phone over night with device management app checking for software updates... when this used to work, it took less than 1 minute to check...
finally, the only way for me to stop this is to go and force stop Device Manager under Applications->All, so before i restore the phone to factory, i was wondering if anyone knows what might be the issue here?
Thanks,
FI
Click to expand...
Click to collapse
The issue is that you're rooted, I wish people would search more
Sent from my SGH-I777 using Tapatalk 2
Nick281051 said:
The issue is that you're rooted, I wish people would search more
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
umm this option was working until a few weeks ago and it randomly stopped so im not sure what rooting has to do with it...furthermore, i did search using various permutations of words around the issue at hand, and i did not find threads that addressed this issue...
fastindy said:
umm this option was working until a few weeks ago and it randomly stopped so im not sure what rooting has to do with it...furthermore, i did search using various permutations of words around the issue at hand, and i did not find threads that addressed this issue...
Click to expand...
Click to collapse
Being rooted you shouldn't even worry about updates, if you had actually searched you would have seen that
Sent from my SGH-I777 using Tapatalk 2
fastindy said:
umm this option was working until a few weeks ago and it randomly stopped so im not sure what rooting has to do with it...furthermore, i did search using various permutations of words around the issue at hand, and i did not find threads that addressed this issue...
Click to expand...
Click to collapse
OTA updates require factory recovery. I'm a bit hazy on the details but I believe CWM, in short, replaces that.
It might also be because you either turned off/uninstalled or inadvertently removed factory bloatware.
BROKKANIC said:
OTA updates require factory recovery. I'm a bit hazy on the details but I believe CWM, in short, replaces that.
It might also be because you either turned off/uninstalled or inadvertently removed factory bloatware.
Click to expand...
Click to collapse
This. Amongst other things. If u insist on trying to eventually upgrade to whatever crap gets pushed out to us yer best bet is to do a full wipe to completely stock firmware.
Nick281051 said:
Being rooted you shouldn't even worry about updates, if you had actually searched you would have seen that
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
once again, the issue is not weather i should worry about updates or not nor did i search for if i should worry about updates...this option was working and something happened that caused it to stop working...and my searches i did was around getting device management to connect to the dm server (which is where the 'Checking for update' got stuck)
BROKKANIC said:
OTA updates require factory recovery. I'm a bit hazy on the details but I believe CWM, in short, replaces that.
It might also be because you either turned off/uninstalled or inadvertently removed factory bloatware.
Click to expand...
Click to collapse
Phalanx7621 said:
This. Amongst other things. If u insist on trying to eventually upgrade to whatever crap gets pushed out to us yer best bet is to do a full wipe to completely stock firmware.
Click to expand...
Click to collapse
both of you seem to be spot on...i didnt realize that removing bloatware which was marked as 'ok to remove' on the document of things to remove safely could have been the issue...initially i had frozen them using titanium...neway i restored the phone using the CWM backup i had and the option started working like expected...thanks for the input
I'm curious...why do you want that option to work?
mattdm said:
I'm curious...why do you want that option to work?
Click to expand...
Click to collapse
so that i can get ICS when AT&T releases the official one... i know there are leaked versions out there, but i dont mind the wait, especially, from the research, i have found people having issues with various features
fastindy said:
so that i can get ICS when AT&T releases the official one... i know there are leaked versions out there, but i dont mind the wait, especially, from the research, i have found people having issues with various features
Click to expand...
Click to collapse
Do you recall all the issues with UCKK6 Gingerbread? That was an AT&T release. The devs had to tear it apart to debug and try to fix it. Any build will have bugs in it. But generally, custom firmwares will have fewer bugs than AT&T firmware.
mattdm said:
Do you recall all the issues with UCKK6 Gingerbread? That was an AT&T release. The devs had to tear it apart to debug and try to fix it. Any build will have bugs in it. But generally, custom firmwares will have fewer bugs than AT&T firmware.
Click to expand...
Click to collapse
unfortunately, i joined the android bandwagon only when i got my samsung galaxy s2, which was a little late in the game, so i have no clue on all the start up issues that people experienced with Gingerbread release...
for now ill need to stick with stock/At&T firmware however ill make the switch to custom firmwares when i stop being lazy and create a USB jig for myself...
fastindy said:
for now ill need to stick with stock/At&T firmware however ill make the switch to custom firmwares when i stop being lazy and create a USB jig for myself...
Click to expand...
Click to collapse
Why would you need a jig? You're already rooted with CWM.
fastindy said:
so that i can get ICS when AT&T releases the official one... i know there are leaked versions out there, but i dont mind the wait, especially, from the research, i have found people having issues with various features
Click to expand...
Click to collapse
I've been running AOKP by Task for a while and have never had a serious issue. The one's I have had were self inflicted and with some reading were quite easy to fix.
BROKKANIC said:
Why would you need a jig? You're already rooted with CWM.
Click to expand...
Click to collapse
if my research that i conducted a while ago is right, then basically samsung has implemented a flash counter which increments each time you flash a custom, non-stock rom...it might also be applied to non-stock kernels/firmwares as well (im not too sure)...so to prevent the flash counter from ever incrementing, ill need to put the phone in download mode using the jig and continue from there...
grubby0 said:
I've been running AOKP by Task for a while and have never had a serious issue. The one's I have had were self inflicted and with some reading were quite easy to fix.
Click to expand...
Click to collapse
alright thanks, ill check it out
fastindy said:
if my research that i conducted a while ago is right, then basically samsung has implemented a flash counter which increments each time you flash a custom, non-stock rom...it might also be applied to non-stock kernels/firmwares as well (im not too sure)...so to prevent the flash counter from ever incrementing, ill need to put the phone in download mode using the jig and continue from there...
alright thanks, ill check it out
Click to expand...
Click to collapse
This is wrong. It is only incremented when you use ODIN to flash nonstock items. CWM has no bearing on flash counters.
Sent from my HTC One X using Tapatalk 2
fastindy said:
if my research that i conducted a while ago is right, then basically samsung has implemented a flash counter which increments each time you flash a custom, non-stock rom...it might also be applied to non-stock kernels/firmwares as well (im not too sure)...so to prevent the flash counter from ever incrementing, ill need to put the phone in download mode using the jig and continue from there...
Click to expand...
Click to collapse
You have some bad information...but I have some good news for you.
The flash counter only counts the number of times you've flashed a custom kernel in download mode via Odin. Using CWM to flash anything can't touch the flash counter. Same goes for Mobile Odin. I've been rooted and flashing for months, I don't have a jig, and my counter is still at zero.
EDIT: Ninja'd by a pirate!
fastindy said:
unfortunately, i joined the android bandwagon only when i got my samsung galaxy s2, which was a little late in the game, so i have no clue on all the start up issues that people experienced with Gingerbread release...
for now ill need to stick with stock/At&T firmware however ill make the switch to custom firmwares when i stop being lazy and create a USB jig for myself...
Click to expand...
Click to collapse
Any GB issues only surfaced if you updated to 2.3.6. 2.3.4 for a "stock" firmware was pretty awesome. I'm on the latest ICS leak from ATT (LD4) and aside from the emmc bug (I'm using a safe kernel so I don't have it) IMHO its more complete then CM9 was. I stopped using CM9 at the end of May and don't miss it at all now.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
alright well i learnt something new today...and now that i have the freedom to flash like a mad man without worrying about flash counter (via CWM), i will surely checkout some of the leaked versions of ICS that you guys are using, and see which one works best for me...thanks for all the new info
fastindy said:
alright well i learnt something new today...and now that i have the freedom to flash like a mad man without worrying about flash counter (via CWM), i will surely checkout some of the leaked versions of ICS that you guys are using, and see which one works best for me...thanks for all the new info
Click to expand...
Click to collapse
I reccomend roms that use i9100 bases as they are usually better, roms like phonebricker, and shostock2 are good, my favorite touchwiz based rom though is serendipity 9. But thats my experiences so try them for yourself (i use aokp as my daily though.)
Sent from my SGH-I777 using Tapatalk 2
Remove Triangle and Reset Counter
http://shetalksandroid.blogspot.com/2012/03/how-to-reset-sgs2-flash-counter-and.html
Please read the above link.
I just did it last night and really works!
Time to hit the Thanks button
EDIT:
This not only makes the meter go back to zero, but also removes the yellow triangle, without the JIG.
Thanks to Chainfire, its free! Just read the above link. (And please "Search" more
Hey..
I have just rooted my Samsung Galaxy S2 to update to JellyBean 4.1.2. But apart from liberty i m very much depressed that i am not been able to play games on rooted phone. i want to ask that if i unroot my phone through Superuser app would it also wash my jellybean. or if there is some way that i could play HD games on the same phone without even thinking of unrooting?
Rooting doesn't affect anything. It could be a problem with phone or with the WAY you rooted.
What root method did you use?
Also i don't think you fully understand the meaning of rooting. Or maybe i didn't understand the statement "I have just rooted my Samsung Galaxy S2 to update to JellyBean 4.1.2" What do you mean, and how did you update to Jelly Bean?
I used odin for this Purpose and rooted using jellybean 4.1.2 official ROM available on internet..
That's what i meant. i hope you understand..
So u are proposing that i can use the *Unroot* option in superuser app and it wouldn't affect JB..??
nabeel559 said:
I used odin for this Purpose and rooted using jellybean 4.1.2 official ROM available on internet..
That's what i meant. i hope you understand..
So u proposing that i can used the *Unroot* option in superuser app and it wouldn't affect JB..??
Click to expand...
Click to collapse
Hmm, I think you are mixing the words flashing and rooting in a really confusing way, or are you saying that you flashed jb 4.1.2 with a custom kernel and then rooted? Whatever the case rooting doesn't effect games, I only know one game which does a root check (I forgot the name of the game but it was made by square enix) and that was later removed by the developer's themselves, just tell us what your actual problem is and what games are causing what kind of problems?
Sent from my GT-P6200 using xda app-developers app
Yeah. i did flashed my phone when it was gingerbread 2.3.3. then i just used odin, followed the instructions to have JB version.
Specifically In case of NFS Most wanted, First logo screen(EA GAMES) appears. and with in 5 secs it just closes down and says "Unfortunately, NFS Most wanted has Stopped* i have also tried modern combat 4. but No Luck
OK...so...
1) you're not rooted
2) even if you were....rooting will not cause problems like this, nor will upgrading Android.
3) all you have done, is update Android to the latest version.
I've a feeling that there's more you haven't mentioned......
What have you done/installed/tweaked/modded since you upgraded? The smallest thing may be important.
Also....after the upgrade, but before installing anything, did you wipe cache/data reset? Not doing so *can* cause all sorts of issues....even if it didn't result in a boot loop (which is the usual symptom).....
Sent from my Chameleon powered S2 via XDA Developers App
keithross39 said:
OK...so...
1) you're not rooted
2) even if you were....rooting will not cause problems like this, nor will upgrading Android.
3) all you have done, is update Android to the latest version.
I've a feeling that there's more you haven't mentioned......
What have you done/installed/tweaked/modded since you upgraded? The smallest thing may be important.
Also....after the upgrade, but before installing anything, did you wipe cache/data reset? Not doing so *can* cause all sorts of issues....even if it didn't result in a boot loop (which is the usual symptom).....
Sent from my Chameleon powered S2 via XDA Developers App
Click to expand...
Click to collapse
No Sir. i think i didn't wiped cache aur data rest.. From where do i suppose to do that cause i am certainly new to this rooting sort of things. i dont know much. infact, i have just got help from my friend to do JB on my phone.
With respect...you say you are new to all of this....
I *could* give you a step by step guide to tell you how to do it....but in all honesty, it's better for you that you search, read and learn.....
XDA has a very useful search function.....
Use it to search for 'entering recovery' and 'wiping in recovery'.....
You need to learn and understand the steps instead of just doing them. That way you're less likely to bork your phone........
Sent from my Chameleon powered S2 via XDA Developers App
After updating to I9205XXUCML1_I9205OXXCML2_I9205XXUCML1_HOME I can't root anymore unless I install a custom rom, are there any pre-rooted stock roms?
If not which PDA from SamMobile is rootable?
reserved
reserved
spirituselectus said:
Never mind I just flashed twrp recovery, wiped everything in advanced wipe, reflashed the portuguese firmware via odin and it booted into the stock rom, weird thing is this time the default language wasn't french, it was polish. Oh well.
Click to expand...
Click to collapse
Hi there... it's a kind of epic story of life... unfortunately it sometimes happens ... By the way - have you heard about prog named Odin?
Anyway I am glad so you have your Mega up and working. It is the best phone ever .
Sent from my GT-I9205 using xda app-developers app
spirituselectus said:
bro, u know how sometimes u read an instructions article in a hurry and sometimes dont finish it thinking your common sense will seal the deal. thats what happened with me, better to be near sure about results then taking chances and regreting it. im positive I wouldve saved alot of time if I stopped for a while and read carefully. atleast I can say I learnt a few things here and there, still dont know whether I can root this rom. frankly cant be bothered to try anymore, developers on the mega section could make their rom introductions abit easier to the common user with simple background knowlege, especially regarding going back if not happy. I was planning to install linux with my root, but after all thats happened these past months i cant be bothered to even adjust settings according to my taste, e.g. my keyboard is still vibrating when i type. the notification bar on top is to far on this tabl...smart phone and settings gets lost in the stock cloud wallpaper. im just gonna roll with it, maybe samsung does know whats best for their phones, if they'd only let us move the app drawer to the centre of the dock dammit.
Sent from my GT-I9205 using xda app-developers app
Click to expand...
Click to collapse
Yes, I know how it happens...
There is thread about rooting ROM with KNOX from ValenteL http://forum.xda-developers.com/showthread.php?t=2574953
As I am afraid your counter of unofficial installation is tipped to 1 and you are already void your warranty, maybe try a shoot for it. Anyway if you want to stay with new ROM it will be sensible to made factory reset of your phone and installing on it newest ROM once more, but this time through Odin from your PC. Lets read about how to use Odin (there are several threads on forum) and download from Sammobile newest, not branded ROM. In this manner you can make fresh start. Then if you dare you can try to root it using method from link above.
Me I am very careful about upgrades and do not decided to flash in blind newest ROMs when they arrive... and all for better, because new ROMs comes with new bootloader (which prevent to downgrade to previous versions and when you try you can brick your phone) and with dreadful KNOX... Now i will wait at least for KitKat to upgrade.
Knox
I really hate it when Samsung went for Knox.. It made life harder for our devs