I'm stuck in a boot loop and I have no idea why, and I've tried wiping cache, wiping data/factory reset, and re-flashing the CM7 rom. Nothing worked. What happned was, my phone died, so I plugged it in, and it went into "charging mode". The phone will boot, but the touchscreen doesnt work, and non of the radios turn on, so that it can just charge I guess? anyway, the phone got to about 20% battery so I decided to reboot it so I could actually use it while charging, but when I did, it started boot looping. I tried everything mentioned above and its still boot looping. Is there anything else I can try?
let phone go all the way dead
I run Cyanogemod with Da_G's kernel and I let the device die. I had a similar lock up when I finally plugged the charger back in. After it got to about 8 or 9% is all and was still unresponsive, couldn't unlock the screen I simply pulled the battery AND REMOVED THE CHARGE CORD and counted to twenty, slapped it back in and held the power button for the count of ten and let go. It booted back up fine and no issues since.
I assumed you tried a battery pull?
fukenbiker said:
I run Cyanogemod with Da_G's kernel and I let the device die. I had a similar lock up when I finally plugged the charger back in. After it got to about 8 or 9% is all and was still unresponsive, couldn't unlock the screen I simply pulled the battery AND REMOVED THE CHARGE CORD and counted to twenty, slapped it back in and held the power button for the count of ten and let go. It booted back up fine and no issues since.
I assumed you tried a battery pull?
Click to expand...
Click to collapse
Yea, that non responsive state is what led me to reboot. It only does that when the phone is dead and you plug it in. I assume it's because with cm7 there is no way to charge while the phone is off, at least that's the way it was with my infuse and captivate. So that's not the issue. It's that when I rebooted to get out of that state, it gets to the cm7 boot logo and then reboots. It's never done that before, and I do that a lot. I searched for this issue and I found someone with a nexus on cm7 that had a boot loop, and it was solved by some cwm zip that deleted the partitions, then once you do that, if you flash cm7, all will be well, but I don't know if that's applicable to this situation.
EDIT: I tried the battery pull, I left it out for 20 min and it's still boot looping
How are you getting into recovery? Seems once you get into recovery and wipe data/factory reset and flash version 4 and flash the kernel it would fix boot loop.
I use three button method to get to clockworkmod recovery.
If you Odin back to stock the method to get download mode for me was volume down only when plugging in.
I have a 400mb+ size file used by recovery of a working image of my favorite setup to flash back to. Everyone should take a few minutes and boot into recovery and make a backup to flash to once you get up and running good.
Sent from my SGH-I727 using CyanogenMod
I tried to duplicate. You are so correct I put the battery back in after making sure the phone was off and then plugged in the power.
For brief moment the big battery symbol appeared, but rather than continuing to stay with that and charge, it blinked away and promptly booted up into that frozen screen and no radio signal.
I had 50% charge when I tested this just now.
Upon pressing the power button I got the shutdown menu, but the screen was still unresponsive and wouldn't let me select reboot.
Ended up doing another battery pull (with no power cord of course)
I don't see how you did it, reboot while in that state escapes me.
Sent from my SGH-I727 using CyanogenMod
fukenbiker said:
I tried to duplicate. You are so correct I put the battery back in after making sure the phone was off and then plugged in the power.
For brief moment the big battery symbol appeared, but rather than continuing to stay with that and charge, it blinked away and promptly booted up into that frozen screen and no radio signal.
I had 50% charge when I tested this just now.
Upon pressing the power button I got the shutdown menu, but the screen was still unresponsive and wouldn't let me select reboot.
Ended up doing another battery pull (with no power cord of course)
I don't see how you did it, reboot while in that state escapes me.
Sent from my SGH-I727 using CyanogenMod
Click to expand...
Click to collapse
I hold the power button until the phone reboots.
fukenbiker said:
How are you getting into recovery? Seems once you get into recovery and wipe data/factory reset and flash version 4 and flash the kernel it would fix boot loop.
I use three button method to get to clockworkmod recovery.
If you Odin back to stock the method to get download mode for me was volume down only when plugging in.
I have a 400mb+ size file used by recovery of a working image of my favorite setup to flash back to. Everyone should take a few minutes and boot into recovery and make a backup to flash to once you get up and running good.
Sent from my SGH-I727 using CyanogenMod
Click to expand...
Click to collapse
I use the three button combo to get into recovery, and I did wipe data then flash both version 4 and the kernel, and it still loops. I am so confused as to how in the world this happened... anyway, I tried to go back to stock using odin twice and it just got stuck at system.img.ext4.
Oh dear you must take this to the Odin thread.... You belong there until you flash back to stock. Did you try only holding volume down when plugging in to download mode? Your skyrocket is powered down when you try?
Sent from my SGH-I727 using xda premium
I got into download mode fine the first time. then when it got stuck, I changed to a usb port on the back of my pc, but it still got stuck. now it just boots right into download mode.
I don't know what changed.. but since going back to stock wouldn't work, I decided to re flash cwm and try to install cm7 again, and I'm now back up and running just fine. This whole situation was very odd... Thank you for being helpful.
Odin3-v1.85.zip is what you have set up on your computer?
Glad you fixed it.
Sent from my SGH-I727 using CyanogenMod
Related
Hello, I moved to TB from Fascinate.
I just rooted my TB and tried to change fonts (systems/fonts, DroidSans DroidSansFallback DroidSans-Bold files)
after I changed everything, I turned off the phone and am trying to turn it back on.
After the sound comes on, it froze showing clouds on the screen.
What should I do? Is there any Odin stock files something like that?
I see the posts on development forum with ADB things but the thing is I can turn my phone back on.
Please help!!!
Give it time to turn on. The clouds freeze. It's part of the boot animation. If that doesn't work hold the sound button down and power on and go into recovery and wipe data or flash a different rom thru cwm
Sent from my ADR6400L using XDA Premium App
I held the sound button down and power on and it straight went to bootloader instead recovery! after that I could turn on my phone but Rom manager doesn't work property. should I go back to stock and reroot it?
katsymoon said:
I held the sound button down and power on and it straight went to bootloader instead recovery! after that I could turn on my phone but Rom manager doesn't work property. should I go back to stock and reroot it?
Click to expand...
Click to collapse
first hold down power and vol down, then once you get into the bootloader, hit vol down till your highlighting recovery, hit power, now your in the recovery. Download a new rom and flash that.
Im havinbg the same problem. i was rooted with S-off and had clockwork installed and i tried to flash a new rom on and after i did that i tried to boot and it stuck on the cloud for 45 mins. afte that i tried again and again to no avail. Finally i went back into clockwork and did a factory wipe, bt it STILL sit on the clouds. Am i screwed?
Try a different rom and do a data & dvlik wipe before you flash...
About to try a different rom now. I also tried to chage my kernel with clockwork. Could that do anything different?
OKay so i got it to load with DAS BAMF. Lightning rom didnt work sadly =( im hoping this reboots good lol
i rooted my phone using odin infused gingerbread kernal.all was good . i messed with some battery logo changer and started messing with this red voodoo screen when in reboot recovery mode.any ways my phone is stuck on the samsung logo.pretty sure i bricked my phone.i have flashed back to stock rom and others but same thing. after reboot stuck on logo
also when i plug it into the usb charger the battey symb pops up but freezes.it wont even charge
Try gtg's ultimate unbrick.
The only known way to completely brick these phones is to flash a bad bootloader, and you have to go out of your way to do that. There's only one known instance of a hardbricked Infuse so far, and that was a volunteer for a known dangerous experiment.
If you can see anything on your screen, you're in good shape as your bootloader is still alive. If you see the Samsung logo you're in great shape as you have a booting kernel that just doesn't like something about your filesystems. Either way, Odining an unbrick package should fix you right up.
Edit: As I understand it, "power-off" charging is somehow handled by the kernel in a special way. At least it is on the Tab 10.1 - so an unhappy kernel means no power-off charging.
im such an nube i need instructions on how to do this.step by step
jamesrfraser said:
im such an nube i need instructions on how to do this.step by step
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1116251
Actually, for a Canadian, this is the best package - http://forum.xda-developers.com/showthread.php?t=1193927
your the best.it totally worked.right back to rogers gingerbread stock.you just saved me 600 bucks
Thanks for this allowed me to unbrick!
samsung infuse 4G stuck on white screen and wont load into download mode or reboot..
jamesrfraser said:
i rooted my phone using odin infused gingerbread kernal.all was good . i messed with some battery logo changer and started messing with this red voodoo screen when in reboot recovery mode.any ways my phone is stuck on the samsung logo.pretty sure i bricked my phone.i have flashed back to stock rom and others but same thing. after reboot stuck on logo
Click to expand...
Click to collapse
Looking for a lil help before I buy another infuse. I fell asleep with the phone in boot loader mode and didn't have it plugged up but phone died and next day tried to turn phone on and showed att then cut off. Plugged it in and keep cutting off and on blinking and won't charge bat. Won't go into either mode (download or reboot). I have read a few but not like mines.. won't read on computer. Any help please. I will tip or pay for cheap fix..? Thanks!
Remove the battery, put it back in, and press and hold only the two volume keys to enter download mode. Then use Odin to flash a package.
superweapons said:
Remove the battery, put it back in, and press and hold only the two volume keys to enter download mode. Then use Odin to flash a package.
Click to expand...
Click to collapse
In this case, not a good idea. The battery is dead.
After a few cycles of it blinking on/off the battery should hopefully have enough charge that it'll eventually stay awake.
I think there are some other tricks to charge the battery when it's severely discharged like this, but I don't know them - I've never been below 30%.
Worst case this should charge your battery a bit to get you out of where you are - http://www.staples.com/Vivitar-SC-ALL-Universal-Battery-Charger/product_791676 , or one of the "standalone" Infuse battery chargers on eBay.
links r dead
im in same boat but cant get links. please repost working links. i searched for 9 hours n nothing works
same thread,
just read the end of it
http://forum.xda-developers.com/showthread.php?t=1492024
edit: link fixed
1.Download ODIN ROGERS UXKG3 packages
Odin_UXKG3_rooted_no_bootloaders_v2.zip
2.Extract .zip file
3.Open Odin3_v1.81.exe
4.Click PDA choose PDA_UXKG3_rooted_no_bootloaders_v2.tar.md5 and PHONE choose PHONE_UXKG3.tar.md5
5.The phone to Download mode, but Phone -!- Com show on screen.
6.Odin message "Add!" start click.
7.Please wait to complete.
8.if fail Message try again to step 3-7
Sorry, I'm not good in English
I think I bricked my Infuse, rooted with odin kernel hack, worked fine, left it in the charger for the night, wake up, its not responding to any buttons, odd, pull out battery, reinsert battery and I get nothing no response from it. Plug in in the wall charger, and I get a little loading circle on the screen thats frozen, unplugged it, pulled out battery, reinsert battery and try booting again, this time it got as far as a ROGERS boot screen, but now Samsung boot screen. Left it for 15 minutes and it was still at rogers boot screen. haven't been able to get past the loading circle since.
Any chance of survival for my week old Infuse?
EDIT: forgot to mention I've tried to get it in download mode with no success.
EDIT2: Solved and recovered with Adam Outler unbrick
Sent from my SPH-D700 using XDA
So i used my xtc clip to s off an inspire and tried installing clockwork and SU but clockwork gave me an SU error. So i loaded the acehack and tried that, then i ended up getting the soft brick, so i flashed the ruu and it seemed to flash fine but now the phone wont turn on it just charges.
Out of nowhere it just turned on and started vibrating while connected to charger. It wont turn on still when i try.
xboxhaxorz said:
Out of nowhere it just turned on and started vibrating while connected to charger. It wont turn on still when i try.
Click to expand...
Click to collapse
Have you started with the easiest fix by pulling out the battery & waiting a minute & putting it back in, then try to power on the phone.
Sent from my Inspire4G using xda premium
yes left it out for 5 mins
Can you get into bootloader or fastboot
Sent from my Inspire 4G using XDA App
left battery out overnight and tried turning on again no go
no fastboot or bootloader
removed all cards and still will not power on
phone was left unplugged with battery inserted, just this moment it is now showing the htc logo and continuously vibrating
thats very weird, i dont think its bricked i think its faulty
turning it off does not work, i have to remove the battery
Does it allow you to get into the bootloader by pressing power and - volume at all?
xboxhaxorz said:
phone was left unplugged with battery inserted, just this moment it is now showing the htc logo and continuously vibrating
thats very weird, i dont think its bricked i think its faulty
turning it off does not work, i have to remove the battery
Click to expand...
Click to collapse
Sounds like you have a corrupt hboot (or ENG hboot on a late model Inspire). You need to get the stock hboot on it and it's not trivial. Try jumping into our irc channel and hopefully we can get you straightened out:
http://webchat.freenode.net/?channels=#liberatedAria
I had a similar situation happen to me. I was able to get into hboot after running hack kit but when it goes to reboot it takes about 10 minutes to finally come back on and does the same as described above. it comes on by itself finally while vibrating for about 2 minutes. after that it will come back up. i have even been able to flash custom roms to it with the only hitch that i can't reboot normally. i still just have to wait til it comes back up on its own. Very inconvenient, but still works. any ideas?
ctsfinishes said:
I had a similar situation happen to me. I was able to get into hboot after running hack kit but when it goes to reboot it takes about 10 minutes to finally come back on and does the same as described above. it comes on by itself finally while vibrating for about 2 minutes. after that it will come back up. i have even been able to flash custom roms to it with the only hitch that i can't reboot normally. i still just have to wait til it comes back up on its own. Very inconvenient, but still works. any ideas?
Click to expand...
Click to collapse
Make a nandroid of your current rom(if it's what you llike/want to use), run the RUU to restore factory config and dl the newest version of the hack kit and reroot it. Once done, restore your nandroid that you made earlier.
ATTN1 made a version of the HK w/ ENG-HBOOT that was discovered to cause very slow boots an pulled it down, the latest version should boot normally upon completion.
thank you for the info. i'll post back when i try to reroot and install ruu
i ended up warranty exchanging my phone, attn was helping me but i think mine was too fubared
If you let the phone battery run down, it will not, I repeat WILL NOT boot back up out of recovery.
When I plug the charger in it just boot it right back into recovery, which we all know won't charge the battery.
Pull the battery, put battery back in, plug in the charger....boot right back into recovery.
Power off from recovery with charger still plugged in...boot right back up in recovery.
Reboot system from recovery...boot right back up in recovery.
No way to charge the battery without getting out of recovery first.
No way to boot out of recovery without enough juice in the battery.
I had to use the extended battery (spare) to boot up the phone and...well you guest it...to flash the "other" recovery to get it working normal again.
Thunderbolt
Miui
TWRP 2.3.1.0
Works fine on earlier version, if this is a false alarm, then please delete.
Update: After reading through a few forums, TWRP might be able to charge while in recovery. It doesn't work for me.
That's a +1 for 4ext. It let's you charge the battery in recovery.
Sent from my Thunderbolt using Tapatalk 2
Your phone should charge in the powered off state though.
Thought so too but I know for a fact that cwm boots you into recovery as soon as there is enough juice to boot. Then having the screen on starting what little there is left. I know because I dealt with that for a month before I realized that my stock battery finally took a drive and wasn't retaining a full charge anymore.
Sent from my SCH-I535 using xda app-developers app
Its recovery 101 never mess with recovery unless you have a decent charge. You are just asking for trouble. I agree it makes 4ext look better because you can charge while in its recovery. If you let your phone die in recovery then you deserve it. Not to sound harsh but for the longest time when devs post roms they said make sure your battery is charged before flashing the rom. You think they was joking? lol
I remember having to do that with the Droid Eris.
Sent from my Thunderbolt using Tapatalk 2
I think what he means is, if you let your phone die normally, then plug it in to charge, it will boot to recovery. I had that happen to me when i first tried clockwork touch.
Sent from my Liquid ICS Bolt
Let me clear it up a bit.
If there's not enough juice in the battery to boot up the phone. If you push and hold the power button and nothing happen then you're screwed.
As soon as you plug in the charger, it will boot right to TWRP. you can not stop it from booting into TWRP, when you power it off from within TWRP it will boot right back into TWRP as long as the charger is connected.
Bottom Line:
If your battery went dead (under normal usage condition) and you don't have a good spare. You are SCREWED. This is a FATAL bug.
There's no way to charge a dead battery.
DarkJedi thinks that I'm in TWRP while the phone went dead. The answer is NO. The battery went dead under standby.
Dark Jedi said:
Its recovery 101 never mess with recovery unless you have a decent charge. You are just asking for trouble. I agree it makes 4ext look better because you can charge while in its recovery. If you let your phone die in recovery then you deserve it. Not to sound harsh but for the longest time when devs post roms they said make sure your battery is charged before flashing the rom. You think they was joking? lol
Click to expand...
Click to collapse
You're not understanding the post. This has nothing to do with messing with TWRP. Battery went dead under normal using condition, has nothing to do with recovery.
Shadow Death said:
Your phone should charge in the powered off state though.
Click to expand...
Click to collapse
That's the problem, it will not power down out of TWRP, as soon as you plug in the charger it will boot right back into TWRP.
It has the same cwm bug there used to be. When you plug the phone in to charge it boots into recovery.
Sent from my Thunderbolt using Tapatalk 2
That's good to know, I had been using TWRP on my Thunderbolt so I guess it's time to switch back to 4ext, i just wish there was software keyboard support in 4ext.
Also with a note, I had this problem the op had when using TWRP on my Asus Transformer, actually strangely, while the recovery was installed it would not charge the device at all, not even when turned off. Once TWRP was taken off of it, and CWM back on, it charged properly. After using TWRP I can say for some reason this recovery has some serious game changing bugs.
EDIT: Also, "Boot Manager" doesn't seem to be compatible with restoring backups made with TWRP.
Give this build a shot and see if it fixes the charging:
http://techerrata.com/dees_troy/mecha.img
Ellises said:
That's good to know, I had been using TWRP on my Thunderbolt so I guess it's time to switch back to 4ext, i just wish there was software keyboard support in 4ext.
Also with a note, I had this problem the op had when using TWRP on my Asus Transformer, actually strangely, while the recovery was installed it would not charge the device at all, not even when turned off. Once TWRP was taken off of it, and CWM back on, it charged properly. After using TWRP I can say for some reason this recovery has some serious game changing bugs.
EDIT: Also, "Boot Manager" doesn't seem to be compatible with restoring backups made with TWRP.
Click to expand...
Click to collapse
No idea what your trouble with the Transformer were but charging on the Transformer isn't done in recovery and changing recovery wasn't the fix.
The Thunderbolt & most all HTC devices made after it use recovery for charging. There's a handful of HTC binaries & a special init.rc that make the device charge while turned off. None of this is part of the recovery code so it's not inherent to TWRP itself.
Dees_Troy said:
Give this build a shot and see if it fixes the charging:
http://techerrata.com/dees_troy/mecha.img
Click to expand...
Click to collapse
my port is busted so i cant test charging but the build does work
Another tester confirmed that it was fixed in that version, so I have updated everything.
I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?
aanonymoushuman said:
I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?
Click to expand...
Click to collapse
First error was you wiped system before reboot so there was nothing there to boot into... Leave the battery out for a bit then insert and boot into recovery.. reflash rom and this time only wipe cache and dalvik not system.. reboot.. Also how charged was the battery? maybe it is almost dead and needs charging!
Racing19969 said:
First error was you wiped system before reboot so there was nothing there to boot into... Leave the battery out for a bit then insert and boot into recovery.. reflash rom and this time only wipe cache and dalvik not system.. reboot.. Also how charged was the battery? maybe it is almost dead and needs charging!
Click to expand...
Click to collapse
I cant boot into anything at all... And the baterry was fine it was maybe at 60% when I flashed
aanonymoushuman said:
I cant boot into anything at all... And the baterry was fine it was maybe at 60% when I flashed
Click to expand...
Click to collapse
what rom were you flashing when this happened?? if it was a stock rom you should have been using odin.. unless it was one of the stock CWM flashable roms... if you can't get it going send me a pm.. I do JTAG repair
aanonymoushuman said:
I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?
Click to expand...
Click to collapse
Wait... you wiped system after flashing stock...? That wiped the stock rom That's why nothing booted after the reboot.
I don't know why you can't get into download mode... When you plug in a usb when the battery is out does the phone vibrate? If not, try another usb cable. If that fails then you do have a hardware issue. If the phone vibrates hold vol + and vol - and power and reinsert battery-you should get download mode.
AFAIK, they (T-Mo) put the phone in download mode and check the flash counter. If it says anything other than "no" they will not accept it. Any odin flash adds to the flash counter.
anactoraaron said:
Wait... you wiped system after flashing stock...? That wiped the stock rom That's why nothing booted after the reboot.
I don't know why you can't get into download mode... When you plug in a usb when the battery is out does the phone vibrate? If not, try another usb cable. If that fails then you do have a hardware issue. If the phone vibrates hold vol + and vol - and power and reinsert battery-you should get download mode.
AFAIK, they (T-Mo) put the phone in download mode and check the flash counter. If it says anything other than "no" they will not accept it. Any odin flash adds to the flash counter.
Click to expand...
Click to collapse
As said before it's a brick, no screen, no vibration nothing. And I don't think T-Mo can even get to the phone unless they jtag it or something, which they will most likely not do as it will cause discomfort and timeloss to the customers (ME)
aanonymoushuman said:
As said before it's a brick, no screen, no vibration nothing. And I don't think T-Mo can even get to the phone unless they jtag it or something, which they will most likely not do as it will cause discomfort and timeloss to the customers (ME)
Click to expand...
Click to collapse
Well I doubt they can do that at the store (I don't have any confidence in the salespeople's tech ability there lol), so if you are under warranty just tell them that when you unplugged it this morning it was like that :laugh:
If it doesn't vibrate when plugged in and no battery installed then it sounds like a hard brick.
I think they do the manufacturer warranty as an exchange on the spot, so even if they do figure it out eventually you should be good.
But it would suck if they can get it into download mode at the store... better try numerous usb ports (even switch computers to be sure!) and cables to be sure Also wouldn't hurt to leave the battery out overnight and try again. If they get it in download mode... well two things. One they won't ever honor any warranty on the phone anymore (and they will give the phone back to you), but two... if they can get it in download mode have them leave it like that and rush back home - and then you're back in business
Kind of a win-win...
anactoraaron said:
Well I doubt they can do that at the store (I don't have any confidence in the salespeople's tech ability there lol), so if you are under warranty just tell them that when you unplugged it this morning it was like that :laugh:
If it doesn't vibrate when plugged in and no battery installed then it sounds like a hard brick.
I think they do the manufacturer warranty as an exchange on the spot, so even if they do figure it out eventually you should be good.
But it would suck if they can get it into download mode at the store... better try numerous usb ports (even switch computers to be sure!) and cables to be sure Also wouldn't hurt to leave the battery out overnight and try again. If they get it in download mode... well two things. One they won't ever honor any warranty on the phone anymore (and they will give the phone back to you), but two... if they can get it in download mode have them leave it like that and rush back home - and then you're back in business
Kind of a win-win...
Click to expand...
Click to collapse
I got a replacement going from T-Mobile, they just sent out the new phone today, but I'm confused do I send them my broken one right now? or wait till the new one comes?
They should have explained everything on the phone, they will send you a box to return it in . And if they find out that it has been rooted and modded , you could be charged the full price for the phone. Every time I sent the phone back I've always read it back to stock if yours was bricked hopefully they won't notice
Sent from my SAMSUNG-SGH-T769 using xda app-developers app