Related
I got my S2 only a few days ago from Vodafone UK and quickly flashed to the latest Checkrom to get rid of the stock bloatware. After suffering severe battery drain to do with wifi i have flashed back to the stock carrier firmware (BUKJ3).
I did this first by using CWM to clear davlik cache and a full wipe and then after enabling USB debugging mode i rebooted into downloaded mode. Upon entering download mode the phone began to make an audible clicking noise which i dont remember it ever doing when i first rooted the phone.
I went ahead and flash the firmware and all seems well but i wanted to see if the clicking noise might indicate a fault with the phone?
One other thing, if i wanted to return the phone back to Vodafone would i need to reset the binary counter thingy even though i'm back on stock firmware? The yellow triangle never bothered me so i never removed it or reset the count after installing Checkrom.
Thanks
[Edit] I've just loaded Kies and it says 'your device does not support software updating via kies'. This is somewhat concerning since i thought i had returned my phone out-of-the-box stock by flashing this firmware -> GT-I9100_VOD_I9100BUKJ3_I9100VODKI2_I9100BUKI1.tar.md5. When i very first got the phone Kies would state that its up to date. After runing *#1234# my settings are PDA: I9100BUKJ3 , PHONE: I9100BUKI1 and CSC: I9100VODKI2.
Re: the clicking thing, no idea. Haven't encountered/heard of that before.
Re: resetting the counter. Put it this way, if you don't, and you return the phone for warranty service you're pretty much paying for the repair out of your own pocket.
I.E the counter is proof you've been messing with the phone, which voids the warranty. What firmware you've currently got on the phone is irrelevant.
Might want to invest a few dollars in a jig just in case you do decide to send it in for a warranty repair.
Goooober said:
I got my S2 only a few days ago from Vodafone UK and quickly flashed to the latest Checkrom to get rid of the stock bloatware. After suffering severe battery drain to do with wifi i have flashed back to the stock carrier firmware (BUKJ3).
I did this first by using CWM to clear davlik cache and a full wipe and then after enabling USB debugging mode i rebooted into downloaded mode. Upon entering download mode the phone began to make an audible clicking noise which i dont remember it ever doing when i first rooted the phone.
I went ahead and flash the firmware and all seems well but i wanted to see if the clicking noise might indicate a fault with the phone?
One other thing, if i wanted to return the phone back to Vodafone would i need to reset the binary counter thingy even though i'm back on stock firmware? The yellow triangle never bothered me so i never removed it or reset the count after installing Checkrom.
Thanks
Click to expand...
Click to collapse
MistahBungle said:
Re: the clicking thing, no idea. Haven't encountered/heard of that before.
Re: resetting the counter. Put it this way, if you don't, and you return the phone for warranty service you're pretty much paying for the repair out of your own pocket.
I.E the counter is proof you've been messing with the phone, which voids the warranty. What firmware you've currently got on the phone is irrelevant.
Might want to invest a few dollars in a jig just in case you do decide to send it in for a warranty repair.
Click to expand...
Click to collapse
Yeah i do have a Jig on the way. I've just encountered another problem as well. My internet speeds over wifi are appalling after flashing back to the stock firmware. 2200kbps down and 355kbps. The phone out of the box and on checkrom both performed as normal (about 10x what it is now). This stock vodafone firmware i downloaded here is clearly not what i had out-of the-box.
In that case, you might want to find out what firmware you had on the phone initially & flash that. As I'm not in the UK, I wouldn't have the foggiest.
At the end of the day, if you're returning it for a warranty repair, I wouldn't be surprised if they reflash whatever stock firmware they're currently using as part of the repair process (I've read many accounts of this happening).
Obviously once you start messing around with the phone, you potentially open a whole can (or many cans) of worms so far as how the phone performs goes. You could easily have just rooted the phone in the first instance to remove the bloatware, flashing a custom rom was not necessary in order to achieve this.
Goooober said:
Yeah i do have a Jig on the way. I've just encountered another problem as well. My internet speeds over wifi are appalling after flashing back to the stock firmware. 2200kbps down and 355kbps. The phone out of the box and on checkrom both performed as normal (about 10x what it is now). This stock vodafone firmware i downloaded here is clearly not what i had out-of the-box.
Click to expand...
Click to collapse
MistahBungle said:
In that case, you might want to find out what firmware you had on the phone initially & flash that. As I'm not in the UK, I wouldn't have the foggiest.
At the end of the day, if you're returning it for a warranty repair, I wouldn't be surprised if they reflash whatever stock firmware they're currently using as part of the repair process (I've read many accounts of this happening).
Obviously once you start messing around with the phone, you potentially open a whole can (or many cans) of worms so far as how the phone performs goes. You could easily have just rooted the phone in the first instance to remove the bloatware, flashing a custom rom was not necessary in order to achieve this.
Click to expand...
Click to collapse
I thought i had flash whatever firmware was on it originally. I downloaded the BUKJ3 UK Vodafone carrier firmware from the stock rom thread since my phone came with BUKJ3. The wifi performance is shocking tho.
hi guys!
i recently flashed uk stock lfb rom over my orange stock rom, i rooted my s3 using chainfire cf-root 6.4 and i used triangle away to reset the counter.
everything went smooth, counter shows 0, but in settings/about device/status/ device status is now MODIFIED and not NORMAL as it used to be.
even if the counter is reset to 0, isn't this an obious proof for servicing companies that phone has been modified and loosin warranty? is any way to go back to normal? i searched the forum and i didn't find a solution.
thank you!
flash stock rom and your phone will show that normal status again. samsung will never know what you did to the poor phone. double check that you don't have supersu or superuser app or else something bad might happen
stfudude said:
flash stock rom and your phone will show that normal status again. samsung will never know what you did to the poor phone. double check that you don't have supersu or superuser app or else something bad might happen
Click to expand...
Click to collapse
i already tried that, but a lot of apps didn't start corect, phone became very unstable and unusable. i even couldn't check if the status went back to normal. could it be because the original version seems to be an earlier release compared to lfb release?
i flashed stock rom, ALE8 to be exact, a few days ago, after having a few problems with wanam 1.9. the status changed to normal after flashing. i use desktop odin to flash. after flashing wanam 2.0 the status changed to modified. tried triangle away, but the status still doesn't change to normal even though flash counter has been succesfully reset.
The full steps are: (in that order)
- Triangle Away
- Flash Stock ROM
- Flash correct CSC / Modem (optional, not required)
- Factory-reset the phone
Reset the flashcounter, update rom and after boot do a facory reset.
flash stock rom, wipe everything, doesn't mean that the phone back to normal. for example, i always set my line to wcdma only. after flash any rom, reset everything, that setting still wcdma only. the only way to have absolutely format, is change csc code. it's truly format back to stock. but, be warning, you will lose everything, backup 1st.
so the trick is factory reset? good to know! i will not try it btw, because i need a working phone for this 2 months. OP, is your question answered now?
I don't know yet
I have to try that first, but i can't do IT right now. I hope that after flashing my original orange rom the phone will be stabile enough to perform a factory reset.
Thank you guys for your suggestion.
noris08 said:
hi guys!
i recently flashed uk stock lfb rom over my orange stock rom, i rooted my s3 using chainfire cf-root 6.4 and i used triangle away to reset the counter.
everything went smooth, counter shows 0, but in settings/about device/status/ device status is now MODIFIED and not NORMAL as it used to be.
even if the counter is reset to 0, isn't this an obious proof for servicing companies that phone has been modified and loosin warranty? is any way to go back to normal? i searched the forum and i didn't find a solution.
thank you!
Click to expand...
Click to collapse
Hey dude. I'd just stick with it
even if you should have to send it in, they'll pretty much only look at the counter (If possible) and if that is not possible, then they'll JTAG it; meaning that EVERY tiny piece of information on that phone is gonna be wiped... Just make sure you don't send it in, just because of a small SIM failure. (Because that's caused by bad radios/basebands). Only send it in, if it's proper bricked, and they'll not no a thing (I've done this loads of times, they haven't noticed a thing to date )
yep, factory reset did the trick.
as i said, after flashing original orange rom over lfb rom the phone became unstable.
i booted into mini cwm that came original with the phone and there is an option to do a factory reset, et voila, no more modified status.
thank you guys!
No problem hit thanks button )
I have a brand new s3 from orange which has not been rooted or anything and the device status shows as modified. i have used the Samsung GS3 Int ToolKit and odin to flash an unsecure boot image so i could back up my phone which i still havent yet as i need to root and install busy box. i have not rooted the phone or changed the rom so why does it say device status modified. I did a factory reset but it still shows as modified.
I will be flashing the rom once i know how to backup the orange rom and data. I want to remove the modified status incase i want to return the phone to orange so they can give me an unbranded phone in the first place.
daflex86 said:
I have a brand new s3 from orange which has not been rooted or anything and the device status shows as modified. i have used the Samsung GS3 Int ToolKit and odin to flash an unsecure boot image so i could back up my phone which i still havent yet as i need to root and install busy box. i have not rooted the phone or changed the rom so why does it say device status modified. I did a factory reset but it still shows as modified.
I will be flashing the rom once i know how to backup the orange rom and data. I want to remove the modified status incase i want to return the phone to orange so they can give me an unbranded phone in the first place.
Click to expand...
Click to collapse
If you flashed an insecure kernel, you did modify the state of the device. Are you saying that it showed as modified out of the box?
same problem
I have never rooted my device, never intended to either. However my device status appears as modified. While I personally feel there arent many glitches in my phone (s3), I'm worried i wont be able to upgrade to jellybean when the update comes out.
Any help?
Which firmware/ROM are you using? Are you rooted?
I'm asking this cause if you bought it second-hand the previous owner could have modified it.
Sent from my Nexus 7 using Tapatalk
would having this status affect OTA updates?
Yep, it generally means the phone is running a custom rom/recovery and is rooted. OTA updates only work on non rooted stock recovery roms... However this doesn't mean you can't update through ODIN...
ultramag69 said:
Yep, it generally means the phone is running a custom rom/recovery and is rooted. OTA updates only work on non rooted stock recovery roms... However this doesn't mean you can't update through ODIN...
Click to expand...
Click to collapse
I don't think so. As long as you're on an official ROM it doesn't matter if you're rooted or not.
donalgodon said:
If you flashed an insecure kernel, you did modify the state of the device. Are you saying that it showed as modified out of the box?
Click to expand...
Click to collapse
Thanks, I realised that later on and was just about to re-edit the post. Im sure it didn't say modified when out of the box. Orange won't replace the mobile as they say all their phones are branded and the replacement would be branded anyway. Im gonna flash with unbranded software as i dont want orange bloatware. Just need to know how to back up this useless orange rom and then i can flash!
---------- Post added at 08:12 PM ---------- Previous post was at 07:59 PM ----------
Lunchbox115 said:
I don't think so. As long as you're on an official ROM it doesn't matter if you're rooted or not.
Click to expand...
Click to collapse
Yep as long as i've read you can download as long as your on official ROM. You might lose your root but you can just re-root again.
I'm currently rooted on stock 2.3.6. I'm trying to sell the phone today and the guy wants me to update to ICS. I just have one problem... Whenever I flash back to stock everything, Kies keeps giving me the error that I'm not eligible. I assume it's because I tripped the flash counter going back to stock. How can I avoid this? Can I use Kies with a custom recovery installed to flash the flash counter wipe, and then it'll just remove the recovery?
Edit - Trying with a custom recovery and it said I was eligible.
I am no expert on here but lurk these forums, but I think I'll throw my 2 cents in here. I received a warranty replacement from ATT in the mail after the manager of the ATT repair center told his lackey to allow my warranty exchange. You see, I had mine rooted (on 2.3.6) and loaded with a custom rom (ICS 4.0.4) and the lackey could see the counter incremented and all. He gave me the script of not being able to warranty it due to the rooting but the manager could see that I knew what I was doing and that the issue (no sim error) was a hardware issue so he said he'd take the hit if it came back due to the flash counter. He had the lackey try to reflash it with official rom with their samsung tools just incase the sim issue could be fixed with a flash, but no cigar. All that did was leave me with an official ICS rom that was unrooted with a counter showing 1. A couple days later the replacement came in and I transferred all my info to the new phone.
Now just to be on the safe side, even though the manager of the corporate repair center ok'd it, I decided to return the defective Gnote back to stock unrooted condition with it's counter reset.
What I did was,
Flash the GB stock unrooted rom 2.3.6 using odin.
Then flashed CWM using odin.
Copied the ATT stock recovery zip and the flash counter reset zip to the internal memory. Reason being is that you will flash the counter reset with the custom CWM and then flash the stock recovery after to replace the CWM with the stock ATT recovery.
Afterwards I checked in download mode and the flash count was :no which means I'm in the clear and the underneath it said Samsung Official.
I haven't used kies, but I do know that using odin was painless. I'd suggest browse these forums for a while until you feel comfortable enough and then take care of the problem without Kies. Could be done in less than an hour after hitting a few links in the stickies of these forums.
DinoSoup said:
I'm currently rooted on stock 2.3.6. I'm trying to sell the phone today and the guy wants me to update to ICS. I just have one problem... Whenever I flash back to stock everything, Kies keeps giving me the error that I'm not eligible. I assume it's because I tripped the flash counter going back to stock. How can I avoid this? Can I use Kies with a custom recovery installed to flash the flash counter wipe, and then it'll just remove the recovery?
Click to expand...
Click to collapse
Its got nothing to do with the flash counter. Unless your phone is completely stock, Kies rejects it.
rangercaptain said:
Its got nothing to do with the flash counter. Unless your phone is completely stock, Kies rejects it.
Click to expand...
Click to collapse
It actually was the flash counter. I wiped the counter and then tried, rooted and with a custom recovery, and it worked. Stock with a 1 on the flash counter and nothing.
Hi all,
I have had my S3 since July '12 and in true Android style rooted it and started flashing ROM's left right and centre. Eventually I stuck on Omega, mainly because I got bored of continually flashing a ROM, installing my fave apps, restoring backups from Titanium, setting up my settings etc...
Christmas eve came and, having some time off work, I decided to start flashing some new ROM's...
Jump forward a few hours.... Tried CM10... liked it but wanted more of the Google/stock bits and pieces back so went to flash another ROM off XDA.
All of a sudden the phone goes off. Phone hard bricked. Wouldn't turn on, wouldn't charge... I shat myself.
I got a little brave and RMA'd to Samsung hoping that if its hard bricked they'll just swap the system board or whatever, and thankfully, a few weeks later and I have my phone back. Yay me!
First thing phone does when I connect to my home Wifi, OTA. Only a small update, and wasn't really paying attention as I was still setting up the phone.
Left it stock for a week and then decided I needed root. Rooted phone using the Samsung S3 all in on toolkit v7 from the XDA boards. All well.
So now I'm a little gun shy of flashing my phone, especially after reading a note in Christiano Matos' ROM thread for crDroid v11 about flashing various Bootloaders; and admittedly not properly understanding it as it seems a little Google-translate jumbled up.
Also http://crave.cnet.co.uk/mobiles/samsung-galaxy-s3-sudden-death-security-flaw-fixed-in-uk-50010094/ makes me a little nervous...
Is the 'hard brick' a hardware fault (and as such I wouldn't link it to any software or ROM I installed and something I'd hope my replacement phone wouldn't suffer twice) or a software issue that can be exploited (in which case which update is it that fixes it and do all decent ROM's include this update)?
And finally, what ROM do people suggest? I want to get rid of the Samsung bloat and have a nice speedy UI with plenty of battery life.
(ignore the FoxHound banner in my sig!!)
Post from crDroid thread:
Quote:
- SAMSUNG APPARENTLY SUDDEN DEATH PREVENT: AS YOU GUYS KNOW SOME S3 I9300 IS SUFFERING WITH A WEIRD BUG THAT SIMPLY ENDS IN SUDDEN DEATH .
USE WITH LAST STOCK, PERSEUS, BOEFFLA OR YANK55.LU KERNELS AND PHILZ RECOVERY.
THIS LATEST FIRMWARE XXELLA COMES WITH NEW BOOTLOADER APPARENTLY THAT FIX THIS BUG. THE BAD NEWS IS: THIS BOOTLOADER CAN ONLY BE INSTALLED THROUGH ODIN PACKAGE. BUT WE DON'T WANT THIS, RIGHT?
FLASHING THIS BOOTLOADER BECOME UNABLE TO GET BACK TO THE OLD ONE. BINARY COUNTER CAN'T BE RESETED (STAY ALWAYS WITH 1 COUNT).
HERE IS A LINK WITH BOOTLOADER FILES. ONLY FLASH IT WITH ODIN PC AND PUT IN PDA FIELD.
If you're scared then just don't do it.
I highly doubt your brick had anything to do with flashing ROMs, just Samsung ****ing up on the hardware front again.
You don't really need to flash any new bootloaders etc. because if it breaks like it did before,you know what's going to happen - Samsung will fix your phone, and that's it.
If you don't like the stock Samsung firmware, try CM10.1. Read about bugs etc. before you start crying about things not working though, because it still isn't, and most probably never will be 100% stable.
bortak said:
If you're scared then just don't do it.
I highly doubt your brick had anything to do with flashing ROMs, just Samsung ****ing up on the hardware front again.
Click to expand...
Click to collapse
Exactly what I thought, until I hardbricked my cousins S2 on the weekend. Never ever thought it could happen. Seems like Samsung is releasing firmware/kernels on the S2 that can hardbrick a phone whenever any sort of wipe is performed in cwm recovery.
Sticky from the S2 forum:
http://forum.xda-developers.com/showthread.php?p=36947154
Anyway, this is the last thing I wanted to hear. Fingers crossed it was just a one off and not actually related to flashing.
Sent from my GT-I9300 using xda premium
well, basically if you don't touch BOOTLOADER staff , it should be highly unlikely to brick devices , except in the case they released problematic firmware as once i bricked my Nexus S with problematic bootloader released by Google... damn it ...
only thing concerns me about S3 is SDS , but i have installed patched recovery and kernel i think i can breath a little easier now ... but still don't like taking ticking bomb around my pocket... it really sucks...
Seems like Samsung is releasing firmware/kernels on the S2 that can hardbrick a phone whenever any sort of wipe is performed in cwm recovery.
Click to expand...
Click to collapse
You are referring to the brickbug in _leaked_ firmware builds. All official releases by Samsung are not affected.
Also the bug is not only triggered by CWM but by every major operation when a kernel with the MMC_CAP_ERASE flag set.
but still don't like taking ticking bomb around my pocket... it really sucks...
Click to expand...
Click to collapse
Afaik the problem was related to a ****-up in the SSD's wear leveling - so if it is fixed it is fixed =)
Btw, just because it is _now_ impossible to reset the flash counter does not mean it will never be. Samsung does not use eFuse's so there is always a hidden switch that can be reset =)
For CM10 - I never expected the full functionality that Samsung's own firmware had, or at least not the polish and extra apps that are bundled but to be honest, I can live without SVoice, kies etc.
I have read the thread on SDS and have checked my phone with eMMC check (and also advised three others who I work with to check their S3's too), and I have also updated recovery (TWRP) to latest version so I should have some protection... shouldnt I?
I think I will stick with stock for now, see what comes in the future, and what Samsung release through OTA etc. (BTW phone was bought outright by me so is UK Unlocked, no branding).
Dear @OP.
Feel free to answer all your questions by yourself. I'd recommend you to stop being lazy, move your ass and read a few things, starting from here as it triggered your attention.
Furthermore, personally I would recommend you to read carefully this to avoid your threads being locked.
In relation to above, I'd like to recommend you visiting this section of XDA Froums, if you want to use something customized. If not, feel free to use this top secret trick to find Stock ROMS here on XDA....
Wow! Who knew! Consider me put in my place... [edit]
Now I will go and beat myself with a wet towel tied in a knot at the end.
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
cooza said:
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
Click to expand...
Click to collapse
Thanks for that Cooza; one thing there I didn't know; you can flash a 3rd party kernel to a stock firmware.
cooza said:
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
Click to expand...
Click to collapse
Kind sir,you can reset the counter on the new bootloader as long as you are running stock kernel and stock recovery! last night i flashed trough modile odin the stock kernel and the stock recovery over philz recovery ,and after i used triangle away without any problems!
bottom line short,with the new bootloader you cannot reset the counter while you are runing custom kernel and/or custom recovery!
Hey guys, I'm curious if I'm the only one who never had the yellow triangle on his device?
I've flashed so many Rom, I've used Odin, CWM and mobile Odin but my flash counter never increased.
Please share your experience, thanks!
Tapatalked from my Galaxy SII
Yep, I have. It only happens to me when I flash a kernel on a stock rom. I use Triangle Away to get rid of it. You can find it on the google play store. There may be other cases where this happens, but this has been the only time for me, personally.
No what karpfenhai is wondering is if anyone else's flash counter is at 0 still after using a custom rom, if I interpret correctly.. Nope. My counter is at one after flashing Siyah via Odin. Subsequent flashes haven't done anything to it.
Karpfenhai, how did you root in the first place and what firmware were you on when you did? My (limited) understanding of PhilZ kernel is that if it's flashed from stock recovery on JB, root & CWM are installed without increasing the flash counter. Then as we all know, CWM / mobile odin can be used with no more increases to the flash counter. Is that similar to what you did? Or, did you root using a method which would ordinarily increase the flash counter and yours seems to be "broken"?
Sent from a galaxy far, far away
Hopper8 said:
No what karpfenhai is wondering is if anyone else's flash counter is at 0 still after using a custom rom, if I interpret correctly.. Nope. My counter is at one after flashing Siyah via Odin. Subsequent flashes haven't done anything to it.
Karpfenhai, how did you root in the first place and what firmware were you on when you did? My (limited) understanding of PhilZ kernel is that if it's flashed from stock recovery on JB, root & CWM are installed without increasing the flash counter. Then as we all know, CWM / mobile odin can be used with no more increases to the flash counter. Is that similar to what you did? Or, did you root using a method which would ordinarily increase the flash counter and yours seems to be "broken"?
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Thx for answering mate, back in May 2011 i was a rookie in terms of custom Rom... if I remember right I used a superoneclick method to root my pre-installed 2.3.4 Gb Rom (think it was xxki4). After going straight to villain Rom (2.3.6) with siyah and speedmod kernel, ics came out and I tried again several Rom until I sticked with ....litening Rom.... and speedmod kernel until jb appeared. After some weeks on lsj and it's successors I finally moved to cm10.1, tried dorimax and now cm stock kernel, I had around 100 flashes on my device and it's still at zero
I never upgraded my bootloader my phone never saw kies, maybe that's the trick.
And yes I maintenance many other phones including several s2 and all other have got the counter increased.
Regards.
Tapatalked from my Galaxy SII
Hahaha that's awesome! I doubt that would work now, as s2 has newer (& smarter) bootloader. Not that I mind my counter being off 0.
I've only been flashing for about 10 months now, so I'm not as good at all this as you. In saying that, I'd be well in the 50-75 zone for flashes I think, a lot of it is just to get a clean flash, or trying one of the various dorimanx releases.
On the other s2's that you have, is the counter at just 1, from the initial flash? As in, unaffected by other CWM flashes? Or is it quite high, meaning that subsequent flashes are still affecting the counter?
Sent from a galaxy far, far away
Hopper8 said:
Hahaha that's awesome! I doubt that would work now, as s2 has newer (& smarter) bootloader. Not that I mind my counter being off 0.
I've only been flashing for about 10 months now, so I'm not as good at all this as you. In saying that, I'd be well in the 50-75 zone for flashes I think, a lot of it is just to get a clean flash, or trying one of the various dorimanx releases.
On the other s2's that you have, is the counter at just 1, from the initial flash? As in, unaffected by other CWM flashes? Or is it quite high, meaning that subsequent flashes are still affecting the counter?
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Nope they are usually at 1 or zero by triangle away, I don't own them I only make their users happy..
Tapatalked from my Galaxy SII
Karpfenhai said:
Nope they are usually at 1 or zero by triangle away, I don't own them I only make their users happy..
Tapatalked from my Galaxy SII
Click to expand...
Click to collapse
Funny you should say that.. Literally right now I'm flashing a friend's S2 with NeatROM