I recently attempted to root my SGS2 but I mistakenly installed firmware from the i9100 instead of the version I had, the i777 ( I was unaware there were two versions of the SGS2).
Odin failed, and all my subsequent efforts to flash proper firmware got as far as the LAST file (hidden.img) and then failed, too. I'm guessing it was a driver issue or a cable issue or something.
In desperation I started looking around the forums for any way to salvage this, and ended up going down a few fruitless tangents, but I did find out about the jig method of resetting the flash counter.
I booted into download mode and realized that the flash counter is actually zero - it says that I have an official binary loaded.
With that said, will Samsung / Sprint honor my warranty under these conditions? I have heard that people have gotten replacement phones even when they successfully flash custom firmware to their phones via the jig reset, so I'm feeling pretty confident they will.
Thanks for your help!
sirdangolot5 said:
I recently attempted to root my SGS2 but I mistakenly installed firmware from the i9100 instead of the version I had, the i777 ( I was unaware there were two versions of the SGS2).
Odin failed, and all my subsequent efforts to flash proper firmware got as far as the LAST file (hidden.img) and then failed, too. I'm guessing it was a driver issue or a cable issue or something.
In desperation I started looking around the forums for any way to salvage this, and ended up going down a few fruitless tangents, but I did find out about the jig method of resetting the flash counter.
I booted into download mode and realized that the flash counter is actually zero - it says that I have an official binary loaded.
With that said, will Samsung / Sprint honor my warranty under these conditions? I have heard that people have gotten replacement phones even when they successfully flash custom firmware to their phones via the jig reset, so I'm feeling pretty confident they will.
Thanks for your help!
Click to expand...
Click to collapse
Somethings up if you are mentioning sprint
Sent from my SGH-I777 using XDA App
Do you have an AT&T phone or a Sprint phone?
AT&T = SGH-I777
Sprint = SPH-D710
If you have the Epic 4G Touch on Sprint, you are in the wrong forum.
If you have the Epic 4G Touch, you have not only flashed the wrong firmware (I9100) but you have tried to fix it with the wrong firmware (I777).
Otherwise, why do you say:
sirdangolot5 said:
will Samsung / Sprint honor my warranty under these conditions?
Click to expand...
Click to collapse
Wow, I didn't even realize that was the case. I'm looking for the SPH-D710, which is the model of phone I definitely have. I'll make a thread there with the exact same text.
Related
I've managed to get a warranty replacement SGS4G from T-mobile, but I'd still like to figure out if I can recover any data and also verify exactly what I did wrong.
I found a Froyo .tar to flash via Heimdall to recover from a soft brick botched ROM/kernel upgrade. Either I selected the wrong file for the wrong thing in Heimdall or the tar was not compatible with the Vibrant but I think it messed up the bootloader.
The flash completed and then then screen would stay black no matter what I did.
No download mode regardless of buttons held, battery insert order, USB plug/unplug etc. No download mode even with USB resistor jig.
I found AdamOutler's UnbrickableMod stuff and tried the ModeDetect program which never saw the device which I guess confirms the hard-brick. So is the only option left for me to apply the Unbrickablemod (solder etc.)?
I've read people saying that it's almost impossible to brick these phones - is that true?
I assume I cannot recover any data from the internal SD card easily without unbricking.
Did I try to flash the wrong file, or would using an incompatible firmware do this? I'll try to post the exact file I used if I can find it.
[UPDATE]
I was trying to use a stock Froyo firmware from samfirmware that I found linked in a thread in the forums: I9000XXJVR_CL425308_REV03_user_low_ship
...and CFRoot kernel so I wouldn't have to root manually each time I had to reflash (CF-Root-XX_OXA_JVR-v4.1-CWM3RFS).
I thought this was compatible with the Vibrant, but are these only for the Galaxy S I9000?
HAHAHAHAHAHAHAHAHAHAHA, rotflmmfao.
I'm sorry, I needed a good laugh today
At the moment, the possibilities are too varied to narrow down. Could be the Froyo ROM you picked up was made for a different phone, or the program didn't install correctly, or the download was corrupt.
Our phones are virtually unbrickable, it's true. One of the few ways to hard brick them is to mess with the bootloader and fail.
djquick said:
HAHAHAHAHAHAHAHAHAHAHA, rotflmmfao.
I'm sorry, I needed a good laugh today
Click to expand...
Click to collapse
Riff box bro. Don't listen to DJ.
Sent directly to your brain from my cyanomodded not-so-Vibrant
Sadly, no. What you flashed was not compatible with the Vibrant. It's for the international version of the Galaxy S only, the i9000. Sounds like your phone is hard bricked thanks to the i9000 bootloader the flash must have added.
Thanks, stupid mistake on my part.
Noob question then: what must only be used for the specific phone it's made for vs. what can be used with other phones? Firmware, bootloader, kernel, modem, ROM, etc?
Hello, I recently bricked my samsung galaxy player, and guess what; it was rooted.
I have tried flashing a rom with the zImage, factoryfs.rfs, and efs.rfs in it, but it just boots into "system recovery <3e>". I think the problem might be I need the recovery.bin and boot.bin in the rom also, perhaps? I bricked it while trying to flash cwm, if that helps. If someone could tell me what I need to do to fix this, that would be great. But, I think I will have to send it into samsung, hence my question; Does samsung detect if devices are rooted, if so will they still fix it for a charge? How much is that charge? Also, how long on average does it take to fix, because I absolutely need it back by the 8th of Jan. Any answer is appreciated!
iJimaniac said:
Hello, I recently bricked my samsung galaxy player, and guess what; it was rooted.
I have tried flashing a rom with the zImage, factoryfs.rfs, and efs.rfs in it, but it just boots into "system recovery <3e>". I think the problem might be I need the recovery.bin and boot.bin in the rom also, perhaps? I bricked it while trying to flash cwm, if that helps. If someone could tell me what I need to do to fix this, that would be great. But, I think I will have to send it into samsung, hence my question; Does samsung detect if devices are rooted, if so will they still fix it for a charge? How much is that charge? Also, how long on average does it take to fix, because I absolutely need it back by the 8th of Jan. Any answer is appreciated!
Click to expand...
Click to collapse
Sorry to her that. From what i understood, they might be able to check if you have flashed your device before and this may affect your warranty. If so, then you may have to pay to get it fix. No one is certain how you will be charged as the they need to assess your device first. Hope for the best.
Well, it is being evaluated by their techs right now, I haven't heard anything yet. Does anyone know how long it usually takes them to repair it? I asked and one person said from 4 to 15 days, another said 3 to 4 days. I really need it back by the first of January, but I have a bad feeling with it being holiday season.
I had rooted phones with Tmobile and Virgin that I would send back under warranty. Nobody said anything to me about them...
Sent from my carrier pigeon using XDA App
Have you tried Odin-ing completely back to stock? Complete restore to stock has gotten me out of multiple hurdles where I'd've been bricked otherwise.
[edit] I was looking around for images to recommend to you, and found out you have already tried that. Sorry.
And yes, they'd probably service you, since they usually don't check at all. Just plug it into the computer and hit "flash." But it is dishonest.
I got an S2 via an upgrade with Vodafone UK and after deciding that the 3g performance was unacceptable i returned the phone. Having flashed Checkrom i bought a USB jig to reset the Custom Binary Counter (or whatever its called) and it worked a treat.
I got a new S2 the other day unbranded from Dialaphone.com but for some reason on this phone the Jig does not work. When i insert the jig the phone automatically boots into download mode like normal but the custom counter has not reset nor has the yellow triangle been removed. Since jigs are so cheap i bought a second one in case the first was faulty but this too does not work.
I've done some reading and i guess it has something to with the bootloader? Being the noob that i am i just wanted to get some clear advice on what it is i actually have to do to sort the problem.
Thanks
Hi! Chances are that your new phone has the new bootloader, which Samsung has disallowed the clearing of the custom flash counter.
Flash the old bootloader referenced in this post
http://forum.xda-developers.com/showpost.php?p=16781156&postcount=2
using Odin and you should be good to go.
Enjoy your SGSII!
i wish if people use the search more often
qwerty warrior said:
i wish if people use the search more often
Click to expand...
Click to collapse
I wish people would read OP's more often. I clearly stated that i had done some reading but wanted clarification on whether i need to flash a new bootloader or something.
Goooober said:
I wish people would read OP's more often. I clearly stated that i had done some reading but wanted clarification on whether i need to flash a new bootloader or something.
Click to expand...
Click to collapse
Np mate. Just flash the old bootloader given in Intratech thread via odin and you should be good
Ok, so I'm kinda already at stock. When I first got my SGS2, I rooted it but didn't put a custom ROM on. I was happy with this arrangement. It's been so long now though, that I've forgotten what I did and how to get it back to how it was when i bought it.
I have taken a screenshot of my info page: Here
I've spent all evening trying to get it back to untouched status - I've managed to unroot it and flash the stock kernel (even though the kernel info in the screenshot still mentions root for some reason). This doesn't seem to be enough though - it's still failing to install an OTA or kies update.
I'm going to be passing this phone on once the SGS3 comes out, so it's vital that it's back to square one and able to handle OTA updates.
I'd really appreciate some guidance here, I've been out of the tinkering game for far too long!
I don't see anything out of the ordinary on your screenshot. Have you ever changed CSC? Also, make sure you disable USB debugging if you ever enabled it.
Try * HERE * for the official O2 UK ROMs, with the latest being XWLP3. These will wipe and unroot your phone.
Intratech has put a link at the top on the procedure you need to follow.
Don't worry what the kernel says. When I first got mine it used to say root and dell and it wasn't a dell or rooted.
What's CSC? I've turned usb debugging off btw.
I've tried the OTAs and they download, but when it comes to installing it stops at 14% for a moment, moves up to 19% then reboots and gives me a failed update message.
I did wonder if i changed the recovery but I'm not sure how to tell - or how to change it back if I did. Would that cause problems?
I'll check out that o2 stuff, thanks. This phone was bought unlocked and unbranded though, will that matter?
Sent from my Galaxy S II using XDA App
More info in attached pic.
A quick google would lead me to say that no, I didn't change CSC. I hope!
Sent from my Galaxy S II using XDA App
r2001uk said:
Ok, so I'm kinda already at stock. When I first got my SGS2, I rooted it but didn't put a custom ROM on. I was happy with this arrangement. It's been so long now though, that I've forgotten what I did and how to get it back to how it was when i bought it.
I have taken a screenshot of my info page: Here
I've spent all evening trying to get it back to untouched status - I've managed to unroot it and flash the stock kernel (even though the kernel info in the screenshot still mentions root for some reason). This doesn't seem to be enough though - it's still failing to install an OTA or kies update.
I'm going to be passing this phone on once the SGS3 comes out, so it's vital that it's back to square one and able to handle OTA updates.
I'd really appreciate some guidance here, I've been out of the tinkering game for far too long!
Click to expand...
Click to collapse
you have to reset the counter as well search forum for custom binary counter and usb jig
other than that you may try to flash an old firmware 2.3.5 and then reset counter;
the stock rom how did you obtain it? is it the right one for your phone's region? did you have another one?
i would recommend you use fusdownloader; get the right stock rom for your phone and flash then; i have successfully unrooted my old sgs II before I gave it away to my mum as a birthday present
I've always stayed at stock rom because I was happy with it. I think the only rom-related change might have been to update to 2.3.3. Pretty sure it was the correct region. I didn't need to wipe anyway.
Would wiping and flashing everything from scratch solve my problem? Rom, kernel, recovery etc. I could do that, but I'd wait until I was about to give the phone away. If there's a single package to flash in Odin that sets everything back to factory standard, that'd be perfect.
Sent from my Galaxy S II using XDA App
Oh and about the jig? If that's the only option that doesn't involve a full wipe, I'll just hold off until I wipe. I don't fancy buying a jig for one task.
This'll teach me for tinkering and then waiting a year to revert!
Sent from my Galaxy S II using XDA App
To me its as simple as flashing O2 firmware via Odin after a full wipe of phone via CWM recovery .
GB O2 was posted KDD and KE2
and ICS LP3 O2 is available and should be on Checkfus .
kernel says root has nothing at all to do with ROOTING or even a rooted phone its a build signature only .
OTA update is known to be poor for some sticking during the download .
jje
Hello i would like to know if flashing a higher build then that is currently released trip knox? So my S6 edge came with "G25AUCU1AOCE" and BestBuy flashed "G925AUCU1AOE2" to it. Well long story short something tripped knox and samsung won't warranty my phone. (Linked here: http://forum.xda-developers.com/att-galaxy-s6/help/s6-edge-auto-custom-binary-t3153156) I got it back to "G25AUCU1AOCE" and went to best buy for an explanation and told him to re-flash my phone like they did last time and what would you know it gave me the same screen saying "unauthorized software had been detected". So was this caused by the higher build flash and samsung should fix my phone?
As long as it was official samsung firmware it should not have tripped knox (was Odin used?), I have read somewhere that people have had knox tripped when flashing samsung firmware, has to be a samsung problem.
Give samsung all the details you have about bestbuy and their flash methods and see how it goes.
Edit: After reading your linked page, I would get bestbuy to replace your phone as they caused the problem.
Yea im going to speak with their manager who did my initial flash and see how it goes.(i was speaking to another samsung rep today there and they said they just cant confirm that i havnt actually did anything aftet to have caused it... I know i didnt so idk how to argue that) No out side software was used for the flash before all this happened. They used theit S.M.A.R.T software to flash which apprantly can only flash latest builds samsung gives them.
Have a quick question reguarding the locked bootloader. Does the software have to be approved by att to get pass the bootloader or only by samsung? Maybe this is the issue here. Cause the message does say its unauthorized by AT&T.
Oh brother this is happening a lot, see pic and I'm on T-Mob, I caused his myself having been already been rooted, running TWRP and modified kernel and 5.1.1 but after trying what I though was an updated software I got had the same problem. Odin back to stock won't help either, I was lucky and had my phone stolen.