z17 speakers dead - ZTE Nubia Z17 Questions & Answers

Hello
Today I have succeed install 4.16 update and the oreo 5.15 with nano gapps. All ok, but when I go to change de sound of incoming calls, suddenly sounds disappear from speakers, and only have sound from usb c adpater to headset speakers.
I return to a twrp backup with miui, and the problem persist. With stock 4.16 the same.
can you help me...
thanks in advance

where did you get 5.15 update ?

sorry, 5.06 update

Finally, today when I paired two smartwatch with bluetooth to listen the audio form the phone, disconnect one and bluetooth stops one moment , then the speakers are working again...
I don´t know why, but very happy
Now, the phone are working 100% with oreo 8.1. Gapps working well. With new trwp 3.2.1 by SY i can mount data and i have made a twrp backup. I flashed the img file inside of zip package with fastboot.
To install oreo i have follow the method from Marcus
Originally Posted by rmarcus
It was a lot through trial and error.
1 I updated after 4.16 is installed and a clean install, factory reset.
2 after 4.16 is cleaned installed you go through manual update and select the new beta Oreo file.
3 after installation of Oreo is complete, run it and then go and install TWRP as you already know.
4 once TWRP is installed you will have to format data with ext2 first and then ext4, you can find it through advanced wipe.
5 download gapps, I used nano, use a software to edit it, I use WinRAR, find the wizard something APK inside gapps and simply delete it, there a phone and tablet, delete both just in case. Just save the zip file, don't do anything else.
6 transfer to the phone running TWRP and install it.
I'm sorry if it is not that clear, as I said, more trial and error than anything.
Good luck and don't hesitate to ask.
I have used twrp 3.2.1 to flash the 4.16 update.

Related

finally custom rom for lg g3 d858hk

hey guys i found custom ROM for d858hk version which is here
http://bbs.gfan.com/android-7892224-1-1.html
can be translated through Google but we need someone to explain to us in details.
I might able to help, I can read Chinese
let me know if you want any explanations.
it's based on lollipop 20d
- v1.0 LED not working, and this v2.0 fixed the problem
- rooted, superSU v2.46
- once you flashed the ROM, no need to flash the ROOT again
- busybox is in the system and no app not there
- works on D857 858 and 858HK
- it's a LIGHT version, there are functions that are deleted, like weather widget for example
- including deleted app inside the ROM, and could recover yourself
- app can write data to external SD card
- split view works for 3rd party app
- smart cover function removed, user can download the "deleted app" and put back into the system to get it working
deleted apps
http://pan.baidu.com/s/1mg86X6o
HOW TO FLASH
FOR D858HK
1. ROOT
2. install TWRP 2.8.1.0
3 Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
4. Flash ROM using this newest TWRP
D857 and D858
1. ROOT
2. download build.prop.zip, extract, using ES explorer to replace the one in "system" folder
3 flash D858HK 's TOT (http://bbs.gfan.com/android-7502599-1-1.html)
4.install TWRP 2.8.1.0
5. Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
6. Flash ROM using this newest TWRP
Do "double wipe" after flashing the ROM, otherwise might have FC messages
Thanks alot i think this will help ...will try it now
but can we install twrp when in lollipop as i am now on lollipop
any ideas?
maybe these
http://bbs.gfan.com/android-7677473-1-1.html
one click Recovery installation
need to be rooted
1. extract files to computer
2 connect phone
3 turn on usb debugging
4. run Recovery.bat
---------------------------------------
old temp way, didn't say if it works on L or only KK
http://bbs.gfan.com/android-7727191-1-1.html
So...can any of you fluent Chinese speakers/readers help with the actual downloading of the ROM? It seems the rom is available at http://pan.baidu.com/s/1mg86X6o, but I get a little overloaded and can't figure out how to download from there. It seems to want me to log in, but I can't figure out if there's a non-login download ability lurking somewhere?
Do you have some screenshoots ?
Two things. First, I had the wrong link before. Correct one is: http://pan.baidu.com/s/1sjoKe4l. Second, I realized the reason is that the zip file is over 1GB and they force you to a "download butler". So the login thing is related to copying that file into your (QQ, for example) account and then you could download the file from there.
If anyone with a D858HK is interested, I was able to install this custom rom on my phone without any problems. I followed steps elsewhere to root (the one click version) and install TWRP. The rom is basically a slim version of the standard lollipop rom. If you end up deciding to install this, be aware that the Google Contact Sync app is not included within the rom and you'll need to also download the "deleted apps" zip file mentioned in the same post (link in OP). In the "deleted apps" zip, you'll want to grab the Gooogle Contact Sync apk and install that ... otherwise you can't get your contacts copied to the new rom. There were a bunch of other apks, but this one the only one so far that seemed like it shouldn't have been removed from the rom.
FYI, here are the version details of the rom:
Android version: 5.0.1
Baseband version: MPSS.DI.3.0.c6.2-00011-M8974AAAAANAZM-1
Kernel version: 3.4.0
Build number: (some chinese)1121561(more chinese)
Software version: D858HK20d-HKG-XX
So in total its not worth installing it? But anyway, thanks for your report!
silencer1979 said:
So in total its not worth installing it? But anyway, thanks for your report!
Click to expand...
Click to collapse
I guess that depends on how easy it is to remove LG's bloatware and whether or not you need all/any of it. I personally didn't care for it anyway. But yeah, other than that, nothing special about the rom.
There were a bunch of other apks, but this one the only one so far that seemed like it shouldn't have been removed from the rom.
i believe there's a thread somewhere in this forum (http://bbs.gfan.com/forum-1508-type-10913.html) regarding d858 MIUI, could someone confirm? Thanks
Edit
twrp flashh from MM
has anyone successfully flashed TWRP from an MM rom i tried it and i got bricked and i cant seem to find one for MM only for LP
Lg g3 d858hk
Hey, did you install? There is a problem or not? All programs worked fluently?
xdax1 said:
let me know if you want any explanations.
it's based on lollipop 20d
- v1.0 LED not working, and this v2.0 fixed the problem
- rooted, superSU v2.46
- once you flashed the ROM, no need to flash the ROOT again
- busybox is in the system and no app not there
- works on D857 858 and 858HK
- it's a LIGHT version, there are functions that are deleted, like weather widget for example
- including deleted app inside the ROM, and could recover yourself
- app can write data to external SD card
- split view works for 3rd party app
- smart cover function removed, user can download the "deleted app" and put back into the system to get it working
deleted apps
http://pan.baidu.com/s/1mg86X6o
HOW TO FLASH
FOR D858HK
1. ROOT
2. install TWRP 2.8.1.0
3 Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
4. Flash ROM using this newest TWRP
D857 and D858
1. ROOT
2. download build.prop.zip, extract, using ES explorer to replace the one in "system" folder
3 flash D858HK 's TOT (http://bbs.gfan.com/android-7502599-1-1.html)
4.install TWRP 2.8.1.0
5. Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
6. Flash ROM using this newest TWRP
Do "double wipe" after flashing the ROM, otherwise might have FC messages
Click to expand...
Click to collapse
My LG-D858HK phone hard bricked:
What happened/how I hard bricked the phone. I'd already rooted the phone with Marshmallow and then tried to flash phone TWRP by (mistakenly) using https://play.google.com/store/apps/details?id=b007.autorecd858hk when it hard bricked the phone. Now, the phone screen is black/blank and blue/red LED light flashing.
In addition, my PC doesn't recognise phone when plugged into USB port/s. Pop-up on PC screen says; “The last USB device you connected to this computer malfunctioned and windows do not recognize it.” And in Device Manager, I see a ‘yellow triangle’ next to LGE Platform Android Composite USB Device Driver.
I tried different methods to go into download mode and I’m not sure if any worked. Because, obviously, I can’t see anything on the phone screen to carry out procedures to fix phone in download mode. Moreover, I’m not even sure if the phone goes into download mode apart from a sound made from PC and the pop-up straight after.
PC always recognised phone when plugged into USB port/s before it was hard bricked.

I upgraded to Nougat Manually and it half worked :S

So I followed a tutorial online to install Android Nougat 7.0 on my Huawei P9 lite. Once I was in TWRP I realised I was supposed to install two update files from two different .zip files. Trouble is I only had the one update on my phone at the time. I didn't want to exit TWRP at that stage because I already installed one of the update files.
When I booted my phone after the update, it all seemed to be working with 7.0 installed. Then I noticed my internet data wasn't working outside of wifi, and my bluetooth isn't turning on. The rest seems to be running fine other than those two things.
I rely a lot on bluetooth and internet on the go. I need it back, does anyone know what I could do, outside of factory reset?
Thanks
factory reset wouldn't help, you need to reflash update.zip and data_full.zip AT SAME TIME without rebooting
Coolyou said:
factory reset wouldn't help, you need to reflash update.zip and data_full.zip AT SAME TIME without rebooting
Click to expand...
Click to collapse
Okay, I realised that just now. Trouble is I am having trouble booting into TWRP now. I just get "your device has been unlocked and can't be trusted." with an orange web link.
For some reason my phone says in the settings that I'm still on android 4.3 although the ui and functionality is 7.0. Also, the EMUI is 2.0. I don't know how I got TWRP working before but I think there's a conflict due to it half being 7.0 so recover won't boot. I have tried loads of tutorials online but none of the rocovery.img or twrp.img files are working.
have the exact same problem, on android 4.3 and stuck.
from what i understand to dload a working stock rom, you need to have the correct oem info that matches the recovery stock rom. i cant flash any OEMinfo as i cant get root from revolution recovery.
no access to Data partition either.
no other recovery's to install as its the only one for nougat.
So i need help for this issue too.
jackvdbuk said:
have the exact same problem, on android 4.3 and stuck.
from what i understand to dload a working stock rom, you need to have the correct oem info that matches the recovery stock rom. i cant flash any OEMinfo as i cant get root from revolution recovery.
no access to Data partition either.
no other recovery's to install as its the only one for nougat.
So i need help for this issue too.
Click to expand...
Click to collapse
I fixed it! It was more simple than I realised. I used the dload folder method; Placing the update.app into a folder called 'dload' on an sdcard. Then holding power, both volume buttons to initiate the update.
Thanks for your help guys!!

WiFI doesnt work Show 02:00:00:00:00:00 mac address.

Hello to everybody, the wifi phone of my OP5 woked very well. One day I flashed one ROM, I dont remember what and broked the wifi, now show the typical broken mac address, I saw all the post even fixing nexus wifi phone but didnt work. I lnow that I need to upgrade to Oreo, now Im in Nougat, but the problem is when I flash the oreo stock rom the phone get a bootloop, I tryied everything so I need to forget upgrade. How can resolve this problem. I updated no stock ROM oreo like aiscp but the wifi not repair. I dont know what do. I tried with QPST QXSM but nothing I can repair my phone. Any help?. I tried too modificating all the files about wifi, wifi.bin (I dont remember the names) and didnt worked
If you are using TWRP make sure to update to latest codeworks version and in the wipe section select format data. This is necessary when moving from Nougat to Oreo on the OP5 if you are using a custom recovery. That will erase everything on your phone except TWRP. Plug your phone into a computer and it will show up like a USB drive. Copy and paste the Oreo ROM zip for stock OOS onto your phone. If you want to be rooted also copy the latest Magisk zip. Flash OOS zip within TWRP. If you boot into the system after that you will be 100% stock including recovery. If you want to be rooted and keep TWRP flash Magisk zip as well before booting into system. Given your circumstance I would highly recommend going 100% stock and making sure everything is working right again. You can always install TWRP and root again later.
i remember how i flashed blu spark kernel for custom rom, when i was at stock oos and get this broken wifi. try to look at that
jhs39 said:
If you are using TWRP make sure to update to latest codeworks version and in the wipe section select format data. This is necessary when moving from Nougat to Oreo on the OP5 if you are using a custom recovery. That will erase everything on your phone except TWRP. Plug your phone into a computer and it will show up like a USB drive. Copy and paste the Oreo ROM zip for stock OOS onto your phone. If you want to be rooted also copy the latest Magisk zip. Flash OOS zip within TWRP. If you boot into the system after that you will be 100% stock including recovery. If you want to be rooted and keep TWRP flash Magisk zip as well before booting into system. Given your circumstance I would highly recommend going 100% stock and making sure everything is working right again. You can always install TWRP and root again later.
Click to expand...
Click to collapse
I did it but didnt work

Moving from stock Android 5.0.1 to Resurrection Remix N v5.8.5.

Hello community!
First of all, I feel I have to apologize to you all since I know I have clogged the forum with a lot of requests of help about upgrading my smartphone... They are scattered all over the place so I have decided to gathered in a definitive one.
I have edited this post to make it a comprehensive guide for all the people who want to upgrade their HUAWEI P8 LITE ALICE from the stock Android 5.0.1 to the Resurrection Remix N v5.8.5. Before go any further I want you to read the following disclaimer:
PLEASE PLEASE PLEASE READ THIS!!
I am not a developer. I am not a programmer. I have been greatly helped by the user Botar230 so, unfortunately, I cannot help you in case of problems. I myself had problems and had to ask for help. The only thing I can say is to be always polite and try to explain, as best as you can, what's going on.
I will try to be as much clear as possible here but keep in mind that english is not my native language so it is possible that I might mistaking something. My apologize. I am not responsible for any damage you may do to your mobile and I am not responsible to any data loss it may occur. You should ALWAYS do a backup before proceeding. ALWAYS.
I've decided to flash Resurrection Remix N v5.8.5. because it is pre-rooted with Magisk.
BEFORE start to upgrade your mobile, read all this post twice and be sure to understood all the things I have written here. Check the links, check if you have the correct files, check if your mobile is fully charged, check if the bootloader is unlocked, check if you have the right ADB files and drivers downloaded and installed. Please do it BEFORE you start everything.
Done? Everything is fine? So, here we go!
GOAL: Moving from stock Android 5.0.1 to Resurrection Remix N v5.8.5.
MY MOBILE: Huawei P8 Lite ALICE (ALE-L21) unbranded single SIM - Build number: BalongC50B311 - Kernel 3.10.61-gcd3fde7 - EMUI 3.1
BOOTLOADER STATUS: unlocked, checked via ADB
The build number and the kernel number might differ. You should check them carefully and search around this forum how to proceed properly. Also, I totally don't know what to do if you have a double SIM phone. Sorry.
These are the files I have downloaded and put on the MicroSD before starting the whole process:
b895_update.zip
open_gapps-arm64-7.1-nano-20180702
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
The file TWRP_3.1.1-0_ALICE_BL.img have to be put in the same directory where adb.exe is since you will flash it via adb command: fastboot flash recovery TWRP_3.1.1-0_ALICE_BL.img once you have entered in fastboot mode AND you have checked that your bootloader is unlocked.
Now, the next steps that worked for me are:
install TWRP_3.1.1-0 via ADB
Factory reset (Wipe -> Swipe to wipe)
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload as suggested by Botar230. I find myself comfortable to use ADB.)
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload
Flash RR-N-v5.8.5-20180302-alice-OpenKirin) via TWRP AND at the same time...
Flash Open Gapps via TWRP. You HAVE TO USE THE ARM64 - 7.1 VERSION!!!
Reboot your device. It is done! :good:
NOTE!! Updating the phone to b895 will take really a lot of time. Seriously. It might be scary but it's ok. It will update EMUI too.
NOTE!! When you install TWRP via ADB, the TWRP_3.1.1-0_ALICE_BL.img file MUST BE in the same directory where the adb.exe file is.
At this point, everything should be fine, working and squeaky clean!
The ROM is pre-rooted with Magisk and that's pretty cool!
At this point I think my brief tutorial is over. If you find out something important missing or wrong, please point it out! It will help other people! Thank you!
Some links about ADB that I found quite useful:
How to Install TWRP Recovery via Fastboot On Any Android Device
How to Use ADB & Fastboot Commands with your Android Device
ADB Shell
Once again I have to thank the immense patience of BOTAR230 and all the people that worked so hard to make everything possible: I mean the guys (and gals? Maybe, I don't know... ) behind the Resurrection Remix ROM, behind the TWRP project and the Open Gapps and the many more I probably forgot! Thanks everyone!
DaGreatAssyr said:
Hello community!
First of all, I feel I have to apologize to you all since I know I have clogged the forum with a lot of requests of help about upgrading my smartphone... They are scattered all over the place so I have decided to gathered in a definitive one.
Next, I am quite insecure on all the steps so I will try to make a comprehensive list and keep it updated hoping it will help all the Huawei P8 Lite ALICE users that will do the same process I am about to do. Let's proceed!
GOAL: Moving from stock Android 5.0.1 to OpenKirin's MoKee
MY MOBILE: Huawei P8 Lite ALICE (ALE-L21) unbranded single SIM - Build number: BalongC50B311 - Kernel 3.10.61-gcd3fde7 - EMUI 3.1
BOOTLOADER STATUS: unlocked, checked via ADB
Now, the next steps would be to root the mobile. My wild guess are
install TWRP_3.1.1-0_ALICE_BL via ADB
install Magisk to root Android 5.0.1
At this point I am not perfectly sure if those steps are right AND if Magisk is the right choice to root Android 5.0.1 on my mobile. Are there other ways to do that?
Once the device is rooted, the next steps should be:
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed)
install again TWRP_3.1.1-0_ALICE_BL via ADB
install again Magisk to root Android 6.0
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
That's the theory. I've used SR5-SuperSU-v2.82-SYSTEMMODE but it bricked the phone after I updated to Android 6.0 and the user Botar230 told me that it is no longer updated and used and suggested me to use Magisk instead.
The files I have are:
b895_update.zip
open_gapps-arm-7.1-stock-20180626.zip
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
pa_alice-7.3.1-EOL-20180203.zip
TWRP_3.1.1-0_ALICE_BL.img
Previously, I have updated my device to Android 6.0 and installed TWRP 3.1.1-0 and everything went really good. When I tried to root the phone with SuperSU-v2.82, it bricked. Now the phone is restored to its initial conditions, brandless.
I have read THIS POST but it's pretty old and most of the link there are not working anymore.
So, if someone is kindly willingly to give me a hand (yeah, another one, I know... ) on this subject, I'd really appreciate it. Again.
Thanks in advance!
Click to expand...
Click to collapse
I didn't fully understand you, so I'll write a quick guide how to move from stock android 5.0.1 to any other custom ROM (I've read that you already unlocked your bootloader and flashed twrp so I'll skip those two)
First of all, use this version of TWRP.
1. Boot into TWRP
2. Factory reset (Wipe -> Swipe to wipe)
3. Flash B896 update (B895 is fine too)
4. Flash TWRP (Install -> Select image -> Recovery)
5. Flash a custom ROM of your choice
6. Flash Open GAPPS (I recommend flashing NANO version)
7. (Optionally) Flash Magisk if your custom ROM isn't pre-rooted (if unsure, check the root status before flashing)
Fun fact: You don't need to put every file on SD card to flash it. You can also use sideload
Botar230 said:
I didn't fully understand you, so I'll write a quick guide how to move from stock android 5.0.1 to any other custom ROM (I've read that you already unlocked your bootloader and flashed twrp
Click to expand...
Click to collapse
Hello Botar230! At the present time, I only unlocked the bootloader.
No TWRP installed so far.
Thank you for adding some steps I have missed (like the factory reset and the GApps! :good: )!!
The TWRP version I have is the same you suggested me so this is fine!
Yes, now that I think about, nearly all the custom ROM are pre-rooted and there's an option to switch the root in the setting panel but I will check it eventually.
I have make corrections in my list after your suggestion:
install TWRP_3.1.1-0_ALICE_BL via ADB
Factory reset (Wipe -> Swipe to wipe)
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload)
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk
The files I have are:
b895_update.zip
open_gapps-arm-7.1-stock-20180626.zip (I will not use these)
open_gapps-arm-7.1-nano-20180630.zip (I will use these one! )
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
pa_alice-7.3.1-EOL-20180203.zip
TWRP_3.1.1-0_ALICE_BL.img
Everything looks good now. Btw you don't need to flash nano gapps exclusively, it's just a matter of your personal preference which one you choose.
Sent from my LG-K220 using XDA Labs
Botar230 said:
Btw you don't need to flash nano gapps exclusively, it's just a matter of your personal preference which one you choose.
Click to expand...
Click to collapse
To be honest, I don't know what to choose between all the options I have seen on the website. Let's say that if the installation works properly it's a matter of seconds to make a backup and try another Gapp. For the moment I will follow your suggestion.
That's what I have done so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload DONE AND OK!
Everything is working fine so far but I am a little bit nervous about these one. I will take a deep breathe and I will proceed right now. I can flash the ROM and the Gapps with TWRP, right? I am mostly sure about but a confirm could ease my fear of bricking the phone again... :silly:
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk
DaGreatAssyr said:
To be honest, I don't know what to choose between all the options I have seen on the website. Let's say that if the installation works properly it's a matter of seconds to make a backup and try another Gapp. For the moment I will follow your suggestion.
That's what I have done so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideloadDONE AND OK!
Everything is working fine so far but I am a little bit nervous about these one. I will take a deep breathe and I will proceed right now. I can flash the ROM and the Gapps with TWRP, right? I am mostly sure about but a confirm could ease my fear of bricking the phone again... :silly:
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk
Click to expand...
Click to collapse
Yes, everything is correct.
Sent from my LG-K220 using XDA Labs
Botar230 said:
Yes, everything is correct.
Click to expand...
Click to collapse
First of all, thank you for your immense patience!!
That's what happened so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload DONE AND OK!
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin) DONE AND OK!
I had to install the open_gapps-arm64 since the system required the ARM64 but apart that...
Flash open_gapps-arm64-7.1-stock-20180630.zip DONE BUT NOT OK! - I've tried to install the NANO and the STOCK Gapps but every time I got the same error message on TWRP: "failed to mount data: operation not supported on transport endpoint". Google Play and all the Google apps cannot connect: the Google error message is always the same: "couldn't sign in". I've double checked the login and they work both on my PC and on the other phones so I'm sure they are correct. Now I'm searching what kind of error it is but I'm not finding much infos about. Plus, there is the warning message saying that "Google Play services has stopped" and it keeps popping on the screen.
Check whether the ROM is rootable and eventually flash Magisk NOT DONE YET but it seems that it is not pre-rooted.
I am searching the web to understand what's going on here.
It's probably because the custom ROM that you've chosen uses f2fs file system on /data partition instead of ext4. Try to do this:
Boot to TWRP -> Wipe -> Advanced wipe -> Choose Data -> Repair or change file system. From here you can see if the file system of /data is ext4 or f2fs. If it's f2fs, then click Change file system and choose ext4.
Before doing all of this, you should flash b895 again, do a factory reset, flash twrp, flash your custom ROM, change /data file system, and finally gapps so there will be no conflicts between old and new gapps.
Hello again!
Sorry for the silence, got some busy day but here I am.
Before doing what you told me, I've tried to do a backup with TWRP and I've been flooded with error messages:
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to recreate /data/media folder
Unable to mount storage
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to mount /data/media/TWRP/.twrps
And, of course, the backup process failed.
At this point I cannot do anything with TWRP.
I cannot backup, cannot flash a ROM or a ZIP.
The phone works fine, it boots and I got no problems. I can boot it via ADB too.
I'm really scared it will brick or loop sooner or later. I am keeping it turned off and wait for any other advice before proceeding since it would be quite pesky to restart from scratch again....
Following your directions I've seen that the data file system is ext3.
DaGreatAssyr said:
Hello again!
Sorry for the silence, got some busy day but here I am.
Before doing what you told me, I've tried to do a backup with TWRP and I've been flooded with error messages:
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to recreate /data/media folder
Unable to mount storage
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to mount /data/media/TWRP/.twrps
And, of course, the backup process failed.
At this point I cannot do anything with TWRP.
I cannot backup, cannot flash a ROM or a ZIP.
The phone works fine, it boots and I got no problems. I can boot it via ADB too.
I'm really scared it will brick or loop sooner or later. I am keeping it turned off and wait for any other advice before proceeding since it would be quite pesky to restart from scratch again....
Following your directions I've seen that the data file system is ext3.
Click to expand...
Click to collapse
Don't worry, it won't brick. Maybe the internal storage is encrypted. In order to remove encryption, go to Wipe -> Format data.
Hello Botar230! Something funny (in a very positive way) happened! I did as you told me: I booted in recovery mode and went to WIPE -> FORMAT DATA.
Then I considered to install the other ROM I had, RR-N-v5.8.5-20180302-alice-OpenKirin and it has been the best idea I could have!!! :laugh:
After I formatted the data, I rebooted in recovery mode and checked that the problems where all disappeared and they actually did. Then I flashed the OpenKirin ROM and the Nano Gapps you told me.
SURPRISE SURPRISE the OpenKirin ROM is pre-rooted with Magisk 15.3 and the installation, this time, went perfectly fine without any trouble! Plus, Magisk updated to the latest version, the 16!
As I promised, I will now update my first post on how to upgrade my mobile phone hoping it will be useful for someone else but first I want to enjoy my brand new phone!
And, of course, I want to thank you for all the support you gave me in these days! You have been really patient and kind! I am really sorry I cannot help you back since (as you have noticed...) I am not much of an expert so all I can give you is my gratitude and thankfulness! THANK YOU 1000 TIMES BOTAR!! :highfive:
You're welcome. Have a nice day! :highfive:
Sent from my LG-K220 using XDA Labs

lineage 17 on samsung galaxy a20e

there are some instructions how to install twrp or lineage on nnthe samsung galaxy a20e. it took me a while to manage it, for one part because it seems sometime i did not do everything exactly like it was described (old fault of mine...) sometimes i found some explication in another instruction.
this is why i post my experiences, to encourage those who also struggle with problems, don't hesitate, sometimes it only takes a bit longer, but also because some things i still don't understand, maybe somebody can explain me what happened..
naturally, firsty of all i first had to install twrp. so i searched for instructions and found some, including liks to download the twrp.tar for my model. some of them i was able to flash by odin, but when i then restarted the phone it only showed a black screen with some pink in the middle, with some fantasy i could read a slight samsung or samsung a20 in it. this happened when i tried to restart in recovery to flas disable-dm-verity, also when i tried to restart direct to system. with all the attempts i got very experienced in flashin back stock rom...
then i found a working recover after restart to recovery i got my twrp screen and was able to flash the no-dm-verity or magisk.
so next i tried to flash the lineage (unofficial lineage 17.zip) but always got the message invalid zip format. tried to unzip and zip again but no way. so i thought i might get lucky with adb sideload, entered the twrp advanced and clicked adb sideload, the screen told me starting adb sideload but the phone could not be detected by the computer. the computer detected it when switched on or in fastboot, so it seems the sideload did not really start.
so i searched the interenet for roms because i really wanted to get rid of google and a million of apps in the stock that i don't need. i found the links to andyyans gsi and several other zips.
as i was not used to the gsi installation i thought i better stick on what i know and tried to install another zip. but most of the time i got the invalid zip message or the zip is for another phone although i downloaded it for the a20e. but then twrp accepted the crdroid.zip (eureka) i downloaded, i was very happy, after the instalation was finished i restarted the phone and the screen went black, turned off and it seemed not pressing to download, to recovery or to start changed anything. i also tried with pressing vol up, vol down and conecting with computer but also no downloadmode started. so i pressed very long always several buttons and after a while the phone vibrated by pressing long vol down and power, but no screen. after it vibrated sometimes like this i turned to vol up and power, it vibrated again and finally twrp started. although the phopne was fully charged when i started the process, it now had only 8% battery.
so i charged the phone again, flashed the stock rom and twrp to try again to find a solution. at this time i also found an instruction that explained why after flashing twrp the system can't recognize the folders (downloads, music... ) and only gives them combinations of letters and ciffers, i have to decrypt it in twrp, wipe, format data, yes and this problem is solved. i don't know it happens always and who made the instructions to flash twrp thought this is common knowledge but in the first innstructions i read it was not mentioned.
i tried again to flash zips and now got a funny eroor message from twrp, unable to zip, this zip is for a20 but this phone is a a10. i tried another zip, the installation started and in the text i could see that it was for a10... so somehow twrp was sure to live on na a10, how could this be??? i thought maybe the twrp was for the a10 (it was a 3.4.x), so i again downloaded a tar directly from the page of twrp for the a20. but when flashed this twrp (3.5.x) and tried to restart to recovery (or to system) the phone was still in downloadmode and refused the custom rom. i had to flash back to stock, then flash again the twrp3.4 that thought my device is a a10, then i could flash the new twrp3.5 i was sure it was from the original site and for my device. i don't know the 3.4 was patched, i got the downloadlink from one how-to-site, but i did not read anything that it was patched...
but after testing all the zips that did not work, and also with the new twrp i was not able to sideload i decided it is time to learn how to handle the xz. so i extracted first the lineage 18, installed it by clicking install image (after wiping) but again the phone turned black and i had to press a while to get twrp restarted and the battery again was nearly down.
the same process worked with the lineage 17, so this is what is now innstalled. both where the correct ab versions, i checked before with treble info what version i need.
so, can anybody explain me
-what happened with my battery when the phone turned to apparently death?
-why could twrp think my phone is a a10, would a twrp for a10 work on my phone?
-is it possible that the sideload feature does not work on this phone?
¡¡¡and many thanks to all those who upload roms and instructions so people like me can make their phones a bit more like they want them!!!
The first time I flashed my A20e (SM-A202F) had the same problems with finding the right TWRP. I cannot answer your questions, but I can tell you what I do.
Beforhand: unloock the bootloader. Upgrade to the latest Samsung firmware. Download AndyYan's 18.1 LineageOS GSI arm64_bvS. Thought arm64_bvS-vndklite can work as well, I found that bvS has less bugs.
After installing the Samsung drivers and the adb stuff on a PC with Windows, I install Odin and flash with Odin the attached TWRP (AP), while phone is in Download mode.
I then go to recovery (TWRP) and if the folders and files are encrypted, I format, then yes. I wipe 4 things: dalvik, catche, system and data.
I then move the GSI image file inside the zip (not the zip) by drag and drop on my PC. Then in TWRP I click install, select image, not zip, select system and flash. Then I reboot to system.
I never had any problems with this installation process. The bvS has a bug with the Lineage music app, but simply install a local music app, such as Musicolet or AIMP from the Aurora Store (from F-droid).
On the camera side I haven't seen any app that significantly improves photo quality. My recommendation would be FreeDcam from F-droid. Use it on special occasions, as it tends to heat the phone.

Categories

Resources