Database Info

problems with [CM5.0.7] fix it, do not move thread

MODS DO NOT MOVE THIS THREAD OR I WILL REMAKE IT HERE. I'M SICK ON NOT GETTING ANY ANSWERS. AND THE ANSWERS I GET DO NOT WORK!!!!
HTC Dream (G1)
CM5.0.7-DS
Radio: 2.22.23.02
build:EPE54B
8GB SDcard [class4] (1Gb ext2/512Mb swap/rest FAT32)
70% of the time I have to reboot my phone before i can make a call, the phone says its calling and vibrates when someone answer but i can not hear them and they can not hear me, nor do i hear the phone ringing
something is killing my battery. a battery that should last all day will be dead in less then an hour and the back of the phone is hotter then ****. again rebooting fixes this
with 3 minute reboot times, REBOOTING MY PHONE 4-10 TIMES A DAY TO USE IT IS F*CKING UNACCEPTABLE. LIKE THE OTHER DAY WHEN I HAD PEOPLE BREAKING INTO MY HOUSE AND I'M TRYING TO CALL THE COPS WHILE GUNS ARE BEING POINTED AT EACHOTHER
i've posted in the Q&A, general help, and PM'ed CM and other with no help or answers other then format your sd card, just put the newest CM on there. why the hell should i upgrade to a new version when the problems are not addressed or fixed.

update to cm5.0.8 or try other roms

gs63 said:
update to cm5.0.8 or try other roms
Click to expand...
Click to collapse
see the last line.

Try checking to see if the battery is the problem. Sometimes the G1 battery can get swollen or warped and could cause that problem. I was having the same issue last week and when I popped the back open, the battery was sticking out, looking like Larry Holmes, flabby and sick.
If that's not the issue, make sure you have Danger SPL installed correctly and an updated radio. You can check what versions you have installed by checking your Fastboot.
If none of that helps, do a full wipe and reflash the ROM I guess.
Hope this helps.
Franco
Sent from my HTC Dream using XDA App

have you tried fast boot code:fastboot erase system -w then re flash ROM, if that does not work you should probably try cm 5.0.8 because they where a lot of fixes in that version

theres gotta be a reason your affected and no one else is..
all i can do to help is go on the info givin which is..
(1Gb ext2/512Mb swap/rest FAT32)
Click to expand...
Click to collapse
is an improper layout, it should be
(fat/ext/swap)
Click to expand...
Click to collapse
secondly, your swap is WAY too high, turn it down to 24-32mb (i use 24mb) and set your swappiness to 10, if your using swap make sure compcache is disabled.
for safe measure compeletly reformat your sdcard, however if your using swap and it is a corrupt portion of the sdcard (since class 4 cards dont have wear leveling to my knowledge).
if your coming from another rom make sure you dont have dalvik-cache still on your ext partition
before installing the rom, use fastboot or the format options in clockworks recovery to format system (may as well format data too if your installing fresh) and flash cyanogenmod then gapps..
donno what else to tell ya, without swap or compcache cm is much for our memory starved g1's. if your a light user than compcache is fine. if your a power user you should use swap. (this way if your listening to pandora for example, and you get a txt message it wont close pandora)
otherwise i dont know what to tell you, im runing cm5.08 with a 24mb swap, 10 swappiness on a properly fat/ext/swap sdcard. i have some custom tweaks and a custom kernel and the bidi font fix and everything is smooth.

ephayzee said:
Try checking to see if the battery is the problem. Sometimes the G1 battery can get swollen or warped and could cause that problem. I was having the same issue last week and when I popped the back open, the battery was sticking out, looking like Larry Holmes, flabby and sick.
If that's not the issue, make sure you have Danger SPL installed correctly and an updated radio. You can check what versions you have installed by checking your Fastboot.
If none of that helps, do a full wipe and reflash the ROM I guess.
Hope this helps.
Franco
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
battery is not swollen or warped
i installed the danger SPL per the instructions
soulife said:
theres gotta be a reason your affected and no one else is..
all i can do to help is go on the info givin which is..
is an improper layout, it should be
secondly, your swap is WAY too high, turn it down to 24-32mb (i use 24mb) and set your swappiness to 10, if your using swap make sure compcache is disabled.
for safe measure compeletly reformat your sdcard, however if your using swap and it is a corrupt portion of the sdcard (since class 4 cards dont have wear leveling to my knowledge).
if your coming from another rom make sure you dont have dalvik-cache still on your ext partition
before installing the rom, use fastboot or the format options in clockworks recovery to format system (may as well format data too if your installing fresh) and flash cyanogenmod then gapps..
donno what else to tell ya, without swap or compcache cm is much for our memory starved g1's. if your a light user than compcache is fine. if your a power user you should use swap. (this way if your listening to pandora for example, and you get a txt message it wont close pandora)
otherwise i dont know what to tell you, im runing cm5.08 with a 24mb swap, 10 swappiness on a properly fat/ext/swap sdcard. i have some custom tweaks and a custom kernel and the bidi font fix and everything is smooth.
Click to expand...
Click to collapse
i have only used CM mods
not sure on the exact order of fat/ext/swap that was just how i typed it
i had compcache on and it created problems so i turned it off
also have the home launcher locked in memory

Trial&error said:
why the hell should i upgrade to a new version when the problems are not addressed or fixed.
Click to expand...
Click to collapse
I would PM CM and tell him you will pay £300 for a version just for you.
You're doing something wrong and you want one of the guys here to do it all for you
Well I am sorry with a attitude like yours I don't htink you will get very far.
First off try another rom to see if it's your phone then move forward.

Trial&error said:
MODS DO NOT MOVE THIS THREAD OR I WILL REMAKE IT HERE. I'M SICK ON NOT GETTING ANY ANSWERS. AND THE ANSWERS I GET DO NOT WORK!!!!
Click to expand...
Click to collapse
First of all, caps and exclamation points do nothing to help you in this case. Calm down, take a few deep breaths, and realize that you are complaining about bugs in an outdated version of a ROM. Also, no one is forcing you to flash any ROM at all, so if it's that much of an issue, go back to stock. I wouldn't recommend recreating threads if this thread gets closed or moved, because that will only serve to piss off the mods who have the power to pretty much do whatever they want. Get a grip, upgrade to the latest version of cyan, and if you still have issues, look in the issue tracker, search the forums, and you will find what you are looking for. Good day.

I had strange problems in the past with my radio (not reachable after a while): what solved mine:
I've reflashed the original RC7 (android 1.0), rooted, flashed radio and spl and then recovery. Did then fastboot:
fastboot erase system -w
fastboot erase boot
reboot & flash any rom you like.
Succes!
btw: I think you should move to CM6 nightly too after installing android 1.0 (much better and (3rd party) things are up to date), shouldn't give any problems at all (but do a fastboot erase system -w when upgrading from 5.x).

robuser007 said:
I had strange problems in the past with my radio (not reachable after a while): what solved mine:
I've reflashed the original RC7 (android 1.0), rooted, flashed radio and spl and then recovery. Did then fastboot:
fastboot erase system -w
fastboot erase boot
reboot & flash any rom you like.
Succes!
btw: I think you should move to CM6 nightly too after installing android 1.0 (much better and (3rd party) things are up to date), shouldn't give any problems at all (but do a fastboot erase system -w when upgrading from 5.x).
Click to expand...
Click to collapse
last i heard apps to sd was not working and all my apps on my sd card

**** you.
This is the development section, not the *****ing section. If you don't like CM, ask for help the right (and polite) way, without your negative attitude and without spamming us. If you're still not satisfied, flash back to stock Android, or buy an iPhone, and stay the hell away from our forums. If you threaten the mods, "If you move this thread I'll just remake it," I think they should delete this thread and ban you. The CM team has put a tremendous amount of work into an excellent and highly stable ROM that thousands use without issue. If you screw it up, many people will help you as much as they can, but you should show a little respect for all the work so many people have done for you, for free.
Asshole.

carnegie0107 said:
This is the development section, not the *****ing section. If you don't like CM, ask for help the right (and polite) way, without your negative attitude and without spamming us. If you're still not satisfied, flash back to stock Android, or buy an iPhone, and stay the hell away from our forums. If you threaten the mods, "If you move this thread I'll just remake it," I think they should delete this thread and ban you. The CM team has put a tremendous amount of work into an excellent and highly stable ROM that thousands use without issue. If you screw it up, many people will help you as much as they can, but you should show a little respect for all the work so many people have done for you, for free.
Asshole.
Click to expand...
Click to collapse
let switch position, so now you have 2 illegal mexican in your house trying to rob you and threating to kill you, you have them trapped on the 3rd floor of your house using a shotgun and they have hand guns..... now your trying to call the cops but have to wait 4 minutes to reboot your phone, and another 4 minutes for the cops to get there. the whole time they are trashing your house and trying to get out and trying to point a gun at you.... do you think you might just be a little ****ing pissed
i had already brought to problem up nicely before this and was ignored

If you need your phone so bad, don't mess with it especially if you're not smart enough to do it an figure things out without making a big fuss over things. You should have known what you were dealing with and the possible consequences of rooting your phone as it is with any device that you have administrative permissions on.

You are a very nice member of XDA.

Trial&error said:
let switch position, so now you have 2 illegal mexican in your house trying to rob you and threating to kill you, you have them trapped on the 3rd floor of your house using a shotgun and they have hand guns..... now your trying to call the cops but have to wait 4 minutes to reboot your phone, and another 4 minutes for the cops to get there. the whole time they are trashing your house and trying to get out and trying to point a gun at you.... do you think you might just be a little ****ing pissed
i had already brought to problem up nicely before this and was ignored
Click to expand...
Click to collapse
If you have people in your house, Mexican or otherwise (racist much?), why do you have time to whine on our forum? Seriously, if your phone is screwed up, it's because you screwed it up, so you can only be pissed at yourself. If you're not smart enough to figure it out, even with help, then give up on modding your phone and stick to stock. CyanogenMod comes with absolutely no warranty or support, and this is made extremely clear before you flash it. So... if you're not happy with the answers you're getting, then tough ****. You have no right to be mad if it doesn't work, whether it causes you to lose your job, become impotent, or be shot by Mexicans. That's what you accept when you use this software. Now deal with it.
Can we delete this thread already?

Six6Sicks said:
I suggest you take a gun and stick it in your mouth, pull the trigger, and see what happens.
You know, Trial&error
Click to expand...
Click to collapse
I'm more of a jag bag, it's part of my name

Is this dude serious? Can't believe he asked for help and threatened the mods. What an idiot. seriously go back to your stock g1 rom

Six6Sicks said:
I suggest you take a gun and stick it in your mouth, pull the trigger, and see what happens.
You know, Trial&error
Click to expand...
Click to collapse
OR
wonder if FireRate could do a Apps to brain script

deuse said:
OR
wonder if FireRate could do a Apps to brain script
Click to expand...
Click to collapse
He already did Apps2Brain! Jesus! Doesn't anyone search around here!

Sudden issues with my phone

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

How to block 4.4.3 OTA on rooted N5?

I followed the method to apply this update to my device when it first came out. I ran it for a few days and HATED it. So I restored back to 4.4.2 from my nandroid and all was well, except for the nag that wouldn't go away. I dealt with it for as long as I could before I had to get rid of it. I followed instructions on deleting the update file and renaming something else and then installed Autorun Manager from Play Store and made sure that com.google.android.gsf.update.SystemUpdateService$Receiver was un-checked (which strangely it already was). I rebooted my phone, and the nag was gone so I thought I was in the clear.
Well this AM I take my phone off the pad, and the battery is at 60% which is quite odd for a phone that's been charging for 9 hours, and I see that my data limit setting has been tripped! This thing used like 2 gigs of data in the background under Google Services OVERNIGHT!!! This is ridiculous! This is Android, for crying out loud... I shouldn't be forced to use an update that I didn't like! Or have to install a custom ROM for that matter, which I used to do on my phones (I loved cyanogenmod) but with GravityBox I've been able to do everything I needed to do with the stock ROM. Any suggestions would be greatly appreciated, however suggesting that I disable background data for Google Services will be unacceptable considering it will break a bunch of other stuff. There's got to be a way around this. Thanks in advance!!!

IrocD said:
I followed the method to apply this update to my device when it first came out. I ran it for a few days and HATED it. So I restored back to 4.4.2 from my nandroid and all was well, except for the nag that wouldn't go away. I dealt with it for as long as I could before I had to get rid of it. I followed instructions on deleting the update file and renaming something else and then installed Autorun Manager from Play Store and made sure that com.google.android.gsf.update.SystemUpdateService$Receiver was un-checked (which strangely it already was). I rebooted my phone, and the nag was gone so I thought I was in the clear.
Well this AM I take my phone off the pad, and the battery is at 60% which is quite odd for a phone that's been charging for 9 hours, and I see that my data limit setting has been tripped! This thing used like 2 gigs of data in the background under Google Services OVERNIGHT!!! This is ridiculous! This is Android, for crying out loud... I shouldn't be forced to use an update that I didn't like! Or have to install a custom ROM for that matter, which I used to do on my phones (I loved cyanogenmod) but with GravityBox I've been able to do everything I needed to do with the stock ROM. Any suggestions would be greatly appreciated, however suggesting that I disable background data for Google Services will be unacceptable considering it will break a bunch of other stuff. There's got to be a way around this. Thanks in advance!!!
Click to expand...
Click to collapse
Out of curiosity what did you hate about 4.4.3? From a UI/UX standpoint, not much changed.

jamel_tza said:
Out of curiosity what did you hate about 4.4.3? From a UI/UX standpoint, not much changed.
Click to expand...
Click to collapse
IDK if it was app incompatibilities, but I had TERRIBLE battery life and constant reboots. My device rebooted at least twice an hour. It was basically unusable. I'm no stranger to these devices and messing around with them, so I'm pretty sure it's not something I did. Normally I like to have the latest and greatest, and visually I did like the little changes. But I couldn't live with it, and I don't feel that Google should be able to nag me to upgrade and then obliterate my data allotment when I take steps to override it. Am I wrong?

IrocD said:
IDK if it was app incompatibilities, but I had TERRIBLE battery life and constant reboots. My device rebooted at least twice an hour. It was basically unusable. I'm no stranger to these devices and messing around with them, so I'm pretty sure it's not something I did. Normally I like to have the latest and greatest, and visually I did like the little changes. But I couldn't live with it, and I don't feel that Google should be able to nag me to upgrade and then obliterate my data allotment when I take steps to override it. Am I wrong?
Click to expand...
Click to collapse
Wow that's pretty unusual... As someone who's rooted I understand how much of a pain in the ass OTAs can be, since you liked some of the changes the update brought I think you should give it another shot, though - this time by heading over to the Android Development section, finding a flashable zip of Stock ROM doing a clean install. Don't forget to make a nandroid backup though!

jamel_tza said:
Wow that's pretty unusual... As someone who's rooted I understand how much of a pain in the ass OTAs can be, since you liked some of the changes the update brought I think you should give it another shot, though - this time by heading over to the Android Development section, finding a flashable zip of Stock ROM doing a clean install. Don't forget to make a nandroid backup though!
Click to expand...
Click to collapse
Maybe a good idea... when I did my upgrade, I don't think anyone had made a flashable zip of 4.4.3 yet. I guess I could give it a shot!

IrocD said:
Maybe a good idea... when I did my upgrade, I don't think anyone had made a flashable zip of 4.4.3 yet. I guess I could give it a shot!
Click to expand...
Click to collapse
Give it a shot, there are tons of zips now, just a matter of choice. Plus if anything goes wrong, you have a backup.
btw - I'm giving you this advice because I was in a similar position when the update rolled out. I didn't want to update right away because of possible bugs. After a week if nags I flashed a zip someone put together and things have been fine since.
Either way, let me know how it goes!

Another way would be to download the 4.4.3 factory images and flash system, radio, boot. The random reboots will surely stop. I've not yet seen any app which is compatible with 4.4.2 and isn't with .3
PS: While changing android versions, I always prefer to clean install.

jamel_tza said:
Give it a shot, there are tons of zips now, just a matter of choice. Plus if anything goes wrong, you have a backup.
btw - I'm giving you this advice because I was in a similar position when the update rolled out. I didn't want to update right away because of possible bugs. After a week if nags I flashed a zip someone put together and things have been fine since.
Either way, let me know how it goes!
Click to expand...
Click to collapse
Welp, I just clean-flashed the de-odexed 4.4.3 and everything is okay, so far. My device was nearly dead <20% by the time I was done flashing, so I'm gonna let it spend some time on the pad and then see if I have any issues. Keep your fingers crossed for me!

IrocD said:
Welp, I just clean-flashed the de-odexed 4.4.3 and everything is okay, so far. My device was nearly dead <20% by the time I was done flashing, so I'm gonna let it spend some time on the pad and then see if I have any issues. Keep your fingers crossed for me!
Click to expand...
Click to collapse
I have 'em crossed tight! I hope everything works out. If you encounter any problems don't hesitate to report back here.
JT

Is my Nexus 5 dying?

In the last three months or so my phone has been struggling. I don't know if it is a memory leak or bad memory flash as every so often the phone will be busy doing something and completely lock up. I'm having to restart my phone once of twice a day. I use Android Auto and need to restart the phone and clear all recent apps in order to get it to work.
I have tried factory resetting the phone, clearing the caches and installing CM13 but still get these slow downs and crashes. Is there anything else I can do or do I admit defeat and get a new phone?

nimdy said:
In the last three months or so my phone has been struggling. I don't know if it is a memory leak or bad memory flash as every so often the phone will be busy doing something and completely lock up. I'm having to restart my phone once of twice a day. I use Android Auto and need to restart the phone and clear all recent apps in order to get it to work.
I have tried factory resetting the phone, clearing the caches and installing CM13 but still get these slow downs and crashes. Is there anything else I can do or do I admit defeat and get a new phone?
Click to expand...
Click to collapse
Have u tried factory flashing? I've also heard of lol downgrading letting run to c if there's any difference than upgrading back to the latest. Another question is do u root your phone and if so do u use or tweak your phone? And my personal unfavored, what kind of apps do u use? Do they take all your memory? Try some of these and also think about these and reply back, I'd like to help you the best I can (I'm no super expert tho, the most I've done is replaced my nexus screen and camera parts)
edit: also be careful of those custom kernels, tweaking around those frequencies can lead to your phone spazzing , hint, hint, over clocking.

Aurey24 said:
Have u tried factory flashing? I've also heard of lol downgrading letting run to c if there's any difference than upgrading back to the latest. Another question is do u root your phone and if so do u use or tweak your phone? And my personal unfavored, what kind of apps do u use? Do they take all your memory? Try some of these and also think about these and reply back, I'd like to help you the best I can (I'm no super expert tho, the most I've done is replaced my nexus screen and camera parts)
edit: also be careful of those custom kernels, tweaking around those frequencies can lead to your phone spazzing , hint, hint, over clocking.
Click to expand...
Click to collapse
I have upgraded and downgraded the software but that doesn't seem to help. Apps are the normal social networking and utility apps. No fast paced games or other battery sucking apps. I haven't messed with custom kernels and OCing on this device.

Hmm that is weird, u even tried clearing the cache too hunh? Let's see, have u ever taken a look inside then? Maybe cleaning it out? I've had to clean my phone before because it wouldn't turn on due to dust and whatnot inside it. That's really strange that you've even factory flashed and that didn't help, usually that'll clear up the problem, the reason I could think of is its reaching that eol point because it's just that time or u didn't take care of it (this obviously isn't the case I assume), or maybe it got damaged somehow, or maybe a good clean. Idk I'm just throwing out ideas. But really tho factory flashing should've solved that problem, flash it 2 times in a row lol

It is possible to unlock and root the H990N! :)

I am now running stock Android 8 with ezV2020 kernel for the DS version. Boot loader unlocked and Rooted.
As far as I can see, it is pretty stable. It was a long and tough process, but having already done the LG F800K it just took some hours to do the LG H990N and not days as the former did to break free.
So... just wanted to tell you guys, and let you know, it is possible. Both Sims are working, screen working, seems smooth and stable and all that.
Well, it was a lot of hoops, but I did think it might be possible - and it was and is.
Used my experience from the F800K on this little guy, and it seemed to have payed off, even if I had forgotten a lot of things or had to gather my thoughts on it.
But what a fight... But there you go.
Although it seems like it might be locked on the 4G, and I wanna have it run 3G as the radiation is much much much smaller compared to 4G. Like it is amazing to see the difference between the 2, one being nearly always in the Green by the testing instrument and the other nearly always in the Red. Just utter terrible. But I a have an app that should work that out, or maybe it just need a code and adjustment. dunno what they done to this. But should be workable. There was this code with putting the mobile number into it that got you into a menu... But I found an application for my new used LG mobile that could do the trick which name alludes me... but wait a minute and I will get it. That will most likely be my first try to fix the issue. 4G Switcher is the name of the app and it should be all clean and free!
Dearly regards
- Darkijah

Update... the good news first.
The H990N is running very smooth with the A8 Rooted with the DS kernel of ezV2020... The bad news... the Rotation and Camera does not work.
Not sure if this was something that happened after I installed Lineage 17.1 A10 and then stored it or if it was a problem before that. I just don't know. It looked like it did fine for me, and yet... apparently some issues. I tried to install a foreign kernel like I had done before, but TWRP would not flash it because the kernel file was foreign to the system. Which is odd as I flashed the mobile with the F800K kernel to get it working first hand, ezV2020 1.0 if I recall correct.
Maybe fastboot or something could installed it, adb whatever - still confused by it all...
Lineage by the way was somewhat horrible, and when I found out the sound from the Phone Jack was utter horrible I quickly turned around back to A8 stock. Although now witnessing these issues. I don't know if those issues where there before or not - or if it was something coming after the restoration from Lineage. A lot of factors can make issues.
But the mobile overall, works with network and it does run very smooth compared to my F800K, at least I seem to feel a difference here. One is slower to react, and the other is just butter smooth.
Not sure if I should toy more around with the stuff... I still have my new mobile incoming at some point when they change the broken screen. Getting a little sick and tired of the Android nonsense everywhere, which is literally is, everywhere. Issues, and looking for work arounds and what not, it is never ending.
Rooting should be as easy as pushing a button - and in my opinion should be default out of the box. No user should need to tinker and toy around with there expensive device to get things in order - the criminal companies purposely working against the users on so many levels. Highjacked the whole thing and filling it up with nonsense in the name of security or what not.

To early to say, but I might have found a fix. That took hours and hours... And still at it. But I have the Camera working and the rotation and it seems to still be running smooth. So... Hopefully no more issues, but I will further test it and try some things. It seems this issue is in all H990N20h stock Roms - I have one left to try out. I just tried a DS stock Rom and after installing the kernel and all, doing all the steps I am now into the system, need more testing if everything works, but... Well the Kernel ezV2020 is DS and now the system is DS, also known as Global if I recall. The TWRP is H990 another dual variant. There are absolutely some options to do, but they only allow 2 images being downloaded from the site and it takes a lot of time trying things out, installing it and making it work in the first place. Hours and hours wasted on this :/
But... just wanted to make an update for you guys Found a solution it seems - although there might come up new issues, usual do with Android, but hopefully it everything works!
You have to use the old version of TWRP to fix the lock issue if you get a screen like that. Very annoying, but the oldest version I have breaks it, and then you can install another higher version thereafter. Wipe out the data, and I have wiped out all else except system, not sure if it is needed overall... But in any case, that is my observations for now. I have used TWRP versions before 3.3.0 to unlock this locking issue.
Another issue is that if you go into the system it seems to delete TWRP, so... There are all these steps to do to make it work, *Sigh*.

H990N20f_00_OPEN_HK_DS_OP_1214 - camera and rotation not working.kdz
H990N20h_00_OPEN_HK_DS_OP_0225 - camera and rotation not working.kdz
H990ds20b_00_OPEN_AU_DS_OP_1108 - Newest DS version and working.kdz
H990N20d_00_OPEN_HK_DS_OP_0920 - Oldest H990N A8 but working.kdz
Here are my data so far.

I don't get it, Android is a madhouse. So after having tried things to get the Camera and the rotation to work in the stock A8, kernels and all... Then now installing the newest that did not work. Now it work all of the sudden. Makes zero sense and typical Android. I thought it might work and just for lunacy of it all I tried to install it to verify it still did not work - and now all of the sudden things that did not work, works even if I did the exact same things. It is an utter madhouse. And just typical Android...
After trying different kernels and what not... Downloading another version that did not work, downloading another and another variant of the DS... Then trying the DS that worked, then trying the oldest of the H990N working, and then trying the Newest of the H990N, and now working...
So once again I seemingly wasted hours and hours on something that now just works... Like this is something that happens all the time working with Android I have found out.

The only thing I can conclude by this, is that the installation of the DS in Partioning DL with boot and recovery unchecked, 4 unchecked in total. Must have done something to it, so it could apparently work for the other main images. At least, that's the best I can do, although I don't see why it would be related to fixing it, but it works now with the main and newest H990N image...
I wonder if my old backups would work with camera and rotation if I installed them... but... I'm not so sure I wanna try... But then again... If so, it would make zero sense. In any case I am now making a backup of the one I know 100% to work with camera and rotation H990N. Then I can always try to restore my old backups and see if the problem is there.

First older backup with the camera and rotation not working, restoring crashed the system now before being restored. *Sigh* Trying the first backup that also had the camera and rotation issue.
Well... At least I got it working, it seems. So, so far so good I guess...

My oldest backup got restored, and the Camera and rotation now works... Seems far out, but it is android so not a big surprize I guess. Faulty by design.
Anyway I will try to restore my second backup again and hope for the best... It must have been the H990DS Rom that fixed something while installing it, although have no idea why, and can make no sense of it.

Got my second backup up restored this time... The Camera and Rotation works... Like... I just don't know what could change here. But it started out working when I installed the H990ds stock so I guess it must have something to do with that, beside that I have no idea.

Seems the sickness went away from one mobile and planted itself on the other... I feel more and more that Satans minions are doing these things... Whatever the case, now my daily working mobile is having Camera problems all of the sudden... This is insane, 2 mobiles which should have nothing to do with each other, one mobile having a camera issue, and solving itself all of the sudden, and now the other mobile is infected... Like, just, just give me a break...

You gotta be kidding me, it now also have the turn issue!... This is utter insanity... Like seriously.... *Sigh* What is going on here.
Thinking seriously that a hammer can fix everything!

I downloaded US996 now that US996 is used so much for the F800 mobiles variants, well my F800K did absolutely not like that, I tried it twice and got nothing. It changes partitions apparently - It never loaded up in the system at all.
Anyway, so knowing that the H990DS stock seemed to have fixed the screen issue and rotation issue on my H990N version, I installed that on the F800K and the system worked, and with camera and rotation, although you need a lower version of TWRP to get through the security nonsense as seems to be standard. Well, the H990DS version worked on the F800K and I wonder if it might be a better choice overall to use for it. But it did look pretty good and no Korean nonsense text. Well... I am now restoring my backup of my former system with the sickness that I made before all this, and see if it has fixed it like it did with my H990N. Need to restore +50 GB because of TWRP programming nonsense and then we will see if the Camera and rotation has sorted itself out.
Interesting if it fixes both variant phones... And maybe then it might be better just to use that version on both phones, not sure...
If it sorts it out at least, I think we have a good indication that the DS version H990ds20b_00_OPEN_AU_DS_OP_1108 is a cure for this sickness, it seems.
The F800K seemed to become more sick and skype did not work and it was terrible slow to respond :/ And then of cause the camera and the rotation did not work either. Not sure what is up with that sadly. Not sure what the overall issue is. Maybe I need to keep to the older versions of TWRP or... Dunno...
But I might try the DS version on both systems, if it fixes the 2 main issues, it might not ever come on it. Maybe... Or maybe it just fixes it overall after having been installed, no idea.

I wonder if twrp-3.2.3-0-h990 might also be used on the F800K - if the US996 is not so compatible with the phone, maybe the TWRP is not so compatible either... And the H990 should be close to the DS and H990N version as far as I know...
Restoration failed.... ohh no.... hmmm - might be that the H990DS is different in regards of partitions I wonder...
I will try again and if it fails again, I will install the right stock image and see if it wanna change some partitions and thereby show if there is anything different which might break the beta full partitioning backup. The foolish nonsense of backing up a lot of empty space. Utter insane, but overall Android is insanity.

I feel that the TWRP programmers are lead by Satan, some of these choices that is found is just outrageous. But if you wipe out the competition you can rule over it all, the same with Magisk if there is no competition then it is easy for them to stir the boat. If programs takes the lead and crush everybody else, then they can begin to play tyrants and promote insanity.
Anyway, most likely will get another fail with the backup, partitioning being different in size or something. As TWRP forces this bull**** on the users, and many other things. But can't complain about it, then the blotting pen comes by here on the forum. Censorship, as always, nothing new these Satanic days of hating Truth.
Anyway, I will fix the F800K image and then restore things, that should do it. Then again, it might be better to jump on that DS image overall... *Sigh*
And see if I can get my data with me... Usually also makes issues, because programmers makes it near impossible for users to easily do what they wanna do.
We can't have to much freedom you see...

58 GB's... insanity and waste of time. Programmers love to put that bull**** on us, Android is faulty by design and the programmers outrageous following blindly along pushing more garbage - oh how I wish the Linux Pine or Librem phones had been closer to running as a daily. I would not be on this Android jail bull****, and insanity land of wasting my time with things which should have taken 1 second to fix without breaking anything and yet ends up taking months. Sick sick sick.
Android seem nothing related to Linux, no freedom, no nothing. Just Tyrant companies and programmers, ads all over and other filth. Well the progress is 42 GB and going, getting close to the breaking point I guess.

XDA is full of ads as well, same as all the website with any android stuff - ugly and disgusting filth. Because no website can be run without any ads, apparently...
Yup the restoration failed... but if the partitioning is different then it is no surprise when TWRP programmers program like drunkards full of demons.

Hopefully will soon have figure this out so I can wipe out windows 10 and get on linux... but using LGUP which is running on windows. Don't think there is a Linux version as far as I know. Okay system installed, although it did not give me any warnings of changing the partitioning... I wonder... If it will now restore my backup and if not... then I am in trouble. As this was my main phone... I should have copied everything from the internal to the Micro SD card before doing this.
Should have taken my precautions as Android never seem to do what is expected of it. Always new wacky loony things incoming from all sides. A backup should work but don't expect it too.... Because, Bull****.

Insanity: doing the same thing over and over again and expecting different results. Albert Einstein
I guess he never tried Android...

The error restoration in TWRP could also be related to the version of TWRP, dunno I might have used the old version. Can't remember, but have to take that into consideration as well... As it did not seem to do anything with any partitioning when I ran the H990N stock image.
In any case the H990N stock image is loaded this time - I will restore it with the old TWRP, and if that fails again try a newer version of TWRP and redo it again again again...
So many factors play in, and downgrading for this and upgrading for that. Because... that's Android.

Well, it restored it although with some errors, but not the overall error. Something about some folders it could not enter, which I have seen before. I don't think it is a problem but... I will just test out the Camera and rotation and then go back and restore it with the newest version of TWRP that I have working and see if I get the same issues. The BIG moment... Have it worked? Rotation works... next... Camera works!
Whatever seems to be the issue the H990ds20b_00_OPEN_AU_DS_OP_1108.kdz takes care of it and one can just return to the former stock version or restore the backup.
And I do wonder if I should just install the H990ds20b version on both mobiles really... Seems to be able to run on both variants of the LG that I have.