Database Users

[How to] Upgrade to 4.5.4 and keep TWRP and root :

Update5: 4.5.5 is out, and there is no reason NOT to update to 4.5.5. Please use the newer 4.5.5 upgrade instructions in the link below :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
Another alternative is Lollipop:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
And these are the earlier (original) 4.5.x upgrade instructions which require modifying the Amazon update file:
Update4: For users with low computer proficiency (a.k.a "newbies"), DoLooper has written a post trying to make the instructions most accessible :
http://forum.xda-developers.com/showpost.php?p=61832754&postcount=10
If you still have questions after that, post here!
Update3: I've uploaded the 4.5.4 update file to Dropbox, now everything is super simple and you can skip steps 1)-4):
https://www.dropbox.com/s/17ngnhmvnkh1cpx/twrp_ready_update-kindle-20.4.5.4_user_454006120.zip?dl=0
md5sum : ab9468126ee7d7ff0b1c38a96313ef20
Use at your own risk (it works for me!)
If the procedure works for you, don't forget to click "Thanks"
Update2: Thanks to DoLooper, this has been established as the simplest and quickest way to get full GAPPS working. The instructions are simplified further to incorporate suggestions.
Update: Looks like the procedure worked for several people, but there is a single pitfall which appears to be common. I added some additional instructions below in red.
### Original post
I am making a separate topic out of this. Tested this yesterday, going from 4.5.2 to 4.5.4
What you need to have before you proceed : unlocked bootloader (according to reports, not really needed, skip), TWRP and rooted FireOS (4.5.3 or below). Also, download jmz tool to somewhere (can skip this too), and SuperSu flashable zip.
Important: If you have anything other than 4.5.3 right now, I recommend that you flash the 4.5.3 bootloader separately first before doing any updating business. I've attached the flashable zip with 4.5.3 bootloader as well (uboot*zip). The other bootloaders are very risky !!! 4.5.1 and 4.5.2 will not let you into TWRP by the "power" and "vol+" button push if you screw up !!!
0) If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
1) Download the latest 20-4.5.4 update to a PC ( https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin ), rename *bin to *zip, unpack, and replace the attached "updater-script" below in 20-4.5.4/META-INF/com/google/android/updater-script
2) Delete the following directories/files :
a) here you remove stuff you will not flash
20-4.5.4/recovery
20-4.5.4/images
b) here you will remove files to make room in /system to flash bigger GAPPS
20-4.5.4/system/priv-app/com.amazon.weather.apk
20-4.5.4/system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
20-4.5.4/system/priv-app/com.amazon.geo.client.maps.apk
(can delete more if you need space in /system and know what is useless, and a few things could just be moved to /data/app with no issues)
3)Rename (just in case, this will make OTA blocked):
20-4.5.4/system/priv-app/DeviceSoftwareOTA.apk to *apk_
4) Zip everything into update.zip. Make sure the paths in zip are the same as in the original 4.5.4 update from Amazon (QC this carefully!). Put the zip on a USB stick with FAT (if you have an OTG cable). Alternatively, upload it to the device somewhere to the Download folder
Possible pitfall: When you create your update.zip, look into it!!! It should have {system,boot.img,etc} right at the top level, just like the original Amazon update. If you have {yourpath/system, yourpath/boot.img,etc}, you need to re-zip and make sure that "yourpath" is removed.
5) Boot into TWRP, and flash the 4.5.3 bootloader. Reboot. Skip if you already have 4.5.3
6) Boot into TWRP, and flash update.zip from 4) . Then immediately after flash supersu.zip ( https://download.chainfire.eu/396/supersu/ ). Reboot to FireOS. If you choose not to flash supersu.zip here, before you reboot TWRP, it will ask you to root the device, say yes (leaving hooks for later root)
7) Re-boot to TWRP, flash a GAPPS package, such as Pico (Uni) GAPPS for KitKat ( http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html ). Wipe dalvik/cache and reboot to FireOS (Note: The free room in /system is still kind of limited, either remove more stuff in Step 2), or go with the smaller GAPPS. If you download my update package, you'll probably have about ~140 Mb of room in /system for GAPPS). Wipe dalvik/cache, reboot.
8) In FireOS, install jmz tool, and do small tweaks. Important, installing GAPPS via this tool is obsolete !!! Don't do it!!!. Alternatively, skip this tool, and just do it manually or via the scripts, as per here :
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
The lockscreen ads can be reversibly blocked via this adb command :
adb shell su -c "pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.LockscreenUpdateS ervice"
(as per DoLooper's suggestion)
P.S. 4.5.4 allows the latest GAPPS to work fine, so they will update themselves over time, let them. No need anymore to keep Google Play Services at 7.0.99

kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin
link to 4.5.4.
nevermind figured it out, was being dumb and right clicking send to zip on the folder instead of adding the files to a zip

bibikalka said:
4) Zip everything into update.zip, and put it on a USB stick with FAT. Make sure the paths in zip are the same as in the original 4.5.4 update from Amazon.
Click to expand...
Click to collapse
You must use USB stick? . . .
. . . so must connect USB stick with OTG cable for step 6?
6) Boot into TWRP, and flash update.zip from 4) . Say yes when it offers to root the device.
Click to expand...
Click to collapse
I'm on rooted 4.5.3 with unlocked bootloader. Will install TWRP.
Haven't done anything like this before. Why not put update.zip in /system and flash from there? Thanks.

DoLooper said:
You must use USB stick? . . .
. . . so must connect USB stick with OTG cable for step 6?
I'm on rooted 4.5.3 with unlocked bootloader. Will install TWRP.
Haven't done anything like this before. Why not put update.zip in /system and flash from there? Thanks.
Click to expand...
Click to collapse
Sorry, I was not clear enough. Indeed, you can put this zip into the internal memory, but not /system (it'll get formatted). Instead, place it into the "Download" folder or something.

Just got done. Everything worked great. I did have to sideload SuperSu and Busybox manually though, but everything is working fine. Thank you.

With an easy way to recover (just re-install 4.5.4), I've been playing with various Xposed modules.
So far has not seen anything very attractive, and most of the system tweaks via Xposed modules don't seem to work.

Easy update 4.5.3 to 4.5.4 -- and working Gapps!!!
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
FWIW, I wasn't prompted to root, which i guess I wouldn't be...didn't you say somewhere that root is preserved during 4.5.3 to 4.5.4 update? (Yeah, I'm still properly rooted.)
Gapps: Since JMZ's tool creates the dummy dirs you mentioned, which prevent play services and store from updating, I installed this Gapps minimal edition instead. Just uninstalled play store first--kept G+, hangouts and Gmail (although it never worked before)--and let play services update. Now everything is running great. :laugh:

DoLooper said:
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
FWIW, I wasn't prompted to root, which i guess I wouldn't be...didn't you say somewhere that root is preserved during 4.5.3 to 4.5.4 update? (Yeah, I'm still properly rooted.)
Click to expand...
Click to collapse
Good to hear that you finally did it!
The update formats /system, so nothing survives there. But you could have had supersu in /data/app before, and that survived. You probably did root when TWRP asked about it right after the update? I think SuperSu needs something installed in /system to work properly, and that's what TWRP does.
DoLooper said:
Gapps: Since JMZ's tool creates the dummy dirs you mentioned, which prevent play services and store from updating, I installed this Gapps minimal edition instead. Just uninstalled play store first--kept G+, hangouts and Gmail (although it never worked before)--and let play services update. Now everything is running great. :laugh:
Click to expand...
Click to collapse
So you did not use JMZ's tool to install GAPPS at all? Did you just flash the minimal edition you've linked to in TWRP, and it worked? That'd be really neat if GAPPS could be flashed via recovery, just like in any other Android version. Btw, the latest Play Services provide correct positioning to Google Maps, so now it finds me on the map.

bibikalka said:
The update formats /system, so nothing survives there . . . You probably did root when TWRP asked about it right after the update?
Click to expand...
Click to collapse
If it were the least bit possible that I didn't get the root prompt, I would swear I didn't get it. I think, however, I left the tablet briefly while update.zip finished flashing. Any chance TWRP only gives you a minute or two to respond to root prompt, then defaults to yes?
Notes I took during update:
"Modified 4.5.4 update.zip installed successfully but i wasn't prompted to root. (see in twrp: HOME, WIPE CACHE, REBOOT SYSTEM) Went back to twrp HOME and flashed SUPERSU.ZIP - got success.
REBOOT."
Click to expand...
Click to collapse
That "see in twrp" is what i saw on screen after "success" with update.zip install. If TWRP always prompts to root and doesn't default to yes when there's no response, I must have done this step and will call a neurologist tomorrow. )
bibikalka said:
So you did not use JMZ's tool to install GAPPS at all? Did you just flash the minimal edition you've linked to in TWRP, and it worked?"
Click to expand...
Click to collapse
Exactly!

Couple last things:
1. Unlocked bootloader: You say unlocked bootloader required (and mine is), but JMZ shut down his thread. I assumed that was because TWRP could be installed without unlocking. Is that correct? If so, is unlocked bootloader really required to do this or is it only necessary to have TWRP?
2. Gapps: Hope you will have users install that minimal gapps. If they use JMZ's tool, to get updated play services and store they have to undo his fixes that make old Gapps work. With minimal package the store just updates itself to current version and prompts to update play services. No fuss.
3. Step 7 says "reboot to TWRP." This implies tablet reboots (or user is suppose to reboot) after "saying yes to root." Perhaps the reboot should be added? (But FWIW: Because I didn't see root prompt I flashed supersu right after flashing update, then rebooted.)

DoLooper said:
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
...... I installed this Gapps minimal edition instead. ......
Click to expand...
Click to collapse
Thank you a million times for this. I'm on 4.5.4 rooted, and was having a horrible time getting gmail to work. I finally uninstalled framework, services, and playstore from that JMZ tool thing and gave this a shot. Gmail works great now. Only having one issue so far. On Google Play Movies, the movies and shows won't stream. They only play if downloaded first.

DoLooper said:
Notes I took during update:
"Modified 4.5.4 update.zip installed successfully but i wasn't prompted to root. (see in twrp: HOME, WIPE CACHE, REBOOT SYSTEM) Went back to twrp HOME and flashed SUPERSU.ZIP - got success.
REBOOT."
Click to expand...
Click to collapse
OK, no mystery then! And a good catch! It looks like update.zip can be safely followed by Supersu.zip, without any reboots. Supersu.zip will flash everything that's needed to have root, so TWRP does not ask for anything when you reboot the device.
DoLooper said:
Couple last things:
1. Unlocked bootloader: You say unlocked bootloader required (and mine is), but JMZ shut down his thread. I assumed that was because TWRP could be installed without unlocking. Is that correct? If so, is unlocked bootloader really required to do this or is it only necessary to have TWRP?
Click to expand...
Click to collapse
I agree, perhaps TWRP can be flashed and will work without any unlock, but I am just too lazy to test this. Do we have a confirmation for this one? I would update instructions accordingly if this is true.
DoLooper said:
2. Gapps: Hope you will have users install that minimal gapps. If they use JMZ's tool, to get updated play services and store they have to undo his fixes that make old Gapps work. With minimal package the store just updates itself to current version and prompts to update play services. No fuss.
Click to expand...
Click to collapse
Another good catch! I was not thinking about this when I wrote the original post, but having GAPPS flash properly is a pretty big deal! I may re-apply update.zip, and try the GAPPS flash, to see if it is indeed so simple.
Did you boot to FireOS after update.zip/supersu.zip, and then rebooted to TWRP, and flashed GAPPS? Or did you go straight from update.zip to supersu.zip to gapps flash, without the FireOS boot ?
DoLooper said:
3. Step 7 says "reboot to TWRP." This implies tablet reboots (or user is suppose to reboot) after "saying yes to root." Perhaps the reboot should be added? (But FWIW: Because I didn't see root prompt I flashed supersu right after flashing update, then rebooted.)
Click to expand...
Click to collapse
As above, supersu.zip flash right away is a nice simplification!
Overall, great help! And the big deal is that GAPPS are easy to flash, work fully, and require no messing around with anything else. This makes flashing 4.5.4 with GAPPS into the fastest way to get fully working GAPPS on this device !!!

Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Thanks for working on this, having fully working play store will be great.
TWRP flashed fine for me without an unlocked bootloader, I already used it to make a backup.

lynnux said:
Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Thanks for working on this, having fully working play store will be great.
TWRP flashed fine for me without an unlocked bootloader, I already used it to make a backup.
Click to expand...
Click to collapse
Good question ... At most you'll have to delete a couple of dummy directories in /data/app, one for the play store, and the 2nd one for the play services which prevented the updates. But perhaps the GAPPS zip will remove those itself ... Why don't you try, and post ?

lynnux said:
Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Click to expand...
Click to collapse
It depends on what changes you made. Before I flashed update.zip, I did what @bibikalka suggests and found and deleted the following dirs in \data\app :
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
After update and before installing Gapps I searched /system for anything "google." Only found "widevine" and left it.
If you installed Gapps per the original root post, you gave this command:
pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
I don't know what this does. Shell command effects seem to be preserved with update, though, so would be worth finding out.
---------- Post added at 12:44 PM ---------- Previous post was at 12:23 PM ----------
bibikalka said:
OK, no mystery then! And a good catch! It looks like update.zip can be safely followed by Supersu.zip, without any reboots. Supersu.zip will flash everything that's needed to have root, so TWRP does not ask for anything when you reboot the device.
Did you boot to FireOS after update.zip/supersu.zip, and then rebooted to TWRP, and flashed GAPPS? Or did you go straight from update.zip to supersu.zip to gapps flash, without the FireOS boot ?
Click to expand...
Click to collapse
Exact steps I did:
Flash update.zip, press TWRP "Home," flash Supersu zip, reboot to system.
Go back to TWRP and flash Gapps zip, wipe cache (per instructions at minimal Gapps page), reboot to system.
FWIW, when rebooted after wipe, I got "updating" message again and it took awhile but all was fine.
4.5.4 Update bin: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin (Fire HD 6 and 7 use identical files)
superSU zip: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Gapps minimal: http://forum.xda-developers.com/showthread.php?t=2779598

I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.

lynnux said:
I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.
Click to expand...
Click to collapse
Download the update in a .bin file and extract (I use 7zip). Once extracted it makes a ton more sense.

lynnux said:
I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.
Click to expand...
Click to collapse
ugcbrian said:
Download the update in a .bin file and extract (I use 7zip). Once extracted it makes a ton more sense.
Click to expand...
Click to collapse
Right. You do steps 1-4 on the computer. See my post above for link to the update bin file.

DoLooper said:
Right. You do steps 1-4 on the computer. See my post above for link to the update bin file.
Click to expand...
Click to collapse
Thanks. I was renaming as a .zip, but trying to make the replacement on the tablet. Since I'm using a linux laptop, I suppose I'll have to rename it as a tar or gz file to work with it there, since linux doesn't do .zips.

lynnux said:
Thanks. I was renaming as a .zip, but trying to make the replacement on the tablet. Since I'm using a linux laptop, I suppose I'll have to rename it as a tar or gz file to work with it there, since linux doesn't do .zips.
Click to expand...
Click to collapse
Okay, if you have to rename the bin file in order to extract the contents, do that. (Maybe double-click will work.) You will see the files and dirs that bibikalka's instructions refer to (excluding the "20-4.5.4," which is just for reference). After doing changes per instructions, make a compressed file named "update" containing what's left (see below). Since the extension will be tar or gz, rename it to "zip" and copy or move it to the Fire's download folder, then do step 6 (assuming you're on 4.5.3).
Your compressed file should contain:
[dir] META-INF
[dir] system
[dir] tools
boot.img
file_contexts
ota.prop

Updating To MM from LP (Moto X Pure)

So I wanted to create a thread dedicated to performing this function. I know as someone who does this quite often, I like to have all my ducks in a row to ensure everything works perfectly. I'm not big on fragging my phone and then frantically trying to find a way to undo all the chaos. I do a lot of research and ask a lot of questions before doing anything.
On that note I would like to first thank all the amazing people on here, whether they be developers or just experienced Tech Guru's, everyone is always a big help. I take absolutely no credit for any of the awesomeness that can be found on XDA, I'm just creating a thread that I hope will help folks find everything in one place for this function. So here we go, I'm going to explain the way I did it, which is the way I have been doing stuff like this for years. I have a preferred method as it has always resulted in perfect flashes and no bricks, not even soft bricks. So I feel it works pretty well.
Just so it is understood, this is for the Moto X Pure, which has been bootloader unlocked and has TWRP and root installed. Also it should be noted that you need to have Developer Options enabled and USB Debugging enabled. You should also be familiar with the ADB process, to some extent, maybe you have at least heard of it.
Steps to follow:
1. Use Titanium Backup and backup all your User Apps, NOT SYSTEM APP's, system apps will not restore across updates and will most often corrupt your new install.
2. Make a Nandroid backup using TWRP, I backed up system, boot, data, and EFS, but I don't think EFS is necessary.
3. Make sure you have the Motorola Drivers installed, get them from here http://www.motorola.com/getmdmwin
4. Get Shawn5162's Restore to Stock Tool, I know others have said it's not necessary to perform a complete restore, but this is part of my process that I have always done, and it's always worked. Get it here by using one of the mirror's created by patt2k in post 6, and don't forget to thank him for the mirrors http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
5. Unzip Shawn5162's zip to a folder on your desktop, and before you move onto the next step, make sure you have backed up everything valuable on your phone, such as pictures, messages, etc..., because everything is going to be erased in the next step, except for the stuff on your MicroSD. I'm so anal, I even remove the MicroSD before flashing. Connect your phone to your computer using a USB and make sure you have USB debugging enabled under Developer Options.
6. Inside the folder you created run the FLASH-ALL.bat, which will reboot your device to the bootloader and begin the restore to stock flash. This will remove root and TWRP, but will not remove the fact you have an unlocked bootloader. Your phone will reboot when complete and should boot back into your system within a short period of time.
7. Once you are rebooted, you may need to do a little setup before you get the message that a System Update is available. DO NOT waste your time installing any apps, wait until you have full root on MM before doing any of that. Once the Update message appears, accept it and download the MM update file, then install it once it is finished downloading and asks if you want to install.
8. The update takes about 20 - 25 minutes so be patient. Once complete your phone will once again boot back to system, now you have MM in it's complete unrooted greatness.
9. Now go into settings, about phone, and tap on build number a bunch of times to enable Developer Options. Then go into developer options and enable USB Debugging.
10. Next download a bunch of stuff from the following links, if you desire to install TWRP and regain root.
TWRP 2.8.7.1 here https://dl.twrp.me/clark/twrp-2.8.7.1-clark.img
Modified Boot Image from here, required to perform systemless root , not sure about the Cowboy hat dude, but click on him, it will download the file.
SuperSU 2.52 from here https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip?retrieve_file=1
11. Next copy the modified boot file and SuperSU file directly to your internal or external SD on your phone, either works fine, although I prefer my External SD.
12. Next copy the TWRP file you downloaded into the same folder you made for Shawn5162's files. This folder has all the adb and fastboot files you need to perform the TWRP flash. Now hold shift and right click and choose open a command window here. Then ensure your device is detected by running the command adb devices, it should show your phones S/N and the word device. If it doesn't, you may need to look at your phone and respond to the prompt about allowing your computer to have access to adb. Try the command again after that. Then run the command adb reboot bootloader, which should reboot your phone to bootloader fastboot mode.
13. Once it fastboot mode run fastboot devices just to make sure your device is still detected, then run the command fastboot flash recovery twrp-2.8.7.1-clark.img. That will flash TWRP to your recovery partition. Then type the command fastboot reboot twrp-2.8.7.1-clark.img or use the volume rocker to toggle to recovery then select the power key to boot to it. Make sure you choose the slider at the bottom to allow modification. Once on the main screen you can choose reboot and then select recovery. This makes sure that you have booted to TWRP at least once, and ensures by rebooting to it, you can get back to it.
14. Now perform a Nandroid Backup, using the TWRP Backup option, of your completely stock MM system, data, boot, and EFS partitions. Enable compression if you like and store it to your External SD if you have one. This allows you to have an unrooted backup on your SD, which is good for future updates. After the Nandroid is complete now flash the modified boot image zip using the TWRP Install feature, and when it's complete, then flash the SuperSU zip file. After I always perform the option to erase Dalvik and Cache, I just think it is a good thing to do, it's probably placebo, but I do it anyhow.
15. Go back to TWRP Home and choose reboot and select system. Your device will reboot and you now have a fully updated and rooted Moto X Pure on MM.
Thanks go out to all the folks who have contributed to the many threads that contain this information. Special thanks to Shawn5162, DaMadOne, Chainfire, and Hashbang173 for their awesomeness. Hope this helps folks that are concerned about performing these procedures. I can say that it worked perfectly for me with no issues at all, but of course I take no responsibility if it doesn't work for you and causes your device to fail. Again these are similar steps I have taken in the past with other devices and I have never had a single brick, so hopefully it works for others as well.
Enjoy!!

I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?

I think I am in way over my head. I am receiving my phone Friday and was looking to unlock to root but from the looks of it, I will not be able to do that.
I've never unlocked & rooted a phone before. So all that looks like the bible to an uneducated man "me".

superkev72 said:
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
Click to expand...
Click to collapse
If I'm not mistaken it will download to your phone but not be able to be installed because of an error

Is there no way to upgrade from LP to MM without a wipe?

superkev72 said:
Is there no way to upgrade from LP to MM without a wipe?
Click to expand...
Click to collapse
Yeah, if you rooted already, you must reflash the original boot.img. Then update, and then restore your root. Read here:
http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
At the bottom of the post, you get the original file you need and it is mentioned here:
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
K?

Why would you want to update without a wipe? You must like sluggish performance

i have no wifi after this

No WIFI either
I ended up with no WIFI after following these steps also.

is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?

skimaniaz said:
I ended up with no WIFI after following these steps also.
Click to expand...
Click to collapse
Same here. Anybody got a fix?

So the last three posts complain of no wifi yet people keep using this method?

The modified boot zip breaks the wifi. You can root by flashing superSU 2.62, I think, or any SuperSU zip that is specifically systemless.

ilovemeow said:
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
Click to expand...
Click to collapse
Not true.

lafester said:
Not true.
Click to expand...
Click to collapse
coz i tried before, it fail in first 2 flash steps

Are you unlocked?

ilovemeow said:
coz i tried before, it fail in first 2 flash steps
Click to expand...
Click to collapse
The partition always fails. Just ignore it. You should be able to downgrade the bootloader. I have been able to so I don't know why you would be having issues with that unless your bootloader is locked/re-locked.
Sent from my XT1575 using XDA Labs

So is this safe or not?

lafester said:
Are you unlocked?
Click to expand...
Click to collapse
yup, it's unlocked, but currently fine for using android M at this moment

[marmite] Android 7.1.2 TOS163B official OTA link grabbed!

Hi everyone,
Since Wileyfox didn't want to supply us with Recovery and Fastboot images, and the update has arrived to my phone already, I've captured the OTA link with Wireshark, so that anyone can update to Android 7.1.2.
INCREMENTAL UPDATE (OFFICIAL LINK) (DRIVE MIRROR LINK by me) (from TOS118C to TOS163B / from aa4d5d86bc to 8eec3af77b)
Just as I have commented earlier,
linuxct said:
If you directly click (the official download link), it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible.
Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string.
Now here's the thing: if you want to switch the UA you'll need an extension to do so. I've used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX wfotaagent/2.3 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
Click to expand...
Click to collapse
Please, note the UA string has changed from rsotaua 1.0 to wfotaagent/2.3, which makes a bit more sense. Enjoy!

Thank you!
Can I update my phone with the OTA-File with TWRP?

For me the OTA failed (probably because I rooted my device) and after a restart it asked me to download again.
Is there a chance to install this update using this file with fastboot, twrp or adb?
BTW, if you are using Linux (or any other OS providing wget, I have actually only used it for Linux so I'm not sure if it's available for other OS) you can easily download the package:
Code:
wget --user-agent="wfotaagent/2.3" LINK_TO_OTA_AS_I_HAVE_TO_REMOVE_TO_BE_ALLOWED_TO_POST_UNTIL_I_REMOVE_THE_LINK
I am currently downloading it although I don't know if it will be useful to me.
P.S. Omg, sending this comment already keeps me busy for minutes to figure out which scripts to allow to be able to send.
P.P.S Iframes are very ugly, requiring google services also.
P.P.S Having to do this Captcha game for a second third fourth time after it already recognized I'm not a robot makes me think my first post here will be my last...
P.P.P.S I'll try to temporarily switch of everything concerning security and privacy to get this post done as i spent so much time and will return to be a passive reader again.

Cappucinto said:
Thank you!
Can I update my phone with the OTA-File with TWRP?
Click to expand...
Click to collapse
mdosch said:
For me the OTA failed (probably because I rooted my device) and after a restart it asked me to download again.
Is there a chance to install this update using this file with fastboot, twrp or adb?
Click to expand...
Click to collapse
You will need to reflash AOSP's recovery in order to install this update, but please do note it's an accumulative patch, not a "Patching system image unconditionally" kind of installation. If the contents of the system partition, or the boot image (yes, that's for us magisk users out there) are unexpected, it will stop the update, and probably try to roll it back.
Recommendation: Reflash AOSP's recovery, then the System image from TOS118C (I can provide those if needed), and then apply the update.
mdosch said:
P.S. Omg, sending this comment already keeps me busy for minutes to figure out which scripts to allow to be able to send.
P.P.S Iframes are very ugly, requiring google services also.
P.P.S Having to do this Captcha game for a second third fourth time after it already recognized I'm not a robot makes me think my first post here will be my last...
P.P.P.S I'll try to temporarily switch of everything concerning security and privacy to get this post done as i spent so much time and will return to be a passive reader again.
Click to expand...
Click to collapse
It's sad that XDA does that to junior members, tbh. With ten posts they'll remove all those restrictions, though. At least to me, it'd feel bad losing the interest of advanced users that might be new to the forum, yet are experienced in the topic.

linuxct said:
Since Wileyfox didn't want to supply us with Recovery and Fastboot images
Click to expand...
Click to collapse
I'm guessing they will release those eventually, right?

linuxct said:
Recommendation: Reflash AOSP's recovery, then the System image from TOS118C (I can provide those if needed), and then apply the update.
Click to expand...
Click to collapse
Hi can I have a link to the AOSP recovery please

Ok, I'll give this site a new try using a temporary fresh profile to not have to spoil my browsers settings.
After some playing around I got 7.1.2 installed and rooted. I'll write down what I did to get it finally work, but YMMV so be aware you might brick your phone.
I was using Debian 9 with fastboot and adb installed.
The steps I did:
Download and unzip the fastboot image from this thread: https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Boot to stock recovery and choose "apply update from adb"
Code:
adb sideload wf-marmite-aa4d5d86bc-to-8eec3af77b-signed.zip
After successful install wipe cache and dalvik/arts cache and reboot to system with the following command:
Code:
adb reboot "dm-verity enforcing"
When the update is configured let the phone switched on for a while (I don't know why, but it ended in a bootloop and I had to start again when I instantly rebooted)
After a while boot to bootloader.
Boot (not flash) twrp: http://twrp.me/devices/wileyfoxswift2.html
Code:
fastboot boot twrp-3.1.1-0-marmite.img
Go to "ADB -> Sideload" and install Superuser: https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Code:
adb sideload superuser.zip
Wipe cache and dalvik/arts cache and finally reboot with this command:
Code:
adb reboot "dm-verity enforcing"
I am not 100% sure if all steps are necessary but finally this worked for me and I am enjoying an up-to-date OS without loosing root.

I've downloaded the update as my 2X still hasn't updated.
I just cant get it to update via the recovery, my phone is default, no mods. I go to update from SD and it just errors with failed to mount SD. Even tried another SD card, same issue.
Am I missing something here? Cant be anything extra needed surely?

linuxct said:
I've captured the OTA link with Wireshark, so that anyone can update to Android 7.1.2.
Click to expand...
Click to collapse
Hello,
How did you get Wireshark to capture your phone's traffic? Did you use MITM or do I have to tweak my linux to make this work?
I tried searching online, but those didn't work for me.

boa05 said:
Hello,
How did you get Wireshark to capture your phone's traffic? Did you use MITM or do I have to tweak my linux to make this work?
I tried searching online, but those didn't work for me.
Click to expand...
Click to collapse
I put my windows pc in router mode using the wifi adapter, and ethernet bringing internet connection. Then it was as easy as capturing just that traffic.

Deleted due to development of Android ROM version

TWRP for P580 running Oreo?

Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!

I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!

Worked !!!
Thank you dear. Its worked for mine in p585 oreo android....
Anyone can search mcmilk 7zip in google and download program to extract boot.img.lz4 and get boot.img :good:

use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:

Latest twrp dose not worked on my device but this solution work fine

I can confirm that this method does work. I used it on my SM-P580 yesterday. I would suggest that you first backup your all of your apps, contacts, photos, etc using SmartSwitch. You will need to restore everything after the tablet tells you that it needs to be reset because it wipes everything. After the restore, you will need to enter all of your accounts and passwords again but at least all of the data will be back.
amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse

Im not sure if this post belongs here, you link to the T580 TWRP, not the P580.
Is that one compatible with P580?
nill3bor said:
use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:
Click to expand...
Click to collapse

If I do this, will I be able to mount my SD Card as internal storage? 16gb just isnt enough on this tablet.

Do you have to be on oreo already for this to work I'm still on 7.0 and with my system modified I can't upgrade normally

This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????

khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
This one worked for me on a P585Y. You just have to skip the steps below.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
Click to expand...
Click to collapse
It will also show on the Device Maintenance, just ignore the warning.
You can freeze some of the system apps to prevent it from showing on the notification again.

amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!

Hello Gyus,
I managed to root the device with the method posted by @amosdinh (Thank you so much). Now I'm trying to configure adoptable storage. So far I didn't achieve this goal. ADB commands doesn't work and I can't install the ASPlugin.zip needed by Root Essentials to set adoptable storage by the app.
TWRP for P585 is corrupted, gives blue/red lines screen. The dev that maintains the code is absent since march. I'm out of luck on this. If anyone have a idea to get adoptable storage on this device while using Oreo, please comment.
Thanks!
---------- Post added at 11:17 AM ---------- Previous post was at 11:11 AM ----------
artaeun said:
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!
Click to expand...
Click to collapse
Just renaming magisk_patched.img to boot.img and adding to .tar file by 7zip worked for me.

We should ask a dev to update twrp for android 8.1

khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
Same freeze for me with the Omni - can't do anything outside of access download mode

Same Problem
cmzizi said:
Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!
Click to expand...
Click to collapse
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.

luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
Really wish this wasn't the case. I'd actually keep this thing if it had a working TWRP.

On my SM-P580 I used Odin and TWRP I don't get the black screen but when I reboot to get into TWRP recovery mode it shows the padlock and says swipe to unlock. Tried many times bit cannot swipe and cannot get past this. All I want is to be able to use the SD card as internal storage. HELP???? Thanks!!

luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
thanks in advanced
where can i find stock firmware?

I've just installed magisk using TWRP via command line. P580
I've just installed magisk using TWRP via command line.
Read the entire post before trying this yourself.
I installed the latest TWRP, the one that bugs and doesn't display anything, this allows to root without wiping data. I'm running the latest korean firmware for P580.
Just do this:
1. Launch TWRP and INMEDIATELY LOCK YOUR SCREEN. (I got ghost stripes that disappeared after 2 days when testing this, work with low light so you can notice your screen whenever it tuens on) Please don't forget this point, don't [temporarily] damage your screen as I did.
2. adb push Magisk-v[Current version].zip external_sd
3. adb shell
4. twrp install external_sd/Magisk-v[Current version].zip
After this you just need to install MagiskManager-v[Current version].apk and you will be all done.
But there is one thing...
If you ever get into recovery mode, there is no way out without using adb as far as I know. You can launch download mode and cancel it but you'll boot back to TWRP.
When in twrp touching your screen or any button will wake the device up and will start burning the ghost image to your screen.
So if you know of a method for rebooting to system without using adb, please let me know.
Also a solution for this would be to flash back the stock recovery, wich may or may not force to wipe system, that something that needs to be tested tho.
Update: Ok so, you can use a handy tool called MTKroot on recovery.img.lz4 to get recovery.img, then use 7z to pack it into a tar file and flash that tar file with odin (AP, same as TWRP)
This way you will not have a 0.001% chance of random boot into recovery mode and damage your screen

I keep loosing root after reboot, Pls help.

Hey guys,
first time posting here so i dont kow how to style the text, so sorry about that.
last time i rooted a phone was on my sony xperia sp , where all i had to do was to go to towelroot .com and click to root.
I tryed to root my OP6T yesterday, after some setbacks i managed to sucessfully do it.
I did it like this:
1. Downloaded full ROM of OOS 10.3.2,
2. copied the payload to a program called payload dumper that extracted the boot image.
3. Copied the boot image to the phone
4. opened Magisk manager and selected install from source where i chose the boot.img
5. it created a copy called magisk_patched.img
6. booted in fastboot
7. on my pc used the command prompt to "fastboot boot magisk_patched.img"
booted normally and i had root.
but then problem appeared
#Problem 1
everytime i rebooted my phone i would loose root and it would say Magisk not installed. To get it back i would need to perform step 7 again and it was not ideal to do that everytime i turned off my phone.
#Problem 2
While tryng to solve problem 1 i read that i needed to open magisk manager and "Install to Inactive Slot (After OTA)."
After doing that it rebooted but now it wont boot at all, even if i try to "fastboot boot magisk_patched.img" the cmd gives me error:
fastboot boot magisk_patched.img
downloading 'boot.img'...
OKAY [ 0.838s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.845s
now my phone is just sitting there i dont want to reset it again. it would be the 4th time that i need to set up my phone in 2 days, so im trying to see if there are alternatives.
If reset is really the only way, i read that with root you can make a full backup of your phone and then restore it. How to do that? can i do it in the situation im in?
How can i root my OP6T running OOS10.3.2, and keep it? Whats the right method bc the one i followed seemed flawed.
I also tried one that had TWRP but maybe i did something wrong bc it didnt work., also there is no official one working for 10.3.2.

What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.

OhioYJ said:
What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.
Click to expand...
Click to collapse
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?

Davide1713 said:
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?
Click to expand...
Click to collapse
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.

OhioYJ said:
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.
Click to expand...
Click to collapse
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Once again thank you so much

Davide1713 said:
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Click to expand...
Click to collapse
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.

OhioYJ said:
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.
Click to expand...
Click to collapse
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?

Davide1713 said:
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?
Click to expand...
Click to collapse
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.

OhioYJ said:
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.
Click to expand...
Click to collapse
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough

GuestD2272 said:
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough
Click to expand...
Click to collapse
Not sure if you're still having this issue but I'll post the solution just in case anyone gets stumped, does a google search, and comes across this post. You were using the wrong command.
"fastboot boot" just lets you boot with the img so you can verify that root works.
"fastboot FLASH boot" will flash it and root will stick after reboot.
No need to jump through hoops with TWRP and such.