Related
I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?
DaGoo_Balls said:
I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?
Click to expand...
Click to collapse
It apparently is.
https://forum.xda-developers.com/r1-hd/development/unofficial-lineageos-14-1-t3689435/post75020813
Thanks. Looks like I have plans for NYE
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
You would be better off to patch my boot image and fastboot boot it.
Then backup your boot image, patch it with magisk, and flash that one back to the device.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/blur2-boot.img"
This keeps things clean, just incase you are using a boot image that is different from your own device. Plus you have a "stock" boot image backup if you ever need it.
Not a bad idea to grab recovery also.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/blur2-recovery.img"
Sent from my ford using XDA Labs
BLU R2 LTE files. Link
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!
bobsmithy said:
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!
Click to expand...
Click to collapse
The size of memory "shouldn't" matter.
Braunish said:
Hi there, am trying to root this phone also. Stumbled upon your thread and had a question. If I take the 3 image files (recovery, boot, system) that are included at mediafire site (that you included in your post) and replace the same 3 image files in stock rom, would that work to root the phone? Thank you for any help, I've tried kingoroot, kingroot, and framaroot to no avail.
Click to expand...
Click to collapse
Read back few post on this thread. They discuss successful root method.
Basically unlock bootloader and use majisk manager to patch boot.img and flash patched image with fastboot.
Root R2 Plus w/ BLU R0190WW V7.0.04.01 GENERIC 11-02-2018
DaGoo_Balls said:
Thanks. Looks like I have plans for NYE
Click to expand...
Click to collapse
Hi there, I recently got a Blu R2 Plus and am aiming to root. I used the boot-sign.img that came with that ROM version in title (9447 KB) when patching with Majisk Manager and came up with a patched file of 9.57 MB size. Is there a way to test this ROM, or can you verify that is the same sizes you dealt with when you went through this process. Thank you for any information. It took me a while and a factory reset before I could get majisk manager installed to patch the correct boot-sign.img file.
Hi There copy img file to where on phone
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
Braunish said:
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
Click to expand...
Click to collapse
If I understand correctly.
You have adb and fastboot installed.
You have a boot image that works for your device and tested it by using fastboot to boot it. let's call it working_boot.img
You have MagiskManager installed.
The next steps:
adb push working_boot.img /sdcard Doesn't really matter where you put it.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on working_boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
adb pull /sdcard/magiskmanager/patched_boot.img
Reboot to bootloader and fastboot boot patched_boot.img
Open MagiskManager. You should see that Magisk is installed and active.
Now that you have temporary root, you have some options.
The easiest way would be to open MagiskManager and use the Direct install option. This will pull, patch and install a patched boot.img to the device.
Unless the the original working_boot.img used is the correct one for your device.
The safer way, pull the stock_boot.img I normally grab recovery also from the device.
For BLU R2 LTE
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/BLUR2-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/BLUR2-recovery.img"
adb pull /sdcard/BLUR2-boot.img
adb pull /sdcard/BLUR2-recovery.img
Then patch it and fastboot boot it to make sure it works.
After that you can either use MagiskManager Direct install or fastboot to flash the new patched_boot.img.
Bricked my device, used SP Flash Tool to update - Now no OTA?
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx
Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.
8milerd said:
Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.
Click to expand...
Click to collapse
These links do not work? Link Direct download links are from MediaFire. Click on the name of the file.
I try to use direct download links from MediaFire. There servers can normally handle it. You do not have to navigate ads and redirects with direct download links.
---------- Post added at 04:58 AM ---------- Previous post was at 04:35 AM ----------
HornyOryx said:
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx
Click to expand...
Click to collapse
A while back , I had to do a factory reset to get an OTA. Then I had to un-root it to get the OTA to flash.
Hi, I recently flashed the latest TWRP for S10 (twrp-3.5.2_9-3-beyond1lte.img) using Odin.
In the Odin app, everything appears to be successful, however, the phone now shows the warning for the bootloader being unlocked and immediately switches to a Download Mode screen. At the top left of the screen it shows this:
ODIN MODE (AVB Fail)
recovery: Error validating footer. (0)
recovery: Error verifying vbmeta image: invalid vbmeta header (6)
VBMETA 6973FXXSBFUF3, 41014081R
No matter how many times I turn the phone off and on, it constantly keeps going back to this screen. The only way I can fix this is by flashing the stock firmware onto the phone with Odin. IfI try to flash TWRP again after this, it just repeats the previous problem. TWRP was working yesterday when I was using it, sol am really confused
as to why this issue is occurring.
This issue seems to have started after I flashed Lineage 18.1 onto my phone through TWRP. Lineage was constantly launching so I turned the phone off and went back onto TWRP and deleted my data, OS and internal storage. I don't know how this would affect anything though, but I can't access TWRP since.
If anyone would have any idea how to resolve this problem and allow me to access TWRP on my phone again, it would be greatly
appreciated. Thank you
(My phone model number is SM-G973F/DS).
Did you ever manage to get this solved?
I'm having the same issue with my S10e.
After flashing TWRP it goes into download mode and whatever I try it always boots into download mode until I flash the stock rom and start over again.
My phone is Samsung Galaxy S10 (SM-G973F).
I have never used Lineage, but I read that Lineage has problems with TWRP.
I root Stock ROM with Magisk. With Magisk I patched AP file, and install BL, CP, CSC and patched AP with ODIN.
After that I install TWRP and vbmeta.
TWRP.img I patched with Magisk. Version of Magisk is 25.1. After I patched .img with Magisk, I copy it on PC with ADB. After copy on PC, I convert patched .img to .tar and it install with ODIN.
First of all, transfer the patched TWRP image (magisk_patched.img) file from your phone’s storage to the PC.
Open the folder where the file was transferred.
Hold the SHIFT key on the keyboard and right-click on any empty space inside the folder.
Then select the ‘Open PowerShell window here’ option.
Now, enter the following command to rename the ‘magisk_patched.img’ to ‘recovery.img’:
mv magisk_patched.img recovery.img
Instead of magisk_patched.img, type the name you got when you patched the .img with Magisk and then Enter.
For me it looks like this:
Next command for Galaxy S10 is: tar cf twrp-beyond1lte.img.tar recovery.img
Now you can install TWRP with ODIN.
I installed TWRP.tar and vbmet.tar with ODIN.
Thanks!
I will give it a try.
Where did you get the vbmeta file?
Or did you have create it yourself? - That's one part I'm unsure of.
Cilvaring said:
Thanks!
I will give it a try.
Where did you get the vbmeta file?
Or did you have create it yourself? - That's one part I'm unsure of.
Click to expand...
Click to collapse
Before root Android.
From here:
[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy S10/e/+/5G Exynos
Official TWRP 3.6.1-* For Galaxy S10/e/+/5G Only for exynos variants - G970F / G973F / G975F / G977B (Europe - Global, Single/Dual-SIM), G970N / G973N / G975N / G977N (South Korea) Disclaimer I am not responsible for bricked devices, dead SD...
forum.xda-developers.com
Here you can download TWRP, vbmeta and multidisabler samsung.
For vbmeta and multidisabler samsung you need click on Instructions: Odin (Windows) CLICK TO SHOW CONTENT. Here are links for download.
Boot into TWRP, Flash Multi-Disabler zip, and Format the Data
Press Power and Volume Down buttons together to exit Download Mode.
As soon as the screen turns off, quickly press and hold the Power, Volume Up, and Bixby buttons together until the Bootloader Warning message appears.
Once the Bootloader Warning screen appears, release the Bixby and Power buttons, and keep holding the Volume Up button to enter TWRP recovery mode.
Tap on the ‘Install’ button in TWRP.
Navigate to the MicroSD card and select the Multi-Disabler ZIP file.
Swipe the button on the screen to flash the Multi-Disabler zip file on your Galaxy S10.
Once the file has been flashed successfully, go to ‘Wipe’ > ‘Format Data’ in TWRP.
Enter ‘Yes’ in the field to format the data partition/factory reset the device.
Finally, go to the ‘Reboot’ menu in TWRP and select ‘Recovery’ to boot your Samsung Galaxy S10 device into rooted OS with.
this method of patching is good, thanks for sharing!
ZmisiS said:
My phone is Samsung Galaxy S10 (SM-G973F).
I have never used Lineage, but I read that Lineage has problems with TWRP.
I root Stock ROM with Magisk. With Magisk I patched AP file, and install BL, CP, CSC and patched AP with ODIN.
After that I install TWRP and vbmeta.
TWRP.img I patched with Magisk. Version of Magisk is 25.1. After I patched .img with Magisk, I copy it on PC with ADB. After copy on PC, I convert patched .img to .tar and it install with ODIN.
First of all, transfer the patched TWRP image (magisk_patched.img) file from your phone’s storage to the PC.
Open the folder where the file was transferred.
Hold the SHIFT key on the keyboard and right-click on any empty space inside the folder.
Then select the ‘Open PowerShell window here’ option.
Now, enter the following command to rename the ‘magisk_patched.img’ to ‘recovery.img’:
mv magisk_patched.img recovery.img
Instead of magisk_patched.img, type the name you got when you patched the .img with Magisk and then Enter.
For me it looks like this:
Next command for Galaxy S10 is: tar cf twrp-beyond1lte.img.tar recovery.img
Now you can install TWRP with ODIN.
I installed TWRP.tar and vbmet.tar with ODIN.
Click to expand...
Click to collapse
Foxlegendary said:
this method of patching is good, thanks for sharing!
Click to expand...
Click to collapse
You are welcome.
/*** BEGIN DISCLAIMER ***/
If you follow this procedure and lose every bit of content on your device / end up with a fancy paperweight, I, nor anyone involved with the referenced open source or otherwise licensed projects is responsible. It's all on you, and this will void your warranty. Do not proceed if you don't understand something. Chances are you will have a bad time.
/*** END DISCLAIMER ***/
Hey everyone - my Samsung Galaxy Tab A 10.1" (2019) - SM-T515 - recently applied a security update without my consent (The Samsung Android 11R September 8th 2021 Security update - side note, make sure that you turn off Samsung's push service ), which canned my previous root access. I use server software and internal port forwarding to do... Things on my device, so I needed my root access back.
Here's how I retrieved it, and how I put TWRP in place as my recovery partition in the process.
The Tools
Make sure you have these before you start. Because this is a Samsung device, you'll have to do some things under Windows, like using Frija and Odin (unfortunately).
1.) Frija - Available here - https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/
2.) The latest SM-T515 / SM-T510 firmware from Samsung for your device's CSC (if you use the firmware for the wrong CSC code the most common problem that I have seen as a result is typically incorrect partition sizes after flashing, which can be corrected with TWRP). Frija is listed first, because you'll use Frija to get this directly from Samsung.
3.) Some kind of generic tool that you're comfortable with for working with archives. Ideally whatever tool you choose should be able to work with .tar, .gz, and .zip archives for this process. Personally I like 7-Zip on *Nix and Windows, and ZArchiver on Android.
4.) Odin (firmware flash tool by Samsung) - attached.
5.) The latest Samsung device USB drivers for your environment (they're fine as long as they enable both ADB and MTP correctly) - available here https://developer.samsung.com/mobile/android-usb-driver.html
6.) The latest TWRP image for Samsung SM-T5xx devices - available here https://androidfilehost.com/?fid=14943124697586374577 (and attached)
7.) ADB - downloading / installing and using adb are outside the scope of this post. It is available here - https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
8.) The latest Magisk APK file - available here https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
The Process
0.) Back up your stuff, and remove your SD card if it makes you more comfortable - do whatever you need to do to be comfortable with "I might lose EVERYTHING on this device." If you plan on following this procedure, you should know how to do this, and I'm not going to try to explain it. If you can't get past this part, you should stop while you're ahead and still have a device that boots.
1.) Unlock your bootloader.
2.) Download the most recent firmware package for your device using Frija and extract all of the individual .md5 files which it contains.
2.) Use Odin to flash the most recent firmware to your device, and factory reset / wipe / format partitions and caches until you have a clean device that boots correctly. If your partitions aren't sized properly at this point it isn't something to be too concerned with, as you can correct them later using TWRP.
3.) Turn developer options back on, enable USB debugging, set the default USB configuration to "File Transfer", connect your device to your PC and copy the Magisk APK over to the internal storage of your device.
4.) Remove .md5 from the filename of the AP file that was included in your firmware package from Samsung and extract its contents into its own directory.
5.) Extract the contents of the latest TWRP package for these devices into the same directory where you extracted the individual partition image files contained in the AP file. Overwrite contents in the destination directory as necessary. The TWRP package should contain three files - param.bin.lz4, recovery.img.lz4, and vbmeta.img.lz4 - If there are uncompressed images (.img files) that correspond to the LZ4 compressed images from the TWRP package in the AP file of your firmware package, remove them first. Odin will (understandably) freak out if you try to flash two different images to the same partition in the same flash operation.
6.) Compress the contents of your modified AP directory which now contains the TWRP package's contents into a tar ball on your PC, and then copy it somewhere that Magisk will be able to access it on the Internal storage of your device (the Downloads directory - "/storage/emulated/0/Downloads/" is a good choice).
7.) Copy the latest Magisk APK to your device (again, the Downloads directory is a good choice), and then install it on your device.
8.) Launch Magisk on your device and choose "Install". Be sure to uncheck the "Recovery Mode" option. We don't want to use "Recovery mode" for Magisk's patching process. Even though this is a Samsung device and this would normally be how to proceed, in this case we're using our own custom TWRP recovery partition, and we don't want Magisk to mess with it. So make sure you aren't patching the bootloader or recovery images in unnecessary ways with Magisk.
9.) In Magisk on your device, choose "Select and patch a file" and then choose the AP file that you created and copied to the device which now contains TWRP as its recovery partition.
10). Let Magisk do its patching and when it has completed take note of where the patched file which it generated was written.
11.) Launch a command line / Powershell / Bash terminal where you can perform ADB commands, and issue the command "adb pull "/storage/emulated/0/Download/magisk_patched-23000_xYzXyZ.tar" (replace "XyZxYz" with whatever random sequence of characters that Magisk generated during its patching operations) to use ADB to download the patched AP file from your device.
12.) Power off your device.
13.) Reboot your device into FANCY download mode by holding the volume up and volume down keys simultaneously while inserting a USB cable that is connected to your PC into your device's USB C charger port. Your device should boot as you insert the USB cable and your bootloader should already be unlocked, so when prompted press the volume up button to continue.
14.) Launch Odin on your PC, and choose the BL, CP, CSC, and UserData images from the firmware package that you retrieved from Samsung to flash the corresponding slots in Odin. In the AP file slot, choose the Magisk patched AP file which contains TWRP as its recovery partition which you retrieved previously using ADB.
15.) Start the flash operation in Odin, and wait patiently for it to complete. Stay alert, because if you left "Auto reboot" checked in the Odin options, your device will reboot immediately upon completion, and there are actions that you need to take while the device is in its "off" state before it re-launches itself.
16.) Once the Odin flash operation has completed, boot to recovery mode. If you left "Auto reboot" checked in Odin, immediately as the flash operation completes, press and hold the power key and the volume up key and remove the USB cable from the device. Otherwise press and hold the power button and the volume down button until the device restarts, and while the device is in its "off" state remove the USB cable and press and hold the power button and the volume up button during device restart to enter recovery mode.
17.) Immediately upon entering recovery mode you should see TWRP do a couple of things that ensure that Samsung's device protection solutions don't remove it. Once those operations have completed, reboot into the system partition.
18.) Your device should be BASICALLY ready to go. Go through the steps to "complete" setup as you see fit. If you have not already done so, connect your device to a WiFi or to an LTE network and then launch the Magisk application.
19.) Magisk may want to download updates, if it does, let it do so.
20.) Once any necessary updates / downloads have completed, re-launch Magisk and it should present you with a prompt to the effect of "Magisk is installed, but additional configuration needs to be done on your device for it to work the right way. Do you want to reboot now?" If you've made it this far, the answer is "Yes, please do."
21.) After rebooting, your device will now be configured, and be running TWRP in its recovery partition, along with a properly Magisk rooted system partition.
22.) ????
23.) PROFIT!
I hope this helps some people out!
- The Scarecrow - 2021/09/22
Has anyone besides been successful?
mydjtl said:
Has anyone besides been successful?
Click to expand...
Click to collapse
I can provide screenshots from the device that I did this to if you would like.
It's pretty cool to see the TWRP logo on a Samsung Tab series device that's running Android 11.
I don't even get the little Samsung warning prompt during device bootup that says "This device's software can't be verified" or whatever Samsung's custom ROM message is. All I get is the "This device's bootloader is unlocked" message, no warning about the integrity of the software.
mydjtl said:
Has anyone besides been successful?
Click to expand...
Click to collapse
Follow this simple as he'll no need to read all these things
pankspoo said:
Follow this simple as he'll no need to read all these things
Click to expand...
Click to collapse
Yeah - pretty much exactly that, except I Magisk patched the system image, and then copied the TWRP package's vbmeta and recovery image into the AP file for the Odin flash, and then flashed every slot rather than just the AP.
is it systemless root?
Will this work on Galaxy Tab A sm-t595? on android 10?
or know of a root guide that will work with said device?
If you dont untick auto reboot, how do you fix any issues that happen because of it?
I rooted my t500 but I think it auto rebooted, which then caused a vbmeta error that stopped it booting. It worked again after flashing the stock rom, but now it gives a vbmeta error if I try to flash a modded rom to root it and I cant get oem unlock to appear in the stock os (download mode says its already unlocked tho)
Hello,
Code:
9.) In Magisk on your device, choose "Select and patch a file" and then choose the AP file that you created and copied to the device which now contains TWRP as its recovery partition
Step 9 yields an error on T515 : Unsupported/Unknown image format
I also tried to install AP patched file with Odin, same result.
Any idea ?
Damn this works so nicely, thanks mate! Cheers!
Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL
If there's enough demand I'll write a proper guide. Also if soft bricked you need to press both volume buttons and plug in usb at right point on restart.
jameswalker457 said:
Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL
Click to expand...
Click to collapse
Thanks @jameswalker457
Which one did you use CSC_HOME or CSC?
When I run with CSC, I get a 'fail' in ODIN However, it does run with CSC_HOME, BL and the patched AP - but it doesn't actually root the device.
Greatful for your help.
Thanks
Used BL AP (with patched boot.img) CSC and HOME_CSC in the userdata
kevinsims said:
Thanks @jameswalker457
Which one did you use CSC_HOME or CSC?
When I run with CSC, I get a 'fail' in ODIN However, it does run with CSC_HOME, BL and the patched AP - but it doesn't actually root the device.
Greatful for your help.
Thanks
Click to expand...
Click to collapse
See above. Missed the quotation
I'm not sure why we need a third thread for this:
SM-X200 root failed...
It's now a bricked tablet after a boot loop, I think should wait to magisk get an update. It won't power on or charge I think. I have two days trying to power on in several times and many key conbinations. No Samsung logo or something. Can I do...
forum.xda-developers.com
The best way to root samsung tab a8 2021 pls
Android 11 I got fast as f boot loop solution below btw An 4 gamers I got fps/ping boost solution below to
forum.xda-developers.com
I still do not have root. What I did:
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" tar -C AP_folder -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
For some reason I can't get from download mode to recovery w/o first booting the fresh android.
No boot loop, but no root either.
These are the file names I got from Samfw:
AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
BL_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_OMC_XAR_X200XAR1AVC1_CL23784803_QB49838021_REV00_user_low_ship_MULTI_CERT.tar.md5
The md5sum of the files:
AP stock: fa97e5cee1deaf26175b27d26df94266
AP patched: 006b12f713fc3caa127bc5cba01ae4b9
BL: 2172ca468462a46917d78e94157aed54
HOME_CSC: 5ede57b9ffe8059f3166dd5de6ef8721
The tar file worried me. It had file names like ./boot.img instead of boot.img. So I created a new file, with the patched boot.img, this way:
cd AP_folder
tar -cvf ../AP_patched.tar *
Then flashed that. Took longer than the previous tar.
On reboot, it asks me to press PWR to accept boot loader unlocked. Then a splash screen saying: unapproved software, then a few boot loops.
I got to recovery, factory reset, the tablet does the LONG boot, does the initial setup thing.
Install Magisk Manager, and root! Google Play still works.
Whoopee! I can now wait for a working TWRP.
jameswalker457 said:
Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL
Click to expand...
Click to collapse
Hello, I have a problem/doubt. I have the files AP, BP... etc I use 7zip to extract the boot.img ..... if I unzip all the AP XXX.tar.md5 the 7zip warns me that there is data after the file, it warns me of an error and at the end it stops in the fota . ...when I replace the boot.img in the AP folder by the one corresponding to the patched with Magisk and use the 7zip again to create the .tar the file does not work with ODIN...I do not know what step or mistake I make. Regards
PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
PS: Root! Thanks Jameswalker457 Cheers! ....
Translated with www.DeepL.com/Translator (free version)
IkeGolden said:
Hello, I have a problem/doubt. I have the files AP, BP... etc I use 7zip to extract the boot.img ..... if I unzip all the AP XXX.tar.md5 the 7zip warns me that there is data after the file, it warns me of an error and at the end it stops in the fota . ...when I replace the boot.img in the AP folder by the one corresponding to the patched with Magisk and use the 7zip again to create the .tar the file does not work with ODIN...I do not know what step or mistake I make. Regards
PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
PS: Root! Thanks Jameswalker457 Cheers! ....
Translated with www.DeepL.com/Translator (free version)
Click to expand...
Click to collapse
> if I unzip all the AP XXX.tar.md5
That is because a .tar.md5 is a tar file with an md5 concatenated to it.
> use the 7zip again to create the .tar the file does not
The proper tool to create .tar files is "tar".
>PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
Care to be more specific on how you did that?
>PS: Root! Thanks Jameswalker457 Cheers! ....
Good news.
Have root my SM-X205 (LTE) for 1 Feb Patch level but no go with latest May update.
Getting constant boot loop (exactly same process, magisk boot.bin etc) so rolled back to Feb for now.
lufee84 said:
Have root my SM-X205 (LTE) for 1 Feb Patch level but no go with latest May update.
Getting constant boot loop (exactly same process, magisk boot.bin etc) so rolled back to Feb for now.
Click to expand...
Click to collapse
What firmware version worked, and which failed?
X200XXU1AVC1 worked for me.
Yes, X205XXU1AVC1 works.
No luck with latest X205XXS1AVE1 (May Patch).
garyemiller said:
I'm not sure why we need a third thread for this:
SM-X200 root failed...
It's now a bricked tablet after a boot loop, I think should wait to magisk get an update. It won't power on or charge I think. I have two days trying to power on in several times and many key conbinations. No Samsung logo or something. Can I do...
forum.xda-developers.com
The best way to root samsung tab a8 2021 pls
Android 11 I got fast as f boot loop solution below btw An 4 gamers I got fps/ping boost solution below to
forum.xda-developers.com
I still do not have root. What I did:
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" tar -C AP_folder -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
For some reason I can't get from download mode to recovery w/o first booting the fresh android.
No boot loop, but no root either.
Click to expand...
Click to collapse
Not sure if this helps but i read an article that says you should patch the whole AP tar file rather than extract just the boot.img. Maybe because it patches the recovery and super etc img files too? I havet tried this yet as I cant even get my bootloader unlocked
dan.langridge88 said:
Not sure if this helps but i read an article that says you should patch the whole AP tar file rather than extract just the boot.img. Maybe because it patches the recovery and super etc img files too? I havet tried this yet as I cant even get my bootloader unlocked
Click to expand...
Click to collapse
Dunno where you read that, don't care. This works (as above):
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" cd AP_folder"
" tar -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
Note the fixed "tar" command. Do not use "tar -C".
garyemiller said:
Dunno where you read that, don't care. This works (as above):
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" cd AP_folder"
" tar -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
Note the fixed "tar" command. Do not use "tar -C".
Click to expand...
Click to collapse
OK, I've un-tarred the AP tar.md5 and patched the old boot-img file on the device, renamed it and replaced the original boot.img in the AP "folder".
Steps 8 & 9 are a little confusing for me, if you could expand on those. Can I use 7zip to re-tar? Those look like DOS commands in step 8.
Ar-Pharazon said:
OK, I've un-tarred the AP tar.md5 and patched the old boot-img file on the device, renamed it and replaced the original boot.img in the AP "folder".
Steps 8 & 9 are a little confusing for me, if you could expand on those. Can I use 7zip to re-tar? Those look like DOS commands in step 8.
Click to expand...
Click to collapse
Slightly expanded:
1. unlocked bootloader
2. install magisk manager 24.3 on the tablet
3. Download X200XXU1AVC1 firmware from Samfw onto PC
4. unzip the X200XXU1AVC1 firmware zip file
5. Make a directory for the AP tar contents
"mkdir AP"
6. Untar the AP tar file into directory AP, all on one line:
"tar -xvf AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5 -C AP"
7. Change the current directoy to the AP directory:
"cd AP"
8. Using adb send boot.img, to the tablet,.
9. Patch boot.img with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
10. Using adb copy magisk_patched-24300-9Iez2.img from the tablet and into the AP directory.
11. Rename magisk_patched-24300-9Iez2.img to boot.img:
"mv magisk_patched-24300-9Iez2.img boot.img"
12 Create a tar file from the AP directory Note the space and period(".") after ".tar":
" tar -cvf AP_patched.tar ."
13. Use adb on PC to enter download mode on tablet:
"adb reboot bootloader"
14. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar as files to be flashed.
15. Flash via Odin, exit download mode, enter stock recovery, factory reset
How about that?
garyemiller said:
Slightly expanded:
1. unlocked bootloader
2. install magisk manager 24.3 on the tablet
3. Download X200XXU1AVC1 firmware from Samfw onto PC
4. unzip the X200XXU1AVC1 firmware zip file
5. Make a directory for the AP tar contents
"mkdir AP"
6. Untar the AP tar file into directory AP, all on one line:
"tar -xvf AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5 -C AP"
7. Change the current directoy to the AP directory:
"cd AP"
8. Using adb send boot.img, to the tablet,.
9. Patch boot.img with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
10. Using adb copy magisk_patched-24300-9Iez2.img from the tablet and into the AP directory.
11. Rename magisk_patched-24300-9Iez2.img to boot.img:
"mv magisk_patched-24300-9Iez2.img boot.img"
12 Create a tar file from the AP directory Note the space and period(".") after ".tar":
" tar -cvf AP_patched.tar ."
13. Use adb on PC to enter download mode on tablet:
"adb reboot bootloader"
14. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar as files to be flashed.
15. Flash via Odin, exit download mode, enter stock recovery, factory reset
How about that?
Click to expand...
Click to collapse
I'm guessing those are Linux commands?
In any event, I made 7zip re-tar the AP folder with the patched boot.img, but it ends in .tar.tar
Is this an issue, or should/can it be renamed .tar.md5 like the original?
Ar-Pharazon said:
I'm guessing those are Linux commands?
In any event, I made 7zip re-tar the AP folder with the patched boot.img, but it ends in .tar.tar
Is this an issue, or should/can it be renamed .tar.md5 like the original?
Click to expand...
Click to collapse
I do them on Linux, but they can also work on WinBlows. Since I do not use M$ products, I can only say I've seen those commands work on WinBlows, but can't say how to set that up.
I also can't help you with 7zip, it can run on Linux, but never use it myself.
People have problems when they don't use "real" tar, so don't. Save yourself the pain.
You do not need to convert the .tar to a .tar.md5. Odin will use either file type. A .tar.md5 file is a .tar file with its md5 hash appended. Odin can use the file to verify the .tar integrity, but that is optional.
Ieudhd
i donloaded diud
Hello Sams10, did you make the bootloader before or not as explained in the tutorial.
You said your flasher with odin more detail would be welcome, how did you do there according to your comment your flashed directly in download mode without having done the manipulation for the bootloader and then did what.
bootloader unlocked and kg checking
every instructions for s10 is outdated including the lineage os website and youtube i have checked all
heimdalll latest 1.4.2 doesnt work with samsung s10.
19.9.2022 on latest android firmware new zealand firmware custom rom doesnt work , only europe and americas will work
Hello Sams10, already a little politeness because I said hello to you, you post 4 times without saying hello.
I don't understand the unlock bootloader ok then S10 is good s10 exynos or 5 G, I followed John Wu's tutorial as explained in the magisk thread on this forum no problem.
You have well modified in magisk AP of the official rom then trafer on your pc with adb pull then odin 3.14.4 flash the 4 files BL-AP patched-CP Home CSC.
g973F exynos, not 5g, u must be americas europe firmware , vodafone nz firmware probably doesnt work
this is my current download mode
my screen is cracked thats the purple lines and dead pixel on top left
Not work
Hello Sams10, you start in dowload mode you flash with odin 3.14.4 the official firmware the one mark in my signature me AUT or XEF lash the 4 BL-AP-CP-CSC files it will restart as on the first day. Then install magisk 25.2 you transfer AP on your S10, you modify with magisk you will have a file in internal memory in dowload magisk_patchedxxxx.tar you transfer it with ADB on the pc which in adb must give this adb pull /sdcard/Download/magisk_patched-25200_G3e9K.tar
once transferred ok you put yourself in dowload mode and you put the file BL -AP patched -CP -home CSC you start you let it restart and you open magisk to activate zygisk then you install the modules you will find here https://forum .xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/
instalation look here from john Wu https://topjohnwu.github.io/Magisk/install.html
read the instruction part, then when you have finished and root I will send you the file to remove the warning message at start-up ok
I use ap magisk patched and CSC , not home CSC when I flashed and had boot loop
Does it have to be an adb pull for the patched firmware from Android , I just use file transfer on windows to transfer the magisk patched ap file from the s10 to the windows
Try with home CSC as john wu says you have to do adb from s10 to pc with adb windows not send all.
Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.
John Wu says CSC not home csc because he want to erase firmware data
Hello Sams10, yes you made a backup of your data before with smart switch or others. For me it worked if you follow the present tutorial look on my tutorial
1- The bootloader follow explanation Use vol down + vol up + USB cable plugged into a PC to boot the phone into download mode;
Long press vol up then confirm that you want to unlock the bootloader (this is only needed once);
* Please note that all your data will be erased, including internal memory, and the phone will restart!!
5- Let the phone start normally, go through the configuration and connect to the Internet (wireless or mobile data) in order to unlock
6- Make sure OEM Unlock is enabled in Developer Settings.
2- Once reboot install magisk 25.2 APK.
3- Download the official firmware on Samobile.com or frija you will find this on the forum.
4- Transfer the official firmware AP to the smartphone.
5- Open magisk recovery mode choose corrective mode choose the AP download press "let's go."
6- Once the modification is finished in the root directory, download a patched_magiskxxxx.img.tar file if found.
7- Transfer it with adb pull like this adb pull /sdcard/Download/patched_patched.magiskxxxx.img[.tar] you can rename it "patched_magisk.img.tar"
8- Put your smartphone in download mode Use vol down + vol up + usb cable connected to a PC to start the phone in download mode, briefly press vol up to
confirm that you want to enter download mode;
9- Open Odin latest version placed 4 files following BL-AP magisk patched.img.tar-CP-home CSC leaves auto start checked in odin option.
10- It will restart open magisk activated Zygisk restart install safetynet modules - shamiko-hidemagisk prop config-busybox nk-lposed see on this page https://forum.xda-developers.com/t/discussion-magisk-the-age -of-zygisk.4393877/
message #3-#6 to #9.
11- Install foxmagiskmodulemanager the catalog of modules for magisk here https://github.com/Fox2Code/FoxMagiskModuleManager/releases
12- Once rooted the security message for the removed open Odin place UP-param.tar in AP and flashed. See attached file
Up_param.tar download link on my mega here to know for S10 exynos for S10e- S10+ versions see 5G I don't know if it works.
Is this normal I have to wait about 30 minutes after power off to try get into download mode??
Maybe something is broken the phone like doesn't turn off properly or something, have to wait sometimes one hour