[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.
Related
I am totally stock, unrooted.It all started after I turned on Google Now. I was trying it out for a few days, didnt like it so I turned it off. After that, I noticed a considerable dip in battery life. After checking with better battery stats app I found that the phone would no longer go into deep sleep and the culprit was "mhl-kernel-wakelock". I have tried everything to get rid of this wakelock.
I have tried: phone reboot, battery pull, wipe data from all media player apps and usb service, deleted all my apps, reinstalled them. I tried a full data wipe/reset and wiped cache.I tried charging my phone while off. I deleted all my media off of my sd card and got a new sd card. I tried connecting to windows based pc. Nothing works, the wakelock remains.
I have never used my note 2 to connect to the tv or anything like that. Also my usb functionality no longer works. It wont talk to the computer. The phone will charge though. I have searched google extensively and there is very little information regarding this wakelock. I'm afraid it might be at the hardware level. The only other thing I can think of is buying an MHL cable to HDMI and hook it up and hopefully when I disconnect it it will shut off the MHL mode that it is stuck in. Obviously I could also root and flash a ROM with a different kernel, but I really enjoy stock and the spen features etc.
If anyone has any suggestions im wide open. Thanks
EDIT (2/1/13): I also realized that when I tried Google Now was around the same time that my house lost power during the night and the power flickered WHILE my phone was charging from the wall outlet. I initially attributed the problem to Google Now, while in actuality it makes much more sense that a power surge fried my USB port on my phone.
I know this probably isn't the answer you were hoping for but I think it might be a good idea to go ahead and, assuming you're comfortable doing this, root and unlock your device. I recommend you try out Jelly'Beans' Build 4 ROM. It has all the great features of stock with the bonus of being much lighter on your phone (smaller system ROM file) and you can set it up to look like AOSP Jelly Bean. Or if you really don't want that look and prefer TouchWiz, you can do that too.
I would do this anyway as imho, it's better to be unlocked and free for the remainder of days you own this device, rather than get an OTA and lose the possibility of unlocking ever again.
And this has a good chance to resolve your situation as you would be totally wiping the system partition and chances are thats where the issue is.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
droidstyle said:
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
Click to expand...
Click to collapse
Thanks.I already tried this several times. I tried it from the OS and from the recovery. I also lost my usb functionality so im not even sure if I can flash a new rom with odin.
I think I'm screwed. I can't even access the hidden menu from the dialer pad to attempt change the USB mode. It looks like a hardware failure, even though I haven't done anything out of the ordinary. It would explain why its stuck in MHL mode with the constant wakelock (despite multiple factory resets and data wipes). and why no USB ( tried 3 different cables) cable or any number of computers (3 different computers) cannot recognize, connect, or exchange information with it via USB. This blows.
I registered with Samsung and am trying to fill out a service request through their website, but it just says the troubleshooting guide is unavailable right now and it won't let me get past that step to actually request a service repair. FTW
Just an update in case anyone has this problem. I was able to get the battery drain under control. However, I'm not absolutely sure which setting it was, but under screen settings it was either auto-rotate or screen timeout, but I pretty much changed them all back to default, rebooted and changed them back to the way I liked them. For some reason it disengaged the MHL mode that it was stuck on. This is even after 3 factory resets and data wipes.. all it took was to switch one of those on and off.
The other problem I had was that my USB hub quit working, although it would charge, but not communicate with any computer. After a couple more days though, it stopped working altogether. It wouldn't charge my phone or do anything. I tested my charger and cord with another phone and computer it works/charges flawlessly.
After that, I took it into Verizon (crossing my fingers, since I got my Note II on release day with no insurance... so way passed the 14 day return period) and told them that I did get my phone back in late November, but I had never tried to plug it into my computer since I got it (even though I had and new about this problem for awhile) so I told them it was probably defective from the release date, I just didn't know about it. Long story short, after talking with 3 of the reps and them mindlessly googling dead-end solutions that I had already tried, the manager issued DOA on my device and shipped me a new Note II for free.
F yeah... very happy at this point. The new one I got is not a refurb, runs flawlessly. I rooted, unlocked, and running Clean ROM... all right before the OTA hit.
facing same problem with mhl wake lock and my n7100 note 2 is not detected any more when connecting to PC
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
I have been having issues where my phone have been freezing up at seemingly random times and then getting into a bootloop until i do a hard power off and turn it back on. I've attempted a clean reinstall of the ROM but no luck.
I was going to flash RUU but my USB port doesn't work for data anymore so fastboot is out. (I tried to use fastboot on 2 computers running Win 7/ 8.1 with a couple different USB cables)
Can anyone recommend any sort of troubleshooting solutions to get this ROM (or possibly a different 4.4 AOSP ROM) to run a bit more stable?
admiral licorice chaps said:
I have been having issues where my phone have been freezing up at seemingly random times and then getting into a bootloop until i do a hard power off and turn it back on. I've attempted a clean reinstall of the ROM but no luck.
I was going to flash RUU but my USB port doesn't work for data anymore so fastboot is out. (I tried to use fastboot on 2 computers running Win 7/ 8.1 with a couple different USB cables)
Can anyone recommend any sort of troubleshooting solutions to get this ROM (or possibly a different 4.4 AOSP ROM) to run a bit more stable?
Click to expand...
Click to collapse
Hi, sorry, I don't have an answer necessarily, but I was having the same issue with OmniRom before I moved over to the new partition layout. One thing you might try, though, is going back to stock (or at least some Sense based Rom) and see if you can get ADB/Fastboot working on it then. I noticed that I wasn't able to get it working on AOSP Rom (I think it was PAC-Rom specifically) but when I restored back to my Initial Stock nandroid, I was able to do it (Run the RUU for new partitions). So give that a try before giving up.
But I also had the random freeze, and boot which could only be stopped by the simulated battery pull like you described, and then it would work. A couple times, I would just be using it and it would freeze. A couple other times I would pull it out of my pocked and it was sitting there with the little android dude sitting there in the circle, staring at me. One time I just left it there for a while, and noticed that it actually was booting (kind of) but super slowly. It would sit there for like a minute, and then the antennae would twitch a little, wait 3 seconds, twitch again, wait 3 seconds twitch again. It was like it was running on extreme slow motion on the boot animation. I don't know if it ever would have finished, given enough time, because I never gave it enough time.
Anyway, if anybody has ideas on why AOSP roms seem to do that, I'd appreciate it. Had a similar experience with PAC-Rom, on the old partitions, with random freezes that couldn't be recovered from.
bpaulien said:
Hi, sorry, I don't have an answer necessarily, but I was having the same issue with OmniRom before I moved over to the new partition layout. One thing you might try, though, is going back to stock (or at least some Sense based Rom) and see if you can get ADB/Fastboot working on it then. I noticed that I wasn't able to get it working on AOSP Rom (I think it was PAC-Rom specifically) but when I restored back to my Initial Stock nandroid, I was able to do it (Run the RUU for new partitions). So give that a try before giving up.
But I also had the random freeze, and boot which could only be stopped by the simulated battery pull like you described, and then it would work. A couple times, I would just be using it and it would freeze. A couple other times I would pull it out of my pocked and it was sitting there with the little android dude sitting there in the circle, staring at me. One time I just left it there for a while, and noticed that it actually was booting (kind of) but super slowly. It would sit there for like a minute, and then the antennae would twitch a little, wait 3 seconds, twitch again, wait 3 seconds twitch again. It was like it was running on extreme slow motion on the boot animation. I don't know if it ever would have finished, given enough time, because I never gave it enough time.
Anyway, if anybody has ideas on why AOSP roms seem to do that, I'd appreciate it. Had a similar experience with PAC-Rom, on the old partitions, with random freezes that couldn't be recovered from.
Click to expand...
Click to collapse
Nah, installing a Sense ROM didn't work out for recognizing data over USB. I'm hesitant to flash RUU over wifi ADB (if thats even possible) because I wouldn't be able to use fastboot if something goes wrong.
admiral licorice chaps said:
Nah, installing a Sense ROM didn't work out for recognizing data over USB. I'm hesitant to flash RUU over wifi ADB (if thats even possible) because I wouldn't be able to use fastboot if something goes wrong.
Click to expand...
Click to collapse
That's good you didn't try it over wireless, because as part of the RUU process, it reboots to fastboot, and if all you had was a wireless connection at that point, the process would fail.
bpaulien said:
That's good you didn't try it over wireless, because as part of the RUU process, it reboots to fastboot, and if all you had was a wireless connection at that point, the process would fail.
Click to expand...
Click to collapse
Hmmm.... I may be out of luck then. I'll just deal with the issues until a new Nexus phone is released (if one ever is).
Thanks for the suggestions though.
Hi there! Long time reader, first time poster (TL;DR below...but it should be a quick read anyways )
So I've been using this S2 of mine for almost 4 years now, haven't had any trouble (other than a couple of battery swaps). For the past 6 months or so I've been using CM 12.1 nightlies without issue.
The events:
- The other day, my phone froze (I wasn't using it when it froze, it was when I went to use it that I noticed...it was on the wifi selection screen if it matters), so I held the power button to shut it down, and when I powered it back up, it just froze at the Samsung boot screen (with the usual yellow triangle).
- At this point, I was able to reboot into download mode at will, but any attempt to boot to recovery just led to the freeze at the Samsung boot screen. Also, the phone would automatically reboot itself at this point any time I inserted the battery (I was of course putting the battery in and out trying everything I could).
- I would have reflashed from Odin at this point, but since I was away for a few days I just kept trying to reboot into recovery, to no avail. On one of these attempts (power+vol up+ home) it showed the Samsung boot screen, and then immediately shut down and I haven't been able to get anything onto the screen since
I'm now home, and I can't seem to fix it. If I plug the phone into a charger, the top half or so of the phone gets warm, and it also seems to get warm if it isn't plugged in and I try to power it up. I was thinking maybe the phone was maybe doing the same thing as before and just not showing anything on screen, but I blindly do the steps to get it into download mode, and Odin doesn't recognize anything (drivers are definitely installed). I have also tried other batteries, no luck.
Any ideas of what I might try? I'm willing to do anything. For the record nothing happened to the phone at all when this all happened (no dropping or water damage or anything, just my attempts at booting into recovery). Maybe I should try a jig? I'm also open to opening the phone if there's something I can do, though I don't have experience with this.
Thanks so much for any suggestions!
TL;DR: phone froze (running CM 12.1 nightly), held power to shut it down, and then consistently froze at the boot screen on any attempts to power it on. After a few attempts at booting into recovery (the phone would only freeze or enter download mode) the screen suddenly shut off and I haven't seen anything on it since no matter what I try. I can't think of anything that happened to the phone I'm open to any and all suggestions! Thanks
One sentence amongst your description stands out like a 'sore thumb'.....
That the device heats up towards the top when you attempt to charge it.......
Until you try a jig I can't be certain, but that heating coupled with a dead/unresponsive screen along with a lack of recovery and/or download modes (download mode is 'hardwired' into the device, and NOTHING should be able to corrupt it) are the primary symptoms of a failed motherboard.......
That is my opinion based on my experience in these forums and personal experience with a (now dead) S2 (one of two that I own).........
Get the jig just to be sure, but I'd be surprised if it had any effect.....sorry to be typing something you don't want to read, but you said it yourself, the device is 4 years old....it's been in service roughly twice as long as most smartphones, and they don't last forever....
http://i.imgur.com/rVnFwJM.jpg
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
smacsmac said:
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
Click to expand...
Click to collapse
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Sorry it took me a while...the jig was in the post haha. It didn't do anything at all (no response when I plugged it in) so I think it's safe to say you were bang-on and the motherboard failed! Happily using a new S2 (with CM13.0 now ) on behalf of my friend though.
Thanks again.
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Elaias said:
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Click to expand...
Click to collapse
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Its hard to tell you and hard to accept. You can almost give up the hope, your NAND Chip is just what we call " wear-out ". In the most cases no write is possible anymore, the funny part is -> sometimes read is still fine. If that is the case: The system is booting and working, but saving just nothing. The NAND is frozen to its state before it broke.
At our local store, customers come to us with issues like " Factory Reset impossible ", "Can't delete my Files" "Can't create files". All these Devices have inaccessible NAND's and inaccessible Recovery. Only Bootloader is working, but as the NAND is broken, flashing doesn't change anything.
smacsmac said:
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Click to expand...
Click to collapse
yeah, flashing with odin did the trick. now running cm13 and everything works fine. sorry to hear that your phone turned to brick.
Hi I'm pretty new to rooting and flashing and all that modifying my phone stuff. Firstly I'd like to thank @roirraW "edor" ehT and @LASERWOLF452 for the guides on rooting my phone which I've been trying to do for over a year, but just now finally succeeded.
Now I've run into a problem leaving my phone useless. Not sure if software or hardware problem. After I turn my phone on, which sometimes that doesn't work, it gets to LG logo then screen goes black, all buttons unresponsive including power button. I think I softbricked my phone because sometimes it gets stuck in the bootloop. (Edit: It doesn't go into the bootloop that often, mostly just blackscreens after LG logo or when I turn it on, it vibrates and that's all, logo doesn't even pop up.) Sometimes when I pull the battery out, wait a few minutes, then put it back in I can get it to turn on and get to the PB Screen after the LG logo (because I have the PitchBlack theme installed). Sometimes I can even get to my home screen even open an app, but then everything freezes and screen goes off. Usually after any of these attempts, doing anything with the power button results in nothing, not even a single vibration. It makes me think that the phone is on just the screen is unresponsive. So I have to pull the battery out and try again. I held volume down and power button til LG logo came on, then let go of power button and immediately held it again until I got into recovery. Scrolled down to factory reset, clicked yes, then most of the time the phone shuts off and the LG logo comes on and goes black again. One time it got TWRP to open up. But it froze and screen went black. I finally got it to go into TWRP again randomly, but trying to click on the "Advanced" key in the process of wiping the dalvik cache my phone half froze. By half froze I mean just that. The status bar showed my phone's changing temperature, the minutes were changing and the battery percent showed. When I went to slide the arrow to wipe the cache it wouldn't move. It was like the bottom part of my touchscreen wasn't working. Then I pressed the power button and it locked the screen and said slide to unlock but I couldn't slide the slider. So it's like half of my phone functioned and half didn't.
I wasn't having major issues like this except occasionally getting my phone to receive a charge or turn on. This booting issue started yesterday when I was at work. I was just playing pokemon GO and decided to charge my phone. I unplugged a charger for a Bose speaker (one of those color sound ones) and plugged it into my phone and it immediately shut off and wouldn't get past the LG logo. After a long night of failed attempts to get it working, this is where I am now.
I rooted my phone last week. After the first night I freaked out because I couldn't get my phone to turn on the next morning, I forgot to charge it and the battery was drained. It wouldn't even receive a charge. Then I googled some stuff and found out that taking the battery out and putting it back in can sometimes get it to receive a charge. Then I have to unplug it before turning it on or else it'll just reboot with the battery logo. I've had to do this every time when the battery is completely drained.
I rooted my phone by downgrading to 35B and doing all that LG FlashTool stuff then used Stump. Then installed TWRP and CM13. The most recent thing I have been messing with is Xposed Installer and downloaded and activated a few modules yesterday. Could those have done something? A few were out of date that I decided to give a try. After I turn my phone on and feel it vibrate and all that, I think it actually is turning on. Whether it makes it to the LG logo or not, it seems like it is turning on and maybe the screen just isn't functioning the way it's supposed to. I can't turn it on again, holding the power button does nothing.
Sorry that this was really long, tried to give a detailed description of my issue. Phone has been useless for 24 hours now. It really sucks because I need it, will be traveling through a few airports later today and need to call people to make sure I have rides. Only thing I can think to try is get a new battery. I would really appreciate any help that anyone can provide! I'm desperate.
Update: Recently I have been able to get the phone to start up like normal and get to the home screen, check my texts, that kind of stuff, but within 30 seconds it freezes and shuts off.
I'll confess, I didn't read everything, but a few questions and suggestions. FYI if it were me I'd skip right to suggestion #3.
Can you still access TWRP?
If so,
1. Try wiping Cache and Dalvik /ART or if that doesn't work wipe Cache, Dalvik /ART and Data.
2. If both don't help, wipe them again, then do a fresh flash of whatever preferably stock based ROM you want and the appropriate Bootstack.
3. I would flash the 10B TOT and start fresh. It's often enough the experience of users who flash non-stock or international stock-based ROMs to have various troubles.
No matter what caused the problem, TOTs contain more partitions that KDZs and flashing TOTs can fix problems that KDZs can't.
Good luck, keep us posted.
roirraW "edor" ehT said:
I'll confess, I didn't read everything, but a few questions and suggestions. FYI if it were me I'd skip right to suggestion #3.
Can you still access TWRP?
If so,
1. Try wiping Cache and Dalvik /ART or if that doesn't work wipe Cache, Dalvik /ART and Data.
2. If both don't help, wipe them again, then do a fresh flash of whatever preferably stock based ROM you want and the appropriate Bootstack.
3. I would flash the 10B TOT and start fresh. It's often enough the experience of users who flash non-stock or international stock-based ROMs to have various troubles.
No matter what caused the problem, TOTs contain more partitions that KDZs and flashing TOTs can fix problems that KDZs can't.
Good luck, keep us posted.
Click to expand...
Click to collapse
Sorry I know it was super lengthy. Sometimes I can access TWRP and sometimes I can't. I'm getting so aggravated with my phone! I think I successfully wiped Dalvik which did not help so I'll try to do the others if my phone wants to cooperate with me. Most of the time it doesn't even want to boot into recovery. Most of the time after clicking Yes under factory data reset the LG logo pops up then my phone just goes black.
Update: Wiped Davlik/Art, Cache, and Data. Rebooted and saw the CM13 logo instead of PB but then immediately shut down.
Yeah, I'd definitely go the 10B TOT route.
I've rooted a few phones, but I'm not a ninja like these other xda'ers are. I'm running Jasminerom 8.0 (which is excellent on the g3), a couple of weeks ago, I tried Dirty Unicorns, but it didn't seem to play well with my phone, so I went back to JR 8.0 (by restoring my nandroid backup) then tried to upgrade to JR 9.0 then 9.1. I didn't even get the LG start screen, the screen was black, but I could tell the phone was on by a couple of noises. I did hyelton's "[Guide] LG G3 Stock Firmware (Go Back to Stock) KDZ & TOT Method With LGUP" http://forum.xda-developers.com/showthread.php?t=2785089 It puts the phone back to dead stock, you have to root again and reinstall twrp, then you can go to the rom you want. It scared me pretty good, but within a day or 2, I had my phone back to where it was. Don't forget to thank the devs who post these guides, they can get you out of almost any jam you get into.:good:
FesterBesterTester said:
I've rooted a few phones, but I'm not a ninja like these other xda'ers are. I'm running Jasminerom 8.0 (which is excellent on the g3), a couple of weeks ago, I tried Dirty Unicorns, but it didn't seem to play well with my phone, so I went back to JR 8.0 (by restoring my nandroid backup) then tried to upgrade to JR 9.0 then 9.1. I didn't even get the LG start screen, the screen was black, but I could tell the phone was on by a couple of noises. I did hyelton's "[Guide] LG G3 Stock Firmware (Go Back to Stock) KDZ & TOT Method With LGUP" http://forum.xda-developers.com/showthread.php?t=2785089 It puts the phone back to dead stock, you have to root again and reinstall twrp, then you can go to the rom you want. It scared me pretty good, but within a day or 2, I had my phone back to where it was. Don't forget to thank the devs who post these guides, they can get you out of almost any jam you get into.:good:
Click to expand...
Click to collapse
I was literally in the middle of following the instuctions in the guide you linked, then when I have FlashTool all ready, I noticed my phone turned off. I read that I might have to put it back in download mode after messing with device manager. Now the problem is I can't get it to download mode. I can get the download mode and blue dots image, but doesn't go to the next screen with the "firmware update don't unplug phone" it just goes to blackscreen help I was literally just in download mode now my computer says it doesn't recognize the last usb device that I plugged in
ArcticPat said:
I was literally in the middle of following the instuctions in the guide you linked, then when I have FlashTool all ready, I noticed my phone turned off. I read that I might have to put it back in download mode after messing with device manager. Now the problem is I can't get it to download mode. I can get the download mode and blue dots image, but doesn't go to the next screen with the "firmware update don't unplug phone" it just goes to blackscreen help I was literally just in download mode now my computer says it doesn't recognize the last usb device that I plugged in
Click to expand...
Click to collapse
Do a battery pull to make sure it is shut off, then do the Vol up while plugging in the usb cable. Even if the screen stays black, it should still go into download mode (that's exactly what had happened to me). When you go into Device Manager, you should see LGE Modem listed under Ports, and keep following hyelton's instructions. I was sure mine was dead, but it worked fine.
FesterBesterTester said:
Do a battery pull to make sure it is shut off, then do the Vol up while plugging in the usb cable. Even if the screen stays black, it should still go into download mode (that's exactly what had happened to me). When you go into Device Manager, you should see LGE Modem listed under Ports, and keep following hyelton's instructions. I was sure mine was dead, but it worked fine.
Click to expand...
Click to collapse
I managed to get into download mode, two additional times. The first time, after started FlashTool, it said download failed at 10%.After an hour I finally got it to go into download mode again. Got to 57% then said download failed. My phone won't stay on or something. Everything was going smoothly, then boom black screen download failed. This has been the problem the entire time with my phone. Sometimes I can get to the homescreen, open my texts, browser an app or 2 then freeze and black screen. It won't stay on long enough for FlashTool so what the hell do I do now?!
Now my phone won't even vibrate when I plug it in while holding Vol Up. It comes up as something slightly different in device manager though. I kept FlashTool open even with the failed download, but it says "Can't change to download mode" in the port 1 box.
Also sometimes after plugging in, when it does vibrate, the LG logo comes on instead of DL mode. When that happens my phone appears as something QualCom in device manager then disappears.
Also, does it matter if my COM41 says 'in use'?
ArcticPat said:
I managed to get into download mode, two additional times. The first time, after started FlashTool, it said download failed at 10%.After an hour I finally got it to go into download mode again. Got to 57% then said download failed. My phone won't stay on or something. Everything was going smoothly, then boom black screen download failed. This has been the problem the entire time with my phone. Sometimes I can get to the homescreen, open my texts, browser an app or 2 then freeze and black screen. It won't stay on long enough for FlashTool so what the hell do I do now?!
Now my phone won't even vibrate when I plug it in while holding Vol Up. It comes up as something slightly different in device manager though. I kept FlashTool open even with the failed download, but it says "Can't change to download mode" in the port 1 box.
Also, does it matter if my COM41 says 'in use'?
Click to expand...
Click to collapse
Now you're getting into territory that I have no experience with. I'm sorry I can't help any farther, I hope some of the more experienced xda'ers can help you out.
FesterBesterTester said:
Now you're getting into territory that I have no experience with. I'm sorry I can't help any farther, I hope some of the more experienced xda'ers can help you out.
Click to expand...
Click to collapse
lol thanks for your help! The only issue I've run into the past hour is that I haven't been able to get into Download Mode. When I hold Vol Up and connect USB it either loads the LG logo or just goes blank. Doesn't give me the 'download mode' with the blue dots.
So I'm guessing it's a bad thing if my phone shows up as Qualcomm HS-USB QDLoader 9008 (COM9)?
Phone just shuts off too fast to do anything. If I successfully make it to download mode, only shows for two minutes in device manager. Qualcomm only shows up for about 2 minutes too. What do I do? I can't even flash the 10B TOT because of this.j
It used to be hard to get the battery to charge, but now I can't get it to charge at all!
Update: I realized, the longer I leave my phone alone, the longer it stays on. I waited an hour then tried Download Mode again. Phone stayed in Download Mode long enough for me to get to the blue screen and the red 3. I forgot what to do when I got to this point so I just let it go and it turned off by itself. I took out the battery, then tried to reboot and it hit the LG logo and the little Android when you first set up your phone then black screen.
Update 2: After waiting another hour, I got the phone to sort of start up. Got to the LG logo, then the green android with a blue loading bar underneath then wham! Green screen saying Tz crash! DemiGod Crash Handler. And some other stuff. What the heck is this? Never even heard of it before.
Update 3: tried to flash again, reached the blue screen with the red 3, pulled out USB and battery then tried to boot up and doesn't even boot up.
Sorry for double post, but this is a huge update. I realized the longer I leave my phone alone, the longer it will stay on. So I left the battery out for an hour. Finally I was able to flash 10B TOT and got to the blue screen with the big 3 on it. I wasn't sure what to do so I just left it there and it eventually shut itself down. Tried to boot up and same thing, black screen after LG logo. Does this mean I'm out of luck @roirraW "edor" ehT ?
Don't tell me this has been a hardware issue the whole time... I even tried new batteries today when I went to a cell phone outlet. Tested 4 LG G3 replacement batteries all with the same blackscreen after LG logo
It does sound like hardware, but its very possible the battery itself is the only issue. Unfortunately, without a spare to try, I don't know any way of finding out for sure if that's the issue without buying a new battery. LG's had them on sale for $15 from time to time, but I don't know if they are now or if they're in stock. On the one hand, I'd hate to see you buy a new one locally only to find out that doesn't fix anything but if the battery is the only issue it's a shame to write the phone off. If you lived around Columbus, Ohio I'd offer for you to try my battery just to see what happens.
There definitely has been enough of a precedent of user's batteries being the culprit with this phone.
That's what I get for reading only 5 out of 6 of the new posts. Sorry, yeah, it doesn't sound like there's much hope. Glad you at least had a place to try a different battery without buying one. I don't know what else to suggest - you could try sending it to LG for service. I can vouch for their warranty service - I can't personally report on their out of warranty. In warranty they returned my tablet fixed four days after they paid to have it packaged and shipped to them.
EDIT: Nevermind, only read part of the post and provided bad advice, lol.
roirraW "edor" ehT said:
It does sound like hardware, but its very possible the battery itself is the only issue. Unfortunately, without a spare to try, I don't know any way of finding out for sure if that's the issue without buying a new battery. LG's had them on sale for $15 from time to time, but I don't know if they are now or if they're in stock. On the one hand, I'd hate to see you buy a new one locally only to find out that doesn't fix anything but if the battery is the only issue it's a shame to write the phone off. If you lived around Columbus, Ohio I'd offer for you to try my battery just to see what happens.
There definitely has been enough of a precedent of user's batteries being the culprit with this phone.
That's what I get for reading only 5 out of 6 of the new posts. Sorry, yeah, it doesn't sound like there's much hope. Glad you at least had a place to try a different battery without buying one. I don't know what else to suggest - you could try sending it to LG for service. I can vouch for their warranty service - I can't personally report on their out of warranty. In warranty they returned my tablet fixed four days after they paid to have it packaged and shipped to them.
Click to expand...
Click to collapse
The guy almost didn't let me try the battery. It was a dinky little stand in a farmers market and I was like let me see if they have any batteries. Luckily they did and I was like can I try it? He had the audacity to say sure but that's 20$ extra. Then I said how much is the battery? He said $40. THIS GUY!!! I almost had to beg just to see if it worked, and he finally agreed. He wouldn't even let me do it myself so I gave him my phone and he tried 3 different batteries and still the same problem.
I really appreciate that you would offer a stranger to test out your battery. It's funny that you live in Columbus because I actually go to school near there! I don't go to OSU but I go to OWU in Delaware, Ohio. But you are right, I'm not currently there but will be there soon.
Anyway, I decided that I had given it my all after trying different batteries, flashing the 10B TOT, etc. and made myself go to the Verizon store. Told the guy that greeted me that my phone wouldn't boot. Mind you I'm a little nervous because I don't want them to find out it's rooted if the 10B TOT didn't flash correctly, but I figured I'd had this phone for over two years, it's out of warranty so whatever. He tried to boot it and got nothing, not even the LG logo. So he said since the screen isn't cracked and no water damage I can get a new phone for free. You should have seen my face, my jaw dropped. I said "What?" He told me I have some warranty extension insurance. I said I know I had some insurance where I paid like 8$ a month, but I canceled that last year. He told me no, you have insurance and you pay 9$ a month. I was astonished and was like wow I thought I cancelled it, oh well, if it fixes my phone for "free" then let's do it. So now I'm eagerly waiting for the phone to arrive in the mail. I've had a brick for 4 days now so I'm feeling all kinds of disconnect. My only regret is that I didn't go into Verizon earlier.
So I'm hoping their warranty service is as great as you say. My only fear is that when I put my current battery, sim, and back cover on the new phone that it won't boot. I suppose at least I'll know for a fact that it's the battery at that point. Weird though that I've had this battery for two years and not a single issue...
Would it be wise to go through the root process again? I did all this in the first place just so I could cheat in pokemon, but then found so many cool modules from Xposed that made my life feel that much better.
ArcticPat said:
Would it be wise to go through the root process again? I did all this in the first place just so I could cheat in pokemon, but then found so many cool modules from Xposed that made my life feel that much better.
Click to expand...
Click to collapse
Only you can determine that, sorry mate.
roirraW "edor" ehT said:
Yeah, I'd definitely go the 10B TOT route.
Click to expand...
Click to collapse
I am on fulmics ROM 5.3 with 35B bootstack. Want to go back to kk10B what should i do.. Like do i need special .dll file as i use 35B bootstack?
Never used kdz or tot except for 10B on my phone. Means Never used kdz or tot to flash official lp or MM
Sent from my LG-VS985 using Tapatalk
minhas729 said:
I am on fulmics ROM 5.3 with 35B bootstack. Want to go back to kk10B what should i do.. Like do i need special .dll file as i use 35B bootstack?
Never used kdz or tot except for 10B on my phone. Means Never used kdz or tot to flash official lp or MM
Click to expand...
Click to collapse
The 35B Bootstack should allow you to use the original .DLL, because it's the correct combination of partitions from both 12B and 35B - which are necessary in order to be able to get into TWRP and as far as I'm aware allow using the old .DLL but also as far as I know and have experienced, you can use the newer .DLL any time. It's only when you're 100% stock 35B or higher that you can't flash the TOT without the newer .DLL, and can't flash KDZs older than 35B.
See post #5 of this thread for a link to a post. The post has another link to directions for Verizon. You can get the 10B TOT and the newer .DLL from my Android File Host link the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, also in my signature below.