Related
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Have you tried deleting the telephone system app?
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
graphdarnell said:
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.
Click to expand...
Click to collapse
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.
hardslog said:
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.
Click to expand...
Click to collapse
I upgraded to the latest TWRP 2.7.0.1, deleted everything and started from scratch. Everything works great now and using new kernel that clocks to 1.8 is flying.
Hey guys,
So here is a straight from source build of Android L, 5.0. I have not done anything beside build it from source and flash it. I have not done extensive testing on it.
So anyways, here is the link:
http://d-h.st/zi0
I have not included gapps or anything else. They will be coming soon. This build is primarily to play around with. I would not consider this a daily driver.
Issues:
Probably a ton, seeing as I have only checked if it boots.
I am not responsible for any issues this may cause or anything else that may happen to your tablet as a result of this.
I also have a ton of schoolwork and other things that keep popping up, so my support may be iffy. Please bear with me or go back to 4.4.4.
Here is a screenshot for proof:
https://www.dropbox.com/s/lnmhdapeemskggi/1743495_10153594576754572_4551962379003400239_n.jpg?dl=0
Future Plans for this Rom:
GApps are not yet possible on Lollipop as far as I can work out, due to the fact that baksmali and smali do not appear to play nicely with ART odex files. I will be rebuild the rom to be odexed and then including a gapps package.
XDA:DevDB Information
[Android 5.0] Straight from source ROM, ROM for the Nexus 7
Contributors
MidnightNinja
Version Information
Status: Testing
Created 2014-11-05
Last Updated 2014-11-04
Tried to adb side load and am getting No OS error. Will restore and try again on device
Sent from my A0001 using XDA Free mobile app
cchant said:
Tried to adb side load and am getting No OS error. Will restore and try again on device
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm..let me know if you still have issues, because I was able to sideload on my device
Awesome!!
When first booted you need to erase it because it is encrypted. But after that it works (for now) like a charm. Wifi working, sound working.
The only problem so far is that after I installed the Play Store it didn't want to open but the Amazon app store works fine.
Niekhout02 said:
When first booted you need to erase it because it is encrypted. But after that it works (for now) like a charm. Wifi working, sound working.
The only problem so far is that after I installed the Play Store it didn't want to open but the Amazon app store works fine.
Click to expand...
Click to collapse
I am missing alot of the google stuff, which is probably why none of that works
That will come shortly, I just need to redo a lot of my vendor files and such to get gapps to be built in.
It worked even though it said no OS
first boot takes awhile but it works!
Confirmed it works.
Sideloading gapps for cyanogenmod 11 and hoping they auto update does not work. Worth a shot though. Time to reflash.
Woah, thanks a lot
Btw, how do I sideload gapps? (especially play store)
Since I think it won't be just installing apk, isn't it?
Working great! I think performance is even better than kitkat
Wi-Fi also working (maybe bluetooth, nfc and gps too)
StardustGeass said:
Woah, thanks a lot
Btw, how do I sideload gapps? (especially play store)
Since I think it won't be just installing apk, isn't it?
Click to expand...
Click to collapse
Flashing GApps is the solution. Sadly, there isn't a package for Lollipop GApps yet.
tatazeuz said:
Flashing GApps is the solution. Sadly, there isn't a package for Lollipop GApps yet.
Click to expand...
Click to collapse
I am currently working on the gapps, right now i have fixed my own build process and am getting a nexus 9 dump to try and fix it up.
MidnightNinja said:
I am currently working on the gapps, right now i have fixed my own build process and am getting a nexus 9 dump to try and fix it up.
Click to expand...
Click to collapse
Yay!
Works great, now waiting for gapps
thanks
Gapps mostly work fine if you edit updater.script
I've only had issue with the keyboard crashing so I'd suggest removing it from the gapps package before flashing.
Woah
I can't wait for the final version, this one, using 4.4.4 binaries, is crazy smooth. Google outdid theirselves on the optimization department.
Awesome work, think im gonna givebthis a try atbwork tomorrow.
What does work and what doesn't
basuraunak said:
What does work and what doesn't
Click to expand...
Click to collapse
So far, everything seems to be working. Have to check camera yet though.
I cant seem to get much else to go with it, but I will share my findings.
I can get TWRP to install,but then I get a bootloop.
If you use the Nexus Root Toolkit v 1.9.3 and "Root" with custom recovery checked. It freezes after trying to temporarily boot the modified boot image.
Hard reset the tablet and boot normally. The toolkit should reboot your tablet back into the bootloader and into TWRP, but this is only good for one boot.
If you mount /system and run a fix permissions, then it stays installed, but never gets past the boot screen.
It boots far enough to get into ADB.
Not sure what to try next though...
I was thinking if we could get a flashable zip without the stock recovery, then we may be able to keep TWRP, but I am not familiarwith building the flashable zips.
Wait, So how do you flash the google play services after you lose TWRP?! I don't understand..
I was installing the most recent nightly update and after the phone restarted it began to flash on and off, I then rebooted it to try and fix the problem but this only made the phone stay of the cyanogenmod loading screen and will not boot after 20+ mins on this screen. How would I go about fixing this issue?
This is the update I installed: cm-12-20150116-NIGHTLY-bacon
What you need to understand is that "nightly" builds are highly experimental and far from stable. They are actually meant for developers if you ever dare to read the description of them.
Unfortunately you will not likely find much support for nightlies as they are updated daily for the most part. You're either going to have to flash a different rom or wait for the next nightly and try your luck.
Thank you
markbencze said:
What you need to understand is that "nightly" builds are highly experimental and far from stable. They are actually meant for developers if you ever dare to read the description of them.
Unfortunately you will not likely find much support for nightlies as they are updated daily for the most part. You're either going to have to flash a different rom or wait for the next nightly and try your luck.
Thank you
Click to expand...
Click to collapse
Ah okay I understood what I was getting into but here's the weird part, I was successful in adding a new ROM and trying to boot using a stable version of CyanogenMod which again was successful however when I rebooted the phone I got the same issue with it being stuck at the boot screen.
Thank you for your help.
Hi guy,
I have been trying to figure this out for a while now and can't seam to figure it out. Everytime I flash a CAF based ROM after clicking reboot the phone turns off. During this time it is very hard to get the phone to turn back on. Holding the power button does not seam to do anything. I have to hold the power+volup+voldown for around 30 seconds let go and do it again in order to get back into recovery. I am not getting any errors at all when flashing. I really have no clue what it could be. I have tried every CAF based ROM I have come across here and they all do it. The only thing I can come up with is my phone has had the screen, camera, and battery replaced. Could one of these parts or another part be causing a problem that doesn't allow CAF based ROMS to work? I know its a long shot but thats all I can think of at the moment.
Right now I am working on trying to flash CyanogenMod from this thread. I have tried both version 13 and version 14 both have the same problem. This is what I have tried.
Flash HammerheadCAF reboot back into recovery
Flash bootloader&radio_HHZ20h+2.30.zip reboot to recovery
Flash cm-13.0-20161029-UNOFFICIAL-hammerheadcaf.zip
Flash opengapps
Flash SuperSu
Reboot
Black screen of death
What is wrong with this process? I have also tried the same process with cm-14.0-20161029-UNOFFICIAL-hammerheadcaf.zip. I am now going to try this same process with cm-14.1-20161029-UNOFFICIAL-hammerheadcaf.zip. I don't expect any difference though. Anyone have any suggestions?
Thanks,
Rocky
*****Update*****
I have tracked the problem down to CAF TWRP. I have formatted the phone which has removed everything except CAF TWRP and I am still getting the black screen of death situation. When the phone reboots it completely turns off. It will not respond unless I hold down power+volup+voldown for around 30 or 40 seconds. Then the phone will finally enter the bootloader. Are there any other recoveries that will flash CAF based ROMs? I don't know what else to do =(
Maybe don't flash supersu? Cm comes prerooted?
audit13 said:
Maybe don't flash supersu? Cm comes prerooted?
Click to expand...
Click to collapse
Thanks for your reply and time. I also tried flashing without SuperSU and it did the same thing. When I tapped reboot the phone would not turn on. I also tried just flashing the ROM and rebooting. The problem is with TWRP CAF because I have even formatted the phone so there was no ROM just TRWP CAF and when I tapped on reboot to recovery the phone just turned off. The power button wouldn't do anything. It would not even turn the phone on. The only thing I could do was hold the power+voldown+volup for 30 sec let go and press them again and go into bootloader.
Hey guys anyone else have any suggestions? I have tried sending a support ticket to twrp over a week ago. I haven't heard a word from them. I really want to use CAF ROMs
Hi!
I'm facing the same problem. I've been trying everything I can think of, and everything ended with a black screen when trying to boot:
Flashing stock again and then TWRP and CAF.
Flashing a lower version of TWRP (2.8.7.0) and then flashing CAF.
Flashing an AOSP version of CM, then TWRP for CAF and finally CAF.
Fixing permissions.
Changing filesystems to F2FS.
I tried to logcat, but adb logcat keeps waiting for the phone and it doesnt find anything.
Anybody has another idea of what could be happening or how to solve it?
Thanks!
I can flash caf, aswell as noncaf roms on my N5 just fine.
I used the CM14 darkrom CAF. Excellent performance, great battery life
i wiped the device in TWRP caf (Latest) (system,data,cache,dalvik0
Then i flashed the rom and the Darkrom gapps (use only those, as rom comes withouth a launcher. Pixwl launcher embeded into gapps package)
Wipe cahce/dalvik & reboot
It looped like: GOOGLElogo ,bootanimation ,self restart and it works perfectly fine since then
---------- Post added at 18:54 ---------- Previous post was at 18:53 ----------
I should also mention, that i use the european D821 model
I was beginning to wonder if it was just me. I felt like an ass for posting for help because I felt like it was my fault. I still have not gotten any response at all from twrp support. I really want to use car based Roms. I use to be able to when I first got the phone. Now I don't have a clue what the problem is. I am using the 820 USA model.
After doing a Google search for CAF TWRP no boot black screen and other combinations I have found posts around the web from people with the same issue. The only resolution was to revert to stock. I have sent TWRP support another email linking to this topic as well as contacted them on g+ hopefully we can get a resolution.
since i dont own the device.... no logs= we cant help you
Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...
I'm having this problem too, I can flash any non-CAF ROM and it will bootup fine, but any CAF rom will leave me in a black screen. Did you found any solution yet?
I have not been able to find a solution to the problem. TWERP tech support seams to be non existent. I have emailed them numerous times. They don't even take the time to say they will look into it =(
Dark_Eyes_ said:
Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...
Click to expand...
Click to collapse
What else could it be if we are able to flash absolutely anything else we want to flash except for a CAFE ROM?
I have never tried editting the updater script. Could you please explain how to do the things you described?
Ok I got an update. Today just for ****s and giggles I tried to flash the latest TWRP twrp-3.0.2-0-hammerhead.img on top of itself from inside TWRP using the image flashing process. I got the black screen I been getting that we are discussing here. Therefore, that tells me that the problem is not with TWRP CAF but with flash recovery's in TWRP. For some reason TWRP does not like that. Therefore, I am manually flashing the fallowing files the old fashion way by hand using the android sdk and adb.
1.) TWRP CAF
2.) The latest bootloader directly from the latest google factory image
3.) The latest radio directly from the latest google factory image
4.) Install the latest build of Dark ROM
I will report back with my findings.
Findings are epic fail. No boot, black screen of death.:crying: After holding down volup+voldown+power I am able to get back into recovery just like with flashing all the files through recovery when I first started. However, I can't get the damn thing to boot the ROM. I don't know what to think anymore. I think we just have to come to the conclusion that CAF based ROMs are out of the question for us :crying: :crying: :crying: When my son gets home and can hold the tablet while I operate the Nexus 5 maybe I will try to make a video of the problem. Hopefully this will help lead to a resolution.
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
will a repaired device not work, mine has had the screen replaced. Nothing else just the screen.
experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
Yup, I have replaced the screen, why is that? Is it too much different than the original, shouldn't it work normally?
Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.
experience7 said:
Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.
Click to expand...
Click to collapse
Wait seriously? because i fixed my screen i am not able to use a caf rom on my device? That seems ridiculous, what would cause that to even be a thing? is there some sort of security flag it checks for?
Yeah I replaced the screen on mine too. Not sure how that plays a role. The only thing I can think of is unless there is a missing driver or something like that because our screens are different.
There's gotta be a way to fix this problem. I wish I knew how to build ROMs, kernels, and recoveries. I don't think anyone will go out of their way to fix a problem that doesn't directly affect them. So for me it is stock, rooted, with ElementalX till this pos croaks.
Not sure what the problem is. Fact is that your screen somehow differs from the 'original' one which causes CAF ROMs to blackscreen.
If you really, really want your phone to run CAF you have to provide a lot more information. You could try to get a running system and fetch some hardware information. Pretty sure there are apps on the Play Store that print hardware brands/model names, etc. Report your results and I'll use the same method to get mine. We should compare. Furthermore we'll need logs. Try to boot CAF. Of course it will blackscreen again but you can reboot to recovery and pull some logs. Maybe last_kmsg and dmesg where the latter one should be even more interesting.
And last but not least I'd like to tag @myfluxi here. Perhaps that's interesting for you...
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?