Related
Hi,
I've got an Samsung Galaxy S7 which won't boot android anymore. this was after the phone was hot.
Recovery and download mode works. Is there a way to copy photos to a computer or sdcard somehow?
Thanks
arjanv said:
Hi,
I've got an Samsung Galaxy S7 which won't boot android anymore. this was after the phone was hot.
Recovery and download mode works. Is there a way to copy photos to a computer or sdcard somehow?
Thanks
Click to expand...
Click to collapse
If you connect your phone to your computer - Does the computer see the phone?
If you have your music and photos on the external sd card (if your pc doesn't see the phone) you could copy from the external sd card with a sd card reader - I believe that if you can boot into recovery that you can cope files from the phone to the pc as well.
Sent from my SM-G930W8 using Tapatalk
shaggyskunk said:
If you connect your phone to your computer - Does the computer see the phone?
If you have your music and photos on the external sd card (if your pc doesn't see the phone) you could copy from the external sd card with a sd card reader - I believe that if you can boot into recovery that you can cope files from the phone to the pc as well.
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
no external sd card, otherwise there was no problem
Could we have some more information please?
Is the device Knox tripped or otherwise modified? (Rooted, custom recovery, custom firmware)
What's the model number?
What's the firmware build number?(The stock recovery will say).
Is the device encrypted?
(If you've set up Samsung Cloud or Google Photos backup you might have better luck there)
I don't think you can enter MTP mode with the phone only working from recovery and download mode. Simply install a ROM via TWRP but do not wipe internal storage. Once the phone boots up to android, retrieve your files.
Good luck
I'm able to boot in download mode.
Odin recognize the phone. is flashing possible without loosing data(only care about stuff on the internal SD card. loosing settings and apps is not a problem.
added attachment/screenshot.
arjanv said:
added attachment/screenshot.
Click to expand...
Click to collapse
Official firmware, so likely encrypted. Boot into recovery and take note of the build number and CSC. Download the exact same firmware from a site like SamMobile. Using Odin, flash the BL, AP, CP and HOME_CSC(NOT the plain CSC) packages in the firmware package by placing them in their relevant slots. It will make like it's doing a system update and take long to boot, but should result in a workable device with your data intact.
hi seems that recovery not working either,i've tried but can't get into recovery. sometimes a red text appears on the top left screen. something about sandforcing.
CurtisMJ said:
Could we have some more information please?
Is the device Knox tripped or otherwise modified? (Rooted, custom recovery, custom firmware)
What's the model number?
What's the firmware build number?(The stock recovery will say).
Is the device encrypted?
(If you've set up Samsung Cloud or Google Photos backup you might have better luck there)
Click to expand...
Click to collapse
CurtisMJ said:
Official firmware, so likely encrypted. Boot into recovery and take note of the build number and CSC. Download the exact same firmware from a site like SamMobile. Using Odin, flash the BL, AP, CP and HOME_CSC(NOT the plain CSC) packages in the firmware package by placing them in their relevant slots. It will make like it's doing a system update and take long to boot, but should result in a workable device with your data intact.
Click to expand...
Click to collapse
What about this? https://www.youtube.com/watch?v=cyCileqUVFQ they seems to flash only AP. Whats the different in results of flashing only AP or Flash AP, BL, CP and HOME_CSC?
arjanv said:
What about this? https://www.youtube.com/watch?v=cyCileqUVFQ they seems to flash only AP. Whats the different in results of flashing only AP or Flash AP, BL, CP and HOME_CSC?
Click to expand...
Click to collapse
Samsung old and new style of firmware packaging. They used to place all parts into a single package(AP), customised per region. This had the disadvantage of requiring a complete different firmware package for every region with little actual differences. New Samsung firmware comes broken up into the BL(bootloader), AP(system, kernel, recovery), CP(modem firmware) and CSC(recovery package which applies all region settings) packages. This way only the CSC needs to be changed per region.
At absolute minimum you should flash the AP and HOME_CSC/CSC package. (Though only if you're sure you're flashing the same firmware as the current or you may trip knox)
The general rule is if you flash AP, then CSC must be flashed aswell, otherwise the firmware becomes very buggy.
The regular CSC file wipes storage, while HOME_CSC does not, but will only work if the current CSC matches the firmware package
If you like you may use Smart Switch Emergency firmware recovery instead, but beware, as it's known to mess up more often than not
arjanv said:
hi seems that recovery not working either,i've tried but can't get into recovery. sometimes a red text appears on the top left screen. something about sandforcing.
Click to expand...
Click to collapse
Did it perhaps say "SEAndroid not enforcing"? That means it's an unofficial recovery image. Not sure how that could happen. Seems like firmware was corrupted somehow.
thanks for explaining.
I've download the latest firmware from sammobile which contains these files:
AP_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship_meta.tar
BL_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship.tar
CP_G935FXXU1DQD7_CL11104523_QB13263377_REV00_user_low_ship.tar
CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
HOME_CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
I want to save photos, so i try to flash AP and HOME_CSC using odin right?
arjanv said:
thanks for explaining.
I've download the latest firmware from sammobile which contains these files:
AP_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship_meta.tar
BL_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship.tar
CP_G935FXXU1DQD7_CL11104523_QB13263377_REV00_user_low_ship.tar
CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
HOME_CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
I want to save photos, so i try to flash AP and HOME_CSC using odin right?
Click to expand...
Click to collapse
Wrong firmware I'm afraid. Notice your screenshot says the device is a SM-G930F, these are SM-G935F files for the Galaxy S7 Edge. Also, since we don't know what firmware revision the device is on, you *need* to flash the BL and CP parts too.
Could you please check the bottom of your box? You need the three-letter CSC code. If you get it wrong your data is toast.
So final process is:
1. Check your box for the CSC code
2. Select your CSC in the "Select Country" dropdown https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/
3. Download the latest firmware
4. Flash BL, AP, CP and HOME_CSC from the package.
5. Device should auto-reboot and will ask you for your lockscreen passphrase.
oops, sorry. copy paste the wrong files.
i meant these files:
AP_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship_meta.tar
BL_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship.tar
CP_G930FXXU1DQD7_CL11104523_QB13263348_REV00_user_low_ship.tar
CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
HOME_CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
arjanv said:
i meant these files:
AP_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship_meta.tar
BL_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship.tar
CP_G930FXXU1DQD7_CL11104523_QB13263348_REV00_user_low_ship.tar
CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
HOME_CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
Click to expand...
Click to collapse
If your CSC code is PHN then yes.
CurtisMJ said:
If your CSC code is PHN then yes.
Click to expand...
Click to collapse
this says the box. see attachment
tried to flash and now this message(see attachment)
what now?
found this on a other post.
just extract your firmware with win rar and copy recovery.img to your desktop
there is a tool for making .tar file from .img called tar-Tool .
with tar tool you can make .tar from .img files
convert recovery.img to recovery.tar with this tool
flash it in pda (AP) in odin . now you can go to recovery mode
then wipe data/factory reset and wipe cache
rebooot
arjanv said:
tried to flash and now this message(see attachment)
what now?
found this on a other post.
just extract your firmware with win rar and copy recovery.img to your desktop
there is a tool for making .tar file from .img called tar-Tool .
with tar tool you can make .tar from .img files
convert recovery.img to recovery.tar with this tool
flash it in pda (AP) in odin . now you can go to recovery mode
then wipe data/factory reset and wipe cache
rebooot
Click to expand...
Click to collapse
That means Odin didnt finish one of its operations. You need to use Odin 3.12+. The device wont let you do anything else until it registers a successful flash in download mode.
I think it's best to just use Smart Switch.
https://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/flash-stock-firmware-using-samsung-t3079176
Video is for S6, but the process is the same.
Beware that the internal SD will be wiped, but since the CSC is nowhere to be seen I think thats the only way, sorry.
EDIT:
Getting back to download mode:
https://forum.xda-developers.com/showpost.php?p=68632831&postcount=5
I've wrote it in many thread and I report here for users that want:
stay stock and updated
root (with Magisk)
unencrypted
never lose data and configuration
Here's my procedure, I'm using it since since I bought my S8 exynos (jun 2017), never had a problem, never lost a single bit of my data. And I don't know any alternative until now.
G950FXXU4DSDA (pie) tested​
I assume you have:
unencrypted device
oem unlock option checked (never uncheck it)
stock rom: any system mod is ok, but you'll lose it
What you need:
last odin (download here)
last stock rom for your country (download here)
last twrp on your exynos device (download here)
last Magisk zip on your device (download here)
Here's the steps:
if you haven't did before, create a magisk config file executing this two command on a shell (this file remain until you clean /data partition):
Code:
echo KEEPVERITY=false>>/data/.magisk;
echo KEEPFORCEENCRYPT=false>>/data/.magisk;
extract the rom and delete CSC_OXM_G950Fxxx (you don't need it, this file do the factory reset we don't want)
reboot you phone in download mode (boot with voldown+power+bixby)
connect your phone (you already have the driver, right?)
select all files in odin
uncheck auto-reboot option
press start
at the end manually restart the phone with voldown+power
the phone will boot in stock recovery and complete the installation ("Installing system update..." and "Erasing...")
keep attention because when rebooting you have to put your finger on voldown+power+bixby to return in download mode (if system boot your data partition will be encrypted)
in odin select TWRP file in AP slot
check auto-reboot option
put your finger on volup+power+bixby and keep there
press start
after a while you'll be in TWRP and you can relase the finger
flash Magisk
reboot in system
Then you can do any other mod you wan't, my favourites here.
I wrote this thread because all the guides I found skip the important (and tricky) 9-10 step and my tests results in:
interrupted csc install (twrp tried to execute a script producing "Error installing zip file 'CACHE:recovery/sec_omc.zip'")
empty CSC (Phone Info app) and no /system/omc folder
phone works well, but i'm not sure I was using VoLTE because I didn't see the icon
dial codes aren't working
korean operator "KT" voice in settings
Anyone else tried this method? Hoping to give it a try later this week when I have some time should something go wrong
so on s8 works too. nice. I've been doing this on my S7 edge every FW update. dirty flash, then root then xposed. So I hope this trick works in my S8 too.
are you on Nougat or Oreo?
Yea it works just fine, dirty flash can cause issues though. Might wanna let people know that.
t12icky0 said:
Yea it works just fine, dirty flash can cause issues though. Might wanna let people know that.
Click to expand...
Click to collapse
this way works like an ota for my experience, not a single issue in one year of updates
Can i root in your way? Im on CRD7 all stock, unroted.
If i follow your guide will be my phone rooted?
Sent from my SM-G950F using Tapatalk
zelenko said:
Can i root in your way? Im on CRD7 all stock, unroted.
If i follow your guide will be my phone rooted?
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
if you've never modify the phone, you're encrypted
if you,re encrypted, you need to format your data partition to get root permission (for what I know is not possible / not safe to stay encrypted)
you can follow my guide adding a format data step before flashing supersu, but the phone will be factory reset
so after doing this i'll still get ota updates and i can install them fine plus having the root privileges ?
No, I've never tried ti install otas (I expect it will fail).
To stay updated you have to repeat the procedure whit the new stock image, usually released before the ota.
pie tested ​:good:
Does is still work? I want to upgrade to Pie but dont want to wipe and lose all data.
Is it still rooted after?
Sorry i'm a noob
S8 rooted
TWRP and Magisk
can you help me please???
silverik1 said:
Does is still work? I want to upgrade to Pie but dont want to wipe and lose all data.
Is it still rooted after?
Sorry i'm a noob
S8 rooted
TWRP and Magisk
Click to expand...
Click to collapse
Confirming, it's working perfectly
@c3k ,
Thanhs for this great solution !!
m.
I still have the stock rom and rooted with magisk. But in twrp I can not mount the data partition. Is it because it's still encrypted ?
... that's what I assume but it`s strange because you should be decrypted already after formatting data installing twrp, magisc etc. ...
m.
Yeah..I know...any suggestions ?
... it sounds like a data format is needed then ... Or does this method from c3k work for you ... ?
You `ve the latest TWRP installed?
m.
How do I install the latest one if I have an older version ? Can I use flashify for it ?
Or with twrp itself ?
I install new twrp via the installed one as an img file.
m.
I've always wanted to post one of these
https://developers.google.com/android/images
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol
Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.
spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.
What is this update 4.3mb
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.
Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.
boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk
Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01
is there new platform tools too?
[UPDATE/KEEP ROOT GUIDE] Jun 2020 (QQ3A.200605.001) "CORAL" Magisk-Patched Boot Image
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
Hey guys, yup, I'm still furloughed... ;_;
So anyway, here are the factory and Magisk Patched (v.24 is still the latest as of typing this) boot images for the June 2020 (QQ3A.200605.001) update.
ALL FILES BELOW ARE FOR JUNE 2020 QQ3A.200605.001!
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=4349826312261824138
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=4349826312261824136
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=4349826312261824137
THESE FILES ARE FOR "10.0.0 (QQ3A.200605.001, Jun 2020)" ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!
Everything seems to work fine so far. Magisk v.24 and EdXposed 5.0.0 (4548 YAHFA). SafetyNet Passing for now... Kirisakura 4.7.5 (just released today!) works great too!
If these files and/or guides are helpful, please drop a thanks and let me know. Thanks! =)
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide exactly if coming EXACTLY from build qq2a.200501.001.b2, May 2020. But the general idea is the same for other builds, you just need the correct files for your device.
coral-qq2a.200501.001.b2-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261824163
coral-qq2a.200501.001.b2-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261796399
June 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-qq3a.200605.001-3b5bb1bd.zip
I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-qq2a.200501.001.b2-factory-boot.img
3. fastboot flash dtbo coral-qq2a.200501.001.b2-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-qq3a.200605.001-3b5bb1bd.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-qq3a.200605.001-magisk_patched-20.4.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)
This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
...More details and guide / cleanups to come. I'm home alone today and taking care of our 5 month old, and he just woke up!!!
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Doesn't work. Even recreating all the patched img files on my own, after a full factory reset, results in a boot to black screen with only the power menu available.
No clue why, unrooted with stock boot.img works fine
edit: should note that this is even without any modules
Shayded said:
Doesn't work. Even recreating all the patched img files on my own, after a full factory reset, results in a boot to black screen with only the power menu available.
No clue why, unrooted with stock boot.img works fine
Click to expand...
Click to collapse
Weird that it wouldn't work even after a full factory reset. Unfortunately I don't have a means of testing that. I edited my 3rd post with some troubleshooting instructions, sort of copied and pasted from my previous thread. You said you already factory resetted and it still doesn't work, but I would have otherwise recommended checking Tulsadiver's thread (he has an updated pre-made Magisk Core-Only mode boot image on his thread) in order to find and disable the bad module. Again, since you already tried factory reset, that wouldn't really apply and that's very strange.
I attached screenshots to the OP that shows it working... Sorry I can't help much more. The baby needs to be fed now...!! Typed all this while warming up the milk bottle...
i5lee8bit said:
Weird that it wouldn't work even after a full factory reset. Unfortunately I don't have a means of testing that. I edited my 3rd post with some troubleshooting instructions, sort of copied and pasted from my previous thread. You said you already factory resetted and it still doesn't work, but I would have otherwise recommended checking Tulsadiver's thread (he has an updated pre-made Magisk Core-Only mode boot image on his thread) in order to find and disable the bad module. Again, since you already tried factory reset, that wouldn't really apply and that's very strange.
I attached screenshots to the OP that shows it working... Sorry I can't help much more. The baby needs to be fed now...!! Typed all this while warming up the milk bottle...
Click to expand...
Click to collapse
yeah it's very odd. The second I try to boot even a clean factory image with a patched boot.img it just gives the black screen.
You guys still have motion sense ?
i can't make it work with magisk....
i tryed factory reset, it worked but once magisk is installed no more motion sense for me..( safetynet is ok...just in case )
any help please ?
i tryed a few things with props edit but no luck
Used this guide to come from the April update, everything seems to be working without issue.
****EDIT
So was bored and wanted to do some testing and it seems to be magisk modules that are most likely causing the majority of the issues
I flashed via fastboot then booted from the 6-2-20 image of this post and disabled all of the modules except the riru core and edxposed
Then rebooted to fastboot and flashed the patched boot image from OP works like a charm for anyone having issues.
EDIT***
Really strange outcome after doing this method for this month's update.
I'm on the smaller Pixel 4 but having been using your threads as a cheat sheet for a while. After the update was installed and magisk-patched boot images was flashed, it booted but I couldn't pull down my notification bar the second time to get into settings, couldn't enable mobile data, couldn't access storage from PC (notification to select USB options wasn't there), no notifications where shown but sounds were still coming in, no developer options, and a ton of other weird stuff. Overall, it seemed like it somehow only installed half the system since it felt like it was missing a lot of options and features. Tried reflashing the full factory image which did not seem to help. Only was able to get it functioning again through a clean install. No clue as to what could've happened this time around.
Copy and pasted method, just as you did in previous month. Your EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS is flawless for me.
baleskoil said:
You guys still have motion sense ?
i can't make it work with magisk....
i tryed factory reset, it worked but once magisk is installed no more motion sense for me..( safetynet is ok...just in case )
any help please ?
i tryed a few things with props edit but no luck
Click to expand...
Click to collapse
That's weird. I just tested it and it worked fine. I only have it enabled for alarms, and that's all I tested for though.
edit: I just tested on my wife's phone which I just updated (it's a Pixel 4, non-XL) and she uses the pause / skip motion sense, and it all works fine after updating... sorry man.
xxxtncxxx said:
****EDIT
So was bored and wanted to do some testing and it seems to be magisk modules that are most likely causing the majority of the issues
I flashed via fastboot then booted from the 6-2-20 image of this post and disabled all of the modules except the riru core and edxposed
Then rebooted to fastboot and flashed the patched boot image from OP works like a charm for anyone having issues.
EDIT***
Click to expand...
Click to collapse
I'm attaching a list of all of my Magisk and EdXposed modules being used to this post. So far, I haven't had any issues whatsoever. Not sure if it'll be helpful, but seems ppl are having scattered issues with this update. Tbh, I don't have a huge number of modules, at least I think relatively.
tysj said:
Really strange outcome after doing this method for this month's update.
I'm on the smaller Pixel 4 but having been using your threads as a cheat sheet for a while. After the update was installed and magisk-patched boot images was flashed, it booted but I couldn't pull down my notification bar the second time to get into settings, couldn't enable mobile data, couldn't access storage from PC (notification to select USB options wasn't there), no notifications where shown but sounds were still coming in, no developer options, and a ton of other weird stuff. Overall, it seemed like it somehow only installed half the system since it felt like it was missing a lot of options and features. Tried reflashing the full factory image which did not seem to help. Only was able to get it functioning again through a clean install. No clue as to what could've happened this time around.
Click to expand...
Click to collapse
Oh no, please don't tell me you flashed any of the files from this thread? They're very different phones in that sense and you need to use the correct files. We just put the little guy down to sleep so I'll write up that thread really quick on the P4 forums. Flashing a full factory image is pretty much the same as a clean install though? Are you sure you were using the correct files? Anyway, the post for P4 will be up in just a few min. (I'm actually updating my wife's phone as I type this, lol)
edit: here ya go: https://forum.xda-developers.com/pixel-4/how-to/update-root-guide-jun-2020-qq3a-200605-t4109307
onlyguynamedniles said:
Copy and pasted method, just as you did in previous month. Your EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS is flawless for me.
Click to expand...
Click to collapse
Thanks for the feedback, you're welcome!
i5lee8bit said:
Oh no, please don't tell me you flashed any of the files from this thread? They're very different phones in that sense and you need to use the correct files. We just put the little guy down to sleep so I'll write up that thread really quick on the P4 forums. Flashing a full factory image is pretty much the same as a clean install though? Are you sure you were using the correct files? Anyway, the post for P4 will be up in just a few min. (I'm actually updating my wife's phone as I type this, lol)
Click to expand...
Click to collapse
No worries, mate. I used my own files. Downloaded many times just to make sure I had the right package. Still not really sure what happened as flashing the factory images should have fixed whatever was going on. Not an ideal situation, but works out since I had to do a factory reset to fix a separate backup issue anyway.
tysj said:
No worries, mate. I used my own files. Downloaded many times just to make sure I had the right package. Still not really sure what happened as flashing the factory images should have fixed whatever was going on. Not an ideal situation, but works out since I had to do a factory reset to fix a separate backup issue anyway.
Click to expand...
Click to collapse
Lol, I edited the post with the link to the other thread right after you responded I guess. Anyway, yeah, that's weird. Could be the cable, corrupt files, or a big number of things. Glad you got it sorted out though! :good:
Thanks for this. I've been following your guide the last few months since its brainless work for me. I checked for your thread yesterday but it wasn't up yet so didn't bother updating. I will tonight but thought I'd say thank you for the guide in advanced - its much appreciated
@i5lee8bit
Thx for your answer i ll try a bit more on my own
baleskoil said:
@i5lee8bit
Thx for your answer i ll try a bit more on my own
Click to expand...
Click to collapse
Hey what modules are you using? Try booting up in Magisk Core Only Mode (or just try disabling all modules and reboot). You can easily boot in core mode if you're not bootlooping by just going to Magisk Manager settings and toggling core only mode. The only thing I could think of is a module not playing nicely, especially if it works when stock. Either that, or maybe there's something you need to Magisk Hide. The only things I have hidden are the stuff recommended in eg1122's thread (https://forum.xda-developers.com/pixel-4-xl/how-to/xposed-discussion-thread-t3992607) plus a few extra things like Netflix and some banking apps. But seeing as how it works when stock for you, it's definitely not hardware related so I would suspect another tweak messing with it. Good luck!
Edit/PS: I got curious this morning and tried on my own phone, and all motion sense functions still work, btw
ouch ...dumb mistake.... I was so focused on passing safetynet i forgot about magisk hide ^^
thx for your help ^^
"** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images"
Does this mean I only need to flash the boot.img and not the dtbo.img if I'm using the stock kernel?
knudsen83 said:
"** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images"
Does this mean I only need to flash the boot.img and not the dtbo.img if I'm using the stock kernel?
Click to expand...
Click to collapse
Correct, I'm guessing you already got it sorted out by now but in case you're wonderinf it wouldn't hurt to flash stock dtbo over stock dtbo either.
Just a heads up to anyone who is wondering about root for this phone - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus model, and it worked. Obviously you need to have already unlocked the bootloader before doing any of this.
I got the stock boot.img from the firmware linked in this thread. I patched it using Magisk Manager (v8.0.7) then flashed it via fastboot. My installed Magisk version is 21.4 (21400).
-- A WORD OF CAUTION: --
As of now there is no TWRP or any other custom recovery for this phone that I am aware of, so if you mess something up due to root, your only option to fix it might be to reflash the stock firmware.
A note about mobile banking apps:
After I installed Magisk Manager, my banking app stopped working and SafetyNet check was failing. After flashing the patched boot.img and rebooting, the SafetyNet check passed but my banking app still wasn't working. I used Magisk Hide and checked off the banking app in the list, but that didn't help either. What I had to do was use the Hide Magisk Manager option where it reinstalls Magisk Manager under a different name. Now my banking app is working again.
DM.IDOL said:
... - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus model, and it worked. ...
Click to expand...
Click to collapse
It worked for me too. It was also easy for me because the only RETUS upload on the mirrors.lolinet site was my exact firmware version. Downloaded that, extracted and used that boot.img for magisk-patching.
The only issues I'm left with are:
1. Adaway isn't working (can't write to any of the canned hosts file paths) and I haven't figured out where I might be able to store a writable hosts file, and . . .
2. Titanium Backup (Pro) works to freeze almost every app that I wanted to disable. The one exception was Motorola Update Service. TiBu toasts that it was disabled and "invisible from the app drawer", but it actually wasn't disabled and still isn't. It still shows under System Applications. So I dunno . . . it's not a deal breaker as long as auto updating stays turned off.
Bootloader is unlocked and rooting via Magisk worked on my Stylus 2021, exactly as advertised.
Update: My solution for AdAway was here, AdAway 5.3 (newest version I believe).
Update2: Sans freezing Motorola Update Service, updates are of course frozen from actually running because of system changes by root & TWRP. So no big worries, just the nuisance of notifications.
cant the new maagisk be used as an alternative custom recovery? Something about renaming the apk to zip and then flashing zip file on recovery?
Mr.Morgan said:
cant the new maagisk be used as an alternative custom recovery? Something about renaming the apk to zip and then flashing zip file on recovery?
Click to expand...
Click to collapse
No, Magisk is not custom recovery.
There are two ways to install Magisk, using the .zip version, with a custom recovery like TWRP or
Using the magisk app to patch a boot.img then flash with fastboot.exe
sd_shadow said:
No, Magisk is not custom recovery.
There are two ways to install Magisk, using the .zip version, with a custom recovery like TWRP or
Using the magisk app to patch a boot.img then flash with fastboot.exe
Click to expand...
Click to collapse
I appreciate the knowledge, but perhaps you can shed some light on what the app means by " Custom Recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC. Check out the updated installation guide for more info"
Mr.Morgan said:
I appreciate the knowledge, but perhaps you can shed some light on what the app means by " Custom Recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC. Check out the updated installation guide for more info"
Click to expand...
Click to collapse
You are partly correct, there has been a big change with Magisk.
You can just change the Magisk.apk to Magisk.zip
But the zip does not replace a custom recovery.
It just eliminates the need for a separate manager.zip
In some custom recoveries, the installation may fail silently (it might look like success but in reality it bootloops). This is because the installer scripts cannot properly detect the correct device info or the recovery environment does not meet its expectation. If you face any issues, use the Patch Image method as it is guaranteed to work 100% of the time. Due to this reason, installing Magisk through custom recoveries on modern devices is no longer recommended. The custom recovery installation method exists purely for legacy support
Click to expand...
Click to collapse
Magisk in Recovery
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.
When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.
Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.
Click to expand...
Click to collapse
This does not replace the stock recovery, just patches the recovery.
I recently purchased this phone, Moto G Stylus 2021, from Amazon. When I enter the dev options menu, OEM Unlocking is greyed out. I did a bit of research and found another thread online where another two users had the same problem, for all of two days.
After two days, the option to enable OEM Unlocking was no longer greyed out for the both of them. Fascinating! I may return this phone before that time is up, but if I don't, I'll report back on any changes for sure.
EDIT: I've decided to return this phone and get a Galaxy Tab S7 instead; there's more room to draw and a better pen!
Can't find my firmware on lolinet (boost mobile qpc30.q4-31-93)
Tried lenovo's rescue tool to see if I could grab the firmware that way and it just kept giving me errors.
If anyone has some how acquired the appropriate firmware would you mind sending it to me?
I can't remember exactly where I seen someone else commenting on this topic but they had lost their cellular network after rooting ,
My problem / question is that I have also my lost my cellular network connection after rooting but not completley only to the original carrier I got t this phone with witch is boost, but if I try another carrier such as tmobile or sprint or even metro it will work because they are basically all 1 company now , but how do I fix this problem to get my phone to read my sim card as valid (I get the invalid sim msg) when I put my original sim in and I just went and got a brand new replacement sim from them to see if that would solve the issue.also going off reading the forums on here I went with the mask retus firmware for flashing because there isn't one on there anywhere for so any help would be hysteria l greatly appreciated. This is my only problem I'm having since rooting everything else is working perfectly fine.
BobbyBlunt said:
Can't find my firmware on lolinet (boost mobile qpc30.q4-31-93)
Tried lenovo's rescue tool to see if I could grab the firmware that way and it just kept giving me errors.
If anyone has some how acquired the appropriate firmware would you mind sending it to me?
Click to expand...
Click to collapse
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
riggin said:
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
Click to expand...
Click to collapse
I tried the lenovo recovery tool again and this time it was able to find the appropriate firmware. I was able to successfully root
Hey well i just installed latest magisk and patched boot img and moved it to my pc and went thru fast boot and just did fastboot flash boot patched.img and it works fine. I dunno if latest update fixed whatever was wrong on yours but if i installed the older one it would not even let me pick the boot img to patch *shrugs* but all working on mine now...we just need full device tree etc so we can get us a a recovery def want that before i go adding mods. If it helps any I have cricket same as ATT the person who lost cell may need to redo their apn or take sim card out and reapply it hope that works.
Moondroid said:
The one exception was Motorola Update Service. TiBu toasts that it was disabled and "invisible from the app drawer", but it actually wasn't disabled and still isn't. It still shows under System Applications.
Click to expand...
Click to collapse
I've been having the same problem trying to disable the update prompts. Titanium Backup doesn't work, nor can I disable it via terminal using pm. The system update screen will pop up multiple times a day, interrupting whatever I'm currently doing to tell me I have an update. It's really annoying that it can't be frozen.
Well after a few days of LTE connection my own unlock now works got root
riggin said:
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
Click to expand...
Click to collapse
hey was just wondering since im kinda in the same situation you were in with not being able to obtain exact firmware need at first for boost model if maybe you can proovide tthe brief steps you made to get the lmsa tool to recognize it and pull the corerct firmware....ty so much if u can
riggin said:
hey was just wondering since im kinda in the same situation you were in with not being able to obtain exact firmware need at first for boost model if maybe you can proovide tthe brief steps you made to get the lmsa tool to recognize it and pull the corerct firmware....ty so much if u can
Click to expand...
Click to collapse
Unfortunately, either LMSA determines the correct firmware or it doesn't, there isn't anything that can be done to fix it, except contacting Motorola.
For other options see
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Hey Guys, I'm continuing on this thread since I've gotten further. I used LMSA to download the firmware zip using the Resuce button. Afterwards I copy that zip (2+ gigs) to my download folder. I open up Magisk and select intall and select the firmware zip. I starts out successfully but then fails. I get this in the log folder.
- Device platform: arm64-v8a
- Installing: 23.0 (23000)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed
I even tried to resuce the phone using the firmware provided by the LMSA program which essentially wipes my phone and try again with a clean Magisk load and I'm getting the same. The only thing I'm thinking is I could be getting my Magisk from another source. I'm using version 23 from github.
steppinthrax said:
Hey Guys, I'm continuing on this thread since I've gotten further. I used LMSA to download the firmware zip using the Resuce button. Afterwards I copy that zip (2+ gigs) to my download folder. I open up Magisk and select intall and select the firmware zip. I starts out successfully but then fails. I get this in the log folder.
- Device platform: arm64-v8a
- Installing: 23.0 (23000)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed
I even tried to resuce the phone using the firmware provided by the LMSA program which essentially wipes my phone and try again with a clean Magisk load and I'm getting the same. The only thing I'm thinking is I could be getting my Magisk from another source. I'm using version 23 from github.
Click to expand...
Click to collapse
It isn't a zip file it's a folder or at least every firmware I have downloaded is automatically unzipped by LMSA.
You only need to copy the boot.img and maybe the recovery.img to the device.
sd_shadow said:
It isn't a zip file it's a folder or at least every firmware I have downloaded is automatically unzipped by LMSA.
You only need to copy the boot.img and maybe the recovery.img to the device.
Click to expand...
Click to collapse
Thanks I figured it out last night. I also figured out pretty quickly that once you root a phone certain applications will no longer function. I didn't deal with this before, but since I work from home I have to use some of those apps that create a "Work Profile". The one app "Intelligent Hub" removed itself and my work profile. When trying to re-install and authenticate with my work it literally said "Won't provision a compromised device".
Within Magsik I used the Magsik hide feature and tried selected that app and hiding all methods that it could detect root. I even then rebooted, removed/reinstall etc. Nothing worked. The app still kept detecting root. I know that the Xposed Framework modules may work in hiding root but I decided to go all the way back to normal since there's little benefit for me to root except for the ability for me to remove bloatware. This is a retail unlocked and there's little if any bloatware on the device.
I removed Magsik and any other junk, turned on OEM locking and rebooted and I'm back to mormal. Thank you everyone this was a leaning exp. I haven't rooted in like 5 years.
DM.IDOL said:
I've been having the same problem trying to disable the update prompts. Titanium Backup doesn't work, nor can I disable it via terminal using pm. The system update screen will pop up multiple times a day, interrupting whatever I'm currently doing to tell me I have an update. It's really annoying that it can't be frozen.
Click to expand...
Click to collapse
FYI, for posterity, instead of getting multiple notifs per day I just tap and let it try to update. It fails quickly and the notification is nixed for a while.