I have acquired a used G6 H872 (T-Mobile). I have been unable to get it network unlocked so the phone is useless to me. I am looking to sell it but first I need to solve the camera issue.
When I first received it, the phone was on stock and the camera worked. I unlocked the bootloader, rooted it, and installed MSM Extended. The camera worked. After deciding to sell it I restored it to stock with LGUP/kdz. Now the camera opens but the screen is black. This is the second time I've encountered this with a T-Mobile G6. Why is this happening? And how do I fix it?
Thanks!
mn1968 said:
I have acquired a used G6 H872 (T-Mobile). I have been unable to get it network unlocked so the phone is useless to me. I am looking to sell it but first I need to solve the camera issue.
When I first received it, the phone was on stock and the camera worked. I unlocked the bootloader, rooted it, and installed MSM Extended. The camera worked. After deciding to sell it I restored it to stock with LGUP/kdz. Now the camera opens but the screen is black. This is the second time I've encountered this with a T-Mobile G6. Why is this happening? And how do I fix it?
Thanks!
Click to expand...
Click to collapse
You need to flash stock Nougat, and camera will work. Arter that you can updrage to Oreo and then to Pie.
SkylineDiT said:
You need to flash stock Nougat, and camera will work. Arter that you can updrage to Oreo and then to Pie.
Click to expand...
Click to collapse
Thanks for the reply. I thought I can't go back to Nougat because of anti-rollback.
Doesn't matter anymore. Found a cheap service that unlocked the phone. Installed MSM Extended and camera works again.
I wonder what breaks the camera in the stock ROM, and why it works in custom ROM.
SkylineDiT said:
You need to flash stock Nougat, and camera will work. Arter that you can updrage to Oreo and then to Pie.
Click to expand...
Click to collapse
mn1968 said:
Thanks for the reply. I thought I can't go back to Nougat because of anti-rollback.
Click to expand...
Click to collapse
Since I now have two H872 G6's that have exhibited the same camera issue, I decided to try rolling back to Nougat. First, I was wrong - I was able to roll back.:good: Second, rolling back completely fixed the camera issue, in addition to the proximity sensor! :good::good: The only remaining issue with that particular phone is that the haptic feedback/vibration doesn't work.
Related
A while back, just before the 2.2 OTA update came out for ATT locked streaks I received a replacement streak from dell. I didn't have it long enough before I applied the update to remember if the compass or sensors were working, but I seem to remember the screen would auto rotate just fine.
After the update the screen would not auto rotate at all. I spent a while looking into fixing it, trying things like srchild.com's calibrate-sensor-on-upside-down-dell-streak-after-froyo-22-android-upgrade
But I have a slightly different version of the menu's than that tutorial shows and nothing I did fixed the auto rotate so I eventually just learned to live with it in landscape mode for a while.
Now I realize that no compass or sensor based apps work. I've installed sensor monitor apps and they show no data. The "Calibration" application that shows bubble levels doesn't move at all. I'm starting to think it is a hardware problem but like I said, I am almost sure that screen rotation worked before the upgrade on this device.
Is there a way to verify for sure before calling dell. Their support was a nightmare to deal with the first time.
TIA
Why go through the trouble? Why not root your Streak and flash a custom ROM. They perform much better.
If you don't like them then you could always use the QDL tool to get back to stock but everyone here knows the OTA updates wreak havoc for almost all Android devices
cdzo72 said:
Why go through the trouble? Why not root your Streak and flash a custom ROM. They perform much better.
If you don't like them then you could always use the QDL tool to get back to stock but everyone here knows the OTA updates wreak havoc for almost all Android devices
Click to expand...
Click to collapse
A new ROM, stock or custom, won't fix the problem if there is a hardware issue. Installing a different ROM might help troubleshoot the problem. I would suggest a stock ROM so that if the problem persists there is no questions concerning the warranty. 353 is the latest AT&T ROM and can be downloaded here.
You don't have to root and then install StreakDroid, you can install SD without rooting first.
The updates I have gotten for the Streak have been excellent. I run Stock 351. My streak was purchased unlocked from Dell. In addition the OTA update I got for my Moto Backflip was a huge improvement and the update on my wife's Inspire that enabled the setting to install non-market apps works fine. I would have to say that not everyone here agrees with your assessment of the OTA updates.
To the opening poster I would suggest a reset or reinstall of 353 and then test with no apps installed.
I should've specified the OTAs from DELL are notorious for causing issues.
And you are correct, not everyone here would agree with them, but if you like to tweak and play, then a stock ROM doesn't offer much flexibility, not to mention performance wise.
When I first got my Streak I bricked it, then I revived it with the QDL tool and then went to StreakDroid. Then I even went back to stock to have a baseline to compare with the StreakDroid beta I'm currently using, and I have to say, stock is just that, stock, it's two worlds, performance and battery on stock just don't compare to any of the custom ROMs.
I know this isn't the place for this discussion but I couldn't help but make my point. If you like the stock ROM, I'm happy for you, but I for one have never been much to settle for less, I'm always looking for the latest thing.
Having not looked into updating android a great deal I'd appreciate any corrections if I'm mistaken on this, but I do believe the over the air update that was installed is the 353 version.
My Streak currently reads:
Baseband version: GAUSB1A135331-US
Build number 15697
marvin02 if you still think downloading and installing the the 353 ROM you linked to would help diagnose the issue I'd be more than happy to, please let me know.
cdzo72 I do plan on installing custom rom's and even getting into Android development in the near future but I do not have time for it yet. I would like to make sure I do not have a hardware problem before installing any custom rom's because it will be easier (less time consuming for me) to make a warranty claim if I need to. Unfortunately right now functional and limited is better than cutting edge and time consuming for me when it comes to my Streak.
data_loss said:
. . .
My Streak currently reads:
Baseband version: GAUSB1A135331-US
Build number 15697
marvin02 if you still think downloading and installing the the 353 ROM you linked to would help diagnose the issue I'd be more than happy to, please let me know.
. . .
Click to expand...
Click to collapse
A fresh install would eliminate (mostly) the possibility that your problem is caused by software, not hardware. If you still have the stock recovery on your phone you can just download the .pkg file, put it on your SD Card, rename it to update.pkg and boot into recovery to install.
I do still have the stock recovery.
I downloaded and installed the 353 ROM. It appears that the sensors are not working (no auto screen rotation). I also tried a factory reset after the update just for giggles, no change.
If I'm not mistaken the Streak_104_4399_21.pkg that can be downloaded from the streakdroid site is the official att&t 1.6 ROM. Would it be worth downloading and downgrading to that to test?
Or at this point do I just endure the call to dell support?
Is there any kind of documentation available for the fastboot menu on the streak? There seems to be options available for sensor stuff in there but I don't want to be just clicking through them without knowing what they do.
One hour on the phone ( which was not much fun ) and a couple days later and I have a replacement. It is a refurb, but in good condition and it works. Thanks all for the help.
Sent from my Dell Streak using XDA App
I have switched to a new device and no longer use this phone but i see many others facing this issue as well so I am keeping this thread open, please do not message me regarding the solution to this issue cause all i did to get out of this mess was getting a new phone.
Hello !
Due to some error while flashing stock rom on Moto G4 Plus XT-1643 my Moto G4 Plus has changed into Moto G4 but the model no shown in the "About Phone" section is correct.
I have lost one Imei no. fingerprint option is no where sim or mobile network doesn't work other than that the phone is fully functional(WiFi,Camers,Audio etc)
There are multiple threads on the same issue but no solution is available I would be highly grateful if anyone could find out any solution to this issue.
P.S : I have tried flashing multiple ROMs available on the forum specific to XT-1643 i.e Indian Version
Also I flashed the OTA file for the Android 7.0 Soak Test due to which I cannot relock the bootloader.
I am currently on Stock Marshmallow 6.0.1 139-63 Rooted&TWRP installed
The phone is basically an iPod without fingerprint sensor
I had the same issue. I relocked the bootloader and sent to service center. They flashed the original firmware. Stock roms roaming here are not exactly stock roms.
this happened to my phone (1640 - brazilian moto g 4 plus), and I tried every single rom out there for moto g 4 plus, and it is only identified as Moto G 4, without fingerprint or any modem activity.
i still cannot recover previous bootloader, because it don't downgrade bootloader version. nothing worked for me so far.
i'll be watching this thread to see if anyone comes with any alternative.
sabithmk said:
I had the same issue. I relocked the bootloader and sent to service center. They flashed the original firmware. Stock roms roaming here are not exactly stock roms.
Click to expand...
Click to collapse
Umm, so according to you too it's a software issue and not a hardware one right ?
The first thing that I do when I boot in TWRP, I do a full backup of all the phone's partitions, and save a copy on my PC, so I can restore the phone in cases like this.
Guys, maybe you need to read this thread:
http://forum.xda-developers.com/showthread.php?t=2617276
if you flashed android 7.0 and then downgraded to android 6.0.1 then expect some bugs because your bootloader gets updated you have to do clean flash but you cannot actually completely downgrade to android 6.0.1 after you updated to 7.0 soak test bootloader still remains updated and your phone will brick when you click update after you receive 7.0 official OTA i warned you this happened to lot of moto x users do some research before you do anything if the phone is your primary device
Soureen said:
Umm, so according to you too it's a software issue and not a hardware one right ?
Click to expand...
Click to collapse
I think so. May be if we flash a wrong modem, the right one never flashes correctly. I don't know how do they managed to flash it correctly.
For me its a software issue... looks like it messed with the bootloader, and since you cannot rollback to an older bootloader, the phone works like an iPod Touch. haha
I hope that when Motorola releases the final 7.0 version for 1640, I'll be able to flash again the right bootloader and that will fix the phone.
SoNic67 said:
The first thing that I do when I boot in TWRP, I do a full backup of all the phone's partitions, and save a copy on my PC, so I can restore the phone in cases like this.
Guys, maybe you need to read this thread:
http://forum.xda-developers.com/showthread.php?t=2617276
Click to expand...
Click to collapse
I did a full flash of an older 6.0.1 ROM, and it still doesn't work. Since the only thing that I couldn't flash is the bootloader, and the phone identify itself as Moto G 4 (and not Moto G 4 Plus) my guess is that the problem is with the bootloader.
I guess i'll have to wait for the official 7.0 for my specific phone (1640) to fully replace this broken bootloader.
Yeah, that's why I didn't upgrade to the N yet, I was sure that the bootloader will be different.
I also have saved the partitions with Partitions Backup & Restore app, after rooting.
Did you try the ElementalX kernel?
http://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
I was also having same issue,got my bootloader locked and went to service center and they replaced the motherboard for free????
Lucky you
Has anyone found a solution to get the plus (fingerprint) back to the phone?
Nope funny thing no one knows anything ??
I am waiting for the Android 7.0 official update so that I can relock my bootloader and send it for service.
That's a bummer but there might be some solution. The phone version number shouldn't be that hard to find if you'd knew witch file that flashes it.
How do you do these backups for they don't look at all as twrp backups so I guess twrp is second best to something. But what?
What is the different with 7.0 coming up? Can't you just relock a backup?
Soureen said:
Nope funny thing no one knows anything ??
I am waiting for the Android 7.0 official update so that I can relock my bootloader and send it for service.
Click to expand...
Click to collapse
I have the same issue, I have seen people with XT1643 having athene_f in build fingerprint but I have only athene. Which one is correct, could this be the issue?
Managed to solve the issue at least to get the signal. This is what I have done
- Restore my first TWRP backup.
- Booted directly into bootloader and NOT system, flashed modem for the build.
- Rebooted and I am getting the signal!!!
m.swastik said:
Managed to solve the issue at least to get the signal. This is what I have done
- Restore my first TWRP backup.
- Booted directly into bootloader and NOT system, flashed modem for the build.
- Rebooted and I am getting the signal!!!
Click to expand...
Click to collapse
Radio is working after TWRP backup + modem flash. Still fingerprint is not working and it is pointing out as athene not as athene_f
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-63/64:user/release-keys
Click to expand...
Click to collapse
l2o88j said:
Radio is working after TWRP backup + modem flash. Still fingerprint is not working and it is pointing out as athene not as athene_f
Click to expand...
Click to collapse
I have spent 1 whole week to get the signal working, at least be glad that you can now use your phone and press thanks if I helped. Regarding athene in build fingerprint you can easily change that in build.prop but it won't help. I think fingerprint service is disabled because ROM thinks that our phone is G4 and not G4 plus. I have tried few things to enable it but not getting it to work, will update if any of my experiment is successful.
m.swastik said:
I have spent 1 whole week to get the signal working, at least be glad that you can now use your phone and press thanks if I helped. Regarding athene in build fingerprint you can easily change that in build.prop but it won't help. I think fingerprint service is disabled because ROM thinks that our phone is G4 and not G4 plus. I have tried few things to enable it but not getting it to work, will update if any of my experiment is successful.
Click to expand...
Click to collapse
I found this trick early and I am using it now. I thought you cracked the last part (fingerprint sensor) which my post was about. I think that the issue is with gpt bin as I tried different bootloader versions along with all possible combinations. Gud to see someone else is working on the same. Will update if found any.
find the correct firmware for the device and flash it else it would lead to such errors
A week ago I bought a used s7 edge. The original owner had done a factory reset. My first thing was to flash the latest local stock rom, bootloader, and modem. Then I installed TWRP and then rooted. All great. After a few days, I got tempted by the new Nougat betas.
OK, so now I've got a huge mess. I updated to the Minotaur 7.0 beta (nice rom) and got it nicely set up. I'm quite sure that I enabled OEM Updates in Developer Options. I was trying a manual setup of the APN and it wasn't working. So I thought a reboot might solve it. When I rebooted, I got a black screen with a little red message at the top - Custom binary blocked by FRP lock.
So I have spent the afternoon on the Internet only to learn that Google and Samsung created that lock so that stolen phones cannot be easily put into service. If OEM updates are checked, that disables the lock. I don't know what happened but I have a phone with a black screen that won't boot. It will go into download mode so I will try to flash a stock rom.
OK, that worked. I lost 2 days set up but the rom is booting.
Samsung Galaxy S5
Exodus CM12 5.1.1
Boeffla kernel
Apex Launcher
Hi.
Download the official firmware for your S7 and flash it with Odin. That should solve the problem.
ByronXg said:
Hi.
Download the official firmware for your S7 and flash it with Odin. That should solve the problem.
Click to expand...
Click to collapse
Yes it did! I was very worried that the stock rom was MM and so I was going backward. But it worked! And now I am all set up again. Just wish I knew what triggered that so I could avoid it in the future....
Sent from my SM-G935F using XDA-Developers mobile app
Did you tilt the option about OEM unlock in develop settings? Also try to flash without setting any PIN or fingerprint in the official rom
How do I do this process with a Claro brand phone? I do not know what firmware to select, the list has every country but Unites States.
rachel10105 said:
How do I do this process with a Claro brand phone? I do not know what firmware to select, the list has every country but Unites States.
Click to expand...
Click to collapse
You can use the European firmware on it.
I have h870 lg g6 with the Israeli version Is it possible to install other country's version to get 8.0 in english?
yes, just download Open EU .kdz from here https://lg-firmwares.com/lg-h870-firmwares/#firmwaresList and flash via LGUP & Uppercut, very easy.
Jostian said:
yes, just download Open EU .kdz from here https://lg-firmwares.com/lg-h870-firmwares/#firmwaresList and flash via LGUP & Uppercut, very easy.
Click to expand...
Click to collapse
It worked. this version is much more stable my phone started going crazy and now its okay
Great!
Sent from my LG-H870 using Tapatalk
I have lg g6 h870ds Indian International model
Can i also flash h870 firmware. if no then which firmware please help i need oreo
mujaheedhaji said:
I have lg g6 h870ds Indian International model
Can i also flash h870 firmware. if no then which firmware please help i need oreo
Click to expand...
Click to collapse
Maybe, but chances are you'll convert your phone into a small Wi-fi only tablet. That's if it doesn't bootloop.
Not sure about LG, but I know for a fact on some HTC phones, flashing DS radio firmware on SS phones disables all GSM radio functionality.
hi, i have a G6 H870 chilean version, without branding, can i install the UE Firmware? and the other question, is if i won't lose my warranty?
orma1 said:
It worked. this version is much more stable my phone started going crazy and now its okay
Click to expand...
Click to collapse
I just did the same last night. I'll let it "settle in" for a day or 2 to see the results.
So far a little lag (in opening apps) compared to Nougat, but stable. Battery drain seems slightly improved but I'll report back later.
If the lag doesn't go away I'll go back to Nougat
jshames said:
I just did the same last night. I'll let it "settle in" for a day or 2 to see the results.
So far a little lag (in opening apps) compared to Nougat, but stable. Battery drain seems slightly improved but I'll report back later.
If the lag doesn't go away I'll go back to Nougat
Click to expand...
Click to collapse
maybe I see more difference because I came from the Israeli version. Also I did a clean install
orma1 said:
maybe I see more difference because I came from the Israeli version. Also I did a clean install
Click to expand...
Click to collapse
I also came from that version
I didn't do a factory reset. because I figure that once I reinstall everything (and I actually use all the apps) I'll be in the same situation.
The slight delay in apps opening is slightly annoying. I suppose I can get used to that, but I prefer a snappy device even if I don't have immersive mode or context menus on the icons...maybe I'll roll back to Nougat
So after a few days, a few observations:
1. The lag seems to have decreased with a few days of settling in. Still not exactly snappy, but less delay in opening apps.
2. There is a new setting in Oreo under apps-battery usage- a toggle for "background activity" . It is available for some apps but not all. It stops these apps from running processes in the background (not connected to "power saving exclusions"). This seems to have improved battery life a bit.
3. No crashes or freezing.
Tried to flash a kdz for H870DS via LGUP but got stuck up at LG logo
Karvenry said:
Tried to flash a kdz for H870DS via LGUP but got stuck up at LG logo
Click to expand...
Click to collapse
Wich kind of kdz ? DS kdz? or other KDZ ?
mohammadstr said:
Wich kind of kdz ? DS kdz? or other KDZ ?
Click to expand...
Click to collapse
I got the Philippines variant for LG G6 which is an H870DS ESA and I flashed a Singapore H870DS SEA oreo firmware (.kdz) and got stuck on LG Logo after I complete the flashing
1. Opened Uppercut / Runned LGUP directly
2. Choose the H870DS kdz file
3. Choose "update"
4. Start the flashing and wait till it finish
5. Stuck at LG logo
On the firmware website I see there is now an "official" version of oreo for the Israeli device (dated 8-8-18)
Anybody try it?
Hi all,
I’d would really appreciate some comments or suggestions on how to solve following problem.
I bought an Essential phone on ebay this week (Sprint “unlocked”), and it came with Android 9 Pie. I initially put a simcard from an operator here in my country and it worked fine.
Due to work reasons I need the phone to be rooted with Android 7.1.1 Nougat (compatibility issue with a software used for testing celullar networks), so as a first step I flashed one of the Nougat images available in Essential’s website. This wasn’t a problem since I had already done this procedure with other Essential phones.
After successfully flashing Nougat, when I inserted back the simcard the phone did not recognize it. I upgraded back to 9.0, and the simcard was working again. The same happened when I downgraded to Oreo for testing.
Does anyone have any suggestions on how could I proceed to solve this issue? I really need it to run Nougat.
Thank you in advance for your feedback!
Make sure you unlocked the critical partitions, that's needed for the full image to flash and produce a fully functioning device, else there may be incompatibilities in the radio/modem/hardware/bootloader.
lecc18 said:
Hi all,
I’d would really appreciate some comments or suggestions on how to solve following problem.
I bought an Essential phone on ebay this week (Sprint “unlocked”), and it came with Android 9 Pie. I initially put a simcard from an operator here in my country and it worked fine.
Due to work reasons I need the phone to be rooted with Android 7.1.1 Nougat (compatibility issue with a software used for testing celullar networks), so as a first step I flashed one of the Nougat images available in Essential’s website. This wasn’t a problem since I had already done this procedure with other Essential phones.
After successfully flashing Nougat, when I inserted back the simcard the phone did not recognize it. I upgraded back to 9.0, and the simcard was working again. The same happened when I downgraded to Oreo for testing.
Does anyone have any suggestions on how could I proceed to solve this issue? I really need it to run Nougat.
Thank you in advance for your feedback!
Click to expand...
Click to collapse
You need to do a full wipe of the data when going backwards.
There is some setting hanging around that is not compatible.
I have seen this also