If you ever flashed a ROM and found that you've not been able to send and receive any kind of wireless activities, chances are your modem file is either corrupted or some problem with it.
It happened to me when i tried to install RR Nougat and found that my modem files are missing and any methods of restoring backup from TWRP ended up unsuccessful. Thank god! i got Fastboot ROM of MIUI 8 Nougat Beta and flashed the modem file which i found inside it.
Download the Modem file from this link.
Instructions:
1. Boot your phone into fastboot mode and connect your phone to PC.
2. Flash the Modem by entering the command
Code:
fastboot flash modem NON-HLOS.bin
3. After flashing, reboot your device.
NOTE: Make sure the modem file is in the same folder as the fastboot binary. If you added the fastboot to your path directory, having modem and fastboot
binary in same folder is optional.
NOTE: Fastboot and ADB codes are case-sensitive, i.e. make sure you type exactly, including the capital letters.
Thankyou!
I have an RN4X(international)
Can I
1) download the latest greatest fastboot ROM from here
http://en.miui.com/a-234.html
2) extract the NON-HLOS.bin (which is >80MB, whereas the bin you linked is just 36MB)
and
3) flash it (as explained by you)
Do i need to unlock bootloader first?
fx3000se said:
I have an RN4X(international)
Can I
1) download the latest greatest fastboot ROM from here
http://en.miui.com/a-234.html
2) extract the NON-HLOS.bin (which is >80MB, whereas the bin you linked is just 36MB)
and
3) flash it (as explained by you)
Click to expand...
Click to collapse
If your board's name is mido then you can. To know the name of your board download AIDA64 from play store and check.
thanks a lot, u saved my phone
Hello,
I'm did everything in this stage but loader is stuck at NON-HLOS.bin and doesnt load it.
I can access fastboot, in fastboot, loading last 2 second. Its says succesfull but it doesnt load. Since loading cant last 2 secon.
Any tips?
Model: 2016102
Windows 10, latest flash loader
crymed said:
Hello,
I'm did everything in this stage but loader is stuck at NON-HLOS.bin and doesnt load it.
I can access fastboot, in fastboot, loading last 2 second. Its says succesfull but it doesnt load. Since loading cant last 2 secon.
Any tips?
Model: 2016102
Windows 10, latest flash loader
Click to expand...
Click to collapse
Bad Cable?
Can i flash this modem with my previous version on my phone is miui 8 8.5.8.0?
Btw, is this file flashable using TWRP? And, what is/are the different between this modem and global? I mean, the one in the global rom?
Shaikat007 said:
Do i need to unlock bootloader first?
Click to expand...
Click to collapse
Obviously. Otherwise your PC's fastboot screen will keep saying that the OEM is locked.
Related
I unlocked the bootloader but my sim card its not recognised, also, when i try to root my device i cant get to get root access, im on jelly bean (stock), yes i know that there are threads about this but none of them helped me, what should i do?
phone info:
fastboot mode: product name - herring
hw version - rev 16
bootloader version - i9020xxlc2
baseband version - i9020uckj1
carrier info - att
serial number - 363106d8a71800ec
lock state - unlocked
other info:
kernel version 3.0.31 -g3b0c5d2
build number: jrO03E
baseband version: i9020auckj1 // see, its like the baseband on the fastboot and on the settings app don't match
where did you get your JB install?
zeiroe said:
where did you get your JB install?
Click to expand...
Click to collapse
Via OTA
agumsb said:
Via OTA
Click to expand...
Click to collapse
Oh crap ... that's disturbing.
zeiroe said:
Oh crap ... that's disturbing.
Click to expand...
Click to collapse
my nexus its an i9020a so i dont know i think that the kernel and the baseband and the rom dont match i dont know, i need help!
I'd start by trying to get your phone back to a stock working load by downloading the correct factory image here:
https://developers.google.com/android/nexus/images
or here for the 4.0.4 ((IMM76D) build
https://dl.google.com/dl/android/aosp/sojua-imm76d-factory-76ad4959.tgz
Unpack that factory image with 7Zip and find the radio-crespo-xxxxxx.img, boot.img, system.img, recovery.img, and flash those to your phone with fastboot.
Once you get it up and running at a working state, download the OTA again and try again.
http://android.clients.google.com/packages/ota/google_crespoa/cSw0yuoF.zip
zeiroe said:
I'd start by trying to get your phone back to a stock working load by downloading the factory image here:
https://developers.google.com/android/nexus/images
or here for the 4.0.4 ((IMM76D) build
https://dl.google.com/dl/android/aosp/sojua-imm76d-factory-76ad4959.tgz
Unpack that factory image with 7Zip and find the radio-crespo-xxxxxx.img, boot.img, system.img, recovery.img, and flash those to your phone with fastboot.
Once you get it up and running at a working state, download the OTA again and try again.
http://android.clients.google.com/packages/ota/google_crespoa/cSw0yuoF.zip
Click to expand...
Click to collapse
How can i flash this with fastboot?
agumsb said:
How an i flash this? because stock recovery wont flash it i tried to install clolckwork recovery but i cant get it working
Click to expand...
Click to collapse
The same way you unlocked the bootloader when you first got your phone
Instead of unlocking the bootloader, you'll be flashing individual partitions. You will have the phone in bootloader mode and connected to your computer.
unzip and move the files I indicated above into the same folder as fastboot in android-sdk\platform-tools
fastboot flash radio <radio-crespo-version.img>
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
zeiroe said:
The same way you unlocked the bootloader when you first got your phone
Instead of unlocking the bootloader, you'll be flashing individual partitions. You will have the phone in bootloader mode and connected to your computer.
unzip and move the files I indicated above into the same folder as fastboot in android-sdk\platform-tools
fastboot flash radio <radio-crespo-version.img>
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
Thanks man! thats sounds like its gonna work!
it did not work :/ can somebody else help me?
Hi ppl. I need help bad! I accidentally erased my os. So when I try to flash a rom using the mi flash tool(which is amazing) it won't work because I have no operating system to enable USB debugging.so it says enable USB debugging but I can't. Any help would be appreciated TW RP installed unlock bootloader. Thanks in advance!!
just flash recovery rom using twrp then.
Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.
So twrp is flashed? Then yes try sideload. Also make sure your ADB is up to date as I've had that cause issues with large files and sideload before.
M.
dirtyrott3njb said:
Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.
Click to expand...
Click to collapse
Miflash doesn't need for usb debugging to flash rom I believe. It's all fastboot. If ur phone is not detected by pc, it means drivers.
It does indicate USB debuging not on. So yes it does . I've used it before to flash TWRP. The flash will also install the drivers before you use it so I can understand why it won't let me transfer anything from PC to phone when fastboot mode. It won't let me get past that stuff in this USB debugging is enabled. Frustrating brand new phone to only a couple weeks old.
Have you booted to twrp and format data (the one where you have to type "yes")?
Mi flash only required adb because it needs to run adb reboot fastboot. I'm in the States as well, PM me and maybe we can get this guy working over remote support. I haven't seen this issue myself, so I can't comment much.
Sent from my Mi MIX 2S using Tapatalk
@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?
dirtyrott3njb said:
@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?
Click to expand...
Click to collapse
Its all good. I'm about to pick up my kids from school, so let me head home, I'll PM you in a bit. We can use TeamViewer or something. If it comes down to it, I also have my work login to use for remote assist. You just need a semi up to date laptop or desktop computer.
Hopefully we can get this solved quickly. I'm unfortunately not in your immediate area, otherwise much easier hands on. The company I work for is down the street from your location however, I'm just a remote systems guy.
Sent from my Mi MIX 2S using Tapatalk
How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?
dirtyrott3njb said:
How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?
Click to expand...
Click to collapse
Tried to pm you but msg sent failed.
Only thing is for some reason I can't transfer anything for my PC to TW RP or my internal storage some reason just doesn't accept it and it's not my computer
I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.
sg01fc said:
I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.
Click to expand...
Click to collapse
The OP's issue was solved by just flashing TWRP, booting to it and sideloading the Stock ROM. I had the OP download the fastboot files as well, but we ended up not needing them.
Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants)
Firmwares
the latest firmware as of time of writing is February's 2020 OTA (BECKHAM_RETAIL_9.0_PPWS29.131-27-1-18_subsidy-DEFAULT_regulatory-DEFAULT_CFC) = https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
previous OTAs RETAIL variant can be found here = https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
future OTAs possibly here = https://androidfilehost.com/?w=search&s=beckham
other variants = https://mirrors.lolinet.com/firmware/moto/beckham/official/
Unlock Bootloader
first you need to install Motorola Drivers = https://support.motorola.com/us/en/solution/MS88481
- ATTENTION - use the most up-to-date ADB Drivers otherwise will brick if older version is used; instead of downloading ADB elsewhere which is often old version, get it directly from GOOGLE, here = https://dl.google.com/android/repository/platform-tools-latest-windows.zip
now you can proceed to unlock bootloader = https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
TWRP
get the official TWRP here = https://dl.twrp.me/beckham/
- ATTENTION - if you just want root access, then there's no need to install TWRP, just boot from the .img once using the latest version
use TWRP to make a backup of EFS partition before installing anything, store the backup files outside of the device
if you want custom ROMs or GSI, then you will need to install TWRP installer .zip into the recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the latest .zip version in the recovery partition. Unfortunately the only official installable version of TWRP that exists is bugged, and the TWRP developers haven't fixed it yet, go talk to them ask for some love, be respectful = https://github.com/TeamWin/android_device_motorola_beckham/issues
Magisk
install Magisk using the new&correct method AKA "Boot Image Patching Method" to be able to install OTA later = https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
when OTA arrives, you may manually install it whilst retaining Magisk by carefully following these instructions = https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
- ATTENTION - you won't be able to install stock OTAs if you use older method or if system partition is modified, be really careful to not alter the hash of the partitions
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
@heynando, what is the difference between "retail" and "retus"? Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?
ritchea said:
@heynando, what is the difference between "retail" and "retus"?
Click to expand...
Click to collapse
RETUS is short for Retail + US.
The difference between RETUS and RETAIL is, I imagine, cannot confirm, the same RETAIL firmware with some US regional modifications such as bloatware or CSC thing
you can check which model is yours in SETTINGS > SYSTEM > ABOUT PHONE > SOFTWARE CHANNEL. Or in the bootloader by running the command
Code:
fastboot getvar product
you can find the entire list of product codes here = https://mirrors.lolinet.com/firmware/moto/readme-en.html#listone
XT1929-4(Canada, SS, 4+32GB) XT1929-3(NA/Sprint, SS, 4+32GB)
XT1929-4(NA/AMZ/BWACA/RETCA/RETUS/USC, SS, 4+64GB)
XT1929-5(BRAZIL/RETBR/TIMBR/TEFBR, DS, 4+64GB / 6+128GB)
XT1929-6(LATAM/AMXLA/NIIPE/ATTMX//TEFCL/TEFPE/RETLA/RETAR/RETMX/RETCL/AMXMX, DS, 4+64GB)
XT1929-6(LATAM/RETLA/TEFCO/TIGCO, DS, 6+128GB)
XT1929-8(EMEA_APAC/RETEU/DTEU, DS, 4+32GB / 4+64GB)
ritchea said:
Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?
Click to expand...
Click to collapse
I believe that's the internal version of the software. If the number changes that emphasizes there has been software changes and/or tweaks in the system and/or firmware. If the number doesn't change, then it's just a regular security patch with no further modifications in system and/or firmware.
Thanks for that info. Yeah, I know mine has the retus software channel. I just couldn't find or figure out if Retail was actually one word or if it was a combo of ret+ail. That version has a LOT of software posted.
I flashed retail on an EU model. And after it the software channel say Reteu just like the original. Also the model number is as it should be. In my opinion you can flash retail firmware on us and EU models.
confirmed that this firmware is working on XT1929-4
these are the steps I took:
downloads and setup
install moto drivers (in windows, not needed for linux)
install android tools (adb and fastboot)
downloaded official TWRP
downlaoded and extracted the firmware
backup of partitions (including efs)
Code:
adb reboot bootloader
fastboot boot twrp_recovery.img
backed up lots of partitions
rebooted system
copied the TWRP backup files to my pc for safe keeping
set the fastboot slot (i did this because many of teh fastboot commands below were failing)
Code:
adb reboot bootloader
fastboot --set-active=a
rebooted back into bootloader
installed the firmware
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot reboot
installed magisk the new good way
did the initial device setup
installed magisk manager
copied the boot.img from the extracted firmware above to the phone.
followed these steps for boot img patching and install of magisk https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
sirkuttin,
Thanks for the detail how to. That worked perfectly for me, and my moto z3 play, same model as yours. I could not get the ota or even lenovo smart assistant to work on my phone. It basically had it locked up, stuck on the boot logo. I'm assuming its the old way of install magisk that caused that. This got me on the latest firmware release, and then installed magisk the new way. Lenovo smart assistant was useful in downloading the firmware.
Thanks.
Hi I tried the new magisk install way. I'm on XT1929-4_BECKHAM_RETUS_9.0_PPW29.183-29-1, copy boot.img and patched it to magisk_patched.img. Then after fastboot flash boot /path/to/magisk_patched.img and a reboot, i'm not stuck on the motorola powered by android screen. Verity mode is set to disabled.
I tried holding down the power button to simulate a battery pull but no luck, the screen just stays on. Can anybody give me any advise? I think now I have to just wait till the device is out of juice. Never experience this before.
---------- Post added at 02:16 PM ---------- Previous post was at 01:31 PM ----------
So the battery pull is "Power + Vol Down". I was able to flash the PPW29.183-29-1 firmware and get it going again. I noticed it tried to upgrade me to PPW29.183-29-1-2 so I must have been on newer firmware. I flashed the magisk_patched and am rooted now.
It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).
ch3mn3y said:
It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).
Click to expand...
Click to collapse
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.
heynando said:
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.
Click to expand...
Click to collapse
It, unfortunately, does... However I csnnot update (continous update unsuccesful) :f Have to check if Xposed module is not a reason.
And You probably could use Installer to flash stock recovery? If not TWTP itself however I've never checked if one for Play has access to recovery partiotion to flash images. It should gave if it can be done using the installer...
Sent from my Moto Z3 Play using Tapatalk
ch3mn3y said:
However I csnnot update (continous update unsuccesful)
Click to expand...
Click to collapse
Me too and it drove me nuts, I did patch the /boot partition with the original file, but the OTA app still failed to install, even after reboot. And there's no useful data in the logcat to debug the app. So I gave up and had to use Titanium to freeze the OTA app otherwise it would keep trying to download and install infinitely.
ch3mn3y said:
:f Have to check if Xposed module is not a reason.
Click to expand...
Click to collapse
It's probably not because I don't use it and the OTA method didn't work me either
ch3mn3y said:
And You probably could use Installer to flash stock recovery?
Click to expand...
Click to collapse
Yes you're right, I agree there..
heynando said:
Yes you're right, I agree there..
Click to expand...
Click to collapse
Just checked the inside of the installer zip file and it won't work. Still once every 3 months it wouldn't be a problem to connect device to PC and flash recovery.img with fastboot.
Is there a list with a commands and order how to flash Z3 Play images of official firmware? I want July patches and have some problems, so clean reflash is what I need.
Additional question is if I have to use "-u" when flashing second and other system images? Remember I had to do it with my X Play coz of unlocked bootloader and here I have one in the same state as well. If yes than could someone tell me where to put it, coz I'm not sure...
tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
Ramble2k said:
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
Click to expand...
Click to collapse
This one, make sure to get the latest. https://mirrors.lolinet.com/firmware/moto/beckham/official/RETUS/
Hi, I'm trying to unlock my Moto Z3 Play bootloader, but I don't get the code on CMD, but only a few numbers ... The version of my device is PPW29.131-27-1-11, channel RETBR software.
Someone went through this, can you tell how to reverse this situation?
I couldn't get the bootloader unlocked for xt1929-4. I tried different computers, Linux and win. Have latest adb and fastboot. When fastboot OEM get_unlock_data is given, I says counttas slot not found etc., can someone help?
It may seem obvious, but you
checked OEM unlocking and USB Debugging?
Hi everyone urgently need help root instructions for the xcover 5. there is a possibility it runs with android 11. thank you in advance
akin03 said:
Hi everyone urgently need help root instructions for the xcover 5. there is a possibility it runs with android 11. thank you in advance
Click to expand...
Click to collapse
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Tab E said:
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Click to expand...
Click to collapse
thanks for the instruction. what do I have to type in adb mode. Is there a program where I can use the adb mode.
akin03 said:
thanks for the instruction. what do I have to type in adb mode. Is there a program where I can use the adb mode.
Click to expand...
Click to collapse
There is no program. You have to download adb and fastboot tools
Once your phone is in fastboot mode and you have opened command prompt in adb fastboot folder in you pc type
fastboot oem unlock (this unlocks the bootloader)
fastboot flash boot boot.img (this flashed the magisk patched or rooted boot.img to your devices boot partition
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Patch Stock Boot Image via Magisk and Flash it using Fastboot
This tutorial contains explanation on how to Patch Stock Boot Image file of your device and subsequently flash it via Magisk.
www.droidwin.com
Tab E said:
There is no program. You have to download adb and fastboot tools
Once your phone is in fastboot mode and you have opened command prompt in adb fastboot folder in you pc type
fastboot oem unlock (this unlocks the bootloader)
fastboot flash boot boot.img (this flashed the magisk patched or rooted boot.img to your devices boot partition
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Patch Stock Boot Image via Magisk and Flash it using Fastboot
This tutorial contains explanation on how to Patch Stock Boot Image file of your device and subsequently flash it via Magisk.
www.droidwin.com
Click to expand...
Click to collapse
Thanks for the instructions. Did it as described. However, I'm stuck in fastboot mode when sending. Is there a guide or a way to flash the patched file via odin?
akin03 said:
Thanks for the instructions. Did it as described. However, I'm stuck in fastboot mode when sending. Is there a guide or a way to flash the patched file via odin?
Click to expand...
Click to collapse
Yes. Compress the file to '.tar' and flash it
Tab E said:
Yes. Compress the file to '.tar' and flash it
Click to expand...
Click to collapse
Ok just the patched file? And do I have to pay attention to something?? Flashing via AP or BL?
akin03 said:
Ok just the patched file? And do I have to pay attention to something?? Flashing via AP or BL?
Click to expand...
Click to collapse
Ap
Tab E said:
Ap
Click to expand...
Click to collapse
Hi does not get errors on odin. Do I just need to flash the patched file or other files.
Request for help.. Have flashed the whole ap file about magisk after a guide now I have bootloop and the device restarts after 3 min. I don't get the device rooted
Hi. Is n'one who can help me...! It's important...?!
akin03 said:
Hi. Is n'one who can help me...! It's important.
Click to expand...
Click to collapse
Hi, if you send me the exact ROM of your device I can create a Root-AP file (boot.tar) for you which you flash through Odin (AP). Note that after flashing the Root file your phone will be factory reseted.
akin03 said:
Hi. Is n'one who can help me...! It's important...?!
Click to expand...
Click to collapse
Or you can follow this guide, it is the exact same process of rooting newer samsung devices.
How to root Samsung Galaxy X Cover 4s Enterprise Edition (SM-G398F)
Hey there, is there a way to root a Samsung Galaxy X Cover 4s (SM-G398F)? The phone is from June 2019 and runs Android 9.0. I haven't found anything on the forum. Here's a link to the Samsung website...
forum.xda-developers.com
I tried to patch the updated AP (boot loop)
I tried to flash the stock AP and then only the updated boot.img (boot loop)
I also tried flashing a patched recovery.img (HASH_MISMATCH error)
Maybe Magisk has some issues with that phone.
Did anyone have success in rooting the G525F?
hatl said:
I tried to patch the updated AP (boot loop)
I tried to flash the stock AP and then only the updated boot.img (boot loop)
I also tried flashing a patched recovery.img (HASH_MISMATCH error)
Maybe Magisk has some issues with that phone.
Did anyone have success in rooting the G525F?
Click to expand...
Click to collapse
How to Root via Magisk Patch:
1) Download and open the stock ROM
2) Extract the boot.img.lz4 and convert it to boot.img with a program like lz4_win64
3) Convert the boot.img to boot.tar with 7zip or winRAR
4) Copy boot.tar to your mobile phone and patch it with Magisk, so you will get magisk-patched.tar
5) Rename the patched magisk-patched.tar to boot.tar
6) Flash it with Odin in AP mode and you are rooted!
Only this method worked for me, if you try it differently it may not work! (Xcover4s)
Should work on all Samsung phones with Android 9 or higher.
I did this with the latest ATO firmware: https://samfw.com/firmware/SM-G525F/ATO
and ended up in a boot loop.
Maybe it's an issue with the latest Android 11 version - or the Xcover 5
I have the same issue . Stuck on boot screen after flashing. Works fine after I re-flash original boot or do a complete re-flash with original firmware. I can successfully root my s9 so am not a complete noob. My region is NEE
One more weird thing is that i cant seem to get it in recovery after the rooted boot flash. Any ideas for checking relevant logs?
There is a extra file in the boot.img called vmbeta compared to the s9 boot.img. Is it possible that this is the issue or am i completely wrong?
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your p
forum.hovatek.com
[CLOSED] What is "vbmeta.img" ?
What is "vbmeta.img" and why it is needed? How it works? Does anybody knows?
forum.xda-developers.com
ive tried like evverything but get stuck on a message sayying my phone isnt running on offical firmwire or something like that. But now i have another problem. When in fastboot adb cant find my device. If my phone is just on and im not in fastboot adb finds it. Why is that happening?
Tab E said:
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Click to expand...
Click to collapse
When my phone is in fastboot mode it cant find it.. WHen its on adb devices finds it but not when in fastboot mode.
A search for "root xcover 5" brings up plenty of ways to achieve this, but most of those sites are click bait, with identical instructions for any device you can think of. Other people are more helpful, like those who replied above, but I would like to know if anyone has ACTUALLY ROOTED A XCOVER 5 SUCCESSFULLY. And yes, if so, I'd like to know how it was done.
NOTICE : As of June 15, 2022 you no longer NEED this method as the OTA for Android 11 has been released. This is here for those who don't get the OTA or need an upgrade from a clean reset manually using only the RSA tool.
Credits to : morpheus092511 over on the Lenovo Forums for tricking the Moto Tool into installing the stock firmware, and Chepr29 from the Lenovo Forums for the fastboot method that doesn't require the tool.
In fastboot on your PC after your extract the Android 11 firmware and have your device in recovery mode enter the following commands (back up your data this will clean wipe it!) :
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot erase userdata
fastboot erase carrier
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
1. BACK UP ANY IMPORTANT FILES OR INFORMATION! DON'T FORGET TO BACK UP YOUR TWO FACTOR AUTHENTICATION CODES AS WELL! This method can be done with other firmwares, but I have only tested a clean wipe upgrade from stock Android 10 to 11 RETUS on the Motorola One Ace 5G (Unlocked from Amazon) and can't comment on other firmwares.
2. Windows ONLY! DOWNLOAD THE RSA software from Motorola that allows you to recover, backup, or flash stock firmware to your device.
https://download.lenovo.com/lsa/Releases/Rescue_and_Smart_Assistant_v6.1.1.9_signed_setup.exe
3. DOWNLOAD the retail Android 11 firmware for the Motorola One Ace 5G (Kiev) Retail USA / Unlocked from here :
https://mirrors.lolinet.com/firmware/moto/kiev/official/RETUS/XT2113-2_KIEV_RETUS_11_RZK31.Q3-45-16_subsidy-DEFAULT_regulatory-DEFAULT_R8_CFC.xml.zip
4. Go to C:\ProgramData\RSA\Download\RomFiles and extract the .zip folder here. You may need 7Zip, or WinRAR to do so. I recommend 7Zip as it's open source and free without nag popups.
https://www.7-zip.org/a/7z2107-x64.exe
5. Connect your phone to the PC via USB-C and shut it off. Hold volume down, and power on at the same time until the recovery screen shows.
6. The RSA software will detect your proper "latest" firmware automatically in fastboot mode, allow it time to download and wait until it's done, give it some time after it hits 100.00% because the program will begin decompressing and unzipping the stock firmware, but it will NOT tell you this, keep that in mind!
7. Under the same directory in Step 4, you should now have two folders. One that says 10 and 11 with almost the same naming convention, delete ALL of the files in the folder that RSA downloaded (the 10 folder), and copy and paste all of the files from (the 11 folder), but LEAVE the name of the folder the same as what it was when RSA downloaded it, don't change the name or you'll either have to re-name it back, or re-download the firmware once more and let it extract.
8. Go back to the RSA program and hit the yellow "Rescue" button. Don't touch your phone and leave it alone! All data will be erased and it will begin flashing the firmware from Android 11 without a single issue. If you have PIN or password locked your phone previously, upon first boot up Android will ask you for your previous device PIN before you can begin setting up the device initially.
NOTE : This should preserve your warranty, mine expired a few months ago and I haven't been able to confirm this 100% because of this. (we waited a LONG time for this update!) Since the process does NOT require your bootloader to be unlocked or modified in anyway whatsoever, I do NOT see how you could possibly void the warranty. As of this writing, I have NEVER attempted to even unlock my bootloader for stability purposes, and because rooting isn't a concern to me on this device. In fact, to my knowledge you are NO LONGER able to unlock the bootloader on Android 11, so proceed with caution if this is something you require! There may be a 3-day wait of being connected to the Internet before you are allowed to use the OEM Unlock function, please keep that in mind if this is an issue.
Since it is stock firmware, there are no functionality issues to be concerned with. Calling, 5G, camera, Bluetooth, NFC and other basic sensors and extra functionality work 100% to my knowledge after testing most functions myself for the better duration of a day, even my Fossil Gen 6 Android Wear 2.0 (updating to 3.0 soon) watch is functioning flawlessly over WiFI and Bluetooth with the new update.
Please note this method is now outdated, as the OTA has been released for Android 11.
TheLastSidekick said:
Please note this method is now outdated, as the OTA has been released for Android 11.
Click to expand...
Click to collapse
It does work though, for anybody needing (or just wanting) to recover from a blown system without having to wait for a Rescue download.
Also it's a bit irritating that 95-9 for RETUS never got uploaded to lolinet. And now since 11 is released, that's all you can get through RSA, because it INSISTS on upgrading the phone to the latest version.
(Edit/Add) I would just like to have 95-9 handy for emergency reflashing if ever needed, but now I can't get my hands on it anywhere . . . except on that "easy" website and I don't really trust it 100%.
NOTE: I just flashed an 11 upgrade (manually via fastboot) and there was only 0-9 sparsechunk files. No super.img_sparsechunk.10 to be found, either the file or in the servicefile.xml . . . ? This was specifically the KIEV_RETAIL_RZK31.Q3_45_16_subsidy_DEFAULT_regulatory_DEFAULT_R8_CFC.xml firmware . . .
Moondroid said:
It does work though, for anybody needing (or just wanting) to recover from a blown system without having to wait for a Rescue download.
Also it's a bit irritating that 95-9 for RETUS never got uploaded to lolinet. And now since 11 is released, that's all you can get through RSA, because it INSISTS on upgrading the phone to the latest version.
(Edit/Add) I would just like to have 95-9 handy for emergency reflashing if ever needed, but now I can't get my hands on it anywhere . . . except on that "easy" website and I don't really trust it 100%.
NOTE: I just flashed an 11 upgrade (manually via fastboot) and there was only 0-9 sparsechunk files. No super.img_sparsechunk.10 to be found, either the file or in the servicefile.xml . . . ? This was specifically the KIEV_RETAIL_RZK31.Q3_45_16_subsidy_DEFAULT_regulatory_DEFAULT_R8_CFC.xml firmware . . .
Click to expand...
Click to collapse
Yeah the whole thing is strange the way the way each firmware is slightly a different size between what is evidently the same Retail build.
Actually, there's an easier method using RSA rescue.
You can grab boot.img for rooting.
mingkee said:
Actually, there's an easier method using RSA rescue.
You can grab boot.img for rooting.
Click to expand...
Click to collapse
I was using Rescue tool for this, may I please ask you how you were able to grab the boot.img? Thank you in advance!
Also, for those wondering if using the method above if OTAs will continue to update the answer is 100% YES confirmed.
TheLastSidekick said:
I was using Rescue tool for this, may I please ask you how you were able to grab the boot.img? Thank you in advance!
Also, for those wondering if using the method above if OTAs will continue to update the answer is 100% YES confirmed.
Click to expand...
Click to collapse
After rescue, check C:\Program Data\RSA\Download\romfiles\
Check Kiev folder