Database Info

[Q] Cannot connect to camera for d2lte

I have 2 of the same phones (i747M with twrp 2.7.1 for d2att installed)
On one, everything worked flawlessly (the older one)
On the other, I had to talk to a developer of twrp to get twrp working...
Now I just realized that the camera app isn't working. It works fine when I restore to the touchwiz stock rom.
I tried wiping my entire device before installing the new stable build 6 rom for d2lte. I also tried flashing the weekly roms for that device on both phones
the result is the same: camera works fine on the older phone while on the newer one, it doesn't
Someone suggested that this might be a hardware issue.. Basically, the TWRP guys fixed my other problem by pulling the latest cyanogenmod build and compiling a recovery. -So I'm wondering if something can be done to make my camera work again on my new phone...
(Before all of this, I of course tried rebooting, closing other apps, clearing data, etc...)
Update: I tried flashing the latest cyanogenmod nightly (June 30) and the camera app worked, but I prefer slimrom
Another update: all the bug report shows when I reproduce the error is
Device: Slim-d2lte-4.4.4.build.6-OFFICIAL-5242
Kernel: 3.4.95-cyanogenmod-gd56ed95 [email protected] #1

Can't root new Mi4. Please tell me what I'm doing wrong.

I have tried XiaomiTool, which resulted in a brick.
I had to factory reset from the recovery, then it turned on, which resulted in all GApps disappearing. Got a 550mb OTA which brought them back.
I read that i can root by using Developer rom, but that is only available in the chinese version.
There is no global developer rom. Please show me how to root this phone, i already bricked it once on the first day.
Android 4.4.4
MIUI 6.5.3.0 Stable.

http://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/
Xiaomi.eu's ROMs have Google Apps and root. 5.7.2 is perfect, haven't tested latest yet.

Which one should I Download?
There are so many links, none of which seem right for the Mi4.
And it says in the post that they are without root?
P.Kosunen said:
http://xiaomi.eu/community/forums/miui-weekly-rom-releases.103/
Xiaomi.eu's ROMs have Google Apps and root. 5.7.2 is perfect, haven't tested latest yet.
Click to expand...
Click to collapse

http://htcfanboys.com/download/acid/?action=list&folder=97014
Cancro is for Mi4 and Mi3. Weekly releases are based on chinese developer version and rooted.

P.Kosunen said:
http://htcfanboys.com/download/acid/?action=list&folder=97014
Cancro is for Mi4 and Mi3. Weekly releases are based on chinese developer version and rooted.
Click to expand...
Click to collapse
Thanks a ton. I am used to a nexus 4 so all this seems new to me.
Is there a guide to flash this? I wouldn't mind wiping data this one time.
What method Should i use to Update, by keeping data?
Thanks again.
PS isnt there something like this based on the global version?
What is the difference between this and the one from the MIUI website Chinese developer rom?

Easiest way is from MIUI Updater app, "..." from up right, choose update package... Can try dirty flash first, If there is problems/apps fc do factory reset.

P.Kosunen said:
Easiest way is from MIUI Updater app, "..." from up right, choose update package... Can try dirty flash first, If there is problems/apps fc do factory reset.
Click to expand...
Click to collapse
And what about the difference between Chinese MIUI Developer official and xiaomi.eu roms?
Thanks.

Xiaomi.eu weekly roms are based on those chinese developer versions so dirty flash might work. They disable chinese only apps and features and add languages.

P.Kosunen said:
Xiaomi.eu weekly roms are based on those chinese developer versions so dirty flash might work. They disable chinese only apps and features and add languages.
Click to expand...
Click to collapse
I have installed it and it is working great.
One major problem, Everytime i install an APK, it asks me to grant permission, and only lets me allow it once after waiting 10 seconds.
There is no Allow Unknown Sources Checkbox.
Please help, it is very annoying as i have so many APKs to install on the new phone.
EDIT: Nevermind, I found the setting.
Thanks a lot for your Help.

P.Kosunen said:
Xiaomi.eu weekly roms are based on those chinese developer versions so dirty flash might work. They disable chinese only apps and features and add languages.
Click to expand...
Click to collapse
Hi again,have you tried the latest rom?
Nothing happens if i just install it, but after i restore about 50 apps, it starts rebooting. Every 2-3 minutes.
Not sure What to do.
Have tried a factory reset.

No i am still with 5.7.2, no hurry to upgrade.
Restoring apps could cause problems sometimes, try clean install. (I open all favorite apps in Firefox and and bookmark them so i can use "Open All in Tabs" and install them easily for any device.)

P.Kosunen said:
No i am still with 5.7.2, no hurry to upgrade.
Restoring apps could cause problems sometimes, try clean install. (I open all favorite apps in Firefox and and bookmark them so i can use "Open All in Tabs" and install them easily for any device.)
Click to expand...
Click to collapse
How is your battery life on those roms?
I am getting horrible battery life with like 1% drain every minute even when I'm not using it.
And I keep getting "com.Google.gapps has stopped.
I've wiped everything, clean install.
Please help.

http://htcfanboys.com/download/acid/?action=load&file=109949
There was some problems in this weeks original, did you try 5.7.26 hotfix? (Im still at 5.7.2, that should be better with battery and Gapps are working.)

P.Kosunen said:
http://htcfanboys.com/download/acid/?action=load&file=109949
There was some problems in this weeks original, did you try 5.7.26 hotfix? (Im still at 5.7.2, that should be better with battery and Gapps are working.)
Click to expand...
Click to collapse
Thanks.
Do you recommend I Install 5.7.2 or the Latest Hotfix?

Haven't tried latest, but can confirm 5.7.2 is working fine so try that. Usually i upgrade only after couple people say it's working good on Mi4 in Xiaomi.eu MIUI Weekly ROM Releases forum.

deleted

P.Kosunen said:
Haven't tried latest, but can confirm 5.7.2 is working fine so try that. Usually i upgrade only after couple people say it's working good on Mi4 in Xiaomi.eu MIUI Weekly ROM Releases forum.
Click to expand...
Click to collapse
Do I need to make a full wipe to downgrade or just flash with the updater app?

Do full wipe because com.Google.gapps has stopped problem.

[ROM] LineageOS 14.1 UNOFFICIAL h631

Latest release
Built from whoshotjr2006/touchpro's sources with minimal changes. All credit to original devs.
I'm not going to commit to regular updates but I'll try to do occasional ones.
Recommend using this TWRP (also stolen from touchpro).
Installation:
Enable developer options in stock ROM (tap build number a bunch of times)
Enable 'Advanced Restart' in developer options
Hold power button, select restart, restart to bootloader
Use fastboot to unlock bootloader
Use fastboot to flash TWRP recovery
Reboot to recovery using fastboot command
Wipe everything in TWRP, format data, and factory reset
Push ROM to /sdcard/ and install
Optionally push Gapps and/or LineageSU and install
Boot and enjoy (first start might take a while)
Tested on a T-Mobile LG G Stylo, all seems well.

As far as I can tell, everything is working fine. You should be able to dirty flash if you are using another Lineage 14.1 build but I haven't tested it.

It's awesome to see others making roms for this device again, but do you think you will be able to make a oreo rom though? ?

ItzBluestone said:
It's awesome to see others making roms for this device again, but do you think you will be able to make a oreo rom though? ?
Click to expand...
Click to collapse
The LOS14 tree is still getting security updates and will run a lot faster than LOS16. I could build an Oreo ROM but there's little chance of finding the vendor FW needed to get camera, bluetooth, etc working properly.

jsheradin said:
The LOS14 tree is still getting security updates and will run a lot faster than LOS16. I could build an Oreo ROM but there's little chance of finding the vendor FW needed to get camera, bluetooth, etc working properly.
Click to expand...
Click to collapse
oh, well that's unfortunate...

So what is different? Just security updates?

This ROM breathed new life into my old MetroPC version of this phone (2GB/16GB)!
I bought this phone two years ago refurbished and carrier-unlocked (other than banned on MPC) off Amazon. Looked brand new. I just installed a new battery last month. Original battery wore out.
ROM works beautifully. Nice to be free of the factory cruft. Also, the TWRP from your OP works much better than the one I had been running. (Neither TWRP reads the current time/date through.)
I had been rooted with SuperSU, now I'm rooted with Magisk. I flashed mini Gapps 7.1.
I have not tested NFC yet.
Thank you for this ROM and your post!

My TMo h631 will not take the image. During the install it will kernel panic and throw an error.
I do factory reset, wipes, formats but still no go.
Anyone knows how I can fix it?

Will this work fine on the LGM631?

SIM Unlocked G920W8, 9.0 and 10.0 ROMs no longer detect SIM.

*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.

I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!

I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.

New StatiXOS OFFICIAL 4.2 build for Essential PH-1

StatiXOS
Download StatiXOS for free. StatiXOS is a homebrew distribution of Android. StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal and clean, while providing quality of life improvements and up to date security patches. This page is to provide downloads for...
sourceforge.net
4.2 has been release
"Introduce our OTA Updater!"

For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
If you download
PH1-OTA-PQ1A.190105.090.zip
and then reboot into recovery (TWRP, be sure to disable pin on phone before hand and backup everything) then flash the above (I wiped everything first but DON'T wipe internal storage) then I did a second wipe of everything but internal storage and then I flashed 4.2 of StatiXOS and then I flashed TWRP, then I rebooted phone and set it up from new and restored everything from Cloud backup and I can confirm that I no longer have the Chrome freezing issue.
You can thank seungbaekm over in the Evolution-X 5.4 thread for this fix as he is the one that accidentally flashed the older PH-1 factory image and discovered Chrome then worked again! This should fix the issue for all the new Android 11 ROM 's out there for us folks that have the Chrome browser locking issues.
I did not even test the new 4.2 ROM on its own to see if it happens to fix the Chrome issue but I doubt that it does since it is not mentioned in the release notes. Also I have no idea if any of the other original factory images will also fix the issue, I only downloaded the one they he said he accidentally flashed and used it.
Hope this helps everyone with this issue as I know how frustrating it has been. Sure, there is the Bromite/Brave/Firefox work around, and I have been using and enjoying Bromite since 4.1 but I like having things working the way they are supposed to work.

Thanks you very much
I will test

Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.

aamadorj said:
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
Click to expand...
Click to collapse
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?

Just a question, does StatiXOS have slim recents included?

Mous3kteer said:
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Click to expand...
Click to collapse
I have no idea if using a.Pie firmware could have side effects in the future. So far, I haven't seen any.
Using the StatiXOS Telegram support group, I shared the information about the different firmwares to the devs, so I think they'll tell us if something can go wrong in the future.

Is anyone else having issues with sending a text message with this rom?

vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off

vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off

Double Post

Just reporting that I did a clean install - "Fastboot -w" on the latest working firmware (JAN20 FW, FEB20 Vendor iirc) and I'm very impressed.
Plus replaced the screen, battery, and buttons cable and now the phone is "essentially" new. Parts are actually quite cheap.
Chrome is working without issues.
360 Camera is working without issues
Haven't tried sending SMS with VoLTE On yet.
Amazing that we still a maintainer.

chanh2018 said:
If you have VoLTE on, turn it off
Click to expand...
Click to collapse
Yup, that worked. Thanks mate..

The March 10th update they pushed out through the OTA updater worked perfectly. It is nice to see we still have good support on this great phone.

SirDigitalKnight said:
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
Click to expand...
Click to collapse
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.

kt-Froggy said:
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
Click to expand...
Click to collapse
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.

SirDigitalKnight said:
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
Click to expand...
Click to collapse
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.

aamadorj said:
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
Click to expand...
Click to collapse
OK, here is my update... Noting your comment in the other post about the downgraded baseband, I decided to exclude the modem from flashing. Flashed everything else from PQ1A.190105.112-NOVENDOR via fastboot, rebooted, and... Chrome froze again. Ugh... :\ OK. I went back to fastboot and flashed the modem - this time after the reboot the problem was fixed.
So, I'd say it's safe to conclude that the modem (baseband) is the actual component that was screwing up the Chromium-based browsers. Go figure...

This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?

chrisrg said:
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
Click to expand...
Click to collapse
Even with stock rom LED is not blink if you're using stock messages, try Textra and see if it works for you.