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.
Related
Hi, I have a big issue installing all but one build of the PAC-Man ROM not installing on my Droid Razr Maxx HD. I've tried installing multiple nightly & Dev builds of them ROM but they all boot loop at the Motorola logo. No one seems to care about this issue either. I've posted on almost all social media the Pac-Man ROM community has bit it seems to not be getting any attention. (Excuse me for getting a little off track) I always do a factory reset with twrp twice before attempting to install this ROM, I've also tried repairing the data partition (which is this fix found on Droidrzr forum) I've tried flashing back to stock KitKat, I would try side loading a build but twrp's side load feature doesn't work. Could some one guide me to sending a Dev a boot log so whatever bug is causing this is squashed? I really want to run this ROM. Or, could someone who has had this ROM installed guide on getting it up and running?
http://www.droidrzr.com/index.php/t...8960unofficialodex444baked-08-01-14/?p=451296 is the fix I tried
These are all the builds I've tried installing, only 1 worked.
https://www.dropbox.com/s/0nsoyd5zh8yb3ww/screenshot.jpg
Playb3yond said:
Hi, I have a big issue installing all but one build of the PAC-Man ROM not installing on my Droid Razr Maxx HD. I've tried installing multiple nightly & Dev builds of them ROM but they all boot loop at the Motorola logo. No one seems to care about this issue either. I've posted on almost all social media the Pac-Man ROM community has bit it seems to not be getting any attention. (Excuse me for getting a little off track) I always do a factory reset with twrp twice before attempting to install this ROM, I've also tried repairing the data partition (which is this fix found on Droidrzr forum) I've tried flashing back to stock KitKat, I would try side loading a build but twrp's side load feature doesn't work. Could some one guide me to sending a Dev a boot log so whatever bug is causing this is squashed? I really want to run this ROM. Or, could someone who has had this ROM installed guide on getting it up and running?
http://www.droidrzr.com/index.php/t...8960unofficialodex444baked-08-01-14/?p=451296 is the fix I tried
These are all the builds I've tried installing, only 1 worked.
https://www.dropbox.com/s/0nsoyd5zh8yb3ww/screenshot.jpg
Click to expand...
Click to collapse
i dont know the answer, so ill just throw out a question.
do you know that the pac rom has been updated to kk source?
bweN diorD said:
i dont know the answer, so ill just throw out a question.
do you know that the pac rom has been updated to kk source?
Click to expand...
Click to collapse
I've known, I've tried the updater to kitkat as well, still no luck
Playb3yond said:
I've known, I've tried the updater to kitkat as well, still no luck
Click to expand...
Click to collapse
i only asked because i didnt know.
so i just went and read this entire post (is this the one we are talking about?), and it has not been updated to kk base yet as far as i can see.
if you bootloop at the boot animation then its most likely because your data partition isnt formatted to ext4
I tried that as well, still no luck
Sent from my DROID RAZR HD using Tapatalk
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.
I realize there are some dedicated threads to this device. Quite a few actually. Probably too many which is leading to information overload.
Also this device isn't the newest kid on the block. NOOK TABLET (BNTV250A)
Just wondering if someone on this forum would share some working rom/gapps combinations with me.
Yes I know about the cyanogen download site. But I am finding that getting a rom working with a gapps is kind of hit and miss.
I do have an old version of jelly bean working on the device now just by chance. I went through many versions of jb gapps before I got it right.
Now I know jb is a good OS but there are some bug that I don't like. black screens and goo.im not working to mention a few.
So I would like to get kit kat or lolli pop working. For kit kat I have found nothing that won't stop boot looping.
And for lolli pop it's so sluggish that it's pretty much unusable. Anyway I won't babble on any more.
This is what I have working right now. ( cm-10.1-20130117-19-acclaim-HD.zip ) internal cm10.1 and ( gapps-jb-20130812-signed.zip )
And no other combination have worked.
Thanks
nandroid123
nandroid123 said:
I realize there are some dedicated threads to this device. Quite a few actually. Probably too many which is leading to information overload.
Also this device isn't the newest kid on the block. NOOK TABLET (BNTV250A)
Just wondering if someone on this forum would share some working rom/gapps combinations with me.
Yes I know about the cyanogen download site. But I am finding that getting a rom working with a gapps is kind of hit and miss.
I do have an old version of jelly bean working on the device now just by chance. I went through many versions of jb gapps before I got it right.
Now I know jb is a good OS but there are some bug that I don't like. black screens and goo.im not working to mention a few.
So I would like to get kit kat or lolli pop working. For kit kat I have found nothing that won't stop boot looping.
And for lolli pop it's so sluggish that it's pretty much unusable. Anyway I won't babble on any more.
This is what I have working right now. ( cm-10.1-20130117-19-acclaim-HD.zip ) internal cm10.1 and ( gapps-jb-20130812-signed.zip )
And no other combination have worked.
Thanks
nandroid123
Click to expand...
Click to collapse
You're device is officially supported by Cyanogenmod.
Just use the latest CM11 / CM12 from HERE
GApps working with ALL CM11/12 roms can be found HERE
Also your device has its own section HERE
Thanks lubeck for your reply.
If you check those cm11 downloads, most of them say 404 not found. Some of the cm12 are the same. CM10 are mostly there.
Thanks for the gapps page I will check that out thoroughly.
Yes I'm aware of the specific thread. No replies to my queries yet.
thanks
nandroid123 said:
Thanks lubeck for your reply.
If you check those cm11 downloads, most of them say 404 not found. Some of the cm12 are the same. CM10 are mostly there.
Thanks for the gapps page I will check that out thoroughly.
Yes I'm aware of the specific thread. No replies to my queries yet.
thanks
Click to expand...
Click to collapse
Its LS.xD, Lübeck is my home town
THIS CM11 should totally do it
Already got latest TWRP ?
Sorry LS.xD stupid me. I will try the cm11. thanks
Is there a specific gapps that you would recommend with this rom ?
Yes I have the newest twrp but still having problems with twrp seeing newly inserted sd cards. I have to run twrp internally and make sure the sd card is already inserted or twrp won't find it. CWM does not have this problem. Any ideas on that.
Will the latest CWM install this cm11 rom correctly ??
thanks
nandroid123 said:
Sorry LS.xD stupid me. I will try the cm11. thanks
Is there a specific gapps that you would recommend with this rom ?
Yes I have the newest twrp but still having problems with twrp seeing newly inserted sd cards. I have to run twrp internally and make sure the sd card is already inserted or twrp won't find it. CWM does not have this problem. Any ideas on that.
Will the latest CWM install this cm11 rom correctly ??
thanks
Click to expand...
Click to collapse
CWM 6.0.4.9 or newer will also flash it. I prefer TWRP due to the awesome and easy to handle touch interface. SD card should always beeing inserted before you run your custom recovery. The linked CM11 is the latest Snapshot (Most features should work on this) and should run fine with the gapps I mentioned.
LS.xD
That cm11 you told me to try is the same one that always boot loops for me.
Just exactly how do you install yours ? What recovery do you use. And can you tell me what gapps you used.
thanks
nandroid123 said:
LS.xD
That cm11 you told me to try is the same one that always boot loops for me.
Just exactly how do you install yours ? What recovery do you use. And can you tell me what gapps you used.
thanks
Click to expand...
Click to collapse
Just follow step-by-step
CM11
CM12
Wow got it to work !!
I had to use the exact recovery that was listed. Guess that will teach me to read instructions carefully !!
Thank you for your help LS.xD
nandroid123 said:
Wow got it to work !!
I had to use the exact recovery that was listed. Guess that will teach me to read instructions carefully !!
Thank you for your help LS.xD
Click to expand...
Click to collapse
Its all about learning
And if i HELPED you, press "thanks" at the bottom of my posts
LS.xD are you currently running any cm12 on the acclaim ?
I read the instructions pretty thoroughly this time but I still have cm12 running very slowly. Haven't actually made it through the google registration without the keyboard or something else failing.
I used the listed recovery and it ran no problems.
Any hints here ?
thanks
nandroid123
nandroid123 said:
LS.xD are you currently running any cm12 on the acclaim ?
I read the instructions pretty thoroughly this time but I still have cm12 running very slowly. Haven't actually made it through the google registration without the keyboard or something else failing.
I used the listed recovery and it ran no problems.
Any hints here ?
thanks
nandroid123
Click to expand...
Click to collapse
CM12 is still under development and you probably get a better performance and more reliable user experience with CM11. Did you you use the PA GAPPS I mentioned before? Did you perform a full wipe before installing a new rom?
BTW
I do not own the device myself, so I have no way to test the specific CyanogenMod versions...
Oh yes I always wipe user data, cache and dalvik before a rom install.
This is the gapps I tried last pa_gapps-modular-pico-5.0.1-20150221-signed.zip
I have tried several others.
cm11 installed so nicely once I used the correct recovery. I thought maybe cm12 would, but not so lucky.
Anyone else have any luck with CM12 ? Maybe you could share the details ?
thanks
I now have CM12 running on my 16gb nook tablet (BNTV250). Never did get CM12 working on the 8gb nook tablet. I'm thinking maybe a memory issue ?
I don't know but I would like to hear from anyone that has CM12 working properly on a 8gb model and how they did it.
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.
Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse
Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.
Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games
zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013
Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
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...