i was doing my first flash of a rom last night and i didnt notice a status bar letting you know what processes were going on or if it was even installing the rom. So... i left it sitting on the vibrant screen for like 20 minutes and i saw absolutely nothing going on and became concerned it bricked. so i whipped out the old trusty backup iphone and went to downloading android sdk and supporting programs so i could adb in and make it reboot. i got tired around 1am and called it a night. put the vibrant on the charger and noticed the battery charging display popped up and it was half full. left it to charge all night and left the laptop updating and downloading all the sdk tools and stuff. got up next morning and plugged the vibrant into the laptop and the vibrant screen popped up as usual when u plug it in to a computer. i paid no attn and brought up my cmd line and was fixing to adb reboot recover and low and behold i heard the tmo jingle and saw the galaxy s icon start going. so long story short would it be a big deal to put a status bar to let someone know its actually doing something other than just sitting there? just a thought... and what length of time does it usually take to flash a rom and reboot the system?
HaCkEdUpViB said:
i was doing my first flash of a rom last night and i didnt notice a status bar letting you know what processes were going on or if it was even installing the rom. So... i left it sitting on the vibrant screen for like 20 minutes and i saw absolutely nothing going on and became concerned it bricked. so i whipped out the old trusty backup iphone and went to downloading android sdk and supporting programs so i could adb in and make it reboot. i got tired around 1am and called it a night. put the vibrant on the charger and noticed the battery charging display popped up and it was half full. left it to charge all night and left the laptop updating and downloading all the sdk tools and stuff. got up next morning and plugged the vibrant into the laptop and the vibrant screen popped up as usual when u plug it in to a computer. i paid no attn and brought up my cmd line and was fixing to adb reboot recover and low and behold i heard the tmo jingle and saw the galaxy s icon start going. so long story short would it be a big deal to put a status bar to let someone know its actually doing something other than just sitting there? just a thought... and what length of time does it usually take to flash a rom and reboot the system?
Click to expand...
Click to collapse
regularly for me, the average is about 5-7 minutes, not including the time it takes to download the ROM itself on computer and transfer.
Probably because i have everything set up, i have a file called FIX BRICK and all the files i need in there to "fix" the "brick"
I'm used to it, and don't mind odin'ing so its all quite short.
but most of the time IS taken up by the phone reformatting everything, then rebooting, the first boot is ALWAYS the longest.
Were you installing a ROM with a Voodoo kernel baked in? If so it takes about 15 min to reformat the file system.
CrazyCharlie said:
Were you installing a ROM with a Voodoo kernel baked in? If so it takes about 15 min to reformat the file system.
Click to expand...
Click to collapse
does it?
I just flashed AXURA with voodoo in it, and it took me like 6 minutes.... o god, lemme confirm i have it enabled or something lol
i heard linda talking and telling me the confirm time, but.......
brb gonna check!
nvm its already enabled lol... guess my phone's awesome?
also i went to stock using odin then flashed so my previous voodoo has nothing to do with this
If it was already enabled when you flashed Auxura then it was probably because the rom you were having trouble with already reformated the file system. Voodoo can be tricky with some of the older rom's but with the ability to enable and disable through clockwork it's much easier to deal with. Remember when flashing new rom's to disable the lagfix first. If the new rom uses a non voodoo kernel you'll get a soft brick.
CrazyCharlie said:
If it was already enabled when you flashed Auxura then it was probably because the rom you were having trouble with already reformated the file system. Voodoo can be tricky with some of the older rom's but with the ability to enable and disable through clockwork it's much easier to deal with. Remember when flashing new rom's to disable the lagfix first. If the new rom uses a non voodoo kernel you'll get a soft brick.
Click to expand...
Click to collapse
na i did it on purpose.
When i want to use a rom for a long time, i odin back, so there are no ghosts what so ever left, and then flash the rom, so its fast just as good as new.
and i checked re-format on odin, so the ext4, was turned back to RFS or RTS what ever that is.
The longest it ever took for my phone was when I went from 2.1 to 2.2 for the first time. Wasn't more than 10 minutes but noticeably longer. Patience is key.
Whether you break your phone now or later, go ahead and get all things necessary to fix. Just sayin...
Agreed. Odin is you're friend.
[ROM] Vibrant AOSP ish JK2 1.1 Official FROYO (Working GPS, WiFi Calling) this is the rom i used. idk if it has a voodoo kernel. i wouldnt think so. it was asthetically pleasing to my eye when i saw the screen shots and i noticed all the bloatware was gone so thats y i chose it. i like it so far. kinda glitchy at the first restart/reboot ( moved all of my widgets back to where they were on first start up after i placed them where i wanted them, and i had to load my google acct twice and my FB contacts twice) but since then it seems like everything has settled down and i am very pleased. kudos to the rom maker. its 10 times better than eclair. thanks for the input guys
btw im really diggin the car section. does it pair via bluetooth?
Related
So,
I downloaded Bionix 1.8 and Flashed through Clockwork. Only after I disable Voodoo of course. After getting all my settings back the way I like it, played a few games, checked a couple emails I placed my phone on the charger. After the phone was completely charged an hour later.
I decided to boot into clockwork and delete my battery usage stats and rebooted. After it rebooted I unplugged the charger and BOOTLOOP.
It shows the vibrant screen and then Snow like a tv. Except there is other colors in the snow. Not many though. Then the vibrant screen and the snow. Your getting the picture, over and over like this even after pull the plug....plugging the charger. I've even tryed going into download mode. I think. It just keeps booting...
So,
Do I have a paper weight?
Will this thing work anymore?
I dont understand what could of happened, IVe done this plenty of times.
Does anyone know what I should try?
Hopefully this is the right thread and someone can help.
Thanks,
Dave
Did I post in the wrong sections, or does anyone have any ideas as to why this would occur? Any help would be appreciated.
Thanks,
Dave
If you're unable to see if you're in download mode, install adb (inside the Android sdk) then follow the guides on how to reboot into download mode. From there install a stock ROM from Odin (maybe JI6 if you want to). Once it's working, feel free to reflash with Bionix 1.8 or any other ROM flavor of your choosing.
Directions on how to use adb and Odin are in the Vibrant Directory "Bible" on the dev sub-forum.
edit: linkage
edit2: You can also use Droid Explorer to access adb
dsellers2 said:
So,
I downloaded Bionix 1.8 and Flashed through Clockwork. Only after I disable Voodoo of course. After getting all my settings back the way I like it, played a few games, checked a couple emails I placed my phone on the charger. After the phone was completely charged an hour later.
I decided to boot into clockwork and delete my battery usage stats and rebooted. After it rebooted I unplugged the charger and BOOTLOOP.
It shows the vibrant screen and then Snow like a tv. Except there is other colors in the snow. Not many though. Then the vibrant screen and the snow. Your getting the picture, over and over like this even after pull the plug....plugging the charger. I've even tryed going into download mode. I think. It just keeps booting...
So,
Do I have a paper weight?
Will this thing work anymore?
I dont understand what could of happened, IVe done this plenty of times.
Does anyone know what I should try?
Hopefully this is the right thread and someone can help.
Thanks,
Dave
Click to expand...
Click to collapse
Hi.. I know you posted a couple months ago but I'm in the same boat and was wondering if you were able to get out of this. Any help would be much appreciated!! =(
Thanks,
Adrienne
i downloaded the oclf and fixed my lag. later i hit a button called kernals and it was one on there that said voodoo something so i hit it and my vibrant went through some process. where a broad was counting and stuff. then when it was finished my phone rebooted but never went pass the first screen that said vibrant samung but the sound still sounds. how do i go back to normal. call me if you want MOD REMOVAL
sirford1 said:
i downloaded the oclf and fixed my lag. later i hit a button called kernals and it was one on there that said voodoo something so i hit it and my vibrant went through some process. where a broad was counting and stuff. then when it was finished my phone rebooted but never went pass the first screen that said vibrant samung but the sound still sounds. how do i go back to normal. call me if you want MOD REMOVAL
Click to expand...
Click to collapse
ODIN is your friend.
And you've just been added to every CALL SPAM list in the world. (not by me, probably by some 12yr old kid on here)
Never give out your phone number over a public forum.
sorry to hear about the flash, but sometimes it takes a long while on first boot after the voodoo....but ODIN is a lifesaver
Don't worry, you can still completely fix your phone like it was brand new.
Have a look here:
http://forum.xda-developers.com/showthread.php?t=849028
http://androidforums.com/vibrant-tips-tricks/223806-guide-fixing-bricks-odin-errors.html
also here on how to do the simple process of using Odin:
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
I've done probably half a dozen resets/flashes using Odin and I must say, it can be temperamental sometimes, requiring you to restart the process a few times before it doesn't get stuck and hang at a certain portion. It should only take a few seconds to get the process on your phone going, so if you are waiting for several minutes and your phone is still sitting in download mode, you need to restart. HOWEVER, it has always gotten me back to stock in the end. Sometimes I just have to start the process 2-3 times.
If you need to get your phone back into download mode after a failed start, power off the phone (remove the battery if necessary and replace it) just hold the volume buttons and plug in the data cable and it should do so allowing you to restart the process.
Wow I totally don't see prank calls coming your way lol
Still flashing , thanks to odin & tw
Replaced phone number with MOD REMOVAL Please post in the right section next time too
i went ahead and tried to put that t something and s1 something but now its just stuck at the black screen its been like that for a half hour and ive done it about 5 times im just about to do an insjob
I used matt's 1.6 utility to install safestrap, and I know I need to make a backup of my rom to flash to in the event of.... an accident... and most tutorials I have come across seem to leave out a good deal. I spent the last 4 hours on XDA trying to figure this out,
any help would be nice.
so after installing safe strap I noticed it had it's own icon in my app drawer and clicked it.... it said... not installed/not safe. Oh well I thought and clicked it. Install successful. Now it loads when I power off my phone. How to stop this? So now I have 2 bootloaders.
I also found this article on getting C7 onto my gsm droid razr bypassing the CW rom manager so to speak. it wants me to install another boot strap.... do I need it? It will make #3 bootloader. I needed to know If I might brick my testy razr by having 3 at once, so I know how to proceed.
**on a side note... since rooting and removing bloatware and install needed root only apps.... my battery dies in half the time it did before. I could surf porn for 2-3 hours and make a few phone calls of 30 min each, listen to 2 or 3 hours of music and standby for a couple more hours before the battery would power off the phone... now in one hour of surfing my battery drops 30-40% and keeps declining rapidly unless the screen is off (this is why im going to C7 it apparently doesnt have that problem.)
EDIT: So yea..... 3 bootloaders does tank my phone. No power on. Doesnt do anything when.plugging it into the charger either. Luckily the bootloaders alreadry installed let me go from a power off state directly to recovery. And then it put me in a bootloop. Was able to get out of it, and now everything is correct. I even understand how to use this to flash a new rom. But since CWM rom manager doesnt work i have no sleek way of making a copy of my present rom to flash back to, or smooth way to transistion into new roms and out again. Its like taking 20 miles of dirt road instead of the interstate because theres a traffic accident for 6 hours, but it gets me where i wanna go. I noticed its been 7 months since this method came out and this is the best work-around we still have? I dont CWM is ever going to support the razr so im giving up on the shiny glossy buttons. Id like to see a full and complete tutorial for newbs on rooting to flashing a rom with the updated methods you guys have worked on, that way they/me dont have post and.hope to hell someone cares enoughs for 60 seconds to post a reply like "thats bad do this instead....." oh well. Now im off on my own to figure how to make a backup... then ill write a tut.for other poor newbs.like me who could finally afford a razr.
UPDATE: SOLVED
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
XDA mark said:
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
Click to expand...
Click to collapse
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
tallman43 said:
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
Click to expand...
Click to collapse
I can enter download mode normally, so I can use Odin to flash stuff.
I just flashed that kernel I wanted to flash before my phone went trippin, but after flash the same continues. Re-downloading ARHD 40 via my laptop now and going to reflash it via odin, hope that my phone can then let go of it's obsession of trying to get into recovery.
There must be a way to fix this, I didn't make a Titanium Backup for a while. Don't want to lose stuff just because I got some super rare weird problem... again. Why does tech hate me
EDIT:
Realized that I can't flash ARHD 40 because it only comes in zip not tar... anyway, tried flashing the newest version of philz touch recovery, still didn't change anything.
EDIT 2:
Flashed TWRP recovery via ODIN, now everything is fine again. It rebooted into TWRP normally, then choose to reboot the device. Everything is still there, like nothing ever happened.
THANK you lord!
Out of interest, how do you find the HTC 1 compared to the S3?
gsw5700 said:
Out of interest, how do you find the HTC 1 compared to the S3?
Click to expand...
Click to collapse
It's an entirely different phone, especially how it feels and looks. After using the One for such a long time, I find it super weird to hold a S3.. it feels so light and "cheap", though ergonomically the S3 is a tad easier to hold then the One. Overall I enjoy using the HTC One much more as it feels really solid.
Besides that it's fast and stable, what you would expect, but not much faster then a S3 with a good ROM. Screen is really excellent, this is also a big difference from the S3. It's a different type of screen and you can really notice. The speakers are the nicest you can get on a phone and compared to the S3 they are really a league above. The camera is average, sometimes it's great sometimes it isn't. Battery life is comparable to the S3.
Not that I didn't enjoy my S2 and S3 at the time, but I'm not really interested in the Galaxy line anymore at the moment. Samsung really has to do something amazing to get my attention again Will see what HTC brings with the successor of the HTC One, might upgrade to that one. I'm also curious about the iPhone 6 to be honest, the small screen is the main reason I haven't owned an iPhone in my life, if that changes I might want to try it. Or I might just use my current device for a second year for a change, since it's excellent
Many thanks for that, I now intend to take a look at the new HTC m8 - hoping the camera is better!
Me too. If they make a big leap with the camera and bring it on par with the iPhone 5S for example, it would be fantastic. Battery life should also be brought to the new higher standards of the LG G2.
If these 2 things happen they already got me, since it's a near perfect phone. Add some bonuses like making the bezels smaller/screen larger in the same body... don't think I could resist
[Q&A] [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Q&A for [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
gpz1100 said:
I gave up trying to calibrate my compass. I have issues with it in any rom including stock TW. Some of these chips are just broken.
Click to expand...
Click to collapse
After trying many of the suggestions on this thread to fix the compass (my GPS lock is fine), I thought I might have messed up the hardware somehow. However, last night I flashed the 7/12 KT GE kernel, and the compass now correctly points in the right direction.
Germany?
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
TheSt33v said:
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
Click to expand...
Click to collapse
Well in case anyone is curious, this ROM gives me great cell service (full signal on Vodaphone.de) but no data in Munich. I tried airplane mode, disabling/enabling data roaming several times and setting the network mode to GSM preferred, but no luck. Flashing the latest release of Hyperdrive ROM allowed me to use data. Oh well.
flashing google edition on verizon s4 on nc5
I'm a noob and can't figure out if i can use safestrap to flash the dandvh google play edition rom.
verizon galaxy s4 on nc5 build, rooted with towel root and running safestrap 3.75
Viper Audio Working?
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Hi everyone, hoping you all can help me with a problem I'm having with my phone. First, some specs:
ROM: Danvdh GPE 9/30
I am one of those lucky MDK users, I got the phone in May 2013 and rooted early
I had been running the NC5 modem for a while now with no issue. The problem started after I flashed the NG6 modem (from Surge1223's thread) in TWRP. Just fyi, here are the steps I took to flash the modem. Within TWRP, I flashed the zip file, cleared Dalvik/cache, then rebooted.
Almost immediately I started getting random reboots. It rebooted twice, then seemed to settle down, so I decided to wait a day or so to see what my phone would do. Sadly enough, it started rebooting again, so I gave up last night and reflashed the NC5 modem in TWRP using the same method as before. The phone was fine after that, until this afternoon. About an hour ago, my phone froze, and rebooted, but the screen cut off at the Samsung custom padlock boot screen. It seems to be off at this point, but I can't power on the phone without pulling the battery. After pulling and replacing the battery, the phone powers on by itself, but again cuts off at the Samsung boot screen, about 3-4 seconds into the boot process. I've tried booting into TWRP and download mode, with the screen turning off and the device seemingly freezing after 3-4 seconds. I'm at a loss as to what to do at this point.
I'm at work right now, but when I get home, I will see if Odin3 can make some sort of contact with the phone. Any help in the meantime would be greatly appreciated!
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Alxoom33 said:
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Click to expand...
Click to collapse
I would love to, but I can't.
I put a video up on Youtube showing what the phone is doing right now. I don't have 10 posts yet, so I can't post links, but if you go to youtube.com then add "/watch?v=3ey5xD9LodY" at the end of the URL, you can see what the phone is doing.
It is the only thing the phone will do. I've tried doing a hard reset by holding the power button, but nothing happens. All I can do is pull the battery and start this process again. If I hold the correct button combos, I can begin to boot into TWRP or download mode, but the phone cuts off/freezes like clockwork after 3 seconds.
I tried to get Odin3 to recognize the phone, but my desktop doesn't recognize that anything is plugged in when I connect my phone to it, so Odin3 by extension doesn't see anything.
Did you install the Samsung apps on your computer? You need them for the computer to recognize your phone.
To hard boot into recovery you need to hold power button and volume up at the same time, then let go of power button once blue writing appears on upper corner of phone.
Sent from my Xoom Wifi using Tapatalk
I'm sure I have. I've been able to send adb commands to the phone in the past. Now however, my PC doesn't even see that a device has been connected to it (nothing shows up in the device manager, not even an unrecognized device).
The phone will no longer charge when I plug it into an AC adapter either (or at least the LED no longer lights up indicating it's charging).
I have tried booting into recovery several times. Each time, it will begin to boot into TWRP, the blue text, "RECOVERY BOOTING...", will display, then immediately afterwards, the screen will cut off and the phone will freeze, just like in the Youtube video I posted.
I'm afraid the thing is bricked...
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
marioluigi64 said:
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
Click to expand...
Click to collapse
Have you tried a different USB cable/transformer? It sounds like you might just have a charging issue. Not enough juice to get it started.
Allowing a battery to cool down will give it more usable power, which as it heats back up will deplete again. This sounds like your situation... Power off for a few, restart it has enough to begin booting, then depleted again.
The phone cannot run on USB alone it needs the battery to sustain it's operation.
I have tried 3 USB cables, 2 AC adapters, and 2 PCs.
When this started on Friday, my phone was hooked up to my PC at work and showing about 50% battery, but it's possible something went wrong with the battery and it's stopped delivering any significant amount of power or accepting a charge.
So it turns out it wasn't the rom or new modem that was the problem, my battery has decided to kick the bucket. I tried my roommate's battery in my phone and it booted right up as if nothing was ever wrong! Strange that an OEM battery would just die like that, but I suppose that does happen from time to time. Thanks for the help!
matycakes said:
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Click to expand...
Click to collapse
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
TheSt33v said:
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
Click to expand...
Click to collapse
Yeah, I have tried reinstalling it, and I am using the latest version of the app. The fact that you haven't had any issues is encouraging. I'll continue to troubleshoot and see what I can find.
I keep getting this (in CWM touch)
Flashing Google Play Edition
Android 4.4.4
Enjoy!
format() expects 5 args, got 4
E: Error in /storage/sdcard1/danvdh-GE-4.4.4-09-30-2014-VZW.zip
(status 7)
installation aborted
Is it just a bad DL?
EDIT: Tried a new DL, same issue. I want to get this fixed asap
Is cm11 theme manager included in this rom?
brd912 said:
Is cm11 theme manager included in this rom?
Click to expand...
Click to collapse
It is not.