Related
Ok so i'm fairly new (only 3 and a half months although been lurking until my hero purchase for around 6 months) and catch on quickly.
I have a cdma hero running darchlegendv.4.3 and forgive me for forgetting his name(The Blue theme his name starts with a g,sorry g*****,lol) but anyhow, i've tried flashing a few roms now and am getting stuck in a constant boot...
I Backup,Wipe Everything but sd,flash the update zip and it installs and boots..
The Problem is It boots and boots and then finally freezes for about 20 seconds then starts the boot animation over and over.What could be the cause of my constant boot???
1)Is It A Bad PRI or PRL???
2)I've Flashed Fresh 2.0d,Darchlegend 5,DC5.6,and Darchvanilla with this problem..
3)(While I'm Asking Questions)I'd Like To start developing and making roms and/or applications for my favorite little green robot. Can anyone take the time out to PM me possibly??
Thank you sooo much for any contribution it's very appreciated
abov3dis said:
Ok so i'm fairly new (only 3 and a half months although been lurking until my hero purchase for around 6 months) and catch on quickly.
I have a cdma hero running darchlegendv.4.3 and forgive me for forgetting his name(The Blue theme his name starts with a g,sorry g*****,lol) but anyhow, i've tried flashing a few roms now and am getting stuck in a constant boot...
I Backup,Wipe Everything but sd,flash the update zip and it installs and boots..
The Problem is It boots and boots and then finally freezes for about 20 seconds then starts the boot animation over and over.What could be the cause of my constant boot???
1)Is It A Bad PRI or PRL???
2)I've Flashed Fresh 2.0d,Darchlegend 5,DC5.6,and Darchvanilla with this problem..
3)(While I'm Asking Questions)I'd Like To start developing and making roms and/or applications for my favorite little green robot. Can anyone take the time out to PM me possibly??
Thank you sooo much for any contribution it's very appreciated
Click to expand...
Click to collapse
I hope you're trying to wipe and then adding the theme... flash or recover your 4.3.1 (although I recommend flashing 4.5) and then flash your darkstar theme over it
Oh no I have the them on top of darchlegend 4.3 , I applied that right i just don't know why it constants boots when i try to flash to a new rom(i do wipe)I just don't know..
abov3dis said:
The Problem is It boots and boots and then finally freezes for about 20 seconds then starts the boot animation over and over.What could be the cause of my constant boot???
Click to expand...
Click to collapse
So plug in the cable, do a logcat, and find out.
How exactlt do i do that? Thanks for the reply
do adb logcat from command prompt.
ALSO,
were you sure that this was in fact a theme for DarchLegend? Cause if it didn't specifically say that, then that is why. Different frameworks between that rom and the sprint roms.
yes I haven't a clue what's wrong, I'm in recovery wipe and it installs but conatantly boots . Note:this is when i flash a new rom,te current will boot
abov3dis said:
yes I haven't a clue what's wrong, I'm in recovery wipe and it installs but conatantly boots . Note:this is when i flash a new rom,te current will boot
Click to expand...
Click to collapse
what are you wiping just data? ive had this happen before, wipe everything dev., ext, data everything then flash again then wipe data again.
Any flash that wipes dalvik cache like a rom our flipz's vanilla lock screen fix can take up to twenty minutes to boot the first time. This also means anytime you wipe the dalvik cache from recovery.
Some details:
HD2 512.
Typhoon 3.5.6.
MAGLDR 1.13.
Recovery 4.0.0.0.
Some things I know:
CM7 takes a while to load anyway.
I believe having lots of media (I have 7GB MP3's) can lengthen boot times. (~Theory is crapped all over with my SGS2 but some people have mentioned this fact).
The problem here is not at the loading stage where the bootanim kicks in, it's the stage before with the static logo after GO GO GO.
My SGS2 literally loads and is ready to use in 10 seconds to OS and 30 seconds to functionality after media scan/widgets etc.
So what's my HD2 doing at the static logo screen? It basically doubles the entire loading time but from my little knowledge, nothing actually happens until the bootanimation? I don't like waiting up to 2 minutes to be using my phone.
I hear CLK has a faster boot option. In anyone's opinion, have they sorted data out enough to come away from MAGLDR?
Thanks in anticipation of any responses.
dkl_uk said:
Some details:
HD2 512.
Typhoon 3.5.6.
MAGLDR 1.13.
Recovery 4.0.0.0.
Some things I know:
CM7 takes a while to load anyway.
I believe having lots of media (I have 7GB MP3's) can lengthen boot times. (~Theory is crapped all over with my SGS2 but some people have mentioned this fact).
The problem here is not at the loading stage where the bootanim kicks in, it's the stage before with the static logo after GO GO GO.
My SGS2 literally loads and is ready to use in 10 seconds to OS and 30 seconds to functionality after media scan/widgets etc.
So what's my HD2 doing at the static logo screen? It basically doubles the entire loading time but from my little knowledge, nothing actually happens until the bootanimation? I don't like waiting up to 2 minutes to be using my phone.
I hear CLK has a faster boot option. In anyone's opinion, have they sorted data out enough to come away from MAGLDR?
Thanks in anticipation of any responses.
Click to expand...
Click to collapse
Don't remember stuck with GO GO GO for long in my Mag days. I am now on cLK, and from the second boot onward, my phone is usable within 45 seconds - this is with a lot of apps, most of with run all the time right from boot.
I am using MAGLDR with Tytung's Nexus HD2 v2.9 build and it takes about 45-50 seconds to load. Much faster than when I was using Cmylxgo's TMOUS Froyo build which took a little over 2 minutes to load for comparison.
ph03n!x said:
Don't remember stuck with GO GO GO for long in my Mag days. I am now on cLK, and from the second boot onward, my phone is usable within 45 seconds - this is with a lot of apps, most of with run all the time right from boot.
Click to expand...
Click to collapse
It's not stuck at GO GO GO, it's stuck at the static boot image for a while, then the animated boot logo begins. Maybe it's the fact the phone looks like it's doing nothing while it's showing the static boot logo but like I mentioned above the SGS has the same amount of media and also it has the same apps as the HD2 and it's usable in under 30 seconds.
Thanks for the response anyway.
dkl_uk said:
It's not stuck at GO GO GO, it's stuck at the static boot image for a while, then the animated boot logo begins. Maybe it's the fact the phone looks like it's doing nothing while it's showing the static boot logo but like I mentioned above the SGS has the same amount of media and also it has the same apps as the HD2 and it's usable in under 30 seconds.
Thanks for the response anyway.
Click to expand...
Click to collapse
If you want to experiment, try Tytung's Mag kernel - get it from his thread and flash it. Mind you, ensure it also has the wifi drivers (bcm4329.ko), else wifi may not work. In my experience, Tytung's implementation of his Kernel boot faster.
Also, CWM 4.0.0.0 is not supposed to be stable (has something with backup/ recovery). Get the latest, or go with 3.2.0.0
I had the same problem when I was using that rom.
I tried to find the prob using logcat, and I saw a lot of errors being thrown at me, and also quite a few a2sd zipalign's, so I removed a2sd scripts from init.d, it started booting faster; but I still had the other errors.
ph03n!x said:
If you want to experiment, try Tytung's Mag kernel - get it from his thread and flash it. Mind you, ensure it also has the wifi drivers (bcm4329.ko), else wifi may not work. In my experience, Tytung's implementation of his Kernel boot faster.
Also, CWM 4.0.0.0 is not supposed to be stable (has something with backup/ recovery). Get the latest, or go with 3.2.0.0
Click to expand...
Click to collapse
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
Moon2 said:
I had the same problem when I was using that rom.
I tried to find the prob using logcat, and I saw a lot of errors being thrown at me, and also quite a few a2sd zipalign's, so I removed a2sd scripts from init.d, it started booting faster; but I still had the other errors.
Click to expand...
Click to collapse
I actually have live logcat bootanimation and I am pretty sure i've seen a lot of errors too. It goes too fast to debug anything, and i've not taken the next step which is of course to do what you did and actually read the logcat, but these errors take milliseconds during the boot phase and I don't believe it's this bit that is the issue - it's the bit where the static logo shows and I don't truly know what the phone is doing at that stage.
Thanks for your helps also guys
dkl_uk said:
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
Click to expand...
Click to collapse
The Mag and the cLK version of the kernel are here- use the one that says 2.3.4 only, even if you or on 2.3.5
I use this in cLK, and know for sure that the required Wifi drivers are in it. Note that the cLK version has cedesmith's data wrapper b5, but the b4 wrapper works better for me. This is in case you choose cLK, and are having data issues after flashing the kernel.
http://forum.xda-developers.com/showpost.php?p=10429937&postcount=3
ph03n!x said:
The Mag and the cLK version of the kernel are here- use the one that says 2.3.4 only, even if you or on 2.3.5
I use this in cLK, and know for sure that the required Wifi drivers are in it. Note that the cLK version has cedesmith's data wrapper b5, but the b4 wrapper works better for me. This is in case you choose cLK, and are having data issues after flashing the kernel.
http://forum.xda-developers.com/showpost.php?p=10429937&postcount=3
Click to expand...
Click to collapse
That's literally the post I came across once I did a search based on what you'd already told me. Thanks for confirming further.
Timed my boot - was 35secs on the watch and 33secs according to logcat. To put things in perspective, I have trillian (5 accounts), gtalk, gmail, 3 email accounts, google+, current widget, CallRecorder, CSipSimple, ClockSync, DSP Manager, Easy Filter, Swype and Where's My Droid loading at boot - in addition to whatever Android loads (Maps, Calendar, Settings...)
dkl_uk said:
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
I actually have live logcat bootanimation and I am pretty sure i've seen a lot of errors too. It goes too fast to debug anything, and i've not taken the next step which is of course to do what you did and actually read the logcat, but these errors take milliseconds during the boot phase and I don't believe it's this bit that is the issue - it's the bit where the static logo shows and I don't truly know what the phone is doing at that stage.
Thanks for your helps also guys
Click to expand...
Click to collapse
You have to use the following command to get logcat to make a file of it.
adb logcat > anyfilename.txt
ph03n!x said:
Timed my boot - was 35secs on the watch and 33secs according to logcat. To put things in perspective, I have trillian (5 accounts), gtalk, gmail, 3 email accounts, google+, current widget, CallRecorder, CSipSimple, ClockSync, DSP Manager, Easy Filter, Swype and Where's My Droid loading at boot - in addition to whatever Android loads (Maps, Calendar, Settings...)
Click to expand...
Click to collapse
At what point are you timing this boot from? Power on? GO GO GO? Splash screen?
If I were to time my boot from the animated boot screen then i'd say possibly 30 seconds too, it's just that for another 30 seconds it's sat on the static boot animation.
Also my launcher screen takes an awful amount of time to parse. You can definitely tell the HD2 is ageing when you compare it with the SGS2. I know it's in a class of its own but still, i'm beginning to lose faith in the longevity of my HD2.
I am on the same boat, I use aMAGLDR 1.13 + MIUI Rom and the boot process is very very slow.
I just timed it:
1. From T-mobile Stick together to go go go: 9 secs.
2. A static splash screen, black background and green HTC logo: 1min 52 secs.
3. From MIUI globe animation kicked in to locked screen: 29 secs.
So basically I have no idea why step 2 takes such a long time. Is there anyway to see any error msg during this stage?
I tried to remove SIM card and/or SD card, it is about the same, so I guess there is something happening in the NAND...
Thanks!
First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
EDIT:
I have TWRP 2.5.0.3 on my phone
sebbo1 said:
First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
Click to expand...
Click to collapse
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot
Colonel Sanders said:
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot
Click to expand...
Click to collapse
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.
sebbo1 said:
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.
Click to expand...
Click to collapse
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.
Colonel Sanders said:
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.
Click to expand...
Click to collapse
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?
sebbo1 said:
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?
Click to expand...
Click to collapse
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.
Colonel Sanders said:
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.
Click to expand...
Click to collapse
Are you talking about slimroms.net? If you are, which addons do I download?
EDIT: nevermind. I downloaded the AIO (all in one)
sebbo1 said:
Are you talking about slimroms.net? If you are, which addons do I download?
Click to expand...
Click to collapse
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.
Colonel Sanders said:
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.
Click to expand...
Click to collapse
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website
sebbo1 said:
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website
Click to expand...
Click to collapse
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.
Colonel Sanders said:
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.
Click to expand...
Click to collapse
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I would say so myself, Odin back to stock, but since you have a mac and I'm not sure if Heimdall support the S4 try this:
Factory Reset
Wipe Cache
Wipe Dalvik
Format /system
Format /data
Format /internal (If CWM-based recovery)
Flash ROM, addons, reboot
sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen
sebbo1 said:
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen
Click to expand...
Click to collapse
That means the battery is low... Charge it up some... Check your PM for my gmail if you need some help, posting back and forth can take a while.
Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore
sebbo1 said:
Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore
Click to expand...
Click to collapse
Glad you got it going man, and enjoy Slim, it's hands down the best ROM there is if you prefer minimal with tons of customization options.
Hi,
I flashed the google edition rom a few weeks ago, all was working fine. This morning, I decided to flash a stock rom from sammobile (was this a bad idea)? I used CF autoroot and twerp custom recovery. It failed. So wiped everything, reflashed the google edition rom, but when I reboot the phone it gets stuck showing "Samsung galaxy s4" white text.
To boot it again i have to wipe data, cache and dalvik, then reflash the ROM, then qipe cache and dalvik, then it reboots. But when I turn it off then on again the whole process starts again.
Can anybody tell me what I'm doing wrong? This is the same ROM that worked faultlessly for weeks...
Thanks
Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app
richard2311 said:
Did u wait long enough, first reboot after flashing a new rom can take a while.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..
dickson123 said:
Yeah, I gave it 5 minutes, but it's not even getting to the boot animation.
When I tried to flash the stock rom could that have messed something up? It said failed, then for ages after that, it kept saying "error-failed to open \data\data .... I/O error" in twrp.
To avoid that I have to wipe data seperately, reboot recovery, then flash the ROM again from scratch. Every time I reboot the phone I have to do a full wipe and flash the rom before it even boots..
Click to expand...
Click to collapse
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297
mobileguynz said:
Have a read if this great guide: http://forum.xda-developers.com/showpost.php?p=43340522&postcount=3297
Click to expand...
Click to collapse
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )
dickson123 said:
Ok, thanks, I'll give it a go later. I'm at work and was hoping for a solution that didn't require ODIN (work PC too locked-down )
Click to expand...
Click to collapse
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove
mobileguynz said:
Well depending on which stock ROM you flashed you maybe affected by the enabled SElinux issue see https://plus.google.com/app/basic/stream/z13xxnmzvyeihn00w23wcdp55terwvove
Click to expand...
Click to collapse
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.
dickson123 said:
I don't understand what the issue is though. I'm not doing anything different than I did 3 weeks ago, and yet this time it doesn't work.
It's now gotten to the stage where it won't boot at all, just sits at the white text, no boot animation.
Is it possible that flashing a stock un-rooted ROM has messed it up somehow? Technically it never flashed because it just failed immediately.
Click to expand...
Click to collapse
If you flashed the latest stock ROM it maybe be one with Knox and that has a secure boot loader and kernel secure Selinux Knox stops you from modifying and installing.
Try using ausdims v16 kernel or wadams Adam kernel for stock roms. Note when I flashed the last ROM waited 10 minutes and had do a wipe and reset for it to boot see last pages for discussion http://forum.xda-developers.com/showthread.php?t=2250824
http://forum.xda-developers.com/showthread.php?t=2250824
Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?
matteosaeed said:
Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?
Click to expand...
Click to collapse
Go back to stock first, and check if that has the same problems...
matteosaeed said:
Hi,
I have been trying to flash few roms. I constantly do though. Last rom I was on, I found that the battery drained very quickly and it keeps changing its stats in a random way.
I decided to flash new roms, and since, I flash the rom, and then the phone turns off by itself. I tried few different kernels "of course the right ones", and some seem to help for few more minutes, but that is not the case.
I tried to flash the latest version of "FOXHOUND ROM' for the i9505, and it would show the boot animation and then turns off instead of starting the phone. Tried to wipe cache and all the stuff, and still the problem persisted. Could it be a bad battery all of the sudden?
Click to expand...
Click to collapse
For some reason I have tried this a lot on my old phone... Some kernels worked for mine and others not... While it should..
Flash stock and see... Keep stock kernel and flash rom, if no problems then try new kernel... If problem returns then flash stock kernel again
Sent from my GT-I9505 using xda app-developers app
DenmarkRootN00b said:
For some reason I have tried this a lot on my old phone... Some kernels worked for mine and others not... While it should..
Flash stock and see... Keep stock kernel and flash rom, if no problems then try new kernel... If problem returns then flash stock kernel again
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the tip. I tried that as well, but Unfortunately, the same problem. I don't have a problem what so ever when I am using the phone while it is charging or plugged in, but as soon as I take it out, and even if it is full, it shuts off, tries to turn back on and it wouldn't, it keeps rebooting, once i plug the charger in it, it would stay on.
That tells me either:
The Battery is bad!
Or
There might be a circuit problem with the phone sucking power out of the battery!