Related
Hi guys,
I have this tablet for quite some time, and until now I have tried numerous ROMs that more or less did the job. But, I am still experiencing issues like slow boot, slow functioning in general. Now, I would like to give it as a gift to a friend, but I want to give it in a good clean state. So, my question to you all is what is the best ROM for this tablet? What can I do so that she can enjoy it and all the features that it has? In my oppinion, this tablet has very good features, way above many other that are on the market, but somehow I did not "feel" all this, but instead with all the testing I have done, I was not convinced ... Could I get your oppinion on the ROMs and gapps versions I should use? Right now I am running ZombiPOP 5.1.1.
Any oppinion/suggestion is welcome
You don't give this device to a friend
ikkeT said:
You don't give this device to a friend
Click to expand...
Click to collapse
:laugh::laugh::laugh::laugh::laugh::laugh::laugh: Is it really that bad?
I have just finished installing the latest version of ZombiPOP, all good but I chose ROM2SD, and for some reason it says something about low on space, even though the SD card is empty (32GB) and there is all the space available on internal, too. Installed the performance patch, and now it is stuck on optimizing app 17 of 84 for about 10 minutes, even though I did not install any google apps in the ROM, I wanted to install the banks gapps.
But seriously, is it that bad that you wouldn't give it to a friend?
If you don't want to be married to it, give it away with the understanding you are done with it!
Personally, I would sell it and be done with it.....it's that bad.
I see ... well, that's not very good news. As I said, it's a friend and I would like to stay in touch with her after this, so probably I won't give it to her. Maybe try to sell it. It's still a mistery, to me as well as many others around here I noticed, how such good performance indicators (CPU, RAM, etc.) in reality perform very badly Although I've seen a couple of good grades for it, regarding different ROMs, I can see that the big majority is against it. Well, I will be waiting for a few days anyway, maybe someone will visit this thread and give such a good review of a ROM, and such details that I can replicate easily, that it would be worth giving it after all
bx3m said:
I see ... well, that's not very good news. As I said, it's a friend and I would like to stay in touch with her after this, so probably I won't give it to her. Maybe try to sell it. It's still a mistery, to me as well as many others around here I noticed, how such good performance indicators (CPU, RAM, etc.) in reality perform very badly Although I've seen a couple of good grades for it, regarding different ROMs, I can see that the big majority is against it. Well, I will be waiting for a few days anyway, maybe someone will visit this thread and give such a good review of a ROM, and such details that I can replicate easily, that it would be worth giving it after all
Click to expand...
Click to collapse
I am still using Cromi-X with f2fs on both internal and external. It is running very reasonable speed/performance. Please PM me if you are interested in testing it and come back here to write comments if it is still suck....
LetMeKnow said:
I am still using Cromi-X with f2fs on both internal and external. It is running very reasonable speed/performance. Please PM me if you are interested in testing it and come back here to write comments if it is still suck....
Click to expand...
Click to collapse
Hey LetMeKnow PM sent
bx3m said:
Hey LetMeKnow PM sent
Click to expand...
Click to collapse
Hi all,
First, many thanks to those that replied to this thread, I know you must me tired of this kind of question - how do I...?
Second, I'd like to thank LetMeKnow for his efforts to help me with this issue. Turns out he does have a formula for success regarding this device, which I've applied and I am very happy with the result.
I've managed to install Cromi-X 5.4 ODEX version, converted the filesystem from ext4 to f2fs, then applied @LetMeKnow's fix (which he has prepared for me) and now I can honestly say that I am finnaly looking at this device as a real tablet
What I've described here are the steps I've made in general, but if anyone wants a detailed description, just ask and I will share all information with you. Please have a little patience, as for some reason I am not receiving email alerts about new messages in this thread, or private messages I am receiving.
Thanks again guys for the gift of making my device work as it should
bx3m said:
Hi all,
First, many thanks to those that replied to this thread, I know you must me tired of this kind of question - how do I...?
Second, I'd like to thank LetMeKnow for his efforts to help me with this issue. Turns out he does have a formula for success regarding this device, which I've applied and I am very happy with the result.
I've managed to install Cromi-X 5.4 ODEX version, converted the filesystem from ext4 to f2fs, then applied @LetMeKnow's fix (which he has prepared for me) and now I can honestly say that I am finnaly looking at this device as a real tablet
What I've described here are the steps I've made in general, but if anyone wants a detailed description, just ask and I will share all information with you. Please have a little patience, as for some reason I am not receiving email alerts about new messages in this thread, or private messages I am receiving.
Thanks again guys for the gift of making my device work as it should
Click to expand...
Click to collapse
I'm interested in the methods you applied. Do you mind sending me a small write up? Your help is greatly appreciated.
bx3m said:
Hi all,
First, many thanks to those that replied to this thread, I know you must me tired of this kind of question - how do I...?
Second, I'd like to thank LetMeKnow for his efforts to help me with this issue. Turns out he does have a formula for success regarding this device, which I've applied and I am very happy with the result.
I've managed to install Cromi-X 5.4 ODEX version, converted the filesystem from ext4 to f2fs, then applied @LetMeKnow's fix (which he has prepared for me) and now I can honestly say that I am finnaly looking at this device as a real tablet
What I've described here are the steps I've made in general, but if anyone wants a detailed description, just ask and I will share all information with you. Please have a little patience, as for some reason I am not receiving email alerts about new messages in this thread, or private messages I am receiving.
Thanks again guys for the gift of making my device work as it should
Click to expand...
Click to collapse
I am glad that your device is working the way that you like it....
BTW, I just noticed that the zip that I created for you was not optimized in term of "Random write" priority comparing to the read process. It can be further improving the performance on the multi-task if you can find the optimal point/balance between the two processes. Also, I just played around with the f2fs on the /cache partition and seems like there is a slightly improvement over all on the device. Please let me know if you like to test out this new improvements on your device. It is just a simple update on your device and you are good to go...
Cheers,
LMK
i'm very interested in this. i'm tired of flashing every time i want it to act right for a week. my internal file system has already been convered to f2fs.
asus sucks<3 said:
I'm interested in the methods you applied. Do you mind sending me a small write up? Your help is greatly appreciated.
Click to expand...
Click to collapse
Hey there,
I am qouting here the indications the @LetMeKnow sent me, all credits goes to him. I have not encountered any kind of issue.
Check list:
1. Cromi-X v5.4
2. Apex launcher
3. Asus browser ( special tweaks on this browser and it is very fast)
To do before installing my tweaks:
1. Backup your current setup in the twrp, just in case some issues are occurred
2. Go here and Delete all the files in this directory "/system/etc/init.d" except this file "50CleanTWEAKS"
3. Go to "Asus system Settings": Under Wi-Fi, Advanced Wi-Fi
1. Set "Keep Wi-Fi on during sleep" to "Only when plugged in"
2. Uncheck the box "Wi-Fi optimization"
4. Go to "ASUS customized setting" and Uncheck the box "Enable smart backlight adjuster"
5. Go to the Asus browser Advanced setting and Uncheck these boxes: "Fast Scroller" and "Dim the screen while website loads"
This I'm not sure how it would go for you, @LetMeKnow made this built for my device, so I would ask him prior to installing it
6. Download my Zip file here:
https://onedrive.live.com/redir?resi...int=file,zip
Reboot into the TWRP and setup the f2fs before installing my zip:
1. Under "Wipe", "Advanced Wipe": Select only "Data" partition and make sure that all others boxes are Unchecked
2. Click on "Repair or Change File System"
3. Click on "Change file System"
4. Click on "F2FS"
5. "Swipe to Change" to format your /data partition with f2fs
6. Back Home and Select "Install"
7. Browse to my downloaded zip file
8. Uncheck the box "Zip file signature verification?"
9. Swipe to install
10. Reboot to system and enjoy your new tf700t
Hope it helps
LetMeKnow said:
I am glad that your device is working the way that you like it....
BTW, I just noticed that the zip that I created for you was not optimized in term of "Random write" priority comparing to the read process. It can be further improving the performance on the multi-task if you can find the optimal point/balance between the two processes. Also, I just played around with the f2fs on the /cache partition and seems like there is a slightly improvement over all on the device. Please let me know if you like to test out this new improvements on your device. It is just a simple update on your device and you are good to go...
Cheers,
LMK
Click to expand...
Click to collapse
Good morning (here ),
That would be interesting to try - would I just convert the /cache to f2fs? Or ...?
bx3m said:
Hey there,
I am qouting here the indications the @LetMeKnow sent me, all credits goes to him. I have not encountered any kind of issue.
Click to expand...
Click to collapse
First, thanks for mentioning my name on this BUT I would like to clarify that I have nothing to do with the ROM and Kernel.... The Cromi-X was developed by @sbdags and the kernel was developed by @Hundsbuah. Please thanks them instead of me. I just tweak/change the setting to my preferences on the device and would like to share if someone is interested in it...
Second, you did a great job in sharing the information and please keep helping others users if they needed, thanks...:good:
bx3m said:
This I'm not sure how it would go for you, @LetMeKnow made this built for my device, so I would ask him prior to installing it.
Click to expand...
Click to collapse
If he/she is using the WW bootloader then he/she is fine with this zip because there are some changes in the build.prop and needed to update. However, if he/she is using the US bootloader, then he/she needs to install the US zip instead of your zip...
bx3m said:
Good morning (here ),
That would be interesting to try - would I just convert the /cache to f2fs? Or ...?
Click to expand...
Click to collapse
Yes, you need to convert your /cache to f2fs and update the fstab.cardhu. I will upload the new zip for you if you would like to test it out. It would be better in my opinion...
---------- Post added at 10:24 AM ---------- Previous post was at 10:23 AM ----------
iateshaggy said:
i'm very interested in this. i'm tired of flashing every time i want it to act right for a week. my internal file system has already been convered to f2fs.
Click to expand...
Click to collapse
Did you check your PM?
probably i tried every tf700 rom and my opinion cromix 5.4 (4.2.1) + Kernel & Tweaks Installer v5.2 _sdbag (second kernel) stock web browser
@LetMeKnow - hm, I could swear that I saw your name in the kernel name, next to sdbags ... I might me mistaking though ... But ofcourse, thanks to all those involved in this development. I can definitely try to help anyone that asks for my help And yes, please, if you could find the time to create this new zip, I will give it a try. But unlike last week, it can wait until you have some spare time on your hands, so don't worry too much about making it now or ...
Hi - is there any chance of having a copy of the zip file mentioned as I'd really like to give these instructions & the software mentioned a go on my device? Many thanks in advance.
bx3m said:
@LetMeKnow - hm, I could swear that I saw your name in the kernel name, next to sdbags ... I might me mistaking though ... But ofcourse, thanks to all those involved in this development. I can definitely try to help anyone that asks for my help And yes, please, if you could find the time to create this new zip, I will give it a try. But unlike last week, it can wait until you have some spare time on your hands, so don't worry too much about making it now or ...
Click to expand...
Click to collapse
No, you are correct.. @sbdags added my name in his change log because he used some of my Tweaks in his Cromi-X v5.4 released... Any way, as long as the ended users are benefited from it. It is all matters, I guessed...
---------- Post added at 10:13 AM ---------- Previous post was at 10:11 AM ----------
Deroyentz said:
Hi - is there any chance of having a copy of the zip file mentioned as I'd really like to give these instructions & the software mentioned a go on my device? Many thanks in advance.
Click to expand...
Click to collapse
Are you referring to me? I will try to upload the new zip file with /cache using f2fs when I am off work....
Cheers,
LMK
Version 3.0 for Cromi-X!
A few more important notes to add:
- You must do a clean installation with the Cromi-X v5.4. A format of your /data partition is preferred or at least a full wipe of your /data partition which means everything on your internal data including your /media. No f2fs conversion at this point, all partitions must be ext4 when you install the fresh Cromi-X.
- Please select only minimal apps for your core system apps during the ROM installation and install others apps from google store so they are resided on the /data partition instead of /system partition.
- Please select Hund's kernel during the installing process.
- After the installation of Cromi-X completed, you need to boot into system and update everything the Apex launcher only from the google store. Otherwise, your device will be in a bootloop...
- Please go to post #12 for the rest of the instructions of how to install and convert your partitions with f2fs...
- File definitions:
- US is for US bootloader
- WW is for WW bootloader
- Data_f2fs is only for /data partition with f2fs
- Data-Cache_f2fs is for both /data and /Cache with f2fs
Note: There is a patch that further improves the overall performance on your device. It is on page #5 and post #41. Please backup your current setup in twrp and install both patches in the same session, thanks. Also, there is a patch to fix the exfat filesystem on page #12 and post #109.
Have fun and enjoy your new tf700t....
thanks for the info lmk. sorry to take so long to respond. hopefully i'll have a few minutes i can devote in the near future (might be weeks or xmas, work is crazy).
Hello Letmeknow, first off, thanks for all the hard work you put into these tweaks! I really appreciate it as I have had nothing but a heart ache with this tablet and I paid 500 bucks for it when it came out =O. I need some help though, please. I'm stuck at the conversion process. After making the tweaks within CROMI, I rebooted into TWRP and went to format data, but I don't see an option for converting file system. Where can I find this? Maybe I missed something? Thanks in advance for your help!
Hello everybody,
I created a tool - initially for the nexus 9 (flounder|flounder_lte) - that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
I enhanced that tool to make it work for other devices too. (See the list below to see if your device is supported)
Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about the features in this tool
* before using it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Background
The Android CDD (Compatibility Definition Document) suggests demands that all devices with the appropriate horse power SHOULD MUST enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. Full-disk-encryption comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in current devices it's the CPU's task. Even though modern devices have quite fast CPU cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any scientific measurements though)
There is an ongoing discussion about this topic in cyanogenmod's gerrit for the nexus 9. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome. Additionally, Google's stock ROMs always have forced encryption enabled on newer devices.
Because performance is important to me and at least my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher).
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then, if necessary, it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
LG Nexus 5X (bullhead)
Huawei Nexus 6P (angler)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
v8 - Added support for LG Nexus 5X (bullhead) and Huawei Nexus 6P (angler)
What do I need to make this work?
A supported device
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
GibHub: https://github.com/gladiac1337/fed-patcher
XDA:DevDB Information
FED-Patcher, Tool/Utility for all devices (see above for details)
Contributors
gladiac, rovo89
Version Information
Status: Beta
Current Beta Version: v8
Beta Release Date: 2015-10-27
Created 2015-10-27
Last Updated 2016-10-23
Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently running stock Marshmallow on my Nexus 6 and i plan to stay like that, but would like to test my device with ForceEncrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.
cyberon said:
Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently on stock Marshmallow and i plan to stay like that, but would like to test my device with forcencrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.
Click to expand...
Click to collapse
Hi @cyberon,
good questions!
Yes, FED-Patcher works on stock! Marshmallow made it necessary to do a new release, v7, to get rid of an error message at boot but other than that, FED-Patcher works just fine on Android 6.
Well, I don't know how the monthly security-updates will be deployed. I guess it will be done by OTA (Over the Air) updates. OTA will probably not work after modifying the boot-image. However, flashing factory images should work just fine. Additionally, most of the time, OTA-zips are being posted here on xda or androidpolice whenever they become available so doing manual OTA updates is another possibility to do updates.
To get back to your question - wiping should not be necessary after an upgrade - be it via OTA or factory images. Google did a fantastic job with the upgrade-functionality in newer Android versions. However, whenever you do an update, be sure to run FED-Patcher afterwards because, in case the boot-partitions got updated, forced encryption will be in place again and on the first boot it will encrypt you device.
Well, I do all my tests on a HTC Nexus 9 (flounder). It is a pretty fast beast. However, on an unmodified stock rom, it was clearly tangible that the GUI had more latency than necessary. Apps loaded pretty slowly - compared to my Sony Xperia Z1 (honami) it took like twice as long to start youtube - and in general it just did not behave like a beast. This was why I started writing FED-Patcher. In my opinion it was worth my time. (it wasn't that much actually)
I hope I could help.
Enjoy, gladiac
Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Am i missing something?
cyberon said:
Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Click to expand...
Click to collapse
That's pretty much how I would do it. You don't even have to flash TWRP if you just skip flashing the recovery.img which is included in the factory-image package.
Thanks @gladiac, will try that way.
PS: I have a feeling that if we had this option added to a toolkit like Wugfresh Nexus Root Toolkit, it would be an instant success.
hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot
Worked on my N9 - thanks!
provolinoo said:
hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot
Click to expand...
Click to collapse
Hi @provolinoo,
well, FED Patcher will disable the forced encryption for you. However, SuperSU will not work so easily. The reason for that is that the stock ROM has SeLinux enabled in "enforcing" mode. SuperSU does not work without adding more SeLinux Policies to the stock ROM. Unfortunately, it's not in the scope of FED Patcher to add SeLinux policies for SuperSU. This should be done inside the flashable ZIP of SuperSU instead.
The last time I tested SuperSU with marshmallow stock was with version 2.52 BETA. It did not work. The result was a boot-loop because of one or more SeLinux denials. A little more info on that matter is here.
So, to get SuperSU working you would have to set SeLinux to "permissive" mode. Alternatively, you can use @Chainfire's boot.imgs to make SuperSU work.
Have fun, gladiac
Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9. Edit: I am using TWRP 2.8.7.1
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.
dmantilal said:
Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9.
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.
Click to expand...
Click to collapse
I agree, I love CM roms but their decision to force encryption when most of cm users are power-user is a nonsense
Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.
jamesalfred said:
Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.
Click to expand...
Click to collapse
Did you follow the directions and format the entire "data" partition?
dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.
nextelbuddy said:
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.
Click to expand...
Click to collapse
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).
dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
dmantilal said:
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).
Click to expand...
Click to collapse
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?
nextelbuddy said:
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?
Click to expand...
Click to collapse
Side-loading the OTA then following that with a FED flash seems much safer.
Loading an OTA directly would over-write the boot.img with a ForceEncrypt boot.img, logically Forcing Encryption (derp) at boot.
I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?
jamespat93 said:
I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?
Click to expand...
Click to collapse
You can if you want But if you want to unencrypt your phone, backup your ROM, copy sd content to your computer, wipe everything! in recovery (twrp) including Format Data, Factory reset, internal storage etc. Connect your phone while in recovery to your computer (you'll see 25.98GB instead of 23.03GB), copy sd content back to your phone, restore your rom backup and you'll be fine.
I can't get it work on Nexus 6 and chroma rom r26.
My steps: wipe everything, push folder (rom,patcher and gapps), flash chroma, flash gapps, flash patcher, wipe everything but system
after boot in setting/security it is again encrypted. what I am doing wrong?
Samsung J120W -exynos 3475
This is a Stock ROM of Samsung J1 Canadian it's pre-rooted and busyboxed . Lots of space after I debloated it . People are free to do whatever they want with this ROM . I'm working on porting MIUI 8 right now but having trouble booting up . If anyone wants to help me with MIUI send me a pm and I'll upload it .
-Deodexed
-De-bloated
-Deknoxed
-Busybox and Rooted
google drive
https://drive.google.com/file/d/1S35WyQFccuOt6hZD6FADCPDJwVhm8EjP/view?usp=sharing
Duanepiche99 said:
Samsung J120W -exynos 3475
This is a Stock ROM of Samsung J1 Canadian it's pre-rooted and busyboxed . Lots of space after I debloated it . People are free to do whatever they want with this ROM . I'm working on porting MIUI 8 right now but having trouble booting up . If anyone wants to help me with MIUI send me a pm and I'll upload it .
-Dedeodexed
-De-bloated
-Deknoxed
-Busybox and Rooted
google drive
https://drive.google.com/file/d/1S35WyQFccuOt6hZD6FADCPDJwVhm8EjP/view?usp=sharing
Click to expand...
Click to collapse
Hello. I would like to try this one out! By "debloating" what has been removed? Also, do I just flash the file within TWRP once performing a full wipe except external sd card? Is this Android 5.1.1 or 6.0.1? Thanks!
All the unnecessary stuff . and All the Google stuff except play store . And it's 6.0 marshmallow
Duanepiche99 said:
All the unnecessary stuff . and All the Google stuff except play store . And it's 6.0 marshmallow
Click to expand...
Click to collapse
Ok thanks for the reply!
Duanepiche99 said:
All the unnecessary stuff . and All the Google stuff except play store . And it's 6.0 marshmallow
Click to expand...
Click to collapse
Any pointers on installing through TWRP. Just wondering which partitions to wipe before flashing.
Just do a regular factory wipe threw TWRP . That's it .
i have a chatr phone thats a j120w thats got a problem with frp lock. will this help me around my problem?
spent seven hours trying to fix it last night and couldnt get it done, custom binary blocked by frp lock, impossible to access the internal storage and can't run anything off the sd card. cant get twrp or SR1-SuperSU-v2.78-SR1-20160915123031 onto the phone
DaDirtiest said:
i have a chatr phone thats a j120w thats got a problem with frp lock. will this help me around my problem?
spent seven hours trying to fix it last night and couldnt get it done, custom binary blocked by frp lock, impossible to access the internal storage and can't run anything off the sd card. cant get twrp or SR1-SuperSU-v2.78-SR1-20160915123031 onto the phone
Click to expand...
Click to collapse
i had this issue too a few months back i might be bit late but for others looking in the future go to updato.com and search your model# then install your stock firmware and flash it on odin3 boot into downloaders mode too
Duanepiche99 said:
Just do a regular factory wipe threw TWRP . That's it .
Click to expand...
Click to collapse
How do you install twrp without recovery img can't find one for j120W anywhere including TWRP Site
can you modify the ROM so that it can be installed on the J120G?
keithk said:
How do you install twrp without recovery img can't find one for j120W anywhere including TWRP Site
Click to expand...
Click to collapse
A bit late maybe, but I use this recovery and even though a little dusty for some at 3.0.2 it works the best out of any i've tried. Also using SM-J120W.
Unzip and flash the .tar in odin.
FIle
Duanepiche99 said:
Samsung J120W -exynos 3475
This is a Stock ROM of Samsung J1 Canadian it's pre-rooted and busyboxed . Lots of space after I debloated it . People are free to do whatever they want with this ROM . I'm working on porting MIUI 8 right now but having trouble booting up . If anyone wants to help me with MIUI send me a pm and I'll upload it .
-Deodexed
-De-bloated
-Deknoxed
-Busybox and Rooted
google drive
https://drive.google.com/file/d/1S35WyQFccuOt6hZD6FADCPDJwVhm8EjP/view?usp=sharing
Click to expand...
Click to collapse
Please @Duanepiche99, i need this file. In google i don't found...
Bye
todonormal said:
Please @Duanepiche99, i need this file. In google i don't found...
Bye
Click to expand...
Click to collapse
Get linux and put stock into superr's kitchen.
Works flawlessly and if you have any questions pm me. Or i'll do one for you tomorrow. It takes the addiction to a new level and you have control.
mindlery said:
Get linux and put stock into superr's kitchen.
Works flawlessly and if you have any questions pm me. Or i'll do one for you tomorrow. It takes the addiction to a new level and you have control.
Click to expand...
Click to collapse
@mindlery : Please, i need your help. This it's the rom: https://www.sammobile.com/samsung/g...e/SM-J120W/RWC/download/J120WVLS2AQK1/198146/ I need Deodexed, De-bloated, Deknoxed, Busybox and Rooted in spanish (if it's possible, rom not include. English it's other option). I don't know superr's kitchen, and i don't have linux in this moment. Thank you very much for your help
NOTE: i found a procedure for change language, in other model, but i don't know if it's possible with it's procedure:
https://www.clangsm.com/forum/index.php?showtopic=487032
todonormal said:
@mindlery : Please, i need your help. This it's the rom: https://www.sammobile.com/samsung/g...e/SM-J120W/RWC/download/J120WVLS2AQK1/198146/ I need Deodexed, De-bloated, Deknoxed, Busybox and Rooted in spanish (if it's possible, rom not include. English it's other option). I don't know superr's kitchen, and i don't have linux in this moment. Thank you very much for your help
NOTE: i found a procedure for change language, in other model, but i don't know if it's possible with it's procedure:
https://www.clangsm.com/forum/index.php?showtopic=487032
Click to expand...
Click to collapse
Hey. Sorry for being so late to reply.
Fell on some hard times. I'll do my best in the next week to help you out if you still need it.
But doing pretty bad over here.... i'll be ok and all, just my situation is not good. Take care and let me know, bud.
mindlery said:
Hey. Sorry for being so late to reply.
Fell on some hard times. I'll do my best in the next week to help you out if you still need it.
But doing pretty bad over here.... i'll be ok and all, just my situation is not good. Take care and let me know, bud.
Click to expand...
Click to collapse
Thank you for your response. I wait what better your situation
I install virtualbox, ubuntu4kitchen and i can create deoxeded, root, debloated, but it's very large. More what original...
todonormal said:
Thank you for your response. I wait what better your situation
I install virtualbox, ubuntu4kitchen and i can create deoxeded, root, debloated, but it's very large. More what original...
Click to expand...
Click to collapse
That's odd.
The way i do linux is to have a preset unallocated disk partition in windows.
Since i often "wreck" my set up by constant tweaking, i always install windows by wiping all partitions and leaving half the disk unallocated.
But! You can shrink your windows disk partition in disk management within windows. So for example if your windows hd is one partition and 500 gb, maybe cut it down to 300 gb leaving 200 gb unallocated.
You can then do a restart while holding shift until you get a recovery screen.
Of course, prior to the shift/restart mode you'll have prepared already a USB flash drive with linux (mint is very user friendly) from a program called rufus...
Seems a bit much but really all you're doing is preparing a linux OS to usb that you boot into, then install. It'll automatically choose the unallocated partition. So, when proceeding with install by default linux will have the option to install alongside windows highlighted. Of course then continue.
Any more questions feel free to ask. It's a bit daunting at first but overall a very simple process.
The only part you may have difficulty with is dependent on your file choice in rufus. Try default settings and if GPT fails do it over with MBR.
---------- Post added at 05:44 AM ---------- Previous post was at 05:38 AM ----------
May i add, once you have linux you can try the free version of superr and it is great for what you want to do.
Download link shows Error 404 Not Found
Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator
Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?
asassello said:
Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?
Click to expand...
Click to collapse
1 : yes
2 : yes..update maybe your modem
re 1: yes2 (using it quite some time on various devices and it seems to do what I expect it should do, though some apps seem to bypass the 'normal' DNS resolution. OT: And I'm still haven't made up my mind yet if DoH or DoT are good or bad ...)
re 2: dark mode? What's that?
rayman95 said:
1 : yes
2 : yes..update maybe your modem
Click to expand...
Click to collapse
Are you sure NFC works? I mean paying in shops? I updated modem and now it's N9005XXUGPQB1. And paying still doesn't work. I've just tried.
odoll said:
re 2: dark mode? What's that?
Click to expand...
Click to collapse
Sorry. It's dark theme (I don't have English set as default language). [emoji846]
installation error
https://download.lineageos.org/hltetmo
Can somebody please confirm that paying through NFC works? If so - what's your modem and baseband?
Also I've installed GAPPS PICO maybe that's the case? Although on LOS 16 I also had Pico and it worked, but maybe I'm missing some app like Google search or something?
Been using Lineage OS 16 ever since it was officially released for HLTE. I gotta say, the development of that release has came a long way and by the time of writing this, I'd say it's the most stable and clean custom rom for the Note 3 out there.
I did try the new release the second I received a notification for an update. How did it go? Well let's just say I'm glad I created a full system backup before wiping LOS 16. This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
I do appreciate all of the time that the devs are still willing to put into the platform. However I'd recommend users that are looking for a rock stable experience to stick with Lineage OS 16 for the time. You're not missing out on a lot.
loudseries said:
This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
Click to expand...
Click to collapse
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx
odoll said:
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx
Click to expand...
Click to collapse
I have to agree with you, because except my 2 issues (with NFC payments and night mode that doesn't switch automatically) I actually don't have any other problems.
Ver. 17 seems faster and snappier than 16.
Also on 16 sometimes sharing from ie. Firefox to WhatsApp caused the later one not loading (just black screen).
So for me only that NFC seems to be a real issue. Other than that I'd advice anyone trying 17.
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
for me the only difference is the size of the home screen changed (changed trebuchet to a larger grid before), otherwise i would not even have noticed it is not 16 anymore, rock stable even after a dirty flash
rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect.
Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?
Scorpionea said:
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect. Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?
Click to expand...
Click to collapse
I'm on PQB1 nordic modem and BRL1 bootloader.
rayman95 said:
I'm on PQB1 nordic modem and BRL1 bootloader.
Click to expand...
Click to collapse
Have the same as you . I thought it could be bootloader issue but guess not.
Thx
Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...
odoll said:
Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator
Click to expand...
Click to collapse
Hello. I have the latest version of LineageOS 16 installed and TWRP (3.3.1.0). I ask you if, after transferring the ROM file to the phone, it is possible to use TWRP to upgrade to 17.1 (by installing the zip file) or if I have to use ADB shell (as it says on the LineageOS official site).
Sorry I'm not an expert and some steps are not clear to me
Thank you
PS
Why you wrote "dirty"
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Hi Apten
i) think your Qs won't need a full quote
ii) drity flashing
iii) sure you can DL the ROM (and TWRP) to your (internal RAM) of your phone and upgrade or clean install from recovery (twrp)
rayman95 said:
Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...
Click to expand...
Click to collapse
I've just dirty updated from 1010 to 1017 build . Will see how it goes later on.
Just tested with chrome downloading lineage and no issue with Fc
Is there any benefit to doing so? You're nuking your security and that's basically it.
Am I missing something?
HeliX99 said:
Is there any benefit to doing so? You're nuking your security and that's basically it.
Am I missing something?
Click to expand...
Click to collapse
At least one point is that custom recoveries cant decrypt /data on Android 12 based ROMs. So it is just necessary.
kosmatyj said:
At least one point is that custom recoveries cant decrypt /data on Android 12 based ROMs. So it is just necessary.
Click to expand...
Click to collapse
I've read in an Arrow OS flashing guide a step that says "[OPTIONAL] Download the latest version of Encryption Disabler". The "optional" part confuses me, can you flash a rom *without* disabling encryption or does it say "optional" because you could use a different tool for the job?
HeliX99 said:
I've read in an Arrow OS flashing guide a step that says "[OPTIONAL] Download the latest version of Encryption Disabler". The "optional" part confuses me, can you flash a rom *without* disabling encryption or does it say "optional" because you could use a different tool for the job?
Click to expand...
Click to collapse
"Optional" - means that you can use this ROM without encryption disabler as usual if you dont planning to do anything in recovery (rooting, backup, restore, etc.). If you are just a normal user with no extra requirements - forget about it. Just flash the ROM and enjoy.
A very useful optional way to see internal contents using twrp based recovery when your using android 12 rom which in current has not custom recovery working in android 12 encryption yet
Where can I read more about encription in android in general and changes in 12?
yasen6275 said:
Where can I read more about encription in android in general and changes in 12?
Click to expand...
Click to collapse
Android 12 | Android Developers
Android 12 now available. Try it today!
developer.android.com
The benefit of disabling encryption is, avoiding the need for formatting data every single time you install a new rom. Imo it's a life saver for anyone who has a lot of data stored on their internal storage.
AmmarHaseeb said:
The benefit of disabling encryption is, avoiding the need for formatting data every single time you install a new rom. Imo it's a life saver for anyone who has a lot of data stored on their internal storage.
Click to expand...
Click to collapse
Do you need to format the data for a "dirty" flash, ie upgrading your existing rom to a new update?
HeliX99 said:
Do you need to format the data for a "dirty" flash, ie upgrading your existing rom to a new update?
Click to expand...
Click to collapse
No you don't need to format data unless it is explicitly stated by the developer/maintainer.
Edit: To dirty flash, you can just use adb sideload (if you're using aosp based recoveries like Pixel Experience Recovery or ArrowOS recovery, or use and External Micro SD Card, or USB OTG (if you're using TWRP or OrangeFox)/
JSGuangco said:
No you don't need to format data unless it is explicitly stated by the developer/maintainer.
Edit: To dirty flash, you can just use adb sideload (if you're using aosp based recoveries like Pixel Experience Recovery or ArrowOS recovery, or use and External Micro SD Card, or USB OTG (if you're using TWRP or OrangeFox)/
Click to expand...
Click to collapse
Thanks for the info