I was rooted on 9.5.4 with the Patched Boot Image. I had 2 modules enabled in magisk (call recording and substratum). Wanted to update to 9.5.5 and did this:
1. Download and install update
2. No reboot
3. Open Magisk and disable the modules
4. Select Install install and then Install to Inactive Slot (After OTA)
5. Rebooted
6. Phone booted so I opened magisk and enabled my modules
7. Rebooted
Now the phone doesn't boot up properly. It goes all the way to first screen asking for my passcode and then turns off and does to stock recovery. Please someone tell me what to do so I don't lose my data!!
Install TWRP, install stock image.
"Bring to life and not delete all" - Are you Thanos?
djsubterrain said:
"Bring to life and not delete all" - Are you Thanos?
Click to expand...
Click to collapse
If I was I would turn a lot of people to ash...
But as for my phone since I was offline the world for 3 hours and got no answers I decided to try to flash stock boot.img
After flashing it in fastboot phone booted up normally and I have everything. Now I'm on 9.5.5 and want to root the phone... Should I go with the TWRP method? I was thinking to delay to flash TWRP since it isn't stable yet. If I open Magisk in phone and select install and then again install and then select option "Select and patch a file" and select boot.img, will it work?
eltarod said:
If I was I would turn a lot of people to ass...
But as for my phone since I was offline the world for 3 hours and got no answers I decided to try to flash stock boot.img
After flashing it in fastboot phone booted up normally and I have everything. Now I'm on 9.5.5 and want to root the phone... Should I go with the TWRP method? I was thinking to delay to flash TWRP since it isn't stable yet. If I open Magisk in phone and select install and then again install and then select option "Select and patch a file" and select boot.img, will it work?
Click to expand...
Click to collapse
"I would turn a lot of people to ass..."
{
"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"
}
The TWRP version is stable enough for use just now. I would flash the rooted boot image (You will lose wifi if you're on 9.5.5) and then flash TWRP installer along with flashing magisk again, then download one of the kernels provided (I'm using ElementalX on 9.5.5 and it's working fine) and flash that in TWRP, then you should have TWRP, root and working wifi, etc.
djsubterrain said:
"I would turn a lot of people to ass..."
The TWRP version is stable enough for use just now. I would flash the rooted boot image (You will lose wifi if you're on 9.5.5) and then flash TWRP installer along with flashing magisk again, then download one of the kernels provided (I'm using ElementalX on 9.5.5 and it's working fine) and flash that in TWRP, then you should have TWRP, root and working wifi, etc.
Click to expand...
Click to collapse
When you say rooted boot.img...What do you mean? I took the stock boot.img, put in phone memory and selected in magisk. Magisk made a new boot.img and flashed that. After that phone didn't boot up like before and went to recovery mode. So to fix it I flashed again stock boot.img
I updated the same way as you (didn't disable my Magisk modules though). Everything went OK, kept root, but something borked in my /system folder and now can't make any changes in it (buildprop, hosts).
I'm not installing any unofficial TWRP, going to reflash the patched boot.img again to see if that works. If not, will go for a clean install. Worth a try?
eltarod said:
When you say rooted boot.img...What do you mean? I took the stock boot.img, put in phone memory and selected in magisk. Magisk made a new boot.img and flashed that. After that phone didn't boot up like before and went to recovery mode. So to fix it I flashed again stock boot.img
Click to expand...
Click to collapse
Rooted boot image : https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205
Follow that guide but, as I said, your rom is a later version so your wifi will break until you flash a compatible kernel, I'm using ElementalX with 9.5.5 and it's fine.
You would be best installing TWRP as soon as you can from here : https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 since you'll be best using this to flash ElementalX
I'm guessing you flashed an incremental ota and not the full system image in step one? Might be your issue.
Sent from my GM1917 using Tapatalk
Flash stock boot IMG and uninstall substratum overlay themes, u will always want to do that before u update, then reflash patched boot image, then u can reinstall your themes
---------- Post added at 01:17 AM ---------- Previous post was at 12:55 AM ----------
larsdennert said:
I'm guessing you flashed an incremental ota and not the full system image in step one? Might be your issue.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
No he said he was able to boot after the update, it was when he enabled his modules, more than likely its a substratum theme issue
Related
Here Is My Modified Safestrap App To work with Lollipop It is still the safestrap by hashcode for kitkat I just modified it so no kernel flashing is necessary
Change Log:
V17 -updated Safestrap Recovery To V5.01
Should load a little quicker
Added A Reboot To Recovery Button In The Safestrap App For Standalone Use
Features:
No More Flashing Kernels To Enter/Exit Safestrap This Process Is Now Automatic
New Themed And Layout Menu
{
"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"
}
Removed Non Working Functions And Rom Slots
SafeStrap Install Zips Will Now Fully Install Safestrap Without Having to Manually Do It With Safestrap Installer
Added New LP Recovery Control Center With Options To Reboot To Safestrap Recovery,Stock Recovery,Bootloader, Or Safe Mode
If You Are Using FlashFire You Now Have The Option To Use FlashFire From The LP Recovery Control Center
Instructions
If you already have safestrap or flashfire installed simply put the Lollipop Safestrap zip on sdcard and flash with either one
If you do not have safestrap or flashfire installed
1. Download this zip and place all 4 apks on your sdcard
2. Install each one
3. Now Open LP Recovery Control App
View attachment 3644238
4.You can now use flashfire to install the Lollipop Safestrap Zip Or You Can Manually Install Safestrap
5. To manually install Safestrap open the LP Recovery Control App
6. Click On Install SafeStrap (ITs The Very Top Option)
View attachment 3644239
7. It may take a bit for the SuperSu Prompt but please wait for it and grant access Then Accept Terms
8. Now click on Install/Update Recovery
View attachment 3644241
9. You will be taking back to the LP Recovery Control App main screen
10. Click On Install SafeStrap and make sure It Says State: Installed If it shows State: Uninstalled Reboot Phone and start from step 5
View attachment 3644243
11. Now you can click the back button to return to LP Recovery Control App
12. To reboot to Safestrap click on Recovery Reboot
13. If for some reason you get stuck on Samsung Screen or go into recovery bootloop.
14 Pull battery reboot to bootloader (Pwr+VolDwn+Home)
15. Plug phone into computer use odin to Flash BOK3 Kernel
16. When Phone reboots start from step 5
17. If you have a failed install or install a zip and it causes bootloop
18. Pull battery reboot to bootloader (Pwr+VolDwn+Home)
19. Plug phone into computer use odin to FlashNI2 Kernel
20. Watch for Safestrap Splash Screen and click to enter safestrap
21. In most cases this will work but if it does not then you may have to start all over and reroot your phone
Downloads
Lollipop_Safestrap_Reboot_Extended_PM_PB1.zip
Lollipop_Safestrap_Only_PB1.zip (For Manual Install)
NI2_stock_kernel.tar.md5 (To enter Safestrap From Bootloop)
Header_Partion_Fix_BOK3.tar.md5 (Use this If Stuck On Samsung Screen)
If you only want the Safestrap app as a stand alone without the Lollipop Control Center
It Has A Rebbot To Recovery Button In The App That Will Take You Straight To Safestrap Recovery
Just Install Like Normal APK
View attachment 3646865
Safestrap-KLTEVZW-5.01.apk
Make Sure These Apks Are Deleted
SafeStrapReboot
Safestrap
LollipopSafeStrap
FlashFire (You Can redownload from play store if you want it)
Thanks
@Hashcode For Safestrap
@klabit87 For Verizon NI2 Flasher
@carl1961 for creating Stock_KERNEL_SafeStrap-Flashable.zip
@benwaffle For Original NI2 Flasher
@Chainfire For Flashfire and SuperSU
saved
It works flawlessly, as always!
Thanks for these!!
@jrkruse think you might be interested in this for the s4. the dev has source on his github.
http://forum.xda-developers.com/showthread.php?t=3311285
Updated twrp3 base
klabit87 said:
@jrkruse think you might be interested in this for the s4. the dev has source on his github.
http://forum.xda-developers.com/showthread.php?t=3311285
Updated twrp3 base
Click to expand...
Click to collapse
I cant get the screen frame rate buffer patches to work
jrkruse said:
I cant get the screen frame rate buffer patches to work
Click to expand...
Click to collapse
Oh ok. Didn't know if you knew about it or not so thought I would bring it up.
Great work though. One guy is gonna do the same thing you have done on our s4
klabit87 said:
Oh ok. Didn't know if you knew about it or not so thought I would bring it up.
Great work though. One guy is gonna do the same thing you have done on our s4
Click to expand...
Click to collapse
Have them PM and I will tell them the process
jrkruse said:
Have them PM and I will tell them the process
Click to expand...
Click to collapse
Ok thanks!
Could we potentially get an update log going in this thread? I find it would be very interesting and useful to know about updates
klabit87 said:
@jrkruse think you might be interested in this for the s4. the dev has source on his github.
http://forum.xda-developers.com/showthread.php?t=3311285
Updated twrp3 base
Click to expand...
Click to collapse
I've been working with mohammad.afaneh over the past few days to get a working updated SS with TWRP 3.0.0-0.
Dudash said:
I've been working with mohammad.afaneh over the past few days to get a working updated SS with TWRP 3.0.0-0.
Click to expand...
Click to collapse
I have been in touch with him also
you are amazing.
wow, that was easy!
jrkuse what would we do without you !?
didn't realize changing the rom didn't affect the apps already installed?
what's the best rom to run? so many to choose from!
I updated with the zip and had to flash the bok3 kernel to get it to reboot.
I was lucky after waiting for the "reboot", the screen went blank for several minutes at this time I pressed the power button and was brought back to ss splash screen which is how I got back to recovery to flash kernel. Not sure what happen. I think it flashed OE1 ss kernel, before I tried the bok3.
Rob684 said:
I updated with the zip and had to flash the bok3 kernel to get it to reboot.
I was lucky after waiting for the "reboot", the screen went blank for several minutes at this time I pressed the power button and was brought back to ss splash screen which is how I got back to recovery to flash kernel. Not sure what happen. I think it flashed OE1 ss kernel, before I tried the bok3.
Click to expand...
Click to collapse
When you flash it for the first time in recovery you still have to flash the kernel to boot back to rom then once you do that it will work. If it doesnt work you need to open install safestrap and manually install it
Thinking about flashing this but had a question. Is there a way to flash a different kernel than the bok3 kernel since it automatically flashes this kernel upon exiting safestrap? That's the only thing holding me back right now. Thanks for this.
capone202 said:
Thinking about flashing this but had a question. Is there a way to flash a different kernel than the bok3 kernel since it automatically flashes this kernel upon exiting safestrap? That's the only thing holding me back right now. Thanks for this.
Click to expand...
Click to collapse
Why you should be running bok3 firmware for everything
Easy peasy.
Thank you for this. Nearly 24 months since this phone's release, and we still have development. Not bad for a "locked down" device.
jrkruse said:
Why you should be running bok3 firmware for everything
Click to expand...
Click to collapse
Its not a big deal, MOAR doesn't seem to be the best with BOK and I was considering going back to BOG5, but I'll probably stick with it and flash this. Thanks for the reply.
Hey Xda,
I have an S7 International G930f and the stock boot image wont flash in odin without bootloop, after frp unlock. So basically ive flashed the G930F(ENGroot) file, but the second part, flashing the boot img isnt flashing without bootloop.
So yeah- my phone is acting weird, im surprised it even works.
Running Stock Rooted 6.0.1 with TWRP
I've rooted/recoveried many a Samsung, but all this Dmverity, FRP unlock, these newer protocols have me confused.
I've got OEM unlock ON which is still a tad new to me-coming from S5. Unknown Sources Enabled. FRP Lock shows as OFF.
I've followed an FRP unlock guide-XDA here but the boot image wont take. Tried many times. Maybe its my July 1st Security patch?
Can someone tell me what i need to do to get this phone to where it is FRP unlocked, dmverity gone,keep root/recovery and update it?
p.s. I'm getting tons of bugs, random reboots, and WiFi passwords aren't saved on reboot. Plz help!
Thank you!
{
"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"
}
Read the main post in the TWRP thread in the development forums, all instructions in there
*Detection* said:
Read the main post in the TWRP thread in the development forums, all instructions in there
Click to expand...
Click to collapse
Thanks for the reply. If you are referring to this thread http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770 thats what i followed.
But i did have some confusion about this section below from said thread. Im not sure what OP means by "if you only want a bootable system partition". Of course i would like this to be bootable, AND i would like to install SuperSU.
Its worded strange. Ok lets assume i did this incorrectly. Would you suggest i start over, factory wipe, then move forward with that threads directions?
If twrp and super su are already installed and working, but i dont have the right boot.img flashed, should i start all over or start somewhere in particular?
10. If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
You will need an external SDcard for this method, if you don't have one you will have to use adb sideload to install SuperSU.
If you only want a bootable system partition:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Note: This does not disable the forced encryption on Bxxx firmware, only Axxx firmware due to a change in vold by Samsung.
Click to expand...
Click to collapse
dovedescent7 said:
Thanks for the reply. If you are referring to this thread http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770 thats what i followed.
But i did have some confusion about this section below from said thread. Im not sure what OP means by "if you only want a bootable system partition". Of course i would like this to be bootable, AND i would like to install SuperSU.
Its worded strange. Ok lets assume i did this incorrectly. Would you suggest i start over, factory wipe, then move forward with that threads directions?
If twrp and super su are already installed and working, but i dont have the right boot.img flashed, should i start all over or start somewhere in particular?
Click to expand...
Click to collapse
"if you only want a bootable system partition" means if you don't want to flash SuperSU, but want your phone to boot correctly with TWRP installed, if you don't follow that step, regardless of SuperSU, your phone is a soft brick
Flash TWRP
Wipe Data (Yep, to disable encryption, so backup first)
Flash DM-Verity~zip
Flash Super-SU.zip
Reboot
More in depth here
http://www.droidorigin.com/root-samsung-galaxy-s7/
*Detection* said:
"if you only want a bootable system partition" means if you don't want to flash SuperSU, but want your phone to boot correctly with TWRP installed, if you don't follow that step, regardless of SuperSU, your phone is a soft brick
Flash TWRP
Wipe Data (Yep, to disable encryption, so backup first)
Flash DM-Verity~zip
Flash Super-SU.zip
Reboot
More in depth here
http://www.droidorigin.com/root-samsung-galaxy-s7/
Click to expand...
Click to collapse
hey man i do appreciate it. Thank you for confiriming,the above link worked! thank you!!!!!!!!
dovedescent7 said:
hey man i do appreciate it. Thank you for confiriming,the above link worked! thank you!!!!!!!!
Click to expand...
Click to collapse
:good:
Hey guys! I haven't been in the rooting community for a while and when I was my phone was end of life. How can I accept an OTA while being rooted?
I assume I will have to unroot through SuperSU, update like normal, then re-root with the latest SuperSU. Is that correct? I saw some using FlashFire, but I am kind of uneasy about an automated app rooting my device.
Some additional info:
Phone on Feb security update
Phone rooted with latest SuperSU
I did not install custom recovery, only booted it to flash SuperSU
I don't want to lose any data on my phone
Thanks in advance guys! Hopefully with your help I can get this bad boy updated!
Bump?
No one can help me?
Google android factory OTA. That will get you to Google's full ota which you will need to sideload with adb. Full instructions are on the page with the download. And probably a dozen how to's posted here in the last couple of days.
What I did i downloaded from herehttps://developers.google.com/android/images#sailfish unzipped the file edited the batch took the -w out saved the file and ran the Bach file re installed twrp and root should not loose anything but its a possibility this link will you better directions its what I used https://forum.xda-developers.com/showpost.php?p=71321307&postcount=31
It's a bit more involved, but I always download the latest factory image, edit the batch file to remove the "-w" which doesn't wipe it. Then I boot back into TWRP and install the TWRP zip (not necessary if you don't want to keep it), then install SuperSU zip.
Here's the easiest method in my opinion (No PC required). This method requires TWRP recovery.
With TWRP already installed, download the next "Sailfish" OTA from here - https://developers.google.com/android/ota. Notice I said "next", not latest. If you're several OTA's behind you'll want to download all of the updates to bring you current. For example, I started yesterday on NMF26V and these are all of the files I downloaded.
{
"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"
}
You'll also need the latest TWRP, SuperSu, and any mods you plan to install. Now we're ready to start.
Boot to TWRP and install the "Next" OTA file. No need to do any wipes, just simply flash it. When it completes, immediately flash TWRP installer, then reboot.
Now reboot back to TWRP, flash the next OTA, immediately flash TWRP again, and reboot. Continue this until you're on the latest update.
Now simply boot back to TWRP and flash SuperSu. I also installed Elemental (after an additional reboot for good measure) as I like the swipe to sleep function.
Sent from my Pixel using Tapatalk
What's the reasoning behind having to do each OTA in order?
joshw0000 said:
Here's the easiest method in my opinion (No PC required). This method requires TWRP recovery.
With TWRP already installed, download the next "Sailfish" OTA from here - https://developers.google.com/android/ota. Notice I said "next", not latest. If you're several OTA's behind you'll want to download all of the updates to bring you current. For example, I started yesterday on NMF26V and these are all of the files I downloaded.
You'll also need the latest TWRP, SuperSu, and any mods you plan to install. Now we're ready to start.
Boot to TWRP and install the "Next" OTA file. No need to do any wipes, just simply flash it. When it completes, immediately flash TWRP installer, then reboot.
Now reboot back to TWRP, flash the next OTA, immediately flash TWRP again, and reboot. Continue this until you're on the latest update.
Now simply boot back to TWRP and flash SuperSu. I also installed Elemental (after an additional reboot for good measure) as I like the swipe to sleep function.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
dejanspa said:
What's the reasoning behind having to do each OTA in order?
Click to expand...
Click to collapse
You're welcome to try going straight to the latest OTA but it's my understanding that each one only contains the updates from that specific release. If it fails you could always modify the flashall.bat file of a full restore image and flash it with your computer. Then boot TWRP with fastboot, flash TWRP from the booted TWRP, and install SuperSu.
Sent from my Pixel using Tapatalk
Okay. Also in this method you don't have to modify any file to get rid of the "-w" so it won't wipe data? If I do what you did all my files and apps should still be there when I reach the last OTA.
Sorry iphone convert so i'm new to this.
joshw0000 said:
You're welcome to try going straight to the latest OTA but it's my understanding that each one only contains the updates from that specific release. If it fails you could always modify the flashall.bat file of a full restore image and flash it with your computer. Then boot TWRP with fastboot, flash TWRP from the booted TWRP, and install SuperSu.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
dejanspa said:
Okay. Also in this method you don't have to modify any file to get rid of the "-w" so it won't wipe data? If I do what you did all my files and apps should still be there when I reach the last OTA.
Sorry iphone convert so i'm new to this.
Click to expand...
Click to collapse
Nope. Nothing to modify as long as you download the OTA files from the link I posted and not the full image files from a different section. The image files are the ones that have the flashall.bat file that have to be modified before flashing. There's nothing to modify in the OTA's. That's another reason I like my method as I have 78GB or pics/videos/music that I'd hate to lose.
Sent from my Pixel using Tapatalk
joshw0000 said:
Here's the easiest method in my opinion (No PC required). This method requires TWRP recovery.
With TWRP already installed, download the next "Sailfish" OTA from here - https://developers.google.com/android/ota. Notice I said "next", not latest. If you're several OTA's behind you'll want to download all of the updates to bring you current. For example, I started yesterday on NMF26V and these are all of the files I downloaded.
You'll also need the latest TWRP, SuperSu, and any mods you plan to install. Now we're ready to start.
Boot to TWRP and install the "Next" OTA file. No need to do any wipes, just simply flash it. When it completes, immediately flash TWRP installer, then reboot.
Now reboot back to TWRP, flash the next OTA, immediately flash TWRP again, and reboot. Continue this until you're on the latest update.
Now simply boot back to TWRP and flash SuperSu. I also installed Elemental (after an additional reboot for good measure) as I like the swipe to sleep function.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Thanks, this was new for me :highfive: I always used to flash the system, boot etc, but this was a lot easier :good::victory:
Juhler said:
Thanks, this was new for me :highfive: I always used to flash the system, boot etc, but this was a lot easier :good::victory:
Click to expand...
Click to collapse
Glad I could help.
Sent from my Pixel using Tapatalk
For the April OTA update I was able to install the file that came to the phone using FlashFire. Trying to uninstall SuperSU and then take the OTA on the phone hadn't worked the previous two times I had tried it. When I tried the March OTA update on the phone with FlashFire it also didn't work, so I'm not clear if the latest FlashFire update was why the April OTA on the phone worked without issue. I thought maybe I needed to use the restore option in FlashFire to get it to work, but on the April OTA it turned out that I didn't need to use any of FlashFire's restore options like I had been planning on trying. For the April OTA to the phone, using FlashFire ended up being quicker and simpler than the previous manual process I had been doing to install the files Google posts online and then root the phone again. Since I'm using SuperSU to root the phone, I'll keep using FlashFire to update if it keeps working like it did this month.
Yeah OTA updates are patches not full OS files so must be done in order.
Using flashall with -w removed is the cleanest method as it rewrites all system files.
Personally I'm not a fan of patching the OS.
{
"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"
}
Tested Working on A750F, A750FN, A750G and A750GN - 22/03/20
This Guide is outdated now..
It "ONLY" works on the initial One UI 2 update that started rolling out in March 2020
It has issues on the june patch. So "DO NOT" report bugs if you are on the june patch.
Use this at your own risk. I am not responsible for any damage that may happen to your device.
Make sure to have the official firmware downloaded for your device in case anything goes wrong.
This will void your warranty
This will also trip the knox counter.
Installation Guide
1. Unlock The bootloader
2. Boot into download mode
3. Using Odin, Flash Magisk_patched_boot.tar in the "AP" Slot.
4. Reboot download and flash Twrp recovery using odin in AP slot.
5. Reboot to TWRP and "FORMAT" , not wipe the data.
6. Flash Magisk-v20.3.zip
7. Reboot to download and flash Officialrecovery.tar in "AP" slot.
8. Reboot your device.
DOWNLOADS
Magisk Boot Img - http://www.mediafire.com/file/m9dwiww6i492xl6/Magisk_patched_boot.tar/file
Official recovery - http://www.mediafire.com/file/nhrj8060rbv43rm/Officialrecovery.tar/file
Notes:
1. Only Magisk v20.3 is tested, other versions may/may not work. Report if other versionswork, I will update OP.
2.This "WILL NOT" install Twrp on your device as Twrp is not updated and it will cause bootloops.
3. Failing to follow and steps mentioned above, you will end up in a bootloop.
Please DO NOT Share direct link to these files, Share The link to this post.
Feedback is Highly appreciated
Hit the Thanks Button
Credits:
Me for finding this method
@ashyx for Building Twrp
And Teamwin
Download link ??
Kumarranveer_RK said:
Download link ??
Click to expand...
Click to collapse
I just realized that xda did not upload the files due to size limit, I have updated OP.. Check it
These files work on the A750G/DS. Or they're just for the F version
JHAM2005 said:
These files work on the A750G/DS. Or they're just for the F version
Click to expand...
Click to collapse
They are confirmed working on A750F and A750GN, if possible, try and report for A750G
Thanks bro .. rooted my a7 2018 (Android Q) .. No issues Till now
well i did flash magisk patched boot, and succesfully flashed TWRP,
but i get this weird problem in twrp part, where my internal storage shows 0 MB in twrp.
and rebooting it, device goes into download mode all by itself.
what should i do now? wipe the internal storage or format it by Writing yes.?
nanodroid.cyberbot said:
well i did flash magisk patched boot, and succesfully flashed TWRP,
but i get this weird problem in twrp part, where my internal storage shows 0 MB in twrp.
and rebooting it, device goes into download mode all by itself.
what should i do now? wipe the internal storage or format it by Writing yes.?
Click to expand...
Click to collapse
Its mentioned in the op please read it carefully format it by typing yes. And install magisk zip from sd card
Can we use the TWRP 3.2.3-1 listed here: https://forum.xda-developers.com/galaxy-a7/development/recovery-twrp-3-2-3-1-galaxy-a7-2018-t3876798
You did not give a link to which TWRP version you used. So just asking.
sameermanas said:
Can we use the TWRP 3.2.3-1 listed here: https://forum.xda-developers.com/galaxy-a7/development/recovery-twrp-3-2-3-1-galaxy-a7-2018-t3876798
You did not give a link to which TWRP version you used. So just asking.
Click to expand...
Click to collapse
No other twrp is available for our device.. So, yes this one
thanks! work like a charm
I downloaded the Indian version and installed it on an a750 FN and it works ....
I will keep trying more things
good job
Delete
The Root works perfectly on the A750G/DS, the only thing that does not work properly is the TWRP, does not recognize the internal memory, only recognizes the SD card
PD... An Official Recovery query is only for version F and GN or also works in G/DS versions
how could I return my battery at the original state? Im having fast drain ..
Hi! I have followed the steps correctly and rooted my Samsung Galaxy A7 2018. However, whenI restart my device, it always got stuck on download mode. Any help I can get?
Equinoxx17 said:
Hi! I have followed the steps correctly and rooted my Samsung Galaxy A7 2018. However, whenI restart my device, it always got stuck on download mode. Any help I can get?
Click to expand...
Click to collapse
This happens when you don't flash magisk zip file, did u flash that after installing twrp? And after that did u install stock recovery? Try this, if it does not work, start from scratch again.
KChoudhry said:
This happens when you don't flash magisk zip file, did u flash that after installing twrp? And after that did u install stock recovery? Try this, if it does not work, start from scratch again.
Click to expand...
Click to collapse
I did flash magisk after installing TWRP. I also installed the stock recovery. But still, it goes back to download mode when I restart my phone.
Equinoxx17 said:
I did flash magisk after installing TWRP. I also installed the stock recovery. But still, it goes back to download mode when I restart my phone.
Click to expand...
Click to collapse
You need to start from scratch then
KChoudhry said:
You need to start from scratch then
Click to expand...
Click to collapse
I guess I'll be staying at Android Pie for now. I think I'll be waiting for other alternatives that doesn't boot into download mode when restarted. Somehow, I thank you for sharing info on how to root Samsung Galaxy A7 2018.
Stable just landed and is nice. Testing battery optimization differences in stable and ob2 that I came from. Great it's here
mattie_49 said:
Stable just landed and is nice. Testing battery optimization differences in stable and ob2 that I came from. Great it's here
Click to expand...
Click to collapse
Do you have boot.img? i don't have good internet for download full ota and extract it :/
franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
Do you have full ota link?
franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
franko_m19 said:
Do you have boot.img? i don't have good internet for download full ota and extract it :/
Click to expand...
Click to collapse
https://drive.google.com/file/d/11bXba50WUUlrgRRyoGCVYqZZXdmvsfiW/view?usp=drivesdk.
I've already patched this. Fastboot flash this then go into magisk let it reboot if it asks to continue setup. Rooted an A13 stock
mattie_49 said:
https://drive.google.com/file/d/11bXba50WUUlrgRRyoGCVYqZZXdmvsfiW/view?usp=drivesdk.
I've already patched this. Fastboot boot this then go into magisk and direct install to backup stock for you.
Click to expand...
Click to collapse
Thx @mattie_49 it's working in LE2115. I started to download and time estimate was 3 hours xd
@mattie_49 : How do you download it? Or where did you got it? With oxygen updater I get 11_C.66
AxelM said:
@mattie_49 : How do you download it? Or where did you got it? With oxygen updater I get 11_C.66
Click to expand...
Click to collapse
Oxygen updater
mh, I only receive 11_C.66 maybe I have to wait
after installing c.66 i received it. @mattie_49 Do you root it like common (patch boot.img via magisk and install it) or are more changes necessary?
franko_m19 said:
Thx @mattie_49 it's working in LE2115. I started to download and time estimate was 3 hours xd
Click to expand...
Click to collapse
{
"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"
}
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.
fhedeitx said:
View attachment 5757793
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.
Click to expand...
Click to collapse
It's the official 16 patched. Just fastboot flash it or ask guy above . He got working with it.
AxelM said:
after installing c.66 i received it. @mattie_49 Do you root it like common (patch boot.img via magisk and install it) or are more changes necessary?
Click to expand...
Click to collapse
No sir I carried it over with magisk from 11 originally. MSM,unlock bl. Patch boot . Then disable modules and carry from A11 to A12 then so on.
fhedeitx said:
View attachment 5757793
When I try to boot your patched .img, my phone goes to "Fastboot Mode |1+|" screen and hangs there. Doesn't make a difference what slot I'm in.
Click to expand...
Click to collapse
fastboot flash boot *boot_name*.img
franko_m19 said:
fastboot flash boot *boot_name*.img
Click to expand...
Click to collapse
I wanted to try booting it before flashing. I tried flashing and same thing happened. Now I'm back at MSMTool
_MartyMan_ said:
Do you have full ota link?
Click to expand...
Click to collapse
No but flash one of the open betas. That's how I received so fast. Was on ob2 and it's getting it first.
fhedeitx said:
I wanted to try booting it before flashing. I tried flashing and same thing happened. Now I'm back at MSMTool
Click to expand...
Click to collapse
I don't had any problem with the img, I upgraded with magisk installed. And now it's working with root.
Do you have Global? Or NA?
franko_m19 said:
I don't had any problem with the img, I upgraded with magisk installed. And now it's working with root.
Do you have Global? Or NA?
Click to expand...
Click to collapse
Global (I believe) LE2115 in US
mattie_49 said:
Oxygen updater
Click to expand...
Click to collapse
I was on open beta 2 is why I received very first. That's the order they put rollout in. To ob 1& 2 before stock devices.
Install in inactive slot (after ota) in magisk is working for upgrading from android 12 to 13 (using oxygen updater zip file) ?Edit: this doesn't work because the device reboots when the installation starts.
Remove magisk boot image from magisk app, update and turn off the device...boot to fastboot and do a fastboot boot magisk_patched.img (you have to extract the boot image with payload dumper and patch it before or after the installation with magisk. Then do a direct install from magisk (on the temp root boot image).
On android 13 you will have this warning on every reboot: Orange state, Your device has been uplocked and can't be trusted.
Thanks for this! I have not had root on my Oneplus 9 for a while and it was driving my _crazy_. Had to do fastboot flash boot boot.img instead of fastboot boot boot.img to get magisk to work properly.
I had to jump through some extraordinary hoops to get it done including breaking out an old Win10 laptop since I could never get my new Win11 laptop to recognize my phone in fastboot, despite hours of work trying to install the drivers to no success.