ICS update from sprint STUCK IN BOOTLOOP! - Samsung Epic 4G Touch

This is amazing, I just got a replacement ET4G from sprint. I was hesitant to flash anything, cuz my last one bricked, blue light, completley dead. So I was waiting for something to tickle my fancy IE a stable JB rom, or maybe just boredom. I woke up this morning, and low and behold... the update was waiting for me. Already downloaded, just waitin for me to install. I knew at some point Id be flashing a rom, so I almost didnt take it, but then I decided, well this way Ill have the newwest modem, bla, bla, bla. So I applied the update, and boom... stuck in a bootloop. HAHA! Anyway, does anyone where it downloads the update? I think is on the root of my sd card, but theres nothing with todays date on there. I found a file from 7-20 called update.zip, but Im worried that was from my old ET4g... Im scared to flash it again, cuz what if Im wrong???? Is it safe to do a factory reset in recovery? Or am I at risk to get hit with the EMMC bug???

Can you get into odin/download mode?
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT

vinscuzzy said:
This is amazing, I just got a replacement ET4G from sprint. I was hesitant to flash anything, cuz my last one bricked, blue light, completley dead. So I was waiting for something to tickle my fancy IE a stable JB rom, or maybe just boredom. I woke up this morning, and low and behold... the update was waiting for me. Already downloaded, just waitin for me to install. I knew at some point Id be flashing a rom, so I almost didnt take it, but then I decided, well this way Ill have the newwest modem, bla, bla, bla. So I applied the update, and boom... stuck in a bootloop. HAHA! Anyway, does anyone where it downloads the update? I think is on the root of my sd card, but theres nothing with todays date on there. I found a file from 7-20 called update.zip, but Im worried that was from my old ET4g... Im scared to flash it again, cuz what if Im wrong???? Is it safe to do a factory reset in recovery? Or am I at risk to get hit with the EMMC bug???
Click to expand...
Click to collapse
The latest update goes into /cache internally. (It's been pulled out in the last few weeks to look for changes) But it should be gone once applied.
As far as the brick issue - sfhub says the risk is still there. Personally, I have done a reset and not bricked. Others have reset with no brick.
I'd take sniper's suggestion on getting to download mode and using a one click.

MoHoGalore said:
The latest update goes into /cache internally. (It's been pulled out in the last few weeks to look for changes) But it should be gone once applied.
As far as the brick issue - sfhub says the risk is still there. Personally, I have done a reset and not bricked. Others have reset with no brick.
I'd take sniper's suggestion on getting to download mode and using a one click.
Click to expand...
Click to collapse
Yeah, i wasnt around a computer b4, but i got to one and one clicked ff18. Funny though, i actually(for the 1st time ever) took a major os update, and it fails. Good job Sprint! Oh well, at least xda is here to help.

Related

HTC EVO stuck in BAD boot loop.. need HELP

I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Drake13 said:
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Click to expand...
Click to collapse
sorry but you're pretty much S O L on this, has something to do with a bad boot.img and you can't get it to take another one might as well file a lost phone claim and pay the $100 and get a new one thats what i had to do and they just happened to have sent me the 3d instead so i guess i got a bit lucky.
i still have my evo 4g and still working on it but its been about a month and i haven't had any luck with it.
Sounds like you have no recovery or not completely rooted. You could try to put a recovery CWM or Amon-Ra file renamed PC36IMG.zip onto your sd card from your computer, put card back into phone then go in to hboot see if it will flash you a recovery then try to go into it
If that doesn't work search for a stock ruu file for the Evo, rename PC36IMG.zip, place on your card, put card back in phone, flash through hboot. This will return your phone to stock unrooted, then you try the process again
Sent from my PC36100 using XDA Premium App
That's what happened to my phone also..It just happened out of nowhere..
I tried everything and in the end I had to file an insurance claim.
And once again, a phone running CM7 goes into this mysterious unfixable bootloop.
What is up with that?
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
HipKat said:
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
Click to expand...
Click to collapse
Most of those phones from the 'CM Scare" had bad nand blocks, and it had to be replaced. They had them frothe very beginning, but just decided to act up then. It also happen to some users using MIUI.
Okay my speaker got distorted so I decided to unrooted to take it in for service. Now the phone is unrooted but theres only one problem! Now the phone will boot up to the normal home screen but within 2 to five minutes, it shuts itself down and boot back up to home screen again and the cycle starts again. I have reset few times but same ting' happens. Now sprint is ordering a new phone for me hope its not the 3D i don't think I like it. So now I have my evo still but will give it to sprint once my new phone is in at the sprint store tuesday! Oh by the way, beside the speaker problem the phone was working fine as normal before the unrooting. thx
teh roxxorz said:
t also happen to some users using MIUI.
Click to expand...
Click to collapse
No! Don't say that!!
tony_2018 said:
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
Click to expand...
Click to collapse
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Concordium said:
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Click to expand...
Click to collapse
No one ever said every install of CM7 will lead to this bootloop, but almost every case of this bootloop, the user was running CM7
HipKat said:
No! Don't say that!!
Click to expand...
Click to collapse
Miui is based of cm's fixes and what not right?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
No, MIUI is not based on CM. It's a completely different ROM
Yeah but I'm pretty sure they use their fixes since its a port
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
It's true that most of the cases happened on CM7, but from what I understand it can happen on any rom... and has happened on Sense and AOSP.
There's no known fix. You can try to RUU, but even if the RUU flashes properly, the phone will never boot. You're eternally stuck with hboot/fastboot. File an insurance claim, that's about all you can do. I had a similar problem with a stock, never-been-rooted Evo. I got a replacement through insurance without paying the deductible, but I was s-on.
Hopefully I don't get slammed for suggesting this, but if you don't want to pay the deductible for a "lost" phone, you can flash a radio through hboot and pull the battery. If you do it at the right time, the phone will completely brick and never turn on again. It may take a few tries. Then you can take it in and you shouldn't have to pay the deductible, as long as you play dumb of course.
I think this happens due to bad nand blocks on your boot partition, so the main cause is hardware. Something in the rom triggers the never-ending splashscreen bootloop (I'm assuming something related to the boot.img). I could be entirely wrong about this though.
You can't live in fear, if it happens it happens. It's one of the risks you take when rooting and flashing. The number of cases is small compared to the number of people with rooted Evos, especially considering only a portion of people are active on this site, and a lot of the reports come from members that wouldn't post or even be a member if they didn't have the problem. I wouldn't let the possibility deter you from running whatever rom you want.
Sent from my Evo + MIUI using Tapatalk!
I myself am stuck with same issue. Nothing takes. So where does hboot reside when loaded? I also have looked in vain for diagnostic flashes....
Now one thing I noticed is that I installed PDAnet and it shows it installed an app to the phone, however I cant connect. I think cause I cant boot the phone and enable what it telling me to...so how is it this software can load an apk and I cant?
Overall, I am now however learning and it has become a hobby.
Theres an answer somewhere I would think. Thinking maybe its time to tear apart and look for jtag points....
I have had this happen to me a few times, I leave the RUU on the sd card and when this happens and do what bimmerman7 wrote on the first page. This has always worked for me when I get stuck in a bootloop when trying to access recovery.

My once bricked E4GT!

To be honest,
Once I got to the rogue et recovery I cried a little (because I actually got there.)
7 hours worth of beating sleep, numb legs from sitting down, afro being dry, and Samantha (samsung support person, cause I really was going to send my phone in..)
Two batteries *thank god!
Don't really, can't explain much. Just a load of reading of the "download shabby's/acs leaked fb17...." thread, xda search tool, google, and youtube.
I'm just glad, I found some way to enable recovery. No, 2 weeks without a phone, no going to the shipping retail location, no "not having my little cloud(white e4gt) in my hand." ....cheesy
I hear birds chirping outside, wow, and the sun is starting to come up.
Now I must figure out what I need to do next in recovery, then get out this desk chair (because my dsfgh...), and go to sleep!
XDA ROCKS!
Wut? You saying you brought your E4GT back from a brick?
Sent from my SPH-D710 using Tapatalk
How did that happen?
I'm guessing it wasn't a real brick as in blue light of death. Probably stuck in a boot loop or something.
Sent from my SPH-D710 using Tapatalk
What type of brick lol? A soft brick all you need to do is go into download mode and ODIN over some new firmware, forget recovery lol. Unless it was a super brick from flashing ICS recovery where you luckily have recovery... your still pretty screwed. But if it was just a bootloop, soft brick the fix is simple.
slick_rick said:
I'm guessing it wasn't a real brick as in blue light of death. Probably stuck in a boot loop or something.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
How do you fix from boot loop ( the yellow triangle )? I can get in recovery and odim but which ever rom I flash it will not boot up...only to the triangle. In the recovery mode it take very long time to format the data and setting.....waiting time is like one minute. Any help?
K.0.0.L. said:
How do you fix from boot loop ( the yellow triangle )? I can get in recovery and odim but which ever rom I flash it will not boot up...only to the triangle. In the recovery mode it take very long time to format the data and setting.....waiting time is like one minute. Any help?
Click to expand...
Click to collapse
...People lack so many details. What rom where you on when the phone last worked, what were you flashing when it screwed up. What is ODIN getting stuck on?
Your either easily fixable, really screwed or completely screwed. Welcome to the 3 possibilities. Without any details for all I know your on Gingerbread and did something retarded or you were flashing in Ice Cream Sandwich and screwed yourself not following directions.
RainMotorsports said:
...People lack so many details. What rom where you on when the phone last worked, what were you flashing when it screwed up. What is ODIN getting stuck on?
Your either easily fixable, really screwed or completely screwed. Welcome to the 3 possibilities. Without any details for all I know your on Gingerbread and did something retarded or you were flashing in Ice Cream Sandwich and screwed yourself not following directions.
Click to expand...
Click to collapse
I was on wicked sensation and flash to AOKP build 39....It never happen to me before but somehow this time it did. I use culklins format all and during the data format it get stuck for long time then I remove the battery and it just never able to go pass beyond that. Just couple hour ago I let it sit on that process and it finally format the data and system..I then flash the AOKP but it get stuck on the boot animation......so I decided to ordin to stock kernel EL26 and now same old thing again...unable to go beyond boot loop. My custom binary download is 11 counts...........I have order the USB jig from ebay to see if it can help to erase the counts, maybe that is the issue why not booting up
K.0.0.L. said:
I was on wicked sensation and flash to AOKP build 39....It never happen to me before but somehow this time it did. I use culklins format all and during the data format it get stuck for long time then I remove the battery and it just never able to go pass beyond that. Just couple hour ago I let it sit on that process and it finally format the data and system..I then flash the AOKP but it get stuck on the boot animation......so I decided to ordin to stock kernel EL26 and now same old thing again...unable to go beyond boot loop. My custom binary download is 11 counts...........I have order the USB jig from ebay to see if it can help to erase the counts, maybe that is the issue why not booting up
Click to expand...
Click to collapse
Wicked sensation is an ICS rom right? Did you flash AOKP 39 from ICS Recovery? The one thing you should not do? If the rom does not have a safe updater binary there is a high chance of super brick when flashing from even a safe ICS recovery, and even higher from the regular repacks. NEVER factory reset from any non safe ics recovery and never flash a zip in ICS recovery unless it is marked as safe to do so.
If when trying to ODIN stock firmware it gets stuck at Data.img then you really did it this time. From what I have heard there are 2 levels of the super brick. The kind where you can still get to download and recovery and the kind where you cant. Stuck on Data.img on the first kind is a bad sign.
As far as the triangle goes that comes up any time you odin an unsigned kernel etc like the el26 cwm one. It is just an indicator and should not be a part of your problem.
Flash any stock gb kernel it should remove the triangle! (ODIN)
I don't really know what's up right now...
The whole reason I'm in this mess is me changing settings when I first flashed AOKP 39. Like setting display, changing the wallpaper. Just going straight down the whole setting page.
I got to the DPI settings, changed it to something lower, 240 i think. Rebooted... Didn't like it, changed it back to the original, rebooted... the words and all were original but not the status bar, not the lock screen, not the navi bar.
It was super weird!
So I thought:
"...doing a factory reset would allow me to start fresh again. If that doesn't work, I can just start completely over(odin back to gb). that way I can install gapps(the arrangement of back and enter buttons confused me, causing me to restart)"
All of a sudden, phone didn't work. Can't really remember what happened at the time. If it went into boot loop or not. But it didn't go into the rom.
Somehow, I ending up doing stuff, since I just got it a week ago I really didn't know much, was just learning as I went. "new phone, new things to learn"
Anyways, ending up with "A" recovery, and I've always been able to get into ODIN.
recovery that works is: rogue_ET-recovery-1.2.2-FB27-rc0.tar
Now that I have some kind of recovery and odin I thought, maybe I could get back to stock. Just don't know how, thats were doing more searches came in. Still got NOTHING. lol.
I was aware of not flashing ics from an ics dadada messages. hint: i read stuff
I did a factory reset which caused all of this. Kinda know I shouldn't of done it now, ...never came across anything about not doing it at the time. I still haven't, I'll google that too.
Umm.. flashing stuff through pda doesn't work. to be more specific
when I look at the progress, it doesn't include data.img (so it PASS)
if I odin something and it says data.img, then its stuck there.
so that recovery I'm using: (volup+pwr)
bootscreen(samsung galaxy s II) -> quick led(blue) -> bootscreen(samsung galaxy s II) -> recovery
any other tries when getting into recovery WITHOUT odin rogue_ET-recovery-1.2.2-FB27-rc0.tar: (volup+pwr)
quick led(blue) -> bootscreen(samsung galaxy s II) -> quick led(blue) -> bootscreen(samsung galaxy s II) bootloop bootloop bootloop. Sometimes it will stay there for a few minutes then bootloop again.
-----
so right now, ....still trying to find a solution. I'm still on google and xda searching. I really don't want to do anything else because both batteries I think are nearly dead...
When I started flashing, I was on ParanoidAndroid, then I found AOKP 39. It worked, was awesome. But I did a factory reset from the settings within the rom and now Im typing this...
flashing in recovery, when trying to erase data(it doesn't work.) though cache and dalvik does.
AndroidRocksSocks said:
When I started flashing, I was on ParanoidAndroid, then I found AOKP 39. It worked, was awesome. But I did a factory reset from the settings within the rom and now Im typing this...
Click to expand...
Click to collapse
Suicide.
AndroidRocksSocks said:
flashing in recovery, when trying to erase data(it doesn't work.) though cache and dalvik does.
Click to expand...
Click to collapse
Because the /Data partition is borked.
RainMotorsports said:
Suicide.
Because the /Data partition is borked.
Click to expand...
Click to collapse
Right, had* to be something.
CPR?
If all you get is the blue led.... Its done. That's what I was seeing when I bricked my first e4gt. On AOKP it says in red all caps too, do not do anything with this kernal.. Probably not word for word, but unless its a safe recovery as stated, you can't do anything with it, not even wipes.
evo-t said:
If all you get is the blue led.... Its done. That's what I was seeing when I bricked my first e4gt. On AOKP it says in red all caps too, do not do anything with this kernal.. Probably not word for word, but unless its a safe recovery as stated, you can't do anything with it, not even wipes.
Click to expand...
Click to collapse
....lol he already said he is getting past that. Still the same issue though he is Super Bricked.
AndroidRocksSocks said:
Right, hand to be something.
CPR?
Click to expand...
Click to collapse
Your at the level where some people seemed to have been able to repartition the eMMC around the origina /Data area consuming space other partitions normally used. Its not considered stable.
There is no premenant fix that can be applied by you, a sprint store, or even jtag service. The Super Brick bug corruption occurs at the lowest possible level. You basically need Samsung to fix it, though just about anyone on the eMMC partner list technically can.
Phone replacement is the primary option or you can see about getting info about the repart here - http://forum.xda-developers.com/showthread.php?t=1644364
Great, ha-ha.
Well, I look into that repart info. If I can't handle it. All I have to do is print out the ups shipping label and send it in. So sad... anything I need to do when sending it in? As in, do I need to put it at some kind of "ok" state? Ugh, I hate this.
AndroidRocksSocks said:
Great, ha-ha.
Well, I look into that repart info. If I can't handle it. All I have to do is print out the ups shipping label and send it in. So sad... anything I need to do when sending it in? As in, do I need to put it at some kind of "ok" state? Ugh, I hate this.
Click to expand...
Click to collapse
I would see about odining over the stock EL29 kernel but the yellow triangle is still going to say hey look at me. If that USB jig arrives should be able to reset the counter.
If its via insurance it wont matter.
RainMotorsports said:
I would see about odining over the stock EL29 kernel but the yellow triangle is still going to say hey look at me. If that USB jig arrives should be able to reset the counter.
If its via insurance it wont matter.
Click to expand...
Click to collapse
Ya know, I was planning to go outside today...
This test thing looks alright though.
I guess I'll follow the steps and the following questions from others who have or are doing it.
AndroidRocksSocks said:
Ya know, I was planning to go outside today...
This test thing looks alright though.
I guess I'll follow the steps and the following questions from others who have or are doing it.
Click to expand...
Click to collapse
Which test? The AOKP 37/ CM9 Alpha 5 test? That was for people wanting to flash things without bricking their phone. I think you caught my link before i changed it to the original post.
RainMotorsports said:
Which test? The AOKP 37/ CM9 Alpha 5 test? That was for people wanting to flash things without bricking their phone. I think you caught my link before i changed it to the original post.
Click to expand...
Click to collapse
Oh wait a min...
Right, yea I did.
This one: Discussion thread for /data EMMC lockup/corruption bug

I read, I watched, I searched, I bricked(Hard)

So just got this phone a couple of weeks ago. I feel like Im no stranger to rooting/flashing, but obviously Im no expert. Ive flashed custom roms on ppc6600, ppc6700, Treo 600w, HTC Diamond, Palm Pre(rooted it, no roms), Samsung Moment, Hero, Evo 4g, Evo 3d, Hp touchpad, and for a few weeks my Epic Touch4g. Ive never had a single problem until today. I must admit when I got this phone, for the first time I was actually scared to root it/flash roms. I read and re-read everything I could find, and finally took the plunge. I had great luck until I tried to flash the jellybean port.
I was originally on Agats rom tFF18_v0.1.0 which I flashed through ODIN. I tried a few other TW roms but ultimately kept Agats rom as my nandroid back up. Since it was a safe kernel/recovery I would always restore my nandroid to do any wipes or flashes. I thought this was being safe.
This morning I updated the kernel with AGAT_v0.3.0 with tREC_v0.2.1 7/19/12, which I flashed through agats recovery. Worked fine. I then wanted to try out CM9. So heres what I did:
I downloaded/flashed the newest nightly and Gapps and flashed them in Agats recovery which worked fine. I loved CM9 so I made a nandroid back up along with my other agat rom backup. I did notice that it was a different recovery but just assumed it was safe since it was a newer nightly. (Mistake?)
I kept CM9 for a few hours and saw that a JB port was available on androidcentral. Had flashed enough without issue, so I thought I try it out.
Heres where I screwed up.
I downloaded the JB port, JB gapps and it said to get chris41g's [Kernel][AOSP] Safe CWM6/TWRP which I did.
First I wiped data(full wipe), cache, and dalvik, then tried to flash the rom in CMW recovery that came with CM9. It gave me an error and aborted the flash.
Then I rebooted the phone back into CM9 because I thought maybe I had a bad download. I went back to the site reread the OP and noticed I was supposed to flash chris41g's recovery first, so I went back into recovery, flashed the Kernel, rebooted back into recovery and tried to flash JB. I didnt wipe anything, I just flashed it. It seemed to do its normal thing, but the progress bar never grew, it just sat there. I let it sit for like 10mins and the next thing I noticed, the screen was off. I picked up the phone, hit the power button.....nothing except the blue light I had read so much about.
I accept full responsibility for what I did. But to be honest, Im really confused what I did wrong. I was under the impression that most bricks happened when doing wipes? This happened when flashing the rom, which Im sure wipes before flashing, so maybe that where I had the problem? Im gonna go to sprint tomorrow and see if they can help, so hopefully Ill get a replacement, but I DONT want it to happen again. Sorry for the MAJORLY long post, but I wanted to be thorough with my explanation so I dont make the same mistake, and maybe someone else could learn from my screw up.
If possible, please be gentle, I already feel like a total idiot.......
EDIT: BTW, if I didnt make it clear, Im COMPLETELY aware this was my fault. I knew what I was getting into, and messed up somewhere by not FOLLOWING directions to a tee.
Your mistake was not wiping anything at the jb flash part.
Plus i think people was flashing jb using the el26 recovery (cwm5) but dont quote me on that i havent read the jb flash procedure throughly
Sent from my SPH-D710 using xda app-developers app
Sometimes stuff like that just happens... Let us know how the replacement goes
Sent from my SGH-I897 using Tapatalk 2
I read somewhere they wont release the jb post on here because of all the bricks that was going on. Tell sprint u prolonged the ics update and ignored it. Then u finally decided to install and it would not boot at all
Sent from my SPH-D710 using xda app-developers app
rovar said:
Your mistake was not wiping anything at the jb flash part.
Plus i think people was flashing jb using the el26 recovery (cwm5) but dont quote me on that i havent read the jb flash procedure throughly
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yeah I thought people were using Chris41g's EL26 CWM as well. Sbrissen himself said when in doubt use EL.
Thanks for the responses guys. My phone now has no solid blue light. Just a VERY VERY dim flashing blue light. Its been plugged in for the charger for like 2 hours. Is it possible maybe something just went wrong with battery? It was plugged in when I flashed, and the battery was pretty full, but not topped off...
vinscuzzy said:
So just got this phone a couple of weeks ago. I feel like Im no stranger to rooting/flashing, but obviously Im no expert. Ive flashed custom roms on ppc6600, ppc6700, Treo 600w, HTC Diamond, Palm Pre(rooted it, no roms), Samsung Moment, Hero, Evo 4g, Evo 3d, Hp touchpad, and for a few weeks my Epic Touch4g. Ive never had a single problem until today. I must admit when I got this phone, for the first time I was actually scared to root it/flash roms. I read and re-read everything I could find, and finally took the plunge. I had great luck until I tried to flash the jellybean port.
I was originally on Agats rom tFF18_v0.1.0 which I flashed through ODIN. I tried a few other TW roms but ultimately kept Agats rom as my nandroid back up. Since it was a safe kernel/recovery I would always restore my nandroid to do any wipes or flashes. I thought this was being safe.
This morning I updated the kernel with AGAT_v0.3.0 with tREC_v0.2.1 7/19/12, which I flashed through agats recovery. Worked fine. I then wanted to try out CM9. So heres what I did:
I downloaded/flashed the newest nightly and Gapps and flashed them in Agats recovery which worked fine. I loved CM9 so I made a nandroid back up along with my other agat rom backup. I did notice that it was a different recovery but just assumed it was safe since it was a newer nightly. (Mistake?)
I kept CM9 for a few hours and saw that a JB port was available on androidcentral. Had flashed enough without issue, so I thought I try it out.
Heres where I screwed up.
I downloaded the JB port, JB gapps and it said to get chris41g's [Kernel][AOSP] Safe CWM6/TWRP which I did.
First I wiped data(full wipe), cache, and dalvik, then tried to flash the rom in CMW recovery that came with CM9. It gave me an error and aborted the flash.
Then I rebooted the phone back into CM9 because I thought maybe I had a bad download. I went back to the site reread the OP and noticed I was supposed to flash chris41g's recovery first, so I went back into recovery, flashed the Kernel, rebooted back into recovery and tried to flash JB. I didnt wipe anything, I just flashed it. It seemed to do its normal thing, but the progress bar never grew, it just sat there. I let it sit for like 10mins and the next thing I noticed, the screen was off. I picked up the phone, hit the power button.....nothing except the blue light I had read so much about.
I accept full responsibility for what I did. But to be honest, Im really confused what I did wrong. I was under the impression that most bricks happened when doing wipes? This happened when flashing the rom, which Im sure wipes before flashing, so maybe that where I had the problem? Im gonna go to sprint tomorrow and see if they can help, so hopefully Ill get a replacement, but I DONT want it to happen again. Sorry for the MAJORLY long post, but I wanted to be thorough with my explanation so I dont make the same mistake, and maybe someone else could learn from my screw up.
If possible, please be gentle, I already feel like a total idiot.......
Click to expand...
Click to collapse
I like story's like this that are long very interesting when bored I'm sorry for your lost...try simple small stuff like the stable good looking fully working roms
sent from my DeRpY SuPeRsOnIc
vinscuzzy said:
Thanks for the responses guys. My phone now has no solid blue light. Just a VERY VERY dim flashing blue light. Its been plugged in for the charger for like 2 hours. Is it possible maybe something just went wrong with battery? It was plugged in when I flashed, and the battery was pretty full, but not topped off...
Click to expand...
Click to collapse
Seems unlikely to be the battery, sorry bud :/ seems like your issue was not wiping anything before flashing the jb rom. Not to mention the jelly bean port is unstable as is. And the ics recoveries. I don't care if people say they're safe, i still odin to el26 to flash. I would've stayed away from jb regardless. But thanks for being mature about what happened, you more than most bricks actually seem like you're careful and read.
Swyped from a Galaxy S2
vinscuzzy said:
So just got this phone a couple of weeks ago. I feel like Im no stranger to rooting/flashing, but obviously Im no expert. Ive flashed custom roms on ppc6600, ppc6700, Treo 600w, HTC Diamond, Palm Pre(rooted it, no roms), Samsung Moment, Hero, Evo 4g, Evo 3d, Hp touchpad, and for a few weeks my Epic Touch4g. Ive never had a single problem until today. I must admit when I got this phone, for the first time I was actually scared to root it/flash roms. I read and re-read everything I could find, and finally took the plunge. I had great luck until I tried to flash the jellybean port.
I was originally on Agats rom tFF18_v0.1.0 which I flashed through ODIN. I tried a few other TW roms but ultimately kept Agats rom as my nandroid back up. Since it was a safe kernel/recovery I would always restore my nandroid to do any wipes or flashes. I thought this was being safe.
This morning I updated the kernel with AGAT_v0.3.0 with tREC_v0.2.1 7/19/12, which I flashed through agats recovery. Worked fine. I then wanted to try out CM9. So heres what I did:
I downloaded/flashed the newest nightly and Gapps and flashed them in Agats recovery which worked fine. I loved CM9 so I made a nandroid back up along with my other agat rom backup. I did notice that it was a different recovery but just assumed it was safe since it was a newer nightly. (Mistake?)
I kept CM9 for a few hours and saw that a JB port was available on androidcentral. Had flashed enough without issue, so I thought I try it out.
Heres where I screwed up.
I downloaded the JB port, JB gapps and it said to get chris41g's [Kernel][AOSP] Safe CWM6/TWRP which I did.
First I wiped data(full wipe), cache, and dalvik, then tried to flash the rom in CMW recovery that came with CM9. It gave me an error and aborted the flash.
Then I rebooted the phone back into CM9 because I thought maybe I had a bad download. I went back to the site reread the OP and noticed I was supposed to flash chris41g's recovery first, so I went back into recovery, flashed the Kernel, rebooted back into recovery and tried to flash JB. I didnt wipe anything, I just flashed it. It seemed to do its normal thing, but the progress bar never grew, it just sat there. I let it sit for like 10mins and the next thing I noticed, the screen was off. I picked up the phone, hit the power button.....nothing except the blue light I had read so much about.
I accept full responsibility for what I did. But to be honest, Im really confused what I did wrong. I was under the impression that most bricks happened when doing wipes? This happened when flashing the rom, which Im sure wipes before flashing, so maybe that where I had the problem? Im gonna go to sprint tomorrow and see if they can help, so hopefully Ill get a replacement, but I DONT want it to happen again. Sorry for the MAJORLY long post, but I wanted to be thorough with my explanation so I dont make the same mistake, and maybe someone else could learn from my screw up.
If possible, please be gentle, I already feel like a total idiot.......
EDIT: BTW, if I didnt make it clear, Im COMPLETELY aware this was my fault. I knew what I was getting into, and messed up somewhere by not FOLLOWING directions to a tee.
Click to expand...
Click to collapse
Where did you have the JB ROM located, on your internal memory or your SDcard?
And wait, Flashing blue light? When mine bricked using the same methods you were using, save for the lack of wiping and I used calk's wipeall before flashing, I had a solid blue light.
Eh, Least now I have a paperweight with a nice light on it for now.
Ophois said:
Where did you have the JB ROM located, on your internal memory or your SDcard?
And wait, Flashing blue light? When mine bricked using the same methods you were using, save for the lack of wiping and I used calk's wipeall before flashing, I had a solid blue light.
Eh, Least now I have a paperweight with a nice light on it for now.
Click to expand...
Click to collapse
it was on the internal memory. And yeah, its weird. It started as a solid blue light for like an hour. I plugged in the charger and a few hours later I thought the light was completely off, but if you look real close, its a super dim flashing blue light.
vinscuzzy said:
it was on the internal memory. And yeah, its weird. It started as a solid blue light for like an hour. I plugged in the charger and a few hours later I thought the light was completely off, but if you look real close, its a super dim flashing blue light.
Click to expand...
Click to collapse
Alright, That's two people who got a brick and had flashed it from their internal.
I'll try and get ahold of the other user who bricked their device and find where they had it and from there, We'll know a probable cause and how to prevent it.
I flashed sb's jb from internal. no problem here.
on el26.
please not I am not trying to be a wise ass; however have you read through this post http://forum.xda-developers.com/showthread.php?t=1525495 ? I have "bricked" a few times and have been able to revive my phone using Odin (the pc version). seems as long as you can get the phone into "download" mode (volume rocker down and power button) be sure to check out QBKing77's posts on YouTube. you have nothing to lose and everything to gain
good luck
al_b said:
please not I am not trying to be a wise ass; however have you read through this post http://forum.xda-developers.com/showthread.php?t=1525495 ? I have "bricked" a few times and have been able to revive my phone using Odin (the pc version). seems as long as you can get the phone into "download" mode (volume rocker down and power button) be sure to check out QBKing77's posts on YouTube. you have nothing to lose and everything to gain
good luck
Click to expand...
Click to collapse
Yeah, that was the post that scared me to even root the phone. I can't get into download mode, and have been trying every combination of turning it on, vol up/dwn, plugging it in without the battery, tried different cables, chargers, scoured all the different Samsung forums to see if there was a way to force into download mode, nothing. Its completely dead. I got this phone right around the time the kernel source got released and that post hasn't been updated since may, so I kinda came to the conclusion(stupidly) that maybe the problem had been fixed. I wasn't around for all the leaks that were causing the bricks.
not being able to get into download mode = not good. there are also dongles out there that cost $5 +/-. might work. I believe you mentioned you have insurance, if that is true take the device to your local corporate Sprint store and play "Micky the dunce" i.e. I have no idea what happened to it; I was updating my PRL and this is what happened ... of course if you accidently backed over it with your car on the way to the store that may dissuade them from trying to resurrect it
vinscuzzy said:
Yeah, that was the post that scared me to even root the phone. I can't get into download mode, and have been trying every combination of turning it on, vol up/dwn, plugging it in without the battery, tried different cables, chargers, scoured all the different Samsung forums to see if there was a way to force into download mode, nothing. Its completely dead. I got this phone right around the time the kernel source got released and that post hasn't been updated since may, so I kinda came to the conclusion(stupidly) that maybe the problem had been fixed. I wasn't around for all the leaks that were causing the bricks.
Click to expand...
Click to collapse
the MMC_CAP_ERASE code that causes the emmc controller to bug out and brick is still present in the FF18 kernel, entropy512 has been in contact with samsung about this, but last time i read the emmc thread a a few days ago he was still having difficulty convincing samsung that it was actually their code directly causing all these bricks... sorry about the brick, I just spent some time with cm10 and the vanilla jb rom and thanks to you and the other gentleman that bricked flashing from internal sd I double checked that the zips were on the external... so at least you've helped some of us out! good luck with sprint
does DirectoryBind_0.2.0k.apk help with the EMMC freakiness? a month or so ago this was useful work around. http://forum.xda-developers.com/showthread.php?t=1410262&highlight=directorybind
gershee said:
I flashed sb's jb from internal. no problem here.
on el26.
Click to expand...
Click to collapse
That is the difference, The other two and I appear to have flashed it from internal but we were using CWM6.
I guess CWM6+Internal=brick whereas EL26+Internal=good to go
Though this is all conjecture, I cannot be completely sure with such a small sample size.
When I was little I once had a jelly bean stuck in my nose.
Good luck.
Pp.
Delivered to you via Mayan technology .
No worries happened to me too( sadly :/). On the lighter/much, much darker side[you choose] sprint reps. won't be able to look at your phones files probably. When it happened to me the tech just came out with the 'WTF?' face and said what did you do, to which I replied "I applied the EL29 update and my phone bricked" cheers.
Sent from my Galaxy S2 E4GT

Bad Flash Stories

Hi everybody!
I figure we should have a thread dedicated to telling horror stories about flashes gone wrong. Whether it's because of power failures, bad USB cables, poorly labeled packages, or pure user error, we've all had that moment of worry: "Did I just turn my device into a paperweight?"
It's my hope that, by sharing these stories, we can help each other realize that we're all human, we all make mistakes, and most mistakes can be recovered from. Don't be afraid to share your stories; we can't learn from each other's mistakes if nobody talks about them!
_____________________________________________
My first story is from my Telus SGS3 (I747M, you'll see why that matters in a moment) and is definitely a user-error kind of story.
I've been playing around with CM10 and its derivatives for the past month or two (got my SGS3 on release day and it wasn't running Samsung software 3 hours later) and I'm not new to Android, having run XDAndroid on my HTC Diamond, and bouncing between CM7 and CM9 on my Milestone. The first thing I did when I got my SGS3 was a full block device backup using DD from the command line, which is the only reason I don't have a paperweight today.
I decided to try out Paranoid Android over a week ago and I've been loving it, so I haven't been flashing much lately. But, when I got back from vacation and saw that CM10 had gone into nightly builds, I couldn't resist the temptation to try a clean install. I've got folders on my SD card for ROMs, GApps, kernels, recoveries, and anything else flashable just to make my life easier. Apparently at some point I downloaded an AT&T (I747, no M) modem, stuck it in a "/modems/" folder with the rest of my flashables, but realized that it wouldn't work on my device, so I never used it. I then promptly forgot that I had put it on the SD card, and it had a fairly cryptic filename. Away I went, flashing CM10, GApps, a nice bootscreen, and... the modem.
Dammit. :crying:
At this point, I was running the newest CM10 build, but with a borked modem. I thought I had fallen victim to the IMEI bug that's been going around, but then I remembered something about that modem file not being usable on a Telus device... And had no idea how to get back to a working state. I already knew that none of my nandroid backups would have the modem in them, and the only "stock" flashables I could find were rooted kernels and a nearly-700MB "stock" package that wouldn't download any faster than 10 kb/s. I couldn't wait 20 hours for a download, I wanted my phone now! I tried using Odin with a few of the TAR packages I found, but that only made my situation worse to the point of failing to boot entirely, even restoring a nandroid wasn't helping anymore.
I started digging through the forums in the hope that someone had ripped the Telus modem into a CWM flashable zip, but had no luck. I tried both the Rogers and Bell modems with the same results. That's when I remembered that I had done a block backup, but I had no idea which block device was the modem, and my phone wouldn't even boot up to let me MTP the files over. I was left with CWM recovery as my only option, and had to ADB push 2.5 GB of .img files to the SD card, and DD them one at a time through the ADB shell.
Somehow, it all worked out, and I was back to running Stock Touchwiz with root, and was then able to restore a nandroid from yesterday and amazingly enough Paranoid Android booted up, happy as ever, and in came my emails and text messages. I know I'm lucky that my IMEI didn't get lost in that mess, but it just goes to show that there's no such thing as a backup being "too extensive". You never know when "mmcblk0p99" needs to be replaced with a known working copy.
I do believe im going to flash a stock/rooted ROM and then do a dd backup.
What options do you set for your backups?
Sent from my SGH-I747M using xda premium
I did as follows:
Code:
cd /dev/block/
ls
(get the list of mmcblk devices from here)
dd if=/dev/block/mmcblk0p1 of=/sdcard/dd/blk0p1 bs=4096
...
dd if=/dev/block/mmcblk0p99 of=/sdcard/dd/blk0p99 bs=4096
Obviously you shouldn't have 99 partitions... but you get the idea. I ran each line manually.
Then just move the /dd/ folder off your /sdcard/ and onto some safe storage.
I bought my device off someone from Craigslist 2 nights ago. Went home with device working great. Decided to update from ICS to JB, downloaded everything on the ol gaming machine, go to update using Kies, then BAM! Hung update, bricks phone immediately. Woo....great experience after dropping $400 on phone lol. Contacted Samsung support who told me my update wouldn't work until I registered? I told him it bricked my phone and it wasn't being picked up by computer anymore and I wanted to go back to ICS, he apparently thought waiting 24 hours would fix driver issues. Found JB official rom and learned about Odin. Worked at it until 2-ish am, never worked, woke up, did ICS instead same method, worked immediately, then update worked.
Moral of story? Don't trust Samsung apparently, go with 3rd party everything....
Can we share from other devices? Because I've had a serious one with my nitro HD lol.
Sent from my SGH-I747 using xda premium
After having my phone on stock rooted touch wiz since day one I was tempted to go jellybean... So months later I'd say Octoberish I finally said f**k it I'm going aokp... So I ran the task and k toonsen romantic for a while until they started porting the t mobile jelly bean stock tw rom... It made me miss tw and it's awesome camera app... So I flashed it after a week or so upon its release... First thing I noticed was the phone would get txts and phone calls rarely (keep in mind I'm in an lte area) and it became un bare able after about an hour. So I reverted back to my aokp nandroid and just figured I'd call it a day... But when I restored my nandroid my service was still messed up.. So after a bit of gooogling I checked my phone status to find my imei to be 0!!! I was beyond upset... So I tried re flashing stock in Odin and everything else I could find (unfortunately the imei restorer wasn't existent yet) and it came to the point where I left it stock and went to the att repair center down the road... The guy didn't know what was wrong with it and I just played dumb... After about 30 mins he came to the conclusion that my sim card slot was broken and I got a new phone...
After getting this one back home I instantly rooted it again
I've been staying away from those ported tmobile roms ever since
Sent from my SAMSUNG-SGH-I747
[/COLOR]
rani9990 said:
Can we share from other devices? Because I've had a serious one with my nitro HD lol.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I dont see why not. All stories are interesting lol
Sent from my SAMSUNG-SGH-I747 using xda premium
No bad flashes .... Yet?
Sent from my Nexus 7 using xda app-developers app
Alright then,
It was my first day with the LG Nitro HD. My first smartphone (don't comment xD) and I was prepared to root and flash the living crap out of it. Done with rooting, now to install CWM. Simple enough, right? WRONG. This was the one time where google was not my friend. I followed a horribly misleading guide, and ended up with a paperweight. Turns out I flashed the recovery image to the secondary bootloader partition, thereby bricking my phone completely and utterly, irreparably. Had to ship it off to LG, and they fixed it, no questions asked. Thank God for that...
I had an HTC Touch Pro on Sprint. You had to flash a stock ROM before flashing a new custom ROM or the phone would stop working properly after almost exactly an hour. The file system would become completely messed up but the OS would keep running from RAM. It would fail to reboot after that. It was such a pain that I updated my phone every ~3-4 months.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
This one actually just happened this weekend.
So I finally got bored of having stock ICS on my i747 (Rogers), and since I loved cm 7/9 on my SGS2, I figured I'd go with the latest (15 dec) CM10 nightly.
downloaded to phone, rebooted in recovery, wiped data and cache, and installed the new firmware.
booted up and I've got no (or inconsistant) cell service. Figure it's a bug that hasn't been fixed, so no biggie, I backed up a week ago, so I decided to revert back to stock for the time being.
go through the process, and discover I still only have EDGE data.... WTF?
So I do some reading *AFTER the fact, hur dur...* and discover the IMEI wipe issue, and surprise surprise, I didn't do an NV backup, since I didn't know it'd get wiped.
Spent a couple hours keeping the phone / computer away from the 13 month old while I replace the IMEI NV data.... Still stuck on EDGE.... at least my IMEI is showing up though.
Nick
Odin back to stock worked for me when that happened to me.... YMMV.
Sent from my SGH-I747 using xda premium
The night I got my phone, I rooted via odin and when it booted, I'd get a framework FC every 90 seconds or so. It took me almost two hours to get cwm recovery on my phone to flash AOKP. Not a brick, but since I hadn't even activated it, yet....not happy.
Sent from my SGH-I747 using xda app-developers app
Each Phone an Adventure
I can completely relate to all of you. Though I'm new as a member (thought I already had an account but apparently I didn't), I've been using the forum for a long time. I have rooted four phones to date, each with its' own disaster story and happy ending. My latest was the AT&T S3. While not a disaster entirely, the no flash counter guide ended up not working out for me. So I paved my own trail so to speak and I found all the root dependencies (Recovery, ROM, the works) by myself. The entire process took me about a day. I also used TriangleAway which threatened explosions if anything went wrong and thankfully nothing did. I'm glad I never had to send a phone back, I've always been very cautious about any type of flashing and always read the forum before doing it.
When I was on the captivate, I really wanted JB so I thought I could grab the Nexus S JB ROM cause the devices were so close to each other. Flashed it via Odin. Good God was that a mistake. I couldn't get back to download mode using the button combo since the button mapping was all switched up. I had this one cable that would give me bad connection, so I jiggled that around in the port for 35 minutes trying to get download mode. Finally, I got it and flashed the stock package. Learned my lesson, will never flash something from a different phone or anything that won't work 100%.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
goobs408 said:
When I was on the captivate, I really wanted JB so I thought I could grab the Nexus S JB ROM cause the devices were so close to each other. Flashed it via Odin. Good God was that a mistake. I couldn't get back to download mode using the button combo since the button mapping was all switched up. I had this one cable that would give me bad connection, so I jiggled that around in the port for 35 minutes trying to get download mode. Finally, I got it and flashed the stock package. Learned my lesson, will never flash something from a different phone or anything that won't work 100%.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
The thing about the Captivate was, no matter what ROM you flashed, the jig ALWAYS worked. It saved my ass quite a few times, until that is, the memory in the phone decided to die. I could flash through Odin as much as I wanted and it would pass everytime, but never go past the boot animation.
Dave the Knave said:
The thing about the Captivate was, no matter what ROM you flashed, the jig ALWAYS worked. It saved my ass quite a few times, until that is, the memory in the phone decided to die. I could flash through Odin as much as I wanted and it would pass everytime, but never go past the boot animation.
Click to expand...
Click to collapse
Flash stock GB with forgot name of kernel baked in. After that in cwm recovery partition external SD card.. then reflash in Odin then install whatever ROM u want
Sent from my SGH-I747 using xda premium
Trying to use Kies to flash anything. That's always a bad story for me
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Don't attempt to explain to a friend of little flashing knowledge how to root their phone. He hard bricked my phone. Odin is easy if you read but he turned it into rocket science and yeah.. Had to wait for another phone
Sent from my SGH-I747 using xda app-developers app
Well let me begin by saying I have a Galaxy Nexus and have been flashing roms, etc like it's going outta style. It's very simple to me and I am no newb. So with this logic in mind, I got a brand new GS3 the other day and proceeded to do the same. First, it took my a while to realize there are so many variants of our phone, then when I did a search I saw that there was a i9305 that is LTE....you already know where this is going. I figured that was the correct variant, spent like an hour trying to install a recovery because of the auto wipe feature and thus increasing the flash counter to 10+ (wtf!). Finally I download a rom, flash it. Freezes half way through (knew that wasn't good) and when I pull the battery, BAM, bricked phone.
After some more reading, not only did I find out the correct way of flashing to not increase the counter but also that the Canadian versions are the i747! Luckily it happened a day after I got it and I switched it out for a new one. Moral of the story: If you are flash happy and think all phones are like the Nexus, that's your biggest mistake! lol

[Q] Phone will only boot-loop... No matter WHAT!!

Hey everyone... Im in a serious situation... I have scoured the entire internet trying to find a solution to my boot loop problem, but it isnt looking good... I originally had an older version of CWM, then a while back I flashed the original stock recovery and used the phone that way... well recently, I got bored and wanted something better than the 4.1.2 JB stock mod, and wanted something a little more, new! (which is why were all here, yeah?) anyways, I reflashed CWM (i dont remember which one, but it had to be older) and kept getting the dreaded STATUS 7... so, I moved up to PhilZ Touch 6 (CWM 6.0.4.5), and was able to flash 4 different roms..... but EVERY single one of them just boot loops... Also, I would have cleared DALVIK cache (in both older and NEWER CWM), but it doesnt do a damn thing... like it literally flickers the screen for a half second, and goes right back to where I was..... I just need a working phone!!! I honestly dont give a damn what OS I am using, I just cant go another day without my phone. Any and all help is much much much appreciated.... (Crosses fingers)
I am also getting every sort of E: cannot do this or that or mount bla bla bla...
I am still able to get into recovery, sync with Odin and do minimal things... Only thing it WONT do is BOOT!
JeffreeHomicyde said:
Hey everyone... Im in a serious situation... I have scoured the entire internet trying to find a solution to my boot loop problem, but it isnt looking good... I originally had an older version of CWM, then a while back I flashed the original stock recovery and used the phone that way... well recently, I got bored and wanted something better than the 4.1.2 JB stock mod, and wanted something a little more, new! (which is why were all here, yeah?) anyways, I reflashed CWM (i dont remember which one, but it had to be older) and kept getting the dreaded STATUS 7... so, I moved up to PhilZ Touch 6 (CWM 6.0.4.5), and was able to flash 4 different roms..... but EVERY single one of them just boot loops... Also, I would have cleared DALVIK cache (in both older and NEWER CWM), but it doesnt do a damn thing... like it literally flickers the screen for a half second, and goes right back to where I was..... I just need a working phone!!! I honestly dont give a damn what OS I am using, I just cant go another day without my phone. Any and all help is much much much appreciated.... (Crosses fingers)
I am also getting every sort of E: cannot do this or that or mount bla bla bla...
I am still able to get into recovery, sync with Odin and do minimal things... Only thing it WONT do is BOOT!
Click to expand...
Click to collapse
Have you tried to flash a stock rom through odin? It'll restore your kernel, recovery and system back to stock and should not bootloop.
What carrier are you with?
chevymeister said:
Have you tried to flash a stock rom through odin? It'll restore your kernel, recovery and system back to stock and should not bootloop.
What carrier are you with?
Click to expand...
Click to collapse
Yes, of course. I have been online for 2 days straight trying to fix this issue and tried MANY "FIXES" for similar issues, but no Cigar...
I am with TMO (SGH-T999L) US, btw
I would sincerely love just to have my phone back and operation-able..... weather an old custom ROM or back to factory 4.1.2 ... I truly dont mind either way, I just need her working again. lol
You need to factory reset most likely. Wiping dalvik alone doesn't usually solve boot hangs. Factory resetting almost always does.
DocHoliday77 said:
You need to factory reset most likely. Wiping dalvik alone doesn't usually solve boot hangs. Factory resetting almost always does.
Click to expand...
Click to collapse
That did absolutely nil. Tried it many many times over...
I think a sensitive folder got deleted or something. I just had them send me a replacement. Thanks!
Ok. Sorry I couldn't help. Glad to hear you're getting it taken care of though!

Categories

Resources