Related
Hi guys!
Recently i buy this Photon Q 4G LTE Sprint to my wife's birthday.
It's a wonderfull device with a nice hardware, but the best is the external keyboard (She likes it, because his old device was Motorola dextr, and she was used to), but we're from brazil and my first difficulty was to find a rom that support drivers without bugs.
So here i was: My first try was MIUI. I unlocked my bootloader, rooted and installed TRWP. Didi Backup, formated and installed MIUI, :good:
First i tryed with Kernell the UFO developed for it, and the device don't boot. After i tryed just the rom, but it has no modem or wifi. So i flashed up the stock rom modem img and worked fine.
But apks like "retrica" doesn't work with it, bringing black photos and others apks made for instragram. I love this rom and i have installed in my Xperia Play. It works perfect, but in this device have a lot of bugs, so i give up.
I know how to use it with bugs, but not my wife. Then i had to try another one.
I downloaded Cyanogenmod CM10.1, CM10.2, CM11 nightly, snapshot. Then after try all "Xt897" roms, i tryed all "moto_msm8960".
I can't get in any of this roms make my wifi or 3G work. I believe that modem is not compatible. Even if i tryed to flashed stock modem after, i still had no signal at all. No IMEI, no MAC Address, nothing. :crying:
This device have few alternative roms, so i decided try to translate the rom with less bugs at all. I picked up the stock rom JellyBeans 4.1.2, but this was my second failure. A language patch is something that you don't find in market, and to disassembly entire rom and work in a translate is something beyond my knowledges.
So i have an answer to someone that know how to do a fix patch to wifi in cyanogenmod(Specific "cm-11-20140518-NIGHTLY-moto_msm8960.zip" ), or someone good in translate rom, or input a language in stocked rom, like The Solutor did in " [Full ICS ROM] Multilanguage/Toggle2g /STK/Tethering" (but the rom he used was 4.0.4 and it have bugs).
I will be grateful for any help. :fingers-crossed:
Hmm, what's the language you want (CM11 already have lots of them - not in the list?), and what WiFi/3G problem are you having? And you also failed to RSD the phone back to stock?
My recommendation is you first sort the RSD thing out and get the phone back to stock 4.1.2, and flash everything from that onwards. Assuming that you don't do anything wrong in the process, you should have no quirks with WiFi/3G.
Sent from Google Nexus 4 @ CM11
Try MoreLocale2 for the stock ROM language issues.
As for the CM issues... I agree with Andy, if it works in stock form, it "should" work on CM - at least that has been my experience.
You are clean wiping / factory resetting before or after flashing CM yes? I see you have done this step for MIUI, so I am thinking that you have already done this step...
If you have, can you provide logs from CM if the wiping/RSD'ing doesn't work?
Thx for help guys...
AndyYan - The language i need is Portuguese(Brasil) and it has on CM 11 and MIUI.
I did it as you said. I downloaded stock from here:
http://sbf.droid-developers.org/phone.php?device=3
Rom version: Android 4.1.2 - Blur_Version.98.10.5.XT897.Sprint.en.US)
And flashed by RSD.
Everything ok till here. No errors, nothing wrong. Wifi working as well, and the network.
My MIUI was taken from here: http://forum.xda-developers.com/showthread.php?t=2444449 (GSM one).
Cool rom, it has wifi and network, but camera bugs with some apks. For me ok, but not for my wife. So this rom was discarded.
CM i dwonloaded from here: http://download.cyanogenmod.org/?device=moto_msm8960
The last one was: cm-11-20140521-NIGHTLY-moto_msm8960.zip (i tryed all of then "XT897" and "moto_msm8960", but none of them could get my network working. No wifi, no IMEI, no MAC, no wifi).
CM was my hope, because it has my language, but in all tries i did the wipe in cache, dalvik, system, factory, even internal memory, before installing, and cache or dalvik after flash. I tried this in all (tried not wiping too) and still has no modem.
After this, just for try, i flashed stock modem "NON-HLOS.bin". Still got no modem in any CM roms.
arrrghhh - i did try "MoreLocale2" for the stock rom, and "Set Locale and Language" (and more). This softwares did a nice job for keyboards and apks, but system stays intact in english. It need to be a real translation for my wife.
My guess is that this issue can be easily solved.
If all JB roms have the same system(at least for "moto_msm8960" processor kind ).
This ROM is generic for Motorola Atrix HD, Electrify M, Photon Q, RAZR HD, and RAZR M right?
Razr HD is a type of phone that came to my country.
Is it possible compile a system from Brasil career stock, for this phone with modem and anything else from my stock rom? Does it will crash my phone?
Please provide logs from the latest build of CM after booting and attempting to engage/connect to wifi.
Logs??
Sotty about my doubt, but i don't know what kind of logs do you want(i'm not used to).
Logs from TWRP in instalation?
This is easy. Installation was made with no errors and succesfully.
Does CM made logs itself??
If does, i dont know how to get them. Please send me a link.
Skymidt said:
Sotty about my doubt, but i don't know what kind of logs do you want(i'm not used to).
Logs from TWRP in instalation?
This is easy. Installation was made with no errors and succesfully.
Does CM made logs itself??
If does, i dont know how to get them. Please send me a link.
Click to expand...
Click to collapse
CM does create logs. If you're not familiar with them, the easiest way is to use an app from the Play Store... which I'm not sure how you will manage without wifi or mobile data, and I assume you are not familiar with adb.
I can go thru the detail, but it's a bit involved. Perhaps this thread will help you?
Once you know how adb works, there's actually an easier method than using adb logcat to output to a file - there are logs stored in '/data/logger'. So:
Code:
adb root
So you can have the permissions to pull the files, then pull them:
Code:
adb pull /data/logger
Will pull all of the log files to wherever your command prompt is. If you 'cd' (change directory) to your desktop, doing the adb pull will send all the log files to your desktop.
Let me know if you have any questions, good luck.
Logs from Adb
Yeap! I'm familiar with ADB!!
(i'm not expert in it, but i already did something with that...)
I don't know exactly what are you lookin for, so i did two logs.
First a complete boot:
Code:
adb reboot system
adb logcat -v long > boot_log.txt
And one for especific modem log from boot
Code:
adb reboot system
adb logcat WifiStateMachine:E *:S -v long > just_wifi_error.txt
(I believe this this won't help u a lot?!)
The first one is the most complete solution for this and have all the boot infos, errors and other things.
If am i wrong please say the correct command to use.
I forgot something...
In filemanager i can't access internal storage.
It shows /storage/emulated/0, and points to nothing.
If i'm right, this was a well know bug on CM 10.2, which supposedly been fixed in CM 11 right?!
I think that information can help to solve this bug...
Please try the adb pull command I sent... Those logs are not very helpful, and quite difficult to read.
However, I have a feeling if you use RSD Lite to flash everything back stock, confirm it works, then start with the latest CM, I'd be curious if it works.
Also, someone mentioned they needed to install the CM10.2 snapshot before going to CM11 - or else BT and wifi did not work.
Eureca...
That is something that i didn't tried! I'd never flashed CM 10 in first!!!
I'm downloading "cm-10.2-20131102-SNAPSHOT-M1-xt897.zip ".
Fisrt i'll flash stock "Blur_Version.98.10.5.XT897.Sprint.en.US" with RSD.
Then fastboot "logo.bin" (to avoid warning unlocked), and TRWP(my stock have a original recovery that can't install CM. I can edit XML, but to cleanse my conscience i'll let this way).
After i'll install "cm-10.2-20131102-SNAPSHOT-M1-xt897.zip" with TRWP and boot with this one.
Then i'll flash "cm-11-20140526-NIGHTLY-moto_msm8960.zip ".
But i'll have to do this at night(it's 12pm here), because i'm working today.
If that don't work i'll pull the log that you said here, but I come back to thank.
Same problem
I confess I was hopeful in that case you said to flash first the CM 10.2.
But again failed. I tried two ways:
In both I tried to install the Snapshot CM 10.2, then the CM 11.
There is no way that cell boot with "CM 10.2" in any case. That saty on boot animation for several time(i waited 30 minutos each).
In the first I downgraded to version 4.0.4 stock to see if the modem worked.
After that i flashed CM 10.2 that stood in boot animation, then CM 11 booted without modem signal (no wi-fi, no signal).
I taked the log for that version (attachment named log_4.0.4.7z)
On the second attempt, I used the default stock 4.1.2.
After CM 10.2 which was stucked on boot animation again, then CM 11 again booted without modem signal (no wi-fi, no signal).
I taked the log for that version (attachment named log_4.1.2.7z)
Strange thing happened on both CM 11 boot. When the system's load, it shows a message "The clock stopped". This is strange thing for me.
Can you wait for CM10.2 to boot...? There is a fsck process which sometimes takes quite a long time to boot.
Also, for your FC issue - you are clean flashing the ROM everytime? You are doing a factory reset everytime you flash a new ROM?
Edit - looking at your logs, I don't think the fsck is the issue... something is causing the CM10.2 boot to die over and over. Please try clean flashing...
I clean everything before.
Yeap. What do you call a clean flashing?
Everytime i flash some ROM, i do factory reset, clean cache and dalvik.
The ROM is flashed on a clean state of the stock one. Is this the clean you are talking about?
CM was taken about 30 minutes to boot, and yet don't load system.
This is why i stop that and flash CM 11 over it.
Is this time bigger than that? How long your cell take to boot this CM 10.2?
Skymidt said:
Yeap. What do you call a clean flashing?
Everytime i flash some ROM, i do factory reset, clean cache and dalvik.
The ROM is flashed on a clean state of the stock one. Is this the clean you are talking about?
CM was taken about 30 minutes to boot, and yet don't load system.
This is why i stop that and flash CM 11 over it.
Is this time bigger than that? How long your cell take to boot this CM 10.2?
Click to expand...
Click to collapse
Yes, factory reset == clean flash.
As for the long boot, I'm not sure the fsck is your issue - basically there is a process which runs a disk check, and sometimes this will make the boot take quite longer than usual. I can't say how long, I've never personally experienced the issue.
However, the fact that CM10.2 isn't booting is a little disturbing. I've heard some people report 45-60 mins... can you do me a favor, charge up the phone, and try to let it boot for at least 90 minutes?
If at the 90min mark it still hasn't booted, pull logs and post them.
Thanks.
The logs contain references to apps that are present only in stock firmware.
That means the CM boot is actually not happening in a clean environment (the data wipe/factory reset in TWRP hasn't worked as it should?).
Please try to use OpenRecovery 2.09 instead of TWRP (as OR is the recovery I personally use and watch for possible bugs) to wipe the device and to install CM11 - http://forum.xda-developers.com/showthread.php?t=2211579&page=10
When installing CM in recovery, you will probably also want to install the gapps package - http://wiki.cyanogenmod.org/w/Google_Apps
Btw., CM11 expects the baseband (modem) and other partitions the be at the 4.1.2 stock level. Experiments with 4.0.4 are useless.
Please post the logs from CM11 boot.
You will need to enable the logger under CM11 by
Code:
su
setprop persist.log.aplogd.enable 1
in Terminal app or ADB shell, it's not enabled on CM11 by default.
Links are broken
Hi... My TRWP version is "openrecovery-twrp-2.7.0.1-asanti_c.img".
Something is not ok with this one. Sometimes this one format the cache, sometimes not.
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
I want to install this one that you said, but those links in the post you sent are broken.
Can you please send me another one?
Skymidt said:
Hi... My TRWP version is "openrecovery-twrp-2.7.0.1-asanti_c.img".
Something is not ok with this one. Sometimes this one format the cache, sometimes not.
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
I want to install this one that you said, but those links in the post you sent are broken.
Can you please send me another one?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=48551561&postcount=75
I'm on an older version of TWRP, and it has never failed me... that's a shame really. I'll try to update and see what's what. In the meantime, flash OpenRecovery I linked above ^^.
Skymidt said:
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
Click to expand...
Click to collapse
TWRP 2.6.3.x should also work properly.
@arrrghhh, so you see it's not just me having the "wiping /data reboots the recovery" problem... I've already sold my PQ (might buy a new one in the future), but please do help let this problem be known to whoever's developing TWRP for us
Sent from Google Nexus 4 @ CM11
I can't believe it works
Unbelievable! :laugh:
This very simple solution worked for me.
My TRWP did not work right.
He said he had done successfully in cleaning the cache and manufactures, but did not.
I downloaded the link you guys sent me and it worked on the first try.
Not needed before installing CM 10.2. Already installed in the first CM 11, has worked with modem and everything. Now I can configure the GSM network my country and language of the country for my wife (PR-BR).
I want to thank the efforts of user @ AndyYan to respond, the attention given by the user @ Arrrghhh teaching me with patience, and the solution given by the user @ kabaldan. :victory:
You are awesome for this forum. Thanks for everything.
If you still want the log I get, but I think with everything working, you guys should already know the outcome.
Q&A for [ROM][4.4.4][AOSPA] ParanoidAndroid 4.6-beta4 | Skyrocket
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
"Security" crashes while triying to change screenlock settings
HTML:
In: [ROM][4.4.4][AOSPA] ParanoidAndroid 4.6-beta4 "Security" crashes while triying to change screenlock settings.
I just want to disable it. ¿Someone knows how to do so by coding?
Thanks!
he;lp
I can't seem to get this ROM to flash. The flash process fails quickly with a non-descript error message:
error executing update binary in zip
error flashing zip
Click to expand...
Click to collapse
I'm using TWRP 2.8.1.0 and I tried flashing the latest nightly as well as the stable version. I verified the MD5 signature after copying the .zip to my SD card. I also did a full wipe with TWRP.
My phone is the i727R with Gingerbread 2.3.5. Do I need to update to the latest official 4.x firmware from Rogers before I try to flash with AOSPA?
Any other suggestions or hints? This is my first time trying to flash a custom ROM, so I'm probably doing something wrong.
Figured it out, didn't have the latest radio installed. Might want to add that to the instructions for noobs like me. It's easy to overlook because the note regarding the firmware is under the "contributors" heading, separate from the basic instructions.
camera doesn't work
Camera is not working for me, but everything else is fine. And pretty darn smooth!
Issue installing
I am attempting to install this using CWM and the installation of the ROM goes perfectly but then when I go to install the GApps, I keep getting the insufficient space error. I have tried Mini, Micro and Nano as well as reformatted the internal memory. Thoughts? Sorry for the ignorant post.
---------- Post added at 05:55 PM ---------- Previous post was at 05:49 PM ----------
harrisd23 said:
I am attempting to install this using CWM and the installation of the ROM goes perfectly but then when I go to install the GApps, I keep getting the insufficient space error. I have tried Mini, Micro and Nano as well as reformatted the internal memory. Thoughts? Sorry for the ignorant post.
Click to expand...
Click to collapse
To be clear, I am talking about the 5.0.2 ROM not the 4.4.4 ROM. The 5.0 thread would not let me post there and redirected me here for some reason.
harrisd23 said:
I am attempting to install this using CWM and the installation of the ROM goes perfectly but then when I go to install the GApps, I keep getting the insufficient space error. I have tried Mini, Micro and Nano as well as reformatted the internal memory. Thoughts? Sorry for the ignorant post.
---------- Post added at 05:55 PM ---------- Previous post was at 05:49 PM ----------
To be clear, I am talking about the 5.0.2 ROM not the 4.4.4 ROM. The 5.0 thread would not let me post there and redirected me here for some reason.
Click to expand...
Click to collapse
I'm not sure if CWM is compatible with the GApps. I recommend using TWRP instead.
But I have used CWM for GApps for all my ROMs so far and it hasn't been an issue. Why would this be different. My understanding is that it is just a space issue so I am wanting to know if there is a way to get this space issue resolved when even the smallest GApps was still too large (supposedly).
---------- Post added at 02:17 PM ---------- Previous post was at 01:22 PM ----------
harrisd23 said:
But I have used CWM for GApps for all my ROMs so far and it hasn't been an issue. Why would this be different. My understanding is that it is just a space issue so I am wanting to know if there is a way to get this space issue resolved when even the smallest GApps was still too large (supposedly).
Click to expand...
Click to collapse
Also I am now just running Cyanogenmod 5.0 with the exact same GApps and that worked fine. Thoughts?
Different recovery
Why did this rom install cyanogen recovery, this recovery sucks and I cant get to any of my backed up roms because it doesnt give me an option, how the hell do I get back to philz?
Trouble updating
I installed the 1/16/2015 version (PA 5.02) plus nano gapps. Most things seemed to work well, and I like the look and feel, but two or three times I have experienced periods where the battery drains even though connected to a charger. This morning, for example, the phone had been on the charger all night and was fully charged. Without disconnecting it from the charger, I checked my email and then put the phone back down. An hour or so later, the battery showed low 90's percent, even though it showed that it still was plugged in.
Yesterday I tried to update to the 2/2/2015 version. After making a backup with TWRP, I installed the 2/2 zip. I have flashed several ROMS, so I am not a complete noob, but I have never done a zip upgrade without factory reset. The upgrade seemed to succeed, but after booting, I had no gapps and my google accounts were missing. I then tried reflashing the same gapps and the systemUI fix. That got my apps back, more or less, but my google accounts still were missing and my home screen layouts all were lost. I then reverted to my pre-upgrade nandroid backup and tried again, by installing the 2/2 ROM upgrade zip, the gapps, and the systemUI fix all without rebooting in between. As before, after rebooting, my home screens were gone and (I think) my google accounts were gone. (By the way, I use the Google Launcher.)
Is upgrading from the 1/16 to 2/2 supposed to require reinstallation of gapps and adding back of accounts, home screen setups, etc? If it is then such an upgrade is almost as much hassle as a complete, clean install. Can someone tell me how this is supposed to work?
I installed the Lollipop rom (and the UI patch) and am still having "Can't connect to camera" issues. occasionally, rebooting the phone helps, but then if I do something like switch from the back camera to the front, it will stop working again.
Sealy64 said:
I installed the 1/16/2015 version (PA 5.02) plus nano gapps. Most things seemed to work well, and I like the look and feel, but two or three times I have experienced periods where the battery drains even though connected to a charger. This morning, for example, the phone had been on the charger all night and was fully charged. Without disconnecting it from the charger, I checked my email and then put the phone back down. An hour or so later, the battery showed low 90's percent, even though it showed that it still was plugged in.
Yesterday I tried to update to the 2/2/2015 version. After making a backup with TWRP, I installed the 2/2 zip. I have flashed several ROMS, so I am not a complete noob, but I have never done a zip upgrade without factory reset. The upgrade seemed to succeed, but after booting, I had no gapps and my google accounts were missing. I then tried reflashing the same gapps and the systemUI fix. That got my apps back, more or less, but my google accounts still were missing and my home screen layouts all were lost. I then reverted to my pre-upgrade nandroid backup and tried again, by installing the 2/2 ROM upgrade zip, the gapps, and the systemUI fix all without rebooting in between. As before, after rebooting, my home screens were gone and (I think) my google accounts were gone. (By the way, I use the Google Launcher.)
Is upgrading from the 1/16 to 2/2 supposed to require reinstallation of gapps and adding back of accounts, home screen setups, etc? If it is then such an upgrade is almost as much hassle as a complete, clean install. Can someone tell me how this is supposed to work?
Click to expand...
Click to collapse
There are issues with the gapps backup script, so the gapps package should be flashed with every ROM update. The loss of gapps most likely caused your accounts and home screen to be removed.
morallyobjected said:
I installed the Lollipop rom (and the UI patch) and am still having "Can't connect to camera" issues. occasionally, rebooting the phone helps, but then if I do something like switch from the back camera to the front, it will stop working again.
Click to expand...
Click to collapse
This should only happen when using the front facing camera. This will be fixed next update.
Bummer
Losing home screens and accounts every time an update is flashed is a bummer. Putting everything back (accounts, home screens, Power Toggles settings, ...) makes me hesitate to try an update very often.
You say the problem is with gapps. Does this same problem occur with all flavors of ROMs and all flavors of gapps? I ask because my previous experience with installing ROMs has been installation of new ROMs, not updates to one already installed.
Incorrect information in battery monitor - PA 5
I've been using (and generally liking) the PA 5 for several weeks. I have noted, however, that the breakdown of battery usage, as reported by the OS, seems inaccurate. As just one example, yesterday, I started a 15-minute call shortly after unplugging my phone from the charger, with a full battery. At the end of the call, I was down to about 90% battery. That seems reasonable to me, based on past experience. The battery monitor said almost all of my battery consumption was for Cell Standby, though, with only a little consumption assigned to actual phone use. I've seen some other examples where the usage breakdown did not seem right, although I did not document them and do not recall exact details.
Am I correct that this is incorrect behavior? Are others experiencing this (or does anyone pay attention to it), either on this ROM or on other ROMs?
i have the problen in de boot reset
friends have a big problem and installed the rom 5.0.2 and it works wonders but when you restart the system displays the logo of sangsung and giving in black screen help me?
I did the steps correctly install the rom and then gapps and finally the root
sorry for my english..XD
s2 ky i727
cwm6.0.3.3touch_skyrocket
gapps --pa_gapps-modular-micro-5.0.1-20150315-signed
[ROM][5.0.2][AOSPA] ParanoidAndroid 5.0-alpha1 Skyrocket [02-19-15]
jorgx said:
I did the steps correctly install the rom and then gapps and finally the root
sorry for my english..XD
s2 ky i727
cwm6.0.3.3touch_skyrocket
gapps --pa_gapps-modular-micro-5.0.1-20150315-signed
[ROM][5.0.2][AOSPA] ParanoidAndroid 5.0-alpha1 Skyrocket [02-19-15]
Click to expand...
Click to collapse
u didnt follow the steps/instructions. read them again.
wrong recovery
dont root
what is s2 ky i727
should be sgh-i727
vincom said:
u didnt follow the steps/instructions. read them again.
wrong recovery
dont root
what is s2 ky i727
should be sgh-i727
Click to expand...
Click to collapse
excuse my model is s2 sgh-i727 model XD
rom behaved extremely stable the only mistake was that hangs on reboot goes black
you recommend I do?
that recobery should I use?
the gapps and rom are well take?
It is the first time I install this rom.....thank you for your help XD
jorgx said:
excuse my model is s2 sgh-i727 model XD
rom behaved extremely stable the only mistake was that hangs on reboot goes black
you recommend I do?
that recobery should I use?
the gapps and rom are well take?
It is the first time I install this rom.....thank you for your help XD
Click to expand...
Click to collapse
i could tell u but for new users u need to start slow, read, start here READ THIS B4 POSTING | THE MOST Common Questions Answered HERE
Sweep2wake feature
Sir, I have problem with Sweep2wake features. when enabled, after i locked my device. the screen wakes when i press either one of the dedicated buttons. even when i enabled the first & last button to wake. hope you can fix this issue. thank you & more power.
LineageOS 14.1 is a free, community built distribution of Android 7.X (Nougat) which greatly extends the capabilities of your phone.
This is an unofficial build of LineageOS 14.1 for the AT&T HTC One XL.
To hear about the latest updates and changes to LineageOS as a whole, please follow +LineageOS on Google+!
Installation Instructions (These are all required)
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
BACK UP YOUR DATA TO A PC/OTG DRIVE. THIS WILL WIPE EVERYTHING
Flash a custom TWRP recovery that supports the EvitaX scheme and prepare your partitions. (Download from the downloads tab).
Boot to Recovery -> Wipe menu -> Advanced Wipe. Change /system to "FAT" format.
Reboot back into Recovery
Wipe Menu -> choose Format Data -> back to Wipe Menu -> manually wipe /system, /cache, /dalvik
Reboot back into Recovery.
Download the unofficial build from the downloads tab.
Locate 7.X ARM Nano Gapps via a quick Google search.
Install the build and GApps
Huge thanks:
mdmower and jrior001 for doing all the hard work.
XDA:DevDB Information
Lineage 14.1, ROM for the AT&T HTC One X
Contributors
h8rift, mdmower, jrior001
ROM OS Version: 7.x Nougat
ROM Firmware Required: 3.18
Version Information
Status: Testing
Created 2017-03-03
Last Updated 2017-03-03
Please be sure to thoroughly read the instructions to do the partition swapping. This should be nearly identical to jrior001's thread for CyanogenMod 12.1
wow..this device is still alive
hats off
It was my first android ...
paras33 said:
wow..this device is still alive
hats off
It was my first android ...
Click to expand...
Click to collapse
It was my first Android also.
Been waiting for a modern ROM for it...
I think I got it loaded, but can't get thru the setup, due to popups...
com.android.phone has stopped...
google play services has stopped....
"that" has stopped...
"whatever" has stopped.....
Edit: I reinstalled the ROM today, and was able to setup properly. Only quirk so far is a red outline that flashes around the screen occasionally.
great news!
@mdmower - I was following your GitHub notes over the past while, always hoping there would be something which we could use!
Thanks to all involved - I still have and use my evita, but often with an alternate SIM for travel. It is still a very nice phone. I put new batteries in both my evita, and my wife's, and they keep going. But security... That's where LineageOS, and this build, will be crucial.
I need my evita as a daily-driver for the next couple of weeks, so I'll eagerly read the results from others for now. But I have three other devices using unofficial LineageOS builds, and I'm very happy with them.
Thank-you, everyone!
Dnorris55 said:
It was my first Android also.
Been waiting for a modern ROM for it...
I think I got it loaded, but can't get thru the setup, due to popups...
com.android.phone has stopped...
google play services has stopped....
"that" has stopped...
"whatever" has stopped.....
Edit: I reinstalled the ROM today, and was able to setup properly. Only quirk so far is a red outline that flashes around the screen occasionally.
Click to expand...
Click to collapse
how exactly did you reinstall? I just did a series of wipes and reinstall and am still getting force closes like mad. cant properly get the device running/through the setup screen
wlewin said:
how exactly did you reinstall? I just did a series of wipes and reinstall and am still getting force closes like mad. cant properly get the device running/through the setup screen
Click to expand...
Click to collapse
I'm not sure just what worked, because I tried so many things. I even tried flashing the evita-x twrp, but it didn't work, so I reflashed the twrp in the op. At one point, I thought I was really screwed, because the data partition showed a size of 0. Then I re-did the format data (step 6), and was able to install the ROM and get thru the setup.
You might try reflashing the twrp, and repeat step 6.
Also, I installed the ROM by itself, booted and setup.
Then flashed gapps and rebooted.
Then flashed SuperSU.
Sent from my SM-T800 using Tapatalk
h8rift said:
Please be sure to thoroughly read the instructions to do the partition swapping. This should be nearly identical to jrior001's thread for CyanogenMod 12.1
Click to expand...
Click to collapse
Great development on the One XL. Thanks guys for the great work. I managed to install the rom. It however seem unstable and apps taking long to open. Also the red box on the edge of the screen. Will try wipe and reflash and see if there will be an improvement
WOW! Nougat on a Five Year-Old Phone!
Thank you so much. You guys are amazing. I can't believe I'm running Android 7.1 on a five year-old phone. Everything works and is running pretty smooth (except for occasional red border flash).
As things turned out, my good old HTC One X has become my primary phone for the time being. And here I am running Nougat. I guess it says a lot about this phone's build quality that it has lasted so long. My deep appreciation to all the XDA developers and their amazing ROMs, apps and troubleshooting tips that have kept this phone, amazingly, at the forefront of Android development all these years.
Well, I couldn't wait. And the summary: I am thrilled
Here are some notes and observations, while installing lineage-14.1-20170226-UNOFFICIAL-evita.zip:
from within TWRP-3.0.N2-1, device always performs a full system-reboot when selecting "Reboot to Recovery". You have to reboot to fastboot (press-and-hold Vol-Down and Power), then enter recovery from the fastboot menu. Later, from within Lineage OS, you *CAN* reboot to Recovery.
cannot flash this ROM and nanoGapps queued together: insufficient memory. Flash this ROM first, then use TWRP file-manager to delete the ROM .zip. Now, there will be sufficient space to flash nanoGapps.
there are plenty of red-border-flashes during setup, and during regular operation It seems like just about every user-input-event, and maybe even every install-decision-point will produce this. It's actually slower than a "flash" - more like a red-border-blink I doesn't hurt anything, and I suspect this will be ironed-out later.
this ROM doesn't include 'su' (SuperUser). For this installation, I opted to use Lineage's 'addonsu-arm-signed.zip'
My roaming SIM won't work where I am now, but I have input my voip details into the provided dialer, and voip/SIP calls work as they should. I added Yahoo as a CM_WeatherProvider, and now cLock looks and works as expected.
a huge THANKS guys, for bringing this ROM to this point - @h8rift, @mdmower, @jrior001 !
Wow, guys this is great!
Thanks for the hard work.
What can we expect from this? Will it be patched to fix bugs or is this a "one build"?
Also, question for the devs: can one realistically hope to use Nougat on evita as a daily driver or is this device simply too old? I'm on CM12.1 and it's not that smooth. Would switching to Nougat better or worsen the experience?
For current testers: what features are currently working (camera, GPS, etc.)?
Again, hat's off!
Device Encryption busted
Device Encryption does not work.
(to be honest, this seems hit-or-miss with other LineageOS 14.1 ROMs; maybe even more "miss" than "hit" :-O . My Nexus 5 will encypt fine; my Nexus 7 (2012) won't).
Camera Works
I've attached an image OF YOUR QUESTION @Luxoboy to show that the camera works. The (exif??) data that I can see in the LineageOS Gallery app shows reasonable information too.
It doesn't seem to crash, nor have weird colors, for still-photos.
HTH,
WiFi stumbles a bit
OK... During setup, the first inkling of a rough-spot for WiFi showed up (for me): finding and displaying WiFi SSIDs took *forever*... Maybe I even skipped past that, and went back to set up WiFi access after the setup was finished and Lineage OS was fully running.
In actual hand's-on usage, I've found that the WiFi connection is both a bit weaker (fewer bars, doesn't reach as far) and lower-throughput than other devices. Both the 5GHz and 2.4GHz bands work; max throughput on 5GHz was 135Mb/s for me, right next to my 802.11n router (running DD-WRT). It's OK though.
Also during use, I sometimes noticed the WiFi icon, and the Settings -> WiFi progress indicating a drop + renew of the WiFi. Right now, my evita is at home while I'm at work - the phone is charging/sleeping but my Voice-Over-IP SIP provider site shows that the evita isn't registered... I suspect that WiFi isn't working, when it was during breakfast when I was playing with it...
The WiFi is certainly usable, but it does stumble a bit here-and-there, it appears.
Does anyone else experience the same, or something different with WiFi?
Nice! thanks guys! The red flashing border and a little lag is
the only thing I see so far... This is awesome!
wildboarhog0 said:
Nice! thanks guys! The red flashing border and a little lag is
the only thing I see so far... This is awesome!
Click to expand...
Click to collapse
You need to root device(install addonsu-arm-signed.zip from attachment) and then add 2 lines to the end of file /system/build.prop with any root file explorer and reboot it.
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
worked like a charm! Thanks!
No More Red Flashing!
kuF3AR said:
You need to root device(install addonsu-arm-signed.zip from attachment) and then add 2 lines to the end of file /system/build.prop with any root file explorer and reboot it.
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
Click to expand...
Click to collapse
Thanks, this fixed the red border flashing, and also has made the phone seem to run more smoothly. I already flashed the latest (2017) version of SuperSU when I flashed the ROM. I notice your attachment has a different version of SuperSU. Is there a difference between the version in your attachment vs. the latest one on the chainfire website. Thanks for your advice.
shannester said:
Thanks, this fixed the red border flashing, and also has made the phone seem to run more smoothly. I already flashed the latest (2017) version of SuperSU when I flashed the ROM. I notice your attachment has a different version of SuperSU. Is there a difference between the version in your attachment vs. the latest one on the chainfire website. Thanks for your advice.
Click to expand...
Click to collapse
I found this file on the lineageos web site as approach to root their ROMs.
h8rift said:
LineageOS 14.1 is a free, community built distribution of Android 7.X (Nougat) which greatly extends the capabilities of your phone.
This is an unofficial build of LineageOS 14.1 for the AT&T HTC One XL.
To hear about the latest updates and changes to LineageOS as a whole, please follow +LineageOS on Google+!
Installation Instructions (These are all required)
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
BACK UP YOUR DATA TO A PC/OTG DRIVE. THIS WILL WIPE EVERYTHING
Flash a custom TWRP recovery that supports the EvitaX scheme and prepare your partitions. (Download from the downloads tab).
Boot to Recovery -> Wipe menu -> Advanced Wipe. Change /system to "FAT" format.
Reboot back into Recovery
Wipe Menu -> choose Format Data -> back to Wipe Menu -> manually wipe /system, /cache, /dalvik
Reboot back into Recovery.
Download the unofficial build from the downloads tab.
Locate 7.X ARM Nano Gapps via a quick Google search.
Install the build and GApps
Huge thanks:
mdmower and jrior001 for doing all the hard work.
XDA:DevDB Information
Lineage 14.1, ROM for the AT&T HTC One X
Contributors
h8rift, mdmower, jrior001
ROM OS Version: 7.x Nougat
ROM Firmware Required: 3.18
Version Information
Status: Testing
Created 2017-03-03
Last Updated 2017-03-03
Click to expand...
Click to collapse
One x or One XL? Can it work on both?
(My Device's SKU - 65383)
You can find download under the "Downloads" tab on the top left of this thread / post.
Or you can find it at, https://forum.xda-developers.com/devdb/project/?id=22974#downloads
XDA:DevDB Information
[ROM][7.1.2][Ovation][EMMC][UNOFFICIAL] LineageOS 14.1, ROM for the Barnes & Noble Nook HD, HD
Contributors
secretwolf98, LineageOS
Source Code: https://github.com/airend/android/tree/cm-14
ROM OS Version: 7.x Nougat
ROM Firmware Required: TWRP 3.1.1-0 and up
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: LineageOS 14.1
Stable Release Date: 2017-12-16
Created 2017-10-24
Last Updated 2017-10-24
Thanks again, i'm using it now and seems to work properly.
Downloaded and installed perfectly. Running fine - will update later.
Good job thanks
Sent from my BN NookHD+ using Tapatalk
Nemesis1278 said:
Thanks again, i'm using it now and seems to work properly.
Click to expand...
Click to collapse
Your welcome
Tight Git said:
Downloaded and installed perfectly. Running fine - will update later.
Good job thanks
Sent from my BN NookHD+ using Tapatalk
Click to expand...
Click to collapse
Your welcome
Hah, awesome, just dug the Nook up from a drawer and was wondering what to do with it, glad to see I can flash a proper updated OS!
Thanks for all your effort!
BSAB said:
Hah, awesome, just dug the Nook up from a drawer and was wondering what to do with it, glad to see I can flash a proper updated OS!
Thanks for all your effort!
Click to expand...
Click to collapse
Your welcome.
Really great work, thanks secretwolf98! Gave new life to my old Nook HD+, especially with some of my favorite apps starting to no longer support older Android versions. A few issues/questions:
How do I get root? I tried installing the official LineageOS addonsu-14.1-arm.zip as well as amaces' addonsu-14.1-arm-new.zip and they both fail in TWRP with
Code:
ApplyParsedPerms: lsetfilecon of /system/addon.d/51-addonsu.sh to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
Maybe related to the previous if it's an issue with the TWRP I have, but I couldn't find a TWRP 3.1.1-0 zip for Ovation so I just replaced the img in amaces TWRP 3.0.1-0 zip. Is there an actual 3.1.1-0 zip that this ROM requires?
When I select Power Off, my Nook reboots instead and I have to hold down the power button to get it to really shut off. Not a big deal since I rarely power off, but a strange bug.
sur4k said:
Really great work, thanks secretwolf98! Gave new life to my old Nook HD+, especially with some of my favorite apps starting to no longer support older Android versions. A few issues/questions:
How do I get root? I tried installing the official LineageOS addonsu-14.1-arm.zip as well as amaces' addonsu-14.1-arm-new.zip and they both fail in TWRP with
Code:
ApplyParsedPerms: lsetfilecon of /system/addon.d/51-addonsu.sh to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
Maybe related to the previous if it's an issue with the TWRP I have, but I couldn't find a TWRP 3.1.1-0 zip for Ovation so I just replaced the img in amaces TWRP 3.0.1-0 zip. Is there an actual 3.1.1-0 zip that this ROM requires?
When I select Power Off, my Nook reboots instead and I have to hold down the power button to get it to really shut off. Not a big deal since I rarely power off, but a strange bug.
Click to expand...
Click to collapse
Thanks, and your welcome. Install this version, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/239817874034
then install this, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/185013076312
Make sure to install G-Apps before ROOT. I recommend, ARM | 7.1 | Pico, from, http://opengapps.org/
Then I recommend going into system and enabling ROOT. Then play around in the system for about 5 minutes. Do a reboot back into the system. Download, https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
and make sure ROOT is working correctly. If it's working... Reboot into TWRP then wipe the 2 caches in advanced. Install my latest version, https://forum.xda-developers.com/devdb/project/dl/?id=27077
Then wipe the 2 caches again (said above), then reboot into system.... See if you have ROOT in "ROOT Checker". If you have any questions, don't be afraid to ask.
Hey I downloaded the twrp 3.1.1-0 from the official twrp site but it seems bugged, in that it doesn't read internal nor external storage. Where can I download a good version? Should I use a different version?
Nolfer said:
Hey I downloaded the twrp 3.1.1-0 from the official twrp site but it seems bugged, in that it doesn't read internal nor external storage. Where can I download a good version? Should I use a different version?
Click to expand...
Click to collapse
Use the latest ClockWorkMod here, https://forum.xda-developers.com/showthread.php?t=2062613
and install the ROM from there. I had this same problem with my first Nook HD.... I thought it was 100% Hard Bricked... But it is soft bricked. Nook's can get into soft bricks only. So I bought a new nook, and it runs better. The first Nook has been dropped so many times... After just using is for 30 seconds it felt like a oven. It was on stock... Until April-30-2016, after school I went to spend the night at my friend's house and then I used his computer to ROOT it. Bad idea only getting 30 minutes of sleep that night... Because I wanted to finish to install CM 10 on the Nook. Then a day or 2 later I installed CM 11. I was so tired on my birthday the next day. So I would say on May-9-2016 it did the same thing in the recovery like yours. I did own the Nook for like 5 years with stock.
secretwolf98 said:
Thanks, and your welcome. Install this version, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/239817874034
then install this, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/185013076312
Make sure to install G-Apps before ROOT. I recommend, ARM | 7.1 | Pico, from, http://opengapps.org/
Then I recommend going into system and enabling ROOT. Then play around in the system for about 5 minutes. Do a reboot back into the system. Download, https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
and make sure ROOT is working correctly. If it's working... Reboot into TWRP then wipe the 2 caches in advanced. Install my latest version, https://forum.xda-developers.com/devdb/project/dl/?id=27077
Then wipe the 2 caches again (said above), then reboot into system.... See if you have ROOT in "ROOT Checker". If you have any questions, don't be afraid to ask.
Click to expand...
Click to collapse
I tried installing the linked ROM, then gapps, then the linked addonsu and still get the same error. I'm convinced my version of TWRP is the problem. Can I use CWM instead?
sur4k said:
I tried installing the linked ROM, then gapps, then the linked addonsu and still get the same error. I'm convinced my version of TWRP is the problem. Can I use CWM instead?
Click to expand...
Click to collapse
Yes, the latest one.
secretwolf98 said:
Use the latest ClockWorkMod here, https://forum.xda-developers.com/showthread.php?t=2062613
and install the ROM from there. I had this same problem with my first Nook HD.... I thought it was 100% Hard Bricked... But it is soft bricked. Nook's can get into soft bricks only. So I bought a new nook, and it runs better. The first Nook has been dropped so many times... After just using is for 30 seconds it felt like a oven. It was on stock... Until April-30-2016, after school I went to spend the night at my friend's house and then I used his computer to ROOT it. Bad idea only getting 30 minutes of sleep that night... Because I wanted to finish to install CM 10 on the Nook. Then a day or 2 later I installed CM 11. I was so tired on my birthday the next day. So I would say on May-9-2016 it did the same thing in the recovery like yours. I did own the Nook for like 5 years with stock.
Click to expand...
Click to collapse
I solved the problem adb flashing twrp 3.1.0-0 wich worked flawlessly.
I now have another problem. I cannot change the default cfq scheduler for internal storage. Every time I change it the tablet frezes and I have to manually reboot
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
sur4k said:
I tried installing the linked ROM, then gapps, then the linked addonsu and still get the same error. I'm convinced my version of TWRP is the problem. Can I use CWM instead?
Click to expand...
Click to collapse
try flashing 3.1.0-0 TWRP
then go to developer options, disable root and then reenable for apps and adb. Reboot. Let me know
Just like to say thanks for all the work on this rom. My 4 year old Nook HD+ now does everything i need from a tablet
Sent from my SM-G935F using XDA-Developers Legacy app
edsib1 said:
Just like to say thanks for all the work on this rom. My 4 year old Nook HD+ now does everything i need from a tablet
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Your welcome
so far so good, updated both my hd and my hd+, both running smooth. Great job secretwolf98 !!!
zspeciman said:
so far so good, updated both my hd and my hd+, both running smooth. Great job secretwolf98 !!!
Click to expand...
Click to collapse
Thanks and your welcome
will not reboot, stuck at loading screen
xecutionkrk said:
will not reboot, stuck at loading screen
Click to expand...
Click to collapse
clean install, wipe everything, except where you have the ROM at.
So this morning I went to check on lineage OS news oh, and I found out that they released today for all pixels. I am running it with no issues although I would recommend to download the micro gapps package cuz if you do the Nano or anything below it will give you issues with your phone reading SIM card. Aside from that I had successfully running the rom with magisk installed.
Which versions of gapps did you try? Only nano/micro? I was thinking of selecting pico. Also, can you update via their in house ROM updater app while rooted?
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
Which versions of gapps did you try? Only nano/micro? I was thinking of selecting pico. Also, can you update via their in house ROM updater app while rooted?
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Will there still wait to check to see if the updater works but it looks like everything is fully functional within it and right now, take a look at the picture that I'm going to attach to this that is her updater and it looks like it is completely 100% functional but I cannot be sure because there is no updates to test it with.
As far as the gapps go, don't use anything smaller than micro. There is something pixel 4 needs in telephony to work that is in micro+ but not in nano or pico ... If you flash rom without gapps , your phone will work to make calls, if you flash any gapps before micro, you will get a " insert SIM, emergency calls only " message.
After you flash rom, MAKE SURE TO REBOOT AND THEN FLASH GAPPS,! otherwise if you try to do it in the same session that you flashed ramen you will get a message telling you that you have insufficient storage to flash and it will fail to flash gapps!
A few things that I wish and I hope they do fix would be the 90 hertz implementation switch as of now there is no switch for it and the screen flickers at low brightness.
Soli gestures would be great, I know DU has them working so it's a matter of time before lineage does as well.... Same goes with the squeeze for assistant,.... It is also not working ..
Not working :
Soli gestures
Squeeze
Smooth display
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
i42o said:
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
Click to expand...
Click to collapse
Thank you for the detailed response!! I greatly appreciate all the info and I'm sure others will as well!:highfive: I will probably try it when the ROM becomes more stable. Currently on DU myself and I don't mind waiting until the project improves further. Would you mind letting us know in the thread how your first update goes while rooted? Thank you again for trying the legendary ROM and letting us know it was released!
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
Thank you for the detailed response!! I greatly appreciate all the info and I'm sure others will as well!:highfive: I will probably try it when the ROM becomes more stable. Currently on DU myself and I don't mind waiting until the project improves further. Would you mind letting us know in the thread how your first update goes while rooted? Thank you again for trying the legendary ROM and letting us know it was released!
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Yeah, so after I installed it and set it up, I then adb sideloaded magisk canary on its stock kernel, it went thru like knife thru butter.
I then rebooted into android, finalized the magisk set up, rebooted and voila... I was rooted.... I then tried Kiri Kernel, since it has the necessary things for TWRP, flashed it within ex kernel and then tried to boot TWRP in bootloader only to get stuck on TWRP splash screen...
I was honestly trying to have lineage working with a working TWRP but unfortunately it did not work as such. So I gave up on the TWRP and I've been running the ROM with magic and modules installed with no hiccups The boot time is amazing battery life is really really good...
Viper worked first try... This has has to be one of three good roms out there with little to no issues.
DU
PIXEL DUST ( CAF )
LINEAGE
i42o said:
Yeah, so after I installed it and set it up, I then adb sideloaded magisk canary on its stock kernel, it went thru like knife thru butter.
I then rebooted into android, finalized the magisk set up, rebooted and voila... I was rooted.... I then tried Kiri Kernel, since it has the necessary things for TWRP, flashed it within ex kernel and then tried to boot TWRP in bootloader only to get stuck on TWRP splash screen...
I was honestly trying to have lineage working with a working TWRP but unfortunately it did not work as such. So I gave up on the TWRP and I've been running the ROM with magic and modules installed with no hiccups The boot time is amazing battery life is really really good...
Viper worked first try... This has has to be one of three good roms out there with little to no issues.
DU
PIXEL DUST ( CAF )
LINEAGE
Click to expand...
Click to collapse
Is 90hz working??
ahoslc said:
Is 90hz working??
Click to expand...
Click to collapse
Read just one or two more posts above the one you quoted to find your answer.
bradical711 said:
Read just one or two more posts above the one you quoted to find your answer.
Click to expand...
Click to collapse
Smooth display is auto switching between 60hz and 90hz that's why I asked if just 90hz was working
i42o said:
Will there still wait to check to see if the updater works but it looks like everything is fully functional within it and right now, take a look at the picture that I'm going to attach to this that is her updater and it looks like it is completely 100% functional but I cannot be sure because there is no updates to test it with.
As far as the gapps go, don't use anything smaller than micro. There is something pixel 4 needs in telephony to work that is in micro+ but not in nano or pico ... If you flash rom without gapps , your phone will work to make calls, if you flash any gapps before micro, you will get a " insert SIM, emergency calls only " message.
After you flash rom, MAKE SURE TO REBOOT AND THEN FLASH GAPPS,! otherwise if you try to do it in the same session that you flashed ramen you will get a message telling you that you have insufficient storage to flash and it will fail to flash gapps!
A few things that I wish and I hope they do fix would be the 90 hertz implementation switch as of now there is no switch for it and the screen flickers at low brightness.
Soli gestures would be great, I know DU has them working so it's a matter of time before lineage does as well.... Same goes with the squeeze for assistant,.... It is also not working ..
Not working :
Soli gestures
Squeeze
Smooth display
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
Click to expand...
Click to collapse
90hz works, 70% plus brightness on coral gives 90hz, below is 60hz. flame has some different tunings percentage wise, but same concept.
RefreshRate will work as soon as we have an official R image I can steal a single APK from.
We won't be implementing Squeeze or Soli most likely - it's RE, and given scrutiy over large projects and reverse engineered code, we likely won't see it unless it's reimplemented OSS (DU reverse-engineered it, but didn't clean room re-implement).
ahoslc said:
Smooth display is auto switching between 60hz and 90hz that's why I asked if just 90hz was working
Click to expand...
Click to collapse
It works.
ok well i went back to stock aug firmware and then flashed the img file, then sideloaded the rom, rebooted right into recovery and flashed gapps ... stuck on the lineage boot animation .. do i need to let it boot up then reboot into recovery and flash gapps?
tried again, flashed the image then rebooted to start menu, rebooted to recovery and flash mini gapps and rebooted ... still stuck on the boot logo
what am i missing?
somehow i got it to boot and had a trebucket error, installed a different launcher - FIXED.
can not finish setup, keep getting data transfer crash
anyone get TWRP to load? im using fsociety kernel and it worked on another ROM
Madjax2020 said:
ok well i went back to stock aug firmware and then flashed the img file, then sideloaded the rom, rebooted right into recovery and flashed gapps ... stuck on the lineage boot animation .. do i need to let it boot up then reboot into recovery and flash gapps?
tried again, flashed the image then rebooted to start menu, rebooted to recovery and flash mini gapps and rebooted ... still stuck on the boot logo
what am i missing?
somehow i got it to boot and had a trebucket error, installed a different launcher - FIXED.
can not finish setup, keep getting data transfer crash
anyone get TWRP to load? im using fsociety kernel and it worked on another ROM
Click to expand...
Click to collapse
You're going to have to skip that by disabling the app when it force closes . It should let you proceed from there on. TWRP won't work and idk why... Trebuchet launcher will FC as well but since Google home launcher is installed via gapps it should be a fail safe. As far as kernel, I am running kirisakura and it has the necessary things to work with TWRP but I won't. Trust me I tried.... Make sure to root with magisk canary .
To fix cts mismatch in magisk download termux
SU
props
And select option 2 forced basic key attestation
Select y for yes and proceed... Reboot and you should pass safety net checks...
Hit thanks if I helped .. one love
i42o said:
You're going to have to skip that by disabling the app when it force closes . It should let you proceed from there on. TWRP won't work and idk why... Trebuchet launcher will FC as well but since Google home launcher is installed via gapps it should be a fail safe. As far as kernel, I am running kirisakura and it has the necessary things to work with TWRP but I won't. Trust me I tried.... Make sure to root with magisk canary .
To fix cts mismatch in magisk download termux
SU
props
And select option 2 forced basic key attestation
Select y for yes and proceed... Reboot and you should pass safety net checks...
Hit thanks if I helped .. one love
Click to expand...
Click to collapse
thank you sir for the reply. However i could not get it to be stable. The initial setup failed no matter what i tried. The error of data tansfer tool would fail. I want to run this as it seemed very smooth, however i think i need to wait for another update or something. i followed the OP to the t and nothing seemed to work properly for me.
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
npjohnson said:
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
Click to expand...
Click to collapse
I'll try again thanks for the info
Seems the wiki says you can sideload gapps right after sideloading the OS, the OP said doing that causes issues lol. But he'll I'll try it anyway
npjohnson said:
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
Click to expand...
Click to collapse
Got this running great, with gapps. Was wondering if you're getting the issue I am with google assistant. It seems to freeze up and not be usable.
followed the wiki directions and used full gapps not nano ( missed that 1 bit of info ) im STILL getting data tansfer tool keps stopping when trying to finish the setup going to try a reboot and see what happens. it shows just a sec then saying looing for updates then installing updates and crashes ... then back t connect to wifi . does this have to do with the gapps?
SO ODD ... reflashed and used nano. asked to connecto to mobile data, nothing as showing up, hit skip, tried wifi and nada .... hit skip then same damn error for setup .... insane. maybe ill just cancel the setup and do everything manually
retied all steps and got the no space error when doing gapps, switched to slot b and tried again and it worked ... waiting to see the data tansfer error ... i dont think my phone wants to play nice lately, or ever.
went back to stock firmware, loaded the 9/6 lineageos and have NO mobile data with nano gapps loaded. doing the update currently and will update shortly what happens
i can officially state i am up and running with so far NO issues, i have mobile data, wifi sent texts and made a call. now going to root and swiftbackup restore all my apps and blah blah
Anyone tried the new 13th nightly? Hopefully they fixed the screen flicker.
Madjax2020 said:
followed the wiki directions and used full gapps not nano ( missed that 1 bit of info ) im STILL getting data tansfer tool keps stopping when trying to finish the setup going to try a reboot and see what happens. it shows just a sec then saying looing for updates then installing updates and crashes ... then back t connect to wifi . does this have to do with the gapps?
SO ODD ... reflashed and used nano. asked to connecto to mobile data, nothing as showing up, hit skip, tried wifi and nada .... hit skip then same damn error for setup .... insane. maybe ill just cancel the setup and do everything manually
retied all steps and got the no space error when doing gapps, switched to slot b and tried again and it worked ... waiting to see the data tansfer error ... i dont think my phone wants to play nice lately, or ever.
went back to stock firmware, loaded the 9/6 lineageos and have NO mobile data with nano gapps loaded. doing the update currently and will update shortly what happens
i can officially state i am up and running with so far NO issues, i have mobile data, wifi sent texts and made a call. now going to root and swiftbackup restore all my apps and blah blah
Click to expand...
Click to collapse
You do remember I said micro right? I specifically explained that by using nano you would have no cell phone connectivity and upon transfer tool just put no transfer
XMayhem2099 said:
Anyone tried the new 13th nightly? Hopefully they fixed the screen flicker.
Click to expand...
Click to collapse
Yes it is still there but much less now
Face unlock working?