On my Samsung Galaxy Tab 10.1, I installed the main new CM10 ROM, as recently announced, and although I had some problems, it now works fine. However, as I was trying to transfer a ZIP file that I did not properly transfer the first time, I discovered that the card reader does not seem to be detected at all when I connect it to the tablet. Also, the tablet, which uses the same port seems to be only partially working. For example, the Home and Back keys do not seem to work at all, although the equivalent buttons on the display seem to be OK.
Are there other things I should do once I have the new ROM installed ? I was trying to get the Google Apps ZIP file tr-transferred to the internal /sdcard partition so I can install all those goodies.
Try to ask the developer of the rom, he/she has the answers. Or maybe revert to stock rom if you really need to those functions.
Hi to all.
I've searched all the web. Readed the info from this forum (Especially how to cook with Android Kitchen, but no luck.
I have a Galaxy Tab 2 7.0 on hands with a goal to make a custom rom with some preinstalled apps and a custom default background in it.
It should rely on original samsung ROM with no ROOT, and best if it had original recovery installed.
There is a local company, that has several devices on hand, wanting this rom, and an ability to reinstall it on their tablets with as few clicks as it is possible without needing to reinstall those crucial apps again.
I tried to cook with original rom with no luck at all (also tried CWM recovery with error Status 0)
Tried to make custom rom based on CM 10.1, added Skype.apk in system/app (Don't know how to delete ROOT from there:crying And after start, Skype was in autoload ang crashing constantly. So no Luck.
If someone has some skills, could help me. It would be much appreciated.
On my Samsung GT-N7000 I'm trying Omnirom again. I've tried it in the past and also tried vanilla CM stable and nightlies. I have also tried SuperNexus and PA and some other stuff that left no impression. Basically on this device for functional hardware, reasonable user control and a coherent UI it is Samsung's Touchwiz rooted, or Omnirom.
It is a bit too hard to install Omnirom and it can be horribly tedious to go from Omnirom back to stock or to another ROM. It's OK after you have done it a few times, but it is a huge obstacle for anyone trying to discover the way via inaccurate, misleading and fragmented documentation. The install guide at omnirom.org is actually utterly useless for this particular device, a complete non-starter. XpLoDWilD your GT-N7000 specific thread at http://forum.xda-developers.com/showthread.php?t=2516933 almost guarantees a boot loop because it only mentions but doesn't identify or link to versions of CWM which are adequate. In fact unless the user by diligent searching (or more likely by blind chance) comes across a link to the specific suitable raw kernel then it is one big dead end. You could spend hours and days searching for a suitable CWM and never find it because actually you should be searching for raw_kernel_r#_j##.zip. But how is anyone meant to know this. It turns what is actually a reliable and rather trouble free 15 or 20 minute process into a some kind of waking torment. In the past the documentation on installing via CWM was so bad that I used ODIN, which is less than ideal IMO because it means that anyone switching from stock to Omni doesn't get the chance to make a full nandroid backup of the original system (so to revert means a very tedious clean install).
So assuming the end user somehow finds the right raw kernel whose recovery can install Omnirom, what should they do? Of course they should back up their current apps and also make a nandroid backup. Apps backup is easy with oandbackup or titanium or similar. How about a nandroid backup to external SD? No problem in CWM but once you have TWRP installed you can't use it to access anything on an exfat formatted external SD card! You can back up before installing Omnirom but afterwards you can't restore! This is 100% nuts. exfat has now been around for 8 years. CWM supports it brilliantly. Even my crusty old Debian stable desktop reads and writes to exfat at very high speeds even via a FUSE FS and my puny Asus EeePC netbook running XP Home handles it fine. TWRP? Nope. exfat? Wha tha? Aaaaaagh.
Sorry to rant But for these specific devices Omnirom (with an exfat SD) is really the only high quality competitor to the stock Samsung, and there surely isn't a good reason for it being so frustrating to install and also to revert? Is TWRP really such a killer facility that it is worth foregoing the ability to backup and restore to the now very common exfat microSDHC? I run plain CM 11 on another device and OTA updates work fine on that. In these days of phatter pipes is it really worth making a huge compromise in functionality simply to avoid 200MB of downloads sometimes? On this device the delta updates are going to fail for many anyway unless they use an exfat card, but if they use an exfat card they.....oooouuuurrrggg...vicious circle.
/rant over.
Loving Omnirom btw and writing as a fan.
#blamesamsung
The Exynos Galaxy S2 family are some of the only devices remaining that don't have separate recovery partitions. This has always led to various annoyances for custom firmware users since it's impossible to change recovery without changing kernel.
Probably the documentation could be updated to indicate a double-flash though. Flash once to get a working recovery, flash a second time to get a working /system
Entropy512 said:
#blamesamsung
The Exynos Galaxy S2 family are some of the only devices remaining that don't have separate recovery partitions. This has always led to various annoyances for custom firmware users since it's impossible to change recovery without changing kernel.
Probably the documentation could be updated to indicate a double-flash though. Flash once to get a working recovery, flash a second time to get a working /system
Click to expand...
Click to collapse
Thanks for responding. I do appreciate that the exynos based devices are sons-of-b...b...bad persons.
I know documentation is boring and mostly thankless but it also matters a lot, most especially for projects which invite the user to perform realtively complex and potentially hazardous tasks.
Personally I would be very happy to edit/update XpLoDWilD's guide, but of course I can't because it's a forum post, not a wiki, so he owns it and it will remain there guiding new and trusting people into disappointment and boot loop oblivion until he decides to change it.
Omnirom has some issues but on the GT-N7000 is probably the only really mature and coherent alternative UI to Samsung's Touchwiz. To me it seems simply insane to direct newcomers into an unnecessary, time consuming, badly described and potentialy hazardous obstacle course, when in fact installation can be done with only small inconvenience.
I'm currently looking for information about installing OmniROM (I'm currently running CM11 nightlies), and I can attest the information in XpLoDWilD's post is somewhat vague, and also doesn't fully correlate with the directions to install Omni at the official wiki -- I'm assuming this lack of correlation is partly due to the fact, mentioned in this thread, that the N7000 doesn't have a separate recovery partition.
Something which made me especially uncertain about the installation process is the following part:
XpLoDWilD said:
- Make sure you're running a proper working ClockworkMod-Recovery - WITH SELINUX SUPPORT!
Click to expand...
Click to collapse
My understanding is that SeLinux is a feature of the kernel -- not the recovery console -- am I wrong about this? Or should I look for SeLinux in the features of the recovery console as well? (if so, how?)
What I currently do, is run adb, or start a console from the normal operating mode (not recovery mode), run the command:
Code:
getenforce
and confirm the reply is:
Code:
Enforcing
which means I have a kernel with SeLinux. Is that good enough to ensure the requisites for the installation are provided?
I'd appreciate any input about this matter.
julian67 said:
Personally I would be very happy to edit/update XpLoDWilD's guide, but of course I can't because it's a forum post, not a wiki, so he owns it and it will remain there guiding new and trusting people into disappointment and boot loop oblivion until he decides to change it.
Click to expand...
Click to collapse
Cant you add device-specific installation guide at the official wiki?
sagie said:
Cant you add device-specific installation guide at the official wiki?
Click to expand...
Click to collapse
I'm back on rooted Samsung TouchWiz. As things stand I wouldn't encourage any normal end user with a GT-N7000 to try a ROM. Hardware support is poor and unlikely to improve, installation documentation is misleading, backup is difficult, and restoring stock Samsung successfully requires ODIN. Also you stand a real chance of bricking the device. On my B+N Nook HD CM11 nightly is, as far as I can tell, beyond criticism but on these Exynos based devices all the third party ROMs have poor hardware support, poor multimedia support, poor stability and truly terrible battery life (even with no gapps installed). I will keep trying out ROMs occasionally and if the day arrives where the hardware is truly supported I will write a guide and drink a bottle of french fizz, but at the moment I would discourage any regular end user from doing anything to their GT-N7000 except running the newest available official firmware and rooting it if required.
I'm pretty sure I can save my twrp backups to my exfat sdcard.
edit: yup. just touch "internal storage" on the twrp backup page and select your sdcard.
julian67 said:
I'm back on rooted Samsung TouchWiz. As things stand I wouldn't encourage any normal end user with a GT-N7000 to try a ROM. Hardware support is poor and unlikely to improve, installation documentation is misleading, backup is difficult, and restoring stock Samsung successfully requires ODIN. Also you stand a real chance of bricking the device. On my B+N Nook HD CM11 nightly is, as far as I can tell, beyond criticism but on these Exynos based devices all the third party ROMs have poor hardware support, poor multimedia support, poor stability and truly terrible battery life (even with no gapps installed). I will keep trying out ROMs occasionally and if the day arrives where the hardware is truly supported I will write a guide and drink a bottle of french fizz, but at the moment I would discourage any regular end user from doing anything to their GT-N7000 except running the newest available official firmware and rooting it if required.
Click to expand...
Click to collapse
i've been using omnirom as my daily driver for 2 weeks now. love kitkat and omnirom features, but its still very unstable i think. stuff that's bothering me for now:
-stock camera is really plain, can't even switch to front camera
-video playback sometimes fail
-music playback will fail the first time i launch and play a song or 2. have to reboot and it'll work all day long
-intermittent random reboots, about 3 times so far the whole week
-wifi signal range is somewhat lower compared to touchwiz rom
-stock clock app, can't manually input time via keypad when you want to add an alarm
-contacts app is very confusing, can't even add a contact with ease. well at least for me that is
other than that kit kat is sure a welcome on this legendary device. contemplating the switch back to stock touchwiz, but loathe at the idea of setting up everything again zzz
In answer to this, and if it can help.
That the second time I install a ROM on my N7000, so it was still a bit frightening for me
Based on a CM10.1, I already had an old CWM.
1) From CWM I've just installed Philz Touch
2) On Philz, i've wiped everything, formated both internal and external sd cards (well I wanted something reeeally clean)
3) Used abd for copying omnirom and Gapp zip on the root
4) installed them from Philz Touch.
And it works like a charm (... but not enough feedback yet, just 2 days).
Now the question is to know if a day Omnirom will accept CWM based recoveries for updates.
TWRP is unfortunately not available on N7000 (from what I see, only USA flavors of Galaxy Note1).
Thanks!
Polux
Polux44 said:
In answer to this, and if it can help.
That the second time I install a ROM on my N7000, so it was still a bit frightening for me
Based on a CM10.1, I already had an old CWM.
1) From CWM I've just installed Philz Touch
2) On Philz, i've wiped everything, formated both internal and external sd cards (well I wanted something reeeally clean)
3) Used abd for copying omnirom and Gapp zip on the root
4) installed them from Philz Touch.
And it works like a charm (... but not enough feedback yet, just 2 days).
Now the question is to know if a day Omnirom will accept CWM based recoveries for updates.
TWRP is unfortunately not available on N7000 (from what I see, only USA flavors of Galaxy Note1).
Thanks!
Polux
Click to expand...
Click to collapse
Per my earlier post - You cannot change kernels on the Samsung GS2 family (including N7000) without also changing recovery.
Conversely, you can't change recovery without changing kernel. It's a limitation of this device since the recovery partition is not actually used, and recovery is in the normal kernel.
Once you flash Omni, your recovery will be TWRP. The reason TWRP doesn't "officially" support any of the GS2 family is because, as I said - you can't change recoveries without changing kernels.
Entropy512 said:
Once you flash Omni, your recovery will be TWRP. The reason TWRP doesn't "officially" support any of the GS2 family is because, as I said - you can't change recoveries without changing kernels.
Click to expand...
Click to collapse
Yes thanks for the precision, i've just seen that now my recovery was TWRP. (well which is good for me since it means I can use OTA). Your details helped me to understand why recovery and kernel are linked together, for my device.
Does it mean that installing omni on a non GS2 device (let's say a more recent device) will not overwrite the existing recovery?
Thanks again!
Polux44 said:
Yes thanks for the precision, i've just seen that now my recovery was TWRP. (well which is good for me since it means I can use OTA). Your details helped me to understand why recovery and kernel are linked together, for my device.
Does it mean that installing omni on a non GS2 device (let's say a more recent device) will not overwrite the existing recovery?
Thanks again!
Click to expand...
Click to collapse
Correct. Sony devices also have this limitation, there is a semi-workaround (where the kernel pulls recovery ramdisk from another location) on those that *in theory* could be done on the old Samsungs... but so few people are working on the old Samsungs that it isn't likely to happen.
Pretty much all GS1s and Exynos GS2s had this limitation. Qualcomm GS2s (Skyrocket/Hercules) had a separate recovery, as did all GS3s and onwards.
Rooted and flashed CM 13. Can't find stylus tools like palm rejection and la paso screen capture. Please help..
Ps. I'm a newbie into all this.
Not sure if this is why but cm 13 and the normal ROM it comes with do not share features the stylus will work on non OEM roms but none of the extra bits of the stylus including tools will be installed by default you may need to manually install some...
Ohh...Any guidance on how to install them manually
Only that it can be a bit of a pain it will depend strongly how interwoven all the components of it is. It could be as simple as pulling some system apps from a stock image to needing to pull and build a custom kernel and install a host of apk. Basically if it was something easy it would be done. This is what diffrenates a stock ROM from something like cm. With cm you gain a clean slate so to speak but as a result you loose baked in features that don't always transfer. The best advise I can give is go to one of the stock based roms and strip out what you don't need or use of of the custom stock on here that did it for you.
Hello everyone,
First let me start of by saying that I love this forum, I love the idea of it; having all android consumers' needs all grouped in one place I wish they were different websites as focused as this one. And I am thankful for every person in this pseudo system that helps everyday, make it a better version of what it is.
I've been considering rooting my device for months. Now, I finally have some time to get to it.
I saved up some questions while browsing the forums, I am hoping you could save 2 minutes to answer whatever question you think your best suited to answer. (I am patient )
1. If I freeze/ delete bloatware from my device, does it become aosp?
2. After downloading, can I download Aosp as my ROM or do I have to use a custom rom like Lineage, MIUI, etc ...?
3. When I Am using a ROM + an android launcher, do the ressources(Battery, memory, ...) used by both add up. What I am asking is it always better to use a rom without a launcher?
4. What are CAFs?
5. what exactly is CMW or TWRP?
6. If I already have greenify, do I need doze? or is it redundant? (stock rom is kitkat 4.4)
I'll be posting again, because, I don't want to brick my phone (SIGH!), untill then have a good day.
CWM and TWRP are custom recoveries that let you install zip files. Custom ROMs and other mods come in zip form so you need TWRP if you want to install anything like Roms.
What device are you planning on rooting?
Anarhy said:
Hello everyone,
First let me start of by saying that I love this forum, I love the idea of it; having all android consumers' needs all grouped in one place I wish they were different websites as focused as this one. And I am thankful for every person in this pseudo system that helps everyday, make it a better version of what it is.
I've been considering rooting my device for months. Now, I finally have some time to get to it.
I saved up some questions while browsing the forums, I am hoping you could save 2 minutes to answer whatever question you think your best suited to answer. (I am patient )
1. If I freeze/ delete bloatware from my device, does it become aosp?
2. After downloading, can I download Aosp as my ROM or do I have to use a custom rom like Lineage, MIUI, etc ...?
3. When I Am using a ROM + an android launcher, do the ressources(Battery, memory, ...) used by both add up. What I am asking is it always better to use a rom without a launcher?
4. What are CAFs?
5. what exactly is CMW or TWRP?
6. If I already have greenify, do I need doze? or is it redundant? (stock rom is kitkat 4.4)
I'll be posting again, because, I don't want to brick my phone (SIGH!), untill then have a good day.
Click to expand...
Click to collapse
1) no, if you freeze/remove bloatware it does not make AOSP.
2) The ROMs you use will depend on what(if anything) is available for your model number, there may be no custom ROMs or there may be up to 10 or 20 custom ROMs. It just depends on whether anyone has chosen to build ROMs and what type of ROM(s) they choose to build. This is all determined by the model number of your device.
3) Yes, everything that is installed, loaded and running will use battery. I don't exactly undrstand why or what you are asking this for.
4) http://openattitude.com/2016/01/18/android-6-custom-roms-aosp-vs-caf/
https://forum.xda-developers.com/google-nexus-5/help/caf-vs-caf-t3341502
5) CWM(ClockWorkMod) and TWRP(Team Win Recovery Project) are custom recoveries used to flash ROMs, make backups, restore backups, wipe the devices partitions, adb access and management, etc..
6) Greenify freezes apps and Doze puts the device in deep sleep so it's OK to use them together as long as it doesn't cause a conflict, it may depend on how you arrange each of their settings.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE