Lineage os 14.1 for pixel xl - Google Pixel XL Questions & Answers

As the title States. I see a few builds of lineage for our phones. Curious if anyone has tried them out and if so how there running.
Update: Builds are running well. Issues on startup
1- If you can't get pass restoring ftom another device-remove sim to by pass issue...
OK google works. Even with screen off and unplugged
Root is built in
Gapps installed
Edit:
Here is the link to download. Permission granted by invisiblek. Big thanks to him for the builds.Give him credit for everything. Thanks cz for finding info!
http://www.invisiblek.org/roms/lineage-14.1/marlin/
Sent from my Pixel XL using XDA Free mobile app

I can't imagine it's far off from what CM was doing. Does anyone know if it's still heavily CAF?
Sent from my Pixel XL using Tapatalk

Nice to know. Is the pixel actually a supported device?
Where are these builds posted?

Not sure if they're still CAF based. I'd I.agine so since it's still basically cm. I haven't found any topics on em per se just builds. Invisiblek is where to look. There's builds for the marlin
Sent from my Pixel XL using XDA Free mobile app

Didn't realize it was out yet.
Was just about to reflash my DU but will download & try out the Lineage just to see what it looks like.
Consider me your first "thanks" for bringing this to our attention. :up:
Edit. It's booting up right now.
---------- Post added at 02:51 PM ---------- Previous post was at 02:35 PM ----------
I'm not getting far on the 1/14/2017 build of 14.1.
It boots up.
Gives this error which I've seen before and aren't worried about:
"There's an internal problem with your devices"
Then it quickly picks up and connects to my WiFi.
Then quickly enables my Data.
But then drops me into this screen:
"On your other device, open the Google app".
"1) Say Ok Google, set up my device"
"2) Touch Pixel XL on the list, and follow the on-screen instructions"
And I can't get past this.
I think it wants me to restore stuff from my other phone but I can't figure out how to get past this section.
So I can't get to Settings or desktop or anything else.

Lol well "thanks" sir. No problem.Ya wasn't sure if there usable or not yet . I have the 1/14 build downloaded was gonna pull the trigger to see what happens. Perhaps I try 13 build
Sent from my Pixel XL using XDA Free mobile app

CZ Eddie said:
Didn't realize it was out yet.
Was just about to reflash my DU but will download & try out the Lineage just to see what it looks like.
Consider me your first "thanks" for bringing this to our attention. :up:
Edit. It's booting up right now.
---------- Post added at 02:51 PM ---------- Previous post was at 02:35 PM ----------
I'm not getting far on the 1/14/2017 build of 14.1.
It boots up.
Gives this error which I've seen before and aren't worried about:
"There's an internal problem with your devices"
Then it quickly picks up and connects to my WiFi.
Then quickly enables my Data.
But then drops me into this screen:
"On your other device, open the Google app".
"1) Say Ok Google, set up my device"
"2) Touch Pixel XL on the list, and follow the on-screen instructions"
And I can't get past this.
I think it wants me to restore stuff from my other phone but I can't figure out how to get past this section.
So I can't get to Settings or desktop or anything else.
Click to expand...
Click to collapse
Where are these builds located? Lineage isn't doing official builds yet.

CZ Eddie said:
Didn't realize it was out yet.
Was just about to reflash my DU but will download & try out the Lineage just to see what it looks like.
Consider me your first "thanks" for bringing this to our attention. :up:
Edit. It's booting up right now.
---------- Post added at 02:51 PM ---------- Previous post was at 02:35 PM ----------
I'm not getting far on the 1/14/2017 build of 14.1.
It boots up.
Gives this error which I've seen before and aren't worried about:
"There's an internal problem with your devices"
Then it quickly picks up and connects to my WiFi.
Then quickly enables my Data.
But then drops me into this screen:
"On your other device, open the Google app".
"1) Say Ok Google, set up my device"
"2) Touch Pixel XL on the list, and follow the on-screen instructions"
And I can't get past this.
I think it wants me to restore stuff from my other phone but I can't figure out how to get past this section.
So I can't get to Settings or desktop or anything else.
Click to expand...
Click to collapse
I was able to get the 13 build running. i am trying the same on the 14 build to see if itll work on that one as well

Got the 14 build up and running. Seems pretty snappy. Gonna play around a bit to see how it is overall.
Edit:
Seems to be running well. Currently restoring apps. Has cm camera and apps loaded but can get all google apps back including pixel launcher.Pretty well polished as far as i can tell

@CZ Eddie, the "internal problem with your device" is due to an out of date vendor IMG usually. You can reflash the latest vendor.img from the factory IMG to get rid of this message.

Yeah, I knew it was something like that.
But it wanted Q instead of V.
And flashing that didn't resolve my issue where it's stuck at trying to restore from some other device (or whatever that prompt is).
I tried flashing the Q bootloader too and still got stuck.

CZ Eddie said:
Didn't realize it was out yet.
Was just about to reflash my DU but will download & try out the Lineage just to see what it looks like.
Consider me your first "thanks" for bringing this to our attention. :up:
Edit. It's booting up right now.
---------- Post added at 02:51 PM ---------- Previous post was at 02:35 PM ----------
I'm not getting far on the 1/14/2017 build of 14.1.
It boots up.
Gives this error which I've seen before and aren't worried about:
"There's an internal problem with your devices"
Then it quickly picks up and connects to my WiFi.
Then quickly enables my Data.
But then drops me into this screen:
"On your other device, open the Google app".
"1) Say Ok Google, set up my device"
"2) Touch Pixel XL on the list, and follow the on-screen instructions"
And I can't get past this.
I think it wants me to restore stuff from my other phone but I can't figure out how to get past this section.
So I can't get to Settings or desktop or anything else.
Click to expand...
Click to collapse
CZ Eddie said:
Yeah, I knew it was something like that.
But it wanted Q instead of V.
And flashing that didn't resolve my issue where it's stuck at trying to restore from some other device (or whatever that prompt is).
I tried flashing the Q bootloader too and still got stuck.
Click to expand...
Click to collapse
You can get it running. I have it running right now.Very smooth

Sent from my Pixel XL using XDA Free mobile app

tcarave said:
You can get it running. I have it running right now.Very smooth
Click to expand...
Click to collapse
Did you flash TWRP immediately after flashing the ROM?
I did.
Trying something else now and noticed that I somehow now have CM Recovery.
I stared at it for a minute wondering how Clockwork Recovery got installed on my phone till I realized what it actually was. :silly:

Yea I installed TWRP after ROM. Did flashing u vendor IMG get rid of internal error for you? I tried v and still got error but everything seems to be working well
Sent from my Pixel XL using XDA Free mobile app

CZ Eddie said:
Did you flash TWRP immediately after flashing the ROM?
I did.
Trying something else now and noticed that I somehow now have CM Recovery.
I stared at it for a minute wondering how Clockwork Recovery got installed on my phone till I realized what it actually was. :silly:
Click to expand...
Click to collapse
On initial boot don't set wifi. By pass it to get around restore. Wifi will pop up again at end
Sent from my Pixel XL using XDA Free mobile app

tcarave said:
On initial boot don't set wifi. By pass it to get around restore. Wifi will pop up again at end
Click to expand...
Click to collapse
Hah, yeah skipping WiFi setup got me past that restore from other device thing.
I'm logged in now and checking it out.
There are several custom options hidden throughout the menus. Not all packed into one section like AOSP ROM's.
I can't find an option to remove the brightness slider though, I really like that option and would miss it.

npjohnson said:
Where are these builds located? Lineage isn't doing official builds yet.
Click to expand...
Click to collapse
Also curious where these builds are. I tried googling it and nothing came up

Post #4 tells you where to find it.
---------- Post added at 06:33 PM ---------- Previous post was at 06:32 PM ----------
It wants the "Q" vendor image.

Its really smooth and has built in root...only thing I don't like is lack of pixel home button animation and it don't allow unlimited backup but I'm sure those features will become available in the near future (or I hope they will)
Great job with the ROM invisiblek!

Related

WiFi Tether Works w/root

I haven't seen any threads where people were announcing this so I thought I would.
Go here and choose the last build that was released yesterday, December 18th.
http://code.google.com/p/android-wifi-tether/downloads/list
Go there and get the latest WiFi Tether. Make sure you are ROOTED and you choose Galaxy Nexus 4G LTE from the Device Profile menu in Settings in WiFi Tether. It works perfectly.
See attached pictures.
thanks for the link going to give it a try, I have a mifi from work but this might be great to have in case I forget it one day and need access.
Just tried it out and it worked perfectly!
Here is the link to the apk I used. I chose the experimental one, the beta did not work properly.
WiFi Tether for Root Users 3.1-pre110 *** EXPERIMENTAL ***
http://code.google.com/p/android-wifi-tether/downloads/detail?name=wifi_tether_v3_1-pre110.apk&can=2&q=
ty just downloaded that one instead.
Another confirmation that the experimental build works. Thanks!
"Not Rooted?" I'm rooted...
Hey, I just rooted my Galaxy Nexus, and I just grabbed the wifi tether. I tried the Beta 8 first, then the experimental build, but both give me an error message saying that I'm not rooted. I rebooted my phone and I saw the little unlock thinger at the bottom of my screen.
Is this just a bug? Or is something wrong?
Please post in appropriate section and be.sure that it hasnt already been posted like this has thanks
Anybody successfully connecting a tablet and getting it to work? I can't seem to get my ipad2 to connect to it...
using the apk that is in this thread and changed my device to the Nexus LTE... any help would be appreciated.
NotSoSiniSter said:
Hey, I just rooted my Galaxy Nexus, and I just grabbed the wifi tether. I tried the Beta 8 first, then the experimental build, but both give me an error message saying that I'm not rooted. I rebooted my phone and I saw the little unlock thinger at the bottom of my screen.
Is this just a bug? Or is something wrong?
Click to expand...
Click to collapse
To be clear just because you unlocked the bootloader does not mean you are rooted. You should have during the process ran a su.zip from the recovery if you didn't you might want to look in the thread for rooting it.
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
jayhawkfan18 said:
Anybody successfully connecting a tablet and getting it to work? I can't seem to get my ipad2 to connect to it...
using the apk that is in this thread and changed my device to the Nexus LTE... any help would be appreciated.
Click to expand...
Click to collapse
Just got it working fine on my Asus Transformer, only thing I did was enable the security and set my key, other then that its stock on the settings other then changing device to Nexus LTE.
PaulG1488 said:
Please post in appropriate section and be.sure that it hasnt already been posted like this has thanks
Click to expand...
Click to collapse
It is in an appropriate section and I made the thread so it would be straight forward and clear. Unlike all of the previous ones. Title says all. If the moderator(s) feel like it is in the wrong place, they move it. We've been trying to keep the users from saying things like this lately because it just starts fights.
brianhh1230 said:
To be clear just because you unlocked the bootloader does not mean you are rooted. You should have during the process ran a su.zip from the recovery if you didn't you might want to look in the thread for rooting it.
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
Just got it working fine on my Asus Transformer, only thing I did was enable the security and set my key, other then that its stock on the settings other then changing device to Nexus LTE.
Click to expand...
Click to collapse
Thanks! I realized that I didn't finnish rooting. Awesome youtube tutorial, now the **** works.
Thanks for helping the nub.
Thanks OP, been waiting for this one
np glad to help.
my phone had some random restarts when using this wifi tether. Looking forward to CM9 for easier/better built in tether.
you may want to edit your title it is very misleading. this application is not google's it is just on code.google.com. very different. good find though.
Originally Posted by NotSoSiniSter
Hey, I just rooted my Galaxy Nexus, and I just grabbed the wifi tether. I tried the Beta 8 first, then the experimental build, but both give me an error message saying that I'm not rooted. I rebooted my phone and I saw the little unlock thinger at the bottom of my screen.
Is this just a bug? Or is something wrong?
Click to expand...
Click to collapse
To be clear just because you unlocked the bootloader does not mean you are rooted. You should have during the process ran a su.zip from the recovery if you didn't you might want to look in the thread for rooting it.
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
Originally Posted by jayhawkfan18
Anybody successfully connecting a tablet and getting it to work? I can't seem to get my ipad2 to connect to it...
using the apk that is in this thread and changed my device to the Nexus LTE... any help would be appreciated.
Click to expand...
Click to collapse
Just got it working fine on my Asus Transformer, only thing I did was enable the security and set my key, other then that its stock on the settings other then changing device to Nexus LTE.
Click to expand...
Click to collapse
Deleted & reinstalled following your exact steps and it worked that time. A little slow but hey at least it works. Thanks!
Sent from my Galaxy Nexus using Tapatalk
Just installed the latest experimental build and it worked. I wasn't seeing the Wi-Fi SSID on my iPod until I switched to channel 6, but after that it worked. However, about a minute after I stopped tethering my phone randomly rebooted while typing a Google + message. Don't know if they are related. I'm unlocked and rooted using Superboot.
Sent from my Galaxy Nexus using xda premium
Is there any files we need to delete so VZW doesnt know were tethering like we had to do on the DX?
not working lots of errors
Galaxy nexus rooted - installed wifi tether without any issues, however when I start it says it started with errors see log
loading wifi driver done
stopping driver failed
loading wifi firmware failed
starting driver failed
configuring softap failed
activating wifi interface failed
enabling nat rules done
enabling ip forwarding done
tethering now running done
I am running stock with root and my bootloader is unlocked.
---------- Post added at 03:03 PM ---------- Previous post was at 02:53 PM ----------
droid. said:
Galaxy nexus rooted - installed wifi tether without any issues, however when I start it says it started with errors see log
loading wifi driver done
stopping driver failed
loading wifi firmware failed
starting driver failed
configuring softap failed
activating wifi interface failed
enabling nat rules done
enabling ip forwarding done
tethering now running done
I am running stock with root and my bootloader is unlocked.
Click to expand...
Click to collapse
Got it working, downloaded the latest beta and now its working just fine.
FYI, just because the project is hosted on Google doesn't mean this is programmed by them...

Infinite Bootloop

Hey guys,
I've never had any real problems with any android phone that I've had. However, I have been running Liquid Beta 2 on my nexus for over a week now and it seemed to be running great. I did see a few random reboots every now and then but thought that might be due to it being a beta.
Today it seemed to escalate to a new level. I turned on the torch in the pulldown bar and as soon as the light came on the phone restarted. However this time it was never able to start back up. It got about half way through the boot animation and started over and will continuously do this.
I can still boot into recovery so that is good news. I have tried restoring previous roms that I had backed up for just in case and they ran into the exact same problem. I have also tried wiping everything and then installing a fresh rom that I had on my phone and again, ran into the same problem.
At this point I am clueless and really have no idea what to do. If anyone can perhaps share some advice or give some suggestions, that would be great and I would greatly appreciate it. Thanks guys.
edit: Not sure if it matters but I do have the Verizon branded GN.
Make sure you are wiping data, cache and dalvik.
Make sure you didn't get a bad download on the rom you are trying to flash.
I am running stock kernels and have never installed any non stock kernels as stock seems to run just fine. I have wiped everything completely and I've tried two different roms and get the same problem. I don't think it has to do with it being bad downloads. Thank you for the advice though guys. Anyone else have any input? I may just have to go to the verizon store and see if I can exchange it out.
Dude. I had that too some weeks ago and had the problem that I encrypted the phone, which made me not getting into recovery mode. I downloaded a fresh restorer rom from samsung. After everything was fresh I never saw the failure again.
Sent from my Galaxy Nexus using XDA App
murflee33 said:
Hey guys,
I've never had any real problems with any android phone that I've had. However, I have been running Liquid Beta 2 on my nexus for over a week now and it seemed to be running great. I did see a few random reboots every now and then but thought that might be due to it being a beta.
Today it seemed to escalate to a new level. I turned on the torch in the pulldown bar and as soon as the light came on the phone restarted. However this time it was never able to start back up. It got about half way through the boot animation and started over and will continuously do this.
I can still boot into recovery so that is good news. I have tried restoring previous roms that I had backed up for just in case and they ran into the exact same problem. I have also tried wiping everything and then installing a fresh rom that I had on my phone and again, ran into the same problem.
At this point I am clueless and really have no idea what to do. If anyone can perhaps share some advice or give some suggestions, that would be great and I would greatly appreciate it. Thanks guys.
edit: Not sure if it matters but I do have the Verizon branded GN.
Click to expand...
Click to collapse
Flash it back to stock and if it still does this, contact Verizon.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
Geezer Squid said:
Flash it back to stock and if it still does this, contact Verizon.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
Click to expand...
Click to collapse
DO NOT CONTACT VERIZON. After unlocking bootloader, your warranty is voided. Verizon will not be able to help you.
@OP: You can always flash back to stock using stock images provided by google via fastboot with the link Geezer provided.
zephiK said:
DO NOT CONTACT VERIZON. After unlocking bootloader, your warranty is voided. Verizon will not be able to help you.
@OP: You can always flash back to stock using stock images provided by google via fastboot with the link Geezer provided.
Click to expand...
Click to collapse
Not kidding. That link to tells him how to return to stock and re-lock the bootloader.

Q&A for [ROM] [cwm]-BLACKEDITION FOR THE SGS2

Post questions regarding the subject ROM here. If you know the answers, please chime in and help. Ravers has authorized this thread - please use it!
Does anyone want to tell me all the current problem with the ROM so far because I want to see of its worth flashing now or waiting for an update.
Thank You
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Hi folks, is anyone having issues getting this rom to start? I get stuck on the booting "google" icon with moving gears animation. Let it sit for 18 minutes before pulling battery. Below is how I installed:
1. Factory reset.
2. Wiped cache.
3. Wipe dalvik.
4. Ran dark wipe.
5. Ran kernel cleanser
6. Installed this rom's latest release.
I do the above steps for all rom's I've tried and never an issue with booting.
Any suggestions? In meantime, gonna try again. Thanks
Sent from my SAMSUNG-SGH-I727 using xda premium
---------- Post added at 08:22 PM ---------- Previous post was at 07:33 PM ----------
blacksheep242 said:
Hi folks, is anyone having issues getting this rom to start? I get stuck on the booting "google" icon with moving gears animation. Let it sit for 18 minutes before pulling battery. Below is how I installed:
1. Factory reset.
2. Wiped cache.
3. Wipe dalvik.
4. Ran dark wipe.
5. Ran kernel cleanser
6. Installed this rom's latest release.
I do the above steps for all rom's I've tried and never an issue with booting.
Any suggestions? In meantime, gonna try again. Thanks
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Update: tried again and issue persists.
***Will my newly installed CWM Touch have something to do with it?
Thanks
---------- Post added at 09:19 PM ---------- Previous post was at 08:22 PM ----------
blacksheep242 said:
Hi folks, is anyone having issues getting this rom to start? I get stuck on the booting "google" icon with moving gears animation. Let it sit for 18 minutes before pulling battery. Below is how I installed:
1. Factory reset.
2. Wiped cache.
3. Wipe dalvik.
4. Ran dark wipe.
5. Ran kernel cleanser
6. Installed this rom's latest release.
I do the above steps for all rom's I've tried and never an issue with booting.
Any suggestions? In meantime, gonna try again. Thanks
Sent from my SAMSUNG-SGH-I727 using xda premium
---------- Post added at 08:22 PM ---------- Previous post was at 07:33 PM ----------
Update: tried again and issue persists.
***Will my newly installed CWM Touch have something to do with it?
Thanks
Click to expand...
Click to collapse
Final update. Went back to non-Touch recovery and now rom loads no problem. All is well.
Just started this whole rooting thing a few days ago but I've found that using Darkside Super Wipe is pretty useful thing to use before flashing a rom. Here's the link for the wipe and more info about it:
http://forum.xda-developers.com/showthread.php?t=1477955
peconaut said:
Does anyone want to tell me all the current problem with the ROM so far because I want to see of its worth flashing now or waiting for an update.
Thank You
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
A simple answer without knowing what you are able to deal with:
Go with RC8 and flash the theme here: http://forum.xda-developers.com/showthread.php?t=1568128
It will be close to perfect...
BTW: you need to go through the development topic to see all the problems. I think nobody would want to do this for you
Sorry for the possibly-newb question, but does the "Customizable Hardware Keys" mention in the OP mean that I can change my stupid search button into a multitasking one?!?! That would be AMAZING!
Android_Monsters said:
Really enjoying the rom
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I want to flash the new ROM (RC10) how is it in your opinion. For example the cons and pros
Sent from my SAMSUNG-SGH-T989 using XDA
RC9
I know it says that RC 9 is experimental, but according to the bug list it doesn't seem so bad. Anybody have any personal experience with it?
For those wondering about the status of all the experimental versions, I will give you a quick rundown of my personal experience with them as far as ability as a DD is concerned.
RC 8: Good DD after inputting APN settings, didnt come across any errors, everything seems to work, except for receiving mms messages, a few others reported the same problem.
RC 9: I personally never had in call audio working, which was reported by others as well, as a result I reverted back to RC 8.
RC 10: Still early in its development, was released early mainly so RaverX3X could get some logcats on things he could not personally test. audio is not working, data (calling, texting, etc) is not working. Unless your looking to help RaverX3X out with logcats and such i would stick to RC 8 or RC 7 as your DD
RaverX3X or anyone else feel free to add or correct me if I'm wrong or missed something.
Edit: Also I installed all roms with non-touch CWM with no problems.
Mixtzin said:
For those wondering about the status of all the experimental versions, I will give you a quick rundown of my personal experience with them as far as ability as a DD is concerned.
RC 8: Good DD after inputting APN settings, didnt come across any errors, everything seems to work, except for receiving mms messages, a few others reported the same problem.
RC 9: I personally never had in call audio working, which was reported by others as well, as a result I reverted back to RC 8.
RC 10: Still early in its development, was released early mainly so RaverX3X could get some logcats on things he could not personally test. audio is not working, data (calling, texting, etc) is not working. Unless your looking to help RaverX3X out with logcats and such i would stick to RC 8 or RC 7 as your DD
RaverX3X or anyone else feel free to add or correct me if I'm wrong or missed something.
Click to expand...
Click to collapse
Appreciate the feedback.
ImARaptor said:
Sorry for the possibly-newb question, but does the "Customizable Hardware Keys" mention in the OP mean that I can change my stupid search button into a multitasking one?!?! That would be AMAZING!
Click to expand...
Click to collapse
Something tells me this simply means you can turn on the on screen hardware keys, similar to what the Galaxy Nexus has. I have yet to figure out what value this is for a device with these very same keys in hardware already, but some people find it cool. I haven't seen a mod that will allow me to reassign my hardware keys to do something else, but I can hardly claim to have seen them all.
kangelov said:
Something tells me this simply means you can turn on the on screen hardware keys, similar to what the Galaxy Nexus has. I have yet to figure out what value this is for a device with these very same keys in hardware already, but some people find it cool. I haven't seen a mod that will allow me to reassign my hardware keys to do something else, but I can hardly claim to have seen them all.
Click to expand...
Click to collapse
Darn, this makes sense. HOWEVER, if Raver or any other developer wanted to allow us to reassign the hardware keys, that would be much appreciated and I'm sure I wouldn't be the only one to appreciate this, as multitasking takes a little longer than it should. Thanks either way though!
I was wondering if we can run Gideons Script on this ROM? I loved the battery life it gave the last ROM i used. Thanks
suaverc118 said:
I was wondering if we can run Gideons Script on this ROM? I loved the battery life it gave the last ROM i used. Thanks
Click to expand...
Click to collapse
Nandroid and than give it a try.
Device: Samsung Tmobile S2 [SGH-T989]
ROM: BlackEdition RC7 ICS Rom
Radio: TMO UVLC8 Modem
Tweak Script: Newest Supercharger V6 ICS with modified services.jar, KAK, 3G Turbocharger
I was wondering if any of the builds have the people.apk? I like that way better than the regular contact app. I saw in the screen shots that it did have the people.apk but when I downloaded and flashed it did not have it. Thanks in advance.
Hey I was wondering, I just flashed the ChicagoROM. I love it, its very smooth. I have seen there is a link for the Google play store. Sorry i'm to new to post it, I tried. But I heard you just flash this like a ROM, but do you flash on top of the current ROM? I wouldn't think you wipe it before. Is this method the same for the Beats Audio upgrade?
so u know i got 2 people to pm me so ill be sending them copies of a un released build and work with them in getting the last issue fixed once done ill re open the dev thread.
I would strongly recommend reverting to 5.0.2.7 (regular clockwork recovery).
My T989 would not start (on a different ROM) when flash with touch, but 5.0.2.7 worked like a charm.
just a heads up a good friend of mine and decent dev will be takeing over and updateing the project for me.. Sence i just dont have time.. I giving him the sgs2 atm to help finish it i know him in rl so expect updates.
sorry about all the delays and not having time... Rl kicked my arse
setting him up with the latest changes so he can go from there.
Corrupt0387 said:
Hey I was wondering, I just flashed the ChicagoROM. I love it, its very smooth. I have seen there is a link for the Google play store. Sorry i'm to new to post it, I tried. But I heard you just flash this like a ROM, but do you flash on top of the current ROM? I wouldn't think you wipe it before. Is this method the same for the Beats Audio upgrade?
Click to expand...
Click to collapse
Yes, you just go into CWM and choose insttall zip from sdcard. after flashing i reccomend using darkside cache wipe. You can find the download link in the dArkside evolution 3 thread

[Q] Just bought Robin.... God help meh.

I have been without Root.... Without TWRP... Without an unlocked bootloader FOR MONTHS with the S7 Edge (T-Mob) and now I finally have a device with all deez things possible!
I Just got my Robin 2 days ago and I wanted to make this post and say hello to the Robin community, but ALSO wanted to ask my annoying questions right off the bat
(side note) this is the only phone ive ever owned that when I first powered on the device (right after connecting to wifi, but before adding an account) it FORCED me to update, i had no say in it... kinda weird.
ANYWAYS. Was hoping for a little insight. My build number is...
Build # OOWW_1_450
Could someone help me out and point me to the links or guides needed to help get me on the right path to ROOT and TWRP and ROMS, cause jeezus H christ I have missed them
papa bless
Is this the only thread I need for EVERYTHING?
http://forum.xda-developers.com/nextbit-robin/development/tool-robin-toolkit-v1-0-root-twrp-t3375908
Has anyone got xposed on Robin?
yanowman said:
Is this the only thread I need for EVERYTHING?
http://forum.xda-developers.com/nextbit-robin/development/tool-robin-toolkit-v1-0-root-twrp-t3375908
Has anyone got xposed on Robin?
Click to expand...
Click to collapse
Anyone .......?
Hey there! Thanks for getting a Robin. We want to make sure you're on the latest software so that's why you got the OTA to download and install. Now that you are on the latest software, you can download TWRP from the Android Development section, unlock your bootloader, and flash the recovery.
Here
http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171
I notice that the community here is a bit quiet. I would say because of the Nextbit Community Page online is where people ask questions and post topics.
Sent from my Robin using XDA-Developers mobile app
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
Welcome to the community. Great phone for $150 and even less if used.
Sent from my Robin using XDA-Developers mobile app
---------- Post added at 02:11 AM ---------- Previous post was at 02:08 AM ----------
I would be in heaven if Franco did a kernel for this Phone
Sent from my Robin using XDA-Developers mobile app
I used this guide. Got this phone a few weeks ago..
yanowman said:
I have been without Root.... Without TWRP... Without an unlocked bootloader FOR MONTHS with the S7 Edge (T-Mob) and now I finally have a device with all deez things possible!
I Just got my Robin 2 days ago and I wanted to make this post and say hello to the Robin community, but ALSO wanted to ask my annoying questions right off the bat
(side note) this is the only phone ive ever owned that when I first powered on the device (right after connecting to wifi, but before adding an account) it FORCED me to update, i had no say in it... kinda weird.
ANYWAYS. Was hoping for a little insight. My build number is...
Build # OOWW_1_450
Could someone help me out and point me to the links or guides needed to help get me on the right path to ROOT and TWRP and ROMS, cause jeezus H christ I have missed them
papa bless
Click to expand...
Click to collapse
I believe I remember you from the g3. Forgive me if I'm wrong. Welcome to the Robin. Its a great phone and lots of fun.
Sent from my Robin using XDA-Developers mobile app
NOOOOO!!!
Well Fawk....
I recently got rooted and TWRP going and all was well...
I installed the Reserrection Rom and was loving it. NOW HERES MY PROBLEM. I decided to encrypt it. Its really odd, it encrypted it just fine. However when I boot my phone on it asks for my password, I enter it, THAN IT BOOTS UP (I see the reserrection boot screen) than it asks for my password again AND IT WONT TAKE THE PASSWORD, I have tried 100 times... Its NOT the same password, what on earth is going on.....
sabresfan said:
I believe I remember you from the g3. Forgive me if I'm wrong. Welcome to the Robin. Its a great phone and lots of fun.
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
That was mehhhh
HELPPPP
yanowman said:
Well Fawk....
I recently got rooted and TWRP going and all was well...
I installed the Reserrection Rom and was loving it. NOW HERES MY PROBLEM. I decided to encrypt it. Its really odd, it encrypted it just fine. However when I boot my phone on it asks for my password, I enter it, THAN IT BOOTS UP (I see the reserrection boot screen) than it asks for my password again AND IT WONT TAKE THE PASSWORD, I have tried 100 times... Its NOT the same password, what on earth is going on.....
Click to expand...
Click to collapse
This is REALLY weird.... It boots up and than I get my normal black de-crypt screen.. I than enter my password and it ACCEPTS the password and than boots into reserrection (shows the boot animation) than requires me to enter my password again and IT FLAT OUT WONT ACCEPT THE PASSWORD... WTF

Wrong Pin - Issue

Since updating to Pie every once in a while after a reboot the phone wont take my PIN and tells me it's wrong. Rebooting fixes it generally but I'm worried at some point it wont any longer. Has anyone else had this issue?
thenags said:
Since updating to Pie every once in a while after a reboot the phone wont take my PIN and tells me it's wrong. Rebooting fixes it generally but I'm worried at some point it wont any longer. Has anyone else had this issue?
Click to expand...
Click to collapse
Rooted or not? If rooted, what magisk version are you using?
Yes, rooted. I'm using the latest Beta of Magisk due to issues with the stable version. After posting this it happened again so I had to reboot and upon rebooting it started loop booting. I reflashed Pie over itself and that got me out of loop boots and I've already had the wrong pin issue come up again since. I may just wipe today and start fresh.
Sent from my Pixel 2 XL using Tapatalk
thenags said:
Yes, rooted. I'm using the latest Beta of Magisk due to issues with the stable version. After posting this it happened again so I had to reboot and upon rebooting it started loop booting. I reflashed Pie over itself and that got me out of loop boots and I've already had the wrong pin issue come up again since. I may just wipe today and start fresh.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
praveen6585 said:
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I had this issue by rooting with the non-twrp method. I believe it also was caused by not removing all security before rooting...fingerprints and all. Eventually I ended up in the bootloop of death which I recovered only with fastboot flash-all.
I rooted again after all this (needed my substratum) and so far no issues since remembering to disable all security before rooting.
Ya know. I've always removed all security before flashing but read it's no longer necessary and when flashing Pie it was the first time I ever didn't. Wonder if that's related.
Sent from my Pixel 2 XL using Tapatalk
thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Click to expand...
Click to collapse
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Click to expand...
Click to collapse
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Thank you. At the gym right now but will give it a shot when I'm home.
Sent from my Pixel 2 XL using Tapatalk
Does it solve the PIN Incorrect issue in TWRP as well?
JazonX said:
Does it solve the PIN Incorrect issue in TWRP as well?
Click to expand...
Click to collapse
Negative. That's a twrp thing. Which is hit and miss for many. The 3.2.2-0 seems to work better than the 3.2.3-0 version in that regard. However, it's not consistent among all users
Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Just installed it. Hopefully this does it. Thanks for the help :good:
After a sequence of
1 Shutting down the phone
2 rebooting into safe mode
3 shutting down the phone again
and finaly my pin will work.
I believe its something with android P as I had the updated versions of Magisk and TWRP and worked fine on O.
And of course googles solution is to reset everything. That dose not help ever. Only makes me more frustrated.
Holy ____ just got the same issue and was on the verge of resetting. I was able to boot to recovery and sideloaded the Magisk version above, and it fixed the issue! Thanks @Badger50 !
Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
WorldOfJohnboy said:
Holy ____ just got the same issue and was on the verge of resetting. I was able to boot to recovery and sideloaded the Magisk version above, and it fixed the issue! Thanks @Badger50 !
Click to expand...
Click to collapse
Scary as **** the first time, eh? I had just got into bed for the night and was ready to sleep and rebooted my phone for some reason. Bam. Wrong PIN. I was like here we go... gonna be a long night.
praveen6585 said:
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Click to expand...
Click to collapse
This zip makes my phone bootloop. Is there an updated one? I am failing safetynet today, anyone else?
JazonX said:
Does it solve the PIN Incorrect issue in TWRP as well?
Click to expand...
Click to collapse
Badger50 said:
Negative. That's a twrp thing. Which is hit and miss for many. The 3.2.2-0 seems to work better than the 3.2.3-0 version in that regard. However, it's not consistent among all users
Click to expand...
Click to collapse
Try "adb reboot recovery" next time or switch to a custom kernel. This way you should always be able to enter your pin without the freezing/crashing. I'd recommend flashing @nathanchance's Flash Kernel via Franco Kernel Manager. Just flash and forget.
SirVilhelm said:
This zip makes my phone bootloop. Is there an updated one? I am failing safetynet today, anyone else?
Click to expand...
Click to collapse
There is this one..
https://nathanchance.me/downloads/magisk/Magisk-v16.7(1675006)-gbfac1f1bc28b.zip
Safety net failing is a known issue.. topjonwu has made the change in the code but a new version is not out yet with that change
praveen6585 said:
There is this one..
https://nathanchance.me/downloads/magisk/Magisk-v16.7(1675006)-gbfac1f1bc28b.zip
Safety net failing is a known issue.. topjonwu has made the change in the code but a new version is not out yet with that change
Click to expand...
Click to collapse
Boot loop on this one as well. oh well, the stable version doesnt seem to be having issues for me.

Categories

Resources