Originally I flashed an unofficial Lineage build: https://forum.xda-developers.com/t/...ageos-17-0-for-umidigi-f1-android-10.3997827/
I then rooted it with Magisk, ended in a bootloop, and fixed it by flashing the original firmware back in: https://www.needrom.com/download/official-firmware-umidigi-f1/
I then re-flashed the custom ROM above, which went fine, except that the fingerprint sensor was completely missing, not even in settings.
Flashed stock: works.
Flashed ROM: doesn't
Tried to restore a TWRP backup I made of the first custom ROM: nada
Found a compatible A/B build of linegae tremble, https://sourceforge.net/projects/andyyan-gsi/files/Testing/: it works, but I had trouble flashing Magisk, and a guide I found online suggested wiping system, flashing magisk and re-flashing the rom, and so did; as a result the fingerprint diappeared.
Went back to stock, worked, tremble again, no, stock again, and now it's not detected even there.
What can I do to get the sensor working again?
(nb: I'm in europe, but for some reason my phone uses the global firmware)
Related
I rooted my samsung fascinate and falshed a CM7 stable, i loved it except for the fact that my GPS wasn't working. So after some reading and research, i learned that i would have to CWM recovery, flash back to stock, get a gps lock, and then restore back to CM7 and i would have a lock.
Few things went wrong, in my original rooting, i somehow managed to wipe data/cache, thus wiping the stock rom from the phone before i could make a recovery of the rooted stock rom. So when i went back to stock with Odin, i had to completely go back to stock (recovery, stock froyo, stock kernel, etc.) Even at completely stock i still couldn't get GPS lock, even though i could get gps lock before initial root, does anyone know why? I thought it was just Cyanogenmod but i flashed MIUI and still couldn't get lock, yet i was able to get a lock with out root.
after not being able to get a lock, i still needed to get back to my recovery that i made of CM7, problem is i'm not sure which version of CWM recovery i used in order to make the recovery, i'm almost certain that it was the recovery that came with the older rom manager version in the CM7 build i used, but i've tried multiple CWM recoveries and none of which is able to read the recovery files correctly and the recovery can't be fully restored. is there anyway to see exactly which version of CWM was used in order to create the dated backup files on my SD card? Or do i just have to keep trying different versions until one works? I've tried the latest CWM from ROM Manager for the fascinate, but unfortunately the latest version is still unable to read the recovery files
any help is appreciated. cheers.
...You dont have to root to flash a custom rom. That being said there is a guide in the general section that explains how to do things properly.
Hi all,
I own a brand new Galaxy S6 Edge, SM-G925F, bought just 3 days ago in European Union/
Germany.
It has installed the latest Samsung Stock:
Android version: 5.1.1
Base band version: G925FXXU3COI9
Build number: LMY47X.G925FXXU3COI9
Security Software: MDF v2.0 Release 3 und VPN v1.4 Release 5.2
Latest Stock: G925FXXU3COI9_G925FDBT3COI6_DBT.zip
After updating OTA to the latest stock I tried to root the phone.
First of all I have flashed TWRP 2.8.7.1 via Odin 3.10.6. Then I have installed
Hacker Kernel V5 and XPosed v75.8 by WANAM (20151030) (using TWRP).
After finishing configuring the phone I have seen the next day that my akku has
been eaten and found out that the phone *never* enters deep sleep mode.
As soon as I go back to Stock ROM, Stock Kernel, Stock Recovery
(G925FXXU3COI9_G925FDBT3COI6_DBT.zip), deep sleep mode is working instantly
(controlled with CPU Spy).
What I have done without success to solve the problem:
1. using TWRP Advanced Wipe: erasingDalvik Cache, Cache several times
2. trying the solutions from zidroid (fix-battery-drain-and-deep-sleep-issue-on-galaxy-s6-and-s6-edge)
Method 1 (zip file flasing and Method 2 (terminal).
Both in several combinations with different kernels, alternative ROM, stock ROM,
root only (flashing kernel using Odin without TWRP)
3. trying differenz kernels:
- Hacker Kernel v4, v5
- UniKernel v8
- AELMultiVariant_v2_9_311015
4. trying the kernels without custom recovery, i.e. first flashing stock ROM, then
flashing the kernels directly using Odin.
5. trying the next solution that I have found in the forum:
first stock firmware again, then TWRP, then kernel (for root). Afterwards extracting stock
recovery image from G925FXXU3COI9_G925FDBT3COI6_DBT.zip, flashing this one only.
Running stock recovery, erasing cache, reboot (repeated several times).
Again no deep sleep.
6. first stock firmware again, then flashing TWRP and CarHDRom_V.14_3COJH.
All these tries without XPosed framework, starting from a fresh installed stock system
(i.e. resetting the whole phone to default, then erasing/formatting everything (without
EFS) from TWRP, then flashing stock recovery, kernel, ROM (G925FXXU3COI9_G925FDBT3COI6_DBT.zip)
by Odin.
Even tried everything without a SIM card.
As soon as I flash something (kernel only, TWRP only, combinations or complete ROM) the
phone never enters deep sleep mode. In "best" case it is working with 200 Mhz only.
Can this be a problem with Samsung's latest boot loader?
Thanks for your assistance!
Problem solved, reason unknown
In the end I have found a working solution.
1. using TWRP Advanced Wipe: erasingDalvik Cache, Cache several times
2. flashing stock recovery, kernel, ROM (G925FXXU3COI9_G925FDBT3COI6_DBT.zip)
by Odin.
3. flashing TWRP
4. flashing hacker kernel (enabling root)
5. flashing XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S.zip
Deep Sleep is working now, even in combination with XPosed framework and XPrivacy.
As XtreStoLite_ROM_v2.4_Deo-Mod-Edition is based on XXU3COI9 , I assume there could
be a problem with the lasted boot loader from the stock firmware XXU3COI9 that I had installed
previously.
yoda947 said:
In the end I have found a working solution.
1. using TWRP Advanced Wipe: erasingDalvik Cache, Cache several times
2. flashing stock recovery, kernel, ROM (G925FXXU3COI9_G925FDBT3COI6_DBT.zip)
by Odin.
3. flashing TWRP
4. flashing hacker kernel (enabling root)
5. flashing XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S.zip
Deep Sleep is working now, even in combination with XPosed framework and XPrivacy.
As XtreStoLite_ROM_v2.4_Deo-Mod-Edition is based on XXU3COI9 , I assume there could
be a problem with the lasted boot loader from the stock firmware XXU3COI9 that I had installed
previously.
Click to expand...
Click to collapse
fixed!
Well guys, i would like to know if i should restore the backup that i made to MIUI8 MM after start flashing ROMS in order to flash the new RR 5.8.
Today i flashed MIUI 8.6.1.12 via MiFlash, then, i installed TWRP and flashed CM13 Official (downloaded from the official site) WITHOUT FLASHING CM13 FIRMWARE and the GAPPS. All was alright until i decided to input a pattern to lock my phone, the application "settings" crashed every time i tried to set up a pattern. So, i decided to wipe all the phone and flash RR Based on android MM, WITHOUT FLASHING CM13 FIRMWARE, it booted normally, but when it asked for wifi, it didnt detect anyone, and it also didnt detect my 2 sim cards. So i reflashed that RR ROM, but this time, flashing CM13 Firmware first, but still no solution, no wifi and no sim-cards
What should i do?
Thanks :fingers-crossed:
[SOLVED]
Recently I've installed Oreo AOSP, I wanted to return flashing from TWRP but stucks on bootanimation, I tried with XGen but the problem persists
Also I tried through flashhtool but the program it doesn't detect my phone, also I tried with Emma, the process was completed correctly but when I boot up the phone the custom ROM is there
Im going to try flashing the Loire kernel through TWRP, at least I want to move to LineageOS
Flash a stock based custom rom (XGEN or Persian Rom) - dirty or clean /system is your choice. If you want extra then flash the clean patched kernel in the rooting thread (we actually don't need this)
Note that the phone won't boot properly and will bootloop, but now the phone will be recognize as F5121/22 in flashtool so you can flash the rom as normal.
n0k0m3 said:
Flash a stock based custom rom (XGEN or Persian Rom) - dirty or clean /system is your choice. If you want extra then flash the clean patched kernel in the rooting thread (we actually don't need this)
Note that the phone won't boot properly and will bootloop, but now the phone will be recognize as F5121/22 in flashtool so you can flash the rom as normal.
Click to expand...
Click to collapse
Already I solved the problem, i flashed the AOSP kernel in Existenz N, then I can boot as usual, however thanks for your answer
Hi guys,
i have an old ASUS MeMOPad FHD10 LTE, which i am trying to use LineageOS with.
TLDR: suddenly no Touch input in TWRP Recovery AND LineageOS 15.1/16 after it worked at first, OTG cable with mouse/keyboard input as workaround, in stock ROM the touch input IS working without problems
I unlocked the bootloader, did a backup of stock recovery img, flashed TWRP v3.2.3-0 for [Asus_ME302KL][DUMA] (from here). I rebooted to TWRP and made a NANDROID backup and flashed LineageOS ROM 15.1 (from here)
Everything worked perfectly fine until here, i booted up LineageOS 15.1 successfully, then i tried to flash mindthegapps (from here), i noticed too late this was the 64bit Version and ofc it bugged out to hell.
I then wiped data/cache and flashed 15.1 ROM and this time i used opengapps full package for 8.1 and flashed it directly after, but on reboot LineageOS 15.1 got stuck (just rebooted after 20min loading screen).
Then after a few more steps and tinkering, including trying out Lineage 16 for ME302KL, at one point the touch input in TWRP stopped responding on entering recovery. Multiple restarts didn't help. I didn't do anything other then flashing ROMs and wiping data/cache (at some point /system too).
I plugged in an USB Mouse with OTG and was able to navigate and flash back the stock ROM from nandroid backup, the touch input worked just fine!
Then i rebooted into TWRP, still no touch. I flashed LineageOS 15.1 ROM, and to my shocking, also no touch input after booting up. Flashing back stock ROM did get it back to working again. I even flashed back the stock recovery IMG and re-flashed TWRP again, still no luck.
What else is there, that i can try?
I was thinking of fastboot erase/format in bootloader, which partitions do i have to delete for a FULL reset, since flashing back stock recovery/rom didn't help?
Got touch input working with twrp-3.1.1-0-duma (older version), proceeded to flash Lineage 14.1 for MeMOPAD10 FHD... still no touch input there.. im so confused, any help?
Got touch working now with AOSP Extended ROM: https://forum.xda-developers.com/android/general/rom-aosp-extended-v4-4-t3637692
For now i'll stick to that.. but why does it break on LineageOS?
Hi, May i know how you unlocked the boot loader? for me the .apk downloaded from ASUS is not working. it always says "An unkown error occurs, which may be a network connection issue. please wait and try again later".
is there any other way to unlock the bootloader? appreciate your response.
Hello, may I ask how you unlocked the boot loader?