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.
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
** Was not sure where to post this.
Today I was successful in building CM 12 for the first time using Docker on Ubuntu 14. The build went fine but when I try to flash my phone with the cm-12-2015-02-01.zip file the flashing goes fine without any errors but when I reboot the device it gets stuck on the Google boot screen and doesn't process to the CM boot screen. I have tried doing a full clean flash, as well as wiping cache(s).
This does not happen if I try flashing an official build from the CM site. This has something to do with my build but I cant figure out what because the build goes fine when I run it.
Thanks for the help in advance
Did you make sure you're building for hammerhead?
Lethargy said:
Did you make sure you're building for hammerhead?
Click to expand...
Click to collapse
Yes I definitely built for hammerhead.
waleed_k said:
Yes I definitely built for hammerhead.
Click to expand...
Click to collapse
Try running a repo sync and rebuild
Hi,
Did you figure it out? We are running into the same issue, build in plain Ubuntu is fine, but if we build in Docker container, then the phone stuck on boot screen.
waleed_k said:
** Was not sure where to post this.
Today I was successful in building CM 12 for the first time using Docker on Ubuntu 14. The build went fine but when I try to flash my phone with the cm-12-2015-02-01.zip file the flashing goes fine without any errors but when I reboot the device it gets stuck on the Google boot screen and doesn't process to the CM boot screen. I have tried doing a full clean flash, as well as wiping cache(s).
This does not happen if I try flashing an official build from the CM site. This has something to do with my build but I cant figure out what because the build goes fine when I run it.
Thanks for the help in advance
Click to expand...
Click to collapse
Still have not figured this out.
I think this is a generic issue about building Android in Virtual Environment (chroot, lxc, docker).
I know that someone else says that Android can be built in VE without any problems, in our company, we do have some Android projects which can be built in VE without any problems too, but somehow, some projects cannot, hope that someone knows Android and VE better can help on this.
waleed_k said:
Still have not figured this out.
Click to expand...
Click to collapse
Hey there,
I've compiled CM13 without any problems. Flashing my build in recovery also went without errors but after reboot I get stuck at Google logo and nothing more.
My question is how to fix this bootloop to make that ROM usable? Maybe I have to do something with source code.. I don't really know.
I would be thankful if any Dev would like to help me with this.
Thank you in advance,
Cheers
Did you put the blobs in there?
Dear ladies and gentlemen,
a couple of weeks ago I decided to switch from SultanROM (latest build from 30th April) to LineageOS 14.1 (nightly build from 5th June 2017). Due to some minor bugfixes I updated to the nightly build from 17th of July. My phone worked well, aside from 2-3 random reboots. But two days a go all of a sudden it hung up. I tried to get it up again with a hard reboot. After a while I realized I was in a bootloop. Of course I tried the first obvious steps to get rid of the bootloop:
Wipe cache (including ART/Dalvik cache)
Flashed the most recent nightly build (2017-07-31) + wipe cache
Factory reset
Updated TWRP from 3.0.2 to 3.1.1
But even then - no chance, I was still hanging in the bootloop. After a few more tries I flashed SultanROM and tried again. Surprise, surprise: it worked perfectly, the phone got almost immediately up!
I'd like to go back to LineageOS, but I don't have a clue how to avoid the bootloop when flashing it again. In the past I flashed other firmwares and images, too (i.e. the 44S and persist.img from this post: https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061). Could this be a problem?
Any help would be appreciated!
grshnckh said:
Dear ladies and gentlemen,
a couple of weeks ago I decided to switch from SultanROM (latest build from 30th April) to LineageOS 14.1 (nightly build from 5th June 2017). Due to some minor bugfixes I updated to the nightly build from 17th of July. My phone worked well, aside from 2-3 random reboots. But two days a go all of a sudden it hung up. I tried to get it up again with a hard reboot. After a while I realized I was in a bootloop. Of course I tried the first obvious steps to get rid of the bootloop:
Wipe cache (including ART/Dalvik cache)
Flashed the most recent nightly build (2017-07-31) + wipe cache
Factory reset
Updated TWRP from 3.0.2 to 3.1.1
But even then - no chance, I was still hanging in the bootloop. After a few more tries I flashed SultanROM and tried again. Surprise, surprise: it worked perfectly, the phone got almost immediately up!
I'd like to go back to LineageOS, but I don't have a clue how to avoid the bootloop when flashing it again. In the past I flashed other firmwares and images, too (i.e. the 44S and persist.img from this post: https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061). Could this be a problem?
Any help would be appreciated!
Click to expand...
Click to collapse
Known issue with latest update of Lineage Os.
Meanwhile you can try latest Unofficial Lineage Os from Sultan.
Mr.Ak said:
Known issue with latest update of Lineage Os.
Meanwhile you can try latest Unofficial Lineage Os from Sultan.
Click to expand...
Click to collapse
Very interesting, thanks! Is there any bugreport or anything else, on which I could track the status?
grshnckh said:
Very interesting, thanks! Is there any bugreport or anything else, on which I could track the status?
Click to expand...
Click to collapse
https://www.cmxlog.com/14.1/bacon/
Mr.Ak said:
https://www.cmxlog.com/14.1/bacon/
Click to expand...
Click to collapse
Thanks, but this is the general changelog for the bacon devices from which I can't say if the bug I'm affected by is already fixed or not. When the issue is a known one, I assume there is some sort of bugreport or discussion going on. Could you provide further information about this bug in particular? Would highly appreciate!
grshnckh said:
Thanks, but this is the general changelog for the bacon devices from which I can't say if the bug I'm affected by is already fixed or not. When the issue is a known one, I assume there is some sort of bugreport or discussion going on. Could you provide further information about this bug in particular? Would highly appreciate!
Click to expand...
Click to collapse
Maybe follow the lineage os discussion thread:https://www.google.co.in/amp/s/foru...iscussion-lineageos-cyanogenmod-t3526394/amp/
Mr.Ak said:
Maybe follow the lineage os discussion thread:https://www.google.co.in/amp/s/foru...iscussion-lineageos-cyanogenmod-t3526394/amp/
Click to expand...
Click to collapse
Are you refering to this one: https://forum.xda-developers.com/showpost.php?p=72344415&postcount=942?
grshnckh said:
Are you refering to this one: https://forum.xda-developers.com/showpost.php?p=72344415&postcount=942?
Click to expand...
Click to collapse
Yes but the whole thread not just a single post.
Mr.Ak said:
Yes but the whole thread not just a single post.
Click to expand...
Click to collapse
Most of the outlined problems are about random reboots and a crashing camera (I read back to page 93). But my problem is: LineageOS 14.1 doesn't even start anymore - after wiping everything, flashing the newest nightly and doing a factory reset.
grshnckh said:
Most of the outlined problems are about random reboots and a crashing camera (I read back to page 93). But my problem is: LineageOS 14.1 doesn't even start anymore - after wiping everything, flashing the newest nightly and doing a factory reset.
Click to expand...
Click to collapse
Well,you can post your issues there or move on to unofficial lineage os by @idprophecy or sultan.
Sent from my A0001 using Tapatalk
I am too facing this issue. Did you get it working @grshnckh ?
CedArctic said:
I am too facing this issue. Did you get it working @grshnckh ?
Click to expand...
Click to collapse
Unfortunately not. I still stick to SultanROM as a temporarily solution, altough I'd prefer to use LineageOS 14.1 again. Which build have you tried?
grshnckh said:
Unfortunately not. I still stick to SultanROM as a temporarily solution, altough I'd prefer to use LineageOS 14.1 again. Which build have you tried?
Click to expand...
Click to collapse
I flashed various builds with no success. What did seem to work is sultanized ROMs, I flashed Sultanized RR and it booted up fine and it was actually pretty good. Just a bit ago I went on a flashing adventure to go and flash AOSPA 7.2.1 but that ended up badly with a bootloop and a broken recovery. I was forced to download WugFresh's toolkit and fix the softbrick (lost all data in the process beware), I am currently on stock CM12.1 and I'm going to flash to AOSPA probably after the boot has finished up.
CedArctic said:
I flashed various builds with no success. What did seem to work is sultanized ROMs, I flashed Sultanized RR and it booted up fine and it was actually pretty good. Just a bit ago I went on a flashing adventure to go and flash AOSPA 7.2.1 but that ended up badly with a bootloop and a broken recovery. I was forced to download WugFresh's toolkit and fix the softbrick (lost all data in the process beware), I am currently on stock CM12.1 and I'm going to flash to AOSPA probably after the boot has finished up.
Click to expand...
Click to collapse
So WugFresh's toolkit did the trick for you? Do you intent to flash LineageOS afterwards again?
grshnckh said:
So WugFresh's toolkit did the trick for you? Do you intent to flash LineageOS afterwards again?
Click to expand...
Click to collapse
Don't think I'm going back to Lineage, RR for me is better (Sultanized or not version). For now I think I'm going to stay on AOSPA. If you try WugFresh's stock flashing tool I urge you to backup all your data.
CedArctic said:
Don't think I'm going back to Lineage, RR for me is better (Sultanized or not version). For now I think I'm going to stay on AOSPA. If you try WugFresh's stock flashing tool I urge you to backup all your data.
Click to expand...
Click to collapse
Thanks for your advice. I already lost everything while trying to get back to LineageOS the last time. Fortunately I had up to date backups.
Have you flashed any ROMs or other stuff before that could cause the problems?
No, not really. I had this issue (meaning that I couldn't change to another non Sultan ROM) for a while now but chose to ignore it. Today I flashed multirom on top of Sultanized RR but I don't think that made any difference, when I flashed to AOSPA everything went South.
CedArctic said:
No, not really. I had this issue (meaning that I couldn't change to another non Sultan ROM) for a while now but chose to ignore it. Today I flashed multirom on top of Sultanized RR but I don't think that made any difference, when I flashed to AOSPA everything went South.
Click to expand...
Click to collapse
I tried several modems a few weeks back, but I'm not sure if this could be the reason.
grshnckh said:
I tried several modems a few weeks back, but I'm not sure if this could be the reason.
Click to expand...
Click to collapse
I originally suspected the firmware as well, turns out that probably wasn't the case, but I am now also now suspecting that the ROMs I tried to flash weren't f2fs compatible and it wasn't sultan's fault after all.
CedArctic said:
I originally suspected the firmware as well, turns out that probably wasn't the case, but I am now also now suspecting that the ROMs I tried to flash weren't f2fs compatible and it wasn't sultan's fault after all.
Click to expand...
Click to collapse
I read about a similar issue: https://forum.xda-developers.com/showpost.php?p=69837921&postcount=3
Highly would appreciate when you keep us up to date here. Good luck!