Related
I have gone through the rooting and upgrading steps. Let me know if there is anything I missed.
1. Prepare PC. Install ADB and Fire HD 10 driver at https://developer.amazon.com/docs/fire-tablets/connecting-adb-to-device.html.
2. Don't connect to Internet. Keep the device offline. The instruction is in the thread for rooting. Note ROM version. I have version 5.6.1.0. Amazon has implemented anti-rollback boot loader since 5.6.1. If you upgrade using official channel, you won't be able to downgrade. If you follow the step below, root 5.6.1, update to 5.6.3 via FlashFire, it will leave the boot loader unchanged and allows you to downgrade if needed
3. Install ES File Explorer. Need to download the APK. Plug in the USB cable, copy the APK file, and use Documents app to file the file and install it.
4. Root.
4a. I first tried HD 10 (2017): Offline rooting. It's an offline process and does not transfer any of your data to internet (so less privacy concerns). It worked on the first try. However, I messed up the upgrade to 5.6.3.0 so I have to restore to stock 5.6.1.0. Then I could not get it to work. It either timed out or reported success but su is not found.
4b. I then went with KingoRoot. [TUT] ROOT HD 10 (7th Gen 2017) - EASY SuperSu (read this before 1st power on!). The rooting process stucked at 78% for a long time (5-10 min) but eventually succeeded
5. Disable OTA update. The instruction is in step 13 in [TUT] ROOT HD 10 (7th Gen 2017) - EASY SuperSu (read this before 1st power on!). I found out the Xposed installer requires internet, even though just briefly. So I decided it's better if I disable OTA.
6. Install Xposed & Flashfire. HD 10 (2017): Xposed, FlashFire, etc.. FF versions. (v0.24 or v.51) are attached in How to install Xposed & Flashfire for easy backups and ROM updates. In my experience, Xposed installer requires internet connection to install the framework. Otherwise you won't get the Official tab. I disabled WiFi once it's done.
6a. v0.51 did not work for me. It always crashes on start-up, regardless if I have time machine set
6b. v0.24 worked. retyre also mentioned it's more reliable in restore backup
7. Upgraded to 5.6.3 HD 10 (2017): Prerooted Xposed 5.6.3.0 image.
7a. I made a big mistake in the first attempt. I renamed the boot.gz and system.gz to .img file instead of extract the file inside the zip. FF accepted the file but generated error during the flash. After that, it got the Amazon bootloop. I had to restore the stock and restart from step 4
7b. Second time around, I put all the folder under /sdcard/FlashFire/Backups. Then I used restore function FF. This is safer and FF will check for md5sum and reject if the files are incorrect. This went through fine. The recovery step is at the bottom.
8. It's possible to disable OS update but continue to update Amazon packages. The instruction is in the second section in same link above How to enable Amazon packages (apk) updates but prevent the ROM updates (keeping root & rootable rom) This allows APK updates and install them in /data/app. The ROM in /system is not touched. It's a good way to stay current while not touching ROM (and keeping root!). Note the image flashed in step 7 already has this taken care of.
9. Install Google Play Store.
@bibikalka has provided the following (post #1)
Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more
Click to expand...
Click to collapse
Run this tool and choose the option to install Google.
Worked!
Here are some other candidates but I did not try them.
COMPLETELY 'GOOGLE-IZE' YOUR AMAZON FIRE TAB (Confirmed Working)
[GUIDE] Sideloading Google Apps - 100% WORKING! (ROOT)
https://www.howtogeek.com/232726/how-to-install-the-google-play-store-on-your-amazon-fire-tablet/
10. Change SuperSU to limit app which has root access. SuperSU access workaround for Fire devices. For me: After forced stop, the App tab will show the new app added without reboot. However, the new app does not take effect until reboot. And upon reboot, any app not yet installed will disappear from the App tab
11. Remove lock screen ad. Use the super tool again and worked! Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more
12. Replace launcher. New: Any Launcher, No Root (Launcher Hijack V3). It worked but the flicker is killing me. I then used Tips, Tricks, and the Root!. Move Nova to system app using Link2SD and disable Fire Launcher. Much better. Note the following from that thread. And there must be empty line at the bottom of build.prop
You should install Nova as a system app. Then you get the Google Now page without having to install another apk. If you are going to keep Fire Launcher, but leave it disabled, add this line to your build.prop, at the very bottom:
Code:
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
13. [ROOT] Enable ALL Lock Screen Lock Options. You need the premium version of Activity Manager. In its settings, these options must be set: Show system app indicator (might be optional), Show not exported activities, Allow ROOT operations. In my experience, about 30% of time after reboot, the screen will loop between screen saver and black and never show the unlock pattern. I have disabled this function and went back to PIN. So I no longer recommend this step.
14. Disable bloatware. [GUIDE] Remove all bloatware from your Fire HD 10 (2017). This is written for 5.6.0. Updated: Amazon System App / Bloatware Tracking Sheet - as of FireOS 5.6.2.0. I did not find a thread for 5.6.3. Note the following 2 if you want to use them
My Account: com.amazon.kindle.otter.oobe
Backup & Restore: com.amazon.device.backup
15. Google Assistant. [GUIDE] [NO ROOT]: Activate FULL Google Assistant!.
Have to install specific version of Google App Google App 8.33.6.21 (arm-v7a) (nodpi) (Android 5.0+) and don't forget to disable auto-update in Play Store. Update: this is working. However, it's a bit sluggish. I have now uninstall Google Assistant.
---- Maybe Later: Other Optimization
Making The Most of Root on Fire Tablet 10 (tweaks/apps/modules/hacks/optimizations).
Appendix
A1. Recovery to stock ROM. The instruction is at Unbrick/Restore/Downgrade Stock Firmware [Amazon Fire HD 8 & HD 10]. This is written for the older version of Fire HD but the steps remain valid. The ROM is available from post 2 in [TUT] ROOT HD 10 (7th Gen 2017) - EASY SuperSu (read this before 1st power on!). I used the below
FireOS 5.6.1.0 (still rootable, but cannot be downgraded to anything earlier!)
update-kindle-40.6.0.5_user_605485120.bin
Click to expand...
Click to collapse
@redhonker
Hmm, must have been hours on XDA to compile this together
For your Google Play Store issue, there is an oldie but goodie - Amazon Fire 5th gen SuperTool. Works like a charm to install Play store on Fire HD 10! In fact, I stopped messing with the GAPPS flashing for Fires even when I have root, and just use this tool. Since 2015, for most tablets the underlying Android is still the same - Lollipop 5.1.1
https://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
https://www.rootjunky.com/
bibikalka said:
@redhonker
Hmm, must have been hours on XDA to compile this together
For your Google Play Store issue, there is an oldie but goodie - Amazon Fire 5th gen SuperTool. Works like a charm to install Play store on Fire HD 10! In fact, I stopped messing with the GAPPS flashing for Fires even when I have root, and just use this tool. Since 2015, for most tablets the underlying Android is still the same - Lollipop 5.1.1
https://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
https://www.rootjunky.com/
Click to expand...
Click to collapse
Thanks, I've added it to the first post. Will try that first.
The link you provided for rootjunky. What should I use from there? I can go to the section for Kindle Fire HD but I think it's the older model. I did own one before and I was able to install TWRP on it. But the 2017 model has no custom recovery available yet, right?
redhonker said:
Thanks, I've added it to the first post. Will try that first.
The link you provided for rootjunky. What should I use from there? I can go to the section for Kindle Fire HD but I think it's the older model. I did own one before and I was able to install TWRP on it. But the 2017 model has no custom recovery available yet, right?
Click to expand...
Click to collapse
Sorry, it was a bit confusing! You should be using this file (it's linked to in the XDA post):
http://rootjunkysdl.com/files/Amazon Fire 5th gen/SuperTool/AmazonFire5thGenSuperTool.zip
Once you unpack, you can start the bat script (under windows), and then it'll have option 2 which will install all Play Store components.
Thank you, this was helpful.. I have ordered a HD 10 as well and plan to do the same.
But, I'm confused on Step 2 and Step 4. In step 4, you say even the latest version can be rooted (which is my understanding as well), but in step 2 you say not to allow it to upgrade to the latest version.
Why not just do all the updates BEFORE rooting? Am I misunderstanding something?
wcarlson40 said:
Thank you, this was helpful.. I have ordered a HD 10 as well and plan to do the same.
But, I'm confused on Step 2 and Step 4. In step 4, you say even the latest version can be rooted (which is my understanding as well), but in step 2 you say not to allow it to upgrade to the latest version.
Why not just do all the updates BEFORE rooting? Am I misunderstanding something?
Click to expand...
Click to collapse
I updated step 2. It refers to anti-rollback so you can't downgrade OS version.
Others have recommended against upgrade first. Maybe Amazon just released a new update and you won't be able to root or downgrade. Practically, it probably won't really happen.
redhonker said:
I just ordered one. I have gathered the following information. Please correct me if there is anything incorrect.
.....
Click to expand...
Click to collapse
This is really great I just got mine yesterday and I was just going to root and remove Amazons stuff. You reminded me that it's probably best to back up something before you start messing with it. I'm used to having a recovery like twrp though, but oh well. I'm wondering what path you will take in regards to installing FF and Xposed and doing a backup. I'm reading your links (from retyre) and it's suggested that you do the backup before installing Xposed (I think) but with FF and SuperSu as system apps. Are u going to use the DD command for back up or just use the altered version FF. I'm just a little confused after reading this links and just wanted to get your thoughts. Incidentally what are you using file explorer for? I would think you can just push it to the tablet than install it alternatively I have a USB to microusb that I think I can mount usb. Thanks. Unless things have changed es file explorer is full of bloat I would suggest mix explorer
I have rooted and installed xposed. I installed google play store and titanium backups. I couldn't really figure out how to install flashfire. But I'm to scared to try to add any modules on xposed as I still can't figure out how to restore my titanium back up??
I haven't done any rooting in a long time, but as far as my memory goes, you make an update.zip file as your backup but you need a custom recover or something to to be able to flash it? like TWRP. is flashfire that equivalent?
@looney417
Yes the bootloader is locked, as of now I guess, and so there is no custom recovery. I do believe flash fire is the method being used for raw backups. One of the links in the first post refers to Retyres work and he also mentioned the Linux command DD to make a back up after you gain root. There is some creative work arounds and some hard work and experimentation done here I think we are benefitting from. I'm struggling with the order of operations here too but I've been playing with and rooting devices since the original Google phone Nexus one and you always try and get a good back up before you start messing around. The one big no-no right now is flashing an older version of the fire OS. This results in a hard brick bc Amazon instituted anti roll back measures in there boot loader.
Hello, I have just rooted my new Fire with the offline method, I have followed all the steps for the newbie listed here but I got stucked at 5) point,
I read couple of times the topics about flashfire and Xposed but I really can't understand some things:
What exactly is Flashfire? Is it an app? Do I need it to upgrade the system?
In order to work FF needs Xposed? Or not?
Why Xposed could be useful on this Fire HD 10?
Last question, in the FF and Xposed topic is written that I have to dd my img?! And then root again?!
I am so sorry for my disability.... Is there any other clear guide to install Xposed and Flashfire? And something that explain why these tools are useful and what aim they pursue
Thank you everyone for this great guides about fire HD btw
I have just purchased a fire HD 10, i am also wanting to root, and install gplay but haven't rooted for a while, i have actually asked Amazon for a return label as i was extremely dissapointed with the poxy adds for the screensaver/lockscreen! I wish Amazon would word things correctly! "With offers" = With ADDS!!! "Without offers" = "Without ADDS"
Other than paying Amazon £10! is there a way to remove them?? Very curious to find out.
Also has anyone had any issues with the brightness slightly fading in and out, ie brightness going up and down?? I have checked the settings, and adaptive brightness is on, however, the lighting in the room is constantly the same and never changes, i have kept it on a stand and monitored it, and it does fade in and out/up and down slightly. Its very odd.
Is this a bug within the OS?
I have even turned off the adaptive brightness and it still does the same?
Was just curious if anyone else had experienced this?
I would also like to remove the bottom nav bar as it is constantly there and really annoying!!
Is there a way to do this, i wish that black bar was transparent, i would then have an actual 10.1" tablet, not a 9.7" one!! Is there a way?
Looks like and Awesome guide, would love to get these issues sorted, and root, but not sure if my experience would be adequet?, some things are a little bit over my head.?
Logoutt said:
Hello, I have just rooted my new Fire with the offline method, I have followed all the steps for the newbie listed here but I got stucked at 5) point,
I read couple of times the topics about flashfire and Xposed but I really can't understand some things:
What exactly is Flashfire? Is it an app? Do I need it to upgrade the system?
In order to work FF needs Xposed? Or not?
Why Xposed could be useful on this Fire HD 10?
Last question, in the FF and Xposed topic is written that I have to dd my img?! And then root again?!
I am so sorry for my disability.... Is there any other clear guide to install Xposed and Flashfire? And something that explain why these tools are useful and what aim they pursue
Thank you everyone for this great guides about fire HD btw
Click to expand...
Click to collapse
I will give it a try before the experts weigh in.
FlashFire is an app. The 2017 Fire HD 10 has a locked bootloader and so far there is no way to install custom recovery. So FlashFire is the only way easy way to backup/upgrade OS.
FlashFire checks date to see when it's valid. If you use v0.24, you need to hack the date. My impression is v0.51 also needs it but I'm not certain. This can be done either by changing the system date or install Xposed with per-app-hack. This is covered in the linked post.
DD is an alternative. It's a command line. If you are comfortable with it, you don't need FF for backup.
bibikalka said:
Sorry, it was a bit confusing! You should be using this file (it's linked to in the XDA post):
http://rootjunkysdl.com/files/Amazon Fire 5th gen/SuperTool/AmazonFire5thGenSuperTool.zip
Once you unpack, you can start the bat script (under windows), and then it'll have option 2 which will install all Play Store components.
Click to expand...
Click to collapse
Sorry, one more question for you. If we use the FF v0.51 you provided, do we still need date hack? If not, will it work without Xposed?
Thanks
Is there any guide like this for the 8th Gen(2018) or does this apply?
Just wanted to ask again if there is a definative way to get rid of the bottom nav bar? Really hate that black bar that takes away a portion of the screen, would be really nice if there was a way that it could be made trasparent, and works with the fire 10.1 (2017) model. Also want to keep everything stock.
fleebleflam said:
I have just purchased a fire HD 10, i am also wanting to root, and install gplay but haven't rooted for a while, i have actually asked Amazon for a return label as i was extremely dissapointed with the poxy adds for the screensaver/lockscreen! I wish Amazon would word things correctly! "With offers" = With ADDS!!! "Without offers" = "Without ADDS"
Other than paying Amazon £10! is there a way to remove them?? Very curious to find out.
Click to expand...
Click to collapse
You can call Amazon, or start a web chat with them, and tell them this device is a gift for young child, and some of those ads shows on lock screen are not appropriate for kids. then they will remove all the lock screen ads for you. you also can go to your amazon account to unsbscribe those offers, it will cost you some money. or, you can find in here some guide to help you remove the ads in lock screen. good luck, mate!
28mufields said:
You can call Amazon, or start a web chat with them, and tell them this device is a gift for young child, and some of those ads shows on lock screen are not appropriate for kids. then they will remove all the lock screen ads for you. you also can go to your amazon account to unsbscribe those offers, it will cost you some money. or, you can find in here some guide to help you remove the ads in lock screen. good luck, mate!
Click to expand...
Click to collapse
I have been very fortunate to get the adds removed by Amazon, a manager gave me a courtesy call and said they would remove them for me for free!
So that's the adds sorted, i'm more concerned about the bottom nav bar its so frustrating just being there permanently! It's now a 9.7" tablet not a 10.1"!!
Is there a way to make it transparent, or to maybe swipe up from the bottom when you need it?
Any help with this would be greatly appreciated.?
playerpatrick said:
Is there any guide like this for the 8th Gen(2018) or does this apply?
Click to expand...
Click to collapse
If I search on Amazon, only the 2017 7th gen Fire HD 10 will show up. Where do you see the 8th Gen 2018?
There is no 8th gen 10.1" tablet. Amazon presently, only sell the 2017 10.1" model that is the latest one. I just purchased one last week, and i also thought there was a 2018 10.1" model. But there isn't until Amazon release another one.
The latest 2018 model is only the 8" model.
I have completed the setup of the tablet and updated the first post.
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!
Hi all
I thought the Galaxy M12 was very popular because of its features, but I think I'm wrong as very few people open topics here.
Anyway , something that is very sought after , is getting the administrator permission , or in other words , rooting your galaxy m12 , so that the person really owns the device they bought , and so do whatever they want in your software....
There are a lot of articles on the web showing how to root the galaxy m12 , but almost all of them are fake
Below is a link , here from the xda forum , showing that rooting the galaxy m12 is possible .
[ROOT] Modified Magisk for Galaxy A21S (R)
It seems that the A21S hasn't had any root since it was released (other than pre-rooted GSI ROMS) When flashing Magisk, the phone went into bootloop, and the only way to fix it was to flash stock rom via Odin. After some analysis, it seems that...
forum.xda-developers.com
Warning
Please read carefully every topic and replies , so there is no error in the procedure
Note that I'm not a programmer, I'm just trying to diversify, issues about the galaxy m12.
I here just redirect you to a serious topic about root on m12, and therefore I am not responsible for anything you do. Do it at your own risk!
Attached is a screenshot on Magisk installed on my Galaxy M12
If you're new to Android like me (I'm new to android, but pretty old haha), find out about Magisk, right here on the xda forum and on the web. If you have problems with a certificate on Google Play , after root , here on the forum there are solutions for the solution
I for example to solve these problems I installed , I installed the second module SafetyNet-Fix-shim-MOD .
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
If you have problems using Samsung apps like the Galaxy Store , please install the MagiskHide Props Config module
---Download a shell terminal such as Termux .
---Open Termux (in this case here), and in the command line type "su" without quotes.
---Then type "props"
---Choose option 2 (Force Basic)
---Then choose option "d"
---After the option corresponding to Samsung , which is 26
---Now a series of versions of Samsung devices will appear. I chose the Galaxy S20 corresponding to 75
---Now choose Yes "y" . The device will reboot to make the configuration take effect
---Test and enter the Galaxy Store
To solve problems with CTS profile , problems with certification on Google Play , I installed Module SafetyNet-Config-Fix
Release v2.1.0 · kdrag0n/safetynet-fix
Changes Fixed new SafetyNet CTS profile failures as of September 2, 2021 Added MagiskHide features that will be removed in future versions of Magisk Donate If you found this helpful, please consi...
github.com
note: Before installing , remove MHPC and SafeNet Fix module , then install the one from the link above
Thank you guys for reading
Thank you very much, it worked for me correctly.
Rooting your Samsung phone permanently BURNS KNOX and voids warranty , paid services ...
It's possible. Root using Odin
cater2 said:
Rooting your Samsung phone permanently BURNS KNOX and voids warranty , paid services ...
Click to expand...
Click to collapse
Not a paid survive but reseting knozlx requirs motherboard to change
It's possible, root using odin
Root for all Exynos 850 devices.
Root for all Exynos 850 devices. A. Root part 1 - Preparing the file I accept no responsibility for bricked phones but I will help you to recover. 1. Download the exact firmware (including upgrade date) for your device from https://samfrew.com...
forum.xda-developers.com
Thanks, it worked for me as well.
mdbshuvo said:
Thanks, it worked for me as well.
Click to expand...
Click to collapse
Hii please share the boot. Img file or magisk patched file for Samsung m12
Is there a version of magisk for rooting M12 android 12?
P.S. I used this magisk to successfully root my M12 android 11.
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 don't know if this is the right place to ask or if it already has been or not, but is there any possible way to get 32 bit apps to run in some type of compatibility mode or something like that? For the most part the majority of my old apps came over from my old phone, however there are some apps I have and used regularly which are not compatable with this phone and I am not sure if the developers are still active or not. I'm assuming the answer is no, or would require root if it were possible and rooting is out of the question for me because I have Verizon. I am expecting to be SOL but figured it was worth asking about here.
This question has been asked and discussed in length, try search
I will not be rude and the short answer is no. Apps on the play store had roughly 2 years to switch 64 bit. For s**ts and giggles I did try to do a search with zero results.
If the devs are still active and they havn't updated to 64bit by now then they are a lost cause.
No Google's heads up to devs gave them ample amounts of time to switch all their apps from 32bit over to 64bit. Tough shiz if the devs didn't take the arning seriously and switched their apps over whenthey had the cance to do so. I'm genuinely curious of 32bit compatibility is a concern and/or a necessity for you why you would buy a smartphone that doesn't support it? I really don't see how that makes much sense when you could have chose from a lot of other new flagships with 32bit support in tact.
Get a Galaxy S22 Ultra, Motorola Edge 30 Ultra or OnePlus 10 Pro. It's likely next year's flagships of any brand will be 64 bit only, so the forced shift is coming.
I did not even know this was a thing prior to buying the phone and don't remember seeing anything posted about it until after I got the phone and google'd and found people talking about it on reddit but I did not find anything on here going into detail about it.
I never stated it was a "necessity" and I have no idea if the developers are active or not. They are older apps that are not overly popular that everyone uses however they were things I used on a regular basis and have no idea how I would even check to have known if they were 32 or 64 bit until I got the new phone and they didn't work and wouldn't let me install them. It's not the absolute end of the world, it's just an inconvenience and means I need to try and find replacements or reach out to the devs but it doesn't hurt to ask here because I figured there would be a way around it but obviously not.
This might be of some help to run 32 bit apps you want:
GitHub - ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com
Interesting I will have to check this out
Not working for my Pixel 7 Pro, version 13 (TD1A.221105.001) : (
I dirty flash patched init_boot.img, and replace Magisk app to initial version of that repo.
VergeDX said:
Not working for my Pixel 7 Pro, version 13 (TD1A.221105.001) : (
I dirty flash patched init_boot.img, and replace Magisk app to initial version of that repo
Click to expand...
Click to collapse
Remove "stock' magisk
Install the patched magisk apk
Patch the stock init boot with the patched magisk apk
Flash the new patched init boot
on a clean install it works for me (beta: cheetah-t1b3.221003.008)
lunacies said:
I did not even know this was a thing prior to buying the phone and don't remember seeing anything posted about it until after I got the phone and google'd and found people talking about it on reddit but I did not find anything on here going into detail about it.
I never stated it was a "necessity" and I have no idea if the developers are active or not. They are older apps that are not overly popular that everyone uses however they were things I used on a regular basis and have no idea how I would even check to have known if they were 32 or 64 bit until I got the new phone and they didn't work and wouldn't let me install them. It's not the absolute end of the world, it's just an inconvenience and means I need to try and find replacements or reach out to the devs but it doesn't hurt to ask here because I figured there wld be a way around it but obvio
Click to expand...
Click to collapse
That's what I meant by and or sorry if me misinterpreting what you meant
bhammler said:
on a clean install it works for me (beta: cheetah-t1b3.221003.008)
Click to expand...
Click to collapse
I've compiled Magisk with the supplied patch from the repo and it isn't working for me. I've verified that the init does include the changes to override ro.zygote, however none of the Zygote processes start as the adb server never starts up, and well it doesn't boot.
Tested with the modified Magisk APK from the repo, same deal.
Strange that a clean install is necessary.
don't bother with a clean install, after I've installed some Mgaisk modules, I had a bootloop ;-)
It's nice to see there may be an option and I hope it works for everyone else. I am stuck with a Verizon phone so rooting is out of the question for me and I figured something like this would require root but hopefully other people are successful in getting it to work.
This works now, the problem was not the modules. If you enabled the zygisk in the 24 manager app than you got stuck in the bootlogo „G“. It’s fixed now, there is a new 25 magisk patched manager app that works with zygisk enabled. All my 32 Bit apps working now.
Wouldn't it be easier to just patch build.prop with a magisk module instead of patching the boot image?
Pixel7_32bit_helper/patch.diff at main · ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com
hahimot483 said:
Wouldn't it be easier to just patch build.prop with a magisk module instead of patching the boot image?
Pixel7_32bit_helper/patch.diff at main · ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
No as I discuss here.
Namelesswonder said:
Didn't sleep, I have gotten closer, but Magisk modules aren't going to be the solution.
The earliest Magisk allows you to modify properties is after the post-fs-data trigger, which is well inside the init.rc. This is problematic because the property needs to be set before init.rc is even read.
Using a Magisk module to replace the init.rc with something else also isn't possible, since Magisk doesn't setup the overlays until well into the boot process.
This replacing is necessary because init.zygote64_32.rc actually has the secondary zygote service disabled, so the file needs to be modified to enable it, or with control over init.rc just stuffing a custom zygote service into it.
I don't think slipstreaming a modified init.rc and init.zygote64_32.rc into the ramdisk in init_boot will work since they would be overwritten once the system partition mounts. Could just modify the system partition, but that'll be for another day.
Click to expand...
Click to collapse
Gerr1 said:
This works now, the problem was not the modules. If you enabled the zygisk in the 24 manager app than you got stuck in the bootlogo „G“. It’s fixed now, there is a new 25 magisk patched manager app that works with zygisk enabled. All my 32 Bit apps working now.
Click to expand...
Click to collapse
Does it? I tried with building my own 24300, 25200, and 25205 and the result was the same on all of them. I didn't remove all modules and kept Zygisk on, so I guess I will have to try completely deleting all Magisk data.
Namelesswonder said:
No as I discuss here.
Does it? I tried with building my own 24300, 25200, and 25205 and the result was the same on all of them. I didn't remove all modules and kept Zygisk on, so I guess I will have to try completely deleting all Magisk data.
Click to expand...
Click to collapse
Yes it works now with the new magisk Manager APK.