Develop Bugs

Did I Brick? Stuck at Android Recovery Screen

Rooted...no issue there.
Installed ROM Manger.
Installed Clockwork Recovery from Rom Manager as I wanted to install a new rom.
Now when I boot, no matter what combination I hold down, it goes to the Android System Recovery screen and in the background is the white triangle, yellow exclamation point and little android guy.
I can move between the three ofered choices but pressing the power button (I assume this is the OK button) does nothing.
Thoughts / help?

Does your computer recognize it? If it does you should try adb download and see if you can get into download mode
Sent from my SPH-D710 using xda premium

Have you even tried pressing any of the soft keys, home button?
Sent from my SPH-D710 using xda premium

Just realized I posted the question in the wrong forum as well.
Computer makes a noise as though it knows it's connected, yet it doesn't show up and odin and kies don't find it either.

I think home button is select and power button is back, but I haven't used stock in a long time, so might be remembering incorrectly.
I suggest you don't use Rom Manager to install recovery. It doesn't work properly for this phone and could lead to non-recoverable problems.
Read this thread and you'll have references to everything you need to undo and start from scratch:
http://forum.xda-developers.com/showthread.php?t=1342728

THANKS!
What a doof........hit the home button and all is fixed!!!!!!!!!!!!!!!!!!!!

jfenton57 said:
What a doof........hit the home button and all is fixed!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
And leave stupid ROM manager alone it's crap on Samsung
Sent from my SPH-D710 using xda premium

I don't know for the life of me why people still use Rom manager to install roms.

I think they are probably HTC converts because nothing here is asking them to use ROM manager.

jordan2333 said:
I don't know for the life of me why people still use Rom manager to install roms.
Click to expand...
Click to collapse
Lazy lazy and most don't know how to do it correctly....
Sent from my SPH-D710 using xda premium

sfhub said:
I think they are probably HTC converts because nothing here is asking them to use ROM manager.
Click to expand...
Click to collapse
I came over from an Evo and believe me everything pointed to not use Rom Manager when I had my phone as well. I agree that if people took the time to read properly they would see that Rom Manager and a few other crazy things they do are not suggested. But they make sure to have time to post and read their threads when they screw up. Honestly with all the brick laying and blue light specials up in herrre. Do you really need to post your problem and how do you fix it...
His problem is one of 100 exactly the same in here and instead of searching and helping himself he did the same lazy thing that got him stuck in the first place. Then too lazy to find out how to work CWM. Quite sure he will be back again if he keeps up this route... @OP not trying to be an ass but just hate to see people who don't want to help themselves.

Sorry to hear that you've bricked OP. Hope you can get a replacement and get back into owning your phone.
Here's what I've done to avoid bricking since I am also somewhat new to the E4GT...
Read the forums on XDA.
Observed what others are doing that worked.
Didn't flash anything you are unsure of.
Became familiar with ODIN.
Stayed away from ROM manager.
Flashed using el29 rogue recovery only. (I've been successful with this so far, others say to use el26.)
Wipd cache/dalvik-cache/data/system.
Purchased mobile ODIN, $5 is better than the deductible to get a replacement.
Sent from my SPH-D710 using xda premium

I bricked but it was a bad recovery well not bad just messy team trolls recovery bricked me 2 weeks ago wiping Cache . But as always when u post questions like this here ur gonna hear it lol but searching helps.
Now if its hard bricked ud not even get to recovery at all just a blue light and a black screen that if is ur case unplug it cause it runs the battery super hot .
If not in that position than try power and volume down if it does not bring u to download mode to Odin another recovery if that don't work idk
Sent from my SPH-D710 using xda premium

sfhub said:
I think they are probably HTC converts because nothing here is asking them to use ROM manager.
Click to expand...
Click to collapse
The OG Epic uses ROM Manager just fine.
Sent from my SPH-D710 using Tapatalk 2 Beta-2

azyouthinkeyeiz said:
The OG Epic uses ROM Manager just fine.
Sent from my SPH-D710 using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
That took a long time and a ton of porting. Pretty recent. Went through Eclair and Froyo without support.

The Root said:
That took a long time and a ton of porting. Pretty recent. Went through Eclair and Froyo without support.
Click to expand...
Click to collapse
Porting was needed for CWM recovery. Not ROM Manager. Support for ROM Manager comes from device devs, not koush. In the form of uploading vetted software, that doesn't corrupt. It is a universal starting point, not a fully functional product.
But regardless, I wasn't even talking about it's support. I was saying people other than ones with HTC devices can get into the habit of using ROM Manager.
Sent from my SPH-D710 using Tapatalk 2 Beta-2

azyouthinkeyeiz said:
Porting was needed for CWM recovery. Not ROM Manager. Support for ROM Manager comes from device devs, not koush. In the form of uploading vetted software, that doesn't corrupt. It is a universal starting point, not a fully functional product.
But regardless, I wasn't even talking about it's support. I was saying people other than ones with HTC devices can get into the habit of using ROM Manager.
Sent from my SPH-D710 using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
I never used it even when there was support. Lol
Sent from my SPH-D710 using XDA App

Doesn't matter the recovery is in the kernel and rom manager will not work on this phone ....there is no separate recovery partition and ROM manager won't flash the recovery right on here since it's part of the kernel partition.koush doesn't really care he made it to temporarily flash a recovery like touch that might work if not for ics kernels... The thing is it doesn't work people should not rely on it like a crutch
Sent from my SPH-D710 using xda premium

Getting a Different Phone

I have a Samsung Galaxy SIII from AT&T (d2att ), and I have it rooted, running task650's AOKP, and TWRP 2.4.1.0 for recovery. It works fantastic, and I love it I have, however, been trying everything I can think of to try and get ktoonsez's kernel to work on it, for the features that his kernel offers. I am having a funky issue, which according to task, kt, and a few others on the boards, is device-related. It seems that my phone, individually, is the problem. This leads me to my question.
How feasible is it to get AT&T (or Samsung?) to replace my phone, based on the fact that there is something different hardware-wise between mine and the vast majority of other peoples?
It seems that nearly everyone who runs this combination of task and ktoonsez has nothing but good things to say, and I have yet to see anyone gripe about the same issues that I have had, and not be able to fix them, usually by a simple full wipe. I have tried to do full wipes with and without letting Google initialize/restore my account. I have tried going back to stock everything, and trying again. I have made sure to turn off Performance Control, so there should be no conflict there. I have tried setting up my phone in its entirety, restoring information, restoring apps with TiBu, and then installing the kernel. I have tried with and without deleting mpdecision. I am following all of the directions posted per OP for both threads, and with the gapps posted by task himself. Nothing works, and I end up in a glitchy boot loop almost immediately after flashing the kernel, even if my phone was running buttery stable before the flash.
I have come up with a couple things to try tonight, but if they don't work, I would like to pursue getting a new phone to replace this one. Is that an option?

You will need to do a warranty replacement through Samsung unless you have device insurance through att. But then you will be paying the deductable on it.
There are quite a few reports of people in ktoonsez's thread that stated they had to return their device and get a new one for his kernel to work. Not sure you searched good enough. But either way, you are not the first to have a device that cant run his kernel. I can assure you of that.

task650 said:
You will need to do a warranty replacement through Samsung unless you have device insurance through att. But then you will be paying the deductable on it.
There are quite a few reports of people in ktoonsez's thread that stated they had to return their device and get a new one for his kernel to work. Not sure you searched good enough. But either way, you are not the first to have a device that cant run his kernel. I can assure you of that.
Click to expand...
Click to collapse
Thank you. I may not have read it well enough Do you mean the deductible through Samsung or AT&T? And ho do I approach the warranty? I know, at least where I work, we wouldn't honor a warranty on something that was used for purposes outside of it's intended use (i.e. rooting). Granted, I don't work for a phone company

drinfernoo said:
Thank you. I may not have read it well enough Do you mean the deductible through Samsung or AT&T? And ho do I approach the warranty? I know, at least where I work, we wouldn't honor a warranty on something that was used for purposes outside of it's intended use (i.e. rooting). Granted, I don't work for a phone company
Click to expand...
Click to collapse
It would be the deductible through AT&T if you have device insurance. If going through Samsung, something would have to be a manufacturers defect in order for them to warrant a replacement device. I don't think either company will replace the device because you can't use a custom kernel. So you would need to get creative on your story before you go either route.

task650 said:
It would be the deductible through AT&T if you have device insurance. If going through Samsung, something would have to be a manufacturers defect in order for them to warrant a replacement device. I don't think either company will replace the device because you can't use a custom kernel. So you would need to get creative on your story before you go either route.
Click to expand...
Click to collapse
Time to get creative lol
Sent from my SGH-I747 using xda app-developers app

Settling In
I don't know if this could be a factor but, you will experience something commonly called a settling in period after installing a new kernel.
I have been through trying a couple other custom kernels for I747 plus all the progression of KT747 releases for TW ICS and TW JB since 9-23 release and have been through two phones due to warranty replacement. On both phones I have experienced significant settling in glitches for a while after flashing KT's or other kernels. These include crashing on boot, frequent screen freezes after boot, KTweaker settings not sticking, etc. These issues are far more extreme on first install of kernel than when flashing a new release to phone that already has kernel installed. First boot after first install can take about twenty problematic boot attempts to start behaving and it can take two or three days before kernel "settles in" and problems pretty much disappear.
In my feeble little mind, I envision the new kernel having to grow neurons into the guts of the phone hardware.
If you want to run this kernel and your phone will basically boot but, is all glitchy, I would say don't freak out. Have some patience, just keep rebooting, and give it time to settle in. For most the phone will straighten out in a few days.
Hope this helps.

bsam55 said:
I don't know if this could be a factor but, you will experience something commonly called a settling in period after installing a new kernel.
I have been through trying a couple other custom kernels for I747 plus all the progression of KT747 releases for TW ICS and TW JB since 9-23 release and have been through two phones due to warranty replacement. On both phones I have experienced significant settling in glitches for a while after flashing KT's or other kernels. These include crashing on boot, frequent screen freezes after boot, KTweaker settings not sticking, etc. These issues are far more extreme on first install of kernel than when flashing a new release to phone that already has kernel installed. First boot after first install can take about twenty problematic boot attempts to start behaving and it can take two or three days before kernel "settles in" and problems pretty much disappear.
In my feeble little mind, I envision the new kernel having to grow neurons into the guts of the phone hardware.
If you want to run this kernel and your phone will basically boot but, is all glitchy, I would say don't freak out. Have some patience, just keep rebooting, and give it time to settle in. For most the phone will straighten out in a few days.
Hope this helps.
Click to expand...
Click to collapse
I suppose that is possibly what's going on with mine, I'll give it a couple more tries
Sent from my SGH-I747 using xda app-developers app

Just an advice, make sure you restore everything to stock before you do
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

pcshano said:
Just an advice, make sure you restore everything to stock before you do
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app

drinfernoo said:
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just depends on how thorough the at&t rep is. You have to Odin back to stock, triangle away, unroot and factory reset for them not to know at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

drinfernoo said:
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Do not intentionally brick your device. That could be just as bad as leaving your phone rooted when you take it in (depending if Samsung can see any part of the storage). As far as warranty exchange "excuse" that is on you to decide. Follow the post quoted below to help your chance at warranty exchange. This has been discussed quite a bit all over the place.
hednik said:
Just depends on how thorough the at&t rep is. You have to Odin back to stock, triangle away, unroot and factory reset for them not to know at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse

You know, I've run tasks rom since it was still 4.1 and have always used the kernel provided in his rom. It runs great, and I wouldn't change it. My battery life and everything else is great. I can get 17 hrs with 3 hrs 34 mins screen time and have 20% battery left. I think trying to get a replacement device just to run a different kernel is absurd... just my .02 cents worth
Sent from my SGH-I747 using xda premium

G-Man. said:
You know, I've run tasks rom since it was still 4.1 and have always used the kernel provided in his rom. It runs great, and I wouldn't change it. My battery life and everything else is great. I can get 17 hrs with 3 hrs 34 mins screen time and have 20% battery left. I think trying to get a replacement device just to run a different kernel is absurd... just my .02 cents worth
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I completely agree. I'm on tasks currently using his underwear kernel provided. I've also tried KT's kernel as well. Yes you can get more customization with KT's and his custom governor, but is it worth it to go through all the hassle to get a new device? I would say no. Like I said I've tried both kernels, I'm currently using tasks underwear kernel, I may try KT's again, may not. When I did before, I didn't notice a drastic difference between the two, esp not enough to warrant going through a device replacement.
Consider this. You are running tasks rom with absolutely no issues with the kernel he provides. Is that not good enough? I know it is for me. His rom is absolutely the most stable rom I've ever tried on any device. Remember it's just a phone. Just some food for thought.
Sent from my SGH-I747 using xda app-developers app

Probably right, but i don't always run task's ROM, either. My favorite ROM so far has actually been ParanoidKANGDroid, but I wanted 4.2.1, so I went to task. I'm actually running PACman right now, and for the time being, even his PC is broken
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

No matter which rom you are running, it's crazy to exchange a device (and having to lie to do it) just to run a different kernel... think about it...
Sent from my SGH-I747 using xda premium

G-Man. said:
No matter which rom you are running, it's crazy to exchange a device (and having to lie to do it) just to run a different kernel... think about it...
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Of course, but if it allows me more flexibilities and control over my phone and what it does, I'm all over that
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Bricking your phone would be the easiest way to get a new one and I've seen plenty of people accidentally bricking their i747 and getting a new one from Samsung. They won't even check if its rooted or not.
Check this thread: http://forum.xda-developers.com/showthread.php?p=34556189
Sent from my SGH-I747 using xda app-developers app

liltitiz said:
Bricking your phone would be the easiest way to get a new one and I've seen plenty of people accidentally bricking their i747 and getting a new one from Samsung. They won't even check if its rooted or not.
Check this thread: http://forum.xda-developers.com/showthread.php?p=34556189
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
That's a douche bag move.... pain and simple.
Sent from my SGH-I747 using xda premium

G-Man. said:
That's a douche bag move.... pain and simple.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
When the s3$ first come out, a lot of people were bricking them. Trying to root or installing an international ROM. I'm pretty sure Samsung staff was aware of that but they still gave free replacement. Some people even got a replacement from att or others carriers for free.
Sent from my SGH-I747 using xda app-developers app

If I do end up getting a replacement, can I take a nandroid, and restore it to the new phone?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Idiot mistake and the company that fixed it for me

I made the ultimate mistake the other day. I flashed a kernel for another device onto my S3 and of course paid the price of bricking my phone.
To set the scenario, I had back surgery last Thursday and was released from the hospital on Friday with a supply of pain killers and orders to not do anything. Well, while sitting around doing nothing I got bored and decided to work on a couple of my friends tablets that needed rooting and roms installed. I got them done without any issue and then decided to mess with my phone. There were a couple of new kernels I wanted to test and so I decided to do this. I booted into recovery and selected the kernel and flashed. At that moment I realized that the kernel I just flashed was not for my phone and when I tried to turn on the phone and nothing happened, I knew immediately what I had done and after saying a few nasty words to myself I started searching for a way to fix it. While searching through the forums I kept reading about MobileTechVideos.com and their ability to jtag repair phones. Since I have never had to do this and my phone was not going to work anyway I decided to give them a call and see what they had to offer. I called them and asked about their services and they said that it should be no problem fixing my phone. I live in Dallas and the company is in Bryan, about 3 1/2 hr drive, I decided the easiest and fastest way to get my phone repaired was to take it to them and wait. On Tuesday morning I drove to Bryan and dropped off my phone. When I had called them they told me it might be a couple of hours to fix it, but once I told them it was a tmobile device they told me to wait because it might only take a few minutes. During this time they showed me around the office and I was really impressed. What impressed me the most is that no one working for this comany could have been over 25, even the owner. So after a brief tour of the office, about 10 minutes, my phone was fixed and was ready to go. I paid my $60, which I believe was well worth it, said thank you and was on my way with my fully functional phone.
They never asked me to post anything and I don't have any affiliation with this company. I just want to post about a company that provided the service they said they would at a price that is reasonable since without it I would have a $600 paperweight. So if anyone ever happens to make the foolish mistake that I made and you need your S3 repaired, I would 100% recommend this company. Here is the link to their website, http://mobiletechvideos.mybigcommerce.com, mods let me know if this is not allowed and I will remove it.
I know I am always questioning online companies likes these, but this particular company has earned a customer for as long as they are open and support whatever device I happen to be using. I just hope that since I made this mistake I will hopefully never make it again.
Moral of story: If on heavy doses of pain killers don't crack flash kernels. If might cost you in the end. :}

Never bricked a phone before but I've heard great things about that company. If I ever run to trouble I'll surely go to them immediately.
Thanks for the review.
Sent from my SGH-T999 using xda app-developers app

Thanks for the review - it's good to hear good comments about the company "just in case".
Hope you're feeling better.

Cool.... Drugs say No to them... Get well
Sent from my SGH-T999 using xda app-developers app

bgbagz said:
Cool.... Drugs say No to them... Get well
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Pain meds after back surgery are a definite yesssssss, just don't brick your phone. lol
Happy to read a ringing endorsement, though - also "just in case".

Hey dude. Im in Dallas too. Good to know. I read all about them. They are really good in jtag fix devices. They were the first ti have s-off on the htc one. They did it after an hour of getting the phone. I havent brick any phones yet but I have their number save just in case. I have seen where they sale the jtag device to do it yourself. It cost about $100 it is well worth it
Sent from my SGH-T999 using xda app-developers app

Good service but more expensive than some.. but local is good.
Sent while sleeping in chair.

I'm glad your device is back and operational. Thanks for letting us know about a trusted reputable service.
Sent from my SGH-T999 running Chihuahua v1 ROM

Thanks. I am not one who likes reviewing companies, but this one time I felt it was justly deserved. I read to many threads about shipping your device to someone and for a cheaper cost they will fix it. That makes me uncomfortable. I would rather pay a little more for the peace of mind. Even then I was more comfortable driving as far as I did, after just having surgery, because of my skeptism. That is why I felt the review was warranted to help someone when they are not local.
Sent from my Transformer Prime TF201 using xda premium

Josh @mobiletechvideos is certainly a trusted guy. He's been here since vibrant days.
Sent from my SGH-T999 using Tapatalk 2

I didn't realize your phone would get bricked with a bad kernel. You can't just go into odin and restore the original system image?
Not criticizing here, I'm just trying to learn something. Glad you had a good experience, as I'm sure at some point in my life I'm going to brick a phone.
Sent from my SGH-T999 using xda app-developers app

I can confirm that flashing a wrong kernel will brick your phone. I did that and still not sure if it was wrong one but in did screwed my phone, luckily I exchanged it for another device since I had it for a week.
Sent from my SGH-T999 using xda app-developers app

I have done the same thing. I flashed an international ROM on my T-999. I had also read great reviews people had using Mobiletechvideos. He had mine back to me in less than 1 week. Awesome work. If someone from MTV is on here, thank you!!

wcterp said:
I didn't realize your phone would get bricked with a bad kernel. You can't just go into odin and restore the original system image?
Not criticizing here, I'm just trying to learn something. Glad you had a good experience, as I'm sure at some point in my life I'm going to brick a phone.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It wasn't a bad kernel, it was a kernel for a different device. I was working on several devices that day and put a kernel for a nook tablet into my S3 folder by mistake. Teaches me to only work on one device at a time.
Sent from my Transformer Prime TF201 using xda premium

Yes don't take painkillers give em to me lol
thanks for the write up good to know

Can't you just re flash the entire rom stock or not with Odin or cwm?
I dunno, first time I "bricked" my phone was from an incorrect kernel also. Just downloaded stock touch wiz rom go to download mode and flash with Odin.
I'm not aware that you can brick your phone unless you mess with the bootloader itself.
Bricking means exactly what it sounds like. It's just a piece of useless hardware that you can't recover, in this case, with an incorrect kernel flash, you can, either through another kernel that is compatible with your device or re flash the entire rom; with either Odin or cwm.

wardoc22 said:
Can't you just re flash the entire rom stock or not with Odin or cwm?
I dunno, first time I "bricked" my phone was from an incorrect kernel also. Just downloaded stock touch wiz rom go to download mode and flash with Odin.
I'm not aware that you can brick your phone unless you mess with the bootloader itself.
Bricking means exactly what it sounds like. It's just a piece of useless hardware that you can't recover, in this case, with an incorrect kernel flash, you can, either through another kernel that is compatible with your device or re flash the entire rom; with either Odin or cwm.
Click to expand...
Click to collapse
When trying to connect to computer it would not recognize the device correctly. So no odin if you can't connect to computer. No flashing anything else if the phone doesn't turn on. That would be as hard bricked as you can get.
Sent from my SGH-T999 using xda premium

tmjohnsonfse said:
When trying to connect to computer it would not recognize the device correctly. So no odin if you can't connect to computer. No flashing anything else if the phone doesn't turn on. That would be as hard bricked as you can get.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yeah but you can't hard brick it if you flash a wrong kernel unless the kernel replaces your bootloader.
Oh wait, ok I get it. You flashed a kernel that replaces the bootloader also, like with the international dual boot kernel

wardoc22 said:
Yeah but you can't hard brick it if you flash a wrong kernel unless the kernel replaces your bootloader.
Oh wait, ok I get it. You flashed a kernel that replaces the bootloader also, like with the international dual boot kernel
Click to expand...
Click to collapse
Correct!
Sent from my Transformer Prime TF201 using xda premium

4th time I had to factory restore. This is unbelievable.

Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium

If its boot looping that's not normal obviously you know that so I would exchange it. Keep swapping until you get a good one.
Sent from my Nexus 7 using Tapatalk 4

Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
wha?? I would return immediately.

Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium

player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Will try that. Thanks!
Sent from my SPH-L710 using xda premium

player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thought I'll give you an update.. Installed CM10.2 for a few days, as you said.. No issues what so ever. Decided to try my luck with CoolRom and it bootlooped the moment I rebooted.
Decided on doing a complete wipe of the device and flashing a factory rom ( http://forum.xda-developers.com/showthread.php?t=2381582 ).
Don't want to give up hope yet.

Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app

smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Rooted it for some apps that required root access.

smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
There are tons of apps that require root access and are mandatory for many people including me.

I wouldn't bother to unlock and root. The N7 is flawless and fast out of the box.
Sent from my Nexus 7 using xda app-developers app

Again, root access is required for most decent backup programs and cloud data syncing apps. The issue doesn't require a debate about whether you need root or not. Yes the N7 is wicked fast and if you only use it as a bathroom reader for Facebook and light use, then that's cool. I like OTG support for my thumb drives when I'm in the field working.
Glad CM is working for you. That at least shows it isn't a hardware problem. I'd reflash stock images and see where that leaves you. Worse case you use CM (oh my!) until we see a patch.
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
You also should do a complete wipe between stock and CM and AOSP and vice versa. It typically bootloops if you dirty flash one type of rom over another. Stock and AOSP are pretty much the same thing but some custom ROMs like CM have different structures that hose you.
Sent from my Nexus 7 using XDA Premium 4 mobile app

player911 said:
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium

Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.

Mine bootlooped today. Stock. No root or anything. I was forced to do a factory reset from recovery. Very troubling that this seems to be happening to a few people. There's a couple of threads over on android central of people having the same problem.
Sent from my Nexus 4 using XDA Premium 4 mobile app

I will admit this device is great without root but I prefer custom ROMs and titanium backup
Sent from my HTC One using XDA Premium 4 mobile app

Just sat here rebooting the n7 a few time and it happened. Held power and got it to re start the boot process and it loaded. As soon as I unlocked it I got an android process media force close
Sent from my Nexus 4 using XDA Premium 4 mobile app

Andro_pty said:
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.
Click to expand...
Click to collapse
I rather not do the whole process of sending, receiving, ect. Call me lazy or whatever. Either way, it seems like my problem is solved, I'm once again happy.
Sent from my SPH-L710 using xda premium

Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Super glad its worked. It worked for me. It worked for another guy. And worked for you. I think there is a bad rom image flashed on all of these that are causing lots of problems. The only fix is to clean slate and reflash the stock image, or move to custom ROMs.
Probably need to get someone to write a little app that just automates flashing the stock image again just for simplicity.
I'll probably create a new thread covering this.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

The stock images and the install script .bat file is simple enough.
Especially if you're rooted already. Since you already have the drivers installed on your computer.
Toolkits need to die a slow painful death.

You need root access a pen drive using an OTG cable, install app like titanium backup etc. Rooting doesn't mean custom rom or kernel
Sent from my Nexus 7 using xda app-developers app

Stuck with 4.3 and it's problems, looking for guidance on what to do now

Yesterday I made the mistake of taking the OTA update to 4.3 while in the process of doing a clean install of the new MOAR rom. Unfortunately, I had failed to do the proper homework otherwise I would have known to avoid the update like the plague. Luckily, I didn't manage to brick my phone, by trying to revert back to an earlier bootloader, but I am stuck now with a tripped warranty bit, and a phone that drains battery at almost 1% per 5mins while being almost completely unable to maintain a cell or data signal.
Now, I know it's going to be a little time before devs have a chance to tear apart 4.3 to fix it's issues, but I'm hoping that I can get some guidance on how I might improve my phone's performance, or at least minimize the negative aspects of the new update in the meantime. Right now I am running MOAR 7 and I have already tried resetting and reinstalling the rom fresh.
Thanks for any help.
Sent from my GT-N8013 using xda app-developers app

treblesum81 said:
Yesterday I made the mistake of taking the OTA update to 4.3 while in the process of doing a clean install of the new MOAR rom. Unfortunately, I had failed to do the proper homework otherwise I would have known to avoid the update like the plague. Luckily, I didn't manage to brick my phone, by trying to revert back to an earlier bootloader, but I am stuck now with a tripped warranty bit, and a phone that drains battery at almost 1% per 5mins while being almost completely unable to maintain a cell or data signal.
Now, I know it's going to be a little time before devs have a chance to tear apart 4.3 to fix it's issues, but I'm hoping that I can get some guidance on how I might improve my phone's performance, or at least minimize the negative aspects of the new update in the meantime. Right now I am running MOAR 7 and I have already tried resetting and reinstalling the rom fresh.
Thanks for any help.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
If you're on MOAR, then your battery issues are not being caused because you tripped the warranty and flashed the OTA. You may flash any rom, mod, kernel, tweak, etc, you want through CWM, just don't try to downgrade to a different bootloader(ie 4.1.2), through Odin, or you'll brick. Try different roms, modems, combinations, just like before, until you get back to what you want. Good luck
Sent from my SPH-L710 using Tapatalk

So I can reflash the MD4 modem? I was under the impression that I was stuck with MK3. Can I basically change anything I want as long as I don't try to Odin in an older update?
Sent from my GT-N8013 using xda app-developers app

treblesum81 said:
So I can reflash the MD4 modem? I was under the impression that I was stuck with MK3. Can I basically change anything I want as long as I don't try to Odin in an older update?
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
Yes, you can flash the MD4 modem, but I tried flashing down to a 4.1.2 modem and lost data, so that may happen to you(probably will). And as long as you flash from cwm you are fine. But read any ROM OPs very carefully, because there are a few out there that flash a bootloader if I'm not mistaken. But overall, yes, you are ok flashing as long as you don't use Odin to try to downgrade to a different bootloader.
Sent from my SPH-L710 using Tapatalk

Well, I guess its good to know that I have some options, but also disappointing that I can't just Odin in a complete package to start from, since in the past that has always been the best way to ensure stability in the end result. As for the warranty bit, I'm not too worried about it, since it can only really hurt me if I need to take it to sprint for some work. That being said, if there really is no way to reset it, or completely remove Knox for that matter, I probably won't be buying another samsung phone... I really don't like the idea that the manufacturer would booby trap their product like that.
Sent from my GT-N8013 using xda app-developers app

treblesum81 said:
Well, I guess its good to know that I have some options, but also disappointing that I can't just Odin in a complete package to start from, since in the past that has always been the best way to ensure stability in the end result. As for the warranty bit, I'm not too worried about it, since it can only really hurt me if I need to take it to sprint for some work. That being said, if there really is no way to reset it, or completely remove Knox for that matter, I probably won't be buying another samsung phone... I really don't like the idea that the manufacturer would booby trap their product like that.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
I'm sure it's only a matter of time before someone cracks it. Genius devs like @Chainfire live for challenges like this
Sent from my SPH-L710 using Tapatalk

I hope they crack it soon.. I've already had the urge to throw it against a wall more than once today. Its magically unrooted itself three times already and the problems seem to multiply every time I try a different OS in the hopes that one will work well.
Sent from my GT-N8013 using Tapatalk