(Moderators, please make this post a sticky, and i will keep it updated of any changes or issues that might come up in future builds, thanks)
To clarify things.... I am the dude who figured out how to side-step from model to model... I have went from 2419 (android 12 .11), to 2413 (android 13), Down to 2415 (android 12 .08), then 2417 (android 12.10), back up to 2415 (android 13), down to 2415 (android 12 .05), 2417 (android 12 .08) and finally a FULL sidestep 2417 (12 .08) to 2415 (12.08) which the latter is supposed to be impossible, with downgrade package, yet i am sitting here and i have done it!
Spoiler: Credits for discovery ===>
!!! Credit for discovering the Downgrade Packages, and Information about OPPO/Oneplus Bootloader restrictions goes to, Maamdroid , and EtherealRemnant !... Without their most important input, i would not have had the courage, and knowledge of exactly what i was going up against, in attempting a region change on a BL/Carrier locked device. They were the geniuses who helped me derive this method, i was just the guinea pig willing to go Dr. Frankenstein on my T-Mobile locked, handicapped device. !!!!
Spoiler: ***DISCLAIMER***
**" I TAKE NO RESPONSIBILITY FOR BRICKS, BOOTLOOPS, SYSTEM CRASHES, INSTABILITY.... WORLD FAMINE, 6G MUTANT INVASION, NANO BOTS ENTERING YOUR FANNY, TRUMP RE-ELECTION, CIVIL WAR, YOU FORGETTING TO DO THAT THING YOU WERE SUPPOSED TO DO EARLIER.... 72 HOUR KARDASHIAN MARATHONS, GLOBAL WARMING, YO MAMA SLAPPING YOU, OR ANY OTHER SIDE EFFECT FROM ATTEMPTING THESE IMAGINARY WORDS THAT YOU THINK YOU ARE READING, YET YOU ARENT BECAUSE READING HASNT BEEN INVENTED YET IN YOUR TIMELINE B.C.5182 , AND THE FACT THAT YOU ARE A MEAT POPSICLE... PROCEED ONLY IF YOU FEEL FULLY CONFIDENT IN THE ANALYSIS YOU ARE ABOUT TO IMAGINE READING , AND THEN REPEAT AFTER ME: ***
" I AM FULLY AWARE OF THE RISKS INVOLVED WITH MAKING MODIFICATIONS OR EXPLOITING FUNCTIONS THAT WERE NOT INTENDED TO BE USED IN THE METHOD I AM ABOUT TO USE THEM FOR. AND IF A ZOMBIE APOCALYPSE ERUPTS DUE TO ANY MISTAKE I MADE FLASHING THE FILES LISTED HERE, I WILL NOT EVER ... EVER... EVEN CONSIDER ANY WORDS READ FROM HERE, AS HAVING ANY THING BUT A TRULY POSITIVE EFFECT UPON MY LIFE! " .... PROCEED!
Spoiler: Only open if you acknowledge the risk!
The ONLY requirements of the downgrade packages on the 10T, is that you CANNOT downgrade to a build version that is lower than your current one IF you are attempting to region hop while staying on the same version of android.... (ie. you cannot go from A12 .10, to A12 .08... but you can go from 2415 A12 .05 to 2413 A12 .08) Got that?
One other important thing is that in the zip file that contains the payload.bin, there is an additional file named payload_properties.txt. You need to open that file in a text editor, and look for the line about the "Update_Engine_Check_Disable".... by default it is set to 0 which makes Local Updater check to see if the models match in some files. A mismatch will just cancel your update. Local updater is KEY to doing any Region Swaps, especially with a locked bootloader. This is because Local Updater does NOT perform any of the flashing itself... that whole progress bar is your phone verifying the contents of the payload.bin to make sure that all files in the manifests are present, and compatible with your device... it actually KEEPS YOU FROM BRICKING your phone because of a mismatched file/ or bad flash. If Local Updater detects ANYTHING that is not interchangeable, it will crash during the verification, your phone will reboot, and start normally as if you never attempted an update.
Local updater is also not capable (afaik) of applying ANY changes to the Bootloader, or boot partition. As well it seems limited in its ability to even fully access some userdata files. All of my developer options were in exactly the same state that they were prior to each flash. The only deviation of that , was in DOWNGRADING from A13 to A12... but every upgrade, no matter which model fw used seemed to have done the 'Data, system, bin, etc, var, lib, and kernel, plus a few others' , but the truly secure partitions such as 'aboot, xbl, and system-priv' + deep memory blocks werent touched i believe.
The END result of each region swap will be your device FULLY IDENTIFYING as the model for that region.. (ex. 2419 will now show as 2415 if Global, 2413 if India, or 2417 if North America)
This will change EVERY TIME you flash a different region, and Local Updater will block you from flashing if it detects a lower build, EXCEPT for the 2415 Downgrade Package. So ALWAYS use that as a base if you want to go to another region. <ie. to go from 2413 to 2417, i recommend first flashing the 2415 downgrade, which will put you on A.08 build, then you can update to any region you want, even the Android 13 builds.... but if you want to go to a different region and back to 12, you must use that 2415 Downgrade or Local updater will stop you. The 2415 is a signed official rollback package direct from oneplus, so it allows you to downgrade from pretty much any version.
***** KEY FACT ***** This ONLY applies to OTA upgrade and downgrade packages that come in a single zip file that contains 3 items. Payload.bin Payload_properties.txt and Meta_Inf folder ... If you unzip the fw that you dl, and it contains anything other than those 3 that i just named, you either have a Fastboot package, a Full system package, or a MODIFIED package which you should NOT interact with unless you completely trust the source it was dl from. I have seen some NAAAAASTY scripts, coded in Russian, Vietnamese, Chinese, and Wingdings (yes that weird windows font!) ... and they are becoming VERY GOOD at moving to an app directory, changing a files name and replacing that file with WHATEVER IT IS, but renamed to a something common to the location! So by doing that, those files evade most onboard detection, if they have modified code, because that file name was whitelisted . Stick with the signed rollback package, and OTA either direct from the Oneplus community websire, or from the "gsmmafia" site, as both are packages sourced direct from the manufacturer and contain no modified code!
***How to get the OTA files for the region you want to switch to... follow instructions EXACTLY and you wont have an error.***
You have to use the "OXYGEN UPDATER" app from the google play store... When you first open it , it will tell you that your device is on the current version... ignore that, and you have to open the settings menu for it, and go enable ADVANCED MODE.... This will allow you to go back and CHOOSE what device you are supposedly using. (kinda a cheap override command)... doing this will let you choose the 2417 (NA) model. **Now once again HIGHLY IMPORTANT that you are doing this ONLY after flashing the Downgrade/Rollback so that you will be on 2415 A.08 build... cuz then when you select the 2417 model, it will show an update available for 2417 A.12 build. and also the Android 13 Beta. Pick whichever you want, and click download... NOW once downloaded DO NOT HIT THE REBOOT BUTTON.... this will attempt to flash it via normal methods... instead jump into ADB , go to Shell, and head to /sdcard/ and start looking for the folder where it just downloaded the update. It places it sometimes in the main /Sdcard/ folder, and other times in the /Sdcard/Android/Data/<app name>/ folder.... you will know it when u see it. Find it and copy it to your computer and then you have the official OTA saved. After that, make sure it is moved to the /Sdcard/ folder and use "local updater". Will ask you to confirm, click Ok, and it should start the verification and flash process.
Be advised it will APPEAR like its frozen or no progress for like 4 minutes, then it will slowly start moving. Once it gets to 99, it will appear stuck again... just be patient and about 5 min later it will complete. Total flash time is arouund 20-25 min.
DO NOT FORGET TO UNPACK THE ZIP FILE
EDIT THE PAYLOAD_PROPERTIES.TXT
CHANGE THE "0" TO A "1" ON THE ENGINE_UPDATE_CHECK_DISABLE =
SAVE THE CHANGES, AND RE - ZIP THE CONTENTS
THEN COPY THIS ZIP FILE TO YOUR /SDCARD/ FOLDER!
if you dont it will fail!
Links to Downgrader Packages used can be found HERE
EDIT: I went ahead and linked the main files necessary for this whole process here for ease, and my peace of mind. Now I know that you have all re required tools. Enjoy!
2015 Rollback Package, courtesy of EtherealRemnant
Oxygen Updater (for current OTA of region)
Local Update apk (official)
... And to clarify again.. This does NOT unlock the bootloader, nor does it change our T-Mobile Devices ability to unlock via conventional methods. (still working on that)
Quick expl. In our T-Mobile models, Oppo worked directly with the carrier and enabled a feature new to Android 12 and future builds, which allows the FACTORY bootloader to be wrapped up and hidden from the FastBoot binary... And move a "copy" of the bootloader into "userspace" partitions. These partitions are called AFTER the initial secure boot has passed, and therefore disabled normal FastBoot operations. Instead in userspace, "FastbootD" is enabled, and for all who know of it, that is not much more than a glorified recovery. All OEM, and Flashing commands are rendered inoperable, because bootloader operations cannot be modified once the system is up, or in "default mode". This proves my theory of Local updater not modifying partitions. It uses the currently identified locations of the files that need to be updated to the new region on just changes them where they are already located. For "FastBoot mode" to work properly, it would need to UNWRAP the original bootloader, and disable the "Userspace Init" instructions, which cannot be done on a already running OS.
If somehow you are LUCKY and after your region change, you are able to run 'adb reboot bootloader' ... And your device starts in 'Fastboot Mode' and does not kick you out, then you should be fully able to run the Unlock commands to unlock your bootloader, without need to flash anything else. The chances of that are very minute... But I have seen stranger things with this device. Tho most likely, that command will reboot you right back into normal android immediately .
I have this problem with bootloader and I don't know how to solve it on ghasedak24 website.
mrwilliamm said:
I have this problem with bootloader and I don't know how to solve it on ghasedak24 website.
Click to expand...
Click to collapse
what you mean??? i dont have any info pertaining to the real bootloader for this, the Tmobile model. Ours ships with this Oppo/Oneplus Hybrid crap what makes Fastboot Mode inaccessible. It doesnt respond to the keypress method of getting to it... and adb reboot bootloader attempts to boot into it, but the phone reboots exactly .5 seconds aftter it shows the screen. The only thing you can access is FASTBOOTD which give you literally ZERO functions that we need for the bootloader. OEM, BOOT, Flashing, Flash all fail in FASTBOOTD. Other than that man i honestly would suggest you speak with MAAMDROID because they seem to know more about the OPPO loader. MY knowledge of what is taking place came from me interrogating a Oneplus employee for about 4 straight hours when he broke and told me everything.
NOW I WILL STATE ONE DEVELOPMENT.... The GSMMAFIA user who is responsible for all the MSM firmwares that are now available for the 10T, is 100% legit. You can download the entire UPDATED Full Flash FW including the MSM TOOL... for free.... but without a login/pass authenticated, they are not much help to us. BUT... i have confirmed that the guy is a REAL Oneplus Employee, and he uses official software to remote connect and flash the MSM Unbrick firmware to your device. His charge is $45 ... but he is HIGHLY sensitive to ppl with Fiddler, or any capture programs running on your computer, so much to the point that he checks your app tray and task manager when he remote connects, and if he even sees one of these kinda programs, you lose your $45 and he disconnects. Just head to the GSM Mafia page for the 10T firmware and you can get his WhatsAPP number to contact him and setup.
Me personally, I have WAY MORE than just Fiddler, Wireshark, Proxifier, WinpCap, and many more programs that i know will spook him, and i am not gonna wipe my pc for something that is not guaranteed to do what i want. BUT if you have a bootloader error, you have nothing to lose, and flashing a full, Unbrick fw thru MSM, like he does just MIGHT format all partitions first and therefore erase the instruction init filee that locks up fastboot. Literally EVERY model except the 2419 has normal Fastboot, and an unlockable BL....
Just a thought!
I did not find any over the air or upgrade packages for the 2417 model from the above link. How did you get back to the 2417 model? And what APK did you use because some of them did not work on my device. It would just say verification failed. I thought I tried to go from a global.08 to the over the air .10 2417 model but it didn't work for me it just said verification failed. I did try to go sideways from the global .10 to the North American .10 but it also did a verification failed. maybe I'll try again. I got the over-the-air 2417 model update from the OnePlus updater app.
tdamocles said:
I did not find any over the air or upgrade packages for the 2417 model. How did you get back to the 2417 model? And what APK did you use because some of them did not work on my device. It would just say verification failed. I thought I tried to go from a global.08 to the over the air .10 2417 model but it didn't work for me it just said verification failed. I did try to go sideways from the global .10 to the North American .10 but it also did a verification failed. maybe I'll try again
Click to expand...
Click to collapse
You have to use the "OXYGEN UPDATER" app from the google play store... When you first open it , it will tell you that your device is on the current version... ignore that, and you have to open the settings menu for it, and go enable ADVANCED MODE.... This will allow you to go back and CHOOSE what device you are supposedly using. (kinda a cheap override command)... doing this will let you choose the 2417 (NA) model. **Now once again HIGHLY IMPORTANT that you are doing this ONLY after flashing the Downgrade/Rollback so that you will be on 2415 A.08 build... cuz then when you select the 2417 model, it will show an update available for 2417 A.12 build. and also the Android 13 Beta. Pick whichever you want, and click download... NOW once downloaded DO NOT HIT THE REBOOT BUTTON.... this will attempt to flash it via normal methods... instead jump into ADB , go to Shell, and head to /sdcard/ and start looking for the folder where it just downloaded the update. It places it sometimes in the main /Sdcard/ folder, and other times in the /Sdcard/Android/Data/<app name>/ folder.... you will know it when u see it. Find it and copy it to your computer and then you have the official OTA saved. After that, make sure it is moved to the /Sdcard/ folder and use "local updater". Will ask you to confirm, click Ok, and it should start the verification and flash process.
Be advised it will APPEAR like its frozen or no progress for like 4 minutes, then it will slowly start moving. Once it gets to 99, it will appear stuck again... just be patient and about 5 min later it will complete. Total flash time is arouund 20-25 min.
DO NOT FORGET TO UNPACK THE ZIP FILE
EDIT THE PAYLOAD_PROPERTIES.TXT
CHANGE THE "0" TO A "1" ON THE ENGINE_UPDATE_CHECK_DISABLE =
SAVE THE CHANGES, AND RE - ZIP THE CONTENTS
THEN COPY THIS ZIP FILE TO YOUR /SDCARD/ FOLDER!
if you dont it will fail!
thx for reminding me.. adding to OP
beatbreakee said:
You have to use the "OXYGEN UPDATER" app from the google play store... When you first open it , it will tell you that your device is on the current version... ignore that, and you have to open the settings menu for it, and go enable ADVANCED MODE.... This will allow you to go back and CHOOSE what device you are supposedly using. (kinda a cheap override command)... doing this will let you choose the 2417 (NA) model. **Now once again HIGHLY IMPORTANT that you are doing this ONLY after flashing the Downgrade/Rollback so that you will be on 2415 A.08 build... cuz then when you select the 2417 model, it will show an update available for 2417 A.12 build. and also the Android 13 Beta. Pick whichever you want, and click download... NOW once downloaded DO NOT HIT THE REBOOT BUTTON.... this will attempt to flash it via normal methods... instead jump into ADB , go to Shell, and head to /sdcard/ and start looking for the folder where it just downloaded the update. It places it sometimes in the main /Sdcard/ folder, and other times in the /Sdcard/Android/Data/<app name>/ folder.... you will know it when u see it. Find it and copy it to your computer and then you have the official OTA saved. After that, make sure it is moved to the /Sdcard/ folder and use "local updater". Will ask you to confirm, click Ok, and it should start the verification and flash process.
Be advised it will APPEAR like its frozen or no progress for like 4 minutes, then it will slowly start moving. Once it gets to 99, it will appear stuck again... just be patient and about 5 min later it will complete. Total flash time is arouund 20-25 min.
DO NOT FORGET TO UNPACK THE ZIP FILE
EDIT THE PAYLOAD_PROPERTIES.TXT
CHANGE THE "0" TO A "1" ON THE ENGINE_UPDATE_CHECK_DISABLE =
SAVE THE CHANGES, AND RE - ZIP THE CONTENTS
THEN COPY THIS ZIP FILE TO YOUR /SDCARD/ FOLDER!
if you dont it will fail!
thx for reminding me.. adding to OP
Click to expand...
Click to collapse
the OP updater app only shows the 500mb OTA 2417 and not the 4gb full install. Will it still work? On the global version .08 I could not get the in built local install to install anything without verification failure. Also 2417 variant does not have beta 13.
tdamocles said:
the OP updater app only shows the 500mb OTA 2417 and not the 4gb full install. Will it still work? On the global version .08 I could not get the in built local install to install anything without verification failure. Also 2417 variant does not have beta 13.
Click to expand...
Click to collapse
Links straight from 1+ community... android 13 OTA update packages for 2413, 2415, and 2417 ....
AND
Rollback packages for the same respective models... All in zip format. Must unpack and change payload_properties... Yadda yadda....
Android 13 all regions and Android 12 rollback all regions!
Now you can rollback to any region you want and start from there! I must remind EVERYONE... If you have not Sim unlocked your device prior to changing regions, you will lose that ability for the near future, because there will not be a T-Mobile official upgrade/rollback packages released afaik until maybe after the new year. (Don't know why.. just relaying what T-Mobile told me!). But the Unlock apk is strictly for the 2419 model and there is not currently a way back to it.
And be aware, that if you have ANY belief that you might be considering either doing this or maybe unlocking bootloader if we find an exploit, I highly advise you flip your OEM UNLOCKING switch to ON, now! Because T-Mobile may find a way to turn that toggle grey again if your sim is still locked. Just an fyi
tdamocles said:
the OP updater app only shows the 500mb OTA 2417 and not the 4gb full install. Will it still work? On the global version .08 I could not get the in built local install to install anything without verification failure. Also 2417 variant does not have beta 13
Click to expand...
Click to collapse
GLO version is not NA. GLO is 2415 EU. I know this because this is the reason I'm stuck on 2415.
yes you are correct... and i can honestly say i have NO idea where i got a 2417 beta 1 android 13 firmware from, but I DO have it downloaded to my computer ... I am looking at it. I know for a fact that i got it from some chinese site, or vietnamese ... something like that... but because of that i wont upload or link it, as i stated in my OP, i had 2 of my Laptops, one macbook pro running parallels 18 from bootcamp, AND my Dell laptop, BOTH infected with a VERY FIERCE malware/virus that took me almost 12hrs to find everything altered, and i STILL dont feel 100% about that! I get some random cpu spikes while doing nothing, but cannot find the process doing it. So it was definitely a modified package of android 13 ... C.11 .... (which gives me ideas because if they modded a payload and it still flashed, then maybe i can do the same to crash that dumbass init script somehow.... anyways... different thread)
if i find the link i will post it with caution.... but YES that 573 mb file will work to move you to 2417. Personally i would consider looking more towards using a GSMMAFIA Full Flash FW, for 2417 , but thats just me, and i trust them. but again, Yes this file will work.
(its very funny how the official oneplus site shows 3 different files for 3 Android 13 updates, as well as 3 files for 3 rollback packages
NONE OF WHICH are the 2419.... why create 3 files for 2 versions?
I can't move to 2417 from 2415 with built in updater. Even changed 0 to 1. Downloaded update apk and it doesn't see ota zip in root directory. I think I need full install zip for 2417. Any ideas how to go from the 2415.08 to the 2417.10? What's even better is the global package doesn't want to install either through the inbuilt updater. I have to use the updater APK to install the global package.
There's something in that zip that keeps it from verifying it and it's not the zero and the one. The updater APK doesn't even see that zip file it only sees the GLO zip file.
The incremental GLO a.12 did not want to flash. Failed every time I tried. The full GLO a.12 package was giving me problems flashing also. It would get to 40% complete and then fail. Third time flashing after rebooting finally took.
beatbreakee said:
yes you are correct... and i can honestly say i have NO idea where i got a 2417 beta 1 android 13 firmware from, but I DO have it downloaded to my computer ... I am looking at it. I know for a fact that i got it from some chinese site, or vietnamese ... something like that... but because of that i wont upload or link it, as i stated in my OP, i had 2 of my Laptops, one macbook pro running parallels 18 from bootcamp, AND my Dell laptop, BOTH infected with a VERY FIERCE malware/virus that took me almost 12hrs to find everything altered, and i STILL dont feel 100% about that! I get some random cpu spikes while doing nothing, but cannot find the process doing it. So it was definitely a modified package of android 13 ... C.11 .... (which gives me ideas because if they modded a payload and it still flashed, then maybe i can do the same to crash that dumbass init script somehow.... anyways... different thread)
if i find the link i will post it with caution.... but YES that 573 mb file will work to move you to 2417. Personally i would consider looking more towards using a GSMMAFIA Full Flash FW, for 2417 , but thats just me, and i trust them. but again, Yes this file will work.
(its very funny how the official oneplus site shows 3 different files for 3 Android 13 updates, as well as 3 files for 3 rollback packages
NONE OF WHICH are the 2419.... why create 3 files for 2 versions?
Click to expand...
Click to collapse
Hey you seem like a very competent programmer you should shoot me a private message and add me and discord I have the OnePlus 10t and I've been trying to figure out how to restore it if we run into a problem again I did restore them at once but it doesn't seem like I can do it the same way again I would like to get more details but I want to keep it to a private chat cuz I don't want to get people's hopes up a way to fix a phone that isn't real
This is great! I have been looking to change region from India onto a Global Version.
I have the Oneplus Ace Pro which is a chinese release of the 10T, the seller I bought this from flash it to Oneplus 10T India region.
Will give it more time though, wanted to get feedback first from those that has the Ace Pro Version.
so after doing some research i have found 2 things... 1. Oppo has ppl watching this thread and has made some alterations to the files that come from their server... these are the only 3 i had original copies of but of those 3 ALL of them had a minor difference and all were modified right after I revealed that i had success in converting my 2419 to a 2415. Once i stated that i was able to move to ANY region using my method, SOMETHING very small was changed in the files, and that is the reason the 2417 OTA fails to load in Local Updater... look at the attached pic.
So this is obvious that they are onto us and this is a concern to them. You should still be able to Downgrade with any region that has an Android 13 Beta. The technique works perfectly as long as you have a full version of Android in between.... AKA 12 to 13, and 13 back down to 12. And because of the new links in the OP, you can use local update to roll back to 2413 or 2415 ... I do believe that a 2417 beta is imminent and as such there will have to be a 2417 rollback released with it. There is still no danger with using this method, as you see because if the file is incompatible. local updater will fail to populate it!
Now for the second thing. OPPO used to have a special function in the Engineering Mode, which when activated would re-enable Fastboot Mode on the devices temporarily. This function is still alive in these devices today, only it has been hidden away deeper. This was confirmed to me after another grueling 3 hr chat with OnePlus technicians. I was told, "Sir we do not have access to the program you are asking about. The MSM Tool is completely maintained and controlled by OPPO division, and while yes we are under their ownership, there remains 2 different divisions in our company" ... 1st tech ..... "Sir you would need to enable fastboot mode so that you can flash the original firmware to your device, if it is failing to boot. You need to enter "Factory Mode" and input the locking code which is calculated from your device Imei. Once you have entered the code, you will be instantly rebooted into fastboot mode, and there you will be able to flash the signed firmware to it. Do not attempt to flash unsigned firmware as it will fail if your device comes with a locked bootloader." ..... 2nd tech......
This is not FastbootD he is talking about, because in FastbootD you do not need "Factory Mode" to enter it, and a little bit further research found this post which almost exactly matches what the tech told me!
Factory Mode Unlock
Of course the same way that Oppo decided to interfere with me, they also interfered with this method. They went and simply unlocked engineering mode completely in our devices, which made the screen where you enter the code, vanish. But i guarantee you, that based on some digging into the system files that our devices have running, i found several processes mentioning privileged processes that have simple flags that are called when "pre-boot" functions are initiated. Now in YEARS of time that OPPO has had to deal with the programming these devices they have never managed to actually eliminate "Fastboot Mode". They just become sneakier in hiding it behind user accessible operations. I am fully confident that the same thing applies here. While i dont have all the answers, i implore you all to apply the knowledge i have given and help find just where it is hidden in ours.
To call Engineering Mode on our phones, the code was changed to:
*#899*
Maybe the unlock screen has been hidden in here under a different label... maybe they created a new dialer code, but make no mistake, OPPO must have a need for this mode for repairing our phones otherwise they would eliminate it completely. Oppo is a 2-bit chinese company who is too cheap to design a new OS, and therefore somewhere, there is going to be a method to gain what were looking for. That is all i have for now.... but i am still digging. ( i have managed to get an additional 2 weeks to hold onto the 10t before i have to drop it into the return box and hand it over. So any ideas that you come up with, you DO NOT have to risk your personal devices! I can try ANYTHING on mine with absolutely ZERO ****s to give, as to it getting bricked! BRAINSTORM PPL! let me know what you come up with and i will try it!)
AkayamiShurui said:
Hey you seem like a very competent programmer you should shoot me a private message and add me and discord I have the OnePlus 10t and I've been trying to figure out how to restore it if we run into a problem again I did restore them at once but it doesn't seem like I can do it the same way again I would like to get more details but I want to keep it to a private chat cuz I don't want to get people's hopes up a way to fix a phone that isn't real
Click to expand...
Click to collapse
as soon as i get some free time, possibly this evening or tomorrow morning, i will shoot you a dm and we will link up.
tdamocles said:
There's something in that zip that keeps it from verifying it and it's not the zero and the one. The updater APK doesn't even see that zip file it only sees the GLO zip file.
The incremental GLO a.12 did not want to flash. Failed every time I tried. The full GLO a.12 package was giving me problems flashing also. It would get to 40% complete and then fail. Third time flashing after rebooting finally took.
Click to expand...
Click to collapse
Well i do know that the Zero - One does trigger a fail, thru simple trial and error. But you are correct in that it is much more than that. I have managed to open 2 different Payload.bin files, SWAP highly important files in each such as Boot.img ... and then pack them back, AND THEY STILL FLASHED... so it definitely doesnt have anything to do with the file signatures, because the sigs would change considering the boot.img is of different sizes. There is something possibly hidden in one of the Android Manifest files, or one of the many Build.prop files in the Payload that is what triggers a fail. If we can figure out exactly what file it is, we can find out whether we can alter them, or eliminate them completely. My focus has shifted though, now that we have a working region swap. Now i am focused on this special function of the engineering/factory mode, because if it can be found, it will mean a FULL BL unlock... THAT will negate the need for these, because we will be able to flash whatever we want !
AND YES OPPO.... I KNOW YOU ARE WATCHING MY THREAD NOW! JUST KNOW THAT IDGAF! I AM AND I WILL CONTINUE TO CHIP AT YOUR B.S. ATTEMPT TO KEEP OWNERS FROM DOING WHATEVER THEY WANT WITH THEIR DEVICES! YOU DONT OWN THE PHONES... YOU MANUFACTURE THEM! ONCE THEY LEAVE YOUR WAREHOUSES, AND WE PAY THE STORE FOR THEM, THEY BELONG TO US. IF YOU DONT WANT TO SUPPORT THEM AFTER WE CHANGE THE FW, SO BE IT.... BUT THAT DOES NOT GIVE YOU THE RIGHT TO DENY US THAT OPTION... THIS AINT CHINA! THE VAST MAJORITY OF THE WORLD WHICH PURCHASE YOUR PHONES ARE FREE REPUBLICS, SO YOU DONT DICTATE OR GOVERN THE USAGE OF OUR DEVICES! REALIZE THIS OR BECOME LIKE MOTOROLA, AND SO MANY OTHER COMPANIES WHO WENT OBSOLETE FOR A VERY LONG TIME! WHEN YOUR SALES DECLINE 50% OR MORE BECAUSE YOU ALIENATED A BIG GROUP OF YOUR CUSTOMER BASE, THEY WILL ELIMINATE THE EXECUTIVES WHO WERE RESPONSIBLE FOR THIS LOSS!
beatbreakee said:
as soon as i get some free time, possibly this evening or tomorrow morning, i will shoot you a dm and we will link up.
Click to expand...
Click to collapse
So I actually have a complete list pulled off of my OnePlus 10t the 2417 edition of the ussd codes otherwise the dialer codes that can and should work on the phone I can post them if you want or I can send a link to them.
kramnod said:
This is great! I have been looking to change region from India onto a Global Version.
I have the Oneplus Ace Pro which is a chinese release of the 10T, the seller I bought this from flash it to Oneplus 10T India region.
Will give it more time though, wanted to get feedback first from those that has the Ace Pro Version.
Click to expand...
Click to collapse
Hey man, that happened to me as well... Amazon right?.
So the only issue is the 12GB Ram... And the antennas in my case (I cant get 5G).
So why do you want to change?.....
I want to know so i can change it as well, lol
Related
Today I have pulled an MM Firmware-Over-The-Air update from my AT&T Galaxy S7 and uploaded the original .CFG file and my compiled .ZIP files for flashing via recovery. Download the file of your choice and place it onto your devices external storage, reboot into recovery, select "Apply Update From External Storage", search for the downloaded file, select it, click yes, and wait for the flash to complete.
Another note: As normal, this WILL NOT wipe any of your personal data. But just know that your recovery might not allow you to flash from External storage if your device is rooted, which means you will either have to completely unroot and restore dm-verity status or try flashing the file via ADB.
If you have any troubles please feel free to write below about it. If this helped you, please be sure to hit the thanks button.
To be clear, I will capture the Nougat update for this device once it is OFFICIALLY released. The update file in this thread is a MM update.
PDA Version: G930AUCU4APJ4
CSC Version: G930AATT4APJ4
--Download links--
Original .CFG File: https://mega.nz/#!D4wzSbhR!IyQKit5s0M-s4_5XbYb0sOWVePk1zcU-TJDJMffwL5A
Compiled .ZIP File: https://mega.nz/#!e0w1RaIa!SmKZ0Gr8iN7ETEUmEUdWljgGZZc_x-x_qhxvXQfUBm8
Cheers!
anyone tried to flash this that's on the unofficial Nougat (G930AUCU4BQA4)
Looking at the CSCVersion.txt File inside the ZIP shows that this is G930AATT4APJ4 for anyone wondering which version
elijahblake said:
anyone tried to flash this that's on the unofficial Nougat (G930AUCU4BQA4)
Click to expand...
Click to collapse
Note that I believe this is just an update to MM. I would expect that you'd need to get the ODIN files for the G930AATT4APJ4 build and do a full flash / wipe to this one.
thelostsoul said:
Note that I believe this is just an update to MM. I would expect that you'd need to get the ODIN files for the G930AATT4APJ4 build and do a full flash / wipe to this one.
Click to expand...
Click to collapse
Is it possible to ask you to flash the update to tell me if it truly works? If it doesn't I'll replace the files.
KingOfTheNet said:
Is it possible to ask you to flash the update to tell me if it truly works? If it doesn't I'll replace the files.
Click to expand...
Click to collapse
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
thelostsoul said:
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
Click to expand...
Click to collapse
Most likely be Spring with AT&T and their release record.
thelostsoul said:
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
Click to expand...
Click to collapse
It's fine, I just flashed it to mine and it's just a security patch for MM. I will capture the official Nougat FOTA release once it comes out.
4APJ4 is Old (October) the latest is 4APK1 (MM)
4=Bootloader Version
A=Marshmallow
P=2016
K=November
1=Build Number
And latest for Nougat is 4BQA6
4=Bootloader Version
B=Nougat
Q=2017
A=January
6=Build
Omar04 said:
4APJ4 is Old (October) the latest is 4APK1 (MM)
4=Bootloader Version
A=Marshmallow
P=2016
K=November
1=Build Number
And latest for Nougat is 4BQA6
4=Bootloader Version
B=Nougat
Q=2017
A=January
6=Build
Click to expand...
Click to collapse
One issue with that... qa6 is feb update...
twizt3d said:
One issue with that... qa6 is feb update...
Click to expand...
Click to collapse
Added screenshot
twizt3d said:
One issue with that... qa6 is feb update...
Click to expand...
Click to collapse
Yeap it doesnt apply for Beta they are always ahead of time only official releases match. (There's always that one build that wants to break the rules, but only happen with unreleased builds mostly because they apply the security patch early for testing and compiler gives that build code.)
It always has been that way with Samsung since the OG Galaxy S.
Check my posts from several years ago on earlier galaxies and you'll notice.
KingOfTheNet said:
Today I have pulled an MM Firmware-Over-The-Air update from my AT&T Galaxy S7 and uploaded the original .CFG file and my compiled .ZIP files for flashing via recovery. Download the file of your choice and place it onto your devices external storage, reboot into recovery, select "Apply Update From External Storage", search for the downloaded file, select it, click yes, and wait for the flash to complete.
Another note: As normal, this WILL NOT wipe any of your personal data. But just know that your recovery might not allow you to flash from External storage if your device is rooted, which means you will either have to completely unroot and restore dm-verity status or try flashing the file via ADB.
If you have any troubles please feel free to write below about it. If this helped you, please be sure to hit the thanks button.
To be clear, I will capture the Nougat update for this device once it is OFFICIALLY released. The update file in this thread is a MM update.
PDA Version: G930AUCU4APJ4
CSC Version: G930AATT4APJ4
--Download links--
Original .CFG File: https://mega.nz/#!D4wzSbhR!IyQKit5s0M-s4_5XbYb0sOWVePk1zcU-TJDJMffwL5A
Compiled .ZIP File: https://mega.nz/#!e0w1RaIa!SmKZ0Gr8iN7ETEUmEUdWljgGZZc_x-x_qhxvXQfUBm8
Cheers!
Click to expand...
Click to collapse
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
suyash1629 said:
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
Click to expand...
Click to collapse
There was no compiling. You can flash the ota update files from stock recovery after renaming the file name extension from .cfg to .zip.
suyash1629 said:
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
Click to expand...
Click to collapse
I didn't flash the update file itself, I had the ODIN files for it. They're the same thing.
When it comes to official updates, no signature modification should be necessary (Or possible, for that matter. I don't think there's a way to modify the signature. If there is, I don't know about it.). The only thing different between the 2 files is the file format.
Hope I answered your questions.
Cheers!
Can You Supply the Latest FOTA roms For.
G930AUCU4BQK2
G930AUCS4BQJ2
G930AUCS4BQH1
I have an Unlocked G930A (not really unlocked just using a cricket SIM) But I cannot Get the Software Updates For it because of AT&T. I have seen the information on reflashing it to the U software but i really dont want to have to restore everything to my phone unless i have to..
The Version currently running on my phone is vulnerable to the bluebourne exploit and im trying to get that patched. :/
On a side note. are you able to do a packet capture while scanning for the updates? There is one on the play store that will also let you perform a MITM on the application and you should be able to capture anything sent over SSL in plain text/hex/etc
I did Want to Ask you a quick question. How did you capture the FOTA package to begin with?
I wonder if it is possible to setup an Authoritative only dns server and then use it to spoof the location of the update servers. to create a DNS method that would allow the FOTA to be pushed to devices no longer on AT&T
Anywho if you can get those firmwares and get me full packet captures of just the update application while it is checking and downloading the update, i might be able to create a web application that is able to capture the headers sent by the phone that identify its model/fw version/etc and be able to push the firmware update Via the built in option in the settings, (although you may need to swap your dns settings for a moment and install a CA cert that allows validation of a connection. im not too sure if a CA cert will need to be installed because im not sure if they push the updates over a SSL/TLS connection. Using the data collected here may also pave the way to enable this to work with other models and carriers and manufacturers. (my hypothesis is that packet captures would be needed on any firmware updates "you" would want to push with this)
Basically Im thinking it might be possible to download those zip files along with the packet capture data to create a simple web application that is able to tell the phone there is a software update available. It would require using a 3rd party DNS server to "redirect" the connection to a server that doesnt care if your an at&t customer. It might also need a self signed CA cert installed into the device to Validate TLS/SSL. From there it might be possible to have the server 301 redirect the zipfile to another url that is behind a CDN to reduce the risk of ddos and keep the server(s) stable keeping the downloads reliable and fast.
Seeing how the Firmware update is already digitally signed by Samsung and/or AT&T it should probably install without an issue. I dont see the possibility of the wrong stock firmware being flashed on the wrong phone provided the manufactuer had a proper assert statement in place to verify the model and sw/hw versions, and im pretty sure a stock recovery wont accept a firmware signed by any key.
I might be Going off topic here, But one more question.
Do i actually need AT&T service to download the OTA updates from the Software update function in the phone settings.
What i mean by this is does the SIM card need to have an active plan on it? or can it just be provisioned to their network with out a phone plan and downloaded over wifi?
UPDATE: It Can Now be officially confirmed that Carriers and Samsung Deliberately block OTA updates when you unlock the device. there are thousands if not tens of thousands out there on a variety of devices as far back as the S4 that may not have been able to get updates. just because they used a Cricket Sim or unlocked the device. I also Spoke with AT&T customer support today and got told the blatant Lie that they push the same OTA updates through the cricket network to ensure that AT&T devices on it can be updates. I also went to samsung service center at bestbuy and they told me my phone was up to date when its not. Samsung Smart Switch Also Reports that my device is up to date when i know for a 900% fact it is not.
So it looks like Someone is going to have to write an app that Hijacks the Requests and replays a valid packet capture just to get the phone to update in its orignial intended built in method.
The sad part is the carriers would see this and just write a patch to prevent it rather then change their policies.
Basically The carrier has the right to deny you a software update because you left their network and leave you exposed to Critical Security Vulnerabilities.
That is their way of sticking up their Middle Finger at the FCC for mandating carriers unlock their devices and the end user who either met his/her contract obligation or outright paid for his/her device
[SARCASM] basically its like saying hey we know you paid for your device, but **** you, you left our network and even though the updates come from a samsung controlled server were going to ensure our middleware deliberately blocks your device from updating so you remain vulnerable and you information is stolen, That'l teach you for unlocking your device and leaving our network because we charge literally an arm and leg for service, how dare you as a customer go against our big monopoly that seeks to buy out every major ISP and cable provider in america but hey thats alright were still winning but because you left our network we will block these updates so we can further Sell your information and viewing browsing habits off to the NSA (Google TITANPOINTE tinfoil hatters!!!!) unless you want to send your phone off to one of our service centers where one of our butthurt technicians will see you rooted your phone and say it has damage and turn our free reflashing service into a paid repair and charge you through the ass for service, also did we mention were not going to update the software because our application is designed not to tell you there is an update available if you unlocked it or used our Subsidary cricket SIM in the device and didnt unlock it Or you can go on XDA and grab an odin package an potentially invalidate your warranty and then when your device comes to us for a cracked screen we can deny you the repair even though the modifcation wasnt a modifcation and has nothing to do with a cracked screen. [/SARCASM]
Anywho im going to Bite the Bullet and Grab an Assortment of AT&T contract Sims and Go Phone sims and Other Carriers, Im going to go to the local pawn shops and buy an assortment of devices and attempt to downgrade each and every single one of them back to their old original firmware versions, Dump all the FOTA updates and dump the packet captures and i guess i will have to research the possibility And be that asshole who gets sued for reverse engineering their software.
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good:
New here. Didn't see a forum for the Moto G Pure XT2163. Mods - I am sorry. Please move wherever's best.
Discovered that the version Verizon is selling (notably the slickdeals thread on the one from Visible) is different. It's -2 vs. -4.
Looks like VZW disabled most of the bands that T-Mobile/Sprint use - 25, 41, 71, for example.
Looking to see if it's possible to enable those bands. One report on SD thread says they bricked their device trying RETUS version but IDK if the bootloader needs to be unlocked first, or if it would even help. Probably more work to unlock these bands if it's even possible.
Downloads look available here https://mirrors.lolinet.com/firmware/moto/ellis/official/
Haven't messed with flashing a phone in years. May be able to try later but hoping anyone else here can look into this.
I'm going to guess as is the case with most other Android devices branded by Verizon that the bootloader will be restricted from being unlocked. There is really no way around this as it's an OEM based policy. If you want to play with custom ROMs or root based modding, I would highly recommend ditching the Verizon or any other carrier branded variant with the exception of T-Mobile/Metro and Google Fi (there are others) that actually allow OEM unlock. Not only that, but if you're looking for certain connectivity bands, you don't want to settle for a carrier device variant designed to use a particular set of bands which don't include the ones you need. No sense getting a Verizon variant to run on T-Mobile/Sprint bands when you can, you know, get the T-Mobile variant in the first place. Get the global unlocked variant model if you can and start from there. Far easier than the headaches you'll get trying to transform VZW to TMUS.
Cross-flashing is not going to unlock bands, you need to change modem configuration. Throw your SoC(Mediatek) followed by "unlock bands" into Google and see if you have any luck.
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
BrittonCBurton said:
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
Click to expand...
Click to collapse
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Agent_Orange1488 said:
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Click to expand...
Click to collapse
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
BrittonCBurton said:
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
Click to expand...
Click to collapse
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Agent_Orange1488 said:
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Click to expand...
Click to collapse
Well I can try and learn how to extract the phones information to my computer. I don't know how to do that exactly. The way I was able to get a hold of the phones stock firmware data was by using Lenovo's Smart Rescue and Recovery software.
You have to enable usb debugging mode, attach the phone to the computer with the software running and make sure that you didn't disable/delete Device Help. That app is what makes the Lenovo software work, otherwise the Recovery software fails to see the phone. If it sees the phone correctly then you can see the preselected target firmware it wants you to download under the Rescue tab along the top.
So I did that and grabbed the files it created without actually applying them to the device. The whole thing is a little over 2GB and difficult to host but I put the stock boot.img file here for anyone who needs it. If anyone wants all the files I can try to upload the whole thing one file at at time. That's the way it was sent to me, an uncompressed folder. If I zip it all up and try to upload it most sites will say file size exceeded. Anyway here's the link...
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Agent_Orange1488 said:
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
Click to expand...
Click to collapse
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
Yeah appears it was produced in late 2021 or sold at that time so it's new and no one has made any custom firmware's or recoveries for it as far as I know. I don't know how to do that, requires computer programming skills. I don't have any of those.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
BrittonCBurton said:
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Click to expand...
Click to collapse
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Agent_Orange1488 said:
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Click to expand...
Click to collapse
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
BrittonCBurton said:
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
Click to expand...
Click to collapse
Ya I'm definitely not going to try anything on the actual device, (ESPECIALLY if I am trying to put it together myself) but I am pretty sure you can test that stuff on a virtual system. Some kind of android emulator or whatever. As for a stock/debloated/de-odexed ROM, I haven't seen one but that couldn't be all that difficult to put together, right? I mean as long as the patched boot.img is included anyway. I feel like a recovery would be a higher priority though...? BTW, I have never used Lineage before, how is it?
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Gamekeeper408 said:
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Click to expand...
Click to collapse
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
I would also like the patched boot.img if it is for the XT2163-4. Thanks
Hey boys I actually got rid of the moto g pure...for now at least lol! GREAT phone and I would be willing to get it back once there is some dev work done on it...will definitely be watching the threads on it. Good luck boys!!!
Hi
I read the above posts, and it seems like even if I am able to root it using Magisk, I won't be able to flash it with custom rom?
Thank you Agent_Orange1488 for the posts.
**Edit: Be sure to read comments at the end of this post******
I've already posted this a few times but I figured I would try to save some people time who want/need to root from any security patch. This is a copy and paste from an answer I gave in another thread but it's a basic how to.
Install DSU sideloader app from playstore to boot a prerooted GSI then use Partitions Backup and Restore app from playstore to save copies on your device. Install magisk app and patch the extracted boot.img and then transfer backups along with the patched boot image to your PC for safekeeping and flash the patched boot.img in fastboot. You can rename any .bin files to .img to flash them if they get extracted as a .bin file. Check your settings in the partitions Backup and Restore app before starting the backup process. You can choose to save them in an easy to find directory and for me it was better to choose to save them RAW/uncompressed then just compress them all into a single archive rather than having a hundred separate archives for each individual partition because it makes it easier if you have to reflash things if you need to recover. You may want to disable battery optimization for the app because it takes a while to extract all the images doing a full backup but its well worth the wait time if it saves you from a brick later on.
I wish I had time to elaborate but hopefully someone else can take the time to elaborate and add to this for anyone needing step by step. I'm surprised nobody has done this already.
Credits to AndyYan for giving advice on the root method. I stole this from him and just made a post with a title that makes it easier to find since so many are still asking how to go about rooting their devices.
*****REQUEST TO COMMUNITY********
There are many who are already on August Security patch and i dont have time to update and post the newest images. So if you are on august patch and pull backups I ask that someone please be so kind as to upload a copy of your backup to Google Drive or a filehosting server of choice and post a new thread so that others can unbrick their devices.
*Please ***DO NOT include**** the following partitions*:
DEVINFO
DINFO
FRP
KEYMASTER_A
KEYMASTER_B
KEYSTORE
LOGDUMP
***MDM1M9KEFS1
***MDM1M9KEFS2
***MDM1M9KEFS3
***MDM1M9KEFS4
MODEMDUMP
OPLUS_SEC_A
OPLUS_SEC_B
RAWDUMP
SECDATA
STORSEC
USERDATA
VM-KEYSTORE
*** These partitions may/contain YOUR personal device info, DO NOT make these public***
You can make a new Google account for the sole purpose of uploading these for the community so as not to fill your own GDrive. Be sure to change permissions for the images to share with anyone who has the link. This would be very much appreciated by many.
*****Update 09/18/2022*****
Thanks to ctschrodinger88 & dmtec for posting more detailed instructions!!! you can find ctschrodinger88's instructions below, scroll down to the 5th post.
dmtec also posted instructions in another thread linked here: https://forum.xda-developers.com/t/august-boot-img.4491831/post-87426877
we are still in need of august modems if anyone cares to upload them to their drive and link them or any other filehosting service.
can you suggest me a pre rooted gsi rom please?
thanks
fictisio said:
can you suggest me a pre rooted gsi rom please?
thanks
Click to expand...
Click to collapse
i used crdroid but its buggy, launcher crashes but its useable, atleast to get this done and then be sure to discard it in the DSU sideloader notification when you reboot so the inactive slot is empty, it will make for easier updates/mods later
has anyone had luck flashing the file in this article? https://www.getdroidtips.com/oneplus-nord-2t-5g-firmware-flash-file-2/#google_vignette
I used the info provided and referenced here as a guide and some external pieces and have things working.
I'll caveat the following, I don't remember the current firmware version I started with, but I'll try to remember to update.
I have the Nord N20 5g, but not the T-mo branded one, though in looking at this, the concepts should be the same.
Base assumptions:
- If you haven't done these beforehand, stop and take care of it. Research if you need, but please DO NOT just keep going or copy, paste, and run, without understanding to some extent what you're doing. If you just run commands it can be much harder to fix later.
a. Your phones bootloader is unlocked. (If you haven't already done it, when you do, your data will be gone, so if you care, back it up NOW)
b. You have access to an Android terminal of some sort (adb or on-device terminal) and you know how to use it. Unless you absolutely can't use a computer for some reason, I would use adb, it makes data backup easier (IMO).
c. You have somewhere to store your backed up partitions (THIS IS IMPORTANT)
Step 0: Download a pre-rooted Generic System Image (GSI) to use. Put it in a good working directory. This page links to several. https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I used the LineageOS image by @AndyYan
If you are wondering about the various file endings this is the basic version
Code:
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
From: https://forum.xda-developers.com/t/teclast-t30-t1px-suitable-gsi-roms.4211427/
Step 1: Enable the Dynamic System Update (DSU) feature flag, you can follow the exact steps for this in this section https://developer.android.com/topic/dsu#feature-flag
If you are unsure, just run the `adb shell` command.
Step 2:
If the image you downloaded needs to be in ".gz" format. Some of the tools will handle alternate types, but that's because it rebundles it at ".gz", you can save some effort doing it yourself.
Code:
gzip -c [IMG_NAME]..img> [IMG_NAME].gz
Step 3: Push the image to the device
`adb push [IMG_NAME].gz /storage/emulated/0/`
This is where I switched from ADB to on-the-device.
Step 4: Download the DSU Sideloader: https://github.com/VegaBobo/DSU-Sideloader
You can do this with adb but I wasn't able to get it to run, so I went with the DSU Sideloader app above which made it much simpler.
Step 5: Run DSU Sideloader. You can follow the instruction there in the README. You will need to run a command that the app provides, either via adb or an emulator. Then you will reboot via the notification.
Step 6: [Once you reboot] Enable Developer tools in phone settings.
Step 7: BACKUP, BACKUP, BACKUP (Please do this now. It will help make life much, much better if you ever have an issue and need to reset.)
This was my process:
Bash:
adb shell
su
mkdir /sdcard/partitions
cd /dev/block/by-name/
for x in *; do dd if=/dev/block/by-name/$x of=/sdcard/partitions/$x ; done
# Note the collective size will be greater than the default space on the GSI boot, so you will want to separate things
# Back on local machine
mkdir [working_dir]
cd [working_dir]
adb pull /sdcard/partitions
# Your files from the adb command should populate the folder
mv [working_dir]/partitions/* [working_dir]/
# On device
rm /sdcard/partitions/*
# repeat the commands above as often as needed.
I don't know for sure all the files you will want to backup, but I pulled everything just to be safe. Keep them safe, because it is your safety net if you fall.
Step 8: Get boot_a or boot_b back on the device along with Magisk.apk (Please only download from here: https://github.com/topjohnwu/Magisk/releases)
Step 9: Install Magisk.apk (you can do this via
Code:
adb install ./magisk.apk
)
Step 10: Launch Magisk and install it to the book image stored on your sdcard.
Step 11: Pull the patched image to your local machine.
Code:
adb pull /sdcard/Download/magisk_patched-[stuff].img
Step 12: Boot phone to fastboot
Code:
adb reboot bootloader
Step 13: This is where there is an ideal and a real.
Ideal command
Code:
fastboot boot magisk_patched.img
where fastboot transfers the files and things just work, and if you reboot the system the regular boot.img is used. I haven't been able to get that to with this device.
I instead just ran
Code:
fastboot flash boot magisk_patched.img
which replaced the existing boot image, which is good, if it works, but if it doesn't, this is why you have backups!!!! Reboot the phone.
Step 14: When you boot, finish installing Magisk and you'll be ready to go.
If I remember other steps I'll add, or if you have questions I will try to help answer.
I just got a MetroPCS nord n20 (gn2200) and will try to root in the next couple days.
ScarletWizard said:
n20
Click to expand...
Click to collapse
Have they removed the unlock portal?
Damn, it's been a long time. Glad to be back.
ScarletWizard said:
No. My serial is 7 digits
Click to expand...
Click to collapse
seems to be a common defect.... if ur device is paid off oneplus can generate you a token but it takes weeks of back-and-forth with support to get it escalated...tmobile may or may not allow you to do that on a device that isnt paid off but i wouldnt even ask tmobile about it if your not paid off already, will only make it harder for those who are trying to unlock theirs if it IS the case that tmobile doesnt want you to unlock it until youve paid the device off in full....oneplus will probably uphold tmobiles decision if your device isnt paid off. for now, we are able to unlock tmobile devices through the portal regardless of the financial status of the device. though you will still be SIM locked unless tmobile unlocks that for you. and their definitely NOT gonna do THAT til it gets paid off.
U.S. carriers dont like customers having unlocked devices and is against most user-agreement policies and can get your service terminated leaving you owing for a device you cant use and for the price of the contract you were on for service
your device is a CPH2459 and not a GN2200?
fictisio said:
can you suggest me a pre rooted gsi rom please?
thanks
Click to expand...
Click to collapse
Andy Yan's Lineage18 or 19..
DrScrad said:
Andy Yan's Lineage18 or 19..
Click to expand...
Click to collapse
pixel experience, crdroid... havent gotten kaleidoscope to work yet. Have heard that someone got aosp a13 going.... There are so many and so long as u use a matching security patch ur good. might work with a newer patch but of the ones ive tried i got thw matching patches to work. If you find one thats on a newer patch in the gsi page you should be able to follow the link and find an older release to match the patch ur on. If ur on may patch try to find a may patch just to make it pess likepy that there will be priblems. If on july or august, likewise find july or august sec patch release. newer patched systems MIGHT work with ur older patched bootloader and other partitions(modems etc...) but def would not advise just straight flashing mismatching security patches... Best to sideload first and see if u can get it working first. Its not very simple to dual boot these devices but i think someone did some work and posted a work around for doing that on a/b devices somewhere on xda......
Am willing to share my stock image with anyone willing to help. I am on the September security update on a OnePlus Nord N20 5G unlocked (Non-Carrier). I am running version 11 and android security update 2022-09-05.
I am having real issues getting LineageOS through DSU. It fails immediately on start every time. Bootloader is unlocked, it even shows through fastboot (Secure boot = on though), flag is set per instructions, and I am trying to install lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.gz . I tried two different versions of the DSU app but nada.
oromis995 said:
Am willing to share my stock image with anyone willing to help. I am on the September security update on a OnePlus Nord N20 5G unlocked (Non-Carrier). I am running version 11 and android security update 2022-09-05.
I am having real issues getting LineageOS through DSU. It fails immediately on start every time. Bootloader is unlocked, it even shows through fastboot (Secure boot = on though), flag is set per instructions, and I am trying to install lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.gz . I tried two different versions of the DSU app but nada.
Click to expand...
Click to collapse
make sure u r using a lineage version with the same security patch as your current OS if your on September u need a GSI on september. i personally gave up on lineage after trying a couple but was successful with a few others while dsu sideloader still worked for me, im not sure what i did to break it on my devices but i havent been able to get it to work on either device in a while.
i have yet to try the october firmware but it should be easy to downgrade and root if you think its the new updates. although make sure ur disabling verity. u might wanna disable the checks on vbmeta_boot too... i usually just disable it on all 3 vbmeta's to be safe.... i have a full july dump and someone else has posted the august dump on TG but that doesnt help in your case since you have the CPH2459 and we are on GN2200's nobody has been able to successfully crossflash them yet and im not sure if it will be possible or not but everyone that has tried it has bricked their devices so far. most have gotten them running again but have lost fingerprint
ScarletWizard said:
im on gn2200
Click to expand...
Click to collapse
Ok my last upload didn't upload correctly for some reason. I will re upload tomorrow I think..... I need to figure out exactly which partitions are device-specific.... I know which partitions get updated in the incrementals so if all of them don't get flashed then everything won't match but I have a feeling that the incrementals update a device-specific partition or two and if so then u will lose fingerprint at minimum...... I think I should just pull full backup of all partitions and then go for it. Worst case so long as u do everything right. U just don't boot and have to reflash the stock boot image... Be sure to flash the stock image to both slots just in case and then switch back to ur active slot and flash the patched boot image. I mean if it was me I would b comfortable doing it but that's completely ur call, I don't wanna encourage anything because there ALWAYS a risk something could go wrong. Power outage or something and it's screwed up but any time u r flashing u will always be taking a risk. Though I think the risk is minimal so long as u do everything right and there's not much to the simple root process, patch the boot image and flash, if it doesn't work then reflash the stock one. If it DIES work out for u we would b grateful for the October firmware if u wanna share it, we didn't get October yet.
ScarletWizard said:
If it dies. Lol scary.
I'm in the process of doing the partition thing
Click to expand...
Click to collapse
If it DOES.. Sry
ScarletWizard said:
who is the ADMIN of this n20 thread?
Click to expand...
Click to collapse
Just look.for the moderator edits lol
PsYk0n4uT said:
seems to be a common defect.... if ur device is paid off oneplus can generate you a token but it takes weeks of back-and-forth with support to get it escalated...tmobile may or may not allow you to do that on a device that isnt paid off but i wouldnt even ask tmobile about it if your not paid off already, will only make it harder for those who are trying to unlock theirs if it IS the case that tmobile doesnt want you to unlock it until youve paid the device off in full....oneplus will probably uphold tmobiles decision if your device isnt paid off. for now, we are able to unlock tmobile devices through the portal regardless of the financial status of the device. though you will still be SIM locked unless tmobile unlocks that for you. and their definitely NOT gonna do THAT til it gets paid off.
U.S. carriers dont like customers having unlocked devices and is against most user-agreement policies and can get your service terminated leaving you owing for a device you cant use and for the price of the contract you were on for service
Click to expand...
Click to collapse
One small problem, although Metron PCS uses T-Mobile towers, they are their own entity and T-Mobile does not have their Bootloader codes. Only OnePlus and Metro PCS have the Metro PCS unlock.bin file. That's what I came here was to try and find a dedicated metro bootloader unlock web page. Like the T-Mobile dedicated page. There is not one so it's going too take several calls over several weeks unless some one here knows a different way or a link to a metro PCS bootloader unlock page? Anyone chime in on this and save all of us that are running in circles back down the straight path to an unlocked bootloader..
jayram1408 said:
One small problem, although Metron PCS uses T-Mobile towers, they are their own entity and T-Mobile does not have their Bootloader codes. Only OnePlus and Metro PCS have the Metro PCS unlock.bin file. That's what I came here was to try and find a dedicated metro bootloader unlock web page. Like the T-Mobile dedicated page. There is not one so it's going too take several calls over several weeks unless some one here knows a different way or a link to a metro PCS bootloader unlock page? Anyone chime in on this and save all of us that are running in circles back down the straight path to an unlocked bootloader..
Click to expand...
Click to collapse
I'm about to file a FCC complaint to get mine then.