Related
On 551 Z00A or AD the official downgrade version of LP WW-52.20.40.196 firmware from any M stock firmware - via sd card
https://www.youtube.com/watch?v=_1T6SMJiUSg&feature=youtu.be
Success -- Downgrade of MM to LP works with the downgrade firmware above , works via update from sd in MM recovery ------- Marvelous
Stays on` updating IFWI ` for approx 8 mins but after that - bingo !
It also erases data after which it didnt updating in same OS
Also , i set it up -- after a reboot , it detected .134 and ..144 and .184 MM update packages and now also should detect .223 latest firmware if on ext SD if written like mentioned and shown in the video !
The above LP downgrade version is detected in .223 latest M firmware after a reboot.
Some pics
Seeing a lot of people bricking their devices downgrading to LP from M .
There is now no need for all these bricks when we can downgrade via M recovery to LP via ext sd card .
If you are on a stock rom MM bl and rooted TWRP ..you just need to flash stock boot.img and recovery for the MM build you are on . Reboot to stock M recovery. Follow above procedure.
If you are on M bl custom Rom and rooted TWRP but have no stock M back-up , flash back boot.img and recovery for.134 , sideload .134 stock. Then downgrade
That above applies to 551 Z00A .
Merry Xmas to all at XDA --Still seeing people looking to downgrade from M to LP even after posting this method above via ext SD card - WOW
So , my present to you is a video of the above process
Say NO to anymore bricks Say NO to ever having to use xFSTK downloader again
This makes our phones fully , changeable forwards and backwards via SD card (for good)
The process will go from .184 M to .196 LP on the 551 Z00AD or Z00A
If you Have MM bl custom rom - use giovix`s Modder tool to `return to stock option` flash boot.img - flash recovery option in Modder . Follow process.
Video Coming Soon ...........
Ps, i assume the process will be exactly the same for Z008 from the latest Stock M to LP but using the relevant downgrade version(whatever that is) from official ASUS site for Z008
I dont have a Z008 so if anyone wishes to attempt it and give me your results here , that would be great for others
pps, i decided to do the video due to either people dont trust this method or people are extremely shy about hitting the thanks button . Whichever -- help others
Yup, using the Asus files to downgrade from MM to LP bricked my brother's phone. I've tried a few methods with xFSTK to fix it but nothing has worked so far. Looks like the phone will be recycled Oh well, he seems pretty happy with his Samsung Note 3 for now
audit13 said:
Yup, using the Asus files to downgrade from MM to LP bricked my brother's phone. I've tried a few methods with xFSTK to fix it but nothing has worked so far. Looks like the phone will be recycled Oh well, he seems pretty happy with his Samsung Note 3 for now
Click to expand...
Click to collapse
Yup , even tho i can unbrick in xFSTK in less time it takes to downgrade (everytime success btw) -- pay attention to the video... on the edited files i show in file manager
timbernot said:
Yup , even tho i can unbrick in xFSTK in less time it takes to downgrade (everytime success btw) -- pay attention to the video... on the edited files i show in file manager
Click to expand...
Click to collapse
Thanks, I'll give it another go when I have a chance.
audit13 said:
Thanks, I'll give it another go when I have a chance.
Click to expand...
Click to collapse
You need to have a working device to downgrade via SD :good:
Okay, I was able to restore stock MM to the phone which is what it has before it bricked. Problem now is that I can't verify the Google account I tried both of my google accounts without success. I'll have to find some other method.
audit13 said:
Okay, I was able to restore stock MM to the phone which is what it has before it bricked. Problem now is that I can't verify the Google account I tried both of my google accounts without success. I'll have to find some other method.
Click to expand...
Click to collapse
But you was bricked a moment ago - no comprehendi ?:laugh:
If you used xFSTK you wouldnt need to downgrade , you would be in LP already.
If done on another device try later , maybe a reboot :good:
I was bricked and was able to iFSTK to get into the bootloader. I then used the Asus Flash tool to flash an MM raw file to at least get the phone booted. I was happy until I was stuck at the set up screen with no way to verify the google account.
Now its time to party vid coming soon .
All the very best wishes to each and all
audit13 said:
I was bricked and was able to iFSTK to get into the bootloader. I then used the Asus Flash tool to flash an MM raw file to at least get the phone booted. I was happy until I was stuck at the set up screen with no way to verify the google account.
Click to expand...
Click to collapse
MM raw file Hey , please share here ?
If there even is a MM raw file that is
Flash 5.0 raw for 5.0 then you wont need to downgrade btw
And this is nothing to do with downgrading via SD card btw - off topic
I believe I used the MM ww raw file from here: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
audit13 said:
I believe I used the MM ww raw file from here: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
Do you know what you are doing ?
Saying , posting ?
Do you have a zenfone ?
Let me know which one of my posts is confusing and I'll try to clarify.
On 551 Z00A or AD the official downgrade version of LP WW-52.20.40.196 firmware from any M stock firmware - via sd card
https://www.youtube.com/watch?v=_1T6SMJiUSg&feature=youtu.be
OP updated
Merry Xmas to all at XDA --Still seeing people looking to downgrade from M to LP even after posting this method above via ext SD card - WOW
So , my present to you is a video of the above process
Say NO to anymore bricks Say NO to ever having to use xFSTK downloader again
This makes our phones fully , changeable forwards and backwards via SD card (for good)
The process will go from .184 M to .196 LP on the 551 Z00AD or Z00A
If you Have MM bl custom rom - use giovix`s Modder tool to `return to stock option` flash boot.img - flash recovery option in Modder . Follow process.
Video Coming Soon ...........
Ps, i assume the process will be exactly the same for Z008 from the latest Stock M to LP but using the relevant downgrade version(whatever that is) from official ASUS site for Z008
I dont have a Z008 so if anyone wishes to attempt it and give me your results here , that would be great for others
pps, i decided to do the video due to either people dont trust this method or people are extremely shy about hitting the thanks button . Whichever -- help others
audit13 said:
Let me know which one of my posts is confusing and I'll try to clarify.
Click to expand...
Click to collapse
Hi , I understand where you went wrong , you flash raw again in boot loader ,where it stays on ' RESULT=OK ' a couple of mins into flash in on screen cmds , you close flash tools . Force close it...restart flash tools .put all stuff in again ...then press vol+ once.
Leave connected to PC from first part flash all the way through closing flash tools and restarting flash ..do not touch fone apart from vol + before second flash.
Serial will be corrected and you will boot into system.
There is a vid of this exact process in my unbrick thread.
Enjoy
Ps , I never let the first flash finish , due to knowing above process to correct serial..
So if you run into probs , you may need to re flash in xfstk again.
timbernot said:
Hi , I understand where you went wrong , you flash raw again in boot loader ,where it stays on ' RESULT=OK ' a couple of mins into flash in on screen cmds , you close flash tools . Force close it...restart flash tools .put all stuff in again ...then press vol+ once.
Leave connected to PC from first part flash all the way through closing flash tools and restarting flash ..do not touch fone apart from vol + before second flash.
Serial will be corrected and you will boot into system.
There is a vid of this exact process in my unbrick thread.
Enjoy
Ps , I never let the first flash finish , due to knowing above process to correct serial..
So if you run into probs , you may need to re flash in xfstk again.
Click to expand...
Click to collapse
THANK YOU, THANK YOU, THANK YOU! It worked.
This is what I did to cause the loss of serial #:
used the sd card method to downgrade from MM based on instructions from another forum (i.e. not XDA);
phone got stuck at the erasing portion of the process and stayed there for about 45 minutes so I powered off the phone;
used xFSTK to successfully flash the bootloader
successfully flashed MM raw file with Asus Flash Tool;
tried to downgrade to LP again and bricked again;
used SFSTK again but serial # was now abcde... in bootloader so I used Asus Flash Tool again. AFT never finished flashing a ROMand the phone was stuck on the bootloader screen with "Result: okay" so I just shut down the phone and left it off until I saw your post this morning.
Edit:
I set up the phone ran software update option from settings but the Android Version is 5.0? Also, when I boot into fastboot, I see the serial # as abcde... but I can get the proper serial # by pressing the volume up and down keys a few times. Lastly, my SD card is not seen in recovery but is seen in the ROM. When I boot to recovery from the bootloader, I see this:
Android system recovery <3e>
LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756_user
E:file path/tmp/last_install
E:file path /cache
E:file path /tmp
Finding update package
Opening update package
E: file path:/sdcard/MOFD_SDUPDATE.ZIP
E: failed to map file
SD installation aborted.
E: Installation failed with status 1
I'm not too worried as these things are cosmetic. The important thing is the phone now works
Just to clear things up.
You never bricked your device using the method in the OP regarding downgrading via sd card. So not to scare people off .
Mofd sdupdate method is for adb sideload using a cable.
In the video it shows how files must be written when downloaded for each stock firmware in file manager in the first few mins. To be recognised from ext sd
Lastly , 2.20 in firmware or raw = LP
4.21 = M which doesn't have a raw yet unless I missed it coming about
Hello.
I've just discovered that I can't switch my phone on because it says "custom recovery block by frp lock". I know there are numerous threads on this forum and other websites describing this problem and ways to solve it, included mantaining data.
Every method requires the download of the same version firmware you had installed on your phone. The problem is that I cannot really remember if I kept my Galaxy A3 2016 to 5.1 or I upgraded it to 6.0. Obviously I cannot check it by phone since I cannot even boot, nor via adb since it isn't able to recognise the phone in the download mode.
So firstly: is there a way to retrieve the firware code, or at least, the android version of my phone? Can adb recognise the phone in downlaod mode?
Secondly. According to this link in xda, that user was able to solve the problem using some kind of firmware image (QB1), which seems to be an upgrade. Is that method valid for other samsung phones? For my A3, should I follow the same steps with the correct firmware version?
Thanks in advance
Frank-95 said:
Hello.
I've just discovered that I can't switch my phone on because it says "custom recovery block by frp lock". I know there are numerous threads on this forum and other websites describing this problem and ways to solve it, included mantaining data.
Every method requires the download of the same version firmware you had installed on your phone. The problem is that I cannot really remember if I kept my Galaxy A3 2016 to 5.1 or I upgraded it to 6.0. Obviously I cannot check it by phone since I cannot even boot, nor via adb since it isn't able to recognise the phone in the download mode.
So firstly: is there a way to retrieve the firware code, or at least, the android version of my phone? Can adb recognise the phone in downlaod mode?
Secondly. According to this link in xda, that user was able to solve the problem using some kind of firmware image (QB1), which seems to be an upgrade. Is that method valid for other samsung phones? For my A3, should I follow the same steps with the correct firmware version?
Thanks in advance
Click to expand...
Click to collapse
1.install KIES
2.press tools
3.press frimware upgrade and installation
4.device id is your device model and serial number can be found under battery
5. allow kies to download and install the image
Video link for more help : https://www.youtube.com/watch?v=LqoX7wNhotk
good luck
Edit: please remember to enable OEM unlock in developer options next time
Kies cannot link to the device in the downlaod mode unfortunetely
Frank-95 said:
Kies cannot link to the device in the downlaod mode unfortunetely
Click to expand...
Click to collapse
try using smartswitch and see if it detects it
-are drivers installed
-does the pc recognize the phone ?
So, I had already tried with Smartswitch, but it says device not supported and does not link at all.
Moreover yes, the computer could read the phone before the frp lock, and even now, odin can detect it in download mode.
Kies just loads for some minutes and then says "unable to link to the device"
EDIT: no sorry kies raises "the device does not respond"
ok we need to flash using odin , i assume you can't access recovery but if you tried and it worked, look at the top of the screen it must show a code like
<your A3 model> followed by <your country> followed by <frimware date>
If you couldnt, we can use an updated version for your model , please provide us with the model if u can.
I can only acces to odin mode. Via that, I have the following text:
Product name is: SM-A310F
Current binary: Custom (it was rooted)
System status: Custom
FRP LOCK: ON
Secure Download: Enabled
Knox Warranty Void: 1
RP SWREV: B:2 K:0 S:0
I am sure that the phone had Vodafone pre-installed applications, and looking at mrcrab.net there exist these possible stock firmware:
Android 5
Android 5
Android 6
Android 6
I only fear that if I mistaken the version I will obtain a wipe of my data, which are not vital but are important to me
Actually there is no way to avoid the reset as we don't know anything about the PDA version, install the drivers type in google "USB Samsung drivers"
It must show developer.Samsung.com/....
I'm on phone so I can't provide it as a link, install the drivers and try again, else we will get the latest version
I already have samsung usb drivers, and odin can succesfully detect the phone in download mode; Kies cannot, though
Anyway, if you open one of the links I posted, isn't the PDA shown in the line:
OS Version : A310FXXU1AOLE (chosen one as example)
In that website there is every stock firmware by model, android version, and mobile operator. I know two out of three, and those 4 links are the 4 possible choices regarding android version. If I picked the right one, would I avoid the data reset, wouldn't I?
EDIT: What, if I did how it is explained here with the latest version? I mean download android 6 last upgrade, extract it, rename .tar.md5 in .tar and flah it with odin? Would it be any risk of loosing data?
Hello,
.MD5 lets odin checksum the rom loaded to it to make sure it's not corrupted, however if you are sure of two main things:
that the frimware you are flashing isn't a downgrade as downgrading flashs a old bootloader which gets you in some kind of troubles possibly a brick, to avoid that, grab the latest version
and the second thing you must make sure of is that the file isn't anyway corrupted.
if you think it's all ok, then you can proceed as of i tried it once and it saved a device.
Okay, I'm sure now that my android version was 6.0.1 because I read that 5.1 didn't have single app permissions manager, and I definetely remember that I had it.
According to this page, I have three possible choices.
1) I think the right version is the oldest one. In case I mistaked, would I risk a brick even if the major version is the same?
2) Also, if I mistaked, do I risk a data loss even though the major version is the same?
Thank you (we're almost there)
Frank-95 said:
Okay, I'm sure now that my android version was 6.0.1 because I read that 5.1 didn't have single app permissions manager, and I definetely remember that I had it.
According to this page, I have three possible choices.
1) I think the right version is the oldest one. In case I mistaked, would I risk a brick even if the major version is the same?
2) Also, if I mistaked, do I risk a data loss even though the major version is the same?
Thank you (we're almost there)
Click to expand...
Click to collapse
The build number must be the same regarding the android version, so to keep the files it must be the same as the one in the phone, else a wipe will be performed.
The problem is that you want your data, that maybe lost if we don't have the exact same build.
Just grab the latest marshmallow or nougat -, but the data would be lost then.
Do a hard reset in case something went wrong.
I was able to unlock the phone a mantain the data! Thanks
I have a special problem with an old Samsung Galaxy A3 2016 SM-A310F (Android 7.0 Nougat)
on which the correct combined file cannot be obtained
I have tried perhaps all FRP removal options without success
A310FXXS5CSH3
Recently I rooted my S9 and installed Lineage OS but I didnt like it and decided to swap back to the stock OS. I used Frija to get the .tar.md5 files for Odin but once I select all the files and hit start the log in Odin loads up to system.img then stops and I get the SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7. BINARY: 6 error on my phone. Any idea on how to fix this? I'd really appreciate some help as I'm going to be travelling soon and I need my phone for it and I'd prefer not to use Lineage OS. Thanks in advance.
Do you have an At&t branded phone? SM-G960U?
I am having a very similar problem. A customer came in and was having issues with device. I told them to back up, wipe, and update device. That didn't work so I tried a full flash with ODIN. Now I can't get the phone to boot at all and it says, "Secure Check Fail : Modem" and "Unauthorized software visit nearest AT&T blah, blah,..)
I think it is because AT&T has pushed out the latest update(OCT. 18th), but the Odin files are not out yet. According to:
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1253489?make=Samsung&model=SamsungG965U
G960USQS7CSI5 is the latest FW. If you google it, there are only four results.
Yep, the problem was the phone was on the latest FW. Newer firmware was just uploaded a few days ago.
I flashed:
G960USQU7CSJ2_G960UOYN7CSJ2_CHA
and now I'm booting again.
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."
ma777 said:
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."
Click to expand...
Click to collapse
^^^^ this ^^^^
the Odin error is telling you that youre trying to flash a revision of the bootloader than was last installed on the phone. to to sammobile.com/fimrwares and get the one with the correct bootloader for your specific phone and flash that.
also download the firmware with the frija tool or samfirm. trust me, its literallt 5x faster than a direct download from the site. The 5 min it takes to get samfirm up and running is worth it, believe me on that.
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!
Youdoofus said:
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!
Click to expand...
Click to collapse
Getting no help was meant I hadn't Posted asking Questions, I read everything ya'll put up and I was able to do it on my own without continuing to ask, so Yeah I did get help here but not by asking only reading what is available
downgrade samsung sm-g570m
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??
pol1345 said:
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??
Click to expand...
Click to collapse
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.
TheMadScientist said:
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.
Click to expand...
Click to collapse
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
Like 99.9%. That's what that error is. The bootloader is blocking downgrade
pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
yes, if you get a firmware version matching the one last installed on your device, itll go right thru and boot just fine. Goodlock is finally working on all modules for A10 as well. Maybe we will see more development occur with this shutdown going on. Let us know if you run into any trouble, the error you were getting is totally resolvable!
at the end I give up on it..! my internet 2 slow 4 go downloading & trying rom after rom.! i am from venezuela.
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
I have S20+ running Android 11 with U7 Binary. I tried downgrading to Androi 10 which has Binary U5. Now I have downloaded the Binary U5 file. But in some video, he is telling that you should download the Binary File with the same number as it is currently installed in your phone, which in my case is U7. So? Am I supposed to download U7 Combination Binary file and flash it in order to downgrade to Android 10
OR
Should I flash the U5 Combination File and flash the Android 10 AP, CSC, BL, HOME ???
Someone has Combination file to G960F with bootloader SF (Version 15)?
Hi all,
It's a couple of days I am trying to root my note10+ however even looking very simple I can't go over the bootloader.
Following the istruction I have:
downloaded firmware accordingly
patched with magisk
unlocked bootloader
unlocked developer mode and toggled OEM unlocking option
When using odin I get the error on phone "blocked by OEM lock" even if it is ulocked on the mobile, I've tried everything!
Any idea please?
Attaching photo as the only doubt I have is on the bootloader screen where I can read on top "odin by xxx"
Thank you in advance
which instructions did you follow?
can you please give me instructions on my smn975u
slinger198569 said:
can you please give me instructions on my smn975u
Click to expand...
Click to collapse
It's not nice to hijack someone else thread.
https://forum.xda-developers.com/t/...sh-twrp-snapdragon-only.4195891/post-84012015
w41ru5 said:
which instructions did you follow?
Click to expand...
Click to collapse
Hi w41ru5, thank you for your reply
I've been searching around, at the end I could manage to unlock properly the bootloader and root with a custom ROM my mobile, harder than expected to find proper files for this model
got stuck bootload, on twrp, some bootloop, stuck after magisks update, but finally is ok now
did you find a solution? I manage to root tricking the lz4 files which is the new type of extension in Android and for this you can not root in a normal way. I followed this guide
Fix Oreo Firmware Installation Issue in Odin for Samsung Devices - DroidViews
Android Oreo has finally made its way to Samsung's latest S series flagships, the Galaxy S8 and S8+. The Oreo update brings with it the usual Android Oreo features such as Picture-in-Picture, redesigned Settings app, etc. It also brings with it Samsung Experience 9.0 which is but a fancier name…
www.droidviews.com
After having the 4 stock files modified without lz4 you must flash them with Odin.
After you take the modified AP file and patch it with Magisk.
Then you flash again stock using the patched AP file and the rest of modified files but you must not select autoreboot in Odin. When the flashing is done you must exit download mode and imediatelly enter in Recovery mod but better use this guide
How to Root Samsung Galaxy Note 10 and Note 10+
In this tutorial, we will show you how to unlock the bootloader and then root Samsung Galaxy Note 10/Note 10+ using Magisk. This guide supports Exynos variants of the Galaxy Note 10 and Note 10+ with…
www.thecustomdroid.com
This methods do not work for me now. I am in the latest R update 07 and it seems dont work. I am serching how to root my phone now...
I have a WW version of ROG Phone 6. I have had it since mid-July.
Previously, I had ROG 2 but it died on me unexpectedly and I switched to Pixel 6, which was very underwhelming. I pre-ordered ROG 6 as soon as it became available.
I have not seen a concise guide to rooting ROG 6. I think it should be the same as ROG 2 but just in case, I read guide to rooting ROG 5.
Are the steps to rooting ROG 6 the same as ROG 5?
Asus ROG phone 5: unlock bootloader and root guide
Asus rog phone 5 guide note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas. bootloader unlock: ! note that unlocking...
forum.xda-developers.com
Thank you!
I sure hope so. . . I cant find much material online but I'm going to try to just run this tool from asus https://rog.asus.com/phones/rog-phone-6-model/helpdesk_download/ and then flash magisk via recovery.
Sorry extract boot.img move it to phone, patch it with magisk and then run
Code:
fastboot flash boot magisk_patched.img
and that should do it. Although you may want/need to flash the official files first by running the flashall_AFT.cmd file.
Found this all on https://forum.xda-developers.com/t/...e-6-can-be-used-for-cn-ww-converting.4474383/ and https://forum.xda-developers.com/t/...-guide-you-should-read.4474241/#post-87255303
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
leathan said:
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
Click to expand...
Click to collapse
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
ausaras said:
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
Click to expand...
Click to collapse
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
leathan said:
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
Click to expand...
Click to collapse
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
You should be done. I just fully updated and then rooted and set up my phone.
The firmware flash would have been to swap over to CN or WW. If you do that then yes you would re-factory reset + re flash stock boot.img. Then afterwards repeat the boot.img patch to obtain root + repeat setting up your safteynetfix + any other magisk modules.
ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
Hi, I am sorry the last answer I gave you was just wrong. I totally forgot when we root we wont get automatic OTA updates. Which for me is a really good thing anyway. But to get the OTA updates we need to download the firmware files from ASUS website. The same place we downloaded the unlock app but its under firmware. Download every WW firmware and put them one by one in order from oldest to newest on the /sdcard and boot up and it will detect an update. I'm pretty sure we cannot just skip to the latest update like we can with custom rom otas so I am going in order.
I left root, and when done updating will again patch the boot.img and flash it over.
Over the weekend I helped a guy root and set up safteynet and if it helps others I might just write up a tutorial.
Cheers!
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strage (or are least I think It strage):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
i need fastboot driver for win 64
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
can anyone provide the patched boot image to have root? Tried looking and asking in other areas but no luck. Or is there a way to patch a bot image that contains root already?