Related
Epic 4g running bonsai 4.0.1, rooted with CWM3.005 and flashed to cricket 3 months ago. I've been using titanium , superuser, pandora, all programs worked great. I even got most of the sprint crap off my screen.
Last week I was powering down to change batteries but I popped the battery out before the final buzz signaling full shutdown. upon reboot, phone had lost my home setting, icon placement, etc, and had sprint crap back on it. i reloaded the bonsai zip, but I cant restore using titanium because it won't let me access titanium, or pandora, and most of the games and apps I've installed. Also the launcher crashes a lot now...
Do I have to wipe the phone and start over? anyone have a suggestion? thx for reading...
Bravo u found a new way to factory reset
Id odin
Sent from my SPH-D700 using XDA Premium App
Yeah, I feel like a tard..
...whats odd is I still have bonsai, and i can still access CWM in recovery mode, so...i'm still rooted, and yet, it won't ACT like its rooted, denies me access to post-root programs. So odin from scratch? (hope this is a lesson for all us impatient noobs....WAIT FOR FINAL LIGHTS OUT! LOL)
Did you try wiping Cache and Dalvik 3x first? If so, sounds like an Odin fix. I would start fresh. One thing I have learned from testing things that aren't released yet is that Odin is actually pretty painless if your phone is recognized by PC. Its 3 min 35 seconds to get back to stock, 2 min for Root. The longest part is the RFS to EXT4 file conversion but its not bad at all and at least you will have a totally clean install.
Sent from my SPH-D700 using XDA Premium App
haven't tried the cache/dalvek wipe yet...doing now...
Hey guys. I've been scouring XDA for a while now, but this is my first post, so go easy on me.
A couple of days ago I flashed my Epic 4g to EH17 Hurricane ROM v1.6 (loving it!) per the instructions here:
http://forum.xda-developers.com/showthread.php?t=1244212&highlight=modem
I also switched to QQLauncher Pro, but I doubt that has anything to do with my problem.
All is working great and I'm loving the rom, except... I can't connect via 4G.
I turn it on and observe the status go from "connecting" to "obtaining IP" to "disconnected". I've even seen it stay connected, but my IP and gateway remain "0.0.0.0". No matter the status, not a single page loads and not a single app connects.
If I turn on wifi or turn off 4g and let it switch to 3g, everything connects/loads just fine.
I also flashed the modem to EH17 per info found here:
http://forum.xda-developers.com/showthread.php?t=1123103
But that didn't help anything - same problem persists.
I believe it's this particular rom, because I tried another (SyndicateROM Frozen) and 4g was working perfectly then. But then flashed back to Hurricane, and no 4g.
Any ideas?
Thanks in advance.
Had the same problem only it started a week after flashing. I had to Odin to EH17 stock Deodexed prerooted ROM, verified 4G worked, then flash Hurricane to get it working again. Just to be safe I restored apps only with Titanium, no data. Then also flashed the journal on zip.
Sent from my SPH-D700 using XDA App
kenny, thanks. I'll give the stock rom you mentioned a shot. Just to confirm, is it the same one as here: http://forum.xda-developers.com/showthread.php?t=1242486 ?
Also, I'm sorry for my ignorance, but what the heck is a journal? Is it necessary?
Thanks again.
fallen888 said:
kenny, thanks. I'll give the stock rom you mentioned a shot. Just to confirm, is it the same one as here: http://forum.xda-developers.com/showthread.php?t=1242486 ?
Also, I'm sorry for my ignorance, but what the heck is a journal? Is it necessary?
Thanks again.
Click to expand...
Click to collapse
That's not the one but you can try it. That is an update.zip which works through recovery. Look for the one that has ODIN in the title thread. Journaling in simple terms is some error protection. It causes the phone to write twice to the system. So if your phone crashes, battery is pulled without waiting for it to be off, or dropped, Data gets corrupted. With journaling on it compares the 2 writes and uses the good one. Not fool proof but stops lots of erros. Something happened to your WiMax files to cause your 4G loss.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
That's not the one but you can try it. That is an update.zip which works through recovery. Look for the one that has ODIN in the title thread. Journaling in simple terms is some error protection. It causes the phone to write twice to the system. So if your phone crashes, battery is pulled without waiting for it to be off, or dropped, Data gets corrupted. With journaling on it compares the 2 writes and uses the good one. Not fool proof but stops lots of erros. Something happened to your WiMax files to cause your 4G loss.
Click to expand...
Click to collapse
Well I tried this one:
http://forum.xda-developers.com/showthread.php?t=1242326
And then put Hurricane on top of that. 4G does indeed work now! Thank you.
However, I noticed a lot more and frequent shut downs (even within a few minutes of my initial boot-up). Have you had any issues with your setup?
Also, this might be a stupid question, but.. between the stock flash via ODIN and Hurricane flash via recovery mode, did you do anything else in recovery mode? wipe, clean, reset anything? I ask because I would typically do factory reset/wipe 3 times, followed by partition cache wipe 3 times, and then dalvik cache wipe 3 times (as instructed in other threads and qbking's videos). But I didn't do any of that in this case because I figured it would wipe out the stock rom I just put on via ODIN, which seems to me like it would defeat the purpose of putting it on in the first place. Am I wrong in my thinking?
Thanks for your help.
You are correct in thinking Odin is a clean start. Data wipe removes any third party apps and any settings you change on your phone. Stock will still be there. I also do not do wipes from a fresh Odin..but I live on the edge, lol. As for your reboot issues, I would get about 1 every hour or so until I started working with the guys in the following thread and don't get reboots anymore:
http://forum.xda-developers.com/showthread.php?t=1276417
Tegrak will cost you $2.34 but well worth it to enjoy GB goodess now with no reboots. You can even overclock if you prefer performance over battery life.
Awesome, thanks a lot kenny, I'll give that shot.
Hello,
I am new to this forum, so If this is the wrong place I do apologize.
Ive recently purchased a new ET4G and decided to root it. I had another one rooted with no problems. Ive been using a couple different roms and this random reboot has became more frequent and has followed me with each ROM.
I have tried to ODIN back to a stock ICS build with Root and then flashing ROMS over again. I still received the same problem.
I am currently using FD26 stock with the addition of root. When the reboots happen. It seems to drain my battery drastically.
Example:This morning at 50% phone reboots and I am at 9% when it comes back on. After a couple reboots it becomes stuck and only a battery pull will allow it to reboot once again.
Anytime I flash a ROM I always follow the recommended flashing method. I do all the appropriate wipes. Id usually think It was the kernel, but even after trying different kernels the issue still happened.
If anyone could shed some light on what could be happening. I would be very appreciative.
do you do complete wipes prior to flashing?
Yes, I do. I usually wipe Davlik and then will run Caulkins format all zip before I flash any Rom. I always odin back to EL26 w/ CWM to flash through to avoid any conflicts with that.
I have no idea what to try next. I've went back to stock a couple times.
This same thing was happening to me honestly about 10 reboots a day and sometimes it would drain me down about 50% battery. I odined back to stock gingerbread using sfhubs latest method, reinstalled clockwork mod and have not had one reboot since. I think I may have heard though that the fd26 build has reboot issues so I would look into that as well. Though I see that you have tried what I have said not sure if you used sfhubs method or not but if so I would just take it back to sprint.
Have you tried flashing this? http://forum.xda-developers.com/showthread.php?t=1433101
I would flash the full restore and if it keeps rebooting unroot and return to Sprint for repair. In the meantime make sure you are not using a cheapo charger and even charge via usb only if its not too much trouble.
someguyatx said:
Have you tried flashing this? http://forum.xda-developers.com/showthread.php?t=1433101
I would flash the full restore and if it keeps rebooting unroot and return to Sprint for repair. In the meantime make sure you are not using a cheapo charger and even charge via usb only if its not too much trouble.
Click to expand...
Click to collapse
+1
Seriously, if you're having problems, to narrow it down you should not be on a leaked Android OS that is still in the testing stages. Always odin back to stock rooted to troubleshoot any issues, report back and we can get go from there.
Edit: If you need help getting back to stock rooted, please ask for help too.
Thanks for all the replies guys. I didn't try flashing the EL29 Restore, But I did try the EG30 and just OTA updated to EL29. It still didn't fix the reboot issue. Even when the phone wasn't rooted, it still would still power cycle. I just went ahead and restored it again and took it to sprint.
It happened about 10times while waiting to talk to a rep in the store. They didn't have a problem setting me up with a replacement. For now I will just use my old 3D. Thanks for the help though everyone.
I'm still stock EL29 till ICS comes out, but I get a reboot every couple days. It actually happened last night about 2AM and woke me up when the Sprint sound came on. Thought maybe there was some update (ICS?) that had caused it, but i didn't see any reason for it. It wasn't charging at the time and the battery was pretty full... Was hoping ICS update was going to fix this, but it doesn't sound promising.
RaheemA said:
Thanks for all the replies guys. I didn't try flashing the EL29 Restore, But I did try the EG30 and just OTA updated to EL29. It still didn't fix the reboot issue. Even when the phone wasn't rooted, it still would still power cycle. I just went ahead and restored it again and took it to sprint.
It happened about 10times while waiting to talk to a rep in the store. They didn't have a problem setting me up with a replacement. For now I will just use my old 3D. Thanks for the help though everyone.
Click to expand...
Click to collapse
On a previous phone (Samsung Moment) I had that issue and it turned out to be a bad battery. They let me borrow a battery in the store and it went away.
Reboots are ICS related.
Sent from my SPH-D710 using Tapatalk 2
revamper said:
Reboots are ICS related.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
got reboots in GB as well so I don't think its solely ICS related... IMO
Yeah... I still was hitting the problem while on Complete stock GB. The phone could have honestly had the problem prior to rooting and flashing. I didn't keep it stock long enough to know for sure haha
Probably not related, but I was having reboot problems due issues with App2SD, so i figure it is worth mentioning just in case...
Issue 25563: OS keeps rebooting when lots of apps are moved to SDcard! HUGE BUG IN ANDROID OS 2.3.5 (and higher)!
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
I'm just going to throw this out there for anyone who may know the answer, after searching for the last 3 days, I'm not finding anyone else having the same problem, so I'm thinking it may be something I did. Here's the issue.
I'm a confirmed flash-a-holic, and flash new roms or backups probably 2-3 times per week. I haven't tried any of the JB roms until recently, but dove in just before Nit's Viper Rom became available for ICS. I had installed the JB "global" rom, and had it working(ish), and then changed to the viper mod, then installed Aeroevan's "unofficial JB" when the 10/25 update on Goo.im came available. The install went smoothly and it worked great for about a day, then tanked big time when I tried to change the launcher from Trebuchet to Nova (I can't even guess why THAT had anything to do with it). It started lagging big time and then boot looping. Now, upon trying to wipe everything (factory reset/cache/dalvik/all partitions but sd), I get nothing but boot loops and NONE of the JB roms will install. From my reading, I know others get boot loops, but after a sequence, finally get into setup. Mine will too after 5-6 boot loops minimum, but the screen freezes on the initial setup screen and it's completely unusable (touch screen unresponsive). I don't get why that is when I HAD it installed the other day and it was very responsive (using Aeroevan's JB mod). I WAS using the 4EXT recovery when I started doing all of this, then switched recoveries to the most recent TWRP, and it allowed me to install Aeroevan's JB mod, and even start the setup, but very soon started lagging and then the boot loops again. At this point, I'm sortof at a loss, and the only thing I can think of is that maybe I should NOT have been wiping the sd partitions and SHOULD have only been wiping cache/dalvik/factory reset. At the moment, anyway all ICS mods are flashing/running just fine (currently on Nit's Vipermod and really liking it btw), but if anyone knows where I went astray, I'd appreciate any pointers. Thanks all, this is by far the best forum I have been a part of!
http://forum.xda-developers.com/showthread.php?t=1805773&page=117
Oh boy..... Be sure and post back if you find a solution, glad I'm not the only one! I thought I did this to myself... which I guess I sortof did if you get technical.
Sent from my Dinc2 using Tapatalk
I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....
auberry05 said:
I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....
Click to expand...
Click to collapse
Which radio did you flash?
Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.
bwpoersch said:
Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.
Click to expand...
Click to collapse
On follow-up, I read mixed opinions about the wisdom of using TiBu on restores, assuming I'm able to ever recover this my thinking is that one could use TiBu to restore apps ONLY and NO data and that would/should not cause a problem (assuming you're restoring a backup from within your installed ROM's file structure .i.e., JB/ICS/GB)? Also, I use My Backup Pro to restore call/MMS/texts only, that oughta be safe too shouldn't it?
I had a similar issue last night. never had problems flashing from viper to cm10 till yesterday. I've flashed back and forth about 3 times until I flashed the leaked 4.2 camera with sphere camera on aero cm10 Halloween build. I was playing around with the sphere camera and attempted to get it to actually finish loading the pics together by overclocking to 1.4mhz and I ended up pulling the battery. it boot looped very slow and laggy after. I did a full wipe, fresh install of aeros cm10 from twrp and got the same thing. So I recovered viper Rom from twrp , booted, then did a full wipe and install of cm10 and still boot loops laggy. I did not have the overclock settings "set at boot" ticked when I put it to 1.4mhz. odd indeed
sent by the viper
So... I was having no issues until today's huge headache. I was on cm10 10-25 and it worked great. Dirty flashed to 31 and it all went to hell. Slowed to a crawl so restarted to recovery to fix permission. Restarted and it kept restarting. I got some failure message when it would boot. Don't recall what it was.
I then tried 3 different recoveries and also full wipes and fresh flashes of 3 different roms. Same loop result basically. Finally an old recovery worked and I'm on a month old mrom version now. Soo... any thoughts on what the heck happened? I did nothing out of the ordinary. I was worried I somehow bricked but obviously not since I'm sending this on my phone. Kinda freaked to do anything right now... any thoughts or help/ideas?
PS... I just use the basic cwm and only cwm for my recoveries.
Sent from my Incredible 2 using xda app-developers app
Ukb wont boot here.
Sent from my HTC_Amaze_4G
so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper
fen0m said:
so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper
Click to expand...
Click to collapse
Someone just threw down on the info. Sounds like I will be flashing the latest mrom. Not gonna repeat the horror of my recent cm10 fiasco. Thanks for this.
Sent from my Incredible 2 using xda app-developers app
Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium
jtsrtr13 said:
Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Sent from my Incredible 2 using xda app-developers app
Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Sent from my MB865 using xda premium
A2Trip said:
Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Click to expand...
Click to collapse
I did the revert a while back for some other issues and didn't have any trouble getting aeroevan's CM10 up and running. I haven't had any issues with it other than the persistent bugs which are no problem for me. I don't think these issues have anything to do with the radio, but with the way the stuff is getting flashed. You might try a different recovery. I have had success with TWRP and CWM (as installed from ROM Manager, not touch) restored from a backup for me, but I didn't install using CWM.
ericsdeadinside said:
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Click to expand...
Click to collapse
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium
Don't know what to tell you. I switched to 4ext ran CDMA miui for a week and I was able to flash cm10 with no issues.
Sent from my Incredible 2 using xda app-developers app
jtsrtr13 said:
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
+1... seems like only Sence ROMs have been working on my girls Inc. 2. Viper seems fine for now... But her phone must literately hate CM9 and 10...7 works fine too. Not quite sure why these issues have been going on to few of us but I'm almost certain it will not be solved... On the move...
Sent from my MB865 using xda premium
hey guys I fixed my Inc 2 with jb ics lag/ boot looping issues.
check it out
http://forum.xda-developers.com/showthread.php?t=1987051
Sent from an incredibly running JB inc2