Hi,
I hope someone can help me with this. I'm having some issues with the gps and the compass
When using any gps app, for example, HERE Maps, its always jumping around, and app always saying to adjust compass.
My phone is ALE-L21, and Build number is ALE-L21C75B146. EMUI: 3.1, Android: 5.0.1
Bootloader is still locked. Its still have the stock rom, but its a modified rom from a service provider.
I dont know if this is a software bug or hardware issue.
When trying to update, it says theres no updates.
If I unlock the bootloader and install the latest official huawei rom, will it fix it? And which one I should install?
Thanks!
Already unlocked bootloader and flashed stock rom. I have now the B188. Havent tested, if it still has the GPS issues
Schematic said:
Already unlocked bootloader and flashed stock rom. I have now the B188. Havent tested, if it still has the GPS issues
Click to expand...
Click to collapse
Hi,
Is B188 Dual SIM enabled?
Schematic said:
Already unlocked bootloader and flashed stock rom. I have now the B188. Havent tested, if it still has the GPS issues
Click to expand...
Click to collapse
Hello,
Where download this ROM version?
I didnt downloaded, it was an update from B170
First flashed the "Flash ROM B052.rar" in fastboot but it was saying balong, and couldnt find any updates, so then I flashed "ALE-L21V100R001C432B046b" to activate the dual SIM, blocked by the service provider, then I think I flashed this for some reason "Huawei_P8_Lite_ALE-L21_V100R001C432B052-Europe-Dual-SIM.rar" .
And yes, dual SIM works in B188.
I have p8 lite (ALE-L21)
and have the same problem with GPS and compass, specialty in compass turn some right about the real in all apps
and I am need GPS too mush
in anyone know how to solve it please say
Tested, and still has problems in GPS and compass even with the latest B188 update.
Im really disappointed with this device, I already have atleast 5 or more dead pixels with just a month of use only. :crying:
No more huawei's for me, I dont trust them anymore and wouldnt recommend to anyone.
Stay away.
Hello guys,
I would really appreciate some help with the following:
Issue
My proximity and light sensor is not working at all. And I am not convinced that it is a hardware issue. It happened on Oxygen OS 3.5.8 which was rooted with TWRP as recovery. The various sensor test apps available on the store will just report that there is actually no proximity/light sensor.
I read around and what I understood is that superSU can break the sensor, and that it is somehow tied to the radio firmware of the device.
What I tried
On OOS I flashed an older radio with no effect (I stupidly flashed the old superSU I had on my device just after, so it might have broken it again).
I also flashed the stock OOS image from Oneplus site.
What I would like to try
I just flashed Vertex OS Carbide. Sadly the sensor is still reported as 'No proximity/light' sensor. I would like to have a link to a compatible radio firmware so that I can test if it somehow help me fix the issue. I am confused on which radio firmware this ROM uses.
Also, if some of you experts are convinced that its a hardware issue (I live in a country where there is no official Oneplus representative), could you share a link to a replacement part? I checked Ebay but they are selling the capacitive buttons ribbons and are labeling it as proximity sensor.
Thank you for your help and excuse my noob-ness.
I think there's a persist file somewhere in the forum that's what you need
Sent from my ONE A2005 using Tapatalk
Hey all. I am in the US but bought international S7Edge when it came out. I dont know what firmware it had I think it was some italian one maybe. Then i rooted and started using custom roms. Then when nougat officially came out for S7Edge i un-rooted and went back to 100% stock using i think Vodafone 7.0 firmware. I think because i rooted i have a negative test response from Knox which i think stops me from getting OTA updates. It shows in software info that my OS version has security patch only from January 2017 so I am clearly not on latest firmware even though OTA says I am on latest.
Is there a site with a database of all firmwares out for the S7Edge international variant So i can find the latest and flash it to my phone since OTA wont get the latest.
samsmobile has the latest.
Yoiu still have an issue with your kernal as phone still thinks you have custom rom. Tripped knox on stock firmware will not stop OTA from downloading.
Hi,
I received my Le Max 2 a couple days ago and all was ok, except the fingerprint sensor worked 2-3 times then just stopped recognising anything at all.
I flashed LineageOS 15.1 (Oreo) today in the hopes it would fix the issue. Later I read in the forums here that modem firmware handles the fingerprint.
Read through a few posts, most notably: CN 26S 05.09 might be the best modem firmware
Now to the problem:
I am not new to flashing, it's not my first (or second ) time using ADB and Fastboot tools, but for the love of God, I cannot flash modem..
I downloaded various modems from the aforementioned link. I tried flashing via TWRP, no errors reported (also tried wiping cache/dalvik after flash). I also tried extracting NON-HLOS.bin and flashing via fastboot.
In both cases, I get no errors, everything goes through, but my Baseband version remains at: [MPSS.TH.2.0.c1.9-00050-M8996FAAAANAZM-1 1 [Aug 21 2016 15:00:00]] (and more importantly, the fingerprint reader does not work).
The only thing I haven't tried is erasing the modem "partition" using fastboot before flashing (and I'm reluctant to do so because if erase succeeds and flash fails again, I don't want to be stuck with a 5.7-inch device with no wireless capability).
If it makes any difference, the model is X820 (at least, came from the factory like that ). 6/128 GB option.
Bootloader was unlocked from the factory (seemed strange to me).
When I ran fastboot oem unlock, it reported that bootloader was already unlocked.
fastboot oem device-info returns the following:
Code:
D:\LeEcoMax2>fastboot oem device-info
...
(bootloader) Device product name: [le_x2_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Display panel:
OKAY [ 0.073s]
finished. total time: 0.076s
Any help is appreciated.
Thanks.
EDIT:
I apologise, looks like the radio is flashing fine, the ...c1.9-00050... part and the timestamp had changed, I just noticed this morning. Stock was ...00033...
I was under the impression that c1.9 implied China, 19S (or something like that). I noticed the change when my second SIM card showed "No Service" last night and after flashing 26S radio at 4 AM, I just went to bed, but this morning I noticed full level (no discrete "bars" on Lineage 15.1 ). So flashing was successful.
Anyway, I'm back to square one, fingerprint sensor is still not working.
Afaik 0050 modem and 466d firmware is the best, at least for oreo
where do i get that modem and firmware from?
ankerede said:
where do i get that modem and firmware from?
Click to expand...
Click to collapse
466D -> https://yadi.sk/d/woKdrlRrv8yhr/Для разработчиков
Heyyo, I'm the dude who made that 26s firmware thread long ago.
So since then I've learned the difference between modem firmware and full firmware.
I host FULL firmware links on my LineageOS 15.1 x2 thread. I'd recommend those over the yadisk modem only firmwares.
https://forum.xda-developers.com/le...x-lineageos-15-1-oreo-leeco-le-max-2-t3771577
Try them out. See which one works best for you as the experience flashing full firmware feels different to everyone.
ThE_MarD said:
Heyyo, I'm the dude who made that 26s firmware thread long ago.
So since then I've learned the difference between modem firmware and full firmware.
I host FULL firmware links on my LineageOS 15.1 x2 thread. I'd recommend those over the yadisk modem only firmwares.
https://forum.xda-developers.com/le...x-lineageos-15-1-oreo-leeco-le-max-2-t3771577
Try them out. See which one works best for you as the experience flashing full firmware feels different to everyone.
Click to expand...
Click to collapse
Sorry, a newbie question. If I flash the full firmware does that interfere with a custom rom? Do I have to re-flash the rom afterwards? (I'm not using lineage right now)
surfersea said:
Sorry, a newbie question. If I flash the full firmware does that interfere with a custom rom? Do I have to re-flash the rom afterwards? (I'm not using lineage right now)
Click to expand...
Click to collapse
Heyyo, firmware is separate from ROM. I know it is a bit confusing as some manufacturers call their ROM's firmware but firmware in the proper sense means the hardware firmware and ROM means Android operating system.
You may flash any firmware from my first post at any time via TWRP and it will not require reinstalling your ROM or Gapps.
ThE_MarD said:
Heyyo, firmware is separate from ROM. I know it is a bit confusing as some manufacturers call their ROM's firmware but firmware in the proper sense means the hardware firmware and ROM means Android operating system.
You may flash any firmware from my first post at any time via TWRP and it will not require reinstalling your ROM or Gapps.
Click to expand...
Click to collapse
I hijack a little the discussion toward fingerprint, which was the reason for the original post btw:
I both tried the 466d and the 20s full firmwares but the fingerprint didn't resuscitate (it worked when the phone was brand new then after the first rom flashing it stopped and never resumed).
Any suggestion?
And just to speculate about it, how can it happen ? Does the rom interfere with the fingerprint part of the firmware?
If so it's strange because I read in multiple thread of people with the same rom both with the fingerprint running and not running.
I read also about a possible problem with the fast charging feature. Is the fingerprint hardware really sensitive to the fast charge?
surfersea said:
I hijack a little the discussion toward fingerprint, which was the reason for the original post btw:
I both tried the 466d and the 20s full firmwares but the fingerprint didn't resuscitate (it worked when the phone was brand new then after the first rom flashing it stopped and never resumed).
Any suggestion?
And just to speculate about it, how can it happen ? Does the rom interfere with the fingerprint part of the firmware?
If so it's strange because I read in multiple thread of people with the same rom both with the fingerprint running and not running.
I read also about a possible problem with the fast charging feature. Is the fingerprint hardware really sensitive to the fast charge?
Click to expand...
Click to collapse
Hmm tbh not too sure why FP readers can go bad. It could be a hardware defect as some people have reported even reverting back to EUI ROM doesn't fix it as it still will not work.
At that point the only fix is to replace the fingerprint reader... Does your Le Max 2 still have any warranty? If so I'd recommend flashing back to the EUI ROM version it came with and lock your bootloader again and then contacting LeEco or the vendor you purchased it from for repairs.
Usually though after flashing a custom ROM for the first time, upgrading the firmware of the Le Max 2 resolves it as I'm guessing the source code for the kernel requires 19s or higher firmware.
ThE_MarD said:
Hmm tbh not too sure why FP readers can go bad. It could be a hardware defect as some people have reported even reverting back to EUI ROM doesn't fix it as it still will not work.
At that point the only fix is to replace the fingerprint reader... Does your Le Max 2 still have any warranty? If so I'd recommend flashing back to the EUI ROM version it came with and lock your bootloader again and then contacting LeEco or the vendor you purchased it from for repairs.
Usually though after flashing a custom ROM for the first time, upgrading the firmware of the Le Max 2 resolves it as I'm guessing the source code for the kernel requires 19s or higher firmware.
Click to expand...
Click to collapse
I just saw on my build.prop file that the fingerprint is recorded as Letv/LeMax2_WW/..... but the device model is the LEX820. Does that mean that I have to try the 19s firmware even though the device is X820 and not X821?
In case, is it safe to flash a X821 firmware on a X820 phone?
surfersea said:
I just saw on my build.prop file that the fingerprint is recorded as Letv/LeMax2_WW/..... but the device model is the LEX820. Does that mean that I have to try the 19s firmware even though the device is X820 and not X821?
In case, is it safe to flash a X821 firmware on a X820 phone?
Click to expand...
Click to collapse
It should be fine as the only real difference between Le Max 2 models is x829 lacks LTE band 20.
The build fingerprint used is from Indian 19s x821 because it is certified by Google.
For reference, I have an x829 (no LTE b 20 for me lol) and I have flashed x821 19s (my device then detected as le_x2_india) and have also flashed x820 20s, 26s, 28s and 416d and 466d (and my device then detected as le_x2) without any issues.
What exactly did I do to cause it? I've flashed tons of roms with no issues on my s8+ exynos, honestly I believe after I flashed the latest CRC7 R3 Firmware off Renovate-Ice website I got the initial "binary something something Samsung Official Only in Recovery)
Why did his firmware update cause this?
And how the hell can I make it never happen again
Stock rom for 6 more days sucks