Related
Hi guys
I was looking to upgrade my firmware on ALE-L02 to B150 via this thread:
http://www.carbontesla.com/2015/09/huawei-p8-lite-l02-c636b150-lollipop-firmware/
The update went though just fine, phone rebooted, relogged all apps. But now the device Build is now C50B311 (hi6210sft) I have found that my LTE is disabled on my nano sim, which usually worked via the old build. Is there a way to upgrade to 5.1? Or move away from this update (BalongC50B311)?
Device is not rooted etc. Stock.
Thanks guys!
Hello, it's because you have to downgrade to a build with two folder's (update and vendor ) and flash the two folder's for don't have this trouble named balong bug.
It's easy look in the zip update if you have the two and use the second folder like the previous .
I can't tell you because for look in I have to download this build .
Not all the update have it (the vendor folders)and you have to downgrade to the good version for don't have the balong trouble. This step factory reset and format your internal memory
Hi everyone,
I have a little problem with fingerprint with these 2 roms.
Normally I could add 5 fingers but I can only 3 max. If I try to configure the last 2, all my fingerprints dont work at all.
Moreover I can't delete fingeprints. When I try, they come back.
That is an issue which not occur with 6.0 custom roms.
Someone know how to fx it?
Thanks.
I'd suggest flashing the stock nougat 93-11 or 93-14 firmware (e.g. from the guides section) to resolve your fingerprint issues. Once that's done, future installs of lineage and RR should have fingerprint support for more than 3 fingers.
Thanks for replying.
I have xt1642. Is there a stock firmware Nougat for this device? I didnt find it
Nicozyp said:
Thanks for replying.
I have xt1642. Is there a stock firmware Nougat for this device? I didnt find it
Click to expand...
Click to collapse
I've got an XT1642 (UK - retGB, EMEA baseband) and updated to Nougat 93-11 using the stock files on here okay (now running Lineage with 4 FPs set).
The ROM I used to upgrade was the one linked here: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-install-official-december-nougat-t3518262 This will bring you up to the official 93-11 update via installing from stock recovery - you need Marshmallow build 139-63/64 however.
However, you may like to try either of these guides as well: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
As long as you can successfully install a Nougat stock ROM onto your device, the updates should mean your fingerprint sensor works properly in the custom ROMs. Bear in mind that updating to Nougat may wipe your data and cause you to lose TWRP/root until you re-install them.
Last question: can I wipe system and internal storage before installing ressurection?
Nicozyp said:
Last question: can I wipe system and internal storage before installing ressurection?
Click to expand...
Click to collapse
Once you've installed Nougat (and I recommend installing TWRP too), if you wish to install Resurrection Remix, only wipe system, data, Dalvik and cache. Don't wipe internal storage, since that's where your ROM zip is stored!
Silesh's initial post on the RR version for Moto G4s has more information on this https://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-n-5-8-0-t3507275
Unable to flash stock recovery => "image not signed or corrupt"
Nicozyp said:
Unable to flash stock recovery => "image not signed or corrupt"
Click to expand...
Click to collapse
The image is flashed. Boot into recovery and you'll realize.
Nicozyp said:
Unable to flash stock recovery => "image not signed or corrupt"
Click to expand...
Click to collapse
Which file are you flashing? Does it end in OKAY after that error?
EDIT - zeomal is too quick for me
Indeed it's ok.
For the moment I upgrade MM, then gonna flash stock Nougat.
So problem solved.
I've flashed RR and configured fingerprint ==> it works fine
Thanks for ur help and advices
fingerprint option is not displayed in my zuk z1
Hey I have installed official lineage-os on my zuk z1 handset but still I can't find fingerprint option in my zuk
What to do help me
I was updating my system security patch from official moto but after restarting it started twrp and asked me if i want to flash that update file, after swiping it opened Twrp homepage(i was unable to restart from its reboot option but i went to the bootloader and started cell (Working correctly currently))
Two Options
1. I should lock the bootloader
2. Leave it as it is.
If option 1. lock my bootloader on stock Android Nougat 7.0 on Moto G4 plus Athene XT1643. As i have stock android and precious data so i only want to lock bootloader Without wiping my system Data (I can wipe if no other way is available).
For option 2. Keep it as it is.
Please suggest me what to do and how?
And tell me about official Oreo or Custom Oreo(best option)
Sorry for my bad English and errors(If any).
Thanks in advance
@cooldude1598 official update can not be flashed through TWRP, you need to have stock recovery and unmodified system/kernel/etc as well.
If you have played with stock ROM (flashed custom kernel/ rooting / installing and flashing other stuff ), it will fail through stock recovery too, for that you need to download appropriate stock ROM according to your current version of stock ROM, and it will erase everything (includes apps and app data, photos, videos and anything on internal storage)
you said, you have system data ?
What is that?
If it is photos, videos, or personal data then move it to external sd card or PC, apps and app-data can be backup through titanium backup, and also move it to safe place.
If not this, then tell us what system data?
Fro another question about LOCKING, it is not necessary to re-lock bootloader, you can go with unlocked bootloader, don't lock again, once you flash stock ROM through fastboot, you can update to any security updates without fail.
English is weak here too, hope you got it what i said.
Hello, I have a brazilian G5 Plus that originally didn't have the retail Nougat image Installed (bought form a carrier), but I was able to update to the leaked brazilian 8.1 update. The phone was never bootloader unlocked or rooted, however I'm willing to return to stock nougat in order to try Pie roms and not lose the fingerprint function. What I want to know is A) can i flash retail nougat images on my phone (as it wasnt retail at first)? and B) at what time should I make backups of EFS and Persist partitions?
Should I unlock bootloader while on oreo. install twrp, make backups of efs and persist and then flash stock nougat?
Or should I be able to downgrade to Nougat without any issues, and take backups of EFS and Persist before flashing Pie Roms?
Any clarification on the subject would be deeply appreciated.
Thanks in advance.
Mrkblo said:
Hello, I have a brazilian G5 Plus that originally didn't have the retail Nougat image Installed (bought form a carrier), but I was able to update to the leaked brazilian 8.1 update. The phone was never bootloader unlocked or rooted, however I'm willing to return to stock nougat in order to try Pie roms and not lose the fingerprint function. What I want to know is A) can i flash retail nougat images on my phone (as it wasnt retail at first)? and B) at what time should I make backups of EFS and Persist partitions?
Should I unlock bootloader while on oreo. install twrp, make backups of efs and persist and then flash stock nougat?
Or should I be able to downgrade to Nougat without any issues, and take backups of EFS and Persist before flashing Pie Roms?
Any clarification on the subject would be deeply appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Don't try to downgrade your bootloader as it going to brick your device. If you want to make back up made the back up of Oreo(now in which your using) and nougat also, as we can't say where it goes wrong. And you can flash retail nougat image but don't flash gpt and bootloade so it don't brick your device.
Read this: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
If you want to try some custom rom and not lose fingerprint, all you have to do is run the persist fix, flash a 7.0 TWRP-flashable stock build and THEN flash your custom rom. No need to fastboot flash the stock image. Of course also backup your persist and EFS as soon as you first boot into TWRP.
prokaryotic cell said:
Read this: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
If you want to try some custom rom and not lose fingerprint, all you have to do is run the persist fix, flash a 7.0 TWRP-flashable stock build from and THEN flash your custom rom. No need to fastboot flash the stock image. Of course also backup your persist and EFS as soon as you first boot into TWRP.
Click to expand...
Click to collapse
Thanks, will have a look at it.
Hello everyone, i installed the leaked soak test with the "apply update from SD card" on stock recovery after locking my bootloader.
One week later, i unlocked it again and flashed TWRP for rooting with magisk.
Even with root tweaks i still face problems with soak 8.1, due to the lack of custom kernels.
So i decided to flash Stock N (1st April) with the TWRP Flashable zip from @Jleeblanch , how i avoid IMEI loss doing that? If i backup Oreo's EFS with TWRP, it will be compatible if i try to restore it after flashing, or it's not even necessary?
The TWRP flashable zip files by @Jleeblanch does not have the commands "fastboot erase modemst1" and "fastboot erase modemst2" so your IMEI will be fine. However Stock Oreo does mess up with IMEI.
Flash TWRP flashable Stock Nougat by Jleeblanch. You will not lose IMEI, but there will still be a problem of persist (i.e you will lost IMEI if you flash Stock ROM via fastboot). So to fix persist, follow this thread: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
Losing IMEI is a persist related problem (Soak Test 8.1, and all 64bit Pie ROMs are causing this). So if you fix persist, then you will never lose IMEI.
I recommend you to take backup of EFS before this process (i.e while having a bad persist and working EFS) and also after fixing persist (i.e while having a good persist and working EFS).
EFS backup by Lyuu's TWRP takes a backup of EFS, fsg and persist.
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Heeth21 said:
The TWRP flashable zip files by @Jleeblanch does not have the commands "fastboot erase modemst1" and "fastboot erase modemst2" so your IMEI will be fine. However Stock Oreo does mess up with IMEI.
Flash TWRP flashable Stock Nougat by Jleeblanch. You will not lose IMEI, but there will still be a problem of persist (i.e you will lost IMEI if you flash Stock ROM via fastboot). So to fix persist, follow this thread: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
Losing IMEI is a persist related problem (Soak Test 8.1, and all 64bit Pie ROMs are causing this). So if you fix persist, then you will never lose IMEI.
I recommend you to take backup of EFS before this process (i.e while having a bad persist and working EFS) and also after fixing persist (i.e while having a good persist and working EFS).
EFS backup by Lyuu's TWRP takes a backup of EFS, fsg and persist.
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat.
Click to expand...
Click to collapse
Rajat's 64bit TWRP doesn't have EFS Backup option here. I will try Lyuu's
Thanks for the help.
xSamukaBRx said:
Rajat's 64bit TWRP doesn't have EFS Backup option here. I will try Lyuu's
Thanks for the help.
Click to expand...
Click to collapse
Read the second post again, I have edited it.
Heeth21 said:
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Click to expand...
Click to collapse
I kinda fear it auto-updating, so i'll make sure to delete the "3c_ota" app from /priv-app
EDIT: Already know the risks of taking OTA with unlocked bootloader or after downgrade...
Heeth21 said:
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Click to expand...
Click to collapse
What about Lineage-based 7.1.2 32 bits ROMs? Can i flash them without issue? Already flashed Stock N
with TWRP, and It worked fine. Just want to know.
Please don't tell me i need the fastboot Stock N, i can't flash that anymore i think. :crying:
xSamukaBRx said:
What about Lineage-based 7.1.2 32 bits ROMs? Can i flash them without issue? Already flashed Stock N
with TWRP, and It worked fine. Just want to know.
Please don't tell me i need the fastboot Stock N, i can't flash that anymore i think. :crying:
Click to expand...
Click to collapse
Yes you can flash Custom ROMs from TWRP, however, I don't think you should right now.
I got my device hard bricked randomly from Custom ROM. idk what caused it, maybe some changes which I did or something else. If a similar thing were to happen with you, there's no guarantee whether the current blankflash would work or not.
Heeth21 said:
Yes you can flash Custom ROMs from TWRP, however, I don't think you should right now.
I got my device hard bricked randomly from Custom ROM. idk what caused it, maybe some changes which I did or something else. If a similar thing were to happen with you, there's no guarantee whether the current blankflash would work or not.
Click to expand...
Click to collapse
Even through i just want a pure lineage OS instead of a custom based on it (too many stuff comes with a risk, right?), i better not try...