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.
My problem is after installation of 4.2 rom i lost my radio, but only in kitkat.The original kitkat tmobile rom seems to fix that, but then again any other rom is with broken radio. CM11 is ok, but if im not wrong the cm radio is being written on different partition, than the kitkats one.Tried KK_baseband_801.zip and LG801_20A_RADIO.zip.Neither of them fixes the issue.A can live with CM11 but i am really sorry i cant have access to the UHD camera.So i guess you guys are going to tell me to downgrade .Probably that will fix it but i`ve to install Windows 7 again so im not in a hurry.I can try it in virtual box but didn't had success before that and had to temporarily install windows.Ultimately id like to interchange betwen cm11 and lightning v2 rom with the slow motion camera and the other extras.Its just too much bloatware with the tmobile version plus its checking to see if you have tethering plan, which is incompatible with unlimited data.
Thanks
Installed stock after all, since the baseband issue still exist if put something else, but i used smileys ROM then installed "autorec xda" which is capable off flashing twrp in case you need CM.The UHD cam is cool to play with , although i wish to be possible to manual focusing during video recording instead this useless thing to take a picture.What do you think.
portis said:
Installed stock after all, since the baseband issue still exist if put something else, but i used smileys ROM then installed "autorec xda" which is capable off flashing twrp in case you need CM.The UHD cam is cool to play with , although i wish to be possible to manual focusing during video recording instead this useless thing to take a picture.What do you think.
Click to expand...
Click to collapse
I agree on your comment. This should have been considered before the device got manufactured..
Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.
chrismin13 said:
Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.
Click to expand...
Click to collapse
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM
shaun298 said:
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM
Click to expand...
Click to collapse
Thanks for the response!
Good idea! I was thinking of going back to stock and repeating everything. It should fix all my issues. It's too bad that I don't have a working stock backup and I will have to flash through Odin. The reason that I am not doing this is because I am afraid of making it even worse from the official status state that I have in Download Mode and my device is an n8013 under About Device. A flash back to stock through Odin would probably flash most of the system parts which would be kinda dangerous. But on the other hand that would mean that I could give it a brand new try with better luck possibly! It's not that TouchWiz ROMs don't work, it's AOSP that doesn't. I played a lot with Hyperdrive and seems like it's doing better from the lag prospective. But that's only gonna last 15 days. I am sure! So, I'll have your response in mind! Might try it out when I have some free time. Unfortunately, that will probably be Christmas.
Thanks,
Chris
Going back to stock is good advice.Should certainly fix the video problem which you said was important.
Phil789 said:
Going back to stock is good advice.Should certainly fix the video problem which you said was important.
Click to expand...
Click to collapse
I don't have any video playback issues. It's just the camcorder that doesn't work in AOSP ROMs.
Yes.My use of the word "video" should have been "video recording".
The time has come!
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.
chrismin13 said:
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.
Click to expand...
Click to collapse
I did it! It worked. Everything went OK but:
- Flash count is 0 and status official
- Back camera records in slow-mo
- Chromecast mirroring does not work
However:
-My device is an N8010
-I use the front camera instead
-Mirroring was not really needed
-LAG IS HISTORY!!! [emoji50] [emoji2] [emoji2] [emoji2]
I am so impressed by the performance, still doesn't best my nexus 4 with KK 4.4.4 but it's a GIGANTIC IMPROVEMENT! Veeery happy! Thank you for your support, I wouldn't be here without you!
Merry Christmas and happy holidays!
Chris.[emoji2]
I'm currently running the feb14 build cm12 of daniel_hk, and I'm experiencing lots of hangs and lags now and then... Apps dont run as smooth as when I was on 4.1.2 especially CoC. Really don't know why (but still cheers to the dev for all the effort)
I'm now planning on changing the rom temporarily, while I wait for a few updates. Especially a Kitkat one. What kitkat rom for my P6200 will be the most stable? CarbonRom or Omni?
I recall trying both and was getting more hangs / reboots in carbon, so I'd say try omni. However nothing more stable than stock JB imo, probably due to full sources never being made available for this model.
Have you try CM 12.1 latest build? I use it as my daily, much more stable than the 14 Feb build, using it for CoC without any issues (no sudden reboots). As for kitkat, i agreed with skurys, better use stock JB than kitkat carbon or omni. Cheers
Installation Aborted
F R Harris said:
Have you try CM 12.1 latest build? I use it as my daily, much more stable than the 14 Feb build, using it for CoC without any issues (no sudden reboots). As for kitkat, i agreed with skurys, better use stock JB than kitkat carbon or omni. Cheers
Click to expand...
Click to collapse
Hi,
I have read the post from Daniel for CM 12.1. It seems very interesting and promising especially after reading the comments from different members about the stability and speed of this ROM. I have followed the procedure to install this ROM as below:
1. Rooted my P6200
2. Flashed cwm-6.0.4.5-p6200.tar via. ODIN as TWRP .zip was giving problem. This was also mentioned in a suggestion from another member in this link http://forum.xda-developers.com/showpost.php?p=41214833&postcount=215
3. Once rooted I installed SuperSU and BusyBox without any problems
4. Wipe the data
5. WIpe the cache
6. Npw when I tried to flash the latest build of CM12.1 i.e. available here https://www.androidfilehost.com/?w=files&flid=33760, I am getting error. Here is the error message :
"ApplyPArsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supporoted on transport endpoint".
E:Error in /storage/sdcard1/<filepath>
(Status 7)
Installation aborted."
I am also attaching a screen shot of the error message for easy understanding and reference. Is this something related to my SD Card/Storage?
I created a back up before flashing so I have restored back to stock with that backup but no luck flashing this ROM. Am I doing something wrong?
Also, since I am junior member I am not allowed to post OR reply directly to that thread.
I cannot finish before appreciating and thanking Daniel for his gr8/wonderful work for the Galaxy Tab throughout his projects. We can use these tabs for some more time now. Thanks you so much.
Please help me..
i think i wanna revert back to stock .. cause so far i install to many version of OS, no such as 1 stable..
included latest release of carbon rom, still have an issue with WiFi can't stored password as well, each time on the signal, need to re-enter the password..
message flickering while trying adding some recipent ..
Hey guys. Two days before i updated my phone manually via ODIN on a german version G930FDBT2ERG2_DBT.
So i just let Google and Samsung restore all my stuff. Then i installed TWRP and root via the no-verity-opt-encrypt-6.0.zip and magisk v16.0.
After that i installed XPosed via the XPosed Installer app. I think since i did that or maybe before, every app needs hours to start and lags.
e.g. opening of Snapchat. Like it's closing so hard in background, that all services need to restart.
Instagram and OneDrive are shown many time as stopped working and i don't know why. Maybe Instagram caused by XInsta?
Okay i recognized OneDrive isn't even working anymore. Was already on Android 7 a problem. Does not seem to be compatible to something else.
You have any ideas or need any information? Let me know
try a factory reset. Personally, I use a modified stock rom (light rom) and it is very stale and very fast.
achour7 said:
try a factory reset. Personally, I use a modified stock rom (light rom) and it is very stale and very fast.
Click to expand...
Click to collapse
Antutu Benchmark gives me 164336 points, so it seems literally to be normally, but i know all loading times of Snapchat and Instagram and so on are so much longer.
I will try to flash it again and to start clean. Just the copying of the WhatsApp folder needs so much time.
So I'm asking again. Nobody else got problems? I still dont get the data mount error fixed, because when I install Magisk it's broke again and my whole phone seems to lag. I dont know if it's because of my Xposed modules or Magisk modules. But for example with the update everythings goes slower even if Antutu says something else. Snapchat needs years to start. Is it cause of dual messenger? But I don't think so. Or when i'm in the car and using Google Maps and Poweramp and tapping skip on my car radio for skipping in bluetooth there is a delay of 20 seconds sometimes so wtf.
Any speedups for S7 or Android 8 on S7???
CptDayDreamer said:
So I'm asking again. Nobody else got problems? I still dont get the data mount error fixed, because when I install Magisk it's broke again and my whole phone seems to lag. I dont know if it's because of my Xposed modules or Magisk modules. But for example with the update everythings goes slower even if Antutu says something else. Snapchat needs years to start. Is it cause of dual messenger? But I don't think so. Or when i'm in the car and using Google Maps and Poweramp and tapping skip on my car radio for skipping in bluetooth there is a delay of 20 seconds sometimes so wtf.
Any speedups for S7 or Android 8 on S7???
Click to expand...
Click to collapse
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.
achour7 said:
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.
Click to expand...
Click to collapse
I like TouchWiz. Is there any ROM that is similar? And never heard of another kernel to fix that. Is that kernel better? Last time i changed kernel and stuff was with my Galaxy S3
CptDayDreamer said:
I like TouchWiz. Is there any ROM that is similar? And never heard of another kernel to fix that. Is that kernel better? Last time i changed kernel and stuff was with my Galaxy S3
Click to expand...
Click to collapse
Tgp kernel gives a good battery life ans smooth UI.
If you didn't flashed a kernel, you need to wipe data partition by writing ''yes''
And you will Lost all you data, so you need to save you data on external storage, hard Drive or computer.
achour7 said:
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.
Click to expand...
Click to collapse
achour7 said:
Tgp kernel gives a good battery life ans smooth UI.
If you didn't flashed a kernel, you need to wipe data partition by writing ''yes''
And you will Lost all you data, so you need to save you data on external storage, hard Drive or computer.
Click to expand...
Click to collapse
Works it without problems? Bro do i just need the kernel or also like I found out this THE GALAXY PROJECT ROM ? It looks like TouchWiz ha?
I have stock phone without root and my phone is getting really extremely hot since it was updated to Oreo.
Even by doing something like being here in the forum is getting so hot that is uncomfortable on my hand
CptDayDreamer said:
Hey guys. Two days before i updated my phone manually via ODIN on a german version G930FDBT2ERG2_DBT... After that i installed XPosed via the XPosed Installer app. I think since i did that or maybe before, every app needs hours to start and lags...
Click to expand...
Click to collapse
If on stock then resources being consumed with bloat. If issues began around installation of xposed wouldn't it make sense to uninstall modules and xposed and see if improved over the next day? Restoring apps and data and rooting and moding is a lot of stress on device all at once, then it gets so warm it starts to go glitch. I've been there too. Best thing is to let it sit 30-60 min after set up finishes to cool off. Reboot too once restored data completes.
Almost makes me miss the rip out and replace with cool fully charged battery days of my S4 [emoji91]
Sent from my SM-G930W8 using Tapatalk