Related
So yesterday I flashed the new aokp build 39 know all the risks of bricking but i thought my phone was immuned lmao no jk but i have been flashing for a few months now sometimes going back to el26 and sometimes i just flashed using ics recoveries wiped data and all and since i never bricked I thought it was safe, but yesterday i was not so lucky like i said i was on aokp 39 and wanted to go back to wicked so instead of going back to el26 i used the included cwm recovery and went to restore my backup and to stop this story from dragging on it restored but when it booted back up it would not go past samsung screen i cld get into recovery and odin mode tried sfhub one click same thing stuck at samsung logo everything i tried nothing worked brought it to sprint today I was honest told em i was rooted and explained i already tried to flash back to stock their guy said' "i'll be able to get it." Lol i said okay but I knew he could not he came bck said he couldnt i have tep and he ordered me a new one and i can get it tomorrow with no charge... Just an fyi u can get ur phone replaced for nothing even if u brick so i have my tablet to get me by til tomorrow so the cwm included in aokp 39 is not safe...
Sent from my K1 using xda premium
"MOD EDIT: Always use the Stock CWM5 recovery for anything you want to flash. Do not use the recovery that comes with this rom to flash or do anything with. "
You kind of set your self up there. The thread states that AOKP B39 doesn't come with a safe recovery. Either way, have fun with your new E4GT
MochaCharok said:
"MOD EDIT: Always use the Stock CWM5 recovery for anything you want to flash. Do not use the recovery that comes with this rom to flash or do anything with. "
You kind of set your self up there. The thread states that AOKP B39 doesn't come with a safe recovery. Either way, have fun with your new E4GT
Click to expand...
Click to collapse
I believe Jay added the MOD EDIT after he had bricked his phone. There was no warning about not using that recovery prior to that. There was a long discussion about that in the thread.
dafluke24 said:
I believe Jay added the MOD EDIT after he had bricked his phone. There was no warning about not using that recovery prior to that. There was a long discussion about that in the thread.
Click to expand...
Click to collapse
Boom. Looks like you're right -- oh well. Sorry OP.
Same thing happened here
sbeekman said:
So yesterday I flashed the new aokp build 39 know all the risks of bricking but i thought my phone was immuned lmao no jk but i have been flashing for a few months now sometimes going back to el26 and sometimes i just flashed using ics recoveries wiped data and all and since i never bricked I thought it was safe, but yesterday i was not so lucky like i said i was on aokp 39 and wanted to go back to wicked so instead of going back to el26 i used the included cwm recovery and went to restore my backup and to stop this story from dragging on it restored but when it booted back up it would not go past samsung screen i cld get into recovery and odin mode tried sfhub one click same thing stuck at samsung logo everything i tried nothing worked brought it to sprint today I was honest told em i was rooted and explained i already tried to flash back to stock their guy said' "i'll be able to get it." Lol i said okay but I knew he could not he came bck said he couldnt i have tep and he ordered me a new one and i can get it tomorrow with no charge... Just an fyi u can get ur phone replaced for nothing even if u brick so i have my tablet to get me by til tomorrow so the cwm included in aokp 39 is not safe...
Sent from my K1 using xda premium
Click to expand...
Click to collapse
Don't feel too bad. I did something similar the other day and experienced a brick myself. I now have a new E4GT, free of charge. I made an elementary mistake, but I knew the risks.
I do not believe the new AOKP posted has a safe updater binary (since they did not say so) which makes it a bad deal to flash in ICS recovery still even a safe one.
Hate to hear this. But seriously OP. Thanks for actually owning up to it. When I bricked mine I did just like you. Sbrissen got me on Gtalk and apologized for bricking my device. I told him that I had not been aware that he had come to my house and flashed my phone for me. He said he hadn't and so I said then how is it your fault. I've seen so many times where someone bricks their phone and blames the dev. So props for being a stand up guy. Also. It is amazing what you can get with sprint reps when you just shoot straight with em isn't it. Glad you got it worked out.
Yea same here bricked mine and was titally my fault did it the same day I got the device and have no insurance really liked this device from the little I got to use it maybe one day I can afford another and nit be so stupid next time but least I know I'm not alone
sent from my Verizon Wireless HTC EVO 3D
@ruffneckZeVo,
First off no need to post the same thing in 3 threads. You'll get a reply.
Even though you didn't have insurance did you try taking it in to get it to Sprint for replacement? Samsung should also cover it but Sprint will probably be the easier solution if possible.
As for modified .PIT files we don't have one for the E4GT - it was quickly recommended not for long term use, so replacement has been the recommended solution. I don't believe anyone has been outright denied one yet - but I could be wrong.
Anybody without insurance that bricks there phone (b.l.o.d.) just go to an a.s.c. location (authorized service center) and tell them your phone won't turn on and you don't know why....you pay $35 and they order you a replacement that will be delivered next business day unless its back ordered. Then you have the option of adding T.E.P. going forward. They will also give you the option of a white or black device. (Unless the tech is a d.bag)
Sent from my SPH-D710 using xda premium
dafluke24 said:
I believe Jay added the MOD EDIT after he had bricked his phone. There was no warning about not using that recovery prior to that. There was a long discussion about that in the thread.
Click to expand...
Click to collapse
same... second brick too. Should've been more careful though.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
anti-up said:
Anybody without insurance that bricks there phone (b.l.o.d.) just go to an a.s.c. location (authorized service center) and tell them your phone won't turn on and you don't know why....you pay $35 and they order you a replacement that will be delivered next business day unless its back ordered. Then you have the option of adding T.E.P. going forward. They will also give you the option of a white or black device. (Unless the tech is a d.bag)
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Make sure you odin to a stock samsung rom(it will fail at data.img, so just unplug it there. This most hints that youre on a non stock rom such as the warning icon.) and then use a usb jig(~$20) This gets rid of all binary flashes in download mode.
That's if you can turn the phone on. Some can and some can't
garwynn said:
@ruffneckZeVo,
First off no need to post the same thing in 3 threads. You'll get a reply.
Even though you didn't have insurance did you try taking it in to get it to Sprint for replacement? Samsung should also cover it but Sprint will probably be the easier solution if possible.
As for modified .PIT files we don't have one for the E4GT - it was quickly recommended not for long term use, so replacement has been the recommended solution. I don't believe anyone has been outright denied one yet - but I could be wrong.
Click to expand...
Click to collapse
Sorry just anxious to get this fixed I had the device one day and really liked it its not on sprint I got it from cl and flashed to vzw so sprint isn't an option to fix it ill find another asc thanks for the info
sent from my Verizon Wireless HTC EVO 3D
For what it's worth....
I've had my SG2 E4GT since the middle of april. Rooted it about 3 days after having bought it. And have been using Blue Kuban's Rom ever since.
Sadly, for some dumb reason, I decided to try out the new AOKP build -.-
Ironically I think I bricked it trying to flash from Blue Kuban back into a Gingerbread EL29 build...... But it had Team Rogue's CWM 5.1.0 or 5.0.1 one of them -.-
Either way, after flashing AOKP went to reboot and black screen, only blue blinking LCD light of doom.
I've ordered a USB Jig so I can try to use that to reboot into recovery... but I'm prolly messed eh?
Should probably try going to the sprint store where I got it? I do have T.E.P.
anti-up said:
Anybody without insurance that bricks there phone (b.l.o.d.) just go to an a.s.c. location (authorized service center) and tell them your phone won't turn on and you don't know why....you pay $35 and they order you a replacement that will be delivered next business day unless its back ordered. Then you have the option of adding T.E.P. going forward. They will also give you the option of a white or black device. (Unless the tech is a d.bag)
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I did the same thing. I felt bad but well you know. Anyway it worked great, they even had it in stock.
I'm tired of my LG Cosmos 2, despite the requirement of a data plan I'm getting an Android Phone. Since this phone has many of the features I like, Especially the unlocked bootloader, I'm 98% going for a Galaxy Nexus on Verizon.
I'm not brand new to android, but I do have a few questions about this phone mainly because of the three variants (GSM,Sprint,Verizon)
1. Does the Verizon Version have a fully unlocked bootloader still? Is there any other carrier locking based crap that they've thrown in to limit people?
2. Is this an essentially 'unbrickable' phone, by unbrickable I mean that (Like my ASUS TF101 tablet for instance) there is a separate 'APX' or download mode that lets me reflash firmware on it's own. (Like ODIN or NvFlash)
3. How many kernels are out there and what are your personal favorites/stability on those, or should I stick with stock? (opinion)
4. What are some of my Recovery choices, such as TWRP or Rouge or CWM, is there a touch interface that also has volume buttons?
5. If anyone's running AOKP, it's my favorite ROM on my Transformer, how's the Stability on the Gnex?
Thanks,
ToD
Tl;DR: Does Verizon put any locks/limits/crap extra on the phone, is there Download/APX mode, and what are some Recovery/Rom/Kernel choices I have?
1) still unlocked
2) there's fastboot and odin.
3) depends on what you want in a kernel. make sure you pick one from the verizon section
4) TWRP and CWM are it i believe - both have touch versions
5) i run it and its quite fine.
Thing O Doom said:
I'm tired of my LG Cosmos 2, despite the requirement of a data plan I'm getting an Android Phone. Since this phone has many of the features I like, Especially the unlocked bootloader, I'm 98% going for a Galaxy Nexus on Verizon.
I'm not brand new to android, but I do have a few questions about this phone mainly because of the three variants (GSM,Sprint,Verizon)
1. Does the Verizon Version have a fully unlocked bootloader still? Is there any other carrier locking based crap that they've thrown in to limit people?
2. Is this an essentially 'unbrickable' phone, by unbrickable I mean that (Like my ASUS TF101 tablet for instance) there is a separate 'APX' or download mode that lets me reflash firmware on it's own. (Like ODIN or NvFlash)
3. How many kernels are out there and what are your personal favorites/stability on those, or should I stick with stock? (opinion)
4. What are some of my Recovery choices, such as TWRP or Rouge or CWM, is there a touch interface that also has volume buttons?
5. If anyone's running AOKP, it's my favorite ROM on my Transformer, how's the Stability on the Gnex?
Thanks,
ToD
Tl;DR: Does Verizon put any locks/limits/crap extra on the phone, is there Download/APX mode, and what are some Recovery/Rom/Kernel choices I have?
Click to expand...
Click to collapse
1: yes fully unlocked!
2: Yes with ODIN
3: a lot of kernels. My favorite kernel is Franco's kernel. Haven't had any problems with it and very smooth!
4: unsure about the available recoveries, but I use cwm touch.
5: AOKP is awesome. Very stable and great features.
There is a good poll in the gnex general discussion about roms and a good discussion on kernels. I don't have the links. Those helped me when I first started out though. you could search for them there.
Sent from my Galaxy Nexus using XDA
One thing to expect from Verizon's version is dropped calls and your mic going out on you. There is currently no fix and there may not be one. Since the S3 is coming out I think Verizon gave up on the issue. Anyone can go into a store and trade the phone across the table for something else.
Sent from my Galaxy Nexus using xda premium
Thank you for the responses (I'll be sure to hit the button when my cooldown refreshes )
I'm more of a texter than a talker, so the mic thing isn't terribly important, and I use a BT headset.
(If it's a Stock ROM problem, I'm going to be on the stock ROM for only about 15 mins when I root and put a Custom ROM on, The Transformer has made me despise and avoid stock... lol)
Thanks
How's the touch screen for texting?
Thing O Doom said:
Thank you for the responses (I'll be sure to hit the button when my cooldown refreshes )
I'm more of a texter than a talker, so the mic thing isn't terribly important, and I use a BT headset.
How's the touch screen for texting?
Click to expand...
Click to collapse
Great! The phone is the best and the S3 is barley better in the us. If you call put up with call issues you won't be dissatisfied in the least bit
Sent from my Galaxy Nexus
mark manning said:
One thing to expect from Verizon's version is dropped calls and your mic going out on you. There is currently no fix and there may not be one. Since the S3 is coming out I think Verizon gave up on the issue. Anyone can go into a store and trade the phone across the table for something else.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You sure about the in store thing? I honestly doubt it.
Sent from my tin can using a string.
SwiftKey 3 with the nexus screen response and size is great for texting! The mic I don't have any issues with. Call dropping occurs more than a previous Motorola, but I have been able to deal with it.
Sent from my Galaxy Nexus using XDA
Slacker101 said:
You sure about the in store thing? I honestly doubt it.
Sent from my tin can using a string.
Click to expand...
Click to collapse
That's what they told me. Idk about the S3 tho but the rep hinted at it
Sent from my Galaxy Nexus
After installing FoxHound ROM on Galaxy S3 i747, and it is absolutely dead now. Not even powers up. Please help. Cannot get to recovery or download either. Just black screen, no signs of life whatsoever.
thanks
michaelkagan said:
After installing FoxHound ROM on Galaxy S3 i747, and it is absolutely dead now. Not even powers up. Please help. Cannot get to recovery or download either. Just black screen, no signs of life whatsoever.
thanks
Click to expand...
Click to collapse
Can you provide a link to the ROM?
That's an i9300 ROM.
scorpion667 said:
That's an i9300 ROM.
Click to expand...
Click to collapse
That's what I thought. Sounds like a hard brick if you can't get to recovery or download mode. Search out mobiletechvideos they offer j-tag services and I have seen them recommended on here often.
The OP made a mistake and now needs help to fix it.
We are all here to help each other not make someone feel worse about themselves!
Let's respect and help each other
Thread cleaned
Thank you for your cooperation
Friendly Neighborhood Moderator
or you can send to samsung for warranty repair, thats what i had to do.
Just go to att service center and get a replacement. That's it. That's what I.did with my skyrocket
Sent from my SGH-I747 using Tapatalk 2
I heard you can pull battery and then attempt to get into download mode from there from a thread long ago.
Sent from my SAMSUNG-SGH-I747 using xda premium
Few days ago I just started installing ROMs for the first time on my rooted AT&T S3. Starting with CM10, then JellyBam, and so forth testing/trying out one at a time. I was clearing dalvik and wiping cache before and after installing each ROM. Each ROM worked fine until I finally reached the fourth or fifth ROM called Foxhound and that's when my phone when to crap. I went through the install and after it rebooted my screen went blank and never came back on. Unable to get into CWM or Download Mode, I did battery pull and also plugged via USB into my PC it still won't boot. I read that the USB jig works on the Galaxy S3, already ordered and waiting for it to come in. If that doesn't work then I'm gonna have to send it in for JTAG repair. I already read off another site that someone encountered the same issue and the USB jig didn't work (this is after I already ordered it) so I'm crossing my fingers.
And this is all because of Samsung Allshare Play isn't compatible with CM10 because it works off touchwiz. So I was looking for a touchwiz based ROM and heard about Foxhound. Once I get my phone back up I'm going to try Jedi Invasion ROM as I heard some good reviews.
KryptonKal-El said:
Few days ago I just started installing ROMs for the first time on my rooted AT&T S3. Starting with CM10, then JellyBam, and so forth testing/trying out one at a time. I was clearing dalvik and wiping cache before and after installing each ROM. Each ROM worked fine until I finally reached the fourth or fifth ROM called Foxhound and that's when my phone when to crap. I went through the install and after it rebooted my screen went blank and never came back on. Unable to get into CWM or Download Mode, I did battery pull and also plugged via USB into my PC it still won't boot. I read that the USB jig works on the Galaxy S3, already ordered and waiting for it to come in. If that doesn't work then I'm gonna have to send it in for JTAG repair. I already read off another site that someone encountered the same issue and the USB jig didn't work (this is after I already ordered it) so I'm crossing my fingers.
And this is all because of Samsung Allshare Play isn't compatible with CM10 because it works off touchwiz. So I was looking for a touchwiz based ROM and heard about Foxhound. Once I get my phone back up I'm going to try Jedi Invasion ROM as I heard some good reviews.
Click to expand...
Click to collapse
Foxhound is for the i9300 as stated above so JTAG is probably your only option! In the future double check to make sure the ROM you are flashing is for your device!
Sent from my SGH-I747 using xda app-developers app
Someone's your I download mode but phone looks off and screen black. Keep it hooked to Odin to check once it's connected.taken me two days before to fix a bricked phone two hundred trys with screen black but it worked once.
Sent from my SGH-I747 using xda premium
xxsicknessxx said:
Someone's your I download mode but phone looks off and screen black. Keep it hooked to Odin to check once it's connected.taken me two days before to fix a bricked phone two hundred trys with screen black but it worked once.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
sometimes, xxsicknessxx, i dont know wtf you're saying. its all good, though. cheers
xxsicknessxx said:
Someone's your I download mode but phone looks off and screen black. Keep it hooked to Odin to check once it's connected.taken me two days before to fix a bricked phone two hundred trys with screen black but it worked once.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Lmao I think I might understand. Sometimes even though the screen is black you can still do the button combo for download mode and it'll actually go into it even though you can't see that it went into download mode. Then plug in usb and hopefully Odin will recognize that you're in download mode and you'll be able to flash stock rom lol
Sent from my SGH-I747 using xda premium
xBeerdroiDx said:
sometimes, xxsicknessxx, i dont know wtf you're saying. its all good, though. cheers
Click to expand...
Click to collapse
I second that, can you repeat that please? Something about hundred tries...? Lol (seriously though)
---------- Post added at 01:22 PM ---------- Previous post was at 01:13 PM ----------
drock212 said:
Lmao I think I might understand. Sometimes even though the screen is black you can still do the button combo for download mode and it'll actually go into it even though you can't see that it went into download mode. Then plug in usb and hopefully Odin will recognize that you're in download mode and you'll be able to flash stock rom lol
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Correct me if I'm wrong, after the combo press to get into download mode, don't you have to press either Vol Up or Vol Dn to continue into download mode? If so which one?
KryptonKal-El said:
I second that, can you repeat that please? Something about hundred tries...? Lol (seriously though)
---------- Post added at 01:22 PM ---------- Previous post was at 01:13 PM ----------
Correct me if I'm wrong, after the combo press to get into download mode, don't you have to press either Vol Up or Vol Dn to continue into download mode? If so which one?
Click to expand...
Click to collapse
Up
Wilcox12 said:
Foxhound is for the i9300 as stated above so JTAG is probably your only option! In the future double check to make sure the ROM you are flashing is for your device!
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
*Update*
I received the USB Jig and it did not work. Will be sending it in for JTAG repair in a few days. I have also been thinking about taking the phone back to the AT&T store and give them a bs story about it just stop working all of a sudden and get it replaced since I'm still under the 1yr warranty. But then again I hate refurbished replacements so I'll might as well send it in for repair.............???
KryptonKal-El said:
*Update*
I received the USB Jig and it did not work. Will be sending it in for JTAG repair in a few days. I have also been thinking about taking the phone back to the AT&T store and give them a bs story about it just stop working all of a sudden and get it replaced since I'm still under the 1yr warranty. But then again I hate refurbished replacements so I'll might as well send it in for repair.............???
Click to expand...
Click to collapse
Search around on here for warranty replacements. I've read a few threads where people have hard bricked and returned to AT&T for warranty replacements. One thing to keep in mind tho, if they were to look into and see that it was because you were modifying your device, after a few weeks you would have a fat 600$ charge on your bill.. I'm not saying its out of the question. Just read a lot and see what other peoples results were first!
Sent from my SGH-I747 using xda app-developers app
Wilcox12 said:
Foxhound is for the i9300 as stated above so JTAG is probably your only option! In the future double check to make sure the ROM you are flashing is for your device!
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, not to make the OP feel bad ( I feel your pain, really) but this should be a warning to all new flashers (myself included).
The International uses a quad core processor, and the AT&T uses a dual core. Not even close to being the same hardware and flashing the wrong rom is an invitation for disaster. This is not the first instance of this I have read either.
I know there is a tendency to say peeps need to watch what they're doing, but a big warning label would be nice, since the S3 comes in 2 hardware flavors.
I hope you get this worked out with a jig. I have read you can rig one up yourself if you're handy, but I have not seen the instructions to do so.
If you can get back in, I can personally verify that this rom flashes back to stock unrooted. Be sure to clear your cache too.
Michael503 said:
a big warning label would be nice, since the S3 comes in 2 hardware flavors..
Click to expand...
Click to collapse
a big warning label (bigger than what they already post) is not necessary, nor is it the devs responsibility to baby-proof everything. if you find yourself hunting around the internet on 12 different sites, looking for rooting guides and roms for the S3, you're wrong. stick to one place, like xda. know your model number, make sure you're in the right forum, read over the kernel/rom page to ensure you're flashing the files meant for your device.
a "big warning label" would only be encouraging the large amount of spoon-feeding that so many (noobs and lazy peeps) on this forum already expect and somebody would still flash the wrong file like an idiot.
cheers
xBeerdroiDx said:
a big warning label (bigger than what they already post) is not necessary, nor is it the devs responsibility to baby-proof everything. if you find yourself hunting around the internet on 12 different sites, looking for rooting guides and roms for the S3, you're wrong. stick to one place, like xda. know your model number, make sure you're in the right forum, read over the kernel/rom page to ensure you're flashing the files meant for your device.
a "big warning label" would only be encouraging the large amount of spoon-feeding that so many (noobs and lazy peeps) on this forum already expect and somebody would still flash the wrong file like an idiot.
cheers
Click to expand...
Click to collapse
I see you joined back in November. How'd you get so wise so fast?
No, I agree that it not the devs responsibility to make sure no one makes a mistake, still, for a phone that comes with 2 different mainboards, it might be a courtesy, just in case the user has misplaced one of the half dozen or so tabs he/she has open in their browser after power surfing for an hour. The OP made a mistake. It happens. Calling him (or me) an idiot or lazy, is neither helpful, or polite.
cheers right back atcha!
Here are the circumstances. Was on Stock Deodexed and out of boredom wanted to try SlimNote2. Did a nandroid before flashing SlimNote2.
Flashed SlimNote2 only wiping Dalvik and Cache. Made sure the MD5 matched before doing so. The install was shaky...I had to reboot twice before the phone would finally boot to the main homescreen. At this point I had seen enough and decided to get back into TWRP to restore the nandroid I had just made. IDK WTF happened but a few seconds after the restore began it aborted. Not sure whether my hand swiped something it shouldn't of or what but it just abruptly aborted. Now I when I try to do a normal power up of the phone I'm just stuck at the main boot screen (black background with white letters: Samsung Galaxy Note 2)
I tried to boot up with volume up and volume down to get into either recovery or Download Mode but it's a no go on either.
I'm thinking my only choice is to bring this thing into Sprint and play dumb. Any suggestions or advice would be appreciated!
Assuming that you know about download mode, I'm guessing you know about Odin - but you're not able to get into download mode.
Have you tried pulling the battery for 2 minutes then reinstalling it and trying to get into download mode?
or
Have you tried pulling the battery, and hooking up the usb cable (from your computer) to your phone and again trying to get into download mode without the battery installed?
These were both tricks of "un-bricking" Sammy's Epic 4g (my current phone - hopefully soon to be replaced w/the note 2).
Hope either option gets you back on track!
altimuh said:
Assuming that you know about download mode, I'm guessing you know about Odin - but you're not able to get into download mode.
Have you tried pulling the battery for 2 minutes then reinstalling it and trying to get into download mode?
or
Have you tried pulling the battery, and hooking up the usb cable (from your computer) to your phone and again trying to get into download mode without the battery installed?
These were both tricks of "un-bricking" Sammy's Epic 4g (my current phone - hopefully soon to be replaced w/the note 2).
Hope either option gets you back on track!
Click to expand...
Click to collapse
thanks but both methods not working.
...same deal with trying to get into recovery?
If so, leave the battery off for longer, maybe 10mins.
The fact that you can get the splash screen up is a great sign, most true bricks are...true bricks (nothing happens).
---------- Post added at 07:10 PM ---------- Previous post was at 06:45 PM ----------
If you're still having issues, ou may want to check out this thread and PM the OP.
SantinoInc said:
Here are the circumstances. Was on Stock Deodexed and out of boredom wanted to try SlimNote2. Did a nandroid before flashing SlimNote2.
Flashed SlimNote2 only wiping Dalvik and Cache. Made sure the MD5 matched before doing so. The install was shaky...I had to reboot twice before the phone would finally boot to the main homescreen. At this point I had seen enough and decided to get back into TWRP to restore the nandroid I had just made. IDK WTF happened but a few seconds after the restore began it aborted. Not sure whether my hand swiped something it shouldn't of or what but it just abruptly aborted. Now I when I try to do a normal power up of the phone I'm just stuck at the main boot screen (black background with white letters: Samsung Galaxy Note 2)
I tried to boot up with volume up and volume down to get into either recovery or Download Mode but it's a no go on either.
I'm thinking my only choice is to bring this thing into Sprint and play dumb. Any suggestions or advice would be appreciated!
Click to expand...
Click to collapse
Are you holding down volume up or down + home key + power? I believe it is a 3 button press for stock roms to get into recovery or download mode...
Next1776 said:
Are you holding down volume up or down + home key + power? I believe it is a 3 button press for stock roms to get into recovery or download mode...
Click to expand...
Click to collapse
didn't realize it involved the Home key as well...unfortunately I may have jumped the gun with this.
Impulsively I took the phone to Sprint convinced that they would be unable to do anything with the phone. I was wrong. They apparently got the phone into Download mode and realized that there is a custom OS on there. They asked if I tampered with the phone and I said NO. They went on to say that if the phone is rooted my warranty will be voided. I think I may have made a big mistake by leaving my phone there <punches self in nutsack!>
Sooooooooo aggravated right now I can't even tell you guys!
SantinoInc said:
didn't realize it involved the Home key as well...unfortunately I may have jumped the gun with this.
Impulsively I took the phone to Sprint convinced that they would be unable to do anything with the phone. I was wrong. They apparently got the phone into Download mode and realized that there is a custom OS on there. They asked if I tampered with the phone and I said NO. They went on to say that if the phone is rooted my warranty will be voided. I think I may have made a big mistake by leaving my phone there <punches self in nutsack!>
Sooooooooo aggravated right now I can't even tell you guys!
Click to expand...
Click to collapse
Dang, you went from starting the thread all the way to dropping your phone off with sprint in a hour or two? You should still be fine. Theyll probably give you crap about it. Is your insurance through them?
Sent from my SPH-L900 using Tapatalk 2
SantinoInc said:
didn't realize it involved the Home key as well...unfortunately I may have jumped the gun with this.
Impulsively I took the phone to Sprint convinced that they would be unable to do anything with the phone. I was wrong. They apparently got the phone into Download mode and realized that there is a custom OS on there. They asked if I tampered with the phone and I said NO. They went on to say that if the phone is rooted my warranty will be voided. I think I may have made a big mistake by leaving my phone there <punches self in nutsack!>
Sooooooooo aggravated right now I can't even tell you guys!
Click to expand...
Click to collapse
sooooooooo, if they void your warranty, get your phone back and it is a 2 minute fix. you'll just be out a warranty and not a phone.
Yeah, I'm an impulsive jackass! So after one of you guys pointed out that I wasn't trying to access recovery/download mode properly I sprinted back to Sprint (bad pun intended.) Of course the store was closed already but the employees were still in there. Lucky for me one of them came over to the door and entertained me. I told the guy I just wanted my phone back and he said he couldn't service it because it had a custom ROM. Then he showed me my custom rom as he handed the phone back (it was in TWRP...dumb bastid don't know the difference between recovery and a rom :cyclops I was happy to the phone was in recovery.
Sure enough I went back home, threw in my SD card and just restored my last nandroid w/o a problem!
Wow, I feel like a real fool. I was so used to entering recovery/download mode with 2 buttons I totally forgot that this phone called for a 3 button method to enter recovery. I thank all you guys for the feedback!
SantinoInc said:
didn't realize it involved the Home key as well...unfortunately I may have jumped the gun with this.
Impulsively I took the phone to Sprint convinced that they would be unable to do anything with the phone. I was wrong. They apparently got the phone into Download mode and realized that there is a custom OS on there. They asked if I tampered with the phone and I said NO. They went on to say that if the phone is rooted my warranty will be voided. I think I may have made a big mistake by leaving my phone there <punches self in nutsack!>
Sooooooooo aggravated right now I can't even tell you guys!
Click to expand...
Click to collapse
Ya, just get your phone back, and it doesn't void their responsibility of trying to assist you in getting the phone operable again. Maybe void your warranty with Samsung. If it were me, I would rather try to revive the phone myself than let them try to load the stock rom on it. Just take what the6 say with a grain of salt, some of these techs want to try to make you think you've committed a felony by opening the OPEN android os...
Believe me, I know, I own a Service Center. I always enjoy the modders that come in and talk about what is working , not working etc. Or when they try to say they didn't do anything to their device, knowing we know, then they find out we are " pro modding" and its a good experience for everyone. We find it a challenge to unbrick bad flashes and mistakes. ..
Good luck with it, pm me if you need help with an exchange, etc.
SantinoInc said:
Yeah, I'm an impulsive jackass! So after one of you guys pointed out that I wasn't trying to access recovery/download mode properly I sprinted back to Sprint (bad pun intended.) Of course the store was closed already but the employees were still in there. Lucky for me one of them came over to the door and entertained me. I told the guy I just wanted my phone back and he said he couldn't service it because it had a custom ROM. Then he showed me my custom rom as he handed the phone back (it was in TWRP...dumb bastid don't know the difference between recovery and a rom :cyclops I was happy to the phone was in recovery.
Sure enough I went back home, threw in my SD card and just restored my last nandroid w/o a problem!
Wow, I feel like a real fool. I was so used to entering recovery/download mode with 2 buttons I totally forgot that this phone called for a 3 button method to enter recovery. I thank all you guys for the feedback!
Click to expand...
Click to collapse
Good for you! Im glad it all worked out.
Sent from my SPH-L900 using Tapatalk 2
Next1776 said:
Ya, just get your phone back, and it doesn't void their responsibility of trying to assist you in getting the phone operable again. Maybe void your warranty with Samsung. If it were me, I would rather try to revive the phone myself than let them try to load the stock rom on it. Just take what the6 say with a grain of salt, some of these techs want to try to make you think you've committed a felony by opening the OPEN android os...
Believe me, I know, I own a Service Center. I always enjoy the modders that come in and talk about what is working , not working etc. Or when they try to say they didn't do anything to their device, knowing we know, then they find out we are " pro modding" and its a good experience for everyone. We find it a challenge to unbrick bad flashes and mistakes. ..
Good luck with it, pm me if you need help with an exchange, etc.
Click to expand...
Click to collapse
Thanks for pointing out my mistake bro...had I just waited long enough to get some feedback on this thread I wouldn't have had need to go into Sprint at all...alas, I'm an impatient fool. Lucky for me it all worked out in the end.
SantinoInc said:
Thanks for pointing out my mistake bro...had I just waited long enough to get some feedback on this thread I wouldn't have had need to go into Sprint at all...alas, I'm an impatient fool. Lucky for me it all worked out in the end.
Click to expand...
Click to collapse
Hey no problem, I've been there myself, asking wtf is wrong, great, I bricked it ! Then ding ding... oh ya, it was THAT. Sometimes I am working on several different devices , roms, and mods within minutes of each other, swapping back and forth -off odin with one, flashing into recovery on the next, moving a rom to an sd card on another. ... and each device having its own quirks, its easy to forget the little things. Glad you got up and running again. At least the store let you get your phone back after close. Its always fun to look up after close and see a customer standing there rattling the door- never know what your going to get, lol.
Haha at this thread.. Entertaining to read.. I swear I hate dealing with a print reps and hearing their ignorant thoughts about rooting.. One lady said I better not root my phone or we won't deal with it.. I'm like she doesn't know about triangle away and stock tars lmao
-TeaM VeNuM Like A Boss
-Galaxy Note II Edition
MiguelHogue said:
Haha at this thread.. Entertaining to read.. I swear I hate dealing with a print reps and hearing their ignorant thoughts about rooting.. One lady said I better not root my phone or we won't deal with it.. I'm like she doesn't know about triangle away and stock tars lmao
-TeaM VeNuM Like A Boss
-Galaxy Note II Edition
Click to expand...
Click to collapse
Not all sprint reps are ignorant to rooting. I'm a store manager and I never keep a stock phone, first chance I get I root my phone and load a rom.
Sent from my SPH-L900 using xda app-developers app
RPAK46 said:
Not all sprint reps are ignorant to rooting. I'm a store manager and I never keep a stock phone, first chance I get I root my phone and load a rom.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Wish I would have ran into someone like you then...maybe I would have been cut some slack.
SantinoInc said:
Wish I would have ran into someone like you then...maybe I would have been cut some slack.
Click to expand...
Click to collapse
thats what throws me off....rooted phones are covered by tep...seems some stores still refuse help though.
Sent from my SPH-L900 using xda app-developers app
00mred00 said:
thats what throws me off....rooted phones are covered by tep...seems some stores still refuse help though.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
You are exactly correct. Rooted devices are covered, I verified the M&P documents myself this morning.
00mred00 said:
thats what throws me off....rooted phones are covered by tep...seems some stores still refuse help though.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
That's what I'm saying.. I've damn near had some stores refuse help just due to me having a third party launcher
-TeaM VeNuM Like A Boss
-Galaxy Note II Edition
MiguelHogue said:
That's what I'm saying.. I've damn near had some stores refuse help just due to me having a third party launcher
-TeaM VeNuM Like A Boss
-Galaxy Note II Edition
Click to expand...
Click to collapse
i get that question from my techs alot...he is this rooted ....i am like no...that's go launcher lol
Sent from my SPH-L900 using xda app-developers app
Ok so a little after midnight i rebooted my phone cuz it was being flaky.
Then it got stuck on the Cyanogen SGS boot screen from PAC 20.1 I tryed to ODIN cwm-5.0.2.7-epic4g.tar.md5. I got that to stick but every time i would flash a rom it would get stuck and end up and the samsung boot screen again. i tryed to flach cm9.1 and it hang at the BLM MTD part for a very long long time. then it went to the gray screen(the backgound of cwm 6) so that didn't work. So i tryed to ODIN stock EL30 EC05 just like hear http://forum.xda-developers.com/showthread.php?t=1052813
Well that ended with the phone booting up after about 40 minues. But i could not unlock the dam thing. So i did it again & left it for an hour & now its just siting there 12:19 on the clock but i cant unlock the phone. the sprint 4G boot aniy was/is all chopy and the sound cuts in and out. IDK i think my Epic is Epicing F(ced
(i'v been ODINing & reading xda all night:crying: )
Any ideas?
How about just going back to 100% stock FC09? Use re-partition, and you may even want to consider EFS clear (unless not on Sprint). Try that and let it run on that for a day. Note any issues that appear.
If no issues, then try to flash another rom.
Worst case scenario, your flash memory is on it's last leg and heading to become kaput. Flash memory only has so many reads & writes before it kicks the bucket. Constant flashing of roms over the lifetime of this phone diminishes the lifespan faster than a regular user.
A regular user wouldn't even come close to the read/write red zone for this flash memory, but a custom rom user/tester could (especially given the age of our phone).
Which is precisely why I find a somewhat stable ROM and stick with it for about 3 months, then i update/switch ROMs
Sent from my SPH-D700 using Tapatalk 2
I typically only flash stable roms and stick with one for 4-8 months before doing a fresh Odin, re-root and new rom flash. I'm your normal user here; I stick with what I know works.
jeffreyjicha said:
Which is precisely why I find a somewhat stable ROM and stick with it for about 3 months, then i update/switch ROMs
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Yes that kinda what i have done.
@nikon120 i tryed FC09 100% stock. i didn't try clearing EFS & yes i'm still on Sprint.
IDK i'm guna call sprint and see what they will give me to keep me?
zman519 said:
IDK i'm guna call sprint and see what they will give me to keep me?
Click to expand...
Click to collapse
A big ole nothing. I've tried to get discounts and upgrade fees waived before, and they have given nothing. I'm a 10+ year customer.
Once a nicer than Nexus 4--Nexus device comes out, or if Sprint's suck-tacular service becomes even more sucky, I'm jumping to T-mobile.
nikon120 said:
A big ole nothing. I've tried to get discounts and upgrade fees waived before, and they have given nothing. I'm a 10+ year customer.
Once a nicer than Nexus 4--Nexus device comes out, or if Sprint's suck-tacular service becomes even more sucky, I'm jumping to T-mobile.
Click to expand...
Click to collapse
SGS III Purple for $0.99 FTW
I really loved my Epic & i'l be back around the forums, my buddy has a busted Epic so maybe i can make one working phone out of the two.:good:
zman I have the EXACT problem with my Epic 4g, it's brand new I have only had it a handful of days and I haven't a clue as to what caused this error, my clock also reads 12:19 and the screen is unresponsive, so I can't slide unlock the screen to get usb debugging checked either. I am by no means new to android, flashing roms or anything else so this wasn't some noob error on my part.
I have messaged QBKing77 and he is as perplexed as I am, and well I figure if he can't figure it out, we might just be screwed.
Did you get yours fixed? If so could you please share what you did.
If i get it fixed I'll be sure to let you all know how i did it.
I have been playing with my new Purpal SGS III
Sent from my SPH-L710 using xda app-developers app
nerdygadgetguy said:
zman I have the EXACT problem with my Epic 4g, it's brand new I have only had it a handful of days and I haven't a clue as to what caused this error, my clock also reads 12:19 and the screen is unresponsive, so I can't slide unlock the screen to get usb debugging checked either. I am by no means new to android, flashing roms or anything else so this wasn't some noob error on my part.
I have messaged QBKing77 and he is as perplexed as I am, and well I figure if he can't figure it out, we might just be screwed.
Did you get yours fixed? If so could you please share what you did.
Click to expand...
Click to collapse
Did you ever get your Epic back to life?
Sent from my SPH-L710 using xda app-developers app
Nope. I had it fixed then it went back to the same old issue. I've tried every version of odin, Heimdall and using every possible pit, .tar and md5 file combination I can come up with and I cannot remember what I used the first time to fix it. blah
Did you get yours fixed or figure out what the problem was? If I ca
zman519 said:
Did you ever get your Epic back to life?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse