so, for some weird, out-of-the-blue reason, i can't flash anything successfully through odin. i tried flashing sfhub's el29 one-click ROM (no data) and it flashed, however, when it's done flashing and it tries to boot, it just bootloops. i used to be able to just go into recovery, wipe data, reboot, and all would be fine, however i can't boot into recovery. when i hold down volume up + power, it shows the galaxy boot ani for a few seconds like it normally does when going into recovery mode, but then it'll disappear, the screen will go black, and then it will try to reboot normally again. it never goes into recovery mode.
i tried flashing EL26 stock CMW kernel, and odin goes through the motions as if it flashes, however, when i try to boot into recovery, it does what it did before: display the galaxy boot animation for a few seconds, disappear, then reboots normally.
now, i'm trying to flash sfhub's fb17 full restore and it's hung at data.img (like only 2% remaining). it's been stuck for about 10 minutes now.
WHAT DO? should i try using Kies to reinstall stock firmware?
Your phone might be bricked with a failure of the data partition on your emmc
http://forum.xda-developers.com/showthread.php?t=1504808
dammit that really blows! i need to order a jig now to clear my count. dammit i knew i should've used the triangle app last night when i had the chance. blahhhhhhhhh
okay so i was able to remove the yellow triangle, but am not able to reset the odin count. is there a way to reset the count via recovery or odin? obviousy i can't use the yellow triangle app cuz i can't even get android loaded. seems like whatever the yellow triangle app is doing should be able to duplicated in recovery too. what say?
cnstarz said:
okay so i was able to remove the yellow triangle, but am not able to reset the odin count. is there a way to reset the count via recovery or odin? obviousy i can't use the yellow triangle app cuz i can't even get android loaded. seems like whatever the yellow triangle app is doing should be able to duplicated in recovery too. what say?
Click to expand...
Click to collapse
Good info of the location the count is stored : http://forum.xda-developers.com/showthread.php?t=1494114
Sent from my MZ505 using XDA Premium HD app
yeah, i saw that earlier, but i can't make anything of it.
i tried "/sys/block/mmcblk0boot0/force_ro" via adb while in recovery, but got access denied. is it because su isn't included in rogue 1.1.2 recovery? if so, how do i install su?
At least you should have the original bootloader so a jig will work.
To help others, do you think you can remember when the problem happened.
Usually it happens when doing operations in an ics-based custom recovery, operations like wipe/factory reset, restoring backups, flashing ROMs, etc.
i guess the usb jig is my only option if i wanna take it to the store. i'm a cheapskate and dont feel like waiting to get a jig shipped to me and then waiting longer for sprint to replace the phone, so i really wanted to find any manual way of repartitioning or just resetting the count myself.
anywho, this all started when...
i was in the process of wiping my phone to install aokp build 31. i flashed calk's wipe all script, then used the factory reset option in cwm recovery (http://www.mediafire.com/?hkydca9ob98z89m, first post of aokp dev thread). everything was kosher. i started odin'ing el26 (cuz i like to play it the safe way, and this way has always worked for me). odin seemed successful cuz it said "passed!"; and i had done this numerous times with every build of AOKP and CNA so nothing seemed out of the ordinary. when it rebooted, it got stuck at boot loop, which is typical in my experience -- i just go into stock recovery and wipe data and all would be good again. however, this time when i went into stock recovery to wipe data, it just froze and didn't do anything. and that's how i met your mother.
also, apparently the only recovery image i can flash via odin is steady hawkin's rogue recovery 1.1.2.
Okay wtf im able to flash cm7 all of a sudden. Brb, blowing load into sock, will report back later.
nvm, it freezes about 5 seconds after loading the home screen.
cnstarz said:
i guess the usb jig is my only option if i wanna take it to the store. i'm a cheapskate and dont feel like waiting to get a jig shipped to me and then waiting longer for sprint to replace the phone, so i really wanted to find any manual way of repartitioning or just resetting the count myself.
anywho, this all started when...
i was in the process of wiping my phone to install aokp build 31. i flashed calk's wipe all script, then used the factory reset option in cwm recovery (http://www.mediafire.com/?hkydca9ob98z89m, first post of aokp dev thread). everything was kosher. i started odin'ing el26 (cuz i like to play it the safe way, and this way has always worked for me). odin seemed successful cuz it said "passed!"; and i had done this numerous times with every build of AOKP and CNA so nothing seemed out of the ordinary. when it rebooted, it got stuck at boot loop, which is typical in my experience -- i just go into stock recovery and wipe data and all would be good again. however, this time when i went into stock recovery to wipe data, it just froze and didn't do anything. and that's how i met your mother.
Click to expand...
Click to collapse
I've never used calks format all with anything ics related because I heard you don't want to format the data. also when you factory reset was that on el26?
I got yelled at for starting a new thread because this is the exact same problem that happened to me. I was in Calks ics rom, I had downloaded the new alpha build for CM9, and installed rom manager and clockwork and went into recovery and went to wipe everything and BOOM, froze, and then when I tried to restart it it got stuck on the galaxy s ii logo and kept cycling like yours did. I cant get into recovery, but can get into download mode.
So OP|, are we screwed? Did you find a way to fix er up? Cuz I haven't
level27xrock said:
I got yelled at for starting a new thread because this is the exact same problem that happened to me. I was in Calks ics rom, I had downloaded the new alpha build for CM9, and installed rom manager and clockwork and went into recovery and went to wipe everything and BOOM, froze, and then when I tried to restart it it got stuck on the galaxy s ii logo and kept cycling like yours did. I cant get into recovery, but can get into download mode.
So OP|, are we screwed? Did you find a way to fix er up? Cuz I haven't
Click to expand...
Click to collapse
check out this thread:
http://forum.xda-developers.com/showthread.php?t=1504808
i've basically moved my discussion to that thread. there's a user who was able to recreate the datafs partition using some of the sdcard storage space with success, obviously at the cost of storage space. check it yo.
level27xrock said:
I got yelled at for starting a new thread because this is the exact same problem that happened to me. I was in Calks ics rom, I had downloaded the new alpha build for CM9, and installed rom manager and clockwork and went into recovery and went to wipe everything and BOOM, froze, and then when I tried to restart it it got stuck on the galaxy s ii logo and kept cycling like yours did. I cant get into recovery, but can get into download mode.
So OP|, are we screwed? Did you find a way to fix er up? Cuz I haven't
Click to expand...
Click to collapse
Level27xrock,
To answer your question first, you're probably "hard" bricked. It's been posted many times that you'll be able to get into Download mode, ODIN *most* of the stock image and it will hang at data.img because a previous action that you did - suspected to be the CWM wipe operation but not definitively confirmed - caused a I/O problem within the embedded memory or eMMC. Please feel free to try this out on your own and verify the results for yourself - it seems that may be the only way of convincing you.
You can find out more in the thread linked above.
I hope you will read the threads more before you try again. Please start with the one that says "How Not To Brick Your E4GT" for example. You also missed the one that said ROM Manager is a no-no for the E4GT - believe it's in the Q&A forum.
If I read the earlier posts right, I believe something similar happened to my friend. He was on AOKP then tried to Odin FD05 and it wouldnt get past splash screen. He then went back to EG30 and ran that through Odin and it did work but if some ROMs effect Odin completely flashing and restoring a stock setup then we are going to have a new surge of problems
Edit..he did NOT wipe in ICS recovery either
Sent from my Nexus S 4G using XDA
Related
ok..
so im stuck.. tried to reflash the stock DL17, using the downloads provided, including PIT (repartition checked).. via ODIN 1.3 to clear back to stock..
after flashing, the phone booted to DL17 - sort of.. no data was gone, all the wife's programs were there, and i got into a FC hell during setup. ACORE, GAPPS, pretty much every program.
then re-odined the DL17 by itself, no repartition, no pit..
now i cant get anything to flash...ODIN tells me it flashes fine, normal on there.. the phone does not hit the samsung logo.. goes straight to the android system recovery and i have NO hotkeys to select anything..
it says at the bottom..
"e:can't mount /dev/block/st111" (twice)
then under that it says
"update.zip gone"
ive tried every combo from the dev tools thread, and all flash fine via ODIN but go straight back to the android recovery, and i cant select anything..
anyone have any creative ideas?
First, "bricked" is used for when your phone does nothing.
Second, this isn't a development post. And read through stickies in general forum. This problem has been solved. Mostly from Irc.
Sent from my SCH-I400 using xda premium
geez im just going to leave this one alone lol
completly correct..my fault..i wasnt paying attention to where i was posting because of my frustration level..
and for the record i tried the heimdall magic fix in general section and it didnt work. phone starts to boot then shuts off. have to pull battery to get power. 3 finger recovery does not work either..just flashes the screen with samsung and dies again.
ciscogee said:
First, "bricked" is used for when your phone does nothing.
Second, this isn't a development post. And read through stickies in general forum. This problem has been solved. Mostly from Irc.
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
MIUI 1.12.9 RickS :: Glitch V13 :: ED05 Radio
Not sure txwolf and tb101 are resident fixers on that. Try to make Irc apmt. Good luck.
Moderator. Can you move post to general?
Sent from my SCH-I400 using xda premium
The fact that no data was gone the first time interests me.... Was it definitely a full system/data/cache/everything else tar?
I would download the EC07 full package, repartition, then try my magic fix....
Sent from my SCH-I400 using xda premium
trailblazer101 said:
The fact that no data was gone the first time interests me.... Was it definitely a full system/data/cache/everything else tar?
I would download the EC07 full package, repartition, then try my magic fix....
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
if i remember correctly, on irc, he said he flashed a rom that wasn't meant for the continuum, rather another galexy device..
well you surely are not bricked. but the cache partition is in deed messed up. (stl11 refers to the cache partition) unfortunatly, it seams as though you have done just about everything.
Try loading up heimdall and load only the pit, the kernel(imnuts hacked kernel is what i recomend using), and the modem/radio(ec07).
This should fix any partition issues. It will format the partitions in place where they should be but it will not write to the partitions. What i recommend next is different from most other things.
Hopefully if all is well, when you install the kernel it should fix the issues with the boot loader. boot into CWM if possible. Now try and flash a version of ec07.
If you are only receiving the stl11 issue all other partitions should be good. once the kernel and everything else is in place and you flash the system it should be good and boot up... hopefully
mrjake1970 said:
completly correct..my fault..i wasnt paying attention to where i was posting because of my frustration level..
and for the record i tried the heimdall magic fix in general section and it didnt work. phone starts to boot then shuts off. have to pull battery to get power. 3 finger recovery does not work either..just flashes the screen with samsung and dies again.
MIUI 1.12.9 RickS :: Glitch V13 :: ED05 Radio
Click to expand...
Click to collapse
Starts to boot? Where does it get to? Do you get into recovery, at all? Also, do you get samsung logo? Before you said it was booting straight into recovery. Has that changed after magic fix? I'd recommend doing a full ec07 stock with repartition in heimdall.
Thank you all..
I havent been to the IRC yet. Been trying everything else.
Here is the full story of the phone...
1. When the first ROM came out for this, I flashed it. Something (no idea what) borked it during the flash, and the phone wouldn't turn on. I could only get to CWM. I would try and wipe data, nothing would happen. I got a walk through from someone here on other stuff to try, which included mounting all the drives, and wiping them. I have never been able to mount (manually) any drive since - but it got me running again.
I was getting errors in CWM constantly.
2. No matter what i flash, or what (or how many times) i wipe data, datadata, system, ect.. whenever i flash anything the data from the old ROM remains on the phone and i end up in force close hell on the new ROM..
3. i probably the most stable ROM was EC03.. it worked but after a while would start random rebooting 4-5 times a day. ..so then wife wanted to try MIUINA.. we had her on V4 for a while. Then with upgrade to V5, things went bad again. I couldn't wipe data, ODIN the stock EC07 worked once, but the old data remained (all her settings/programs were force closing and old wallpaper remained.) then after that, I tried to ODIN MIUINA v5 again, ODIN said it worked, phone bootlooped into "stock" recovery, but gave the errors i posted above. no keypresses avail. t
tried heimdall fix all solution, now it boots to the SAMSUNG screen and hangs then shuts off, and wont turn on until a battery pull.
i cant 3 finger to recovery (wont let me, just hangs at samsung screen and then dies after about 2 minutes)
right now, i can get ODIN to work about half the time with the phone "taking" the flash, will get to the verizon logo and while building the dalvik, it dies, shuts off and then wont boot past samsung logo.
im going to try and see if i can get ODIN to let me flash CWM and get to cyan recovery and try a nandroid restore if it will let me.
can i use the DL17 stock MD5 file in heimdall? this is my first time using heimdall.. dont i need other files?
mrjake1970 said:
Thank you all..
I havent been to the IRC yet. Been trying everything else.
Here is the full story of the phone...
1. When the first ROM came out for this, I flashed it. Something (no idea what) borked it during the flash, and the phone wouldn't turn on. I could only get to CWM. I would try and wipe data, nothing would happen. I got a walk through from someone here on other stuff to try, which included mounting all the drives, and wiping them. I have never been able to mount (manually) any drive since - but it got me running again.
I was getting errors in CWM constantly.
2. No matter what i flash, or what (or how many times) i wipe data, datadata, system, ect.. whenever i flash anything the data from the old ROM remains on the phone and i end up in force close hell on the new ROM..
3. i probably the most stable ROM was EC03.. it worked but after a while would start random rebooting 4-5 times a day. ..so then wife wanted to try MIUINA.. we had her on V4 for a while. Then with upgrade to V5, things went bad again. I couldn't wipe data, ODIN the stock EC07 worked once, but the old data remained (all her settings/programs were force closing and old wallpaper remained.) then after that, I tried to ODIN MIUINA v5 again, ODIN said it worked, phone bootlooped into "stock" recovery, but gave the errors i posted above. no keypresses avail. t
tried heimdall fix all solution, now it boots to the SAMSUNG screen and hangs then shuts off, and wont turn on until a battery pull.
i cant 3 finger to recovery (wont let me, just hangs at samsung screen and then dies after about 2 minutes)
right now, i can get ODIN to work about half the time with the phone "taking" the flash, will get to the verizon logo and while building the dalvik, it dies, shuts off and then wont boot past samsung logo.
im going to try and see if i can get ODIN to let me flash CWM and get to cyan recovery and try a nandroid restore if it will let me.
can i use the DL17 stock MD5 file in heimdall? this is my first time using heimdall.. dont i need other files?
Click to expand...
Click to collapse
You will need the dl17 pit file. And to use heimdall, you need to break the tar down to its component files. I use 7zip for that, but winrar works too. I'll be in irc in 30 minutes, if you want to run through it.
thank you Txwolf1980 for the offer of an IRC chat, seriously..i just got this late this afternoon..i had to leave friday evening, and didnt get back until late.
i finally got the thing to boot..but it was out of total desperation, i started (logically, yet with reckless abandon, since I had nothing to lose at this point) flashing crap..
here is what i did to get this puppy running again..
ODIN, heimdall and CWM were doing nothing for me..no boot, no recovery, no 3 finger..nothing... still couldnt even boot into original system recovery..
since i have a fascinate, i had a few beers and decided to flash cwm4 (for the MTD ROMS) just to see what would happen...tried a 3 finger and it flickered the screen as if it *wanted* to go to recovery but didnt go into recovery, just kicked me back to the samsung screen..however i took the flicker as a good sign, maybe that jogged something somewhere..
i immediately reflashed the CWM adryn that is used for the continuum.. and 3 fingered after ODIN rebooted..
PROFIT! i now had the softkeys back to select the update zip for cyan recovery..
got into cyan recovery and went to mounts and storage, and mounted everything, wiped them (except for sd card) then unmounted them all and wiped them all again..
it took the commands.. i wiped the snot out of everything i could find to wipe.. i went back to install zip from SD card and flashed stock EC03 that i put on there months ago.. and hit reboot..
PROFIT! it booted.. it was all FUBAR, had screen flickering funny, and key presses were delayed by 3-4 seconds.. the phone was functional, calls, text, market all worked.. however, when the phone was powered off, it returned to stock (like a data wipe) upon restart. which was really weird..
f-it, i was booted.. and it was functional.. now to fix this for good...
i then did some research here, and found i was using the wrong PIT and EC07 ODIN files when flashing in ODIN.. found the right ones...and pulled battery, went to download mode, and flashed EC07 leak (production) with the I500 PIT, repartition checked..and ODIN immediately applied the PIT and flashed EC07...
the wifes phone is now running like a champ.. its not rooted, and is binged and bloated, but its looking like its completely fixed.. time will tell, but its been running for the last 6 hours now perfectly. I even rebooted 2x to make sure the changes/data/downloads stuck this time, and they did.
the wife threatened to snip off my giblets if i attempted to root it or mess with it anymore i tried to remind her that she is the one who liked the "cool other rom-thingies" but that didnt fly.. so i handed her the phone and said have fun....
sincere and heartfelt thanks to all who pitched in to the conversation to help... i hope that this post will help others who think their continuum is completely fubar..
im done messing with her phone. ill head back to flopping between ICS and MIUI on my fascinate where i know more abotu what im doing.. i haven't turned my fassy into a door stop in almost a year of HEAVY flashing..
Hi, first let me give you the background of my phone.
I bought it off eBay used and it came in an almost perfect condition, preinstalled with Gingerbread 2.3.6. The only problems known with the phone is that it won't get recognized by Samsung Kies, but it does by my PC. Onto the problem...
My friend introduced me to the Cyanogen Mod 9, telling me it could increase battery life, performance, etc. I was interested and wanted to install this mod. I first rooted my phone with a Zip off a tutorial and that worked flawlessly and I had Super User. I then installed Rom Manager and proceeded to installing the mod. He gave me two zips to put into my SD card to install for the Cmod and Google Play. Long story short, after wiping cache, data user, and every other wipe before installing these two zips, I was stuck in a boot loop with the Samsung Logo and Cyanogen Mod 9 Animation. I didn't think much of it and turned off my phone for the night, leaving it for the morning.
This morning, I tried going to Download Mode and flashing a stock os with Odin3 and it went from boot loop to soft bricked. It gave me a message to connect the phone to Samsung Kies in order for it to before restored, but the problem is that the phone isn't recognized by the program. I tried .tar files and it led to nothing on Odin3 because it wouldn't get past "Get Pit for Mapping...". I tried numerous times and on one occasion, I accidentally had Re-Partition ticked but the flash didn't go through so I unplugged my device. After that, the phone turned off and no response after that.
It won't turn on, no device recognized through USB or Odin3. I tried the wall charger to see if it was the battery's fault but it led to nothing. What are my options in reviving my Samsung Galaxy S2 ?
Yikes. Sounds hard bricked. I think your only option is to pay to get try a jtag recovery. Search the board on that.
Sorry man.
Sent from my SGH-T989 using xda app-developers app
I agree. Not a lot of options especially since warranty will be difficult without proof of purchase.
For future reference (for you and anyone else in this situation) the boot loop you experienced is due to cwm v5.0.2.7 not wiping caches correctly. After flashing an ics rom, if you are running this recovery, you have to flash the darkside cache wipe to get the rom to boot.
yoft1 said:
I agree. Not a lot of options especially since warranty will be difficult without proof of purchase.
For future reference (for you and anyone else in this situation) the boot loop you experienced is due to cwm v5.0.2.7 not wiping caches correctly. After flashing an ics rom, if you are running this recovery, you have to flash the darkside cache wipe to get the rom to boot.
Click to expand...
Click to collapse
Thanks for the replies! I was wondering how reputable is MobileTechVideos on doing JTAG repairs on bricked phones. Also, do you have a tutorial on how I can try to install Cyanogen Mod 9 again with the Dark Side cache wipe so i wont get the same problem again? Thank you.
Ok, so I flashed a MIUI port for the AT&T Note 2, and it was disgusting...it crashed everything, and needless to say I ended up stuck at the boot logo for a long time. FINALLY managed to get it to flash via Odin...so I flashed Stock Rom...and now it's stuck on Samsung logo...Ok..so I go flash CWM...do a wipe and everything, and install CM10.1 via that...stuck at CM logo. I've left each ROM plugged in, stuck on boot screen for over 20-30 minutes each. I'm at a loss of what to do. Could I need to flash a kernel? or am I missing something obvious? The good news, I guess, is with a few steps, I can get into DL mode and use Odin, and I can flash CWM and get into that..but I can't inject anything into my phone so CWM can use it, I only have what's there now, which is CM10.1. I'm so mad...I've never had too many issues with ROMs but this one jacked things up badly...guess that's what I get for using a port even though it noted that everything was working now. Anyway...does anyone have any advice?
Edit: I flashed CWM, and tried to clear cache/dalvik then factory reset...the first two worked...as soon as I hit factory reset, that's where the screen goes black and it resets...it's like it just refuses to do it. I'm seriously at a loss here. Is it toast?
Edit again: sorry but I'm trying more to give more info. I went into CWM and went to advanced and started formatting one by one...it's when you hit format /data that it immediately dies and restarts. So..something weird is going on there. Can I use a PIT file for this phone, if it exists, to reformat and just get it going? I'm desperate...
Us this http://forum.xda-developers.com/showthread.php?t=2052779 on a PC.
Follow directions and Odin back to stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
OfficialDoughboy said:
I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Ali7000 said:
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Click to expand...
Click to collapse
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Thanks for the response and taking time to answer.
OfficialDoughboy said:
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
OfficialDoughboy said:
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Click to expand...
Click to collapse
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
aybarrap1 said:
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
Click to expand...
Click to collapse
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
OfficialDoughboy said:
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
Click to expand...
Click to collapse
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
hednik said:
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
Click to expand...
Click to collapse
I actually did that, sorry I wasn't clear in my original post. This last time, I wiped the cache and rebooted the phone, that didn't work. Then I tried Odin to see if I could save internal data, re-flashed and again couldn't boot. Last thing I did was do a factory reset through stock recovery and got the phone to boot.
I have Cyanogenmod 10.1 (stable) installed; the other day it crashed while I was on Instagram, rebooted itself, and wouldn't go past the spinning circle screen. Tried rebooting it, now it won't go past the screen before that, with the blue Cyanogenmod man and the Samsung logo.
I have TWRP 2.5.0.0 installed with it, which I don't know how is possible being that the file systems are incompatible, so unless I used Odin to install CM10.1, I don't know how I did it without installing Clockworkmod Recovery over TWRP.
I've been trying to fix it for a couple days now (I'm kicking myself for not getting around to posting here sooner). When I go into TWRP it asks me for a password (which I've never set, I assume it's asking me because that's all it knows to do when the file system is incompatible), which I click cancel at every time, and when I try to do just about anything (including installing new ROMs or recoveries from within TWRP) it gets errors when trying to mount any partitions on the device, so I can't change anything on the phone at all.
I've tried re-installing TWRP AND Clockworkmod Recovery with Odin, and they succeed, but when the phone tries to reboot, the screen just turns off and nothing happens, and I have to take the battery out to do anything else.
So right now I'm totally screwed unless I can fix this thing. I'd like to not have to drop 200 on a Nexus 4 after only a year or having this phone I bought brand new, especially with the Nexus 5 already coming out later this year...can somebody help me???
EDIT: I should clarify that I can access recovery and download mode
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
FoxTrotz said:
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
Click to expand...
Click to collapse
I should've clarified that I've tried this with a bunch of roms, and it just shows SBA2 in the status box forever. I left it for a full hour before and it never changed.
According to this page http://www.alliance-rom.com/community/wiki/bricked-android/ reformating your external sd card may help. It also links to something I personally have never heard of but apparently this: http://forum.xda-developers.com/showthread.php?p=15330252 can help unbrick any samsung phone that's flashable with odin.