Hello, XDA Community.
Since the release of the last major update, Android Pie 9.0/OneUI, as soon as we trigger an update to the bootloader while we are running unofficial binaries, like TWRP and custom ROMs, a message pops up on boot splash when we perform a simple reboot:
"Only official released binaries are allowed to be flashed"
This message shows up when we have KG State Prenormal (you can check KG State by entering download mode).
Before the Pie update, we were able to skip RMM State Prenormal by setting system date for 7 days before current date, then triggering a "check for system update", then setting back to current date. However, this doesn't work on the new Pie bootloader, which is why I am writing this guide, as I got caught many times into this damn state
The workaround I've found is downgrading bootloader from Pie to Oreo, but, as we know, after flashing Pie bootloader, we are not able to downgrade it to Oreo using Odin, however it's possible forcing the downgrade using Heimdall on Ubuntu.
REQUIREMENTS:
1. Ubuntu 16.04+
2. Heimdall (install it through Ubuntu terminal)
sudo apt install heimdall-flash
Click to expand...
Click to collapse
3. 'cm.bin' + 'modem.bin' + 'sboot.bin' files from Oreo firmware (you can get them by extracting BL and CP .tar files from the official stock firmware zip - download them on SamFirm, SamMobile or updato.com)
4. Internet connection (important - needed to download PIT file)
5. Attention while typing the commands
GUIDE:
1. Boot your phone into download mode (Power + Vol (-) + Bixby, then Vol (+) to enter download mode)
2. Place cm.bin + modem.bin + sboot.bin into your Ubuntu user folder (/home/username/) - check attachment
3. Open terminal (Ctrl + Alt + T)
4. Type the following command:
heimdall flash --CM cm.bin --RADIO modem.bin --BOOTLOADER sboot.bin
Click to expand...
Click to collapse
5. It should take about 5 seconds. After that, you're done and now you can flash unofficial binaries (e.g. TWRP), or even fully downgrade to Oreo, if you got fed up with Pie :laugh:
I hope this helps anybody. If this guide helped you, leave me a 'Thanks' and/or drop a comment.
Yours sincerely,
James
^ I flash TWRP normally through Odin, at this point KG state is "Checking"
Reboot to recovery, if you try to flash something at this point it fails since it can't mount data and system if I remember correctly, either you format them or change the filesystem for the partitions that can't be mounted to another format and then again to the original format(ext4). Now you can flash dm-verity disable and a custom ROM. This was my case. I don't know about the rmm state bypass you mentioned earlier. The only thing I know is that KG State is set to Checking, and stays like that.
i have all files but flasher i mean heimdall-suite-1.4.0-win32 its not working because me PC is win 7 64 Bit so what must i do need help please.
and i got this flash file G955FXXU4CRL3 and some device like Z3X, UMT, Chimera ETC.. can i use this device or u will give me any other tool?
THX.
I thought Heimdall didn't work for s8 and new firmware
then whats is the solution for RMM Status prenomal ?
talhagsm said:
i have all files but flasher i mean heimdall-suite-1.4.0-win32 its not working because me PC is win 7 64 Bit so what must i do need help please.
and i got this flash file G955FXXU4CRL3 and some device like Z3X, UMT, Chimera ETC.. can i use this device or u will give me any other tool?
THX.
Click to expand...
Click to collapse
"win32"? I have tested this solution on Ubuntu. I can't guarantee this works with Windows 7, sorry
talhagsm said:
then whats is the solution for RMM Status prenomal ?
Click to expand...
Click to collapse
On Oreo, I used to follow this guide:
https://forum.xda-developers.com/ga...iscussion/stoping-damn-rmm-prenormal-t3883519
However, this doesn't work with Pie/OneUI
TheMadScientist said:
I thought Heimdall didn't work for s8 and new firmware
Click to expand...
Click to collapse
Worked for me while downgrading DSBA to CSB1 bootloader
jameskunst said:
Worked for me while downgrading DSBA to CSB1 bootloader
Click to expand...
Click to collapse
Last I heard it hadn't been updated. I stand corrected
thank you
but how to remove KG State Prenormal if i want stay on pie
like i have file to remove rmm state and byebass
are there any way to byebass KG State or remove
Can I use this to get back to nougat?
Whats the best way to 'extract' the BL & CP files? If I use 7zip in windows or archive manager in linux it gives me cm.bin.lz4 & sboot.bin.lz4 etc. Do I rename these or use them as is?
kgr said:
Whats the best way to 'extract' the BL & CP files? If I use 7zip in windows or archive manager in linux it gives me cm.bin.lz4 & sboot.bin.lz4 etc. Do I rename these or use them as is?
Click to expand...
Click to collapse
I used linux dude, lz4 is another form of compression, like zip etc.
If you rename the files it'll fail.
In parrot linux, lz4 wasn't installed.
##so I downloded it first##
sudo apt-get install lz4
##then i used lz4 to decompress each of the files##
lz4 -d modem.bin.lz4
this will decompress and spit out the modem.bin file you're after.
---------- Post added at 11:11 AM ---------- Previous post was at 11:01 AM ----------
SM-G950F
SO I successfully flashed the required .bin files in linux to the phone as per the guide.
Booted back into windows to used odin and tried flashing twrp-3.2.3-2-dreamlte.img.tar
Still failed with "only official released binaries etc" error on the bootloader after Odin fails.
RMM prenormal still showing on the bootloader.
Is this normal and I have to wait another 7 days or should this have worked?
what is KG gate?
there's no need to go through all that, just reflash BL,CP & Home from Oreo Stock rom.Then you can reflash TWRP after that,atleast thats what i did on G965N Pie and it worked
flash this using odin
done
peeyemv said:
flash this using odin
done
Click to expand...
Click to collapse
On AP tab?
LU SONEVESSO said:
On AP tab?
Click to expand...
Click to collapse
If your going to flash it then yes use AP section in Odin.
I threw my S8 Fury can not do anything oem unlock no longer appears now I have an S10 .... XD The Life is Strange
Psydt0n3 said:
I used linux dude, lz4 is another form of compression, like zip etc.
If you rename the files it'll fail.
In parrot linux, lz4 wasn't installed.
##so I downloded it first##
sudo apt-get install lz4
##then i used lz4 to decompress each of the files##
lz4 -d modem.bin.lz4
this will decompress and spit out the modem.bin file you're after.
---------- Post added at 11:11 AM ---------- Previous post was at 11:01 AM ----------
SM-G950F
SO I successfully flashed the required .bin files in linux to the phone as per the guide.
Booted back into windows to used odin and tried flashing twrp-3.2.3-2-dreamlte.img.tar
Still failed with "only official released binaries etc" error on the bootloader after Odin fails.
RMM prenormal still showing on the bootloader.
Is this normal and I have to wait another 7 days or should this have worked?
Click to expand...
Click to collapse
yeah, the same here with s8+, done with linux and went back to windows, flashed twrp and fails, i don't know what to do now
the only different thing was the phone state was custom, but still rmm was lock
i even flashed stock oreo but nothing
and i must say, the linux thing is a pain in the ass, that procedure is not for everyone,im a soft engineer and it took me 2H
peeyemv said:
flash this using odin
done
Click to expand...
Click to collapse
doesn't work, get "SECURE CHECK FAIL : (BOOTLOADER)" in download mode and state is still Prenormal
Related
I've noticed a bunch of folks posting their problem after encounters with this demonic screen:
[UPLOAD MODE]
Subsystem Crashed: MODEM
------------------------------------
DDR Vendor: Samsung
SOC_HW_REVISION: 2.1
MODEM INFO
err type: Fatal
Task: ml1_mgr
File: trm_rfm_path_srch.cpp
line: 1916
Invalid combination for LTE VCO selection. Num Rx: 3, Num Tx:
last_ns : 0x6d
Generating summary...
>General info
>DDR info
>DCVS Info
>RPM
>TrustZone
>Hypervisor
>APSS
>Modem
Done!
So I decided to start a separate thread to share what worked to get my Sprint S8 out of this hellish bootloop.
1.) Start off at a place where you get good reception and that has a STRONG Wi-Fi signal (I brought a laptop to Starbucks). It seemed to me the modem crash screen occurred most often in places where I had a weak signal.
2.) Start downloading your stock firmware from either (A)here or (B)herr. Either way, download Odin v3.12.7 found in hyperlink B.
3.) Follow the directions as described in the PWND thread https://forum.xda-developers.com/galaxy-s8/development/samsung-galaxy-s8-root-snapdragon-t3659305 using 7zip to extract your EXT4 file which will complete the rooting process.
4.) Now with the same options selected described in the procedure section, use the Odin 3.12.7 to flash the CSC and CP from the stock firmware you downloaded and be PATIENT. I took me about 20 minutes of anxiety, worrying that it had frozen up until "file analysis" finally popped up on the screen and Odin started to do its thing.
Hope this helps. It worked for me on Sprint. Peace.
Addendum: Read next post for additional info.
Curtex said:
I have been seeing a bunch of folks posting their problem with seeing this demonic screen:
[UPLOAD MODE]
Subsystem Crashed: MODEM
------------------------------------
DDR Vendor: Samsung
SOC_HW_REVISION: 2.1
MODEM INFO
err type: Fatal
Task: ml1_mgr
File: trm_rfm_path_srch.cpp
line: 1916
Invalid combination for LTE VCO selection. Num Rx: 3, Num Tx:
last_ns : 0x6d
Generating summary...
>General info
>DDR info
>DCVS Info
>RPM
>TrustZone
>Hypervisor
>APSS
>Modem
Done!
Hope this helps. It worked for me on Sprint. Peace.
Click to expand...
Click to collapse
Couple things:
Flashing system or the sampwnd zip will delete all your data. Plan accordingly.
Also, if you are having modem crashes you apparently should also flash NON_HLOS.bin file in the BL archive. Apparently it's part of the lte modem software and you want those all to be thr same version, no more than one version older or a newer than sysyem, and as up to date as possible.
Thanks for posting this
All you have to do to fix this is flash the cp and csc file for the correct software version. Example when I rooted and updated to AQGL I got that error. I flashed the cp and csc for AQGL and that fixed it. Just use normal Odin.
wgorham said:
All you have to do to fix this is flash the cp and csc file for the correct software version. Example when I rooted and updated to AQGL I got that error. I flashed the cp and csc for AQGL and that fixed it. Just use normal Odin.
Click to expand...
Click to collapse
The people who are having modem crashes sometimes need matching lte drivers which is the NON_HLOS.bin file. It appears to differ greatly based upon drive itself and what version of firmware is installed on each part
partcyborg said:
The people who are having modem crashes sometimes need matching lte drivers which is the NON_HLOS.bin file. It appears to differ greatly based upon drive itself and what version of firmware is installed on each part
Click to expand...
Click to collapse
From a working root environment per the sampwnd instructions can we simply flash cp, CSC and non_hlos from BL file using old Odin?
Will data be lost?
Yes
I'm having the modem crash also. Anyone have a verified link to xfinity mobile S8 firmware? I was led to believe that CCT was the carrier code for them but when I used files from CCT firmware during root process, I was greeted by Cricket Mobile bloatware and modem crashes.
Curtex said:
Yes
Click to expand...
Click to collapse
That was a "Yes" to data being lost if those files are Odin'd?
wgorham said:
All you have to do to fix this is flash the cp and csc file for the correct software version. Example when I rooted and updated to AQGL I got that error. I flashed the cp and csc for AQGL and that fixed it. Just use normal Odin.
Click to expand...
Click to collapse
Did it erase data from the phone?
Edit: Yes it did, just like it said in the OP My bad.
partcyborg said:
Couple things:
Flashing system or the sampwnd zip will delete all your data. Plan accordingly.
Also, if you are having modem crashes you apparently should also flash NON_HLOS.bin file in the BL archive. Apparently it's part of the lte modem software and you want those all to be thr same version, no more than one version older or a newer than sysyem, and as up to date as possible.
Thanks for posting this
Click to expand...
Click to collapse
Sorry for updating this 30+ day old thread but I am stuck with a 'Subsystem Crashed: Modem!" error every time I leave home and don't have a strong Wifi signal which requires several reboots to get the phone back in a working state and I haven't found a better suggested resolution online than the one found in this thread which ...as is... isn't working for me. So I seek additional info....
So how exactly does one flash NON_HLOS.bin file from the BL archive? I extracted the NON-HLOS.bin file from the BL archive and followed the instructions for creating a custom tar.md5 file based on instructions from this and this posts.
With that newly created custom NON-HLOS tar.md5 file, I tried using odin to flash it along with the CP and CSC files referenced in the OP. I also successfully used odin to flash just the CP & CSC files by themselves and then tried to flash the custom NON-HLOS.bin tar.md5 file by itself. In both cases, I get "FAIL! SHA256 is invalid" and the custom NON-HLOS bin file is not flashed.
So how does one flash just the NON-HLOS.bin file in Odin? Do I just flash the entire BL file instead of just the NON-HLOS.bin file? If so then you end up using the BL, CP & CSC files from the original Stock Galaxy S8 firmware. In that case why even use the S8 odin images that came with SamPWND? You could have essentially used the stock s8 images for my carrier. [sprint]. No?
serendrewpity said:
Sorry for updating this 30+ day old thread but I am stuck with a 'Subsystem Crashed: Modem!" error every time I leave home and don't have a strong Wifi signal which requires several reboots to get the phone back in a working state and I haven't found a better suggested resolution online than the one found in this thread which ...as is... isn't working for me. So I seek additional info....
So how exactly does one flash NON_HLOS.bin file from the BL archive? I extracted the NON-HLOS.bin file from the BL archive and followed the instructions for creating a custom tar.md5 file based on instructions from this and this posts.
With that newly created custom NON-HLOS tar.md5 file, I tried using odin to flash it along with the CP and CSC files referenced in the OP. I also successfully used odin to flash just the CP & CSC files by themselves and then tried to flash the custom NON-HLOS.bin tar.md5 file by itself. In both cases, I get "FAIL! SHA256 is invalid" and the custom NON-HLOS bin file is not flashed.
So how does one flash just the NON-HLOS.bin file in Odin? Do I just flash the entire BL file instead of just the NON-HLOS.bin file? If so then you end up using the BL, CP & CSC files from the original Stock Galaxy S8 firmware. In that case why even use the S8 odin images that came with SamPWND? You could have essentially used the stock s8 images for my carrier. [sprint]. No?
Click to expand...
Click to collapse
You need to use comsy Odin the regular one won't work.
Also don't bother with the .md5 part. Just make tars with ustar and flash those direct.
The farther apart your individual ROMs are, the more likely it is that you will have some kind of issue, and sometimes even one apart is a bad idea.
As for the ROMs that are for root. Not all the files are from stock, some are from the "factory "combination" rom that is given somehow to service companies and is regularly sold online to the public. Whether or not all files come from the combination rom or not, at least abl.elf, devcfg.mbn, boot.img and recovery.img have to be from a factory/combo image or you will not get root and if you change system it will no longer boot. I personality source every subsequent file needed (minus system and userdata) from the latest stock image released, but that is just how I do it.
G950U right? Are you rooted? What version/carrier are you on?
I ask because I probably have files uploaded already that may fix whatever is wrong, or at least point out what already is
I think my issues are resolved. I'm posting this in the hope it will help someone else but also for myself so I remember what I did in the future if a new root process is not found. I apologize in advance for the length.
So, I did try the Prince Comsey odin. I also tried Odin 3.07, 3.10.6, 3.12.3 & 3.12.7. The instructions for creating a custom TAR Ball for flashing involved using a version of odin that had a 'Phone' button that was on older versions of Odin but on newer versions including PrinceComsey that button was renamed. No version was successful though. Or so I thought...
In the end, the second half [Part 2] of the SamPWND instructions call for you to use Flashfire to flash the stock system.img.ext4 and SamPWND_G950U. In one of my attempts, I unsuccessfully tried to get Flashfire to flash the custom NON-HLOS.tar.md5 file along with the other two files. I say it was unsuccessful but it is really hard to tell what's going on while Flashfire is doing its thing because the screen goes really dark and while you can see something happening, you can't actually read anything.
Anyway, in the process, I made a decision that I would have Flashfire NOT reboot back into Android [bootloader] but reboot into 'Download' mode immediately after flashing system.img.ext4 & SamPWND_G950U. In download mode I then used PrinceComsey Odin [which was still open from Part 1 of SamPWND instructions] and flashed the CP & CSC archives mentioned in the OP of this thread. I tried this a couple of times. Even though the flashing of NON-HLOS failed each time [or maybe it didn't; unclear], I noticed that after flashing the CP and CSC files with PrinceComsey the random reboots had stopped. I couldn't seem to recreate the 'Subsystem Crashed: Modem!' error and I was really trying.
So to make sure I understood what was going on, I started from scratch. I used Full Odin 3.12.7 to flash Samsung Galaxy S8 Original Stock firmware. Made sure that stock firmware and the phone's hardware were still functioning as expected. It was. I then followed the SamPWND instructions to the letter. Including using only PrinceComsey Odin. The only thing I changed was the very last step I had Flashfire reboot the phone into Download mode (without booting into Android) and then used PrinceComsey Odin to flash the CP & CSC archives as mentioned in the OP of this thread. This seems to have worked for me. I have manually rebooted serveral times. I have gone out to various stores and different WiFi environments that I know caused the Subsystem Crashed: Modem! Error.
I have been running for about 18hrs without any errors at all. I will test some more tomorrow but I have a good feeling about all this.
In the end, with my phone [Sprint Galaxy S8 (SM-G950U) - Snapdragon variant], I never had to use the NON-HLOS.bin file or the custom TAR I created. I only needed to have Flashfire avoid booting into Android and instead reboot into Download Mode as its final step and then use PrinceComsey Odin to flash the CP & CSC archives mentioned in the OP.
Note: Be Careful of other versions of the Samsung Galaxy S8 Root (Snapdragon) Instructions you may find on the internet. I ran into a couple that were wrong and caused me major headaches. Only use the Samsung Galaxy S8 Root (Snapdragon) instructions found on XDA-Developers. :victory: :fingers-crossed:
---------- Post added at 05:58 AM ---------- Previous post was at 05:44 AM ----------
By the way I used SamFirm_v0.3.6 to obtain the latest Samsung Galaxy S8 Sprint firmware directly from Samsung servers using the instructions located at the link below... The CP, CSC and System.Img.Ext4 files were obtained from the same download so there would not have been a difference in the versions
"How to download Samsung Galaxy Full Firmware Files Directly from Samsung Servers"
(I can't post external links, but google the above string of text and look for the site called, androidsage.com)
i need some help I have the exact same phone and with sprint I am rooted and I no longer have access to my phone other then the downloading part it is in a infinite boot to modem crash please help me
About all of this
I just rebooted into download mode and flashed twrp but didn't boot into recovery. Odin brought my phone back to life.
I got first modem crash today! Note 8 with samFAIL. =8 assertion : carrier data failed lol!
sam is a big time failure, should have recalled all the note 8's for not allowing 'carrier' brand direct purchased unlocked bootloaders after all it is the purchaser's phone after all, wow imagine buying a car and having it engine turn off if you got a custom dash cover or aftermarket led headlights!! Away with the same bot failures!!!! Haahahahahahahahahahahahahahahahahahahah. HA!
serendrewpity said:
Sorry for updating this 30+ day old thread but I am stuck with a 'Subsystem Crashed: Modem!" error every time I leave home and don't have a strong Wifi signal which requires several reboots to get the phone back in a working state and I haven't found a better suggested resolution online than the one found in this thread which ...as is... isn't working for me. So I seek additional info....
So how exactly does one flash NON_HLOS.bin file from the BL archive? I extracted the NON-HLOS.bin file from the BL archive and followed the instructions for creating a custom tar.md5 file based on instructions from this and this posts.
With that newly created custom NON-HLOS tar.md5 file, I tried using odin to flash it along with the CP and CSC files referenced in the OP. I also successfully used odin to flash just the CP & CSC files by themselves and then tried to flash the custom NON-HLOS.bin tar.md5 file by itself. In both cases, I get "FAIL! SHA256 is invalid" and the custom NON-HLOS bin file is not flashed.
So how does one flash just the NON-HLOS.bin file in Odin? Do I just flash the entire BL file instead of just the NON-HLOS.bin file? If so then you end up using the BL, CP & CSC files from the original Stock Galaxy S8 firmware. In that case why even use the S8 odin images that came with SamPWND? You could have essentially used the stock s8 images for my carrier. [sprint]. No?
Click to expand...
Click to collapse
I use chimera tool, you can actually check the specific files on the firmware that you want to flash and uncheck the ones you want left out
How to Flash Factory Firmware
Warning
You will loose all your data. Make sure to backup. You are doing this at your own risk. Neither me nor xda is responsible for any bricked devices.
Youtube Video :- https://www.youtube.com/watch?v=eCGB-yxC09w
Text Guide
HOW TO INSTALL STOCK ROM IN MOTO X4:
Download Moto X4 Stock Firmware from below (in factory firmwares section).
Extract factory firmware to a folder.
Install Motorola Driver and ADB Fastboot Driver on your PC.
Copy all contents of ADB fastboot folder and paste it in factory firmware folder.
Download flash-all.sh(Mac & Linux) or flash-all.bat (Windows)
Place flash-all.sh/flash-all.bat file in factory firmware folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt/terminal window, navigate to factory firmware folder.
Windows
Code:
fastboot devices
Mac & Linux
Code:
./fastboot devices
Make sure device is detected in fastboot mode.
Windows
Code:
flash-all.bat
Mac & Linux
Code:
./flash-all.sh
Once everything is flashed.
Windows
Code:
fastboot reboot
Mac & Linux
Code:
./fastboot reboot
Motorola Bootloader Unlock - https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Downloads
Motorola drivers for Windows & Mac :- https://support.motorola.com/us/en/drivers
Setup ADB and fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
flash-all.sh (Linux + Mac) - https://mega.nz/#!OYFiRKZC!2CjMLxpoEAqpFyB_q1Q1FncC9a1oNofh9Hjm99PwiGo
flash-all.bat (Windows) - https://mega.nz/#!DF1XwSjC!tkHhb9H9-1piNr1AbKaPJK_yLuv4rpIxw1AWicD1I94
Factory Firmwares
https://mirrors.lolinet.com/firmware/moto/payton/official/
US Retail Android 9.0 Pie :- https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Android One Android 9.0 Pie :- https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Twitter Account to Follow for latest firmware uploads
https://twitter.com/motofirmware123
you da man!
Your tutorials are very helpful .Thanks
When will you have the 28.2 firmware with the May update? Thats what version mine was on before I bricked it.
jpolster2005 said:
When will you have the 28.2 firmware with the May update? Thats what version mine was on before I bricked it.
Click to expand...
Click to collapse
you should be able to flash the latest firmware listed above as long as you can boot into fastboot.
but my locked boot loader says preflash validation failed
jpolster2005 said:
but my locked boot loader says preflash validation failed
Click to expand...
Click to collapse
unlock the bootloader.
I can't, because OEM UNLOCKING is set to off
Thanks for the simplified guide. Worked great, I was able to relock the bootloader and accept an OTA with no problem. Only issue is the device doesn't pass safety net - signature validation error, and when I boot up I get the device has been modified pop up.
michael28056 said:
Thanks for the simplified guide. Worked great, I was able to relock the bootloader and accept an OTA with no problem. Only issue is the device doesn't pass safety net - signature validation error, and when I boot up I get the device has been modified pop up.
Click to expand...
Click to collapse
rooted?
No -unrooted, stock rom from this thread, locked bootloader.
michael28056 said:
No -unrooted, stock rom from this thread, locked bootloader.
Click to expand...
Click to collapse
well, i never stay on stock long enough to check that ..sorry cant help with that.
guys PLEASE help me I have a $300 paperweight here. Best Buy wouldn't take it back so I NEED to get it fixed. I was already on the newest OTA when I bricked my phone on a locked boot loader, and when I try to flash 28.1 thru Fastboot, it says validation failed. is there anyone out there who has access to the Fastboot flashable 28.2? I need my phone back!
jpolster2005 said:
guys PLEASE help me I have a $300 paperweight here. Best Buy wouldn't take it back so I NEED to get it fixed. I was already on the newest OTA when I bricked my phone on a locked boot loader, and when I try to flash 28.1 thru Fastboot, it says validation failed. is there anyone out there who has access to the Fastboot flashable 28.2? I need my phone back!
Click to expand...
Click to collapse
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Neffy27 said:
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Click to expand...
Click to collapse
same peeps thread
aw man... well, I meant to post specifically to the last post in the thread but was on the mobile app.
:good::good: Just wanted to say thank you for this post, the links to the image files and the flash-all BAT file. This really saved my butt with a Project Fi Moto X4, which I had rooted using Magisk before checking on the availability of factory firmware images from Motorola. (of course there are not any available from Motorola ) The phone was continuously prompting for an OTA update, which would fail. I first tried the Magisk uninstaller, which ran successfully in TWRP, but the OTA update was still failing. After some digging on Google I found your post and used the Project Fi image to flash the phone, it worked perfectly! There was an OTA update available after flashing (The May 2018 security patches, "28.2") and it installed successfully. I love the Android community, the XDA community, and folks like yourself who take the time to write posts like this. Seriously, thank you!
g3m1n1 said:
I love the Android community, the XDA community, and folks like yourself who take the time to write posts like this. Seriously, thank you!
Click to expand...
Click to collapse
glad to be of help :highfive:
g3m1n1 said:
There was an OTA update available after flashing (The May 2018 security patches, "28.2") and it installed successfully.
Click to expand...
Click to collapse
Hello!
I understand you have Android One version. If that's the case, anyone catching the URL to OTA for the Android One 28.2 update? I've been looking for it for days, and the OTA link generator is not working (at least with the data I'm providing which should be correct).
Neffy27 said:
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Click to expand...
Click to collapse
how long before we see one. I have been relegated to using an iPhone 6 32GB! I really NEEEEEEED my phone to not be bricked. I tried to do the blank flash and boot off sd card and all that to no avail. none of it worked. meow I am getting so frustrated.
Hi all, thanks in advance for reading me.
I have this model:
S8+ (SM-G955FD) with the last firmware from sammobile G955FXXU4CRJ5
When I flashed that firmware with ODIN I wanted to root, so this is what I did:
1. Changed the date of the date of the phone and went to "update firmware" and then reset to get OEM unlocked
2. Went to download mode and flashed succesfully TWRP.
3. In TWRP I formated data (yes) and rebooted into recovery
4. Flashed the following files: a) Magisk, b) No verify 6.0, c) RMM state bypass Mesa, d)samsung anti-root removal 4.1
5. Rebooted into system
Click to expand...
Click to collapse
After doing that, everything seems to be OK... I can re-config my phone and Magisk Manager is installed. But when I went to Developer options I can't see "OEM unlock" activated. So, when I rebooted I got the "only official released binaries are allowed to be flashed" error.
I made the procedure several times. Is that related to the "October security patch update"? I think the error is due to a failure in RMM state bypass flashing, although the flashing procedure says "OK. Done".
Anyone have the same issue? do you guys know how to fix it?
josegon30 said:
Hi all, thanks in advance for reading me.
I have this model:
S8+ (SM-G955FD) with the last firmware from sammobile G955FXXU4CRJ5
When I flashed that firmware with ODIN I wanted to root, so this is what I did:
After doing that, everything seems to be OK... I can re-config my phone and Magisk Manager is installed. But when I went to Developer options I can't see "OEM unlock" activated. So, when I rebooted I got the "only official released binaries are allowed to be flashed" error.
I made the procedure several times. Is that related to the "October security patch update"? I think the error is due to a failure in RMM state bypass flashing, although the flashing procedure says "OK. Done".
Anyone have the same issue? do you guys know how to fix it?
Click to expand...
Click to collapse
More than likely RMM state zip didn't work are you using the version 2 zip and did you allow modifications in twrp before flashing zip files.
@spawnlives; thanks for your repply, I guess that was part of the solution. What I did was to flash a custom kernel plus RMM state bypass v2. I read a custom kernel could fix my problem.
Now I have my phone rooted and with OEM unlock enlabed.
josegon30 said:
@spawnlives; thanks for your repply, I guess that was part of the solution. What I did was to flash a custom kernel plus RMM state bypass v2. I read a custom kernel could fix my problem.
Now I have my phone rooted and with OEM unlock enlabed.
Click to expand...
Click to collapse
what kernel did you use? i have the same issue. i cant reboot on unlocking as i get the dreaded only official binary....
Johnny™ said:
what kernel did you use? i have the same issue. i cant reboot on unlocking as i get the dreaded only official binary....
Click to expand...
Click to collapse
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).
thanks im really struggling, im on the 11th try, every time is just gives me only official bineries.... , ive tried several methods, all root nicely but wont reboot.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
i cant find the v2 its coming up as 4k where v1 is 100k?
josegon30 said:
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).
Click to expand...
Click to collapse
let me buy you a beer! got it working thanks, the V2 did the trick. I used your kernel as well just in case. no more nasty red message!
Johnny™ said:
let me buy you a beer! got it working thanks, the V2 did the trick. I used your kernel as well just in case. no more nasty red message!
Click to expand...
Click to collapse
:good: I´m glad it worked.
josegon30 said:
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).
Click to expand...
Click to collapse
Okay, that's great and all but I can't even do the first step because every time I'm in Download mode and try to flash TWRP with Odin, it says "Only official released binaries are allowed to be flashed (RECOVERY). I have triggered Knox security but I can't undo it now, so I can fix the RMM state with the bypasser because I can't even flash TWRP. It was suggested to change the date to another one, prior to the security patches, but that didn't work. Sad times...
nasko7 said:
Okay, that's great and all but I can't even do the first step because every time I'm in Download mode and try to flash TWRP with Odin, it says "Only official released binaries are allowed to be flashed (RECOVERY). I have triggered Knox security but I can't undo it now, so I can fix the RMM state with the bypasser because I can't even flash TWRP. It was suggested to change the date to another one, prior to the security patches, but that didn't work. Sad times...
Click to expand...
Click to collapse
Depending on .android version, you will need to have the following coditions to be able to flash non signed samsung firmware eg: twrp,root, custom roms etc.
In system - OEM unlocked
Download mode -
RMM status - normal ( or disappeared )
KG status - checking
Otherwise you will get errors
Root Samsung Galaxy A52 SM-A525F Android 11 Official - AUC4 Firmware. TWRP Recovery for Galaxy A52 Android 11 does not available yet when I posted this rooting guide. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Rooting Instructions ( Don't make mistake )
Make sure the bootloader are unlocked, OEM unlock option is grey out
Patch boot.img then Pack it to magisk_patched.tar. If you don't want to do it by your self, you can download it from link below
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN
Insert magisk_patched.tar in AP, then click start. The phone will rebooting to ANDROID RECOVERY MODE
in ANDROID RECOVERY, Select Factory data reset and press power key to confirm
select 'Factory data reset' again and confirm
Setup the phone
Connect to Internet
Install and Open Magisk App, it will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Download
magisk_patched
Telegram: https://t.me/SamsunGalaxyA52
Watch This Video Tutorial
Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.
Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?
<deleted>
VonSparq said:
Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?
Click to expand...
Click to collapse
On qcom devices, not really. Even on exynos devices after removing that you still need to physically press the power button or if you don't wanna even do that you have to w8 bout 10 to 15 extra seconds..
hansxl said:
Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.
Click to expand...
Click to collapse
Okay, solved. Flashed latest firmware (AUC5) and patched boot.img with Magisk. Fingerprints works now and no reboots so far
Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?
Rerel14 said:
Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?
Click to expand...
Click to collapse
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com
hansxl said:
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?
Rerel14 said:
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?
Click to expand...
Click to collapse
Yes, it's more or less the procedure. But I would just download the latest magisk (22.1) from
Magisk v22.1 brings an improved log writer, resetprop bootloop fixes, and much more
The latest stable update for Magisk (v22.1) has been released with tons of bug fixes and feature improvements. Read on to know more!
www.xda-developers.com
the UI is a bit different from the one in your video
My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?
Rerel14 said:
My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?
Click to expand...
Click to collapse
bootloader unlocked
hansxl said:
bootloader unlocked
Click to expand...
Click to collapse
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?
Rerel14 said:
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?
Click to expand...
Click to collapse
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also
hansxl said:
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also
Click to expand...
Click to collapse
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?
I think I found one :
Rerel14 said:
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?
Click to expand...
Click to collapse
How To Unlock Samsung Galaxy A52 Bootloader - NaldoTech
In this tutorial, you will learn how to unlock the bootloader on your Samsung Galaxy A52. A bootloader is the piece of code that runs before the operating
www.naldotech.com
don't forget to backup your data. I think after unlocking bootloader your phone will return to factory settings
I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?
I installed Magisk from an other source and eventually I succeeded to get root !
Huge thanks Hansxl for your help and patience. Really appreciated it.
Last question : if I update the firmware I'll need to make the full procedure described above again ?
Rerel14 said:
I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?
Click to expand...
Click to collapse
deinstall magisk and install magisk again
Previous android version: Android 11
Previous base-band version: A125USQU2BUG5
company: wireless cricket
In the context of flashing with the new firmware I used :
- Odin version: 3 v3.14
- Firmware used: Samfw.com_SM-A125U_USC_A125USQU2BUL1_fac_2
The error is related to the vbmeta check. Did you used a sock firmware or you have patched it with magisk? Btw i reccomend to use frija to download the firmware.
If i can suggest I would make this steps:
1) download latest firmware with frija
2) Flash the stock and see if it work
Otherwise if this not help:
1) download latest firmware with frija
2) patch the whole ap and not only boot.img with magisk
3) open odin and flash it using the patched ap on the ap slot
If nothing above works, I think you can try this... not sure it will work. Replace inside the ap the vbmeta.img with the attached one that have the disabled verified boot.
Oneplus# said:
The error is related to the vbmeta check. Did you used a sock firmware or you have patched it with magisk? Btw i reccomend to use frija to download the firmware.
If i can suggest I would make this steps:
1) download latest firmware with frija
2) Flash the stock and see if it work
Otherwise if this not help:
1) download latest firmware with frija
2) patch the whole ap and not only boot.img with magisk
3) open odin and flash it using the patched ap on the ap slot
If nothing above works, I think you can try this... not sure it will work. Replace inside the ap the vbmeta.img with the attached one that have the disabled verified boot.
Click to expand...
Click to collapse
Thanks for the reply.ok
1- The firmware is stock.
2- I didn't patch any of the files I got ( any recommended guide on how to proceed>?)
3- I' so new at this
But anyways, yesterday I kind of sorted out the stuck by adding BL file, and CSC file along the AP file to ODIN, the phone restarted ok but found out it hasn't been unlocked from the carrier yet, so I guess that by judging what u just said, there are few thing I need a guide to
- Flashing the stock
- Patching the AP file
Ps Frija opens up when executed, but it closes in less than 1 second. (Pc 's OS: win 10 enterprise 64 bits)
leonardo07746 said:
Thanks for the reply.ok
1- The firmware is stock.
2- I didn't patch any of the files I got ( any recommended guide on how to proceed>?)
3- I' so new at this
But anyways, yesterday I kind of sorted out the stuck by adding BL file, and CSC file along the AP file to ODIN, the phone restarted ok but found out it hasn't been unlocked from the carrier yet, so I guess that by judging what u just said, there are few thing I need a guide to
- Flashing the stock
- Patching the AP file
Ps Frija opens up when executed, but it closes in less than 1 second. (Pc 's OS: win 10 enterprise 64 bits)
Click to expand...
Click to collapse
When you flash with Odin you always need to use all the files provided on the stock firmware ap, bl, csc and cp. If u are upgrading you can use the home_csc instead of the csc file that will let you keep your data.
Are you sure you have installed the framework that Frija need?
For the ap patching, is only meant if you want root your phone, flashing the whole ap instead of the boot.img only will let you fix the vbmeta checks too.
Install the magisk app.
Open it and tap Install, it will ask for a file to patch, chose the ap file of the stock firmware you downloaded.
Final step, flash ap patched and the others (bl,csc,cp).
When you say unlocked by the carrier what do you mean? You have any sort of sim block? Or you only want remove your carrier apps and configs?
Oneplus# said:
When you flash with Odin you always need to use all the files provided on the stock firmware ap, bl, csc and cp. If u are upgrading you can use the home_csc instead of the csc file that will let you keep your data.
Are you sure you have installed the framework that Frija need?
For the ap patching, is only meant if you want root your phone, flashing the whole ap instead of the boot.img only will let you fix the vbmeta checks too.
Install the magisk app.
Open it and tap Install, it will ask for a file to patch, chose the ap file of the stock firmware you downloaded.
Final step, flash ap patched and the others (bl,csc,cp).
When you say unlocked by the carrier what do you mean? You have any sort of sim block? Or you only want remove your carrier apps and configs?
Click to expand...
Click to collapse
thanks for all that
- it s sim block
Oneplus# said:
When you flash with Odin you always need to use all the files provided on the stock firmware ap, bl, csc and cp. If u are upgrading you can use the home_csc instead of the csc file that will let you keep your data.
Are you sure you have installed the framework that Frija need?
For the ap patching, is only meant if you want root your phone, flashing the whole ap instead of the boot.img only will let you fix the vbmeta checks too.
Install the magisk app.
Open it and tap Install, it will ask for a file to patch, chose the ap file of the stock firmware you downloaded.
Final step, flash ap patched and the others (bl,csc,cp).
When you say unlocked by the carrier what do you mean? You have any sort of sim block? Or you only want remove your carrier apps and configs?
Click to expand...
Click to collapse
Mannn thanks!
I rooted my tab 5Se a long time ago and deleted the firmware files except the AP.
I got stuck on the same screen today when I re-locked my bootloader after a stock AP-only flash
Then I saw your reply here and got the rest of the files flashed and it worked and booted
And for those who are reading if you don't have a SIM on your tablet you don't need a CP that's why you won't find it in your firmware zip file
Cheerios