Hi,
New PH-1 owner here. Just got the phone new from Amazon. It was on 7.1.1. Immediately it upgraded to 9.0, and then to 10, build QQ1A-200105.32 with Feb. security updates. Impressive! After reading through some (a lot) of the material collected about the phone, I decided that at first I'd only root it (i.e. without installing TWRP) with Magisk. After getting familiar with the two rooting guide ("[GUIDE] Rooting your Essential PH-1" and "[Guide] How to Install TWRP & Root Essential PH-1(Method 2)") I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
So, that's the status, and I'll welcome any and all advise on the above, but in the meantime, a question:
1 - If I flash this ('4.4.166-stock-twrp-mgk181.img') image will I loose Android 10,or the ability to have later upgrades?
Thanks!
MarSOnEarth said:
Hi,
New PH-1 owner here. Just got the phone new from Amazon. It was on 7.1.1. Immediately it upgraded to 9.0, and then to 10, build QQ1A-200105.32 with Feb. security updates. Impressive! After reading through some (a lot) of the material collected about the phone, I decided that at first I'd only root it (i.e. without installing TWRP) with Magisk. After getting familiar with the two rooting guide ("[GUIDE] Rooting your Essential PH-1" and "[Guide] How to Install TWRP & Root Essential PH-1(Method 2)") I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
So, that's the status, and I'll welcome any and all advise on the above, but in the meantime, a question:
1 - If I flash this ('4.4.166-stock-twrp-mgk181.img') image will I loose Android 10,or the ability to have later upgrades?
Thanks!
Click to expand...
Click to collapse
First, TWRP doesn't work well with latest stock ROM (QQ1A.200105.032), if you'd like to use TWRP, you should use one level down (QQ1A.200105.007)
Second, there's no more upgrade for this ROM, Essential stopped support it, and Feb update was the last one.
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?). So, not much interest in TWRP, just root.
Regarding 4.4.166-stock-twrp-mgk181.img: what Android version does it have, and when installed, can it be upgraded?
Thanks
MarSOnEarth said:
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?). So, not much interest in TWRP, just root.
Regarding 4.4.166-stock-twrp-mgk181.img: what Android version does it have, and when installed, can it be upgraded?
Thanks
Click to expand...
Click to collapse
Maybe I don't quite clear about your question, but why do you use that TWRP file?
I always use the official one from TWRP
https://twrp.me/essential/essentialph1.html
And regarding to Google update, as long as you don't use custom rom + microg then I believe you always get updated from Google Play store for your apps.
chanh2018 said:
Maybe I don't quite clear about your question, but why do you use that TWRP file?
I always use the official one from TWRP
https://twrp.me/essential/essentialph1.html
And regarding to Google update, as long as you don't use custom rom + microg then I believe you always get updated from Google Play store for your apps.
Click to expand...
Click to collapse
Ah, yes! My interest in 4.4.166-stock-twrp-mgk181 image is because, a) I failed to get root with Magisk, and b) this is a `fastboot` image that's already rooted (notice the mgk181 part of the name), BUT because it was made in January of 2019, I think (if it does, and I know too little to know that) it contains older version of Android, hence the question about whether I will be able to update from it.
Thanks
MarSOnEarth said:
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?).
Thanks
Click to expand...
Click to collapse
As I understand it Google will push some updates/security patches for Android via Play store but not everything, you still need updates from your manufacturer (which we now won't get) so you likely won't have all security patches, for this you need an up to date custom ROM like LineageOS (only at ver 9 pie currently) or maybe use the GSI (see Android 11 preview thread) but that is still in development at the moment so probably not suitable for daily use due to bugs & missing features.
MarSOnEarth said:
I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
Click to expand...
Click to collapse
I don't use TWRP, but I do have root, so if that's enough for you, see the steps below. Magisk version that you mentioned (v.20.3 and MMgr. v.7.5.1) works perfectly.
Since you are already on Feb update (the latest and the last one from Essential), you don't need the OTA zip. You only need the "PH1-Images-QQ1A.200105.032.zip" - the full fastboot image. Make sure you download and install the ADB/Fastboot from Essential website on your PC - it comes bundled with the Windows driver linked on their Developer page. Also make sure you have a good USB cable (do NOT use the one that comes with the phone!), and avoid using USB3 ports on your PC (use USB2 instead).
1. Extract boot.img from PH1-Images-QQ1A.200105.032.zip.
2. Install Magisk Manager, if not installed already.
3. Copy the extracted boot.img to the phone, then patch it with Magisk.
4. Copy the patched boot.img to PC.
5. Reboot the phone into bootloader.
6. Run the command "fastboot flash boot <your_patched_boot>.img" from your PC.
7. Reboot the phone.
8. Enjoy the root access.
IronRoo said:
As I understand it Google will push some updates/security patches for Android via Play store but not everything, you still need updates from your manufacturer (which we now won't get) so you likely won't have all security patches, for this you need an up to date custom ROM like LineageOS (only at ver 9 pie currently) or maybe use the GSI (see Android 11 preview thread) but that is still in development at the moment so probably not suitable for daily use due to bugs & missing features.
Click to expand...
Click to collapse
True. Eventually, a proper custom recovery, like TWRP, might be essential (har, har) years down the road (although I only now am coming down from a Moto X (first gen, 2013) that between AFWall and XPrivacy I managed to keep on stock firmware all along), but now I need to get this phone prepped up for daily use, and that means getting root first of all (and from kt-Froggy's note I shall... I see now where I goofed).
I appreciate your input. Thanks!
kt-Froggy said:
I don't use TWRP, but I do have root, so if that's enough for you, see the steps below. Magisk version that you mentioned (v.20.3 and MMgr. v.7.5.1) works perfectly.
Since you are already on Feb update (the latest and the last one from Essential), you don't need the OTA zip. You only need the "PH1-Images-QQ1A.200105.032.zip" - the full fastboot image. Make sure you download and install the ADB/Fastboot from Essential website on your PC - it comes bundled with the Windows driver linked on their Developer page. Also make sure you have a good USB cable (do NOT use the one that comes with the phone!), and avoid using USB3 ports on your PC (use USB2 instead).
1. Extract boot.img from PH1-Images-QQ1A.200105.032.zip.
2. Install Magisk Manager, if not installed already.
3. Copy the extracted boot.img to the phone, then patch it with Magisk.
4. Copy the patched boot.img to PC.
5. Reboot the phone into bootloader.
6. Run the command "fastboot flash boot <your_patched_boot>.img" from your PC.
7. Reboot the phone.
8. Enjoy the root access.
Click to expand...
Click to collapse
Thanks! From the above, it looks like I messed up on the very first step; I was giving Magisk the whole PH1-Images-QQ1A.200105.032.zip file and not the boot.img extracted from it. Oops!
MarSOnEarth said:
Thanks! From the above, it looks like I messed up on the very first step; I was giving Magisk the whole PH1-Images-QQ1A.200105.032.zip file and not the boot.img extracted from it. Oops!
Click to expand...
Click to collapse
That was my suspicion from how I read your post... ? Yeah, you need just the boot image extracted from the zip. The process is really simple, and it's been working for me with no issues, apart from one specific laptop where I was consistently getting errors for no apparent reason, so I just used other PCs.
kt-Froggy said:
That was my suspicion from how I read your post... Yeah, you need just the boot image extracted from the zip. The process is really simple, and it's been working for me with no issues, apart from one specific laptop where I was consistently getting errors for no apparent reason, so I just used other PCs.
Click to expand...
Click to collapse
OK, that worked splendidly. Thanks!
Related
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?
Few days ago as expected, official users (who is using CN-EN official ROMs) of Le Pro 3 AI (further mentioned "x7") got an OTA update to the latest release of EUI 6.0.030S.
The miracle that expected was not appeared. It is still based on Android 6.0.1 (Marshmallow).
The ROM is still not localized for other countries, it contains only CN and EN languages.
And there still many bloatware of LeEco services that is very annoyance.
But first of all, the apps inside are now more optimized and as I see, they starting and function faster then previously.
Ok, let's go to the main part - links =)
The Official Site where you can download the ROM based on OTA update scheme is HERE. Also you can download a copy of OTA package from HERE.
But if you want to download faster, you can use my clouds where I'm continuously holding the most of Official ROMs for x7.
---> MEGA (follow into the folder called "original_stock")
---> FEX
Inside my clouds you can find that the ROM filenames contains not only a version but also an appropriate suffix (_OTA or _FASTBOOT). It's used to separate the ROMs by the installation method.
The FASTBOOT prepared ROMs contains an installation scripts (.BAT for Windows and .SH for Linux/Mac) for not only full installation (with clearing of User Storage), but also for update (without clearing of User Storage).
Please be careful, don't even try to install via FASTBOOT without clearing of User Storage, if you currently have functioning non Official multilingual EUI like 5.9.027S (faked as 028S in menu "About phone") or other non official!!! If you'll do this you will get many conflicts in settings and apps.
I expect that the FASTBOOT updating instructions are widely known, but remind them once more:
1) Enable the "Developer options" menu by clicking on "Build number" 7 times in the "About phone"
2) In the "Developer options" menu, turn on "OEM unlocking" and "USB debugging"
3) Connect the phone to the computer with a USB cable
4) Run one of the installation scripts from the folder of the unpacked firmware
5) Immediately upon startup, allow on the phone screen the "USB debugging" permission for your computer, preferably within the checkbox "always trust this device"
6) Wait until the installation process finishes (15-20 mins), calmly referring to the fact that the phone itself will reboot into FASTBOOT mode, and also please ignore the Sparse format error message (it's normal)
7) The phone itself will reboot into a new OS ... the first launch will be very long
Please feel free to ask anything here about the installation process, cloud links etc.
But be ready that I'm not fast answering.
Any other questions including the comparison of EUI versions performance and functionality will be ignored by me.
We still have the device that is highly secured with unknown protection mechanism and that gets us unable to build any quality custom ROM. =|
thank you
I should have researched before buying the device kk was already "lost" trying to find a customized rom for him. this part of the text: "We still have the device that is highly secured with unknown protection mechanism and that gets us unable to build any quality custom ROM. =| " , clarified me a lot
I istalled it but it does not have google play store?
azizo07 said:
I istalled it but it does not have google play store?
Click to expand...
Click to collapse
ROM does not have Google applications. You need install it. I think this still working in this version: https://forum.xda-developers.com/le-pro3/leeco-le-pro3-a1-model-x651-guides-development--and-mods/automated-installer-gapps-morelocale2-t3752576
Ok installed the 30s mod version from https. ://4pda.ru/forum/index.php?showtopic=895159&st= 2020#entry77308634
and it includes gapps.
You can install another launcher to get rid of ads.
There is no root for this rom, right?
azizo07 said:
Ok installed the 30s mod version from https. ://4pda.ru/forum/index.php?showtopic=895159&st= 2020#entry77308634
and it includes gapps.
You can install another launcher to get rid of ads.
There is no root for this rom, right?
Click to expand...
Click to collapse
030S mod is based on APKs of 030S with few modifications... but it also runs the old Boot from version 027S... so it may have some unexpected behavior...
yes, all of these ROMs have no root... but with mods based on Boot of 027S version you can use a temporary root (one time booting into TWRP) for further system modifications and then back to boot with native stock kernel and modified system will run good (expect the problems with apps you may cause by modifications)
hi, how i can install this ROM if I use a non official Rom? I mean, I recived this phone yesterday with a 028s (stable) that is non official, and I want to install this official ROM.
Help please
My cell phone has brick
You have some rom to fix it?
Does the NFC work on this rom? I had 028s before but the NFC was disabled.
Hi im install rom eui 6.0.030s "https://4pda.ru/forum/index.php?showtopic=895159&st=2020#entry77308634"]https://4pda.ru/forum/index.php?showtopic=895159&st=2020#entry77308634 But me phone have in antutu 50000 . Ealier was 100000. What is wrong i see Stock-thermal.zip but i cant dowload . plise help
can't see inside the package "4) Run one of the installation scripts from the folder of the unpacked firmware"
or can i use rename the package to update.zip and run on the system update?
cyzarine said:
can't see inside the package "4) Run one of the installation scripts from the folder of the unpacked firmware"
or can i use rename the package to update.zip and run on the system update?
Click to expand...
Click to collapse
What you can't see? The scripts?
You need to look at the contains of unpacked ROM zip that have suffix "FASTBOOT" in filename. There must be files with names like "x7_fastboot_tool.bat" and "x7_fastboot_tool_noUser.bat" and also same files with ".sh" extensions for Linux.
For installation to start you need to run one of this scripts. To run from CLI (CMD), not by double-clicking on it.
what's the score in antutu in new rom ? I have 50000....
dilnix,
I've downloaded the FULL_X7_X7-CN-FN-KGXCNFN6003009091S-6.0.030S.zip which don,t have the fastboot tools.
Do you have instructions to install this?
Big thank you!
cyzarine said:
dilnix,
I've downloaded the FULL_X7_X7-CN-FN-KGXCNFN6003009091S-6.0.030S.zip which don,t have the fastboot tools.
Do you have instructions to install this?
Big thank you!
Click to expand...
Click to collapse
This is an OTA package. But it's buggy, my try to make a direct update from 028S to this 030S with OTA way was failed, and I heart many reviews about same behavior.
So I think the best way to update is to use Fastboot with scripts and executable provided in my package that contains "_FASTBOOT" suffix in filename.
From there you can use script "x7_fastboot_tool_noUser.bat" (or .sh option in Linux) to make update to 030S (only from clean stock 025S, 026S or 028S, not from fake 027S or any mod) without clearing of Userdata Storage.
Or you can use script "x7_fastboot_tool.bat" (or .sh option in Linux) to make a new installation of 030S with clearing of Userdata Storage (from any other previous ROM).
If you can't download by my links provided in topic, please write here and I'll try to solve this.
grzegorzkuc said:
what's the score in antutu in new rom ? I have 50000....
Click to expand...
Click to collapse
My x650 shows 87000 in antutu on 030S. I can't know what is reason you having less.
Currently my Le pro 3 ai is on non official 5.9.27s I have to downgrade it to 5.9.25s.what should I do. Further I want to update my device to eui 6.0.30s. Any help is highly appreciated .
I think that is 027s custom rom better than this 028s. I recommend you to not change anything.
Sent from my LEX657 using Tapatalk
AmanS99 said:
Currently my Le pro 3 ai is on non official 5.9.27s I have to downgrade it to 5.9.25s.what should I do. Further I want to update my device to eui 6.0.30s. Any help is highly appreciated .
Click to expand...
Click to collapse
As an example of this way how to move into stock 028S with flashing first 025S and then just update to 028S (or 030S if you want) I prepared a video half of year ago. HERE
I understand that not all processes there are perfect... for example I used ADB to push ROM instead of MTP that is much faster =)
But if you have experience and you sure in other option of processing the steps explained in this video - enjoy and good luck.
Hope it will help somebody.
P.S.: Now I have some trouble with focus (can't focus larger then 120 cm) in stock Camera on EUI 030S and have a plan to get 028S back just for testing of Camera and focus processing.
P.S.2.: If you will have desire to get back into custom 027S you had earlier, you always can make it. It's available on both forums (XDA & 4pda). But you need to know, that changing of using between clean stock and custom ROMs is always requires you to clean a Userspace too.
Thanks for your reply . But I want to ask is there is risk of getting brick if anything goes wrong.
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.- Don't worry about taking the battery out when the tutorial says to.- If you have issues with the driver provided in the download, try these. (Run dpinst.exe) - Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time - Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Kernel Source: here
Just yesterday I've dusted off this tablet, and so I was browsing the forums to see what rom I can put inside, and lickily, about the same time this thread was created! Installing it right now, gonna post a follow-up once I'm finished tinkering with it.
OK, firstly wanna thank you for this awesome rom, it's stable and fast, no major issue with it. What I did find, however, is that the camera flash is not working along with the night mode which is not turning on. Besides those two issues, everything seems to be in working order
Cheers!
LukaHM said:
OK, firstly wanna thank you for this awesome rom, it's stable and fast, no major issue with it. What I did find, however, is that the camera flash is not working along with the night mode which is not turning on. Besides those two issues, everything seems to be in working order
Cheers!
Click to expand...
Click to collapse
Thanks for the report.
Camera flash? My A7600 Does not have a flash. No actual LED to produce a flash.
As for the Night mode, I have ported a lot of ROMS to this device and I havn't ever seen the night mode work right. If I even do get it to turn on, it lags the whole device.
SaberShip said:
Thanks for the report.
Camera flash? My A7600 Does not have a flash. No actual LED to produce a flash.
As for the Night mode, I have ported a lot of ROMS to this device and I havn't ever seen the night mode work right. If I even do get it to turn on, it lags the whole device.
Click to expand...
Click to collapse
Haha, I've turned the damn thing over, looked at the sensor, and you're right. Havent actually used this device previously to know about it, so glad we have that one sorted out!
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
---------- Post added 08-02-2019 at 12:38 AM ---------- Previous post was 07-02-2019 at 11:57 PM ----------
caoiveen said:
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
Click to expand...
Click to collapse
So I put in an sd card and I then had option to save to downloads or sd. I still could not select downloads but I could select sd card which is worrying for me now. Thanks again Sabership. Nice work
caoiveen said:
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
---------- Post added 08-02-2019 at 12:38 AM ---------- Previous post was 07-02-2019 at 11:57 PM ----------
So I put in an sd card and I then had option to save to downloads or sd. I still could not select downloads but I could select sd card which is worrying for me now. Thanks again Sabership. Nice work
Click to expand...
Click to collapse
What app are you using? I have not seen any issues with downloading yet. If you see 10.43Gb it sounds like your internal storage is formatted correctly. I haven't seen any download issues with Firefox and ES-File Explorer.
Unable to flash firmware - because unable to install Android USB driver on Windows 10
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
D2sx34 said:
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
Click to expand...
Click to collapse
Main post updated with signed drivers. Please try it now.
Thank you @SaberShip!
The installation of Resurrection Remix 5.8.5 was successful after installing the signed Android USB driver!. System is stable and fast. Thank you again.
App issues:
1. Netflix app (not available on playstore, but at netflix web site) works online, but does not allow video downloads.
Netflix diagnostic error for download is OF.NA.4 -which probably means device does not meet security requirements. ? any workarounds?
// Amazon Prime video works, with offline video downloads as well. Google chrome works. Tried other apps as well.
Documentation issues (minor):
1. "- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)" --> Google Apps Super package did not install since the device ran out of space (error 70). Google Apps "Nano" worked.
System issues:
1. Wifi still does not auto-reconnect after Wireless Access Point is rebooted, but given that this has happened with different ROMs I am concluding it is due to a hardware issue with this device (and not ROM specific).
// Skype camera issue fixed. Camera image is NO longer upside down.
D2sx34 said:
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
Click to expand...
Click to collapse
Netflix app not working on ROM due to Widevine DRM
Great job on the ROM!! - it is fast and stable.
I have been investigating why the <latest> Netflix app with offline download capability does not work with Resurrection Remix 5.85 ROM.
I found that some other ROM has similar problem, and it was caused because Widevine DRM was not supported. Netfix (latest app and offline download) started working after Widevine DRM support was added to that ROM.
Is it possible to support Widevine DRM in this ROM?
Here is the quote from another ROM:
"Quote:
Originally Posted by Federek
I recently found out the reason why after opening the Netflix app it shows the error "this app is not compatible with your device". The only workaround right now is to download an old APK directly from Netflix website (it doesn't support the feature of downloading movies). After some digging, I'm pretty sure the error is due to the fact that on, I think any Oreo rom available for bacon, Widevine Drm is not supported (as u can see in the screenshot below). I think it's connected to the files in the screenshot below, but I didn't manage to find a solution. I believe it must be implemented by someone directly in the rom code (I'm absolutely not an expert). I'm also sure it's not connected with root or anything else (the Netflix app is available in the play store for me).
(sorry is my first post)
[/IMG]"
SaberShip said:
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.
- Don't worry about taking the battery out when the tutorial says to.
- If you have issues with the driver provided in the download, try these. (Run dpinst.exe) - Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time - Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Click to expand...
Click to collapse
SaberShip, thank you for all your work and caring about the A7600-F! Your instructions are clean and elegant. It's great to be able to install your ROM without root. It looks and performs great.
I installed your ROM a week ago. Unfortunately, I've spent much time since then trying to get NordVPN to work. It worked fine on the stock version of my tablet. Now, it connects to NordVPN servers, but fails to adopt the remote IP address (whatismyv6.com reports my ISP IP).
I've exhausted [email protected] I'd be grateful for any pointers you might have.
Hello,
so i will thank Sabership, too, for his new build. I went the way as most builds are normally flashed - reboot from AIM build into TWRP, did a factory reset, and flashed RR and a new GApps build. Everything went fine, i am just typing on it. The bug with WiFi not connecting automatically i am hoping will be gone, it was the only bug i found in AIM for me.
One question: the security patch date is of November 2017. Will there be an update (as asked in AIM, too)?
Regards
jfaheyfan said:
SaberShip, thank you for all your work and caring about the A7600-F! Your instructions are clean and elegant. It's great to be able to install your ROM without root. It looks and performs great.
I installed your ROM a week ago. Unfortunately, I've spent much time since then trying to get NordVPN to work. It worked fine on the stock version of my tablet. Now, it connects to NordVPN servers, but fails to adopt the remote IP address (whatismyv6.com reports my ISP IP).
I've exhausted [email protected]. I'd be grateful for any pointers you might have.
Click to expand...
Click to collapse
I believe VPN connectivity may have been one of the issues with the original ROM even before I ported it to the A7600F. Therefore, there isn't much I can do unfortunately.
If you absolutely need VPN, your options are to use Stock ROM or find a different ROM that has VPN working. Another possible workaround is to setup NordVPN on your router or whatever gateway is between you and the internet: https://support.nordvpn.com/Connectivity/Router/1047409322/Setting-up-a-router-with-NordVPN.htm
Catfish78 said:
Hello,
so i will thank Sabership, too, for his new build. I went the way as most builds are normally flashed - reboot from AIM build into TWRP, did a factory reset, and flashed RR and a new GApps build. Everything went fine, i am just typing on it. The bug with WiFi not connecting automatically i am hoping will be gone, it was the only bug i found in AIM for me.
One question: the security patch date is of November 2017. Will there be an update (as asked in AIM, too)?
Regards
Click to expand...
Click to collapse
I have witnessed wifi disconnection issues on every ROM I've ever ported/used for this device aside from Stock I wish there was more that I could do. As mentioned in the title and before, this ROM is ported from another device. What this means is that I don't have the source code and therefore cannot update things like Android security patch dates. If this were a ROM built from source, I would simply have to sync with updated RR sources to get the new patches and RR bugfixes/features. To do it with a port, I need to find a whole new ROM with the updated sources and then port the whole ROM over to this device again. That is just too much work.
As a side note, I had intended this to be the last ROM I ported for this device due to its age, however If there is enough demand and I can find one, maybe someday I will port a more updated Oreo ROM to this device. Good quality MT6582 Oreo ROMs built from source are still not really common.
SaberShip said:
I believe VPN connectivity may have been one of the issues with the original ROM even before I ported it to the A7600F. Therefore, there isn't much I can do unfortunately.
If you absolutely need VPN, your options are to use Stock ROM or find a different ROM that has VPN working. Another possible workaround is to setup NordVPN on your router or whatever gateway is between you and the internet: https://support.nordvpn.com/Connectivity/Router/1047409322/Setting-up-a-router-with-NordVPN.htm
I have witnessed wifi disconnection issues on every ROM I've ever ported/used for this device aside from Stock I wish there was more that I could do. As mentioned in the title and before, this ROM is ported from another device. What this means is that I don't have the source code and therefore cannot update things like Android security patch dates. If this were a ROM built from source, I would simply have to sync with updated RR sources to get the new patches and RR bugfixes/features. To do it with a port, I need to find a whole new ROM with the updated sources and then port the whole ROM over to this device again. That is just too much work.
As a side note, I had intended this to be the last ROM I ported for this device due to its age, however If there is enough demand and I can find one, maybe someday I will port a more updated Oreo ROM to this device. Good quality MT6582 Oreo ROMs built from source are still not really common.
Click to expand...
Click to collapse
Thanks for your answer. If only i could do something like that of my own... i have so much interests, i don't know if i could learn that in a usefull time!
By the way, why did you call it "old"? i'm using the Galaxy S2 build 2011, with LineageOS 16. I think this is an old device , like my Galaxy Tab 1 and 2.
But anyway, thanks for your work. After some time i'll write again about issues i found, if it will be helpful.
Regards
Thank you, SaberShip. It's been on my list to get a DD-WRT enabled router, so maybe now's the time.
I've had no problems with WiFi.
If you build an updated Oreo ROM, I volunteer to test it. I'm fond of my A7600-F.
SaberShip said:
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.
- Don't worry about taking the battery out when the tutorial says to.
- If you have issues with the driver provided in the download, try these. (Run dpinst.exe)
- Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time
- Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Click to expand...
Click to collapse
Does usb otg work?
thierry_w said:
Does usb otg work?
Click to expand...
Click to collapse
Just tested, It works perfectly with my USB wireless Keyboard and mouse combo.
When I tried a USB flash drive it did not mount automatically, however "SDA" does appear in the /dev/block/ directory so you can likely mount the flash storage manually with some terminal commands. YMMV
USB OTG works with both my wired and wireless trackballs (Logitech).
I mount/unmount flash drives with StickMount and explore them with Total Commander.
excellent. Works very well
Hi,
I have a Samsung S9+ (star2lte) on which I installed e os 1. This is essentially Lineage with a some tweaks and e Recovery. I would like to root my device, so that I can install AFWall+. Open to alternatives, but most don't offer a comparable deal in term of privacy, security and sideeffects. I will probaby also need MAgisk to hide root from banking apps. So I decided to go for Magisk, which I have used in the past as well.
So there is no lack of guides when you search for this topic. However, noone mentions e os. And this twist seems to matter. While trying to follow various guides (I have by now started from factory a couple of times, as I almost bricked my device...)., I came across a lot of errors, which were not mentioned in either guide. The install would fail, sometimes messing up the entire installation, so that I had to start from scratch.
I think I identified one of the main issues, which happens to be the recovery. The e Recovery won't install the proper magisk boot image. Well, unless there was another issue in the background, but I also found hints towards TWRP being needed to install magisk. So I installed TWRP latest version, which worked fine. Then I tried to install magisk boot image - and it failed. /data could not be mounted, apparently this relates to the encryption of the file system.
I'm also about unclear on the role of Odin (latest). I understand I need it to flash my Samsung device, e.g. with TWRP. I'm somehwhat unclear on the various filetypes one can flash (AP, BL, CSC,...). So I strictly adhere to the guides for this. MEaning, I have never tried to flash Magisk via Odin - is that possible? Does it make sense? How?
One sideeffect of the guides I found would be, that TWRP is installed as recovery. In an ideal solution, I would like to return to e os recovery, so that everything is as close to the orignal setup as possible, except with root (and possibility to hide this for specific apps).
As I have spent two days backing up, flashing, reading guide, reading more guides and still failing all the time with results which forced me to redo everything from vendor image - I finally resorted to asking for help here. Can someone please guide me though the process of installing magisk?
Versions:
Samsung SM-965F DBT (star2lte)
e os 1.0-q-2022052618889-stable-star2lte
TWRP 3.6.1_9_0-star2lte
Odin 3.14.4
Magisk: Latest App.
Best,
YeOldHinnerk
same problem with a oneplus 5, i updated to e/os/ 1.0 and no more magisk/root...i try to update with magic manager (magisk 25), it asks a patch but not proposing install...
You need to extract the boot.img from e. Download the tar/zip, extract and locate the boot.img within. Copy that somehhere on your phone and feed it to magisk.
TWRP will not see the file by magisk since the file system is encrypted, see above.
Btw encryption is a must-have for me, for security reasons and my apps for work won'T run without (Citrix Secure Hub).
it's working Thks a lot !
Was intended as llooking for help here - but glad I could help too
Hi @YeOldHinnerk & @pommedefrance , I wonder if you'd mind taking a look at my post:
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Same issues but with Samsung S7.
Any pointers?
Thx
I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!
You can create dumps of your partitions using ADB shell in system; TWRP is not required to do this.
Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.
A very similar thread with the same topic has been discussed a few days ago - you can check here
Anyone can compile TWRP - it's opensource. Pixel 6+ owners are unlikely to get an official build from TWRP since it requires a volunteer to maintain the repo, deal with bug reports, etc.
It's recommended to simply compile the image on an individual basis (you really don't want to rely on a third-party supplied image when you have no way of knowing whether it's safe or not). Compiling isn't a difficult process, but does require an hour or two of reading TWRP's and Google's applicable developer pages, along with ~30 - 60 minutes of set up time on a PC/laptop (I prefer to compile within an Ubuntu VM, but I believe it can also be done in Windows' WSL).
robroy90 said:
I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!
Click to expand...
Click to collapse
They still haven't finished official support for Android 12. Since recovery resources on A12+ are located in vendor_boot, bigbiff is trying to figure out a decent way for TWRP to live there, at least as far as the Pixel 5 is concerned. Not sure what other obstacles may be present on the Pixel 6 series and above.
nooted1 said:
Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.
Click to expand...
Click to collapse
Hey thanks for this! How did you flash just the recovery partiton on the Pixel? I am an old hand with Odin on the Samsung devices, but Google official devices are still new to me. Will the StagOS recovery recognize an external USB-C flash drive for storage?
s3axel said:
A very similar thread with the same topic has been discussed a few days ago - you can check here
Click to expand...
Click to collapse
Thank you, I went over there and read everything. Much appreciated!