I cannot get passed the samsung galaxy s2 screen. When i go to recovery it takes forever to try to wipe cache and system and comes up with miscellaneous red text problems. I have never had this happen and have flashed roms since this phone came out. Does anyone know how to get passed this??? I even odined back to various versions of os to included EK02, EL29, EL29 ROOTED, using one clicks and regular odin. Is there anyway to get passed this problem. I looked all through the forums and still can't get the phone to boot. Please help
Were you trying out CM9/AOKP? Did you do wipe data/factory reset in an ICS kernel?
Yes... I was trying the AOKP :-( I was tired so i may have used clockworkmod to wipe while on ics kernel. I know i should have used mobile odin to change kernel, I had no problem going from ics to ics or ics to GB with AGAT's . Have a made a fatal mistake? You knew exactly which rom i was trying. I know not to do that but i may have on accident. Can i get passed this? I can only get to the samsung galaxy screen. and then it turns off and comes back on. Even with the phone off and on charge... The battery charge icon shows up frozen
Can you get to download mode?
Try to boot into download mode from a cold boot, if you can do that I would suggest using ODIN, the flashing god, to restore your phone back to a stock ROM. Preferably EL29, then if that is successful use ODIN again to flash FF11.
Sent from my SPH-D710 using xda premium
I can get to download mode but when i use OC it gets stuck shortly before the modem flash. I have been successful in using 1.85 with the EL29 tar but it still does the same thing. I will try ff11 to see if that works. So many red text errors in recovery. Sometimes i can wipe data sometimes i can't. I even got to a point where i actually used nandroid to restore my backup of wicked sensations ff11 (which i was success doing a few times before the brick) I will try again... with your suggestions. Thank all of you trying to help. This is very frustrating
UGH!!! Tried the FF11 one click and it still stops at the datafs portion! Just freezes. Going to wait a year to download the odin tar from slow file factory and hope that brings some progress... If anyone knows how to get past this, it would greatly be appreciated
That doesn't sound good. Sorry man. Some people have had luck pulling the battery and leaving out our for a few hours then trying the oneclick again. Sounds like you're hard bricked though.
Sent from my SPH-D710 using xda premium
You're bricked my friend ... there goes another victim
There's a bug in the EMMC firmware that causes the phone to lockup when certain mmc erase operations are done. This basically causes a superbrick which can't be fixed at this time.
The best you can hope for is to map around the problem, which is some effort and you'll always feel you phone isn't complete.
I would suggest you get it replaced.
What is considered mapping around the problem? Is there any way i can return to sprint or will that be a no go seeing how i can't reset the binary counter (as far as a know) without a jig? It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen
mremale said:
What is considered mapping around the problem? Is there any way i can return to sprint or will that be a no go seeing how i can't reset the binary counter (as far as a know) without a jig? It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen
Click to expand...
Click to collapse
Same here, exactly the same.
Does any of this add up to yours? What's happening completely sucks. :/
My once bricked....
mremale said:
It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen
Click to expand...
Click to collapse
Nothing is strange about it. The area of flash the /Data partition is mapped to is corrupted at the wearlevelfs level, something that cant be fixed by JTAG. From what I have seen there are 2 levels, the blue light of death and then able to get to recovery and download. The causes are pretty well known, known by Google and some parts of Samsung before we even knew about it.
Have you tried using ODIN to go back to EL26? sometimes EL29 doesn't work when i flash back to that version.
First off, thank you ALL for your replies and attempts to help. It is very appreciated! I odin'd to pretty much every kernel and rom i could. Some got me further than others. The end result was still the same. I get to see either the frozen battery charging icon or samsung galaxy s2 logo and nothing else. I did finally find a stock unrooted EL29 md5 (since everyone is on the one clicks these days) and was able to odin back to stock unrooted with no yellow triangle in hopes that my visit to sprint doesn't bad. This sucks, i can't believe i am hard bricked yet i can odin, get to recoveries, and even flash roms as well as nandroid restore. I looked into the Jtag thing i the post before this one says that's a no go too. Hopefully someone will have a miracle fix or sprint has a heart...
Think those of us with this problem are pretty much screwed...
If this helps anyone out there who may have an answer for me... I had just clean installed AOKP-39 and had a barrage of force closes... I went back into recovery (Actually didn't try flash from ics to ics or ics to gb) to wipe data, cache, ect... and that was the end of my glorious Epic 4g touch! Don't wipe anything people... If you can manage to open mobile odin through all the bs force closes, head back home that way!!!! Still hoping someone has the all spark for my Epic
mremale said:
If this helps anyone out there who may have an answer for me... I had just clean installed AOKP-39 and had a barrage of force closes... I went back into recovery (Actually didn't try flash from ics to ics or ics to gb) to wipe data, cache, ect... and that was the end of my glorious Epic 4g touch! Don't wipe anything people... If you can manage to open mobile odin through all the bs force closes, head back home that way!!!! Still hoping someone has the all spark for my Epic
Click to expand...
Click to collapse
ah, so it looks like you had a bad download of AOKP or a bad flash (they happen) and in your panic forgot to Mobile Odin back and instead you reflashed AOKP from the stock recovery?
Sorry to hear about the brick. It's definitely a good lesson for newer members to read. If you have insurance, at least you'll only have to shell out $60 or so.
Yeah, i think it may have been a bad flash. I don't know what the deal was with all the force close notifications. I didn't try to flash back, i tried to do a wipe and then the trouble came. It was bad after that, so i tried to flash and it was the same situation
To those who have recently suffered a brick due to this issue I will kindly suggest still consider taking your phone to Sprint to ask for replacement. It certainly doesn't hurt to try. As a fallback contact Samsung and you can ask them to fix/replace under warranty.
And just to clarify - is there anyone before this rash of bricks that didn't or wasn't able to get their E4GT replaced? Just curious because it seemed like just about everyone was good.
Related
Hello,
Last night I rooted my device using this (http://forum.xda-developers.com/showthread.php?t=1265429) method and file from zedomax and everything worked great except when I booted my device there was a yellow triangle with a black “!” in it. I figured that just indicated the device was rooted or running a 3rd party kernel so I didn’t worry about it.
Today I launched my camera app and it failed to load the interface but showed the image from the camera momentary then crashed back to the home screen. I restarted my device and when the device restarted it was very slow and unresponsive and after unlocking it my live wallpaper was gone replaced with the last background I used before selecting a live background a couple weeks back. No icons or widgets loaded and I am unable to open the settings tray. The only things I am able to do with the phone is pull down the notification bar, respond to text messages, adjust the volume and hold power to restart the phone. All of which are very slow and delayed.
When I connect the device to my computer windows is no longer able to load the drivers and Kies is unable to connect with the device. I am not sure what caused this or how to resolve this issue so any advice or known fixes would be fantastic! I am unable to get to clockwork mod to restore my backup and I am unable to get to Kies or the phone settings to do a factory reset so I really don’t know what to do they were supposed to be a last resort and now I don’t even think I can do them. I am an experienced techie but I am new to android and this is the first device I have rooted so any advice would be great no matter how basic it may be.
UPDATE: I just connected the phone via USB to my laptop at work and it was able to discover and install everything it needed to connect with the phone. I am installing Kies now so at least there is hope of a factory restore, although I really hope it doesn't come to that!
Boot into download mode and flash the stock eg30 tar file from crawrj.
Sent From My Evo Killer!!!
Thanks Already started doing that waiting for it to download now
Still no touchwiz... great!
Try flashing a stock rom via clockworkmod.
efarley said:
Still no touchwiz... great!
Click to expand...
Click to collapse
You can root again and restore your backup, or go to this website www.lostandtired.com (midnight roms blog) click on android development and download and flash the sprint bloat and TW restore zip. Hope that helps.
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
efarley said:
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
Click to expand...
Click to collapse
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
dallastx said:
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
Click to expand...
Click to collapse
Ohhhh that's what happened! Awesome thanks. I will be much better prepared with backups out the wazoo this time haha.
Now if only I could figure out why Touchwiz died in the first place hmmm....
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Khilbron said:
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Click to expand...
Click to collapse
haha SPRINT removed it?! So that person thinks sprint monitors every device and has a team of techies on staff to hack your phone and brick it if you break their rules?... yeah that totally makes more sense than a file got corrupted when you were messing with the kernel.. some people maybe shouldn't be rooting their devices in the first place haha
Hey everyone,
So this is my last ditch effort to attempt to save my device. I would really prefer not to perform another warranty exchange given that I am not under insurance, but I'm afraid I have no choice.
My phone was rooted and I was using Darkside without issues, as I had been for the past two weeks. I am always careful when I flash roms and I made sure to follow every possible protocol. That's the background information.
My battery life was running at approximately 6 percent yesterday and I sent a text message as normal, and it was stuck at sending. I tried turning wireless data off from the toggles in the pull-down and it was unresponsive. When I went to Wireless Network in the settings option, my phone rebooted. Once it started up again, my service would not come back, and the phone would continually bootloop once it got past the traditional "media scanner running", etc. My window of opportunity to do anything was really slim.
I charged my phone to see if it made a difference, but it didn't. Tried with my SIM card removed and it still bootlooped. I was able to get to CWM from the advanced power menu before it rebooted again and I fixed permissions and cleared cache and dalvik. Now the phone wouldn't even get past the boot animation before rebooting.
I put the phone into download mode and reverted back to stock using Odin. The phone now got past the boot animation in stock mode, but was unable to find service and after about 10 seconds fell into the same bootloop pattern. I tried removing the SD card but that didn't help either. Using Odin again, I reflashed recovery, followed by root and tried reinstalling a rom through CWM (I have only used regular CWM, not the touch version) with a superwipe to ensure a clean flash. Once again, it wouldn't make it past the boot animation before bootlooping. I reverted back to stock using Odin, and this is where I stand.
I have tried all traditional methods to salvage the phone and, for the life of me, I cannot understand what happened. The only thing I notice is that regardless of how long the phone stays on before rebooting, it is never able to find service. It's like the radio or modem broke and the phone has no other choice but to restart forever. But reflashing the stock UVKL1 should also reflash the proper modem and radio, right?
Has this ever happened to anyone? Any suggestions (aside from the typical reverting to stock) as to how I might be able to stop it? I searched but haven't been able to find a situation quite like this one. Thanks in advance for your help.
Really sorry to hear about your problem. Assuming the 2.3.6 stock image you flashed via Odin is the one provided by Przekret and that that didn't work, then I'd try one or both of these two longshots to try to clear possible corruption problems in either the kernel or modem spaces:
For each of the following wipe cache and Dalvik cache in CWM before flashing and again wipe Dalvik afterwards and also fix permissions:
1) Format system (do this 3x) under mounts & storage in CWM. Flash the standalone Darkside kernel X v1 final immediately after flashing, e.g., the current Darkside rom. (You'll need to wipe data, too, if not coming from a Darkside rom. Do not do any Superwipe - neither the standalone version nor using a flag.)
2) Flash the KID modem (do this 3x). Both Odin- and CWM-flashable versions are available. (You can always flash back to KL1 if the problem is fixed.)
Hope this is clear. It's late! These are both things that have helped get my phone out of troubles, though not as bad as yours. Good luck!
Sent from my SGH-T989 using XDA App
Also if u used the one from przekret then I'm almost positive that Odin package flashes the new radio too. If memory serves me right. Op let us know what happened
Thanks for your help. Unfortunately, nothing has worked. I'm on the phone with T-Mobile, I see no other solution but to get it exchanged under warranty and it's not getting here until March 15th, according to the representative. I suppose I'll just use a replacement phone in the meantime. It's just really weird and frustrating... I could understand a bad flash or something similar, but I followed every step accurately as I always have and everything was working just fine until it randomly decided to die without warning.
Well since you're getting another one anyways I would continue trying to fix this one, just in case you come up with a solution and for another worst case scenario for your new phone.
Powered by the SGSII....
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
shehrammajid said:
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Forgive me for asking, but what is the EFS folder?
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)!
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
Hello everyone,
been creeping the forums for the past week...new to the android world but i find the idea of customizing your phone in your own unique way was a good enough reason to leave blackberry after using it for 7years. Anyways....onto my real problem here.
(I appolgize in advance if i mess up the terminology. hopefully you can understand me)
I use a phone on wind mobile (SGH-T999V) and from what i know it's been a safe assumption that if the T999 works then the t999v will most likely work.
I was on AOKP build 5 prior to flashing to the CM M2 ROM...used odin to install CWM_Touch 6.0.1.2.tar then did the steps in
http://forum.xda-developers.com/showthread.php?t=1946701
Edit : I forgot to mention...I can get the screen to go into recovery mode...however, when i press up on the volume key my phone will turn itself off.
and i plugged the phone in again and it decided to be read by my computer.
to install the ROM which worked successfully... however this is where I think i messed up or maybe it has nothing to do with it at all... But my MMS messages did not work so i tried to just play around with some settings and i searched the forums and tried the things that were posted but to no avail. One of the things i did try was to uncheck the privilege unknown applications button and to turn off developers option so USB debugging should be off...or it may have been on...not too sure.
Anyways, so i remembered that I haven't finished the last 2 steps from the "how to flash a rom" in the midst of reinstalling my programs using titanium backup. So i reboot into recovery mode(and this is where i messed up i think) and i wiped my factory data again so after noticing that i did that i went back and restarted the phone and filled in all the information on the welcome screen again. and went back into recovery.
did "wipe cache partition" 3 times AND dalvik cache once then proceeded to install from my sd card the "lk_aosp_jb_tmo-v1.6". After installing i rebooted the device again and i get to see the Samsung Galaxy S3 screen and my screen will go completely black. However, I know it's still on as the battery charging indicator is on and my two buttons around the home button are lit up constantly....out of curiosity i decided to call myself using a land line and the phone is still working (I hope this is good news and that i'm not bricked but teased in a sense i can't fix the screen).
I tried to plug my phone in and it didn't detect it so i reinstalled the drivers and it did detect the phone. I laoded the Samsung Galaxy S3 Toolkit V.2.3.0 in hopes of trying to recover via option 6 "backup and restore your phone" and was hoping to revive it by restoring the nandroid backup however when i typed in my folder the toolkit crashed on me...and now it can't detect my phone as when i try to install the drivers again - the MDA driver seems to fail everytime.
Sorry for the long message...I wanted to be detailed in a sense I don't have to keep giving people more details... your help would be appreciated...Thanks everyone!!
Where'd you get the lk_aosp_jb_tmo_1.6 file from? Never read about it. All you need to do is wipe completely from recovery (data, system, cache...) and install cyanogen and then gapps, reboot.
Sent from my SGH-T999 using xda premium
You can also just odin back to stock and start over from fresh. If you can still get into cwm then just do what he just stated above.
Sent from my SGH-T999 using xda app-developers app
Where'd you get the lk_aosp_jb_tmo_1.6 file from? Never read about it. All you need to do is wipe completely from recovery (data, system, cache...) and install cyanogen and then gapps, reboot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1845836
It was 1.6 as of yesterday when i downloaded it but it looks like it's 1.7 now. That was my original plan however when i boot into recovery i literally have roughly 1second to pick an option before my screen goes blank again. I tried to boot it a few times into recovery trying to "beat" the blank screen but that hasn't worked.
You can also just odin back to stock and start over from fresh. If you can still get into cwm then just do what he just stated above.
Click to expand...
Click to collapse
Yeah the problem is I can't get back into the cwm as my screen goes blank
I tried to find a link for the stock kernel but the 2-3 that i found all have 404.
Something tells me i just ran into bad luck with the kernel flash. or does it have to do with me doing a wipe/data reset again and perhaps not selecting the debugging options/trusting unknown apps checkbox before running it through again? I'm not sure...just grasping at straws here to why my phone is doing that.
Anyone else have more ideas?? Anything will help...Thanks again!!
Looking like an Odin is your option here. To flash a ROM/kernel, wipe data,system,cache... flash ROM then gapps(optional for which ever ROM you are on) and then kernel. Make sure you're flashing the proper kernel.
Sent from my SGH-T999 using xda premium
mt3g said:
Looking like an Odin is your option here. To flash a ROM/kernel, wipe data,system,cache... flash ROM then gapps(optional for which ever ROM you are on) and then kernel. Make sure you're flashing the proper kernel.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Okay - I'll try it tonight when i get home from work. Here's where my lack of knowledge/noob status comes into play. Thanks for the help.
Do i get into Odin via trying to start my phone in download mode? (I tried to hold the power button/down/home) but that's when i get that glimmer of hope before my screen turns blank again when it asks if i want to continue or reboot my phone.
Or do i try to get it running through Samsung Galaxy S3 Toolkit V.2.3 ?? (If that's the case can you tell me which option i should use to get to the appropriate screen? or should i just launch the odin executable file? (however I'm not sure how that would get anything accomplished if my phone doesn't enter download mode...or maybe it's in download mode when i press up on the volume key but the screen is actually blank? Or maybe i don't understand the process 100%)
But lets say hypothetically speaking I manage to get Odin working. Which proper kernel should i be using? I tried looking for the stock kernel but all the links i found 404'ed. Does anyone have one that works? I'm just kind of trying to get my phone working in general...even if it means going back to stock everything. Pointers Anyone?
Thanks!!
Edit: Forgot to mention the fact that I may not be in debugging mode as i tried to turn that off to see if that had anything to do with my inability to send out MMS msg's as i mentioned in my first post... so that might stop me from using Odin no?
Update
Ok well just an update in case it happens to someone else - I pretty much left the phone alone and didn't touch it for 16hrs. Came home from work and it decided to boot up recovery mode so i just wiped data/cache quicker than a little kid wanting to open Christmas presents on Christmas day when they wake up... Needless to say I didn't bother testing the lk 1.6 kernel so i'm not sure if it works with CM10 running a SGH-T999V (Wind Mobile) phone. I'm trying to think of what may have happened and I'm thinking MAYBE it's because i was charging my phone from 20% all the way to about 95 then decided to plug it into my computer ...so maybe an overheat issue?
Anyways. Thanks for everyone's attempt to help. Much appreciated!