Database Users

Galaxy Grand Prime LTE (SM-S920L) / Lollipop 5.0.2 / Straight Talk

I just got one of the new Straight Talk Grand Prime variants from Walmart. I can't find ANYTHING on the model (SM-S920L) AT ALL. Anyone else get this model? I'm desperately seeking the stock recovery.tar for this phone as i attempted to flash a CWM recovery without backing up the stock firmware. Needless to say this didn't work and i was left with "recovery is not Seandroid enforcing"., when i attempt to boot into recovery.
HELP!!!!!
http://www.walmart.com/ip/Straight-Talk-Samsung-Prepaid-Galaxy-GRAND-Prime-LTE-S920C-Smartphone/46716301
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I have this SAME model. Im rooted with KING ROOT but cant find a custom recovery.

hondais1 said:
I have this SAME model. Im rooted with KING ROOT but cant find a custom recovery.
Click to expand...
Click to collapse
I just tried king root and it failed. I have the same model

I'll upload the version of KINGROOT that I have. Give me a few hours

Deejaydark said:
I just tried king root and it failed. I have the same model
Click to expand...
Click to collapse
That's odd...Kingroot worked like a charm for me as well. Do u have super su installed?

I think you're right. I think it has to be the newest version of King Root that doesn't use the kinguser app anymore(version 4.6.2). Oh! And I've submitted the files needed to fashion a custom recovery but haven't heard back yet. I will keep u guys posted.

Hydro_Axis said:
That's odd...Kingroot worked like a charm for me as well. Do u have super su installed?
Click to expand...
Click to collapse
Got it now

Hydro_Axis said:
I think you're right. I think it has to be the newest version of King Root that doesn't use the kinguser app anymore(version 4.6.2). Oh! And I've submitted the files needed to fashion a custom recovery but haven't heard back yet. I will keep u guys posted.
Click to expand...
Click to collapse
Finally, something is beginning to Surface on this model. Can you by chance upload the pit file? I bricked while I ventured into the unknown....every flash attempt fails....can't even do smart switched recovery. Hell, this model isn't even in Samsung's database.

adrwill2000 said:
Finally, something is beginning to Surface on this model. Can you by chance upload the pit file? I bricked while I ventured into the unknown....every flash attempt fails....can't even do smart switched recovery. Hell, this model isn't even in Samsung's database.
Click to expand...
Click to collapse
is this what your looking for? I know what u mean about not being able to find anything. I'd imagine its because the manufacture date is 6/15. This variant is still very new. I'm willing to do whatever i can to help get the ball rolling though.
Regards

Hydro_Axis said:
I think you're right. I think it has to be the newest version of King Root that doesn't use the kinguser app anymore(version 4.6.2). Oh! And I've submitted the files needed to fashion a custom recovery but haven't heard back yet. I will keep u guys posted.
Click to expand...
Click to collapse
Hydro_Axis said:
is this what your looking for? I know what u mean about not being able to find anything. I'd imagine its because the manufacture date is 6/15. This variant is still very new. I'm willing to do whatever i can to help get the ball rolling though.
Regards
Click to expand...
Click to collapse
Thanks for that! Except now I need a stock rom. I'm going to look into that one. Sounds like a task....I just want to get this puppy to work again.

Grand Prime sm-s920L
I am stuck in recovery mode and I have taken the battery out for a few and stick it back in and still stuck in recovery mode. How can I get out of this?

Same boat, but I am stuck in Odin mode. Made the mistake of trying to flash TWRP on it. Cannot find a the right one to reflash the ROM. I see many for other versions, but not ours.

Their isn't a custom recovery for this particular LTE version, I've seen one individual say.he got it to work with TWRP but he has to be bull****ting...their is the stock rom already posted to the forums tho if you can get it to were your able to flash it...I see that CWM has its own custom recovery builder on their site now I was wondering if that would actual work???

Medfordite said:
Same boat, but I am stuck in Odin mode. Made the mistake of trying to flash TWRP on it. Cannot find a the right one to reflash the ROM. I see many for other versions, but not ours.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gra...sm-s920l-straight-talkverizon-galaxy-t3252413
this is the link that someone has with the stock firmware. I got mine out of recovery by trying to odin the pit file but failed and it still booted back where i had my device. good luck

SM-S920L Rooted
Hello, i got my device to take ROOT in about an hour.
Here is the list of programs i used:
~Samsung USB Driver for Mobile Phones for Windows
~SuperSU apk v2.46
~Superuser apk v3.1.3
~One Click Root for Windows
~Kingo Root for Windows
~KingRoot for Windows
~Root Check apk
step 1. run as administrator: SamsungUSBDriver.exe (Windows)
step 2. Install Superuser.apk v3.1.3 (Android) does not require ROOT
step 3. run as administrator: One Click Root.exe (Windows) ROOT Will Fail
step 4. run as administrator: Kingo Root.exe (Windows) Root Will Fail
Step 5. run as administrator: Kingroot.exe (Windows) Device ROOTED
Step 6. Install SuperSU apk v2.46 (Android) Update Binary Normal
Step 7. Enjoy

That is an unnecessarily convoluted path to rooting this device. KingRoot apk v4.5.0 can literally root this phone is less than 5 minutes and SuperSU-ME Pro can replace KingRoot in a further 5 minutes.

Wonder if there's actually anyone making progress towards obtaining the Rom for this model.

Doubtful. There is zero interest in this variant.

Gahhh nooo, dont say that. Here's hoping an anon comes and saves the day sometime soon.

Hydro_Axis said:
I just got one of the new Straight Talk Grand Prime variants from Walmart. I can't find ANYTHING on the model (SM-S920L) AT ALL. Anyone else get this model? I'm desperately seeking the stock recovery.tar for this phone as i attempted to flash a CWM recovery without backing up the stock firmware. Needless to say this didn't work and i was left with "recovery is not Seandroid enforcing"., when i attempt to boot into recovery.
HELP!!!!!
http://www.walmart.com/ip/Straight-Talk-Samsung-Prepaid-Galaxy-GRAND-Prime-LTE-S920C-Smartphone/46716301
Click to expand...
Click to collapse
mr hydro i have this phone model too.. i love it but i bricked mine from messing with the build.rop fiel... if you see this reply i need you to post a full partition back up of your /system, /boot, /recovery folders or watever.. i was going to ry to flash in folders to fix my phone

[Discussion] Dumb attempt to upgrade to Marshmallow with TWRM in osprey

Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.

+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?

did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk

Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.

sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.

No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.

golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM

i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download

hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning

I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too

Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk

nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again

VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.

hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.

So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??

Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk

nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.

Boost E4 1766 Only Boots to TWRP

-Screwed up somewhere as my goal was to install LineageOS and try to use it on an At&t mvno.
-Package was unopened for months, so it still had the older firmware.
-Everything seemed okay after I unlocked the bootloader.
-Then I installed TWRP.
-Did a backup of everything using TWRP before I was going to try and root the device.
-I knew something was wrong when no verity opt encrypt and Magisk gave some error message and failed.
-Now whenever I boot the device, I get a N/A in the top left corner and then goes into TWRP.
-Restoring the backup using TWRP did nothing.
-I thought this would be the solution (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M), but I get the bad key first and then N/A before going back to TWRP.
https://forum.xda-developers.com/moto-e4/help/moto-e4-metro-variant-rebooting-to-twrp-t3825841
What should I do now?
Any help would be appreciated. Even links to other posts that dealt with this issue is fine. Be aware that my skill level is only a little better than following Youtube videos.
Thank you.

N/A is normal. It will be there forever after you unlock bootloader. Did you format data in TWRP and type yes to format?

Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.

ah-le-le said:
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
Click to expand...
Click to collapse
once you flash TWRP you have to flash a no verity zip and probably magisk and definitely format data to remove encryption for your phone to boot.

Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ah-le-le said:
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
Click to expand...
Click to collapse
I can't read that, LoL. Maybe... Failed toount data? That's because you're still encrypted.
Put the zips on external storage. Format data, type yes.
Now reboot recovery (not system) then flash the zips.
And you can take screenshots in TWRP.

Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.

One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.

ah-le-le said:
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
Click to expand...
Click to collapse
ah-le-le said:
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
Click to expand...
Click to collapse
Use caution going with a custom ROM on this device, especially with a mvno. You may score far more hurt than benefit. Also consider what you are trying to accomplished going with custom ROMs given the clean stability of Moto stock ROMs. Toss in Xposed framework and a few modules like Gravitybox for full control/customization.
OTA updates can not be processed with a custom recovery (one of several prerequisites that your device no longer meets). You may get notified but the update won't install; you'll be dumped into TWRP. You can easily disable the update engine and corresponding notifications on a rooted device.

October 2020 Security Update now available

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
October Security Update just released today.

Official 2020, October, MiA2 Stock fastboot ROM image V11.0.15.0.QDIMIXM link in appropriate thread: https://forum.xda-developers.com/showpost.php?p=83773363&postcount=144
CAPTCHA:
After clean fastboot flashing of this version with flash_all_except_data -> rebooting phone forces to stock recovery and requests factory reset.
Seems like after installing OTA possible behaviours are: either the same request for reset, or bootloop.
Reflashed back V11.0.14.0.QDIMIXM in order to make data backup

Aerobatic said:
Official 2020, October, MiA2 Stock fastboot ROM image V11.0.15.0.QDIMIXM link in appropriate thread: https://forum.xda-developers.com/showpost.php?p=83773363&postcount=144
Click to expand...
Click to collapse
nice! thanks for this!

Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.

Yes, the update seems buggy.
Even my phone was not able to start after the update.
Tried multiple times. Eventually had to factory reset it ?
xdxita said:
Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.
Click to expand...
Click to collapse

update works fine for me with no issues at all.

xdxita said:
Tried to apply update from OTA and my device failed to start, tried again and same result. Anyone else facing the same problem?
Tonight I'll try to flash full image directly.
Click to expand...
Click to collapse
same here, now I'll try to flash V11.0.14.0.QDIMIXM and let's see...
*update1*
It worked, I did flash_all_except_data and at first reboot it went to recovery and it showed up the same message saying that data may be corrupt but when I tried to boot it again it worked fine... now I'll backup everything and let's see if it works well at every reboot.
*update2*
everything fine running V11.0.14.0.QDIMIXM

So this is yet another botched update to skip, got it.
Thank you, brave ones who are willing to update first.
I'm just too afraid to update this device nowadays.

I had to reset device after last update this is really worst device support I had

For those who have reverted to V11.0.14.0.QDIMIXM, you don't have any bootloop on androidone screen?
My wife did the update, so I reverted to V11.0.14.0.QDIMIXM with flash_all_except_data but for now it still bootloop

updated successfully. there are no visible improvements

gromez said:
For those who have reverted to V11.0.14.0.QDIMIXM, you don't have any bootloop on androidone screen?
My wife did the update, so I reverted to V11.0.14.0.QDIMIXM with flash_all_except_data but for now it still bootloop
Click to expand...
Click to collapse
Try to switch to inactive slot.

How is your experience with stock rom and october patch?

HTCDevil said:
How is your experience with stock rom and october patch?
Click to expand...
Click to collapse
for me, it's snappy and stable.

Same problem here, unacceptable

Failed install here too, had to do a full reset
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
PereVidi_77 said:
same here, now I'll try to flash V11.0.14.0.QDIMIXM and let's see...
*update1*
It worked, I did flash_all_except_data and at first reboot it went to recovery and it showed up the same message saying that data may be corrupt but when I tried to boot it again it worked fine... now I'll backup everything and let's see if it works well at every reboot.
*update2*
everything fine running V11.0.14.0.QDIMIXM
Click to expand...
Click to collapse
I tried unsuccessfully to reboot, Everytime showed this message, finally I accepted to erase the phone and let download the backup, I lost some downloaded stuff I may download again later.
It's an Shane this happening to Android one devices, suddenly we got from special to second class citizens

I had the same problem, which was solved for me by going into fastboot and issuing a fastboot boot recovery which for some reason returned by phone to a working state with an update failed notification. will skip this one

oferwald said:
I had the same problem, which was solved for me by going into fastboot and issuing a fastboot boot recovery which for some reason returned by phone to a working state with an update failed notification. will skip this one
Click to expand...
Click to collapse
i have same probleme how you doing ?
Go in fastboot and after ?
Thanks. i dont want loss my picture on my phone.... mi a2

maxou88 said:
i have same probleme how you doing ?
Go in fastboot and after ?
Thanks. i dont want loss my picture on my phone.... mi a2
Click to expand...
Click to collapse
Hi,
All I did was go into fastboot using the power and volume shortcut, and than I connected the device to my laptop and issued the command:
fastboot reboot recovery
(naturally using the SDK Platform tools)
After that, the phone started working again. Although there is no reasonable reason it should have worked. I was surprised enough so that I decided to take the effort to create an account here and share this for others. But again, maybe it was pure luck, YMMV.
Will be crossing my fingers for you.

I've tried to update and got the "Can't load Android system. Your data may be corrupt" messege. Tried again a few times, until the phone reverted back to the previous version and said it couldn't install the update. No October update for me. =(

Updating from 10 to 11 with root

Ok, so I'm gonna do the update to android 11 now that it seems to be more stable. My question is, once I do that, and I keep root, is there a way to do a factory data reset and not lose root all together? I like to do a factory reset when doing a major update just to make sure things run as smooth as possible, but I'd like to not lose root in the process. Thanks in advance!

Root (aka Magisk) IMHO resides in the boot image, so a factory reset would not interfere with root itself. Of course you would need to reinstall Magisk manager (Canary) after the factory reset. Oh, and you need to be on Canary Magisk for A11 anyway - so if you do the update from A10 you need to make sure you are on Magisk Canary (Manager and Magisk itself) or it won't work afterwards...

s3axel said:
Root (aka Magisk) IMHO resides in the boot image, so a factory reset would not interfere with root itself. Of course you would need to reinstall Magisk manager (Canary) after the factory reset. Oh, and you need to be on Canary Magisk for A11 anyway - so if you do the update from A10 you need to make sure you are on Magisk Canary (Manager and Magisk itself) or it won't work afterwards...
Click to expand...
Click to collapse
Nope latest beta works great too. Canary isn't needed anymore.

imneveral0ne said:
Ok, so I'm gonna do the update to android 11 now that it seems to be more stable. My question is, once I do that, and I keep root, is there a way to do a factory data reset and not lose root all together? I like to do a factory reset when doing a major update just to make sure things run as smooth as possible, but I'd like to not lose root in the process. Thanks in advance!
Click to expand...
Click to collapse
I have guides for this and for 11-11 they're in the guides section.
Thoroughly tested.

Kollachi said:
Nope latest beta works great too. Canary isn't needed anymore.
Click to expand...
Click to collapse
So I just need beta magisk and the regular app? Cause I just installed the canary magisk manager and it's missing quite a few options like magisk hide and such. And I definitely need those.

dladz said:
I have guides for this and for 11-11 they're in the guides section.
Thoroughly tested.
Click to expand...
Click to collapse
That is a lot more involved than I was expecting this to be. I figured I could just retain root with an update the same way I always do.

imneveral0ne said:
That is a lot more involved than I was expecting this to be. I figured I could just retain root with an update the same way I always do.
Click to expand...
Click to collapse
It's 9 steps?
You need to remove modules, you will need to use the updated boot img and your won't have twrp to fall back on.
If you want to wipe after you'll need to set up then reinstall magisk then obtain your boot img, patch it and boot it then flash it directly.

dladz said:
It's 9 steps?
You need to remove modules, you will need to use the updated boot img and your won't have twrp to fall back on.
If you want to wipe after you'll need to set up then reinstall magisk then obtain your boot img, patch it and boot it then flash it directly.
Click to expand...
Click to collapse
It's not that, it's just that I usually used a pretty simple guide for updates and I didn't need to do anything on the computer for it to work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it because we're updating from 10 to 11 that these extra steps are needed? Sorry, I'm just curious is all.

imneveral0ne said:
It's not that, it's just that I usually used a pretty simple guide for updates and I didn't need to do anything on the computer for it to work.
Is it because we're updating from 10 to 11 that these extra steps are needed? Sorry, I'm just curious is all.
Click to expand...
Click to collapse
No not at all.
Tbh it's extremely similar.
Just that the way I've written it means you won't have issues, I'd rather cover bases in a guide than answer a 100 questions later.
If you have magisk functional already then you're halfway there.
I've updated the OP in my guide.
Some steps are informational

dladz said:
No not at all.
Tbh it's extremely similar.
Just that the way I've written it means you won't have issues, I'd rather cover bases in a guide than answer a 100 questions later.
If you have magisk functional already then you're halfway there.
I've updated the OP in my guide.
Some steps are informational
Click to expand...
Click to collapse
I installed the canary built of magisk from your thread, but there isn't an install button. ?
Edit: I went back to the beta build and it worked fine with patching.

imneveral0ne said:
I installed the canary built of magisk from your thread, but there isn't an install button. ?
Edit: I went back to the beta build and it worked fine with patching.
Click to expand...
Click to collapse
Good stuff..so what channel did you change it to.? Are you able to provide a version as someone has the exact same issue.

dladz said:
Good stuff..so what channel did you change it to.? Are you able to provide a version as someone has the exact same issue.
Click to expand...
Click to collapse
Just the beta channel. And I can once I get my phone working again lol. You straight up told me I was gonna need to use this to root my phone after a factory reset. And I went ahead and installed twrp anyway. Using the msm tool now to fix it lol.

imneveral0ne said:
Just the beta channel. And I can once I get my phone working again lol. You straight up told me I was gonna need to use this to root my phone after a factory reset. And I went ahead and installed twrp anyway. Using the msm tool now to fix it lol.
Click to expand...
Click to collapse
Lol no worries man. Glad you're up and running.
:good: