Related
Hi @all...
I never thought rooting the phone (to get the CM9 nightlies) was such a complicated ordeal. I've no clue how much time I spent reading threads and evaluating all the possible ways to root.
I want to avoid increasing the flash counter by all means as I still have one year of warranty left... just to be on the safe side. Unfortunately I already have Android 2.3.6 (kernel 2.6.35.7-...LA4) on the phone, so from what I was able to figure out on my own, this means SuperOneClick or in general zergRushExploit based roots won't work anymore since the leak has been fixed. I could flash an insecure kernel but some people say that in general everything flashed through Odin will increase the flash counter and others say, that flashing an insecure kernel won't do anything to the counter (the whole idea would be kinda pointless if it didn't imho). Also there is the talk of a newer bootloader which will prevent resetting the counter. So much information to digest...
So, I would really like to ask for some friendly help. Is there any way to root the i9100 without increasing the flash counter that will still work with my current firmware and that I can use as a stepping stone to flash the CM9 nightlies? Or some alternative I am not seeing? (except for staying on stock)
Thanks a lot for helping me out in advance...
matthew.
Zergrush 4 (Doomlord) works on KL1 2.3.6 - I'm on it.
No "counter" issues
Also if you do increase your counter there is triangle away app which resets it to 0 without a jig.
Sent from my GT-I9100 using Tapatalk
Get a jig...
It costs only a dollars or so!!!
Sent from my GT-I9100 using XDA
What you can do is:
go to the cm9 user discussion and flash the recommended bootloader
download the clockwork mod recovery from the rom manager website, gapps and latest cm nightly then place it on your external SD card and not the internal
Using stock recovery navigate to the clockwork recovery zip and apply
It will bring up clockwork mod recovery
Do a factory reset...then you can wipe system/data/cache partition from mounts and storage but its optional (I did this because I just wanted a super clean install)
Install the nightly and gapps
you have succesfuly installed CM9
Enjoy
Sent from my GT-I9100 using XDA
koolshubh said:
Get a jig...
It costs only a dollars or so!!!
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
A jig won't work on 2.3.6 onwards..
And just remember triangle away app only works on ics...
Sent from my GT-I9100 using XDA
First of all, thanks @all for your help.
@LenAsh: If KL1 is your kernel build version, you are actually on a older kernel. If it is your firmware version, you are newer though (KI4 here). The reason why I am pointing this out is that I have read in both developer threads, that with LA4 kernels and/or Android >= 2.3.6, the exploits used won't work. But again, there were also people reporting otherwise. Could you maybe clearify what exact versions you are on, please?
@st3chn0: Hm, won't flashing the bootloader also increase the dreaded flash counter because it is done through Odin?
@Li4m79: I know. What I haven't figured out so far (and maybe you can help me out on this one): Is the requirement an "ICS bootloader" or really ICS? So if I flash CM9 from my GB stock and keep the bootloader as is, will I still be able to use the Triangle Away app?
So long,
matthias
2.3.6 - in my sig
LenAsh said:
2.3.6 - in my sig
Click to expand...
Click to collapse
Ok, that I got the first time. But it is just part of the story. Firmware and kernel version would be nice to know. Thanks.
BinaryKhaos said:
First of all, thanks @all for your help.
@st3chn0: Hm, won't flashing the bootloader also increase the dreaded flash counter because it is done through Odin?
Click to expand...
Click to collapse
Flashing just the bootloader wont do anything to the bootloader since its the samsung official bootloader... only things such as custom kernels etc (not verified by samsung themselves) will increase the counter
BinaryKhaos said:
First of all, thanks @all for your help.
@Li4m79: I know. What I haven't figured out so far (and maybe you can help me out on this one): Is the requirement an "ICS bootloader" or really ICS? So if I flash CM9 from my GB stock and keep the bootloader as is, will I still be able to use the Triangle Away app?
So long,
matthias
Click to expand...
Click to collapse
Not sure mate... but if you are flashing cm9 why keep the boot loader? ... just flash cm9 and then use triangle away...
Sent from my GT-I9100
Hello, I hope it's okay to resurrect this for a related question.
I've got my SGSII (I9100) only a couple of days ago, but coming from another android (which is nowadays lowend: I5800) which was always rooted I couldn't stay un-rooted for long. I've rooted using su/busybox injection via temporary CWM, as that obviously doesn't increase flash count (and consequently doesn't cause the yellow triangle).
I'm a bit worried about possibly needing warranty at some point, when the phone is in a state where I can't use it anymore to use "triangle away" (like display hardware issues, whatever) but Samsung can read the flash counter (possibly denying warranty).
So on to my actual question: I tried to find some clear information about what exactly causes the flash counter to increase and/or causes the yellow triangle. There isn't any sticky about it (in any of the sticky thread collections), so could someone clarify that for me?
My phone already shipped with ICS, I would conclude that I already have one of the new bootloaders that can no longer be reset using a jig (unless I flash an old one just for this, obviously).
I've read the only operation that can cause triangcle/counter increase is flashing a kernel (and rom with a kernel) in download mode (Odin) and that Samsungs own (unmodified) kernels are always OK to flash. Correct so far?
Concluding from that, it would mean that any nandroid restore operation would also be safe (for returning to some custom rom after testing/disliking a different one). Just like applying and update.zip (including things like flashing a rom this way). Still correct, I hope?
I really wish there was a sticky explaining this in detail, not just the existence of the counter/triangle and that it's possible to get rid of it, but not how to avoid getting it in the first place.
You can use for ics triangle away app and for GB u can use the one click root
Sent from my GT-I9100 using xda premium
For my case when i needed to flash GB i upgraded the os to ICS and rooted the ICS then i installed odin for mobile and then i flashed the GB again with ODIN from my mobile and i already reset my counters with triangle away in the 1st step try this one it will make u happy lol
Sent from my GT-I9100 using xda premium
moe.nassef said:
You can use for ics triangle away app and for GB u can use the one click root
Click to expand...
Click to collapse
Thanks for the reply, but I already know that. It will most likely be no problem to reset, but writing to the bootloader always entails a certain risk (of hard brick), however slim. This is also clearly stated in the "triangle away" description and forum thread.
Since the knowledge of what exactly increments the counter is surely out there, I'd just like to avoid doing those things in the first place.
Can you confirm/deny my statements above? Like about odin/update.zip and so on?
TheCreat said:
Thanks for the reply, but I already know that. It will most likely be no problem to reset, but writing to the bootloader always entails a certain risk (of hard brick), however slim. This is also clearly stated in the "triangle away" description and forum thread.
Since the knowledge of what exactly increments the counter is surely out there, I'd just like to avoid doing those things in the first place.
Can you confirm/deny my statements above? Like about odin/update.zip and so on?
Click to expand...
Click to collapse
Dear,
I know its risky but am using android since its early beging and never encounter a brick for my galaxy s2 i always use odin and triangle away and i dont have any issues believe me if you are having any issue in solving a little problem like this dont go deeper as u'll not feel the happiness of solving it due to your fears .. if i were you and am afraid i wont try .
Wish you the best
Sent from my GT-I9100 using xda premium
moe.nassef said:
Dear,
I know its risky but am using android since its early beging and never encounter a brick for my galaxy s2 i always use odin and triangle away and i dont have any issues believe me if you are having any issue in solving a little problem like this dont go deeper as u'll not feel the happiness of solving it due to your fears .. if i were you and am afraid i wont try .
Wish you the best
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
You are completely missing my point. I'd have to clear the counter after every flash that increased it, as I can't guarantee my phone would be in a state where I can do it the moment I do need the warranty. I know it's quite unlikely that something will go wrong and the operation results in a brick.
But why risk even that, if it can easily be avoided? I just need to know what exactly will and what will not increase the counter. Hence my skating for exactly that information.
Swyped on my Galaxy S2
you know i have rooted my phone more times than i can remember, versions of GB, ICS and now i use F1 Nexus ROM and i have always been able to get rid of the yellow triangle and reset the counter without any problems.
it is a jig solution, so i have 1 of those, then i have a an old bootloader file that is called 'oldbootloader' !!! thing is i dont remember where i got it from. anyway, every time after having rooted the phone, i just flash the oldbootloader in Odin PDA box, turn off the phone, plug in the jig and counter is reset, triangle gone. so far it has never failed.
Its very simple, you should have known this......
Flashing a non Samsung kernel / in secure kernel will do that.
Still there are ways you can flash in secure kernel without counter go up, but you have to be rooted and using mobile Odin.
TheCreat said:
You are completely missing my point. I'd have to clear the counter after every flash that increased it, as I can't guarantee my phone would be in a state where I can do it the moment I do need the warranty. I know it's quite unlikely that something will go wrong and the operation results in a brick.
But why risk even that, if it can easily be avoided? I just need to know what exactly will and what will not increase the counter. Hence my skating for exactly that information.
Swyped on my Galaxy S2
Click to expand...
Click to collapse
Any custom rom will increase your counter any root like CF root will increase ur counter if you are using a new non stock kernal it will increase the same .. the idea is if you reset the counter one time and then installed mobile odin app on your phone you want have any increase in the counter your whole life and also you will not lose the root and you can flash what ever you want you will not lose the warranty
And they will not able to find out that you one used a custom ROM i already sent my device to the warranty and they mentioned that i'm a noob and am treating the device in a decent way lol
Again ...
If you use your odin while flashing a stock os like xxlph it will increase nothing if you used a stock kernel nothing will happened but if you do so you will lose your root and if you lost your root and u wants to get it back it can increase except if you flashed the root kernel from the device with odin mobile or CWM .. forgot to tell also that if you installed any thing with CWM it will not affect your counter
Sent from my GT-I9100 using xda premium
Hi all.
My SGS2 needs to be sent in for repairs in the imminent future, and in preparation I unrooted my phone and flashed a Stock ICS build (my carrier is Optus, Australia). Before this I was running a few different GB roms. When I boot my phone I do not get the yellow triangle (I assume this is because I am running official Samsung firmware), but if I put the phone into download mode, it still shows the 8 custom flashes I did earlier.
My real question is will Chainfire's Triangle Away app remove the binary count even if the triangle isn't there?
And a better question would be, would having official firmware be enough to still claim warranty, or would I need to have both official firmware and a "0" custom flash count?
Thanks for any help!
I believe Samsung may throw a stink about the counter, even if you are on stock/official firmware. This counter would imply that you have voided your warranty previous to the current state of the phone and it's OS
To be safe I would use the Triangle away app
EDIT: Yes, the app does reset the flash counter. See https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&hl=en
Its always safe to clear the counter before returning it for service. yes the triangle away app will clear the counter with/without triangle.
download it for free from here
http://forum.xda-developers.com/showthread.php?t=1494114
Thanks guys!
I tried to run the app but it's telling me I need Superuser access...
Does this mean I need to root the phone, use the triangle away app, then UNroot the phone?
Sorry if this is obvious... Not overly confident of my ability to keep the phone unbricked haha.
sdardz said:
Thanks guys!
I tried to run the app but it's telling me I need Superuser access...
Does this mean I need to root the phone, use the triangle away app, then UNroot the phone?
Sorry if this is obvious... Not overly confident of my ability to keep the phone unbricked haha.
Click to expand...
Click to collapse
You are correct. Root the phone first, use the app, then unroot.
Thanks!
So it will still think it's Samsung official after that process?
You'll need a rooted ICS firmware already on your phone.
Check the Triangle Away forum to ensure its working with your firmware version.
Flash Triangle Away, this will remove Yellow Triangle and reset Custom Counter to 0.
Flash official unrooted firmware using Odin, this wont increase your Custom Counter as its official. Use a firmware thats specific to your region.
http://forum.xda-developers.com/showthread.php?t=1075278
Job done.
Also check my sigi for links
Thanks! This forum is full of amazing help.
So theoretically I could follow those steps then flash the stock ROM a thousand times and the flash counter would remain at 0?
If it makes you feel any better I went to Optus 3 weeks ago with a phone that wouldn't turn on with ICS for another region with root and they fixed it.
I think my USB jig cleared the counter to 0 though. I couldn't connect my phone to dl mode or anything
The app removes the triangle as well as the counter
Yeah I tried using the jig a while ago but I think I have the newer bootloader, so it didn't do anything, which was very disappointing.
I'd just hate to take it in then have them tell me to get bent because I rom'ed it.
Ok so let me know if theres a problem with my process.
I'm using ICS and the kernel is XWLP4.
There was no LP4 in Chainfires thread but I read that I could use the next closest one. So I should flash something like "CF-Root-SGS2_XW_O2U_LP3-v5.4-CWM5.zip" and then triangle away then use the Optus stock ICS?
UPDAT: I tried this method and it worked perfectly! Thanks so much to everyone who helped.
has worked like a charm for me everytime i put stock firmwares on my phone
Safest way is to flash a really old firmware and thus flashing the old bootloader. Now reset the counter with an usb jig. Done.
Sent from my Transformer TF101 using Tapatalk 2
d3l1 said:
Safest way is to flash a really old firmware and thus flashing the old bootloader. Now reset the counter with an usb jig. Done.
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Or just flash the old bootloader.
Hello everyone,
Hoping you can help me before my mrs cuts my nuts off. She asked me to update her GS2 (GT-I9100 on 02) and completly wipe the phone as she has had random apps appear etc etc.
I said that wouldnt be a problem as ive done alot on my GS3, though i am still pretty new to the Android scene (Previously iPhone).
So she was on Stock 4.0.4 XXLQ6 firmware.
I followed the guide to root from here as i was aware of the hardbrick bug in this firmware.
http://forum.xda-developers.com/showthread.php?t=1501719
After that it was time for the Wipe data etc and flash the new rom. I chose JELLYBAM as its Android 4.2 with a mix of other things. Sounded perfect.
I followed all the steps EXACTLY from the Devs page:
http://www.igio90.net/how-to-install/
All seemed to be going well at first, got to select afew options etc. Then it said it was Extracting the package...This is were the problems started.
It was stuck at 2% for AGES, then out of the blue the screen just went BLACK/BLANK......Hmmmm i thought!
I have since been trying to source info from everywere about how to turn the phone back on but having no luck at all. I have tried all the Soft/Hard boot methods, ive left it on charge (Yes it gets hot near the camera) and tried all boot methods whilst plugged into laptop with ODIN loaded up.
Nothing seems to be working.
Any help what so ever will be much appreciated. This device was never previously rooted. Im gutted a it was all going so well...I shoulda guessed something would go wrong.
Toon
Are you able to enter download mode? If you can make sure you have samsung drivers installed! Also JellyBam rom is not only for i9100 but other models too, are you sure you had the right rom? If you can't enter downlaod mode then try a USB jig?
Sent from my GT-I9100 using xda premium
UltimateAnas said:
Are you able to enter download mode? If you can make sure you have samsung drivers installed! Also JellyBam rom is not only for i9100 but other models too, are you sure you had the right rom? If you can't enter downlaod mode then try a USB jig?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thank you for your reply, Unfortunatly i cannot enter any mode what so ever. The phone is literally dead...yet getting VERY hot as its plugged in.
Was thinking about taking it in to O2 2mora and seeing what they can do. Damn.
If your still under warranty you should get a new motherboard.They won't be able to tell you've rooted it since it seems hard bricked.
Next time,get a custom kernel on it a.s.a.p and backup efs and make a nand backup before you start flashing roms.
Either that or stay away from 4.0.4 stock.
Sent from my GT-N7000 using xda premium
theunderling said:
If your still under warranty you should get a new motherboard.They won't be able to tell you've rooted it since it seems hard bricked.
Next time,get a custom kernel on it a.s.a.p and backup efs and make a nand backup before you start flashing roms.
Either that or stay away from 4.0.4 stock.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks for your reply, I did put a custom kernal (Sirayh?) on it prior.
The phone was a year old august just gone! Not sure Samsung be interested.
See if you can get your hands on a usb jig.If that fails try for a jtag.
Samsung warranty should be 24 months if you need it.
Sent from my GT-N7000 using xda premium
So you did a wipe on a Samsung 4.0.4 ROM with original kernel? Then you have indeed hardbricked your phone. You said you were aware of this bug, so I can't figure out why you would do a wipe?
Cenobite_ said:
So you did a wipe on a Samsung 4.0.4 ROM with original kernel? Then you have indeed hardbricked your phone. You said you were aware of this bug, so I can't figure out why you would do a wipe?
Click to expand...
Click to collapse
No i changed the kernal, but followed the guide posted by DEV to install the ROM. Guessing i made a mistake somewere down the line as the phone is bricked!!
JIG & JTAG....will these help solve my problem? Not really clued up on them though i have done a brief look around. JTAG services is not in my area.
NO, on hardbricked S2 JIG/JTAG won't be useful. You can check my thread http://forum.xda-developers.com/showthread.php?t=1756242 for more info.
PS : the direct signs of this kind of hardbrick is a totally dead phone & back side getting hot (near the camera lens)
googy_anas said:
NO, on hardbricked S2 JIG/JTAG won't be useful. You can check my thread http://forum.xda-developers.com/showthread.php?t=1756242 for more info.
PS : the direct signs of this kind of hardbrick is a totally dead phone & back side getting hot (near the camera lens)
Click to expand...
Click to collapse
Is there any way to fix this or do i owe my mrs a new phone?
Just took it to a repair store and he said its knackered, but to be honest he wasnt much help...more interested in the texts he was getting on his phone!.....Typically a GS2...Im still pondering if he was taking the micky :silly:
if your s2 is still under warranty, just take it to the reapir service and tell them that the phone was on charge all night and didn't wake up in the morning
they won't be able to know what you did to it since it's completely unaccessible. If you successfully convince them, they'll change the motherboard !
PS : That isn't my idea but from what I saw in the hardbrick warning thread, most of the concerned people did the same trick ...
googy_anas said:
if your s2 is still under warranty, just take it to the reapir service and tell them that the phone was on charge all night and didn't wake up in the morning
they won't be able to know what you did to it since it's completely unaccessible. If you successfully convince them, they'll change the motherboard !
PS : That isn't my idea but from what I saw in the hardbrick warning thread, most of the concerned people did the same trick ...
Click to expand...
Click to collapse
Yeah i think this is the route imgoing to have to take Just spoke with them regards my GS3 and they said itll be 2 weeks to repair and return. No phone for 2 weeks
I just got off the phone with Samsung and they are taking it in for repair. No local service centers so im awaiting a jiffy bag. Then 2 weeks to get the phone back!
Plese, need help, tried to downgrade firmware from 4.0.4 to 4.0.3 using Odin and now i'm getting an error: android.process.acore has stopped, and can't really do anything.
is there anything I could do now or is my phone bricked?
Thanks in advance!
Pooshkis said:
Plese, need help, tried to downgrade firmware from 4.0.4 to 4.0.3 using Odin and now i'm getting an error: android.process.acore has stopped, and can't really do anything.
is there anything I could do now or is my phone bricked?
Thanks in advance!
Click to expand...
Click to collapse
Please be more specific if you expect anybody to bother to help you.
When you say "can't really do anything" that doesnt tell us what you have tried and not tried!
1) Can you enter recovery mode?
2) Can you enter download mode?
3) Have you tried a USB Jig?
4) Have you removed battery for 30 mins?
5) What happens when you power on phone?
TheATHEiST said:
Please be more specific if you expect anybody to bother to help you.
When you say "can't really do anything" that doesnt tell us what you have tried and not tried!
1) Can you enter recovery mode?
2) Can you enter download mode?
3) Have you tried a USB Jig?
4) Have you removed battery for 30 mins?
5) What happens when you power on phone?
Click to expand...
Click to collapse
Sorry.
1) Yes
2) Yes
3) trying to find now what it is
4) For 30 mins no, for few minutes - yes
5) It starts and then i got some errors memo.process, process.acore and few others (can't remember now). I can get email, explore through home screens and menus, but can't call, receive calls, write messages, look up contacts or memos and stuff only going through screens. Maybe I could do a hard reset or wipe the phone, but then won't i brick my phone?
EDIT: As user Pilaf suggested (thanking him a lot!) I installed a new siyha kernel then did a full wipe / factory reset, seems everything is backing up from google account and phone is working..
So you're telling me that the official 4.0.4 has a hardbrick bug? Well that's great.
Should I just wait for the official 4.1 or can I flash for example the Siyah kernel and then start flashing other ROMs?
krnrdstrm said:
So you're telling me that the official 4.0.4 has a hardbrick bug? Well that's great.
Should I just wait for the official 4.1 or can I flash for example the Siyah kernel and then start flashing other ROMs?
Click to expand...
Click to collapse
Did you just get released from a 6 month stretch in jail/or been in a coma or something.
Sent from my GT-N7000 using xda premium
theunderling said:
Did you just get released from a 6 month stretch in jail/or been in a coma or something.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
:laugh:
Come on man, he's serious, so let's answer seriously
@krnrdstrm : to avoid the hardbrick, just flash a safe kernel (siyah, speedmod, dorimanx, philz ...) and enjoy ...
PS : didn't you have internet in jail ? :silly:
emmc bug
krnrdstrm said:
So you're telling me that the official 4.0.4 has a hardbrick bug? Well that's great.
Should I just wait for the official 4.1 or can I flash for example the Siyah kernel and then start flashing other ROMs?
Click to expand...
Click to collapse
Yea, have a look here http://forum.xda-developers.com/showthread.php?t=1756242
Siyah should be good,
Thanks: googy_anas
Hi,
I'm starting this thread because I can't seem to find anyone on here/the whole internet that seems to have had a similar problem.
I've got a UK unlocked Samsung Galaxy S3 GT I9300 in pebble blue 16GB. I bought it pretty much when it came out and was pretty happy with it. I updated it to JellyBean 4.1.1 via KIES last year when it came out (October/November?) and again was pretty happy with it.
Unfortunately despite being super OCD over my devices I managed to crack the screen. I sent it off to a Samsung repair centre and they changed the screen out for a hefty price. Phone came back and it hadn't been wiped or factory reset etc.
Then in December last year, I think it was the 12th, I got the Sudden Death. Phone was close to full charge in pocket for a few hours, took it out to make a call, wouldn't turn on. So I took it into the shop and they sent it away to be fixed. Got it back about 10 days later, working, factory reset to 4.1.1.
So when I got it back I noticed that 4.1.2 I9300XXELL4 firmware was out. I downloaded that and Odin and flashed the BTU firmware for unbranded UK devices. All seemed to go totally fine, phone has been working ok since.
Once small problem I have had since as long as I can remember is that in about phone, under status, the device status changes from normal to modified all the time. It turns out this has something to do with my 64GB EXFAT micro SD Card though. I found a few people with similar problems and thought nothing more of it.
Now however, I've noticed the 4.1.2 firmware with the exynos abuse fix and MAYBE sudden death fix was out, so I'm pretty interested in flashing it. Anyway I came to flash it and thought I'd check to make my custom binary count etc was as it should be. Turns out its not! I've got custom binary download YES (2 counts). Current Binary SAMSUNG OFFICIAL and System Status OFFICIAL. So I'm just a bit perplexed as to how this has happened? Can this happen without rooting and just flashing stock firmware? Or has it been modified/rooted when its been aware for repair to Samsung? I'm just a little bit perplexed/annoyed that I've made sure I've always kept it stock so that its protected by the warranty etc as I've been an early adopter and have to keep it for 2 years. Yet here I am without any of the benefits of rooting yet I've technically voided my warranty and haven't actually done anything?
So just hoping for some thoughts on what could have caused this? Also, is my only option to remove this to ironically root, triangle away, stock flash/factory reset/unroot? I would like to flash this new I9300XXELLA firmware if its got potential fixes but I don't want to add to that binary counter if flashing through Odin unrooted is going to do this. Obviously KIES won't do it anymore as it thinks it's modified.
Hope you guys can help, any thoughts are appreciated!
Many thanks in advance.
UPDATE - Have just flashed using Odin the I9300XXELLA firmware found here: http://forum.xda-developers.com/showthread.php?t=1646610 Phones working fine and it hasn't added to the custom binary download counter. Still shows: YES (2 Counts)
ELLA is really smoother than rest of firmwares. If i was you i would.
1. Root with Cf root
2. Run triangleaway
3. Go into download mode and check if its official binary stock sammy 0 counts.
4. Remove battery.
5. Download odin 1.85
6. Downlload xxella
7. Flash xxella as PDA.
8 .wipe data in stock recovery
Sent from my GT-I9300 using xda app-developers app
Adams756 said:
Hi,
I'm starting this thread because I can't seem to find anyone on here/the whole internet that seems to have had a similar problem.
Multiple posts on this if you looked on the forum .
jje
Click to expand...
Click to collapse
JJEgan said:
Adams756 said:
Hi,
I'm starting this thread because I can't seem to find anyone on here/the whole internet that seems to have had a similar problem.
Multiple posts on this if you looked on the forum .
jje
Click to expand...
Click to collapse
Could you link me to them? I really couldn't find them for the i9300 that's never been rooted.
Endrit9, thanks I think that's my best bet. I've flashed ELLA already, can I still root with CFroot?
Click to expand...
Click to collapse
Yes it should work then run triangleaway check download mode. Flash lla wipe data good luck but if u bought the phone and live in europe theres nothing to worry about.
Sent from my GT-I9300 using xda app-developers app
The 4.1.2 firmware you flashed via Odin is not officially signed by samsung( this is what i read I'm not 100% sure) This causes your counter to increase.
endrit9 said:
Yes it should work then run triangleaway check download mode. Flash lla wipe data good luck but if u bought the phone and live in europe theres nothing to worry about.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks I'll check out the root threads and give it a go. I live in UK, I bought the phone on a contract here but it's unbranded, I just got an O2 sim with it. Will this still be valid for warranty?
Thanks unitnerd. I didn't realise it might not be signed. Although thinking about it now I imagine it's probably because they're compiled by someone else after it comes out of KIES.
https://fsfe.org/freesoftware/legal/flashingdevices.en.html
Read ↑
Cf root is good by chainfire
Sent from my GT-I9300 using xda app-developers app
same problem its so confusing
First of all, I'm sorry if these things are already discussed somewhere. I never owned a Samsung phone, so this is my first time here. A friend of mine bricked her SGS3 and I have to help her to get it back working. She tried to install an update and the phone is now stuck on Samsung logo, but she can access the download mode.
Since I'm not an Samsung user, can you, please, give me some easy to follow instructions how to repair the phone? Is there an repair option in Kies/Odin or we have to flash the ROM manually? The phone is not rooted, and everything was stock.
And another question, before proceeding, is it possible to save some data from the phone or no?
Thank you a lot!
xplod2841 said:
First of all, I'm sorry if these things are already discussed somewhere. I never owned a Samsung phone, so this is my first time here. A friend of mine bricked her SGS3 and I have to help her to get it back working. She tried to install an update and the phone is now stuck on Samsung logo, but she can access the download mode.
Since I'm not an Samsung user, can you, please, give me some easy to follow instructions how to repair the phone? Is there an repair option in Kies/Odin or we have to flash the ROM manually? The phone is not rooted, and everything was stock.
And another question, before proceeding, is it possible to save some data from the phone or no?
Thank you a lot!
Click to expand...
Click to collapse
You can this guide (+more) in FAQ thread on top: http://forum.xda-developers.com/showthread.php?t=2323847
Odin shouldn't delete any files after recovery, but you'll have to perform a full wipe after doing a backup in order to avoid versions merging issues
Sent from my GT-I9300 using Tapatalk
amirTor said:
You can this guide (+more) in FAQ thread on top: http://forum.xda-developers.com/showthread.php?t=2323847
Odin shouldn't delete any files after recovery, but you'll have to perform a full wipe after doing a backup in order to avoid versions merging issues
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Is there an repair option rather than manual flashing? I don't know which firmware to use and which is her model exactly. It's a Galaxy S3 in Croatia.
xplod2841 said:
Is there an repair option rather than manual flashing? I don't know which firmware to use and which is her model exactly. It's a Galaxy S3 in Croatia.
Click to expand...
Click to collapse
If she has official stock ROM, than you can try using kies: Tools->recover firmware
Sent from my GT-I9300 using Tapatalk
amirTor said:
If she has official stock ROM, than you can try using kies: Tools->recover firmware
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot Yes, everything is stock on it. We will try and see. There is a high possibility that the phone is hardware damaged because she used to have problems with it and the repair center told her that there are signs of water and corrosion inside. Is there a possibility to permanently brick the device if something went wrong during repair? For exampe, if the USB connector fails or something?
xplod2841 said:
Thanks a lot Yes, everything is stock on it. We will try and see. There is a high possibility that the phone is hardware damaged because she used to have problems with it and the repair center told her that there are signs of water and corrosion inside. Is there a possibility to permanently brick the device if something went wrong during repair? For exampe, if the USB connector fails or something?
Click to expand...
Click to collapse
There is always a (minor) chance, but thats part of the fun
Sent from my GT-I9300 using Tapatalk
xplod2841 said:
...
Is there a possibility to permanently brick the device if something went wrong during repair? For exampe, if the USB connector fails or something?
Click to expand...
Click to collapse
There is always a possibility if the installation is interrupted anyway. But in almost all cases, things go fine so don't worry about it. Plus, flashing takes a couple of minutes.
Thanks! I managed to repair the phone with Kies recovery and now it's running Android 4.3 and all data is still there. The phone is pretty slow but it's full of apps and data so I adviced her to do a factory reset.