Related
I've had this phone since the day it released and generally had no problems with it. But a couple months ago, I started having issues with the home screen loading the icons up every time I went to home. Random reboots for no reason, too. I read that it seemed to be a common issues for the phone, so I thought I'd wait for Gingerbread. But today the phone wasn't begin responsive when I tried to text, so I tried rebooting and now it's stuck on the endless reboot. It seems the only way to stop this is to get it to factory reset itself, but I'm hoping I don't have to do that because the phone did a factory reset by itself a month ago and I don't want to deal with starting over again. Is there another trick to it?
Maybe I'm better off getting it replaced. Are the newer models free of all these glitches or is it all still more or less a crapshoot with the problems I've had, screen bleeding, ect?
Just so it's out there, I rooted my phone with SuperOneClick, but I didn't flash or install any roms.
yea i would sumtimes u just get a bad phone when u flash it!! but i'd try another rom and see what that does!!!
But I never flashed it to begin with. It this happened 6 moths after already having the phone.
But if I can fix it by flashing it, maybe I'll try that. I've been wanting to try that cyanogenmod since it's lookign better than my stock froyo.
Yea I would flash it b4 tryin a new1...n if that doesn't wrk then u no what to do
Sent from my HTC VISION using xda premium
If I flash it, is my phone going to reset itself anyway? Totally new to this.
yup thats y i always flash lol
If you have Clockworkmod Recovery try to just clear the Dalvik Cache. Reboot loops are usually Dalvik Cache issues. The first boot after clearing the cache can take around 5 minutes so be patient.
I went ahead and factory reset it, since I have never flashed it or have any of those apps. If I decide to look into installing Cyanogenmon on my phone, where should I start reading to get all the information to learn how to do it? I've rooted my phone, but that's it. I've stuck to pretty much what was on the phone.
C16MkII said:
I went ahead and factory reset it, since I have never flashed it or have any of those apps. If I decide to look into installing Cyanogenmon on my phone, where should I start reading to get all the information to learn how to do it? I've rooted my phone, but that's it. I've stuck to pretty much what was on the phone.
Click to expand...
Click to collapse
If you rooted it, that means you installed Clockworkmod Recovery. To install CM7 you download the zip package, go into recovery, do a factory reset and wipe the dalvik cache, format the system and flash the zip you got from CM.
I rooted it in Superoneclick though, I don't know if I have Clockworkmod recorvery, unless it's not supposed to show up in the app tray like Superuser does.
Isn't there a way to backup my current state on my phone so I keep all my settings in place? I'll probably get into this tomorrow after work.
Check out tgagunmans nvflash method to get cwm 5.0.2.0 on your phone in dev section.
Sent from my LG-P999 using xda premium
Alright, now it's really ****ing up and pissing me off. I haven't done anything new to it. I was browsing the Market today and now I see that the home button doesn't work at all, I can't snap any pictures, there's no screen lock screen, I can't even change it to airplane mode when holding power, it only gives me the off option. What happened to this thing?
C16MkII said:
Alright, now it's really ****ing up and pissing me off. I haven't done anything new to it. I was browsing the Market today and now I see that the home button doesn't work at all, I can't snap any pictures, there's no screen lock screen, I can't even change it to airplane mode when holding power, it only gives me the off option. What happened to this thing?
Click to expand...
Click to collapse
Have you loaded a lot of apps that autorun when you turn on the phone? Many do and you could be unaware of that. If too many apps are running, or a badly programmed app is running, it can cause issues such as this with your phone.
Also, it sounds like you are still on Froyo with the old baseband. You might want to consider factory resetting it again and running the LG Updater to get GB and the new baseband. Then use the One Click Flasher to install Clockwordmod so you can do backups (basically snapshots of the current state of your device) and then you can play around with alternate roms.
if that doesn't fix it then your device is defective. If you have a warranty you might just want to get a swap going on it.
Yeah, I'm still stuck on Froyo. Is the LG Updater working now? Last I read, it was bricking phones. If it works now, I'm guessing my plan should be:
Factory reset
Use LG Updater
Use One Click Flasher to Install Clockworkmod
Install a rom (Cyanogenmod)
Alot of this terminology is totally new to me, so I'm totally lost reading these tutorials that seem to rely on knowing what these terms mean.
Anyway, would be nice to get rid of all these errors. I can't even install anything from the marketplace anymore, I get a force close.
Alright, tooling around on Cyanogenmod 7 now. I don't like that it doesn't have the LG camera or Swype, so I switched to Weapon G2X. Liking it. Any other recommendations?
Weapon G2x is awesome i keep coming back to it my self.... but for the record i've only owned my phone for about a month and i havn't had any problems at all with i love actually .. i just can't find a kernel that doesn't mess things up back on subject i pretty sure GB took care of most of the problems people were having with the phone i don't know if they did any hardware updates to the newer models
Yeah, it's great. The only issue I have is that Swype doesn't give me a list of alternatives when I double tap a word, so I need to re-Swype the word "if" when it was supposed to be the word "of".
Last question, Can I make multiple backups with Flashworkmod? Now that I've fully set up all my phone, apps and fully configured all my settings, I wanted to back it up to this point so my personalized settings are still accessible. Or is it only one backup?
C16MkII said:
Yeah, it's great. The only issue I have is that Swype doesn't give me a list of alternatives when I double tap a word, so I need to re-Swype the word "if" when it was supposed to be the word "of".
Last question, Can I make multiple backups with Flashworkmod? Now that I've fully set up all my phone, apps and fully configured all my settings, I wanted to back it up to this point so my personalized settings are still accessible. Or is it only one backup?
Click to expand...
Click to collapse
Do you mean Clockworkmod Recovery? The backups are coded by date and time so you can make as many as you want. Consider each one a snapshot of the exact state of the device at the time you made the backup. It will be restored exactly the same.
Yeah, whoops. Clockworkmod Recovery. Thanks for the help!
jboxer said:
Do you mean Clockworkmod Recovery? The backups are coded by date and time so you can make as many as you want. Consider each one a snapshot of the exact state of the device at the time you made the backup. It will be restored exactly the same.
Click to expand...
Click to collapse
Should I be deleting old back ups how much memory does each back up take?
Sent from my LG-P999 using XDA App
WHAT NOT TO DO
1. Do not flash Nexus S 4G stuff on a regular Nexus S. That actually goes for any device. Never flash something that wasn't made for it. [thanks polobunny!]
--------------------------------------------------------------------------
Hello, I am new (well, actually hoping to become part of this family tomorrow).
So, tomorrow I'm hoping to get my Nexus S. It will be my third Android phone; the first one was already rooted when I got hold of it (Galaxy Spica) the second one had only 30 minutes of stock ROM (Galaxy 5 - it took me 30 minutes to get home and power up my computer). This is exactly what I intend to do with my future Nexus S (about which I am extremely excited, I;ve already watched some videos with it running various CMs and it looks promising, especially from someone coming from 600MHz/800MHz phones that could barely support CM7).
I want to get home tomorrow, power up my computer and root it. I am still pondering whether to go with the nightly cm10.1 or settle for the stable cm10 ( I know myself pretty well as to not lie to myself that I will stand not at least trying cm10.1).
Now, on my previous phones there were a bunch of no-nos which if performed, would result in hardbricking the device. The only one coming to mind at the moment is: if we flashed a boot logo larger than 190kb on Spica, it would not go pass it, so no adb, no nothing, only jtag would resolve it.
What are the big no-nos of Nexus S. What should I NOT do, under any circumstances, to my (hopefully) new second-hand phone? I've already viewed the video explaining how to unlock the bootloader, flash CWM and flash SuperUser (will use SuperSU because it's awesome!). Also, how's the compatibility with Titanium Backup? That's one app I couldn't live without :fingers-crossed:
I promise to be a good member
EDIT: I also thought it would be a good idea to make a list in the first post. So future newbies like me have a place where they can find them all
There's no many no nos.
Only one I know that will nearly assuredly make your life a nightmare, flashing a Nexus S 4G bootloader on a Nexus S or vice versa. Yes, some people are that awesome...
Otherwise the Nexus S is nearly unbrickable. Make sure to make a backup of your EFS, just in case, and you're good to go.
I highly suggest using the latest CM10 nightly rather than the stable (released on December 20th 2012) because it integrates some important fixes that the stable doesn't have.
CM10.1 is good for trying, but definitely not my best, as the Nexus S is definitely showing its age there.
Added! Thanks. Will double check when I get home and start flashing it.
Also, what are the hotkeys? For example to go directly into Download Mode or Recovery? On my Galaxy 5 width cm10.1 I did the very intelligent thing of trying out the multiple display thingie and the phone was unable to boot. My luck was that the phone got stuck in a sector where adb was available and could do a factory reset.
Liking the backup EFS bit. Had that on Spica but not on Galaxy 5..
andrei1015 said:
Added! Thanks. Will double check when I get home.
Also, what are the hotkeys? For example to go directly into Download Mode or Recovery? On my Galaxy 5 width cm10.1 I did the very intelligent thing of trying out the multiple display thingie and the phone was unable to boot. My luck was that the phone got stuck in a sector where adb was available and could do a factory reset.
Click to expand...
Click to collapse
VOL up + PWR = fastboot (can access recovery from there)
VOL up + VOL down + PWR while plugged in computer = download mode
That's it.
Edit: Oh and it's not any Nexus S 4G stuff. If you flash a Nexus S 4G radio, it's recoverable. A Nexus S 4G recovery? Also recoverable. A Nexus S 4G rom? Recoverable. Only the bootloader has not to be messed with.
Much obliged good sir
Does upgrading/downgradin require me to do a factory reset? I will use titanium backup on a daily basis, but heh..
EDIT: has it ever happened to anyone to miss a call because the phone is so laggy and you couldn't answer?
andrei1015 said:
Much obliged good sir
Does upgrading/downgradin require me to do a factory reset? I will use titanium backup on a daily basis, but heh..
EDIT: has it ever happened to anyone to miss a call because the phone is so laggy and you couldn't answer?
Click to expand...
Click to collapse
Upgrading from revisions (such as Jellybean 4.1.x to 4.2) usually doesn't require wiping your data.
Changing bases though (AOSP to Cyanogenmod), downgrading (Jellybean 4.2 to 4.1.x or to ICS) or upgrading major revisions (ICS to JB) usually necessitate a wipe or a wipe is very recommended.
Never missed a call. Sometime did get a text notifcation that didn't popup because the phone was under too great of a load though. The Nexus S is still only a 1GHz phone with 512MB of ram (but with much less usable). The ram is really what "kills it" for a lot of people.
My question is completely unrelated to technology.
So I usually reset my phone every two weeks... It's not just a factory reset, but I do a full wipe of /cache, /data, /system, etc. and reinstall the ROM. To be honest, I don't really know why, but it's driving me crazy, since it takes forever to set up everything again!!! So I'm curious, are any of you folks out there like me? Or do I have a mental problem and need to consult a psychiatrist?
Oh and also, I avoid apps with advertisements like plague (unless it can be blocked by AdAway).
It does sound a bit like OCD, but whatever floats your boat. Maybe you should use the opportunity to try different roms. The reason I stick with one rom is because the effort it takes to reinstall everything.
You should take a lot of "lucky patcher" to help you get rid of advertisements in apps if adaway fails to block them.
Sent from my SAMSUNG-SGH-I747
error: username not found said:
My question is completely unrelated to technology.
So I usually reset my phone every two weeks... It's not just a factory reset, but I do a full wipe of /cache, /data, /system, etc. and reinstall the ROM. To be honest, I don't really know why, but it's driving me crazy, since it takes forever to set up everything again!!! So I'm curious, are any of you folks out there like me? Or do I have a mental problem and need to consult a psychiatrist?
Oh and also, I avoid apps with advertisements like plague (unless it can be blocked by AdAway).
Click to expand...
Click to collapse
This is not normal, but on the other hand, in my case it is just changing and modifying soft to another, and so around.
error: username not found said:
My question is completely unrelated to technology.
So I usually reset my phone every two weeks... It's not just a factory reset, but I do a full wipe of /cache, /data, /system, etc. and reinstall the ROM. To be honest, I don't really know why, but it's driving me crazy, since it takes forever to set up everything again!!! So I'm curious, are any of you folks out there like me? Or do I have a mental problem and need to consult a psychiatrist?
Oh and also, I avoid apps with advertisements like plague (unless it can be blocked by AdAway).
Click to expand...
Click to collapse
I used to do that. My last phone (evo 4g) probably had a different rom on it every week. I have calmed down a bit now. Maybe once a month now.
Sent from my SPH-L710 using xda premium
Domoo said:
It does sound a bit like OCD, but whatever floats your boat. Maybe you should use the opportunity to try different roms. The reason I stick with one rom is because the effort it takes to reinstall everything.
You should take a lot of "lucky patcher" to help you get rid of advertisements in apps if adaway fails to block them.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Yeah, OCD was what I was looking for. The description of OCD on Wikipedia is a pretty accurate description of me!
I'll try lucky patcher. I used to use AdBlock Plus, but it runs as a background process, so I switched to AdAway which patches the hosts file.
flaco123 said:
I used to do that. My last phone (evo 4g) probably had a different rom on it every week. I have calmed down a bit now. Maybe once a month now.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Actually, I have about three different ROMs on my SD card all the time, so when I get bored of one, I flash another. I'd be happy to try a new S2 ROM that's looks different from AOSP or TouchWiz... Any suggestions?
Alright I am absolutely PI$$ED OFF. I installed 2.0.0 earlier this morning and I've been at it all day trying to fix all the stuff that "update" broke. Moment I installed it my wifi & camera ceased to function, moments later WhatsApp is crashing. So after trying to fix those issues I gave up and restored a backup back to 1.8.0 right? Well now my wifi and camera work but all of Googles bull**** is crashing (google play services, something else) and WhatsApp is still messed up. I installed a new copy of gapps and the google crashing is still persisting. WhatsApp I can't really do much about because I'm using an old number on it to prevent from giving people my new one and i don't want to lose that privilege. The only way I can even use my phone is by slowly getting to Titanium backup and freezing them all. I've wiped my /system, /cache and dalvik cache about 5 times and still no luck. I can't even begin to see how this could relate to my /data partition as I was sure to not let the 2.0.0 update touch it but if it is then please tell me cause I am so fed up right now that I'm ready to toss this phone into a wall then snap it in half and set it on fire.
(THIS IS ABOUT ViperROM)
What in the the Nar Shadda do I have to do to fix these phone wrecking issues? I just want to use the version I've been using for the past month or so again, honestly if I'd known I would have to deal with this much crap I never would've EVER installed this update.
Now on to a little less venting and to more explaining, I've had this wifi issue that I had on 2.0.0 back when I first switched to KitKat on my old Galaxy S4. The camera issue I have never experienced and none of the fixes fixed it except downgrading to 1.8.0, the camera would never display anything on the default camera app & when i downloaded googles camera it would say "Can't connect to camera". on the google apps topic i figured installing a new gapps would solve it but apparently i am wrong. Whatsapp issue i haven't the slightest clue.
Sounds like some sort of firmware problem to me.
S1L3nTShaDoWz said:
Alright I am absolutely PI$$ED OFF. I installed 2.0.0 earlier this morning and I've been at it all day trying to fix all the stuff that "update" broke. Moment I installed it my wifi & camera ceased to function, moments later WhatsApp is crashing. So after trying to fix those issues I gave up and restored a backup back to 1.8.0 right? Well now my wifi and camera work but all of Googles bull**** is crashing (google play services, something else) and WhatsApp is still messed up. I installed a new copy of gapps and the google crashing is still persisting. WhatsApp I can't really do much about because I'm using an old number on it to prevent from giving people my new one and i don't want to lose that privilege. The only way I can even use my phone is by slowly getting to Titanium backup and freezing them all. I've wiped my /system, /cache and dalvik cache about 5 times and still no luck. I can't even begin to see how this could relate to my /data partition as I was sure to not let the 2.0.0 update touch it but if it is then please tell me cause I am so fed up right now that I'm ready to toss this phone into a wall then snap it in half and set it on fire.
(THIS IS ABOUT ViperROM)
What in the the Nar Shadda do I have to do to fix these phone wrecking issues? I just want to use the version I've been using for the past month or so again, honestly if I'd known I would have to deal with this much crap I never would've EVER installed this update.
Now on to a little less venting and to more explaining, I've had this wifi issue that I had on 2.0.0 back when I first switched to KitKat on my old Galaxy S4. The camera issue I have never experienced and none of the fixes fixed it except downgrading to 1.8.0, the camera would never display anything on the default camera app & when i downloaded googles camera it would say "Can't connect to camera". on the google apps topic i figured installing a new gapps would solve it but apparently i am wrong. Whatsapp issue i haven't the slightest clue.
Sounds like some sort of firmware problem to me.
Click to expand...
Click to collapse
First thing. Before you ever take a update... Have you ever heard of a nandroid...
Second. Did you check your md5?
Third. Actually try wiping your data partition... When switching ROMs or even doing a update to a ROM with a new version such as 4.4.3 from 4.4.2 it's smart to wipe data and everything except internal and external SD card.
Forth. Why did you install a new GAPPS? That WILL cause crashes...
Fifth. We don't have updated firmware for 4.4.3 with a 2.22 base. That will cause some issues. It's a given.
Sixth. Have you tried a clean flash of viper 2.0?
Seventh. Have you tried installing another ROM. If so did you have the issues there.
Sent From My HTC One M8 Running Insert Coin. S-OFF.
I agree with person above me...don't flash viper 2.0 till we have 4.4.4 firmware.
An why not flash stock recovery do a factory reset an then go one about your way with it back to out of box set up.
Tigerstown said:
I agree with person above me...don't flash viper 2.0 till we have 4.4.4 firmware.
An why not flash stock recovery do a factory reset an then go one about your way with it back to out of box set up.
Click to expand...
Click to collapse
I didn't really read up too much on 4.4.3 other than it was a security patch I believe? & I considered that but I had tons of messages which I would lose that were important beyond what I'm willing to explain. In the end I said f*** it and just restored my 12 day old backup. Really the only thing stopping me from doing that is my WhatsApp account, I have it setup to use one of my old phone numbers so I never have to disclose real information when I want to give someone my WA. Losing that would mean giving a lot of people something I really don't want to give out...
Now onto the person above me and his idea of my Nandroid doings, yes I have some but I don't have the storage to keep making them everytime I flash something which is practically every week knowing me. & before someone tells me to quit being a lazy "idiot" I simply don't want to spend the time deleting my backups every month when I run out of storage, much un-needed inconvenience. Yup could put them on PC, too bad I'm also running out of storage there too. Could use cloud, no, not into putting my private information and files onto a highly vulnerable privacy invading idiotic creation. In before someone insults me for calling the cloud idiotic, yes it is. I stand by that and have no intents on replying to anyone that may bring that up.
Onto the /data topic, it shouldn't have even touched my data partition if it was just a mere "update". & just now I went and read up on 4.4.3/4.4.4 and the differences = Bug fix & Security update (4.4.4). Most ROM's I've seen actually tell you you don't have to wipe /data unless coming from another ROM, simply that it's better to do it. If it was really such a necessity it should've been stated or stated more seriously/obviously. If 2.0.0 was like Jellybean to Kitkat or Kitkat to Lollipop then yeah i'd understand. If someone with a higher knowledge would like to enlighten me as to why my /data was ruined from such a minor update then feel free to tell me (no more cocky responses after this please, civil only.). Maybe 4.4.2 to 4.4.3 really is a big deal and I just don't realize it & actually it could be the firmware thing the guy above mentioned could be a good reason for it but something I read tells me otherwise, just can't remember it at the moment.
Lastly just incase pball sees this again, for the lols that is.
1. No of course not, I did hear something about a Bandroid 2014 though. Heard it bans all the sarcastic insulting comments to OP's on the internet.
2. No.
3. Might try that if it's ever serious enough to require it. <3.
4. Because I was quite sure it would reinstall the google services, and if you install the correct version for your ROM/OS version I'm pretty sure it shouldn't cause any problems, could be wrong though. Anyways it was not the cause of my GServices crashing anyways.
5. Thanks for the info, I'll consider that next time.
6. Clean as in without wiping /data, yes. With wiping data, no.
7. Yes & the problem went away but I restored to my 12 day old backup of Viper anyways and it's solved now.
52998. Hello!
Anyways problem solved!
/case /closed
You can easily store text on cloud well factory reset. Just FYI. But glad your all set.
There is no correct version of gapps for the ViperOne ROMS. I usually only save the last two nandroid backups as long as everything seems to be working ok. If you want to save the older ones, well . . . . but you don't have the space on your pc. And sdcards are getting real cheap
S1L3nTShaDoWz said:
Lastly just incase pball sees this again, for the lols that is.
1. No of course not, I did hear something about a Bandroid 2014 though. Heard it bans all the sarcastic insulting comments to OP's on the internet.
2. No.
3. Might try that if it's ever serious enough to require it. <3.
4. Because I was quite sure it would reinstall the google services, and if you install the correct version for your ROM/OS version I'm pretty sure it shouldn't cause any problems, could be wrong though. Anyways it was not the cause of my GServices crashing anyways.
5. Thanks for the info, I'll consider that next time.
6. Clean as in without wiping /data, yes. With wiping data, no.
7. Yes & the problem went away but I restored to my 12 day old backup of Viper anyways and it's solved now.
52998. Hello!
Anyways problem solved!
/case /closed
Click to expand...
Click to collapse
Hello, I am back. Just a suggestion in a civil manner. Could you try backing all of your apps up. Make a backup of what you have now, just incase something happens again.. Then, go in and flash the new viper 2.0 or 2.0.1 either or is fine. Please do a clean install. Meaning wipe your data partition. Not your internal SD card not external. In viper I know it gives the option to do a clean install. Please consider actually trying it and seeing the outcome. What's the worst it could do? As for the GAPPS. HTC uses there own personal GAPPS, so it might clash with let's say banks minimal GAPPS. It's not containing the same files and they may just clash with each other. Causing more crashes and instability than before. Somewhat make sense? Lastly, I wasn't trying to be "snarky" or "sarcastic". I may have came across that way, because the way the original post is stated sounds very problematic to some. I went through and listed all the things that could have gone wrong or been happening. Because a lot of ROM threads do mention clean installs with updates or new ROMs. I've seen lots of threads. "If you're having problems please wipe you data, cache, and dalvik cache partition or clean install the ROM again.
Tl;Dr actually try a clean install and check the md5 for matching numbers. A clean install can solve a lot of issues.
Sent From My HTC One M8 Running Insert Coin. S-OFF.
pball52998 said:
Hello, I am back. Just a suggestion in a civil manner. Could you try backing all of your apps up. Make a backup of what you have now, just incase something happens again.. Then, go in and flash the new viper 2.0 or 2.0.1 either or is fine. Please do a clean install. Meaning wipe your data partition. Not your internal SD card not external. In viper I know it gives the option to do a clean install. Please consider actually trying it and seeing the outcome. What's the worst it could do? As for the GAPPS. HTC uses there own personal GAPPS, so it might clash with let's say banks minimal GAPPS. It's not containing the same files and they may just clash with each other. Causing more crashes and instability than before. Somewhat make sense? Lastly, I wasn't trying to be "snarky" or "sarcastic". I may have came across that way, because the way the original post is stated sounds very problematic to some. I went through and listed all the things that could have gone wrong or been happening. Because a lot of ROM threads do mention clean installs with updates or new ROMs. I've seen lots of threads. "If you're having problems please wipe you data, cache, and dalvik cache partition or clean install the ROM again.
Tl;Dr actually try a clean install and check the md5 for matching numbers. A clean install can solve a lot of issues.
Sent From My HTC One M8 Running Insert Coin. S-OFF.
Click to expand...
Click to collapse
Yes I'll back up the apps tomorrow, I used to do that with titanium and make a flashable zip but It rarely occurs to me to use Titanium anymore. Matter of fact 90% of the time I don't even realize I have it or it even exists. Last time I did it I did the wrong option which probably turned me off from it anyways soo I'll just have to pay attention this time.
I'll install 2.0 another day, too traumatized after my last experience to mess with it again LOL.
On the GAPPS topic yes it makes sense, I was unaware HTC had their own as it doesn't really say anywhere that they do or at least I haven't found anything stating such yet up until your response but yes it makes 100% sense.
& yeah I understand, I was quite frustrated and angry at the time and probably should've waited til I calmed down before originally posting this thread. Anyways my bad for even calling you out on that, I didn't originally plan to respond due to my natural urge to wanna retaliate when I feel I've been insulted, mocked or other words "attacked". Not literally attacked but you get what I'm saying, felt like I needed/wanted to be on the defensive. If that even makes sense, oh well.
Lastly, as to the "If you're having problems please wipe you data, cache, and dalvik cache partition or clean install the ROM again." I may have just skimmed over that and maybe just completely ignored the data part in my head. Having read so many I don't really bother to read anything other than the features and some other stuff anymore. I'd say what other stuff but I'm tired and can't think of it at the moment.
Anyways, thanks for trying to help even though my original post sounded like it was made by an idiotic jack***. How frustration & anger makes you change eh? & apologies for responding to what I thought was a "snarky & offensive" reply with attempt to try the same thing. Night!
My viperone 2.0 works just fine on my verizon m8 boot times are really slow but it works a lot smoother and faster with the update. I will deal with long boot times as its woth it to me, no other problems on mine.
Roefastford said:
My viperone 2.0 works just fine on my verizon m8 boot times are really slow but it works a lot smoother and faster with the update. I will deal with long boot times as its woth it to me, no other problems on mine.
Click to expand...
Click to collapse
May I ask if you wiped your /data when you installed it? (clean installed)
S1L3nTShaDoWz said:
May I ask if you wiped your /data when you installed it? (clean installed)
Click to expand...
Click to collapse
No I dirty flashed from 1.8 to 2.0.0 then I dirty flashed from 2.0.0 to 2.0.1 because the ota kept coming back corrupt download so I just flashed the full rom to get from 2.0.0 to 2.0.1
teddyearp said:
There is no correct version of gapps for the ViperOne ROMS. I usually only save the last two nandroid backups as long as everything seems to be working ok. If you want to save the older ones, well . . . . but you don't have the space on your pc. And sdcards are getting real cheap
Click to expand...
Click to collapse
SD cards cheap? Um buy a class 10 scandisk ultra 64g top of the line not cheap by any means it might cost you 70 bucks like mine did but well worth it. Viper ROM needs no gapps its a sense ROM so I'm confused with that.
Looks great spec wise: microSD, no notch garbage, headphone jack.
I need something to replace my OP5 and need a headphone jack and microSD slot.
How is linageOS and flashing? Fairly simple or is it one of those really complicated phones?
I recently got this phone, and the phone itself is pretty great. The flip camera is amazing, and I impress everyone I go to take a selfie with.
Flashing LOS 17 is pretty normal I'd say. This was my first A/B device so it took a bit of getting use to, but a few tries, and I got it down.
As far as support, I think this phone has been pretty lucky to have as these people working on it, like luca for the LOS build, mauronofrio for his 9.0 TWRP builds, and bigbiff for this current TWRP builds, just to name a few. (Thanks to everyone out there helping as well!)
However, as always, the information on some of the details about this phone are scattered around the internet, and its taken me a few weeks to get a good grasp on what my options are with this phone, and some things im still not clear on. Sometimes, a particular detail is only mentioned once in one specific thread, and I guess there just arent enough users with this phone to spread the information around.
Specifically, this is some information I wish I knew about before I tried flashing this phone:
- On LOS 17 (the Android 10 versions), you will have a horrible camera experience. Not sure if its just me, but I havent found a camera app that works correctly, and has modern features like save to SD card / panorama / slow motion / etc. You would think the flipping camera would be the problem, but that actually works fine! One thing that seems completely botched is autoflash. I know nobody probobly uses autoflash, but it seems to use flash at random, in any camera app. The stock lineage camera app is extremely basic, and the quality isnt as great as stock, but if you can live with ONLY pictures and video, then I guess it works (autoflash still doesnt work). There are a couple of GCam ports. I havent tried them all, but they are patchy. The best one I tried only didn't have slow motion working (and autoflash). To my knowledge, there is no way to get the stock Asus camera app on LOS 17. There is, however, a flashable zip for the Asus camera for LOS 16 (Android 9), but that leads me to the next point.
- LOS 16 is a major pain to flash. I am actually going to try and flash LOS 16 right after this, so wish me luck. Ill update this if it goes well. Something is wrong with flashing these versions of LOS. I don't fully understand, so I dont want to say something wrong here and spread misinformation. The steps dont seem to be the same as flashing LOS 17. There are sometimes issues mounting partitions, and some people mention using the unofficial mauronofrio builds over the offical builds for some problem with encryption? Trying to boot into the Lineage Recovery for the 16.0 builds takes like 10 minutes, I almost thought my phone was just stuck, but leaving it there long enough, it finally opens recovery! Its just a pain. Lineage sometimes doesnt work if it wasnt installed using its own recovery, so i try to install LOS with LOSRecovery, and then switch to mauronofrio TWRP to install gapps, magisk and the asus camera app, but i havent gotten a working flash yet. I have to keep trying different combonations and it just takes forever for recovery to start and to flash things in the right order.
-There was an update released for this phone for Eastern countries for VoLTE/VoWifi, but it never made it to the west, and someone said they spoke to Asus, and said they dont plan to release that here (in America, canada, etc) Im not even sure if euro countries got it, but dont quote me on that. Point is, this phone _can_ use VoLTE/VoWifi, but you have to enable it yourself. This amazing man has a guide for the ROG Phone II, but i followed his steps, and it works perfectly on the Zenfone 6! https://forum.xda-developers.com/rog-phone-2/how-to/guide-enabling-volte-vowifi-v2-t4028073
Shoutout to HomerSP. Thank god this works. Why Asus wouldnt ship this phone without VoLTE amidst the 3G shutdown, i have no idea, but this features seems almost necessary to make and receive good quality calls anymore. So yea, if you get it, follow his guide. You need root for most of the steps. It seems complicated but its very easy if you just sit down and do it.
Uh yea, thats what I can think of right now.
Sorry for the wall of text.
I wish this phone was perfect, but flashing LOS and getting everything working correctly is taking me a while to figure out. I don't understand why I cant get LOS 16 to work, but If i get something working Ill post what I did incase anyone else is searching for an answer like me.
For anyone else looking to get this phone, Im starting to think just sticking with Stock firmware with Magisk is the way to go. Killer chipset, amazing cameras and app, 3.5mm, duel sim AND SD card (seriously wide tray, 3 slots!) The only thing this is missing is an AMOLED (if you prefer) and Band 66+71 (T-Mobiles best bands aside from 5G)
Alright, enough of my ranting. Message back with any questions, ill do my best to respond.
bobs50000 said:
I recently got this phone, and the phone itself is pretty great. The flip camera is amazing, and I impress everyone I go to take a selfie with.
Flashing LOS 17 is pretty normal I'd say. This was my first A/B device so it took a bit of getting use to, but a few tries, and I got it down.
As far as support, I think this phone has been pretty lucky to have as these people working on it, like luca for the LOS build, mauronofrio for his 9.0 TWRP builds, and bigbiff for this current TWRP builds, just to name a few. (Thanks to everyone out there helping as well!)
However, as always, the information on some of the details about this phone are scattered around the internet, and its taken me a few weeks to get a good grasp on what my options are with this phone, and some things im still not clear on. Sometimes, a particular detail is only mentioned once in one specific thread, and I guess there just arent enough users with this phone to spread the information around.
Specifically, this is some information I wish usenew about before I tried flashing this phone:
- On LOS 17 (the Android 10 versions), you will have a horrible camera experience. Not sure if its just me, but I havent found a camera app that works correctly, and has modern features like save to SD card / panorama / slow motion / etc. You would think the flipping camera would be the problem, but that actually works fine! One thing that seems completely botched is autoflash. I know nobody probobly uses autoflash, but it seems to use flash at random, in any camera app. The stock lineage camera app is extremely basic, and the quality isnt as great as stock, but if you can live with ONLY pictures and video, then I guess it works (autoflash still doesnt work). There are a couple of GCam ports. I havent tried them all, but they are patchy. The best one I tried only didn't have slow motion working (and autoflash). To my knowledge, there is no way to get the stock Asus camera app on LOS 17. There is, however, a flashable zip for the Asus camera for LOS 16 (Android 9), but that leads me to the next point.
- LOS 16 is a major pain to flash. I am actually going to try and flash LOS 16 right after this, so wish me luck. Ill update this if it goes well. Something is wrong with flashing these versions of LOS. I don't fully understand, so I dont want to say something wrong here and spread misinformation. The steps dont seem to be the same as flashing LOS 17. There are sometimes issues mounting partitions, and some people mention using the unofficial mauronofrio builds over the offical builds for some problem with encryption? Trying to boot into the Lineage Recovery for the 16.0 builds takes like 10 minutes, I almost thought my phone was just stuck, but leaving it there long enough, it finally opens recovery! Its just a pain. Lineage sometimes doesnt work if it wasnt installed using its own recovery, so i try to install LOS with LOSRecovery, and then switch to mauronofrio TWRP to install gapps, magisk and the asus camera app, but i havent gotten a working flash yet. I have to keep trying different combonations and it just takes forever for recovery to start and to flash things in the right order.
-There was an update released for this phone for Eastern countries for VoLTE/VoWifi, but it never made it to the west, and someone said they spoke to Asus, and said they dont plan to release that here (in America, canada, etc) Im not even sure if euro countries got it, but dont quote me on that. Point is, this phone _can_ use VoLTE/VoWifi, but you have to enable it yourself. This amazing man has a guide for the ROG Phone II, but i followed his steps, and it works perfectly on the Zenfone 6! https://forum.xda-developers.com/rog-phone-2/how-to/guide-enabling-volte-vowifi-v2-t4028073
Shoutout to HomerSP. Thank god this works. Why Asus wouldnt ship this phone with VoLTE amidst the 3G shutdown, i have no idea, but this features seems almost necessary to make and receive good quality calls anymore. So yea, if you get it, follow his guide. You need root for most of the steps. It seems complicated but its very easy if you just sit down and do it.
Uh yea, thats what I can think of right now.
Sorry for the wall of text.
I wish this phone was perfect, but flashing LOS and getting everything working correctly is taking me a while to figure out. I don't understand why I cant get LOS 16 to work, but If i get something working Ill post what I did incase anyone else is searching for an answer like me.
For anyone else looking to get this phone, Im starting to think just sticking with Stock firmware with Magisk is the way to go. Killer chipset, amazing cameras and app, 3.5mm, duel sim AND SD card (seriously wide tray, 3 slots!) The only thing this is missing is an AMOLED (if you prefer) and Band 66+71 (T-Mobiles best bands aside from 5G)
Alright, enough of my ranting. Message back with any questions, ill do my best to respond.
Click to expand...
Click to collapse
Hot damn this was an excellent read. I will say I'm deathly afraid of this new A/B partition nonsense. I swear google did it just to screw with us modders. I don't mind putting some work in but I hate when it feels like I'm flying blind in a volcano lol.
I debated the OP7 Pro, but not having and SD card slot or a 3.5mm jack is just unacceptable at this point honestly.
I do prefer IPS, but I would hate to miss out on 66+71 ...dang that stinks
So it looks like this phone is a strong maybe, might just be the best I guess as I can't find any other better options. Though maybe I should look at the ROG Phone II?
Let me know how LOS16 goes if you don't mind, especially if it fixes the camera.
Alright. I know it's been a while since my other post, but I wanted to leave my latest here for any body else reading.
I could not get LineageOS 16 to work at all. The best I was able to get was LineageOS 16 booting, getting to the first time setup saying "Just a sec...", and then a black screen. Holding the power button or using the volume buttons caused the side controls to show up, like the "Power off", "Reboot", or the volume slider to appear, but the rest of the screen was black. After about a minute or two. It would actually freeze up, and restart. But that was it. I mentioned it in my other post, but the recovery for LineageOS 16 takes 5 minutes to boot, I timed it. Its unusual, something must be wrong.
So my options were LineageOS 17 (Android 10) with a horrible camera, or Stock ZenUI (also Android 10).
So I'm choosing Stock, so that I can have a decent camera experience. I really wish I could have LineageOS on this phone, and is one of the major reasons I bought this phone, but the camera app on LOS 17 breaks it for me. I'm just going to have to put up with Stock shenanigans and limitations.
Because I have been flashing so many different times, the state of my device is quite messy. I've been following these steps I wrote down to get a good install every time:
Boot into the bootloader
Use flashall.cmd to revert Slot A back to Android 9 ZenUI v1906.167
Without entering the system, boot into recovery
I edited the end of flashall.cmd so that it wouldn't automatically reboot to system
Apply the ZenUI v1909.194 update, which will end up in slot B
While still in the recovery, use the "Wipe data/factory reset" option
Boot into the bootloader, then back into recovery, to end up in slot B
Reapply the ZenUI v1909.194 update, which will now end up in Slot A. Both slots now have ZenUI v1909.194
Wipe data/factory reset
Bootloader, recovery, your in slot A
Apply the Android 10 ZenUI update, which ends up on slot B
Wipe data/factory reset
Bootloader, recovery, your in slot B
Reapply the Android 10 ZenUI update, which ends up on slot A. Both slots now have Android 10 ZenUI
Wipe data/factory reset
Go into the bootloader once more to get into slot A
Boot into the latest TWRP for Android 10
Swipe to allow system modifications
Check to make sure there are no mounting errors in the log
Flash the TWRP installer
Flash the latest Magisk
And your all done! Reboot to system.
Swipe to install the TWRP app on your way out
flashall.cmd is from the Sevice Firmware zip I downloaded from somewhere. It was in an unbricking guide, but It helps me by downgrading to Android 9, and setting up the partitions correctly again, in case they got messed up (which they have been throughout my testing)
The ZenUI updates I downloaded directly off of Asus's support page for this phone. You just have to pay attention to the fact that these are incremental updates, and need to have a specific firmware already installed in order to be flashed correctly (They say which once in the description). They also only can be installed with the stock recovery. (or at least, twrp never got very far when trying to flash them). I'd say just stick with the stock recovery for installing updates.
Speaking of TWRP, it has issues with restoring backups. It normally ends up with an error like "TarFork() Error 255", but apparently that can mean a bunch of different problems, so its not very helpful. I found that if you want any chance of the backup being restored correctly, you need:
- To be on the same Android version the backup is for (Android 9 restoring Android 9 / Android 10 restoring Android 10 / etc)
- Make sure TWRP doesn't have any mounting errors. This seems obvious, but most times, I had issues where TWRP couldn't mount a partition for some reason.
- You MUST have the option "Use rm -rf instead of formatting" enabled. I never got a backup to work without it enabled
Even after all that, sometimes the backup STILL wont apply. Once a backup fails to apply, nothing will work until I flash the service firmware and incremental updates again in order to try again. It's very time consuming.
Now, I don't know as much as I probobly should about linux or android, but that last option makes me tells me that instead of actually formatting / recreating the correct partitions, it just deletes all files and puts back the ones from your backup. That works great and all, but if the partitions get messed up somehow, the only way I know to restore them is by flashing the stock ZenUI updates in order (Service Firmware -> ZenUI v1906.167 -> Android 10 ZenUI). To add to the confusion, I'm not actually sure if TWRP backups/restores include both slots, or just the slot you are on. For good measure, I make sure to update both slots evenly, so that they end up with the same firmware version, however, I have only flashed one slot per update, and gotten a backup to work also. For example, instead of flashing each update twice, to get it on both slots, I have only flashed each update once, so that Slot A gets the service firmware, then flashes slot B with Android 9, then flashes slot A again with Android 10, and then restore, and It works. Its all very confusing and seems inconsistent. Maybe I'm missing an important detail, but I can't figure it out.
One last thing about restoring backups. I have a hunch that going through the first-time setup of the phone (specifically, adding a figerprint/pin) does something to the system or data partition. Whenever I was restoring a backup, I had a better chance of it working if I went through first time setup, and skipped adding a fingerprint/pin. I would then get to the home screen, and restart into recovery to restore.
Sorry if this is confusing to read. I'm kinda just dumping all my information for me or someone else to read later if they are as frustrated as I am now.
I wish it would all just work, or at least give more descriptive errors. Trying to google any leads I find reveal almost nothing. I feel like If I'm not a retired developer, there's no way to understand any of this.
Also, if you know how something works better than I do, or if I'm explaining something wrong here, please let me know! Really, I need all the help I can get on these topics.
Uh yea, so that's all I got. I have my fingers crossed that all the pieces can come together for this phone, but I know its going to take a long time if its going to happen at all. The Zenfone 7/Pro just got announced(released?) and maybe everyone will just abandon the 6 now. That seems to be the trend now anyways.