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 ...
Related
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
dandrumheller said:
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
Phone has been plugged in the charger for awhile now...nothing.
AJ Newkirk said:
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
Click to expand...
Click to collapse
I only used a nandroid backup for restoring back to the stock rom. For everything else, I used CWM and a zip install.
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
AJ Newkirk said:
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
Click to expand...
Click to collapse
That's what I thought. Like I said, it started the flash but then look like it hung. The progress bar did not move at all. After a bit the phone turned off. What is hard locked-up? I do remember when I first plugged the charger in after the phone died/suspended it did vibrate.
creepyncrawly said:
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Click to expand...
Click to collapse
Phone is basically new. I tried leaving the battery out and holding down the vol keys and plugging into USB. Screen does nothing.
c0ldburn3r said:
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
Click to expand...
Click to collapse
As I posted above I only used Odin from the original rooting. Everything else was CWM.
I guess I need to find out how to make a jig and try that as my only remaining option??
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
w1209 said:
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
Click to expand...
Click to collapse
That's not what I want to hear
I just don't understand how this can happen. Even if lets say worse case scenario the rom is screwed, my battery dies during the update or whatever...I should still be able to get into CWM or at least download mode right?
It's very odd indeed considering MIUI doesn't have a bootloader included either, and according to CWM it flashed without any problems. The only other possibility I could think of is that the ROM got corrupted while copying onto the phone. I checked MD5 checksum after downloading onto my computer but not on my phone before flashing. Still, could a corrupt ROM without bootloader hardbrick the phone? I thought the SGS2 was supposed to be very hard to brick when not flashing something like a bootloader
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
If a USB jig doesn't work, I guess call up Samsung and play dumb? Worst thing that will happen is they'll send your phone back to you. Sorry to hear about your bad luck :/
Here's an odd idea... you didn't happen to get water in it, did you?
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
dayv said:
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
Click to expand...
Click to collapse
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
nakedninja42 said:
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
Click to expand...
Click to collapse
Not sure, but if your param.lfs got corrupted that could be your problem.
Sent from my SGH-I777 using XDA Premium HD app
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Yes....coincidence. I have flashed form UCLD3 to AOKP (and CM9) & back more than a few times without issue.
@avus_m3, w1209, and nakedninja42:
With three similar hard bricks, there is a patern. We should gather as much information as possible. What package did you use to put UCLD3 on the phone immediately before the bad flash? Also, exactly what parts did the AOKP or MIUI package that resulted in the bad flash contain?
I used the latest version posted in the thread (I think there is only one LD3 package?): hxxp://goo.im/devs/task650/SGH-I777/Task650_I777_UCLD3_signed.zip
(not allowed to post links yet)
Same for MIUI: hxxp://goo.im/devs/ktoonsez/downloads/miuiandroid_I777-2.4.13b.zip
(not allowed to post links yet)
I know for sure that the MIUI MD5 checksum matched after downloading to my computer. Will see what the MD5 checksum is of the file on my phone after I get it back from MTV. If it is the same there is a definite pattern. If not it was just bad luck and my fault for not verifying it on phone before flashing
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Just to be clear this did not happen to me directly - just responded as I remember reading somewhere about a battery dying during a flash and that person needing to get another battery to get their phone back to life - again the battery may not have anything to do with what happened hear.
But it does look like this happened to two people after flashing away from ld3 leak - though it just may be coincidental hardware issues. we will see if there are more people who have trouble after flashing the leak.
Sent from my SGH-I777 using XDA Premium HD app
Current issue
Odin recognizes phone. I can get to download mode. it turns off. Ive let it set for 24 plus hours prior to this and there is no change. It will stay on for 10 to 15 seconds then turn off.
I have repartitioned, put in a new pit and kernel. it will not stay on long enough to install a new ROM.
leading up to this i had a sleep of death issue. that progressively got worse. It would turn on and be fine tell it went to sleep i could use all the apps if i stopped and it went to sleep i would have to reboot. I had during this point cleared all the cache devlik etc. to no avail. i then decided to flash to stock. I got about 10 seconds into the ROM flash and it turned off. now I'm at the point described above.
This has been w/ and w/o sim and external flash memmory
Thank you for any suggestions and help.
How old is your battery, and what kernels have you experienced this with?
What is a quick recap of what you were running/tried while this SOD problem started occurring, seems related to the DL mode shutting off.
Battery is the orginal, but i have 2 batterys 2 vibes. i switch batteries every month or so due to im more battery heavy then my wife, i have used them both fully charged.
Icy Glitch or subzero, though i think it was Icy. i was running slim ics. this is the only kernel i have ever had a sod problem.
Only extra apps i have installed or had issue with, 1 kindle stopped working on me well b4 any of this happend around 3 weeks or so. i installed adilko. Also installed calorie counter and myfitness pal these are the only 2 that really can be related. I had started using myfp more then the other for cutting.
only run music for during work, eh and for books, no games. i use advanced task killer to kill extra apps, a couple times a day to save on battery,
otherwise phone calls and txting.
Can you boot to recovery mode? If you can, try a factory data reset. You could use adb to push a kernel zip to your internal sd and flash through cwm but only if you can actually boot into recovery mode. If that doesn't work you could try flashing a different kernel through odin. Kernels usually flash in less than 10 seconds in my experience.
Sent from my SGH-T959 using Tapatalk 2
I have already flashed a new kernel and pit.
i cannot get into recovery.
i can get on odin long enough to put a pit and kernal and repartition.
this made no change to my problem.
Have you tried flashing a custom kernel like Semaphore with CWM included and then try booting into CWM?
eksasol said:
Have you tried flashing a custom kernel like Semaphore with CWM included and then try booting into CWM?
Click to expand...
Click to collapse
flashed semaphore. was able toget into cwm for 10 seconds before it shut down on me. now at least for a few seconds i have cwm. wait a sec it kept rebooting into it i cleared dev init.d cache fixed permissions, i was able to mount my usb, still mounted for a few min i think it might be good. ill update, im thinking init.d was the culprit. ill update in 10 min or so to see if i can ge back on my phone.
Bankai247 said:
I have already flashed a new kernel and pit.
i cannot get into recovery.
i can get on odin long enough to put a pit and kernal and repartition.
this made no change to my problem.
Click to expand...
Click to collapse
I was meaning to flash a stock kernel only, then flash back to stock JFD. I'm pretty sure you don't load a pit file when flashing just a kernel but I could be wrong, it has been awhile since I flashed a kernel through odin.
Sent from my SGH-T959 using Tapatalk 2
So i have been able to finaly get back to stock yay. its staying on long enough to get there. im flashing it now. and its up. SO If anyone has a Download sod error,
1 turn odin set pit and semaphore.
2 download mode , check for sync
3 install from odin.
4 it will reboot into cwm clear everything.
5 i cleared davlik, cache, init.d, then wiped/factory reset/ then cleared nstools, init.d davlik cache and fixed permisions.
6 odin back to stock.
7 look at the stockness get sick puke in local trash receptor. find some amazing devs goodness of your choice. thank them and all the helpfull people on the xda forums.
thank you all for your help im back to stock no SOD im golden.
big time thanks to eksasol for the semaphore tip
Hi there,
i tried a lot of word combinations to get a thread with my specific problem but i didnt manage it to find one.
So here is the deal:
i have german galaxy s 2 (9100, bought in september 2011) and i flashed it last year with darkyrom HD something gingerbread-style.
so it was rooted and all that stuff.
it worked pretty fast and it was stable and it looked sleak.
Last year in November i put Ressurrection remix 3.x (dont know which version of it) on my phone.
It had a lot of crashes, freezes and while playing ingress it always drained around 20% of the battery within 10-20minutes.
So i stopped it. I put the last version of it 3.1.3. of it onto my phone with a full wipe, cache partition, factory reset onto my phones and the problems went keep going.
As an example:
-I couldnt access options where i can select ringtones or to see what is on the sd. it crashed and went back to the "main screen".
-Yesterday i tried around 15 roms, and nearly everything except militant rom keep crashing while iam installing them.
-Sometimes it crashes already while iam installing the rom, sometimes its after a couple of hours, that i cant access the rom any more.
-The newest problem is, that sometimes the power button doesnt respond, when i push it (in jelly bam)
Please explain, what iam missing or is my phone just broke?
It never fell down, no water or anything freaking other things.
I hope you can help me.
should i send it back or what is wrong?
i dnt knw bt samsung.. bt may b it happens coz of when ur changing ur rom gb to i cs or jb whole operating system is diff so u hav to format ur sd card to make it working.
Try that way too
Sent from my Xperia Neo V using xda app-developers app
Try changing kernel
Sent from my GT-i9100
sreehari.007 said:
i dnt knw bt samsung.. bt may b it happens coz of when ur changing ur rom gb to i cs or jb whole operating system is diff so u hav to format ur sd card to make it working.
Try that way too
Sent from my Xperia Neo V using xda app-developers app
Click to expand...
Click to collapse
so what do i have to do to make it work flawlessly?
i cant boot it right now without the power plug.... and the battery is at 90%....
so something is completely broken within the system....
jootanen said:
Try changing kernel
Sent from my GT-i9100
Click to expand...
Click to collapse
i thought the kernel is already included when you're installing one of the roms?
which one should i take?
or how wipe the whole system to have it like "out of the box"?
flash a stock ROM and see how it behaves.
Sent from the little guy
Sakujou_Kei said:
i thought the kernel is already included when you're installing one of the roms?
which one should i take?
or how wipe the whole system to have it like "out of the box"?
Click to expand...
Click to collapse
if you are rooted, you can try flashing NeatROM lite 4.2 based on LS8 and see how it behaves else flash official JB 4.1.2 using odin.
kmaq said:
if you are rooted, you can try flashing NeatROM lite 4.2 based on LS8 and see how it behaves else flash official JB 4.1.2 using odin.
Click to expand...
Click to collapse
ok, ill try that right now..
if not using odin and try to do something with my nand???
after cleaning and putting a stock rom on it and afterwards rooting it with cwm still the same problem: boot loop or while the first installation, it crashes.
so what to do?
just hang around with the stupid official one?
If you did everything from Factory reset to changing kernel, and everything is still bad like that. I think that there's something with your phone's hardware.
Sakujou_Kei said:
ok, ill try that right now..
if not using odin and try to do something with my nand???
after cleaning and putting a stock rom on it and afterwards rooting it with cwm still the same problem: boot loop or while the first installation, it crashes.
so what to do?
just hang around with the stupid official one?
Click to expand...
Click to collapse
after flashing the ROM via odin, reboot into recovery, wip/factory reset and then go in to mount & storage, make sure system, data and sd cards (internal & external if any) are all mounted if not mount it and reboot.
kmaq said:
after flashing the ROM via odin, reboot into recovery, wip/factory reset and then go in to mount & storage, make sure system, data and sd cards (internal & external if any) are all mounted if not mount it and reboot.
Click to expand...
Click to collapse
well, i tried that. still nothing. it crashes or i have a bootloop.
so whats up with this phone?
so except the stock rom, where i can boot into it, all custom firmwares just crash or work for a while and then they'll crash.
i dont get this.
it started just days ago, now i dont even can use anything....
Sakujou_Kei said:
well, i tried that. still nothing. it crashes or i have a bootloop.
so whats up with this phone?
so except the stock rom, where i can boot into it, all custom firmwares just crash or work for a while and then they'll crash.
i dont get this.
it started just days ago, now i dont even can use anything....
Click to expand...
Click to collapse
just as an example, when i tried to put on the neatrom-lite on my phone, it crashes while iam selecting the country. and this is just 2-3seconds after booting into the fresh and new system.
something is completely ****ed up....
so right now, i have the militant rom on my phone, got booted up, but the power button doesnt work.... when the phone is on...
so everytime, when i want to switch of the screen, i have to wait, or take of the battery. and switching on is only possible with the home button.
whats wrong?
Given you have the same problems on stock, hardware problem. Back to stock, reset counter, send it in for warranty service (if you have warranty), if not, take it to local mobile repair shops.
reseting the counter... with stock? how to do that? i thought this is only possible with root? and i thought, as soon as i root, there is something already on the counter?
Sakujou_Kei said:
reseting the counter... with stock? how to do that? i thought this is only possible with root? and i thought, as soon as i root, there is something already on the counter?
Click to expand...
Click to collapse
You have two option. Either flash a custom kernel (siyah, for example), then reset the counter using triangle away app. Then flash a stock firmware using odin. This wont increase the counter.
Or, if you have a USB jig, flash an older bootloader (have to careful here), then simply plug in the jig.
Sent from my GT-I9100 using xda app-developers app
hey, i got the problem:
i transferred a few files between the sd card and the internal storage of my device, and i realised, that the device is not able to fully transfer the files. it says after 40-50% that its done. is there a flash the roms via ODIN? or how to do that? just put the rom.zip as PDA?
Sakujou_Kei said:
hey, i got the problem:
i transferred a few files between the sd card and the internal storage of my device, and i realised, that the device is not able to fully transfer the files. it says after 40-50% that its done. is there a flash the roms via ODIN? or how to do that? just put the rom.zip as PDA?
Click to expand...
Click to collapse
Unzip first.
I'd advice you to read about flashing with odin and watch a couple of videos on youtube before you put yourself up to it or else you're gonna have a bad flash, and that means trouble.
Sent from the little guy
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.
This has been doing my head in for quite some time, sometimes when I take a picture and flash/focus and then shoot it turns my phone off, to the point I can't turn it back on and I have to battery pull.
I thought it was a ROM related issue (at the time I was on Ultima ROM 4.2) so just recently I've upgrades to 4.3.2 KitKat and it does exactly the same. It's not an app issue although it does it far less in MX Camera then stock camera.
Does anybody know why? it's driving me crazy
UrbanDesigns said:
I got this error in CWM after I tried flashing a KitKat ROM, I googled the error and found it's because my CWM is old and I need the updated version that's able to flash some KitKat ROMs but i wipe factory/data reset and when i reboot i just reboot into recovery
I figured i can just flash the .tar file from Odin and reboot into the new recovery and then flash the ROM but the .tar is nowhere to be found and i'm pretty out of practise with all the flashing ROMs business, I don't know what my alternatives are. I'm updating from 4.1.2 and that's only because the bug on this app is doing my head in (turns phone off sometimes when flash focus taking a picture, got to battery pull)
phone is stuck in recovery until some chap helps me out
phone is scaring me now lol, had trouble getting it into recovery then. i can see the brick light and its glowing
much appreciated
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=34379030
Go here and download the latest Phil's touch recovery... Both tar and zip files are present...
Sent from my GT-I9300 using xda app-developers app
edit: fixed my first problem, now to the reason that caused me to upgrade to kitkat in the first place... it's still occuring
bumo because i can't cope with this anymore, it will be the death of me
UrbanDesigns said:
bumo because i can't cope with this anymore, it will be the death of me
Click to expand...
Click to collapse
Yeah that's happening to me too, I'm on Imperium rom v31.0 (based on stock Samsung 4.3) with Boeffla 5.3 kernel.
I'll try figure out what's going on, it might be the battery getting old. If you can, try a newer battery.
EDIT: Problem seems to be fixed for me, setting max CPU clock to 1600mhz and GPU to 266/350/440/533/600 overvolting to +25mV through Boeffla-Config V2.