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?
Related
Right... so, I think I traced down why OTA doesn't work.
Namely, whenever I click on system update to search for update, it searches, but nothing happens.
Online I found that this is likely because a WW custom ROM was flashed... and so OTA doesn't work.
My phone is brand new (got it today actually), but 'stuck' on Android 5.0 (ugh).
So... I would like to ask for the recommended course of action so I can get either latest OTA, or just install a stable and up to date clean Android ROM (without all the Zen bloatware) that works.
Also, I'm relatively new with flashing this phone and there's tons of info on rooting, different CWM and TWRP's, etc.
Problem is, which ones to use?
How to determine if you're using the right one and avoid bricking the phone in the process?
My phone arrived with SuperSU... which would indicate it's been rooted (and I was able to install AdAway).
So bearing that in mind... what would you recommend?
Your phone should not be rooted when bought in a store. So it seems to be used before, and not correctly refurbished.
Anders
As there is no possibility to get evidence that you did not do that yourself, you can only hope to get a replacement from the vendor,or any warranty.
On the other side: the device is already rooted, so you can flash a 6.01 rom yourself.
Depending on the way the phone was rooted in the first place, OTA will not always work.
I did see an original rom surface recently. With that you can go original, Unrooted and locked, so the vendor will not be able to void your warranty claims.
Verstuurd vanaf mijn ASUS_Z00A met Tapatalk
Sorry for the late reply.
Was busy.
The phone was bought off Amazon UK, and no modifications to the device were done by me apart from installing my apps.
Trouble is, I don't know how to flash a new ROM onto this thing.
The forums are overflowing with information which is all over the place and it is extremely confusing.
Yes, I tried the search function and found some info, but it is all over the place.
I have to be able to figure out the original firmware apparently if I want to flash the CWM or TWRP... and in some cases, flashing TWRP can break the device it would seem (what's up with that?), and I cannot figure out the original firmware because the mobile was not delivered with one (a custom WW ROM was apparently flashed on top of I don't know which version), and I really do not know where to look for this.
So, I'm very confused.
There's too many threads to sift through and each seems to be giving its own unique information and a list of no no's which appear to contradict each other.
I could use some help in sorting through this 'mess' (well, 'mess' for me) so I could try at least flashing the original ROM and get OTA (for which I require concise instructions).
Also, something else seems to be happening... Asus Zentalk forums appear to refuse to load on my laptop for whatever reason.
Settings>About - will show you what rom you have.
I would recommend unlocking bootloader 1st as this seems to have helped me. If you have any recovery but stock or have a white splashscreen then this has already happened... I used the unofficial unlock tool to do this and thus my imei numbers stays off the "no warranty" list..
If you go to the pre-rooted rom thread you can download the newer stock roms. These also have the recovery, boot and droidboot.img files included with the .rar file of a system.img (unrar it of course)...
I believe it may also contain the flashtools, if not look at the CN to WW thread...
Using fastboot you can flash these onto your phone using commands -
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Make sure, if do this the commands are correct. Copy and paste can be your enemy because if you use the same command and just overwrite your boot/droidboot or recovery every time you flash, it may result in a brick...
Good luck and happy flashing...
I seem to get OTA's pushed now..
Tnx.
Now that I look back, it doesn't seem too complicated.
My bootloader seems to already be unlocked though.
One other thing... about flashing that system.img
I think I stumbled upon similar instructions before, however, I couldn't find system.img file (everything else was accounted for).
Also, does the the procedure for flashing new ROM's or possibly just OTA's require repetition of ALL those commands, or just some?
Oh and I was able to access the stock recovery (which the seller said he used to flash the custom WW rom). Could I use it to update OTA's manually? And would I need to first unroot the mobile?
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Iam uploading my special Bricked moto Z Loader Stock Oreo TWRP Moto G5+ for those who may need it, ciao!!!
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
SowilM said:
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
Click to expand...
Click to collapse
Happy to help brother!
So this will work for european users who did not break their persist?
Fabiuz99 said:
So this will work for european users who did not break their persist?
Click to expand...
Click to collapse
As far as i Know only for retail americas but you can try on your own and let us know
Battery performance is for fully happy and satisfied OVERWHELMING
will it work for indian version
will it work for indian version
---------- Post added at 06:48 PM ---------- Previous post was at 06:00 PM ----------
prnv1312 said:
will it work for indian version
Click to expand...
Click to collapse
thnks alot man
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this?
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this? june security update
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
I am friom mexico and my phone is working perfect...is your question anserred alwearu...can not go back to nouhat
will it work for indian version XT1686
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
Click to expand...
Click to collapse
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
nvrpayretail said:
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
Click to expand...
Click to collapse
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
LLegion said:
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
Click to expand...
Click to collapse
Sorry, I still a bit confused. The text I quoted says "bootloader stays MotoZ". If I install this update, as is, will my bootloader be MotoZ or remain Moto G5+?
Thanks...
I have the US version (retus), bootloader unlocked, nougat 7.0 with August patch (NPNS25. 137-93-18). Can I use this method safely? Thanks
I do not know what else to say...just flash as edpalined if phone breaks then unbrick it reading other tutos sorry pals but seems you are not reading enough
No risk no Win buddies
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
JohnSmith8786 said:
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
Click to expand...
Click to collapse
Do no flash from twrp but from runnimg the batch file oreo desde cero and it will flash the recobery as well to the oreo stock and thats it.buddie
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)?
Hello!
Been studying forums for a couple days but can't seem to get to a definitive answer.
Here's all I want - get android 9.0 on my phone - I don't care about saving data, unlocking bootloader or not, etc. It can be a custom ROM as long as it's stable. Ideally I'd like to put the stock RETAIL version on it. There are so many posts and many of them end of last year when PIE dropped but I can't find something that really summarizes for this model.
1. How to unlock bootloader and root if need be (https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792)
2. How to flash stock PIE on this phone
3. How to install custom recovery
(How does Magisk play into all this)
4. Stable custom ROM if needed?
If I'm missing something obvious, I'm ok taking the heat, but, if not and someone has this phone and has some answers, I'd be grateful!
Thanks.
----------------------------------------------------------------------
UPDATE:
1. I unlocked my bootloader following moto's website - easily googleable
2. Then I just flashed the retail OEM via fast boot using commands - i.e., I downloaded the retail for 9.0, extracted in in adb folder (which has fastboot), booted phone into fastboot mode and flashed it all manually. So far it's working fine. It complains at boot about unlocked bootloader and I can't get OTA updates. I know I can still root it via guide above.
I'll post any updates as I have them.
MrRedPants said:
Hello!
Been studying forums for a couple days but can't seem to get to a definitive answer.
Here's all I want - get android 9.0 on my phone - I don't care about saving data, unlocking bootloader or not, etc. It can be a custom ROM as long as it's stable. Ideally I'd like to put the stock RETAIL version on it. There are so many posts and many of them end of last year when PIE dropped but I can't find something that really summarizes for this model.
1. How to unlock bootloader and root if need be (xx)
2. How to flash stock PIE on this phone
3. How to install custom recovery
(How does Magisk play into all this)
4. Stable custom ROM if needed?
If I'm missing something obvious, I'm ok taking the heat, but, if not and someone has this phone and has some answers, I'd be grateful!
Thanks.
----------------------------------------------------------------------
UPDATE:
1. I unlocked my bootloader following moto's website - easily googleable
2. Then I just flashed the retail OEM via fast boot using commands - i.e., I downloaded the retail for 9.0, extracted in in adb folder (which has fastboot), booted phone into fastboot mode and flashed it all manually. So far it's working fine. It complains at boot about unlocked bootloader and I can't get OTA updates. I know I can still root it via guide above.
I'll post any updates as I have them.
Click to expand...
Click to collapse
Can you elaborate on what retail version you used?
I have the same (XT1710-01 albus_C RETUS...... which actually says "albus_retail/albus" in recovery mode) and currently on 8.0.0/OPSS27.76-12-28-20/19.
When I try to side load via adb "ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" I get an error saying: "footer is wrong", "signature verification failed" and "error 21".
Trying to load "Blur_Version.29.11.30.albus.retail.en.US" I got a version mismatch (albus vs albus_c).
You have to flash in via fastboot. Not in recovery.
Can someone please point me in the direction to Unlock Bootloader and Root the OnePlus 9 Pro T-Mobile Version? I had the Global US Unlocked OnePlus 8 Pro and it was simple. Thank you in advance!
How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com
Have u received token from tmo
Alright, my bootloader is unlocked now, but I'm not sure how to root at this point. My software version is 11.2.2.2.LE54CB. I can't find that last part (LE54CB) anywhere for download, so I'm not sure where to get my boot.img from. Anybody have some ideas?
Since there's no TWRP for this phone (yet), you have to get the boot.img file and use Magisk to directly patch it. I'm about to embark down this path, I got the T-Mobile version, also on 11.2.2.2 and I just got the bootloader unlocked. Now I need to root it.
glitchsys said:
Since there's no TWRP for this phone (yet), you have to get the boot.img file and use Magisk to directly patch it. I'm about to embark down this path, I got the T-Mobile version, also on 11.2.2.2 and I just got the bootloader unlocked. Now I need to root it.
Click to expand...
Click to collapse
Please let me know if you find a way. I'm super hesitant because of this other thread but I'm not willing to stop using my rooted OP7pro until my 9 is rooted.
I'm about to use https://forum.xda-developers.com/t/...ot-image-and-apply-root-to-the-phone.4263811/ djsubterrain's guide. Seems straight-forward.
1. I downloaded the Payload_Dumper program
2. I grabbed the official ROM from OnePlus's support site (https://www.oneplus.com/support/softwareupgrade/details?code=PM1617074857015) which is the same version my phone is already running.
3. I unzipped the OnePlus9ProOxygen_22.O.05_OTA_0050_all_2103242259_3611e0858f954e7d.zip file I got from OnePlus and there is a payload.bin file
I have to reboot out of linux and into my Windows partition in order to do the next part. But the Payload_Dumper program is supposed to extract a "boot.img" file from the payload.bin; I copy the boot.img file to my phone, into a temporary directory or whatever, and I use the Magisk application on my phone (which can be installed even if not rooted) to patch the boot.img file. I can then use fastboot to flash that image file. (Fastboot Boot rooted_boot.img) and after I reboot, I should, in theory, be rooted.
Since I didn't touch the stock recovery, I should also, in theory, be able to accept OTA updates pushed to my phone. Just normally an OTA update would "unroot" your phone, but guide has a "To retain root access after ROM/OTA update" section that I'm sure to try out next time an update is available. Worst case scenario though, the OTA update unroots me and I have to grab the new version from OnePlus's support site and go through the procedure again to extract the boot.img, patch it on the phone then flash it.
hmm. technically my phone is currently on "11.2.2.2.LE5ACB" and the one on OnePlus's support site is "11.2.2.2.LE15AA"
So there is a slight difference. Meh, should be ok. Worst case scenario I have to flash the entire "11.2.2.2.LE15AA "from OnePlus and I get T-Mobile De-Bloated.
Yeah, I had the exact same hesitation. I'm sorely curious to see how it goes for you. Because I have the OTA for the global rom, and I'm about to use the payload dumper. But if you're a step ahead of me, I'm happy to wait and see if it works for you.
jfsat said:
Yeah, I had the exact same hesitation. I'm sorely curious to see how it goes for you. Because I have the OTA for the global rom, and I'm about to use the payload dumper. But if you're a step ahead of me, I'm happy to wait and see if it works for you.
Click to expand...
Click to collapse
Happy to report it worked just fine. I was able to grab the boot.img from the "11.2.2.2.LE15AA" file on OnePlus's support site. I was able to use Magisk to patch the boot.img file. Then moment of truth..
"fastboot boot 11.2.2.2.LE15AA_patched_boot.img"
And my phone booted just fine. And it was now (temporarily) rooted. I was able to then go back into Magisk and direct-install root. Then reboot.
Magisk confirmed I'm still rooted.
So to all those curious, the boot.img from OnePlus Stock 11.2.2.2.LE15AA works fine on the T-Mobile 11.2.2.2.LE5ACB version.
I may look into using OOM or something to try and force-flash 11.2.2.2.LE5ACB onto my phone and completely De-T-Mobile this phone. I suspect I'll get OTA updates faster from OnePlus than I will from T-Mobile.
so I flashed to global coming from T-Mobile to global 11.2.2.2.
Everything went well. Until I system updated to 11.2.4.4. I realize now it didn't switch to full update and installed the incremental instead. After reboot I no longer have service.sim card is detected but again no service. Don't all the basics, so hopefully someone can help...
ryantf420 said:
so I flashed to global coming from T-Mobile to global 11.2.2.2.
Everything went well. Until I system updated to 11.2.4.4. I realize now it didn't switch to full update and installed the incremental instead. After reboot I no longer have service.sim card is detected but again no service. Don't all the basics, so hopefully someone can help...
Click to expand...
Click to collapse
How did you flash from T-Mobile's 11.2.2.2.LE5ACB over to the Global/USA 11.2.2.2.LE15AA ? The instructions say to put the zip file on the "sdcard" and then go to the update section and do a manual update. However T-Mobile conveniently removed that manual update option. So I was thinking I'd need to use msmtool or something to flash it.
Also you installed the AA version of the ROM, right? That's the U.S (not international) version, but it's generic, not T-Mobile modified. That's the one we should be flashing over our T-Mobile phones, converting them to the U.S Generic version, not the international version. AFAIK the U.S version isn't running 11.2.4.x yet, so not sure why you would get an OTA prompt about 11.2.4.x unless you'd flashed (again, how did you do this?) the international version and not the U.S version.
glitchsys said:
How did you flash from T-Mobile's 11.2.2.2.LE5ACB over to the Global/USA 11.2.2.2.LE15AA ? The instructions say to put the zip file on the "sdcard" and then go to the update section and do a manual update. However T-Mobile conveniently removed that manual update option. So I was thinking I'd need to use msmtool or something to flash it.
Also you installed the AA version of the ROM, right? That's the U.S (not international) version, but it's generic, not T-Mobile modified. That's the one we should be flashing over our T-Mobile phones, converting them to the U.S Generic version, not the international version. AFAIK the U.S version isn't running 11.2.4.x yet, so not sure why you would get an OTA prompt about 11.2.4.x unless you'd flashed (again, how did you do this?) the international version and not the U.S version.
Click to expand...
Click to collapse
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
ryantf420 said:
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
Click to expand...
Click to collapse
Using fastboot to flash the img files? There's liike 34 img files. (abl.img, aop.img, bluetooth.img, boot.img, cpucp.img, ..., ..., xbl.img, xbl_config.img). You flashed all 34?
If you're still having problems, I'm rooted and am on the stock 11.2.2.2.LE5ACB from T-Mobile. I can dd up certian partitions and provide them to you if you need. It may help you get back to stock.
glitchsys said:
Using fastboot to flash the img files? There's liike 34 img files. (abl.img, aop.img, bluetooth.img, boot.img, cpucp.img, ..., ..., xbl.img, xbl_config.img). You flashed all 34?
If you're still having problems, I'm rooted and am on the stock 11.2.2.2.LE5ACB from T-Mobile. I can dd up certian partitions and provide them to you if you need. It may help you get back to stock.
Click to expand...
Click to collapse
yes yes please that would help
Rooting is simple. Once your boot loader is unlocked head over to the thread on how to unlock the boot loader. He posted a patched boot IMG for T-Mobile. Flash it in fast boot restart open open magisk manager click direct install it will detect your boot IMG is patched it installs and reboot.
MurphSAN84 said:
How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com
Click to expand...
Click to collapse
ryantf420 said:
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
Click to expand...
Click to collapse
Flash your tmobile modem over global.
Where to get tmo modem img?
ryantf420 said:
Where to get tmo modem img?
Click to expand...
Click to collapse
You were supposed to back your's up prior to conversion...