Pretty sure I bricked my phone. I tried to do a factory data reset, and it never would boot back up. I then tried flashing the mini note 2 rom, and hellraising it for compatibility with sirya kernel, still no luck. However when I boot into recovery I do have the sirya recovery version. So I don't think this is something I'm stuck with.
When I get home from school, I am going to try and use Odin and flash a stock rom, is this the correct option I should move forward with?
Thanks
Sent from my PantechP9070 using xda app-developers app
Spewed said:
Pretty sure I bricked my phone. I tried to do a factory data reset, and it never would boot back up. I then tried flashing the mini note 2 rom, and hellraising it for compatibility with sirya kernel, still no luck. However when I boot into recovery I do have the sirya recovery version. So I don't think this is something I'm stuck with.
When I get home from school, I am going to try and use Odin and flash a stock rom, is this the correct option I should move forward with?
Thanks
Sent from my PantechP9070 using xda app-developers app
Click to expand...
Click to collapse
All you need to do is boot into cwm and flash another rom or a backup.
Thanks will do that when I get home.
Sent from my PantechP9070 using xda app-developers app
Once again, flashed a new rom, this time I flashed SHOSTOCK. Still stuck at Samsung Galaxy SII boot screen.
Again, I want to state that it got in this shape because I went into recovery and tried wipe data/factory reset. Who knew it would cause such a problem doing this.
I'm still able to boot into recovery, and once again, it flashes the recovery version that comes with the rom I flashed, in this case the SHOstock rom.
Going to try and use Odin now. Will come back if it does not work.
factory reset in recovery is the way that you install a new rom....that in itself doesnt cause issues
Pirateghost said:
factory reset in recovery is the way that you install a new rom....that in itself doesnt cause issues
Click to expand...
Click to collapse
Like I said, it got stuck at Formatting/Data", then again at the Samsung Galaxy SII screen and just never recovered. I must be dealing with some super strange issue then. I've never had this happen, with the 10 phones I've rooted, unlocked and put roms on. This is kind of ridiculous. I wonder if this could be in someway hardware related? It took a pretty good fall before I attempted any of this and the screen cracked. I decided then I would use this particular phone for romming, etc before replacing it with a new s2, I guess I wont be putting a rom on the new s2 that I get either.
Any ideas?
After, doing the Odin install, It claims on Odin it passed, it gets in the recovery portion where it copies the kernel and updates the packaged, and I ge t"Multi-csc applied failed. E: Failed to mount / cache "invalid argument", along with numerous other errors along the same lines.
Edit:, after the Odin install, everytime I reboot it goes back to "Deleting cryption meta Data" #manual mode#. Not sure what to think of this. Everything I try fails.
Even when this process finishes, and gives me the option of rebooting the phone now, it goes right back to this same screen. I am officially stumped. From there I try to do the Factory reset, once again gets stuck at Formatting /data
What was your phone running when you performed the wipe data/factory reset that caused the initial problem? Was it stock 4.0.3 by any chance?
Spewed said:
Like I said, it got stuck at Formatting/Data", then again at the Samsung Galaxy SII screen and just never recovered. I must be dealing with some super strange issue then. I've never had this happen, with the 10 phones I've rooted, unlocked and put roms on. This is kind of ridiculous. I wonder if this could be in someway hardware related? It took a pretty good fall before I attempted any of this and the screen cracked. I decided then I would use this particular phone for romming, etc before replacing it with a new s2, I guess I wont be putting a rom on the new s2 that I get either.
Any ideas?
After, doing the Odin install, It claims on Odin it passed, it gets in the recovery portion where it copies the kernel and updates the packaged, and I ge t"Multi-csc applied failed. E: Failed to mount / cache "invalid argument", along with numerous other errors along the same lines.
Edit:, after the Odin install, everytime I reboot it goes back to "Deleting cryption meta Data" #manual mode#. Not sure what to think of this. Everything I try fails.
Even when this process finishes, and gives me the option of rebooting the phone now, it goes right back to this same screen. I am officially stumped. From there I try to do the Factory reset, once again gets stuck at Formatting /data
Click to expand...
Click to collapse
Sounds like the emmc cap erase brick bug.
Sent from my Apple IIe
creepyncrawly said:
What was your phone running when you performed the wipe data/factory reset that caused the initial problem? Was it stock 4.0.3 by any chance?
Click to expand...
Click to collapse
It was on stock 4.0.4, I believe.
billyjed said:
Sounds like the emmc cap erase brick bug.
Sent from my Apple IIe
Click to expand...
Click to collapse
Any ideas how to fix that?
If it is the emmc bug..... New phone
Since you can flash in Odin and get to recovery it should not be that.
How about going to the Siyah kernel and wiping inside of that. Mr. Cook has a cwm package you can flash to wipe everything at once.
Sent from my SGH-I777 using xda premium
Spewed said:
Any ideas how to fix that?
Click to expand...
Click to collapse
No. If it is actually memory damage, you'd need to replace the memory, which means replacing the main board. But I'm not convinced that is what you have.
My first thought was eMMC memory damage due to the 4.0.3 kernel. It may be that the eMMC brick bug was still present in the 4.0.4 kernel as well. If so, memory damage *could* be the problem, but it's not conclusive by any measure. There were actually very few confirmed reports of memory damage, although many people used the 4.0.3 and more recently 4.0.4 kernel as their daily driver. But performing a wipe data/factory reset was one of the actions that might have caused memory damage if it was going to happen.
Since you now have the "deleting cryption meta data" error message, I'm not sure the problem is memory damage, and I would not suggest giving up just yet. Look at this thread, specifically post #2 and post #4. Follow those instructions, and see if that gets your phone going again.
creepyncrawly said:
No. If it is actually memory damage, you'd need to replace the memory, which means replacing the main board. But I'm not convinced that is what you have.
My first thought was eMMC memory damage due to the 4.0.3 kernel. It may be that the eMMC brick bug was still present in the 4.0.4 kernel as well. If so, memory damage *could* be the problem, but it's not conclusive by any measure. There were actually very few confirmed reports of memory damage, although many people used the 4.0.3 and more recently 4.0.4 kernel as their daily driver. But performing a wipe data/factory reset was one of the actions that might have caused memory damage if it was going to happen.
Since you now have the "deleting cryption meta data" error message, I'm not sure the problem is memory damage, and I would not suggest giving up just yet. Look at this thread, specifically post #2 and post #4. Follow those instructions, and see if that gets your phone going again.
Click to expand...
Click to collapse
Thanks, going to give this a try. I did something similar to this with the Odin 1 click installer, but this has a few additional steps, I'll try this when I get the chance and let you guys know what happens. Directions seem a little strange, but I'm going to try and figure it out when my wife gets home and can take over child watching duties for me.
Thanks again, hope this work.
Related
Hi Guys
I flashed the leaked ICS but hate it. Can I flash to stock GB via Odin? What about the baseband versions etc.., would it matter?
Sorry, I read another thread but it's unclear and I want to avoid bricking. Thanks
As far as what I've read you can flash stock from Odin or even use CWM to a previous nandroid of gingerbread.
Sent from my SAMSUNG-SGH-I717 using XDA
If you got your Note from AT&T, simply flash this stock ODIN:
http://forum.xda-developers.com/showthread.php?t=1506330
I went from ICS back to Gb cause I missed the tethering and it was easy. Just make sure you clear the caches and all should be well.
Thanks.. I was worried of the different baseband would have any adverse effect, but it doesn't sound like it will. I'll give it a try.
I Odin'd back to stock and I'm in a world of ****. My phone cant do anything, it just gets stuck on every swipe and reboots about every 5 minutes. Does anyone have any ideas?
Mines fine..only baseband is different, phone works.
Before I Odin to stock, I booted into recovery, factory reset and wiped cache. Odin, then booted into recovery and performed another factory reset and wiped cache again.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
beall49 said:
I Odin'd back to stock and I'm in a world of ****. My phone cant do anything, it just gets stuck on every swipe and reboots about every 5 minutes. Does anyone have any ideas?
Click to expand...
Click to collapse
Try factory wipe/format usb from within GB..it may help.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
beall49 said:
I Odin'd back to stock and I'm in a world of ****. My phone cant do anything, it just gets stuck on every swipe and reboots about every 5 minutes. Does anyone have any ideas?
Click to expand...
Click to collapse
figured it out. My post is below.
lindenhurst said:
You get it figured out? I did the same thing. . My old apps still there. I can tell it is gingerbread, but nothing works now. I hope you got your figured out!!
When I boot into recovery I get the screen that tells me to use the up and down keys and when I choose factory wipe, and press power button, nothing happebs. If I hold it down eventually the phone shuts off. When i restart it, nothing changed.
Click to expand...
Click to collapse
I had to revert from ICS to GB yesterday and, even tho I am on Telus, I had success by flashing the pda-odin-att-stock.rar image
I can't post links .. I'm too new. But literally.. google what's bolded above and you will find the hotfile link.
It replaced everything (including the recovery) ... FULL system image. Solved everything and brought me back to 100% stock.
So yes, I lost my root and my CWM recovery software.. but it got my phone working again.. I can reflash CWM and re-root as I need.
After the install, wipe cache, factory reset etc.
I too flashed the stock ATT rom but like the previous poster, it gave me a phone which started up but wouldn't work. When I tried to get into recovery mode, it went to a screen with the recovery mode stuff at the top, but with a yellow warning sign in the middle and some words about manual mode, and it would not let me do a wipe or reset.
Here is what I just did that did work.
I flashed the recovery-i717-cwm-b4.tar file with odin. This worked and allowed me to get into the "proper" recovery mode to do a wipe and factory reset, as well as a cache wipe. I then reflashed tieh the stock ATT rom, and my phone now is back to stock.
This is the second phone this has happened to, so I'm inclined to believe the problem resides in either the recovery package or there is no way to go from ICS to stock. Here's what I did and what the result was.
1. Initial phone was having hardware issues. I needed to return it to the warranty exchange depot, so I went to flash the no BL file that you can download from the recovery thread. Everything indicated that it flashed just fine. Phone reboots after the process and it gets the the "rethink Everything" splash screen and just sits there. After a minute, it reboots the phone again. Does the same thing. I take the phone in and get it swapped out under warranty.
2. Load CM9 on new phone and notice that GPS doesn't work. Everyone else says theirs works for the same nightly (5/22), so obviously it's my phone that's the problem or a bad flash. Flash a new nightly (5/29) and GPS still doesn't work. I want to flash back to stock to ensure that it's the hardware that's the problem, not the software. I download the most current recovery NO BL file from the recovery thread to ensure I have a good one. Flash it and the exact same thing happens. I get the splash screen then a reboot.
So now the question is, does flashing ICS permanently make it so you can't flash back? Does ICS work fine, but for some reason CM9 doesnt? Has anyone else done this without a problem? If so, what did you do because 2 phones 'bricking' like this isn't convinsing me that it can be done.
stalked_r/t said:
This is the second phone this has happened to, so I'm inclined to believe the problem resides in either the recovery package or there is no way to go from ICS to stock. Here's what I did and what the result was.
1. Initial phone was having hardware issues. I needed to return it to the warranty exchange depot, so I went to flash the no BL file that you can download from the recovery thread. Everything indicated that it flashed just fine. Phone reboots after the process and it gets the the "rethink Everything" splash screen and just sits there. After a minute, it reboots the phone again. Does the same thing. I take the phone in and get it swapped out under warranty.
2. Load CM9 on new phone and notice that GPS doesn't work. Everyone else says theirs works for the same nightly (5/22), so obviously it's my phone that's the problem or a bad flash. Flash a new nightly (5/29) and GPS still doesn't work. I want to flash back to stock to ensure that it's the hardware that's the problem, not the software. I download the most current recovery NO BL file from the recovery thread to ensure I have a good one. Flash it and the exact same thing happens. I get the splash screen then a reboot.
So now the question is, does flashing ICS permanently make it so you can't flash back? Does ICS work fine, but for some reason CM9 doesnt? Has anyone else done this without a problem? If so, what did you do because 2 phones 'bricking' like this isn't convinsing me that it can be done.
Click to expand...
Click to collapse
I know it works, I just used it the other day to go from ics to gb. Did you do a factory reset after flashing? Make sure you have your sdcard backed up before you use stock recovery.
Sent from my SGH-I777 using xda premium
nakedninja42 said:
I know it works, I just used it the other day to go from ics to gb. Did you do a factory reset after flashing? Make sure you have your sdcard backed up before you use stock recovery.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
by factory reset, you mean from the recovery console?
nakedninja42 said:
I know it works, I just used it the other day to go from ics to gb. Did you do a factory reset after flashing? Make sure you have your sdcard backed up before you use stock recovery.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok. You may now mock me. I did a factory reset and it worked. Feel like such a noob.
nothing to see here folks. Move along. Red, you can shut 'er down.
stalked_r/t said:
Ok. You may now mock me. I did a factory reset and it worked. Feel like such a noob.
nothing to see here folks. Move along. Red, you can shut 'er down.
Click to expand...
Click to collapse
No one would mock you over this. It is your experience.
Next time, when somebody hit the same or similar problem, do help them.
Friendly reminder.. If you can start your title with [q], it probably belongs in QA...
Mock mock mock!
Great to know, this may not be posted and is only available as "common knowledge". You sir have made this solution available to anyone searching for it. Thank you!
Clay
Sent from my SGH-I777 using XDA
Here's the fact
1. I was running the 12-31-13 CM11 Nightly with KToonz 12-21 Kernel.
2. I had some problem with the screen not turning on after I accept a call. It's been going on for a few months now, despite doing full wipes in between, so I decided I was gonna just do another wipe and hope that it would somehow solves itself.
3. While I was in TWRP 2.5.2.X , I did factory reset
4. I also wipe /system
5. I flashed CM11 1-1-14 / 12-30 GApps / KTkernel / BootAnimation / SuperSU 1.86
6. During the last portion, I get some running message that it failed to mount E:/ something something & Partition and such
7. Thinking it was a fluke, I pressed reboot and... bootlooped at the Samsung logo screen
8. I Power + Vol UP back into Recovery and flashed the 12-31 CM11 nightly, plus GApps etc,
9. Got the same strings of messages telling that it failed to mount partition and E:/ and /data/ and something lost and found/
10. I rebooted and... Bootlooped at the Samsung logo.
11. I tried to get back into recovery and has been unable to.The little blue "Recovery Booting" seems to appear for a very short time before the phone rebooted again. Seems like it's not there anymore.
Part of me thinks that perhaps the phone's internal memory failed. So far the only thing I can do with it is charge the phone.
Anyone with any knowledge of this, please help.
you gotta go to back odin to get a recovery back on your phone. Also the screen not turning on has been an AOSP issue for awhile, it's not just you and reflashing won't do anything to fix it.
Sent from my CIA sanctioned device
joshm.1219 said:
you gotta go to back odin to get a recovery back on your phone. Also the screen not turning on has been an AOSP issue for awhile, it's not just you and reflashing won't do anything to fix it.
Sent from my CIA sanctioned device
Click to expand...
Click to collapse
What would I do with another recovery? Is the one I have on it now doesn't work anymore?
asianrage said:
What would I do with another recovery? Is the one I have on it now doesn't work anymore?
Click to expand...
Click to collapse
well if you can't boot into it, it's not working right?
asianrage said:
What would I do with another recovery? Is the one I have on it now doesn't work anymore?
Click to expand...
Click to collapse
Just a note keep in mind TWRP is not recommended for CM11. Also I am lucky I have MDK device and a version of the no data wipe stock install, whenever things go wonky (like bootloop on Samsung Logo) I Odin back to stock. make sure the phone works, then restart from scratch and re-root, re-install recovery and reflash CM. I am not super technical so sometimes it can take about 1-2 hours from screwing up the phone to going back to having a working CM11 GS4.
All Hail invisiblek
http://forum.xda-developers.com/showthread.php?t=2559335
stein5830 said:
Just a note keep in mind TWRP is not recommended for CM11. Also I am lucky I have MDK device and a version of the no data wipe stock install, whenever things go wonky (like bootloop on Samsung Logo) I Odin back to stock. make sure the phone works, then restart from scratch and re-root, re-install recovery and reflash CM. I am not super technical so sometimes it can take about 1-2 hours from screwing up the phone to going back to having a working CM11 GS4.
All Hail invisiblek
http://forum.xda-developers.com/showthread.php?t=2559335
Click to expand...
Click to collapse
Thanks for the reply. I've already started the process to flash back to stock MDK. I've been using TWRP for a while and have always been annoyed at how long it'll take to go past the logo screen (if I didn't give up and pulled the battery). Wish me luck.
I will be eternally grateful if you can help me.
So half an hour ago I was browsing the Internet on my phone when it suddenly turned off. Then it started to start at the Galaxy I9300GT black screen, and booting on that black screen. And the biggest problem is that I cant access to the Recovery Menu (I have latest Philz)
I have not tried to remove the battery, nor accessing the Download Menu, since I am in class now and I cant return to home in about 4 hours. Also, I was using NeatRom 6.3, boeffla kernel 5.1 beta 17, and in the last flashing I formatted the internal SD card, so basically I did a clean install. I can not guess what is happening. This is similar to when I had a brick installing some Xposed software, and I solved it installing old CWM recovery, which I could access into, and basically wiping the hell of it. Is this a problem of Xposed....Or am I facing a SDS..in Android 4.3....
Partition corruption during the unplanned shut down, without recovery you will need Odin to flash a full stock rom or philz.
If you are lucky the emmc chip is still okay, this exact same thing happened to me once.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Partition corruption during the unplanned shut down, without recovery you will need Odin to flash a full stock rom or philz.
If you are lucky the emmc chip is still okay, this exact same thing happened to me once.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Luckily I can access to the Recovery Menu....but for some seconds. Its weird. When I am in the Select Option screen (the one which says if you proceed or you cancel and restart the phone) it shows for some seconds until it then starts again at the title screen, like it autoreboots. Also, there is some insane battery drain, because the back of my phone is somewhat hot. I tried to remove the battery, and plug it again, and although I could not access to the recovery menu for a while later I could get back to the recovery...until it fade off like I previously describe.
Luckily I too have a full stock ROM stored in my home computer. But as I said to you before I had Philz installed and it doesnt show up. So I am planning to install the old Clockworkmod, because the last time I experienced something similar it worked for me.
So, basically, do you think I should be fast and get to the Odin menu before the Select Option screen fades off and gets back to the booting title? And also, what can I do to prevent partition corruption? Is there a way to avoid having that problem again? Mind that before flashing the ROM I formatted the SD card, so it was clean install...
For these moments I will keep the battery on the phone, I dont want more unexpected problems, but I fear for it, since it is consuming battery slowly....
And, if it happens that the emmc chip is not okay...what could I do?
You mean download mode, where you volume up to connect with Odin. If download mode is weird then you may have bigger problems.
To prevent future partition corruption you need to avoid unplanned shut downs -kernel panic due to mods are a likely cause.
I would suggest removing the battery until you can use Odin, there is no point in leaving it to drain.
If the emmc chip is dead then a new motherboard is required.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
You mean download mode, where you volume up to connect with Odin. If download mode is weird then you may have bigger problems.
To prevent future partition corruption you need to avoid unplanned shut downs -kernel panic due to mods are a likely cause.
I would suggest removing the battery until you can use Odin, there is no point in leaving it to drain.
If the emmc chip is dead then a new motherboard is required.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Dude.....I dont know what happened....its REAAAAAAAAAAAAALLY WEIRD.
I REPAIRED IT BY FLASHING CWM.
I could access to Odin, which was Version 3.04 "Model Name ", and then flashed the Clockworkmod, version 6.0.3.2.
And then automatically the phone booted again! I could get to the Neat ROM working again!
Sincerely, I dont know it this was a kernel problem, seeing as how an old CWM got the phone working again. I just cant explain it. I hope you can, because I am now confused and scared of changing to another recovery, seeing how this old CWM works even better than Philz.
I even tried to reboot the phone twice, and it has worked. Strangely the boot sound from Neat ROM has been activated. CWM asked me if I wanted to disable flash to stock recovery option, and I ticked no. It then followed that it may flash stock recovery and lose root access, and event then I ticked no. But when I restarted the ROM I had the root access, and as I said I rebooted twice to recovery, and had CWM, so it was kinda...ok. Maybe Neat ROM doesnt flash the stock Sammy kernel as default option, who knows...
I havent done any wipe, seeing as this is working wonderfully again, without any problem whatsoever...which is reeeally weird. Yeah, I am shocked that I somewhat magically fixed it. Normally this takes about 2 hours...lol.
Also, I have more questions for you. You talked about unplanned shut downs, due to kernel panic because of mods installed. Can you explain this kernel panic thing to me, or share with me a link to a post that explains this problem? And more, do you know about a kernel that doesnt "panic" so much? I have Boeffla 5.1 beta 17, but I am questionig keeping using this, since this problem...
Or maybe it was a panic caused by the recovery? Can recoveries origin such problems? And what recovery do you recommend? Because CWM seems rock stable to me...
Oh, and thanks for your help. I removed the battery as you said...and now that my phone is working again I could check that it was at 20% battery...thank you, I could save a little battery for an emergency flashing thanks to you :good:
Also, this morning while turning on the phone I noticed that there was no boot sound when showing the Neat ROM animation...why suddenly the ROM stopped using the boot sound, when last night it was active after flashing the CWM recovery? I even rebooted the phone twice that night and the sound was activated...but not this morning, why?
Actually boot sound is not a very important feature for me but I am puzzled of why it was working before and not now, and that without touching any boot options....
Check if you still have boot sound PowerOn.ogg in system/ media /audio/ui
JJEgan said:
Check if you still have boot sound PowerOn.ogg in system/ media /audio/ui
Click to expand...
Click to collapse
Yes, it is there, as you said.
I have a similar problem .. what exactly fixed this?
flashing an old CWM? mind guide me to that ...
I know I sound like a total noob for the title alone, but I think this is something more complicated than you may have probably thought. My father gave me a ring, but my phone was locked back then. Now, I tried to answer the call but the screen was black and blank but my back and menu keys were lighting up. But I had to "cancel the call", but I wanted to know the time back then, so I proceeded to try and unlock the phone but to no avail. So, I had to try and take out the battery since my phone probably had crashed or something. Now, upon rebooting I'm now faced with a bootloop problem. I tried reflashing my rom, formatting /system and also flashing my previous Kitkat roms but still to no avail. Now, I do hope a kind soul can help me with this problem... please?
Flash a full stock firmware with Odin, boot into recovery and factory reset. Check for any error messages in recovery then test.
It sounds like a partition corrupted, hopefully not permanently damaging the emmc chip.
Sent from my GT-I9300 using Tapatalk
Thanks!
boomboomer said:
Flash a full stock firmware with Odin, boot into recovery and factory reset. Check for any error messages in recovery then test.
It sounds like a partition corrupted, hopefully not permanently damaging the emmc chip.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Will try, sir! Will reply once I'm done!
boomboomer said:
Flash a full stock firmware with Odin, boot into recovery and factory reset. Check for any error messages in recovery then test.
It sounds like a partition corrupted, hopefully not permanently damaging the emmc chip.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks, it worked!