Database Users

[Q] About Defy+ & CM11

I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS

System + data + cache wipe, use core gapps 2-26. If you encounter issues, then again install rom after full wipe, but don't install gapps immediately. Reboot, and delete unwanted system apps to free up space, and then flash gapps and wipe cache
No easy way to backport safestrap (replacement for boot menu)
Sent from my MB526 using Tapatalk

johnaddams83 said:
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
Click to expand...
Click to collapse
do not use standard gapps..system partition not big enough to store standard gapps..install core gapps

New User - CyanogenMod Questions

Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!

dude...I just got the N6P and ran CM13 within hours. This is what I did...
unlocked the bootloader
downloaded the lastest (MTC19X) image off of https://developers.google.com/android/nexus/images and unpacked it into the C:\Program Files (x86)\Android\android-sdk\platform-tools folder
ran the flash-all.bat
fastbooted TWRP
installed CM13. (didn't wipe internal storage)
installed arm64 open Gapps pico
BAM!!!
right now running stock kernel. it's cool. I'm PrivacyGuard-ing the hell out of all my apps (turned off START AT BOOT and KEEP AWAKE for almost every downloaded app), though, so battery is OK
also using Kernel Adiutor but underclocking values for the CPUs doesn't seem to stick

So it likely worked for you since you had flashed the newest vendor.img first. Apparently there are compatibility issues with certain features that cause them not to work (such as WiFi) if you're using an older one.

chaoticyeshua said:
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
Click to expand...
Click to collapse
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!

kaufikauf said:
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
Click to expand...
Click to collapse
Very much so. I appreciate it!

Has anyone encountered the constant popup of the Select Sim Card message? I'm using project fi and I am still unable to find a solution to this issue.

No keyboard after custom ROM install (bounty!)

I just moved from Pure Nexus 7.1 to SuperXE 8.1. I think I forgot to flash vendor image but otherwise did full clean flash. ROM boots but when trying to connect to WiFi there is voice input but no keyboard. Haven't ever seen something like this before... Added vendor image and redid full/clean flash multiple times with same result. Unfortunately, activity on that ROM thread is a bit slow and I'm down without my phone so decided to ask for help here.

Adding $20 bounty for help fixing. Serious withdrawal mode without my phone. I have a backup phone but it is nearly unusable...

Solution here https://forum.xda-developers.com/showpost.php?p=76126862&postcount=263

Since you are coming from Nougat to Oreo i would suggest you first flash the full oreo factory image before flashing the oreo custom rom. Its not usually a must but solves a lot of minor problems

Is it worth to update from a rooted android 4.2.2 c6603 to higher versions?

Don't ask why I stayed so long on 4.2.2, did PhD and the phone was running nicely and hat no time to update, root again etc. pp. Now that the PhD is finished I wonder if it is worth at all to invest the time to update to higher version. It looks like 5.0 was the last update supported by sony. I don't have a custom ROM, just rooted original Sony firmware with flashtool.
In general I don't see a personal benefit to buy a new phone. Keeping the Z and updating to the best Version or custom ROM running smoothly on the old hardware and which can be rooted is my choice.
Which version and ROM do you suggest?
Thank you for your time and advise

It depends on what you need.
If all you need is a durable battery, then better stay on 4.2.2, but you know...as time goes by, most application will stop their support for jellybean.
If you want more performance, then 5.1.1 is the choice, but not battery friendly. STAMINA mode is present to help saves some battery.
For the best updated OS version, go for LineageOS 14.1. It's based on nougat 7.1.2.

Many thanks, as far as I remember I can do a image with CWM of current system and can give LineageOS a try! I saw now that some modern apps need at least jellybean 4.4 to be installable. Battery shouldn't be a problem, I rather want the camera to work nicely also under a customROM, actually I think the original Sony camera app is quite good and this one I would loose. All other Sony apps I never noticed really. For all the other possible customROM I don't really have the time to study them, camera would be most important. I guess recovering most of the apps from jellybean 4.2.2 to Lineage via Titanium Backup will work so I can check this fast?
Thanks in advance!

You can also try to use RR Oreo if you like the latest Android.
https://forum.xda-developers.com/xperia-z/development/rom-resurrection-remix-o-6-0-0-t3747588
Here what I think about it:
https://mastodon.social/@ahmd_amsyr/99954433452073565

Hmm, I installed lineage 14.1 zip via ROM Manager and it was succesful, but then I also wanted to add directly after this the optional lineage root. The phone was already rooted and unlocked and when pressing the option, the screen went immediatley black. When pressing power button the lamp is short igniting green/red and screen stays black. Installed the newest flashtool and flashtool drivers, but when trying to root or flash the xperia z again via flashtool, it always says in the flashtool log, the driver is too old under Win 7 and Win 10 on 2 PCs. I installed pc companion and additionallly the flashtool drivers.
Do I have to install distinct versions of flashtool and drivers? Flashtool is version 0.9.24...?
I could manage to get it in boot loop now, showing sony logo. But with same flashtool it's not possible to flash ftf in flash or fast boot mode, because it is constantly rebooting. What to do now?
https://forum.xda-developers.com/xperia-z/development/kernel-ub-t3198491
this does not work
https://forum.xda-developers.com/xperia-z/general/disaster-recovery-getting-z1-zu-z-zl-to-t2229250
also doesn't help
Still would like to install lineage.zip again. But how do I get the device booting normally and is the rom manager stil alive? If not I can also flash directly via flashtool a .ftf?

Nevermind, I could repair it, now on 5.1.1 stock.

as someone asked per pm:
I'm also not sure what changed it. I went then to very old flashtool version on my old notebook, probably over 5 years old when I flashed my xperia neo smartphone. With this it worked. Flashtool version is one point. My bootloader was unlocked. The flashing of lineage 7.1.1 also worked, I then made the error to root also via Lineage package directly after flashing the rom, then I was in Boot loop. It's best to start flashing, let flashtool compile the zip, this takes some minutes, progress shown in flashtool, and then you connect via usb smartphone, especially when in boot loop. But start with different flash tool version and post your error messages in the thread i posted. I stil have the old xda tabs in my browser history that helped me to install ics on neo and lollipop on xperia z (and it is really fast again after complete reinstall) no need for new phone

I flashed to LineageOS 7.1.2 and I do not regret it. I have the (almost) latest version on Android. I can manage the apps permissions and it all works great.

Screen problem

Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.

Up :good:

When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.

Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.

Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.

Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !