Related
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.
CyanogenMod and D2VZW: Marshmallow Love!
To Make this easy, I am going to copy a bit of the common sense information Master Cylinder put up for the release of Lollipop, same basics apply here!
Huge thanks to Invisiblek for making these builds for us!
Thanks to Master Cylinder for all the super useful information!
De-unified Marshmallow builds for the Galaxy S3 line. This is for the Verizon variant (SCH-I535) only
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 which is designed to increase performance and reliability over stock Android for your device.
Notes:
Please Use Firmware: VRBMF1
and
Modem/Baseband Version: NE1 (Also, see "Notes - Possible Bugs" section below)
(EDIT: The following statement might not be true. It happened to one user. Unsure about circumstances...)If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
If you know you never took the 4.3 OTA, then you can flash the firmware and modem to your hearts content.
CWM Recovery addicts: Please seriously consider giving up CWM and come on board with what works for sure with 5.1.x and up, TWRP. Problems have been coming up with CWM users so if you have one, that's were to start. Hopefully there's a 12-step program somewhere for y'all
Google apps addon:
Open GApps opengapps.org They have many options for you to choose from based on your needs. Updated daily.
>>>WARNING!!<<< The first time one installs Open GApps, you have to do it with a ROM update (or reinstall current ROM) AND manually wipe the system partition first. Then install the ROM and the GApps normally, then wipe Dalvik and Cache. After that, you can flash them anytime. (More info on Website.) ALSO, for now, don't install Webview as it might not work. There is an "Android System Webview" in the Play Store that will work.
I personally don't use GApps on my Daily Driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Dalvik and Cache, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs!
This page will be a work in progress, so please don't yell if something is missing. I just got the OK to share this with others and wanted to get it out there for you to enjoy. I have been playing with it for the last 24 hours and it is ROCK SOLID in my opinion. I haven't found any issues yet! Daily Driver for me for certain. If you have issues, please post them for discussion below!
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
And without further delay, the link you all want! : http://www.invisiblek.org/roms/cm-13.0/d2vzw/
BUGS:
Need to possibly load a different File Explorer to access SD Card (DoctorImpossible)
Access to camera is not functioning correctly (DoctorImpossible) *EDIT 11-23 build camera works, camcorder fix coming next build!
Outgoing text messages show "not sent", but actually send fine. (Stealth111)
Incoming phone calls do not show caller information (Stealth111)
**When you get your ROM installed and up and running, please be kind and put a small post with information about your install so we can get as much info gathered as possible. (ROM build you installed, Recovery type/version, Clean install, or Dirty (and if dirty, over what version did you flash), what GApps package you installed(exact one please) as well as when you installed it (if on same initial install as ROM, or differently). And lastly maybe the firmware/modem combo you are running. Thanks!
***IMPORTANT INFORMATION*** If you are going to flash to cm-13.0-20151121-UNOFFICIAL-d2vzw or later build, there have been some database changes. InvisibleK has provided a flashable zip file to accommodate nuking your old telephony and settings databases. Nandroid or backup files as needed if you want, as I seem to remember doing this with CM before, and clearing the database wiped texts and call logs I believe. This only needs to be done 1 time, the first time you flash any build from 11-21 on. After you have done this once, you are good to go moving forward, you will be upgraded to the new databases. If you do not flash the "Nuke_It" zip file, you will get phone FC's and a "No SIM Card" error message. So whether upgrading, dirty flashing or whatever, reboot into recovery, flash the ROM, and BEFORE you boot, flash the following zip!
Nuke IT Database Wiper
Profit!
Enjoy!
Stealth111
For Future Use
First
For Future Use
Second
Stealth111 said:
Second
Click to expand...
Click to collapse
First!! To download from here ... I see you've got an OpenGApps link, but it says a patch has to be used. I think I saw it mentioned on a thread somewhere (when I was tracking you to see where you got the build, which didn't lead me anywhere, but then I remembered our old friend invisiblek!)
And thanks a million for starting this thread!!!:good::good::good:
Master Cylinder said:
First!! To download from here ... I see you've got an OpenGApps link, but it says a patch has to be used. I think I saw it mentioned on a thread somewhere (when I was tracking you to see where you got the build, which didn't lead me anywhere, but then I remembered our old friend invisiblek!)
And thanks a million for starting this thread!!!:good::good::good:
Click to expand...
Click to collapse
I personally don't use GApps on my Daily driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Caches, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs! I'll add this bit up-top as well! I don't know anything about a patch though..
Stealth111
Stealth111 said:
I personally don't use GApps on my Daily driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Caches, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs! I'll add this bit up-top as well! I don't know anything about a patch though..
Stealth111
Click to expand...
Click to collapse
Thanks. I also misread the notation at OpenGApps, which said that need a "ROM" with the patch to allow Google services permissions. Also, there are some posts I've found about fixing permissions after boot then reinstalling GApps, but I won't post that here in case it misleads. I'll be the guinea pig as I've dloaded and backed up and ready to jump out the window!
Stealth111 said:
CyanogenMod and D2VZW: Marshmallow Love!
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d..._NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
And without further delay, the link you all want! : http://www.invisiblek.org/roms/cm-13.0/d2vzw/
Enjoy!
Stealth111
Click to expand...
Click to collapse
Hello and thank you for providing us, S3 users, with the chance to try the long awaited Marshmallow ROM.
I downloaded the ROM a minute ago, but unable to download the MF1 firmware and NE1 modem, via link. I keep getting:
Error 404: Server be all like
Am I doing something wrong? If not... What next?
I just finished booting it. It seems pretty nice, and I only noticed a few things. The boot time was around half an hour as usual with lollipop. I did notice that there wasn't any camera app preloaded and I couldn't access my sd card through the file explorer (I chose not to format my sd card as internal and I gave the file explorer root access).
Ghost Protocol said:
Hello and thank you for providing us, S3 users, with the chance to try the long awaited Marshmallow ROM.
I downloaded the ROM a minute ago, but unable to download the MF1 firmware and NE1 modem, via link. I keep getting:
Error 404: Server be all like
Am I doing something wrong? If not... What next?
Click to expand...
Click to collapse
Yes, @Stealth111 you've copied the text from the CM12 OP but that won't work for links EDIT: that are truncated in a post. You have to manually copy the link, ex: right click on the link (if you're using a computer,) copy link location of whatever, and insert it manually.
Here is the working link: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
On another note: I couldn't get my install to function past the first couple of screen in setup. com.android.phone fc avalanche stops all progress. Wiped and installed 3 times with no success. Running NE1 modem (after flashing and booting with ML1 the first time.)
Doctorimpossible said:
It seems pretty nice, and I only noticed a few things. . I did notice that there wasn't any camera app preloaded and I couldn't access my sd card through the file explorer (I chose not to format my sd card as internal and I gave the file explorer root access).
Click to expand...
Click to collapse
I also can't access the camera even after installing a new camera app. A new file explorer took care of my sd card issues however.
@ Master Cylinder, thanks for the heads up on the link, I have fixed it in the OP. For ****s and giggles, trying wiping and installing just the ROM, and then wipe Dalvic and Cache and see how it goes. Maybe a GApps issue. Also, goes without saying, make sure the MD5 from the download matches to verify you got a good DL..
@Doctorimpossible, glad you were able to sort out the access issue. I install ES File Explorer right away, so I didn't notice the issue. Good catch. These are the types of thing we need to sort out as quickly as possible to get this thing rolling! I will say that my initial boot only took about 5 minutes, but again, I did not load ANY GApps.
Master Cylinder said:
Yes, @Stealth111 you've copied the text from the CM12 OP but that won't work for links EDIT: that are truncated in a post. You have to manually copy the link, ex: right click on the link (if you're using a computer,) copy link location of whatever, and insert it manually.
Here is the working link: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
On another note: I couldn't get my install to function past the first couple of screen in setup. com.android.phone fc avalanche stops all progress. Wiped and installed 3 times with no success. Running NE1 modem (after flashing and booting with ML1 the first time.)
Click to expand...
Click to collapse
So is this a hit or miss when flashing or not?
Ghost Protocol said:
So is this a hit or miss when flashing or not?
Click to expand...
Click to collapse
I have installed it on 4 devices myself with no issues. They were all with TWRP 2.8.7.0, clean installs, data wiped, ROM only install, and wiped caches before first boot. DoctorImpossible also has installed it and is up and running. I don't know what GApps he is running (if any). I will add to the OP asking people to put what they did/used for successful installs.
Stealth111 said:
@ Master Cylinder, thanks for the heads up on the link, I have fixed it in the OP. For ****s and giggles, trying wiping and installing just the ROM, and then wipe Dalvic and Cache and see how it goes. Maybe a GApps issue. Also, goes without saying, make sure the MD5 from the download matches to verify you got a good DL..
@Doctorimpossible, glad you were able to sort out the access issue. I install ES File Explorer right away, so I didn't notice the issue. Good catch. These are the types of thing we need to sort out as quickly as possible to get this thing rolling! I will say that my initial boot only took about 5 minutes, but again, I did not load ANY GApps.
Click to expand...
Click to collapse
I tried that just now for the 4th crapout, and there's no MD5 that I can see, but I'm gonna dload the ROM again to my lap and push it over and try again.
Ghost Protocol said:
So is this a hit or miss when flashing or not?
Click to expand...
Click to collapse
Of course! It's the first unofficial build for us.
Stealth111 said:
I have installed it on 4 devices myself with no issues. They were all with TWRP 2.8.7.0, clean installs, data wiped, ROM only install, and wiped caches before first boot. DoctorImpossible also has installed it and is up and running. I don't know what GApps he is running (if any). I will add to the OP asking people to put what they did/used for successful installs.
Click to expand...
Click to collapse
I used the GApps linked in the description with the stock option and flashed using TWRP 2.8.7.0. I rebooted from 5.1.1, factory reset, manually wiped system, flashed the rom, then flashed GApps, wiped the cache, rebooted, rebooted again and flashed xposed (which works by the way!)
Master Cylinder said:
I tried that just now for the 4th crapout, and there's no MD5 that I can see, but I'm gonna dload the ROM again to my lap and push it over and try again.
Of course! It's the first unofficial build for us.
Click to expand...
Click to collapse
Here is the MD5 from my file if it helps!
192BD2F6A83BCA791E0AFE9570134058
Doctorimpossible said:
I used the GApps linked in the description with the stock option and flashed using TWRP 2.8.7.0. I rebooted from 5.1.1, factory reset, manually wiped system, flashed the rom, then flashed GApps, wiped the cache, rebooted, rebooted again and flashed xposed (which works by the way!)
Click to expand...
Click to collapse
Yuppers! Exposed for Android 6
Thanks for the report!
Fingers crossed for Master Cylinder!!
Stealth111 said:
If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
Click to expand...
Click to collapse
how do i know if i have the right one ? it was a while since i rooted and flashed my phone.
thanks.
Sent from my SCH-I535
Jaws4God said:
how do i know if i have the right one ? it was a while since i rooted and flashed my phone.
thanks.
Sent from my SCH-I535
Click to expand...
Click to collapse
There's no way to tell, but you're probably okay. How did you flash your ROM? This is to warn people that the recent post for a procedure to "Downgrade" from their locked bootloader 4.3 OTA that all of us avoided because we were already rooted, etc. This new method has only been around since this summer, so if you have been rooted in the years category, you're probably okay.
Besides, it may even not be a problem if one had done that new method.
Master Cylinder said:
There's no way to tell, but you're probably okay. How did you flash your ROM? This is to warn people that the recent post for a procedure to "Downgrade" from their locked bootloader 4.3 OTA that all of us avoided because we were already rooted, etc. This new method has only been around since this summer, so if you have been rooted in the years category, you're probably okay.
Besides, it may even not be a problem if one had done that new method.
Click to expand...
Click to collapse
all i rememeber was downgrading from h2 to h1 to get root access.. then flashed CM12.1 on top of that ..
Sent from my SCH-I535
Dear ladies and gentlemen,
a couple of weeks ago I decided to switch from SultanROM (latest build from 30th April) to LineageOS 14.1 (nightly build from 5th June 2017). Due to some minor bugfixes I updated to the nightly build from 17th of July. My phone worked well, aside from 2-3 random reboots. But two days a go all of a sudden it hung up. I tried to get it up again with a hard reboot. After a while I realized I was in a bootloop. Of course I tried the first obvious steps to get rid of the bootloop:
Wipe cache (including ART/Dalvik cache)
Flashed the most recent nightly build (2017-07-31) + wipe cache
Factory reset
Updated TWRP from 3.0.2 to 3.1.1
But even then - no chance, I was still hanging in the bootloop. After a few more tries I flashed SultanROM and tried again. Surprise, surprise: it worked perfectly, the phone got almost immediately up!
I'd like to go back to LineageOS, but I don't have a clue how to avoid the bootloop when flashing it again. In the past I flashed other firmwares and images, too (i.e. the 44S and persist.img from this post: https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061). Could this be a problem?
Any help would be appreciated!
grshnckh said:
Dear ladies and gentlemen,
a couple of weeks ago I decided to switch from SultanROM (latest build from 30th April) to LineageOS 14.1 (nightly build from 5th June 2017). Due to some minor bugfixes I updated to the nightly build from 17th of July. My phone worked well, aside from 2-3 random reboots. But two days a go all of a sudden it hung up. I tried to get it up again with a hard reboot. After a while I realized I was in a bootloop. Of course I tried the first obvious steps to get rid of the bootloop:
Wipe cache (including ART/Dalvik cache)
Flashed the most recent nightly build (2017-07-31) + wipe cache
Factory reset
Updated TWRP from 3.0.2 to 3.1.1
But even then - no chance, I was still hanging in the bootloop. After a few more tries I flashed SultanROM and tried again. Surprise, surprise: it worked perfectly, the phone got almost immediately up!
I'd like to go back to LineageOS, but I don't have a clue how to avoid the bootloop when flashing it again. In the past I flashed other firmwares and images, too (i.e. the 44S and persist.img from this post: https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061). Could this be a problem?
Any help would be appreciated!
Click to expand...
Click to collapse
Known issue with latest update of Lineage Os.
Meanwhile you can try latest Unofficial Lineage Os from Sultan.
Mr.Ak said:
Known issue with latest update of Lineage Os.
Meanwhile you can try latest Unofficial Lineage Os from Sultan.
Click to expand...
Click to collapse
Very interesting, thanks! Is there any bugreport or anything else, on which I could track the status?
grshnckh said:
Very interesting, thanks! Is there any bugreport or anything else, on which I could track the status?
Click to expand...
Click to collapse
https://www.cmxlog.com/14.1/bacon/
Mr.Ak said:
https://www.cmxlog.com/14.1/bacon/
Click to expand...
Click to collapse
Thanks, but this is the general changelog for the bacon devices from which I can't say if the bug I'm affected by is already fixed or not. When the issue is a known one, I assume there is some sort of bugreport or discussion going on. Could you provide further information about this bug in particular? Would highly appreciate!
grshnckh said:
Thanks, but this is the general changelog for the bacon devices from which I can't say if the bug I'm affected by is already fixed or not. When the issue is a known one, I assume there is some sort of bugreport or discussion going on. Could you provide further information about this bug in particular? Would highly appreciate!
Click to expand...
Click to collapse
Maybe follow the lineage os discussion thread:https://www.google.co.in/amp/s/foru...iscussion-lineageos-cyanogenmod-t3526394/amp/
Mr.Ak said:
Maybe follow the lineage os discussion thread:https://www.google.co.in/amp/s/foru...iscussion-lineageos-cyanogenmod-t3526394/amp/
Click to expand...
Click to collapse
Are you refering to this one: https://forum.xda-developers.com/showpost.php?p=72344415&postcount=942?
grshnckh said:
Are you refering to this one: https://forum.xda-developers.com/showpost.php?p=72344415&postcount=942?
Click to expand...
Click to collapse
Yes but the whole thread not just a single post.
Mr.Ak said:
Yes but the whole thread not just a single post.
Click to expand...
Click to collapse
Most of the outlined problems are about random reboots and a crashing camera (I read back to page 93). But my problem is: LineageOS 14.1 doesn't even start anymore - after wiping everything, flashing the newest nightly and doing a factory reset.
grshnckh said:
Most of the outlined problems are about random reboots and a crashing camera (I read back to page 93). But my problem is: LineageOS 14.1 doesn't even start anymore - after wiping everything, flashing the newest nightly and doing a factory reset.
Click to expand...
Click to collapse
Well,you can post your issues there or move on to unofficial lineage os by @idprophecy or sultan.
Sent from my A0001 using Tapatalk
I am too facing this issue. Did you get it working @grshnckh ?
CedArctic said:
I am too facing this issue. Did you get it working @grshnckh ?
Click to expand...
Click to collapse
Unfortunately not. I still stick to SultanROM as a temporarily solution, altough I'd prefer to use LineageOS 14.1 again. Which build have you tried?
grshnckh said:
Unfortunately not. I still stick to SultanROM as a temporarily solution, altough I'd prefer to use LineageOS 14.1 again. Which build have you tried?
Click to expand...
Click to collapse
I flashed various builds with no success. What did seem to work is sultanized ROMs, I flashed Sultanized RR and it booted up fine and it was actually pretty good. Just a bit ago I went on a flashing adventure to go and flash AOSPA 7.2.1 but that ended up badly with a bootloop and a broken recovery. I was forced to download WugFresh's toolkit and fix the softbrick (lost all data in the process beware), I am currently on stock CM12.1 and I'm going to flash to AOSPA probably after the boot has finished up.
CedArctic said:
I flashed various builds with no success. What did seem to work is sultanized ROMs, I flashed Sultanized RR and it booted up fine and it was actually pretty good. Just a bit ago I went on a flashing adventure to go and flash AOSPA 7.2.1 but that ended up badly with a bootloop and a broken recovery. I was forced to download WugFresh's toolkit and fix the softbrick (lost all data in the process beware), I am currently on stock CM12.1 and I'm going to flash to AOSPA probably after the boot has finished up.
Click to expand...
Click to collapse
So WugFresh's toolkit did the trick for you? Do you intent to flash LineageOS afterwards again?
grshnckh said:
So WugFresh's toolkit did the trick for you? Do you intent to flash LineageOS afterwards again?
Click to expand...
Click to collapse
Don't think I'm going back to Lineage, RR for me is better (Sultanized or not version). For now I think I'm going to stay on AOSPA. If you try WugFresh's stock flashing tool I urge you to backup all your data.
CedArctic said:
Don't think I'm going back to Lineage, RR for me is better (Sultanized or not version). For now I think I'm going to stay on AOSPA. If you try WugFresh's stock flashing tool I urge you to backup all your data.
Click to expand...
Click to collapse
Thanks for your advice. I already lost everything while trying to get back to LineageOS the last time. Fortunately I had up to date backups.
Have you flashed any ROMs or other stuff before that could cause the problems?
No, not really. I had this issue (meaning that I couldn't change to another non Sultan ROM) for a while now but chose to ignore it. Today I flashed multirom on top of Sultanized RR but I don't think that made any difference, when I flashed to AOSPA everything went South.
CedArctic said:
No, not really. I had this issue (meaning that I couldn't change to another non Sultan ROM) for a while now but chose to ignore it. Today I flashed multirom on top of Sultanized RR but I don't think that made any difference, when I flashed to AOSPA everything went South.
Click to expand...
Click to collapse
I tried several modems a few weeks back, but I'm not sure if this could be the reason.
grshnckh said:
I tried several modems a few weeks back, but I'm not sure if this could be the reason.
Click to expand...
Click to collapse
I originally suspected the firmware as well, turns out that probably wasn't the case, but I am now also now suspecting that the ROMs I tried to flash weren't f2fs compatible and it wasn't sultan's fault after all.
CedArctic said:
I originally suspected the firmware as well, turns out that probably wasn't the case, but I am now also now suspecting that the ROMs I tried to flash weren't f2fs compatible and it wasn't sultan's fault after all.
Click to expand...
Click to collapse
I read about a similar issue: https://forum.xda-developers.com/showpost.php?p=69837921&postcount=3
Highly would appreciate when you keep us up to date here. Good luck!
I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?
Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.
Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?
I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?
BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.
When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??
BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.
I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.
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?