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..
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
So just to state the lead up to the unbootable phone.
Condensed version:
Flashed to Bio360 (ONLY working rom that was running for me thus far)
After a week of use, phone would boot for 5 seconds until screen turned pixelated
reflashed but did nothing
flashed to ICS using download mode again and worked but with limited function as when I first flashed ICS before Bio360
flashed using CWM6 back to Bio360 but still same problem
now will not boot into CWM6 and gets the pixelated screen either way
WILL go into download mode so I tried a few more ROMs to hopefully write over whatever issue there is with the software but nothing
reflashed using ODIN the CWM to 5 and 6 but same problem (will not load to CWM at all now
tried a few more times in the precise order as the first time I ever got the phone working with Bio360 (STILL a messaged up screen)
More detailed account of things:
I originally tried updating to the ICS upgrade a few weeks ago but got stuck on the boot screen and other issues. I finally flashed the CWM6 and updated the rom via that to the Bio360 rom. I finally had a working phone again after countless hours of trying to get it working. I locked my screen after timeout to a pin number but actually found it was a pain in the behind so tried to switch back. However I used the 'settings' feature which was present on the home screen after boot that comes with the Bio360. Then I deleted the icon an could no longer find the one that I was originally using, but found the other newer icon in the applications. So I took the lock feature off. Though it did nothing and the phone still required the pin. I tried changing it etc etc etc and nothing worked.
So, I flashed the Bio360 rom again and tried to start fresh, only to find that most of the settings that I originally were using before the re-flash were still present. This lead me to believe the settings are not completely wiped and flashing through CWM6 does not do a pristine clean update. Then I read that I should have to clear any and all settings by factory reset, clear cache, partition or whatever other clear functions I found within CWM6. So I did that and everything was back in good order again.
That is until I woke up 3 days ago and found my phone 'bricked'. Not literally as I am told it is almost impossible to brick one of these. Upon rebooting the phone I found that it was booting to the Samsung logo and after about 5 seconds, the screen becomes pixelated with red and green colours, sometimes lines all over. The longer I leave it, the more the screen becomes a wash out.
So I tried flashing the rom again using CWM6 hoping this would fix, but the same thing occured. So I tried to use CWM5 hoping that would fix it but still the same. I tried flashing back to gingerbread, then ICS, then Bio360 as I originally did to get the phone working with Bio360 but the only thing that I can do now is boot into download mode. Anything else causes the screen to become pixelated and wil not boot past the messed up screen no matter how long I leave it.
I searched for other threads but only found threads based on a single large pixel or a physically damaged screen. However, the screen is still functional as when I boot to download mode or just before the screen becomes pixelated, everything looks great. Plus there was one time when I flashed to ICS I got into the blank screen with limited functional capacity as when I first flashed ICS and the pixelated screen disappeared. So this leads me to believe this is a software issue.
I believe that there is an issue with files being left behind that are corrupted or something similar but I cannot even boot to CWM in order to clear everything possible.
ANY IDEAS? I have explored every option that my limited understanding of software could.
picture of what it looks like
This is a crappy picture from my old phone of something like what it looks like.
https://plus.google.com/photos/111944628817208100010/albums/5793637254528885841
This is a capture after it was turned off even and I plugged it into my computer, displaying the battery charging animation, though turned pixelated after a few seconds.
My gut says hardware damage, like something inside the Tegra itself is fried, ESPECIALLY since it's happening sometimes while still in the bootloader (charging animation).
Try Kies emergency recovery. If it flashes successfully but still won't boot, or glitches out like this during the flash, you'll have to start the RMA process.
I am unsure if it would be a hardware issue though since the screen is fine during the 'download mode' and did boot into the stock recovery after a flash a while back, then flipped back to not getting past the Samsung logo and pixelating again.
Would I be able to load the download mode portion of the phone if it was a hardware issue?
I ask because my gut says the opposite.
flashing CWM 6 causes my phone to be unbootable and pixelated screen
So, I have tried to update the phone into whatever other ROM that I can possibly get working only to find out that after flashing a ROM that flashes the original recovery program included with Android, voilà! The phone works again and boots into the black screen with pull down menu. Back to square one for me.
Why would CWM6 be causing such a thing?
EaglesIII said:
So, I have tried to update the phone into whatever other ROM that I can possibly get working only to find out that after flashing a ROM that flashes the original recovery program included with Android, voilà! The phone works again and boots into the black screen with pull down menu. Back to square one for me.
Why would CWM6 be causing such a thing?
Click to expand...
Click to collapse
I'm on CWMR6 since the begining without any issue. Did you flash the touch or the non touch version ? Also whcih odin version are you using, maybe that makes a difference. The 1.82 and 1.85 are tested to be working fine with both cwmr 5 and 6. Also by reading your thread is seems you've never been able to flash through ICS one click, if possible try doing that.
ninthsense said:
I'm on CWMR6 since the begining without any issue. Did you flash the touch or the non touch version ? Also whcih odin version are you using, maybe that makes a difference. The 1.82 and 1.85 are tested to be working fine with both cwmr 5 and 6. Also by reading your thread is seems you've never been able to flash through ICS one click, if possible try doing that.
Click to expand...
Click to collapse
I have been using the cwm5/6 touch and non touch. I have tried flashing them both. I have been using the most suggested version of ODIN 1.85 to flash. I do not think that it would make a difference as to which ODIN version I use, but then again I am quite ignorant on software.
The first thing that I did was tried the flashing using the one click method. I could only get to a black screen with the pull down menu containing the turn wifi on/off etc. I read that the problem may be permissions but I have tried that using the CWM when it worked and I was still stuck at the black screen with pull down menu. Without CWM I have no way of doing anything really since everything is in zip form and without CWM you cant use the zips.
EaglesIII said:
I have been using the cwm5/6 touch and non touch. I have tried flashing them both. I have been using the most suggested version of ODIN 1.85 to flash. I do not think that it would make a difference as to which ODIN version I use, but then again I am quite ignorant on software.
The first thing that I did was tried the flashing using the one click method. I could only get to a black screen with the pull down menu containing the turn wifi on/off etc. I read that the problem may be permissions but I have tried that using the CWM when it worked and I was still stuck at the black screen with pull down menu. Without CWM I have no way of doing anything really since everything is in zip form and without CWM you cant use the zips.
Click to expand...
Click to collapse
Well then probably a logcat output to a developer would help understand the problem you're facing. Find some knowledgeable developer who can help you read the logcat and find the issue. Or post it here and maybe somebody would give you a clue.
EaglesIII said:
So just to state the lead up to the unbootable phone.
Condensed version:
Flashed to Bio360 (ONLY working rom that was running for me thus far)
After a week of use, phone would boot for 5 seconds until screen turned pixelated
reflashed but did nothing
flashed to ICS using download mode again and worked but with limited function as when I first flashed ICS before Bio360
flashed using CWM6 back to Bio360 but still same problem
now will not boot into CWM6 and gets the pixelated screen either way
WILL go into download mode so I tried a few more ROMs to hopefully write over whatever issue there is with the software but nothing
reflashed using ODIN the CWM to 5 and 6 but same problem (will not load to CWM at all now
tried a few more times in the precise order as the first time I ever got the phone working with Bio360 (STILL a messaged up screen)
More detailed account of things:
I originally tried updating to the ICS upgrade a few weeks ago but got stuck on the boot screen and other issues. I finally flashed the CWM6 and updated the rom via that to the Bio360 rom. I finally had a working phone again after countless hours of trying to get it working. I locked my screen after timeout to a pin number but actually found it was a pain in the behind so tried to switch back. However I used the 'settings' feature which was present on the home screen after boot that comes with the Bio360. Then I deleted the icon an could no longer find the one that I was originally using, but found the other newer icon in the applications. So I took the lock feature off. Though it did nothing and the phone still required the pin. I tried changing it etc etc etc and nothing worked.
So, I flashed the Bio360 rom again and tried to start fresh, only to find that most of the settings that I originally were using before the re-flash were still present. This lead me to believe the settings are not completely wiped and flashing through CWM6 does not do a pristine clean update. Then I read that I should have to clear any and all settings by factory reset, clear cache, partition or whatever other clear functions I found within CWM6. So I did that and everything was back in good order again.
That is until I woke up 3 days ago and found my phone 'bricked'. Not literally as I am told it is almost impossible to brick one of these. Upon rebooting the phone I found that it was booting to the Samsung logo and after about 5 seconds, the screen becomes pixelated with red and green colours, sometimes lines all over. The longer I leave it, the more the screen becomes a wash out.
So I tried flashing the rom again using CWM6 hoping this would fix, but the same thing occured. So I tried to use CWM5 hoping that would fix it but still the same. I tried flashing back to gingerbread, then ICS, then Bio360 as I originally did to get the phone working with Bio360 but the only thing that I can do now is boot into download mode. Anything else causes the screen to become pixelated and wil not boot past the messed up screen no matter how long I leave it.
I searched for other threads but only found threads based on a single large pixel or a physically damaged screen. However, the screen is still functional as when I boot to download mode or just before the screen becomes pixelated, everything looks great. Plus there was one time when I flashed to ICS I got into the blank screen with limited functional capacity as when I first flashed ICS and the pixelated screen disappeared. So this leads me to believe this is a software issue.
I believe that there is an issue with files being left behind that are corrupted or something similar but I cannot even boot to CWM in order to clear everything possible.
ANY IDEAS? I have explored every option that my limited understanding of software could.
Click to expand...
Click to collapse
I have the same problem, i bought mine in ebay, (i live outside USA so i cant get money back) my problem start when i try to install a apk, then, i try to restore with wipe in cwm (sometimes works, sometimes no) and eventually, only download mode work. I dont know what i do, but in one of my trys, ICS 4.04 works everything, but i was network lock,i try to downgrade to Gingerbread and the problem come back, i dont know what to do, i feel like i waste te money.
PD: I have the roger version
EDIT: I just flashed ICS from ATT And works, but i w ould like to root and i cant, every time that i flash CWM, the problem come back
EDIT 2: I use the one click to install ICS from att and works, its seem the problem is when i use a custom rom or the CWM, dont know why, its seems that is not hardware because ICS works perfect, but Every custom rom or CWM, cause the problem
Maybe is there a way torecreate all the internal partition, i dont know, or something like that, to make a clean install, I am starting to regret for buying this phone, maybe the problem is because is from rogers (a security rule maybe?)
Sorry for my english
EaglesIII : your phone has hardware malfunction.
It is basically trash.
*sorry*
Sent from my SGH-I927 using xda app-developers app
ericpeacock79 said:
EaglesIII : your phone has hardware malfunction.
It is basically trash.
*sorry*
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
I dont Know, its happen similar to me, but if i use ICS from ATT, everything works right
---------- Post added at 03:05 AM ---------- Previous post was at 02:45 AM ----------
Ok, i learned something, when a flash the Gingerbread version, there is a error while booting (the first time that boot lik recovery) , the error is can't access to /system/csc/ATT/system/
When i use the ICS from ATT, that doesnt happen, maybe that is the problem? i dont know, maybe someone can tell us what are these files
There is a working solution, http://forum.xda-developers.com/showthread.php?t=1953672 thanks to Rawr0w0,its works when you flash in that order, my phone is rooted and full working in ICS, i hope that helps you
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.
Hello everyone, so the other day i went out to sell my Xperia S and when i went to seal the deal i literally could not do the factory reset. I went into the menu, started it, it rebooted and it ended up on a black screen after "rebooting" with the blue light on indefinitely. If i hard reseted it, my google account and settings were still in it. Tried to log into recovery, and the effect is the same, blue led on black screen but nothing else, and same effect from the Android device manager.
Since Sony update service is not supported it exits(it always worked with that before) and the PC companion tells me im running custom rom, and exiting instead of flashing the factory image...
I tried to reflash the recovery through adb but no success.
I'm running the unofficial PA 4.6 beta from this forum, and had the TWRP-CWM dual recovery(which looked like has been rewrote to be CWM purely by the PA OTAs)
So any ideas what i can do? In this form, whit all the data on it, I can't even give it away for free, not to mention asking money for it...
TheGregButcher said:
Hello everyone, so the other day i went out to sell my Xperia S and when i went to seal the deal i literally could not do the factory reset. I went into the menu, started it, it rebooted and it ended up on a black screen after "rebooting" with the blue light on indefinitely. If i hard reseted it, my google account and settings were still in it. Tried to log into recovery, and the effect is the same, blue led on black screen but nothing else, and same effect from the Android device manager.
Since Sony update service is not supported it exits(it always worked with that before) and the PC companion tells me im running custom rom, and exiting instead of flashing the factory image...
I tried to reflash the recovery through adb but no success.
I'm running the unofficial PA 4.6 beta from this forum, and had the TWRP-CWM dual recovery(which looked like has been rewrote to be CWM purely by the PA OTAs)
So any ideas what i can do? In this form, whit all the data on it, I can't even give it away for free, not to mention asking money for it...
Click to expand...
Click to collapse
Did You try flashing a stock ftf using flashtool?
The problem is that it doesn't even get into recovery, like I said I reboot into recovery and it drops me on a black screen (lit) with the blue led on, but neither cwm not twrp comes in and it just idles there indefinitely.
Mirhawk said:
Did You try flashing a stock ftf using flashtool?
Click to expand...
Click to collapse
Disregard my first reply, I totally missed your point on it... Will try flash tool tomorrow!