[GUIDE] How to Prepare Your Phone to Return to the Store or for Warranty Replacement

creepyncrawly

Senior Member
Sep 3, 2010
2,770
3,276
0
So I clear the flash counter, then flash entropy512's uckk6 and remove root manually with root explorer and then follow the walkthrough from creepycrawly to root again ? Its seems odd to flash ROM's in mobile Odin but I guess it works.
No. You said "I want to go back to stock and do a warranty claim." For that, you would need to remove root, or flash pure stock. (And this is the warranty guide.)

If you want to wind up with ShoStock then it doesn't matter which stock plus root package you flash. But keep the root and continue on with the guide. (Not this giude, but the first one in the sig below.)
 
Last edited:
  • Like
Reactions: hednik

hednik

Senior Member
May 31, 2012
1,529
707
0
Fort Worth
No. You said "I want to go back to stock and do a warranty claim." For that, you would need to remove root, or flash pure stock. (And this is the warranty guide.)

If you want to wind up with ShoStock then it doesn't matter which stock plus root package you flash. But keep the root and continue on with the guide. (Not this giude, but the first one in the sig below.)
I'm sorry for me flip flopping on what I want to do. It hard to say if a warranty is the route I want to do because I'm not sure what caused the "voltage to high" error. It could be caused from so many things and I'm unsure if going back to stock will fix it or if its an actual hardware issue. This walkthrough seemed like a great place to start to help me get his phone back to factory specs if its what I really need to do. I've flashed your one click before to root his phone and it worked perfectly. Just worried to flash anything with his error he gets and the phone being finicky as I don't want to brick it. Also wondering if the flash counter is all they would check ? Basically if it says zero flashes and I followed your walkthrough is there Anything else they check to see.

Sent from my SGH-I897 using xda app-developers app
 

aintwaven

Senior Member
Jul 13, 2009
210
10
0
Tecumseh, OK
I am trying to fix my nieces bricked stock phone. I could not get it into recovery and had to use jig to get into download. Using Oden3 v1.85 I get to NAND write start!! and it hangs. Any ideas?
 

creepyncrawly

Senior Member
Sep 3, 2010
2,770
3,276
0
I am trying to fix my nieces bricked stock phone. I could not get it into recovery and had to use jig to get into download. Using Oden3 v1.85 I get to NAND write start!! and it hangs. Any ideas?
It's hard to say what might be going on without more information. What package did you use with Odin? Also, describe the problem with the phone. What caused the problem in the first place, and what steps have been taken so far? Provide as much information as possible.
 
  • Like
Reactions: 4-2ndtwin

aintwaven

Senior Member
Jul 13, 2009
210
10
0
Tecumseh, OK
It's hard to say what might be going on without more information. What package did you use with Odin? Also, describe the problem with the phone. What caused the problem in the first place, and what steps have been taken so far? Provide as much information as possible.
Okay here is what I know. She said before it went down things got real slow, when she gave it to me I could not get it into recovery mode and I had to use my jig to get it into dl mode.I first tried Kernel + cache + rooted UCKK6 system package: http://dev-host.org/8LA and it would start and then hang no mater how long I let it go. I then tried the UCKH7-CL503881 with Oden3 v1.85 I get to NAND write start!! and it hangs. I also tried to add the 512 PIT file with no change. Is it possible the internal memory is bad?
 

BNAS

Senior Member
May 24, 2006
133
10
0
Boot loop after step 4

I followed all your steps and the package completed successfully. It went into a boot loop so I followed step 4 and went into recovery and did a factory data wipe. It went into a boot loop again so I am trying to enter recovery again and when I do I get the following message:

Deleting Cryption Meta data.

After that message it enters a boot loop again. Even while hold all thre buttons. Any ideas?

Thanks,
 

sebbysludge

Member
Jun 6, 2012
5
1
0
I had to return mine when i originally got it it had a factory issue and i had already rooted it. The premade Jig i bought worked perfect the come in handy
 

BNAS

Senior Member
May 24, 2006
133
10
0
I had to return mine when i originally got it it had a factory issue and i had already rooted it. The premade Jig i bought worked perfect the come in handy
Where did you buy your Jig? I have had my SGS2 for over a year and it just did this after I have been running custom ROM Unnamed 1.3.2 since last December.
 

russg62

New member
Jun 17, 2011
2
0
0
Do I need to install a driver to get Odin to talk to the phone?

Prepare Your Phone to Return to the Store or for Warranty Replacement by following these steps:

1. Read the flash counter to make sure your flash count is at "NO". If it reads "YES (x counts)" then you must buy or build a Jig to reset it to "NO"...
...or use chainfire's "Triangle Away" program (which only work on ICS, Android 4.x)
2. Flash the UCKH7-CL503881 stock kernel and system package using Odin or Heimdall.
3. Deal with any special problems.
4. Do a wipe data/factory reset, and remove any personal or sensitive information that remains on the phone.


Thanks for this note. I am trying to reset this device to give to someone else.

I followed the instructions exactly as above. My custom binary download showed NO in step 1) so I went ahead and followed 2a.) Flash the UCKH7-CL503881 stock kernel. After downloading and starting Odin, I plugged in the phone holding down the vol up and down buttons and then pressed vol up to go into download mode. However, the small edit box in the upper left corner of Odin never turne yellow, and didn't display anything. It seems like some communications driver is required for Odin to talk on the USB cable. This is a new laptop. Abandoning the download and restarting the phone worked fine.

What should I do to proceed?
 

bykviking

Member
Dec 7, 2012
5
1
0
San Diego
Step 4 - 3e Recovery still not available

I am running an I777 that was stock with Official AT&T ICS (even flashed AT an official device repair center). The phone would occasionally hang so I would just reboot, finally yday it would not boot past the "SAMSUNG Galaxy S2" open screen. Hard reset wouldn't work. All I could do is enter Odin DL mode by holding "-vol & pwr."

Finally gave up and after much reading, tried to flash some Siyah Kernels as phone is out of warranty. Odin3 said they uploaded, yellow turned green and confirmed successful 1, still no luck booting or accessing 3e Recovery. Flashed back to Samsung official "I777UCLE5_I777ATTLE5_I777UCLE5_HOME.tar.md5". Odin mode always reported Custom Binary DL as NO. After more reading I found this thread and I followed 2A, with confirmed success. Still no reboot and still no 3e recovery option. I can flash through to the second intro screen but it simply hangs there.

I have tried every variation of plugged into USB with and without battery, key combos, the works. Nothing gets me past the "SAMSUNG Galaxy S2" intro screen unless I boot to Odin DL mode. Help!?! -Thanks bykviki'noob"g
 

creepyncrawly

Senior Member
Sep 3, 2010
2,770
3,276
0
I am running an I777 that was stock with Official AT&T ICS (even flashed AT an official device repair center). The phone would occasionally hang so I would just reboot, finally yday it would not boot past the "SAMSUNG Galaxy S2" open screen. Hard reset wouldn't work. All I could do is enter Odin DL mode by holding "-vol & pwr."

Finally gave up and after much reading, tried to flash some Siyah Kernels as phone is out of warranty. Odin3 said they uploaded, yellow turned green and confirmed successful 1, still no luck booting or accessing 3e Recovery. Flashed back to Samsung official "I777UCLE5_I777ATTLE5_I777UCLE5_HOME.tar.md5". Odin mode always reported Custom Binary DL as NO. After more reading I found this thread and I followed 2A, with confirmed success. Still no reboot and still no 3e recovery option. I can flash through to the second intro screen but it simply hangs there.

I have tried every variation of plugged into USB with and without battery, key combos, the works. Nothing gets me past the "SAMSUNG Galaxy S2" intro screen unless I boot to Odin DL mode. Help!?! -Thanks bykviki'noob"g
First thought is memory damage. However, I am puzzled by your quote:
All I could do is enter Odin DL mode by holding "-vol & pwr."
The button sequence for entering download mode is to hold vol- and vol+ but not power while plugging in the usb cable. If I remember correctly, vol- and power is the button sequence for the international version.

The correct button sequence on the I777 for entering recovery is to hold down all three buttons, vol- vol+ and power, continuously until it boots into recovery. If it doesn't boot into recovery after the first splash screen, then continue holding down the three buttons and let the screen go black and the splash screen appear a second time. If this gets you into recovery, perform a wipe data/factory reset and see if it boots up ok.

In any case, let us know your results.
 
  • Like
Reactions: bykviking

bykviking

Member
Dec 7, 2012
5
1
0
San Diego
First thought is memory damage. However, I am puzzled by your quote: The button sequence for entering download mode is to hold vol- and vol+ but not power while plugging in the usb cable. If I remember correctly, vol- and power is the button sequence for the international version.

The correct button sequence on the I777 for entering recovery is to hold down all three buttons, vol- vol+ and power, continuously until it boots into recovery. If it doesn't boot into recovery after the first splash screen, then continue holding down the three buttons and let the screen go black and the splash screen appear a second time. If this gets you into recovery, perform a wipe data/factory reset and see if it boots up ok.

In any case, let us know your results.
The confusing quote is exactly right, I was able to enter download mode by just holding VOL- and long pressing and releasing PWR. Maybe I was also pressing VOL+ unknowingly, but I did it numerous times. I bought the phone October 2011 in an Escondido AT&T store. Either way, I mostly have been entering download mode using the VOL+&VOL- plus USB since I learned that trick, more consistent results.

Regarding entering recovery, I'm trying again now... and this time it didn't even go past the first splash screen. Trying once more... went to second splash but still no dice, hung. You said memory issue, am I S.O.L. or is that addressable?

Thanks for the quick reply btw.
 

creepyncrawly

Senior Member
Sep 3, 2010
2,770
3,276
0
The confusing quote is exactly right, I was able to enter download mode by just holding VOL- and long pressing and releasing PWR. Maybe I was also pressing VOL+ unknowingly, but I did it numerous times. I bought the phone October 2011 in an Escondido AT&T store. Either way, I mostly have been entering download mode using the VOL+&VOL- plus USB since I learned that trick, more consistent results.

Regarding entering recovery, I'm trying again now... and this time it didn't even go past the first splash screen. Trying once more... went to second splash but still no dice, hung. You said memory issue, am I S.O.L. or is that addressable?

Thanks for the quick reply btw.
If it is damaged memory, then there is probably no way to recover. Let's hope that is not the issue. What made me think of that is that the phone was stock ICS with the stock ICS kernel, which many here think is still possibly susceptible to the eMMC superbrick bug. You can do some reading here if your're not familiar with it.

I am aware that holding vol- and power will boot to download mode when the battery is removed, and the phone is powered by the usb cable. But until now I haven't seen that reported to work while the battery is in.

What puzzles me is that, if I read your post correctly, all the odin flashes finished and reported success. If there were memory issues, I'm not certain that the odin flashes would complete successfully. The problem could be a corrupt bootloader or param file. I certainly would not give up on trying to recover the phone yet. You might try flashing secondary bootloader or param.lfs or both. You can find them in the download repository. (See my signature.)

As a final resort, you could send it to Mobile Tech Videos for a jtag repair. I think that costs $50 or $60 or something. If it actually has eMMC memory damage, then they can tell you that also. If it was me, I'd call them first before sending the phone there.
 
  • Like
Reactions: bykviking

bykviking

Member
Dec 7, 2012
5
1
0
San Diego
If it is damaged memory, then there is probably no way to recover. Let's hope that is not the issue. What made me think of that is that the phone was stock ICS with the stock ICS kernel, which many here think is still possibly susceptible to the eMMC superbrick bug. You can do some reading here if your're not familiar with it.

I am aware that holding vol- and power will boot to download mode when the battery is removed, and the phone is powered by the usb cable. But until now I haven't seen that reported to work while the battery is in.

What puzzles me is that, if I read your post correctly, all the odin flashes finished and reported success. If there were memory issues, I'm not certain that the odin flashes would complete successfully. The problem could be a corrupt bootloader or param file. I certainly would not give up on trying to recover the phone yet. You might try flashing secondary bootloader or param.lfs or both. You can find them in the download repository. (See my signature.)

As a final resort, you could send it to Mobile Tech Videos for a jtag repair. I think that costs $50 or $60 or something. If it actually has eMMC memory damage, then they can tell you that also. If it was me, I'd call them first before sending the phone there.
Awesome thanks, I'll check these out, but first I'm going to go visit the Service Center tomorrow and hopefully see the same guy I saw both times before. He was suspicious that it could be hardware causing my freezes but reassured me both times that it was likely app related. (Even though it froze once immediately after he re-flashed it as I was shaking his hand walking out the door!!) So maybe he'll take pity on me as I did reach out twice before my warranty was up. I'm just hoping flashing the original profile doesn't cause him to question what I've been up to, but based on the experience so far I suspect it might not have even taken despite the positive result. I'll also just tell him that once it was down I only saw your post and simply tried to flash back to factory settings. (BTW don't know if it matters but I realized I left it out of my original details, Kies does tell me that I am running 4.0.3 according to my S/N.)

I'll report back what goes down because if he sends me packing I'll try the bootloader /param.lfs route. Even more jargon deciphering... yay.
 

bykviking

Member
Dec 7, 2012
5
1
0
San Diego
Awesome thanks, I'll check these out, but first I'm going to go visit the Service Center tomorrow and hopefully see the same guy I saw both times before. He was suspicious that it could be hardware causing my freezes but reassured me both times that it was likely app related. (Even though it froze once immediately after he re-flashed it as I was shaking his hand walking out the door!!) So maybe he'll take pity on me as I did reach out twice before my warranty was up. I'm just hoping flashing the original profile doesn't cause him to question what I've been up to, but based on the experience so far I suspect it might not have even taken despite the positive result. I'll also just tell him that once it was down I only saw your post and simply tried to flash back to factory settings. (BTW don't know if it matters but I realized I left it out of my original details, Kies does tell me that I am running 4.0.3 according to my S/N.)

I'll report back what goes down because if he sends me packing I'll try the bootloader /param.lfs route. Even more jargon deciphering... yay.
Update - Service Center manager lady was nice and sympathetic but was also surprised that phone wouldn't reboot even though her flash reported success. Told me that because I was out of warranty but did have insurance that her hands were tied and I would just need to replace it via my own means. I pleaded for her to pull some strings, no dice, her suggestion go get an S3, slightly better than the HTC One X. I can replace the S2 via insurance for $200, but don't have an upgrade available yet so an S3 would be $450. Retail store jacknapes offered me an early upgrade if I bought a bluetooth Jambox and some other BS accessories for an extra $100 or something. Wouldn't budge otherwise.

Just flashed the bootloader and param.lfs files from your repository, both reported success but still no reboot or 3e recovery... guess I might need to call the folks you suggested unless there are any more suggestions. I also thought it was odd that the bootloader file was suggested to be flashed via PDA and not the bootloader option. This isn't the forum to tell me why, but if you think I should use the sbl.tar with the bootloader option and the param.lfs in the PDA I can try that too.

Any other ideas?
 

bykviking

Member
Dec 7, 2012
5
1
0
San Diego
Update - Service Center manager lady was nice and sympathetic but was also surprised that phone wouldn't reboot even though her flash reported success. Told me that because I was out of warranty but did have insurance that her hands were tied and I would just need to replace it via my own means. I pleaded for her to pull some strings, no dice, her suggestion go get an S3, slightly better than the HTC One X. I can replace the S2 via insurance for $200, but don't have an upgrade available yet so an S3 would be $450. Retail store jacknapes offered me an early upgrade if I bought a bluetooth Jambox and some other BS accessories for an extra $100 or something. Wouldn't budge otherwise.

Just flashed the bootloader and param.lfs files from your repository, both reported success but still no reboot or 3e recovery... guess I might need to call the folks you suggested unless there are any more suggestions. I also thought it was odd that the bootloader file was suggested to be flashed via PDA and not the bootloader option. This isn't the forum to tell me why, but if you think I should use the sbl.tar with the bootloader option and the param.lfs in the PDA I can try that too.

Any other ideas?
Final Update: Talked w/ Josh at Mobile Tech Videos. He said it was likely the eMMC, but that I might be able to repartition it as they don't yet offer eMMC replacement service yet. Suggested I look for the Galaxy Note N700 8.25gig PIT file. I searched around for a bit, but couldn't track it down. When I finally called the insurance company they actually upgraded me to the S3 for the same $200 it should have cost in the store... but it required I send my S2 back, so I never got to try and flash a PIT file. Oh well. The S3 is quite nice, just BIG. Thanks for all the help.
 
  • Like
Reactions: creepyncrawly
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone