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
Related
Okay so my phone decided to do a force close on everything that i tried to do so I turned it off and tried to turn it back on again but all i was getting was the galaxy screen flash up and then it would turn black.
I flashed with Odin 3 times now and it says that it was successfull but when i go to turn the phone on it reboots and says that the data wipe has failed and then continues to flash the galaxy screen and then black. Can someone please help. I am a noob and haven't done anything but flash my phone.
The answers you are going to get are to odin back to stock, however ive had this problem and to get past it I had to do a factory wipe all data in the recovery menu then it booted. You lose all data. Before you do that try cycling the phone through restarts with battery pulls, I had another issue where doing this kicked me into normal boot after about 18 tries. I'm no expert but this is how I got fixed. Mine was a busy box issue it was never installed right
Sent from my SGH-T959 using XDA App
yeah, i agree w/ kcp about the battery pull... I would try this to see if you can get your system up and running, so that way you can dl Titatium Backup and Rom Manager. I had a problem on mine that would not let me reinstall packages and then it would never leave recovery, but after i pulled the battery, rebooted, and downloaded rom manager, i found that it was the same issue as kcp (busy box had to be updated). I don't understand why, after you re-flashed the Rom w/ odin it is not working.... did you flash 2.1 or 2.2? Remember, after you flash with odin you need to wipe data and chached memory, then reboot (maybe a battery pull). Try to give more info about exactly how you flashed w/ odin.
Also my titanium says it downloads busy box but doesn't had to go get it from the market and put it in the x bin you might want to do the same when it boots to be safe.
Sent from my SGH-T959 using XDA App
in_dmand said:
yeah, i agree w/ kcp about the battery pull... I would try this to see if you can get your system up and running, so that way you can dl Titatium Backup and Rom Manager. I had a problem on mine that would not let me reinstall packages and then it would never leave recovery, but after i pulled the battery, rebooted, and downloaded rom manager, i found that it was the same issue as kcp (busy box had to be updated). I don't understand why, after you re-flashed the Rom w/ odin it is not working.... did you flash 2.1 or 2.2? Remember, after you flash with odin you need to wipe data and chached memory, then reboot (maybe a battery pull). Try to give more info about exactly how you flashed w/ odin.
Click to expand...
Click to collapse
How do i know if i flashed with 2.1 or 2.2? How do you wipe data and cached memory? I turned it back on after i flashed and it showed that it was rebooting and wiped the cached memory but the data wipe failed.
also, my phone is not unlocked
Update: I flashed with 2.2 but I did not know that it was for tmobile. I am with bell. Now i can't get it to go into download mode so that I can flash with the right rom. It also won't charge when plugged in. Am i going to have to just get a new phone?
anything on this yet? mine is cycling aswell and cant get it into DL mode ;(
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
Solved
Hello everyone
Since a few days ago my S2's Wifi is not working
h.ttp://i.imgur.com/ojDOm.png
The icon stays like this, pressing it does nothing. it happened 3 - 4 times before, usually, I'd just reboot it and that would do the trick (I google'd a bit and saw this is a common glitch when trying to turn wifi on), but not anymore, it refuses to turn on no matter what I do, rebooting, shutting down and restarting, it's stuck.
h.ttp://i.imgur.com/KeMxb.png
I can't Scan, add a network nor switch the toggle on/off because pressing them does nothing, So... I thought I should do backup and factory reset it, nope. still stuck.
What's wrong with it? Any ideas? The phone is a year old, running 4.0.3 Stock
Sorry about the dots in the URL's, can't post links yet.
Edit: Forgot to mention it started doing this since I got ICS, maybe I should try flashing it to see if that fixes it, I'm kinda reluctant though, since the factory reset didn't seem to do anything and I haven't done it before.
Cathari said:
Hello everyone
Since a few days ago my S2's Wifi is not working
h.ttp://i.imgur.com/ojDOm.png
The icon stays like this, pressing it does nothing. it happened 3 - 4 times before, usually, I'd just reboot it and that would do the trick (I google'd a bit and saw this is a common glitch when trying to turn wifi on), but not anymore, it refuses to turn on no matter what I do, rebooting, shutting down and restarting, it's stuck.
h.ttp://i.imgur.com/KeMxb.png
I can't Scan, add a network nor switch the toggle on/off because pressing them does nothing, So... I thought I should do backup and factory reset it, nope. still stuck.
What's wrong with it? Any ideas? The phone is a year old, running 4.0.3 Stock
Sorry about the dots in the URL's, can't post links yet.
Edit: Forgot to mention it started doing this since I got ICS, maybe I should try flashing it to see if that fixes it, I'm kinda reluctant though, since the factory reset didn't seem to do anything and I haven't done it before.
Click to expand...
Click to collapse
Do the steps below
- Boot to CWM recovery
- wipe cache partition
- wipe dalvik cache (under advanced)
- fix permissions (under advanced)
- reboot system now
The above steps will not make you lose some files and data
If that does not help, then flash another kernel
Since putting a custom kernel on my phone my bluetooth does exactly the same as what your wife is doing. Only way to turn it on is to reboot the phone whilst it is trying to turn on (ie whilst it is a shade of green)
saywhatt said:
Do the steps below
- Boot to CWM recovery
- wipe cache partition
- wipe dalvik cache (under advanced)
- fix permissions (under advanced)
- reboot system now
The above steps will not make you lose some files and data
If that does not help, then flash another kernel
Click to expand...
Click to collapse
Gonna try that and flash CM9 while I'm at it, never done this before... Lets see how it goes following the steps on CM's wiki
Cathari said:
Gonna try that and flash CM9 while I'm at it, never done this before... Lets see how it goes following the steps on CM's wiki
Click to expand...
Click to collapse
you should be Ok its relativley straight forward
Well, Flashed in CWM Recovery and CM9, wiped cache, Dalvik cache and fixed permissions but the wifi is still not working... it's still stuck at "Turning Wi-Fi on"
I really have no idea about kernels and that stuff, I don't know how to flash 'em (unless it's the same as flashing CWM) or which one to get at all, since theres too many and I don't know what they do/know if they're compatible.
Flashing kernels are the same as flashing ROMs and modems..
There are 2 ways to flash kernels.. 1 is via odin (.tar file) and 2 is via CWM (.zip file)
Now, if your ROM is on JB then use a JB Kernel
If ICS = ICS Kernel
AOKP = AOKP Kernel
AOSP = AOSP Kernel
The thing with kernel is that you have to match it with the ROM's base..
Sent from my GT-I9300 using xda premium
Hm...Checked my phone 7 hours after flashing CM9 on it and suddenly the Wifi's back on
Any explanation for this? It doesn't make any sense, I didn't even touch the phone during that time and it fixed itself?
Edit: Thanks for clarifying that up saywhatt, since I already flashed if and thus, voided the warranty I might as well go ahead and try flashing a kernel to improve battery life and get into the scene.
Cathari said:
Hm...Checked my phone 7 hours after flashing CM9 on it and suddenly the Wifi's back on
Any explanation for this? It doesn't make any sense, I didn't even touch the phone during that time and it fixed itself?
Edit: Thanks for clarifying that up saywhatt, since I already flashed if and thus, voided the warranty I might as well go ahead and try flashing a kernel to improve battery life and get into the scene.
Click to expand...
Click to collapse
No problem.
Perhaps the ROM was "settling"? Lol i dunno.. but i'm glad to hear you got it sorted out. You can revert back to complete stock if you have some serious problems and it is needed to be sent to the service center..
1 download triangle away to clear the binary count
2 flash stock firmware
Voila! U no longer have a void warranty
Sent from my GT-I9300 using xda premium
So I've had the joy of rooting/unlocking a Thunderbolt and a Galaxy Nexus and now my DNA, so I'm vaguely familiar with how it works.
I had unlocked and rooted the phone about two months ago. I think I'm running a stock ROM with all the bloat removed I couldn't tell you exactly which one, but I think it's just the one that's deodexed with bloat removed. Had been running fine for awhile. Decided to use the Cubed DNA Kernel 2.4.2, roughly after I did this my phone would start to randomly reboot, which started about 2 weeks ago.
I didn't think anything of it up to this point and thought I'd fix it at some point. Today it rebooted once again, but this time it would never make it back into the Android OS, or if it did make it it would immediately freeze and I'd have to force reboot it. At this time I could still get into the CWR and the Bootloader. But that's really all I could do. I attempted to roll back to previous backups, this didn't work. So then I thought maybe it's the Kernel, so I was going to put it back to stock. Per the instructions I attempted to flash the boot.img file before flashing the stock kernel modules zip file.
After I did the flash for the boot.img, I can no longer get into CWR. I can still get into the bootloader, but that's really about it.
Unfortunately I have no device to fall back on. So any help or suggestions would be extremely helpful.
What happens when you try to go into recovery?
And just so you know, it was your kernel that was causing the reboots. It is a known issue with cubed kernel that dsb is working hard to fix.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
What happens when you try to go into recovery?
And just so you know, it was your kernel that was causing the reboots. It is a known issue with cubed kernel that dsb is working hard to fix.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
It basically just reboots. It says "entering recovery" at the top of the HTC boot screen, then reboots immediately after that again and attempts to boot normal, it then goes into the droid boot animation and just hangs there.
cowprince said:
It basically just reboots. It says "entering recovery" at the top of the HTC boot screen, then reboots immediately after that again and attempts to boot normal, it then goes into the droid boot animation and just hangs there.
Click to expand...
Click to collapse
Try redownloading and reflashing the boot.img in fastboot. And if that doesn't work than flash a different recovery and see if that helps.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Try redownloading and reflashing the boot.img in fastboot. And if that doesn't work than flash a different recovery and see if that helps.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Thanks Big, I was going to try it before I went to work this morning, but now it seems like the device is completely dead.
Will not power on and I get no lights when I attempt to charge it. I've tried multiple USB cables and charging methods, none result in any charging LED...
cowprince said:
Thanks Big, I was going to try it before I went to work this morning, but now it seems like the device is completely dead.
Will not power on and I get no lights when I attempt to charge it. I've tried multiple USB cables and charging methods, none result in any charging LED...
Click to expand...
Click to collapse
I should have been more clear there now that I've reread it, I never got the chance to try your suggestion, it's as if the battery died overnight and won't charge now.
cowprince said:
I should have been more clear there now that I've reread it, I never got the chance to try your suggestion, it's as if the battery died overnight and won't charge now.
Click to expand...
Click to collapse
Plug it in & Hold the power button down for about 15 to seconds for a hard reboot. If you can get it to boot, then try to flash the original stock kernal (link is located in dsb cubed kernel thread or here http://d-h.st/Ma1 ).
Once you flashed the original kernel flash dsb's other kernel stock cubed kernal here http://forum.xda-developers.com/showthread.php?t=2064066 . This one works real good, its basically stock but you can read/write and it has the hsic fix for a little better battery life.
You can use the stock cubed until the full cubed kernel is up and running with its fixes.
Hope this helps...
Jrocker23 said:
Plug it in & Hold the power button down for about 15 to seconds for a hard reboot. If you can get it to boot, then try to flash the original stock kernal (link is located in dsb cubed kernel thread or here http://d-h.st/Ma1 ).
Once you flashed the original kernel flash dsb's other kernel stock cubed kernal here http://forum.xda-developers.com/showthread.php?t=2064066 . This one works real good, its basically stock but you can read/write and it has the hsic fix for a little better battery life.
You can use the stock cubed until the full cubed kernel is up and running with its fixes.
Hope this helps...
Click to expand...
Click to collapse
Thanks Jrocker, I just hope I can get the thing to charge and/or boot when I get home.
Well it's not completely dead. Looks like I made it back into the bootloader. I can't seem to flash the boot.img file though:
fastboot flash boot boot.img
sending 'boot' (5412 KB)...
OKAY [ 0.839s]
writing 'boot'...
FAILED (remote: battery low)
finished. total time: 0.863s
So first thought would be, well ok charge the phone. However, I'm not so sure it's actually charging.
I have it plugged into the AC adapter while the bootloader is showing and it says FASTBOOT AC, however I see no solid orange LED telling me that the device is charging.
Also is there a way to push files to the SD card using fastboot. For example the stock kernel zip file?
OK I'm pretty sure I know what happened. Same thing has happened to me a few times. Apparently it only happens on some phones. I think the /data partition on your phone got borked. As in corrupted. It has done this to me about 3 times, each time I was running a custom kernel. Now that I know that my phone is one of the susceptible ones, I've been running DSB's stock system write kernel and have not had any issues since.
If this is the case, it sucks but the only thing you can do to fix it is to factory reset. When this has happened to me I have run fsck2 (disk checker) on my /data partition and it comes up with multiple errors and fixes them, but the phone still won't boot. I know dsb is aware of the issue, as are others, but there is no fix as of now besides either running stock kernels until it is fixed, or getting a new device (which may or may not be susceptible.) You can run fsck2 on your data partition and see if maybe it boots after fixing the errors, but I've had no luck 3 out of 3 times. Hope this helps.
EDIT: didn't realize that your recovery partiton got borked too, that's weird. Never had that happen. Reflash your recovery and then you should be able to go from there.
BotsOne said:
OK I'm pretty sure I know what happened. Same thing has happened to me a few times. Apparently it only happens on some phones. I think the /data partition on your phone got borked. As in corrupted. It has done this to me about 3 times, each time I was running a custom kernel. Now that I know that my phone is one of the susceptible ones, I've been running DSB's stock system write kernel and have not had any issues since.
If this is the case, it sucks but the only thing you can do to fix it is to factory reset. When this has happened to me I have run fsck2 (disk checker) on my /data partition and it comes up with multiple errors and fixes them, but the phone still won't boot. I know dsb is aware of the issue, as are others, but there is no fix as of now besides either running stock kernels until it is fixed, or getting a new device (which may or may not be susceptible.) You can run fsck2 on your data partition and see if maybe it boots after fixing the errors, but I've had no luck 3 out of 3 times. Hope this helps.
EDIT: didn't realize that your recovery partiton got borked too, that's weird. Never had that happen. Reflash your recovery and then you should be able to go from there.
Click to expand...
Click to collapse
So ultimately if I just do a factory reset and then restore one of my old backups after flashing the stock kernel boot.img I should be good then? Or should I still run fsck2?
cowprince said:
So ultimately if I just do a factory reset and then restore one of my old backups after flashing the stock kernel boot.img I should be good then? Or should I still run fsck2?
Click to expand...
Click to collapse
If you plan on restoring a backup there's no need to wipe. Recovery will wipe the data partition before it restores the old one. After that just flash your kernel and modules and you should be back up and running.
Fsck2 is not necessary. The only reason you might want to run fsck2 would be to:
1. verify that this is indeed your problem.
2.you have have a (slim) chance of fixing your data partition, saving you from wiping. Like I said I tried it and it did fix the disk errors, but still wouldn't boot.
Well it looks like I cannot do a restore of an old backup, I get an error saying that it can't mount /system
Am I doing this all in the right order?
reboot to bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
reboot to bootloader
reboot to recovery
factory reset
flash kernel
restore recovery backup
reboot
cowprince said:
Well it looks like I cannot do a restore of an old backup, I get an error saying that it can't mount /system
Am I doing this all in the right order?
reboot to bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
reboot to bootloader
reboot to recovery
factory reset
flash kernel
restore recovery backup
reboot
Click to expand...
Click to collapse
You might be able to fix that error by flashing a newer version of whatever recovery you are using. Not sure, never had that error. If you can't get your backup to flash do this (I'm assuming you already have a custom recovery installed/working since you tried to restore a backup)
1. reboot into bootloader
2. fastboot flash boot boot.img (dsb's stock kernel img)
3. reboot into recovery
4. factory reset
5. flash modules (dsb's stock kernel modules)
6. wipe cache and dalvik for good measure
7. cross fingers
8. reboot
If it doesn't boot after that I think I would reflash the rom and try again starting at step 4, but I think that^^ should do the trick.
Looks like I'm back in business, went ahead and flashed the stock system writable kernel and CWR, then the kernel module zip, a fresh ROM the Genome ROM and was good to go again.
However I still have one remaining problem. The wifi errors out and won't turn on.
cowprince said:
Looks like I'm back in business, went ahead and flashed the stock system writable kernel and CWR, then the kernel module zip, a fresh ROM the Genome ROM and was good to go again.
However I still have one remaining problem. The wifi errors out and won't turn on.
Click to expand...
Click to collapse
Glad to hear you're back up and running! Wifi not turning on is a telltale sign that you need to reflash your modules for whatever reason.
BotsOne said:
Glad to hear you're back up and running! Wifi not turning on is a telltale sign that you need to reflash your modules for whatever reason.
Click to expand...
Click to collapse
That's kinda what I had assumed.
Now I just need to hope for an AOSP ROM and some email widgets not bound to the Sense UI...
Actually no dice on the reflashing of the kernel modules. Maybe I should do the boot.img as well?
cowprince said:
Actually no dice on the reflashing of the kernel modules. Maybe I should do the boot.img as well?
Click to expand...
Click to collapse
U should do the boot.img 1st then boot into recovery and wipe cache/davik cache and flash the module. If u still having problems then get the stock DNA kernel
sent from my beastly powered viper DNA using Tapatalk 2
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 ...