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
Related
This is purely just out of curiosity. Today I updated my SGS II to KE7 from KE4 because the battery life was AWFUL, and people have been saying it's a known issue with KE4. Kies never showed the update, I think because I got the Polish version from eXpansys, so I just did it myself. Now if I understand correctly, this counter goes up when you flash unofficial software like a custom rom or kernel, but it doesn't when you flash official software, like KE7? It's not a big deal if it goes up either way, I don't want to put my phone in download mode again to check it, only to have to flash it again to get it out.
Even if it does I can get one of those Jigs that people are talking about and reset the count if I ever have a problem with it (that I can't fix).
Correct non standard rom or kernel flashed counter goes up one .
Recovery jig clears the counter .
jje
Hey all,
I just received my i777 and I'm impressed. Coming from a sgs4g seems like a huge improvement, though the devices look physically the same LOL (with the i777 being a bit on the larger side).
Anyways, I've been flashing roms for about a year now with my sgs4g. The forums for the sgs4g had very detailed instructions when flashing, instructions like, what to do if coming from stock, but on this forum ppl just assume you have CWM installed.
What I want is a safe way to upgrade to, let's say, phone bricker. I've noticed that all roms are installed through CWM, and all OP say is "make sure CWM is installed", but there's no mention whatsoever on how to install CWM on this phone.
Maybe i'm complicating things a little bit. On my previous phone, Rom Manager downloaded from market was a NO NO because it'd brick it. So we had to flash a modded CWM via odin made specifically for our phones. Maybe for this phone installing rom manager is all that is needed? yes? OK, found the FAQ. no ROM manager.
Also, somehow this phone came rooted... I bought it new from a store but the unlocked version since I live outside USA.
So, if I'm not mistaken, I should just install rom manager, select my phone from the list, flash CWM recovery and flash away roms on the dev section. Am I correct? I don't want to brick my phone
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
I bought the full version of mobile ODIN. makes life a little simpler when flashing, in my opinion. It's worth the few bucks.
eep2378 said:
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
Click to expand...
Click to collapse
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
mikeflash said:
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
Click to expand...
Click to collapse
You don't need pro version, lite version will do just fine. Are you sure you're rooted? You have superuser app? Whether you're rooted or not look here(if you are rooted look at #3 : http://forum.xda-developers.com/showthread.php?t=1311081
Check out this thread, was my experience and I'm running PhoneBricker just fine!
However, backup your apps before flashing and factory reset, wipe cache and dalvik after (possibly before as well) and you should be fine! Will root then you can flash away.
Clay
Sent from my SGH-I777 using XDA
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Well, I flashed my phone last night. Used mobile odin for flashing a kernel (siyah) to get CWM, then flashed phone bricker via CWM like I used to do on my old phone. Everything went smooth.
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
creepyncrawly said:
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Click to expand...
Click to collapse
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
If that's the case, then I'm not too worried about flash count because I live outside US, and my AT&T phone wouldn't get warranty over here, but I'll definitely look into that, to check where my counter is at and to check if resetting it back to 0 is still possible.
I'll be checking up on the links you provided.
Thanks a lot.
mikeflash said:
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
Click to expand...
Click to collapse
It is a true ICS rom. Samsung didn't do a lot of cosmetic changes when they moved the S2 to ICS though...most changes are under the hood.
If you want something that looks and feels more like true ICS, you should consider trying either CM9 or AOKP. They are both based on Google's source code, nothing Touchwiz about them.
Or if you'd rather stick with what you have, you can always try different launchers. I'm running ICS, but I use Go Launcher and it runs beautifully.
mikeflash said:
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
Click to expand...
Click to collapse
That is mostly correct. You're right about the purpose of the flash counter, but it actually counts how many times you flash kernels, not roms. And even then, it only increments if you flash a kernel via Odin in download mode. Flashing a kernel in Mobile Odin or CWM doesn't touch the counter.
Incrementing the flash counter also places that possibly annoying yellow triangle on bootup on your phone. Since you're on ICS, you can just use triangle away app from play store (free version is on here somewhere) to get rid of it, though I'm not sure if that'll fix the whole secondary bootloaders thing (probably not). I think it'd be worth it to fix that just so you don't run into anymore problems later if you decide to change something, especially since after the fixes you can just nandroid back to your current setup, but it's not essential and completely up to you.
Sent from my Samsung SGH-I777 using XDA
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Phalanx, did you not read the Title?
It says be nice!
crawls back into hole
Sent from my SGH-I777 using XDA
Phalanx7621 said:
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thank you friend.
To sum up for OP
1. Strongly suggest NOT to use ROM Manager on any custom ROMs unless you are surely running CyanogenMod ROM.
2. Check the "About phone" to see if it is true ICS or ICS-theme GB.
Hi guys.
First up hello. Im a refuge from the Ace section, have a Galaxy SII due for delivery over the next couple of days so Im moving over. On the Ace I flitted between CM7, CM10 unofficial, Lewa and a few others.
Im generally used to rooting via stock recovery and then using CWM to do everthing else, not familiar at all with ODIN as I have never needed to use it. Standard UK SII, unlocked running Gingerbread.
Have read around this section and will continue to do so for a few days, but a few starting pointers would be nice.
Rooting/CWM/Kernels
Whats the easiest way for rooting the SII, preferably from stock recovery
Whats the easiest way for installing CWM?
What the best basic Kernel out there, or Kernel that will do an AIO Root/CWM/Kernel job?
Im reading a lot about this hardbrick lark with ICS, is this purely an issue with stock ICS roms, and its fine to go down the CM10 route?
I can use the search feature, but as Im sure you know thats not always the most productive route.. Although I shall use it in the meantime.
Cheers.
You can learn a lot just by reading peoples problems, and the answers given.
For rooting, you would normally just flash like a siyahv4+ kernel with Odin.
That gives you root, cwm and safe from brickbug.
Theres several other ways also like exynos or doing stuff via recovery.
theunderling said:
You can learn a lot just by reading peoples problems, and the answers given.
For rooting, you would normally just flash like a siyahv4+ kernel with Odin.
Click to expand...
Click to collapse
How have i avoided ODIN so long.. hmm, Siyah 4.
Do you know how cumbersome the search feature is here, finally found the download for v4.1.15 (and then realised it was in your signature), now im trying to find the instruction to install via ODIN,. If you happen to know offhand, the exact thread that would be appreciated.
Regarding roms, Im assuming CM10 is the standard, not familiar with any of the devs over on this side of the fence.
Ok, from what I can gather
Download Keis and make sure all drivers for the SII installed
Download Siyah-s2-v4.1.5
Disconnect your phone from your computer
Start ODIN
Click the PDA button, and select Siyah-s2-v4.1.5
Put phone in download mode
Connect the phone to computer
Make sure repartition is not checked
Click the start button
Wait for the phone to reboot
correct???
(sorry, i suffer anxiety, one of the side effects is double checking anything before doing it)
If your on ICS, you can download that siyah kernel, but make sure you get the .zip type.
Get the 1st and 3rd file in the ics rooting guide in my sig.
Stick them all on sd card.
Boot into recovery.
Flash the 1st file-which is temp cwm
Flash the 3rd file-which is su/busybox
Then flash the siyah file-which gives you permanent cwm and safe kernel.
Then reboot phone.
Then you are rooted, with cwm and safe kernel.
The easier way is obviously using odin.
Ps.hope you aint got the g model.
theunderling said:
If your on ICS, you can download that siyah kernel, but make sure you get the .zip type.
Ps.hope you aint got the g model.
Click to expand...
Click to collapse
No, its not the G..
It is on gingerbread currently though, not ICS.
GB ffs......lol.
Right you can update to ICS (pain)
or
Set up Odin and flash siyah s2 v2.6.14.tar file
or
Try exynos abuse (may not work on GB).
theunderling said:
GB ffs......lol.
Right you can update to ICS (pain)
or
Set up Odin and flash siyah s2 v2.6.14.tar file
or
Try exynos abuse (may not work on GB).
Click to expand...
Click to collapse
I shall go S2 v2 route then. assumedly i can then just flash cm10 iwthout any problems.
Yes GB model, but no, not GT-I9100G
Youll need to check what the install instructions are for the rom
Eg if you need to be on GB or ICS.
Ive never used it, Ive just read you need cwm though.
If possible I would first update to ICS via Kies or OTA then afterwards flash Siyah v4 via ODIN. Once you have done this you are ready to reboot into cwm and flash away. Remember to wipe data/factory reset in CWM though after flashing Siyah kernel and before flashing new rom.
TheATHEiST said:
If possible I would first update to ICS via Kies or OTA then afterwards flash Siyah v4 via ODIN. Once you have done this you are ready to reboot into cwm and flash away. Remember to wipe data/factory reset in CWM though after flashing Siyah kernel and before flashing new rom.
Click to expand...
Click to collapse
Ah, ive been reading on problems with ics and hardbrick, i guess that is prevented by flashing siyah post update.
Thanks guys, sorry for the noob questions, im not a noob, but rooting always makes me nervous (a hangover from the days when flashing the bios on the pc was a dangerous hit and miss affair), i just like to double check.
Once im rooted and got CWM im back in familiar territory.
Any other general tips on making the leap from Ace to SII appreciated.
Dont you just love it, when the phone arrives and its pre rooted with siyah and cwm
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!
Hi, I'm a middle aged person struggling to get to grips with unrooting.
Situation is this
I want to return my phone to an unrooted state for a warranty repair.
I have only rooted the phone, but not flashed any ROMs
Do I just need to re-Flash the correct official firmware, for Vodafone UK, using Odin and then it will be unrooted?
And then use a jig to reset the counter?
Are there any other steps I need to take.
Thanks for your help
Yes, if you flash a stock rom that will unroot the phone, you could also flash just a stock kernel if you can get hold of one - search the usual haunts (Samfirmware/etc).
A jig will probably work only if you've been running Gingerbread stock roms, if you've been running ICS or JB stock roms, use Triangle Away to reset the flash counter before you unroot/flash another stock rom or kernel, then flash away.
MistahBungle said:
Yes, if you flash a stock rom that will unroot the phone, you could also flash just a stock kernel if you can get hold of one - search the usual haunts (Samfirmware/etc).
A jig will probably work only if you've been running Gingerbread stock roms, if you've been running ICS or JB stock roms, use Triangle Away to reset the flash counter before you unroot/flash another stock rom or kernel, then flash away.
Click to expand...
Click to collapse
Hi MistahBungle, huge thank you for this, just the pointers I needed. Very good of you to help some random bod on the Internet. I found the firmware I need and have installed Triangle away.
I'm all set really, going to do a bit more refreshing of my memory before I go for it. One thing am slightly curious about but will Google it, is if you reset the counter with Triangle away, and then I re-flashed the kernel with a stock, won't neck count as another flash, or is the flash counter only active if the phone is being rooted? No need to answer as long as it works
Thanks again for your help, much appreciated
No probs No, flashing stock won't trip the counter again. Good luck/post here again if you have any dramas.
Mistahbungle is a helpful guy.......and hes old enough to be your father