So the other day I took the plunge and decided to flash cm14 on my H811. Everything went perfectly well. Camera worked, flashlight worked, calling worked. Then I decided to flash Gapps as is customary and when I booted up again I had perfect access to the play store and the Gapps that I wanted, but now the camera doesn't work (just shows a black screen and then crashes), the microphone doesn't work (tried in several different applications), the calling doesn't work and neither does the speaker. I returned to stock marshmallow kdz using lgup and the same problems happened on the stock software.
Any suggestions? Perhaps I wiped some important files the phone needs when I did a wipe in TWRP?
BreakingRAD said:
So the other day I took the plunge and decided to flash cm14 on my H811. Everything went perfectly well. Camera worked, flashlight worked, calling worked. Then I decided to flash Gapps as is customary and when I booted up again I had perfect access to the play store and the Gapps that I wanted, but now the camera doesn't work (just shows a black screen and then crashes), the microphone doesn't work (tried in several different applications), the calling doesn't work and neither does the speaker. I returned to stock marshmallow kdz using lgup and the same problems happened on the stock software.
Any suggestions? Perhaps I wiped some important files the phone needs when I did a wipe in TWRP?
Click to expand...
Click to collapse
what version were you running when you installed CM14 and wich version did you use for KDZ.?
raptorddd said:
what version were you running when you installed CM14 and wich version did you use for KDZ.?
Click to expand...
Click to collapse
I was running 20i when I flashed cm and for KDZ I used was also 20i
BreakingRAD said:
I was running 20i when I flashed cm and for KDZ I used was also 20i
Click to expand...
Click to collapse
do this cleaning procedure. and even after clean. do a KDZ make sure refurbished optin is ticked.
https://forum.xda-developers.com/tmobile-g4/development/turbo-cleaning-proceure-h811-t3417606
I went ahead and updated from 20i to 20o using the organic built in method from the phone. It worked wonders and I'm glad to say my G4 is now running CM 14 flawlessly!
Related
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( https://www.youtube.com/watch?v=epcXXkMPRWk ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
It's possibly a corrupt backup file. I would use TWRP to flash the stock ROM & see what happens.
i assumed re-rooting would clean everything since it uses the send-command program (essentially dd's the whole disk) but i guess not.
we also tried installing the rooted stock rom using twrp but still no joy.
Re-rooting doesn't do anything to the rom or drivers unless you're doing the easy root using a system img file. Then you're pretty much replacing your rom with one that has superuser already on it. That being said, did you upgrade to the 10n firmware/bootstack? The easy root is for 10h firmware/bootstack so that could be the source of your issues.
schneidz said:
hi, my friend called me on a different fone to walk them thru the process of rooting/twrp'ing an h811 using this as a guide ( ).
and it booted up fine and the touchscreen worked. so i suggested they also try cyanogenmod (11.12.2015 nightly). they booted into twrp and did a backup then factory wipe and installed the cm-12.1...zip.
they booted into cyanogenmod and the touchscreen worked. but the t-mobile lte internet wasnt working so they wanted to go back.
good thing they created a backup first...
so they did a factory wipe then restored their image. when they rebooted the got a message process system not responding and the screen doesnt acknowledge any touch.
we tried going into twrp and doing wipe dalvik/cache ... we tried re-rooting using the steps outlined in the youtube video ... but the same problem persists.
after playing around with twrp and wiping random stuff the fone eventually allowed them to unlock the screen but there was no t-mobile service and after about a minute the screen stopped responding while they were scrolling thru the app-drawer.
i think as of now the only os where the touch-screen works is cyanogenmod; is it possible that cyanogenmod/twrp broke the touchscreen or lte modules in android ?
i thought they were two different os's that used different software/firmware ?
suggestions ?
thanks,
Click to expand...
Click to collapse
I relatively had the same problem where I flashed CM and did not like it because it was buggy and so I restored an nandroid and the once working nandroid was plagued with errors of the touchscreen not working, the phone would freeze, system crashes... It ended up being caused by the fact that I did not flash the 10N bootstack update before hand. After I flashed the new firmware and then flashed CM; all of CM's bugs disappeared. I haven't gone back to stock LG software since CM works flawlessly and is now my dailydriver so I cant say for sure if it will fix the stock rom but It probably will since it cleared up all my bugs like the camera not working, videos now playing...
btw to get data working in CM go to settings/mobile networks/Access point Names/ then scroll down and click "T-Mobile US LTE IPv6" and that should fix the internet issues you have since it fixed it for me.
they didnt do anything with the 10n bootstack (i dont know what that is).
maybe cyanogenmod automatically does the 10n thing (how to manually go back to 10h) ?
i assumed re-loading the 5 gb .img file would bring us back to square-1 but i guess not.
also, how to know what bootstack they are running. i told them to check about fone but they told me nothing in there mentions 10n or 10h.
About phone > Software Info > software version will will say h81110n if on 10n.
Same here on Stock...
I have this running stock H81110n software, which I flashed using a KDZ. However, it only freezes up occasionally, and turning the screen on and off once or twice always gets rid of the problem. It's not bad enough for me yet to warrant any factory resets or tweaking so far, but the problem is there...
Hi
I have installed many of the Android 7.0 ROMS for Shamu and all of them have this annoying problem:
When I dial out I cannot hear the ring or the other person.
When I receive a call I don't often hear the other person but they may hear me.
Yes I've installed the N6 boot loader and radio and do not load any other mods, custom kernels.
I just can't figure this out. Any ideas? Is there a Android 7.0 firmware that I need to install to prepare my Shamu for Android 7?
Thanks
Aussie
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Flashing Stock 7.0
aroy97 said:
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Click to expand...
Click to collapse
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
aussie1234 said:
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
Click to expand...
Click to collapse
Flashing stock does not relock the bootloader.
Didn't work
Ok I flashed stock 7.0 using Wugfresh's tool.
But still when I use the phone I can't hear who is on the other end.
Really odd!
Anyone have any suggestions?
Thanks
Aussie
I'm having the same issue on a stock Nougat phone as well. The problem appeared a few days ago out of the blue. The only band aid fix I've found is the sound about app and force assigned the mic and earpiece functions.
Sadly, this doesn't address the main issue in the first place.
none
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
---------- Post added at 07:53 AM ---------- Previous post was at 07:50 AM ----------
USMC retired said:
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
Click to expand...
Click to collapse
If you need anything else you can PM me
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
stevew84 said:
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
Click to expand...
Click to collapse
have you tried reflashing your radio? Maybe try flashing a MM radio as well
Just wanted to chime in, I think this is actually more of a VoLTE/HD issue. It happens to my N6 that's still on MM. Sometimes the dialtone/ring is there, other times it's not. Would love to know of there's a fix!
Found a fix..
Hello all.
I found a fix to Shamu+Nougat ROM problem when I am called I do not hear the other person and vice versa.
To install Factory Nougat from Google: https://developers.google.com/android/nexus/images
FIRST backup your phone (contacts, files, pics, movies etc) as this will totally erase EVERYTHING!
When you are on the Factory Images for Nexus Devices page click "backed up to your Google Account" then go click 'back' on your browser and click on 'Acknowledge' to see the list of Factory Nougat ROMS for Shamu come up on the right.
Download the Android 7.0 Factory ROM for Shamu/Nexus 6.
Do not flash this stock ROM using Wugfresh's tool. Instead follow precisely the 'Flashing Instructions' on the page https://developers.google.com/android/nexus/images. Allow the phone to reboot and fully set up. Restart the phone again.
Then use Wugfresh to Root the phone and also to install custom recovery (I already have unlocked bootloader).
Now, nothing against Wugfresh Tool (I do not know why the flashing method above works better) as Wugfresh has saved my phone many times.. Its just that Googles recommended flashing instructions worked best.
Now I use the phone and not only do I hear the caller and they hear me I have much better reception (Australia). Yes I did previously flash latest radio but the above method seemed to improve my Shamu 100%.
What I have not done yet is flash a custom ROM in case the problem re-appears. But my phone is rooted and unlocked so I can install other mods that work with Nougat.
Hope this works for you.
Cheers
Aussie
Another Fix Part 2
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
aussie1234 said:
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
Click to expand...
Click to collapse
Has there been a listed fix for people who haven't rooted their nexus?
First off, I want to say that I take full responsibility for this fiasco, it's my own fault because I didn't read the instructions well enough.
I bought a T-mobile G4-H811 in May, successfully rooted it and installed TWRP and all was well.
Last night I decided to install a custom Rom, and I screwed up BAD. I went with the Genisys rom and theme pair, but I didn't wipe the system before installing, and then I only installed the Theme without the Rom (i.e. I installed the Genisys 4.2 theme onto the stock Rom). Surprisingly, the system didn't brick. Instead when I booted back up, I got the error "Unfortunately, camera has stopped", and most phone functions stopped working: camera, audio and video files, youtube, even the dialer. It's got text messaging, web browsing, and that's about it.
I've tried wiping the system and installing the Genisys rom, no change. Also no change with the stock stock rom, and Resurrection Remix rom, exact same problem on all of them. Cyanogen gives install errors, and after I fixed those it just hangs on the boot screen.
I'm perfectly willing to accept that I've irreparably broken my device, but I'm hoping someone here has an idea of what I broke and how to fix it.
Thank you for your time reading this.
MellowshipSlinky said:
First off, I want to say that I take full responsibility for this fiasco, it's my own fault because I didn't read the instructions well enough.
I bought a T-mobile G4-H811 in May, successfully rooted it and installed TWRP and all was well.
Last night I decided to install a custom Rom, and I screwed up BAD. I went with the Genisys rom and theme pair, but I didn't wipe the system before installing, and then I only installed the Theme without the Rom (i.e. I installed the Genisys 4.2 theme onto the stock Rom). Surprisingly, the system didn't brick. Instead when I booted back up, I got the error "Unfortunately, camera has stopped", and most phone functions stopped working: camera, audio and video files, youtube, even the dialer. It's got text messaging, web browsing, and that's about it.
I've tried wiping the system and installing the Genisys rom, no change. Also no change with the stock stock rom, and Resurrection Remix rom, exact same problem on all of them. Cyanogen gives install errors, and after I fixed those it just hangs on the boot screen.
I'm perfectly willing to accept that I've irreparably broken my device, but I'm hoping someone here has an idea of what I broke and how to fix it.
Thank you for your time reading this.
Click to expand...
Click to collapse
use LGUP and search for KDZ file flash it.. have in mind once you are in 20o version you cant downgrade to lower version or wour phone hard bricks.
raptorddd said:
use LGUP and search for KDZ file flash it.. have in mind once you are in 20o version you cant downgrade to lower version or wour phone hard bricks.
Click to expand...
Click to collapse
Thank you!
While I didnt do the same that you did, I had the same symptoms. They even carried over into 20i stock rom. I tried flashing the 20i KDZ and it didnt fix anything. I flashed 20p and everything was magically fixed.
I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
citrusfizz said:
I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
Click to expand...
Click to collapse
There will be no locking of the bootloader unless you issue the command. No exploits needed. Just flash away...
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilĂ it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.