Related
My phone has gotten super sluggish on the last couple rounds of flashes. ParanoidAndroid 2.16 was solid for a day but I started losing it as well, 2.17 was freezing. I'm totally back to stock rom. I tried installing PA, Slim and even a CM9 Seraphim, and the latest CM10 nightly, everything is freezing the phone.
The stock rom is disturbing, it had big gaudy icons, much squareness, tacky color scheme and a big gold pen on the screen. No rom is better than a stock rom, that's for sure, I about vomitted. Even stock rom via odin was boot looping, until I flashed CWM. It booted but its barely even able to stay on for long unfrozen.
Is this a hardware issue? It's not like I overclocked it or anything. I cant imagine what could be causing it. I know PA is good, I'm sure slim and seraphim are too. PA was very fast for about a day until the phone went downhill this afternoon.
Any ideas?
I did some more testing and this is the result.
[finding update package...
[opening update package...
[installing update...
[assert failed: getprop("ro.product.device") ==SGH-I717"
more stuff like that
then it says also
[E:Error in /sdcard/pa_quincy-2.17-etc etc etc
[(Status7)
[Installation aborted.
I had copied several roms to both the sd and the internal
Now I tried /emmc/aokp_quincy (09/28) etc...
It installed completely. I wiped the cache, reset and dalvik.
I'll installed gapps, one of the tmo radios for JB and reboot. But I was able to do this from /sd_card where I had earlier been unable to read the zip files.
I already know its toast, because the start button on the welcome screen is already freezing and the screen fades are glitching badly on any rom, stock or not.
Status 7 = incorrect cwm. Use latest cwm or twrp.
Sent from my Note...where BIGGER is better!
djbrian52 said:
Status 7 = incorrect cwm. Use latest cwm or twrp.
Sent from my Note...where BIGGER is better!
Click to expand...
Click to collapse
I went out and bought another one, so now what? I guess I can put my extra sim in it.
Let me hurry and root this new one I got Samsung Galaxy Note x2 now!
A format of the EMMC partition and the external card should clean the old phone up nicely ...
But be sure to move pictures etc...to pc first or they will be lost ...
You probably didn't need a new device ....just a deeper cleaning ..g
gregsarg said:
A format of the EMMC partition and the external card should clean the old phone up nicely ...
But be sure to move pictures etc...to pc first or they will be lost ...
You probably didn't need a new device ....just a deeper cleaning ..g
Click to expand...
Click to collapse
Edit:
Now I have two SGH-i717, both have TWRP. 1 has CM 9.1.0 quincyatt Aug 28 The other has H0tsauce 20120817.
Bother are not very responsive, very very sluggish. I have absolutely no idea why. Could someone please tell me? I'm sure I have made a mistake with something but I cant remember what.
neko_tensai said:
Edit:
Now I have two SGH-i717, both have TWRP. 1 has CM 9.1.0 quincyatt Aug 28 The other has H0tsauce 20120817.
Bother are not very responsive, very very sluggish. I have absolutely no idea why. Could someone please tell me? I'm sure I have made a mistake with something but I cant remember what.
Click to expand...
Click to collapse
I'll buy one off from you for $100 (one hundred bucks)
considering a brand new one, on contract going for $99
I'm being serious... :good:
condition:
barely used.
AT&T or T-Mobile version ?
and as for the error...
yeah +1 on that last advice !
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
Q&A for [ROM][E970/E971/E973]LG Official Kitkat 4.4.2[stock]
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.
Before posting, please use the forum search and read through the discussion thread for [ROM][E970/E971/E973]LG Official Kitkat 4.4.2[stock]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Music from SD Card
I just flashed the rom on my e970 and everything works including the phone seeing the SD Card but I can't get any music player to read the music that is on the sd card. Any help would be greatly appreciated.
Use sd scanner app from play store, that works fine for me.
Will this support Mod kernels? I think that's what I want to say but I'm not a complete Android geek.... Yet
2g-3g switch problem
I can't switch to WCDMA from gsm. It only receives 2g signals.
When I try to launch mobile networks , it crashes.
I couldn't locate the modem settings in engineering mode either.
i have thesame problem...
Upgrading to CM12 Lollipop
Hi, I'm trying to upgrade to Lollipop from this ROM and at first while flashing the CM12 zip i encountered the error "This zip is intended for gee, geeb" etc. So, I tweaked the updater-script and removed the assert and ran the script which installed the ROM but I'm unable to install the Google Apps. I tried with all gapps packages (minimal, micro, full), but none of them works. Can you please help me out?
Does this have anything to do with build.prop? Even though I flashed the fix to show as ATT e970, the CM12 updater-script identified this device as "geehrc4g"??Also, build.prop has some lines like
ro.com.google.cliendidbase.am=android-kt-kr
ro.com.google.cliendidbase.am=android-kt-kr
Do you know where can I find the exact build.prop for e970 (Kitkat)?
Device: LG - e970
Recovery: TWRP 2.8.3.0
is all good w the e971 and this rom?
Hi, just wondering how everything functions on the e971 with this rom? Flashing roms is new to me and am so bummed to finally receive word from Rogers there will be no official update for this device which is in my opinion unacceptable buying a flagship device and getting only 1 update for it 6 months later when the phone manufacturer has updated it, I'm done with them, anyways some help would be appreciated as I need my phone to function properly, I am on official JB 4.1.2 from Rogers, I have unlocked the device to be used with any carrier, now I am planning on rooting using the zv9-zvb universal root method, i was then planning on unlocking bootloader using freegee and then using freegee to install cwm phils touch and then gonna install this rom, anyways are those the propper steps and if I so will all functions of my e971 work as they should with this rom?
Also if i need to go back will it be as easy as downloading paulicats rogers 4.1.2 zip and using cwm to install it and revert back? Any help would be greatly appreciated and if your ever in my neck a the woods I'll buy ya a beer. Thanks.
Working fine for me
This is my first android device so I was attempting this for the first time, I was on Stock JB. First I Rooted the phone(universal root kit), unlocked its boot loader(app from playstore), was taken to cwm, tried to flash the ROM it didn't work a status 7 error occurred, then I flashed philz recovery, flashed the ROM again and its working fine.
I am new to this android world so this may sound noob but is there a way to backup my apps only so that I don't have to re install them every time I flash a new ROM. (Will be trying a lot of roms from now).
lg optimus g e971
When flashing the kittkat do I need to us cwm and be rooted
how to flash e970 stock ROM!
I tried it by installing zip via cwm recovery but it says error in zip.
Flawless Installation
I just installed this ROM on my LG Optimus G E971 and the entire installation was simple and flawless. Prior to this ROM, I had [ROM][5.1.1] [GEEB] [Mako base] Unofficial CM-12.1 which is a great ROM too, however, I wanted to try something that was based on stock. I have the latest version of CWM for LG Optimus G E971.
This is how I installed the following ROM:
1. Downloaded the ROM onto my phone
2. Booted into CWM recovery
3. Wiped data/factory reset
4. Wiped cache Partition
5. Installed ROM
6. Rebooted
Once I have used this ROM as my daily driver for a while, I will get back and share my opinion and thoughts about it.
I stumbled on to this rom and I must say it is very good. There are only two issues I am having that hopefully someone can help me out with. The first issue is an annoying data network setting prompt that happens when I boot up which tells me that I will incur additional data charges. There is a setting under mobile networks that is checked called "ask when data connected" Whenever I try to uncheck it it reverts back to being checked. The second is under access point names. There are two other apn there that I cannot delete for some reason. Does anyone have any ideas how I can resolve these issues?
how do i flash e973 kk flash to my phone?
first of all, im sorry to bring back an old thread back to life, also for my lack of knowledge,
but id really love to install KK on my e973.
I managed to root my phone using root with restore by Bin4ry, but im lost at the steps forward from that.
Could anyone advise me with the prerequisites, tools and steps?
Thanks
Mobile network not working
The only thing that doesn't work is data/mobile network connection. I can make calls and receive texts, but data doesn't connect. What are some fixes I can try?
Kiplacon said:
The only thing that doesn't work is data/mobile network connection. I can make calls and receive texts, but data doesn't connect. What are some fixes I can try?
Click to expand...
Click to collapse
Try flashing the jellybean modem and see if that fixes the issue.
Kilogrm said:
Try flashing the jellybean modem and see if that fixes the issue.
Click to expand...
Click to collapse
Just straight on top of the rom, or should I do a fresh install?
EDIT: Also are there different versions of the modem? This post only has one: http://forum.xda-developers.com/showthread.php?t=2220048
Kiplacon said:
Just straight on top of the rom, or should I do a fresh install?
EDIT: Also are there different versions of the modem? This post only has one: http://forum.xda-developers.com/showthread.php?t=2220048
Click to expand...
Click to collapse
Yes the one you have linked to. Just reboot into cwm or twrp which ever recovery you have and flash it. Once done reboot.
Kilogrm said:
Yes the one you have linked to. Just reboot into cwm or twrp which ever recovery you have and flash it. Once done reboot.
Click to expand...
Click to collapse
I tried flashing the modem, but it doesn't seem to have any effect. I'm still getting this error (i.imgur.com/Ds2sHYc.png) and everything works the same as before (but at least nothing new is broken).
What APN Settings are you using?
Kilogrm said:
What APN Settings are you using?
Click to expand...
Click to collapse
I'm not really sure what APN is, but after Google-ing it I found this on AT&T's support site (att.com/esupport/article.jsp?sid=KB424489&cv=820#fbid=lMQAN_Ixyrx).
I don't know what it did, but following the instructions fixed the problem
Thanks for the advice
Foolish and frustrated; I refuse to belief that I now have just a light up Nexus 5 paperweight. I had recently purchased a Nexus 5 Android phone and I absolutely loved it. I unlocked and rooted it and had it tweaked and tuned like a thoroughbred. It was clean trimmed and snake quick. I then received the notifications that 5.0 Lollipop was available to download and upgrade to I was keen to see how much better my phone could be. The upgrade downloaded fine but the installation failed again and again, so I thought I might have installed an app or something that may be interfering with the 5.0 upgrade. I figured wiping and resetting to stock would allow the upgrade and then I would just fine tune it again.
I clicked to wipe and reset – The phone indicated that the wipe was successful but then the phone went black and then lit up with the black and white Google Logo and that is where it remains. (A lit up paperweight)
Is there any way this phone can be salvaged?
Again needing a phone I purchased another Nexus 5 and although the tweaking I had down to the first one far outperformed this new one, I have not done anything other than upgrade it to 5.0 Lollipop.
I would love it if I can resuscitate the first one and just use the second new one as back up phone.
Is there any hope?
Boot into bootloader and flash the update manually. Ota only work on pure stock set ups.
zelendel said:
Boot into bootloader and flash the update manually. Ota only work on pure stock set ups.
Click to expand...
Click to collapse
Thank you very much for your reply. I would love to try that fix, how exactly would I go about doing that?
cjangione said:
Thank you very much for your reply. I would love to try that fix, how exactly would I go about doing that?
Click to expand...
Click to collapse
Check the nexus 4 section for everything going you need
Q&A for Vanir Lollipop Build...
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.
Before posting, please use the forum search and read through the discussion thread for Vanir Lollipop Build.... If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Vanir
Bassdj427 said:
I'd redownload it...didn't have this problem
Click to expand...
Click to collapse
Battery any better than CM12 version
working LOLLIPOP!
i've been running this bad boy for most of the morning, so buttery smooth and havent yet had a hitch!
Camera
For those with issues with camera, I used the gapps from the CM12 page, and everything works perfectly. I have to agree with those who say that this is the best lollipop build yet!
Anyone have issues with your phone not charging?
Idk if its the ROM or what but I just purchased 2 caseology batteries off of amazon and when I put them in it sees a sim card but it shows now number or sim in settings. Put the original battery in and still nothing. Tried everything but a new sim
issues
My phone runs warmer than usual with this rom and for some reason I'll get notification of an app finished installing and I clear the notification, and it pops back up in 5-10 seconds....anyone know what this could be?
Hey guys haven't dug much into lollipop anyone know where the boot animation is kept at. Is it as easy to change as it was in KitKat?
I'm looking for the new TWRP to flash this new Vanir L. Can anyone help me out?
dfogelstrom said:
I'm looking for the new TWRP to flash this new Vanir L. Can anyone help me out?
Click to expand...
Click to collapse
Most people are reporting it is flashing fine on 2.8.0.0 as the vs985 does not have a 2.8.1.0 build yet. If you are having issues with TWRP though, you can try Philz recovery. It is already Bump'd and ready to be flashed just like TWRP was.
Ahh, thank u!
I did flash with Philz and booted the Vanir Lollipop. Now when it came time to restore my CM11 I flashed back to TWRP via flashify then restored my nandroid. Kind of a pain, but to see lollipop, it was worth it. Def not ready for me to be a DD.
Anyone having a problem restoring TiBu in 5.0??
dfogelstrom said:
Yes, sleek ROM, but after installing my apps from scratch via play store, I still ended up stuck at the commotio screen. I know TiBu is a no go, but why would this happen over 5 times...tried all different ways. And always a clean install. After I get it all set up and backup...then next boot will get stuck? Anyone having problems with getting stuck at the Commotio boot screen after a few boots?
Click to expand...
Click to collapse
(quoting from the other thread because I don't have the post count)
I've had this same issue with both the CM12 and Vanir builds of 5. I've done clean installs of both, with both TWRP 2.8.0 and Philz. I even backed everything up and wiped internal and SD storage - everything off the phone. The first boot is always slow, which I expect. I setup and get everything updated then return to recovery and make a backup. The phone won't boot after backup. It will be stuck on the CM/Commotio boot animation.
Couple things I know: it's not caused by the act of making the backup. I just restarted my phone and it's not coming back up. Flashing a previous backup won't bring it back. Clearing cache/ART won't do it either. However, if I dirty flash the ROM and gapps my phone does boot up correctly again.
I avoid rebooting now.
Is there a way to sync my contacts back? When i flashed it i lost my contacts and when i try to import them back in it fc saying it stopped working. And how to i restore all of my old settings without using tibu?
ToF_Itachi said:
Is there a way to sync my contacts back? When i flashed it i lost my contacts and when i try to import them back in it fc saying it stopped working. And how to i restore all of my old settings without using tibu?
Click to expand...
Click to collapse
Did you not back your contacts up to google? Or do you keep them locally only?
stinkynathan said:
(quoting from the other thread because I don't have the post count)
I've had this same issue with both the CM12 and Vanir builds of 5. I've done clean installs of both, with both TWRP 2.8.0 and Philz. I even backed everything up and wiped internal and SD storage - everything off the phone. The first boot is always slow, which I expect. I setup and get everything updated then return to recovery and make a backup. The phone won't boot after backup. It will be stuck on the CM/Commotio boot animation.
Couple things I know: it's not caused by the act of making the backup. I just restarted my phone and it's not coming back up. Flashing a previous backup won't bring it back. Clearing cache/ART won't do it either. However, if I dirty flash the ROM and gapps my phone does boot up correctly again.
I avoid rebooting now.
Click to expand...
Click to collapse
Yeah man. Its really messed up. I'm just staying on cm11 nightlys lol!! Check out the thread I started about multiple partitions on my SD. I posted a screenshot and everything. Lmk what u think about that? Could it be from all the bs we have been going through??
Lazereth said:
Did you not back your contacts up to google? Or do you keep them locally only?
Click to expand...
Click to collapse
See i dont know how to back them up through google. I never bothered to mess with it.
ToF_Itachi said:
See i dont know how to back them up through google. I never bothered to mess with it.
Click to expand...
Click to collapse
Did you check to see if verizon has them backed up with the cloud?
I asked this on the main thread and just saw this at the very end of the thread but does any one know a fix for the remote?
That's the only thing that I would personally need to make this a perfect ROM. I have had little to almost no problems. If only I had my remote back though.. Anyone who has a fix I would be greatly apprciated!
Sent from my LG-VS985 using XDA Free mobile app