Related
My Phone Info:
Single sim 2gb ram + 16gb rom
Hello folks I've been searching for a nougat update for XT-1644, but unable to find over the xda if anyone of you havs upgraded your xt-1644 then kindly tell the procedure here, Thanks.
Here is my About Phone Info.
http://cloud.tapatalk.com/s/589c8f61b2eab/Screenshot_20170209-203359.png
http://cloud.tapatalk.com/s/589c8f48b01b2/Screenshot_20170209-203401.png
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
echo92 said:
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
Click to expand...
Click to collapse
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
waseemmayaa said:
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
Click to expand...
Click to collapse
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
echo92 said:
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
waseemmayaa said:
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
Click to expand...
Click to collapse
I see you've received a response in the other thread regarding if XT1644 will accept the update; given you've flashed TWRP, if you wish to be very safe, I would suggest re-installing your Marshmallow ROM so you have a stock install before proceeding to Nougat. There's nothing stopping you from directly flashing Nougat, and the fastboot method for either Nougat build may correctly overwrite the relevant files, the only way is to try the procedure. Don't use the TWRP backup images of Nougat - they don't contain updates to your baseband modem and other core parts of your device - they are only meant to be used once your entire phone is updated to Nougat.
If you wish to restore back to stock MM before flashing Nougat, here's links to stock firmware for XT1644: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980
But either way, read all the instructions first, ensure you've got all the firmware and tools you need installed/downloaded, your phone has at least 50 % battery and plenty of time, and you should be okay.
OK Please note (4-25-17) this message is a work in progress, as I slowly restore my system.
This is a listing and hopefully helpful listing of what I did (right and wrong)
in upgrading my Systemless-rooted (suuser) phone from 6.01 to 7.00 (nougat)
# 1. it did not work, and I went back to 6.01 successfully using the twrp recovery
I have previously used Bender's guid (here) to get the system-less root on 6.01.
essentailly, here's the best plan. Use the Minimal ADB and Fastboot package (MADB &F) (here)
(Explanation: the MADB&FB package will allow you do do LOTS of stuff related to updating your phone, with very little grief.)
it also includes the ability to automatically "push" a package over your usb connection if the ZIP file doesnt load right. **THIS will come in handy later!
Once MADB&F is installed, make note of your directory, and then make sure you start your dos window (for pc users) as an administrator!
BTW, if I HADN'T made the "TWRP backup" of my system, I'd be Sh*t out of luck right now...", because I screwed up the 7.0 upgrade.
the technical problem was that I had no data, no modem, no way of getting data/voice in/out.
SIMPLY using the TWRP restore fixed me!!!
(so far, we have MADB&FB, downloaded and bender's (chainfire) rootless guide.
Next you want to download the current firmware image for your phone. This will be a lifesaver, I promise!
3) Download a TWRP image (this will MAGICALLY load on your pc when you tell it you need help! Look HERE
(Athene is the Motorola Codename for the motoG4+)
3) copy the athene TWRP image into your madb&FB directory to make it easy to load
4) next, (you still haven't touched your phone yet, you realize: (skipping some basics here, you can search here on XDA to find more info)
a) plug your phone into your pc
b) make sure you are a developer
c) make sure your phone shows you are connected to your pc for file transfers, NOT for charging
5) in your MADB&FB directory, (aka a dos/(admin) window) type the following:
all commands at this point will take place in whatever directory you installed Minimal ADB & Fast boot (MADB&FB)
Connect your phone to your PC and open MADB&FB, check the connection with:
adb devices
return should include your "serial-no" and "device".
6) next, on pc, tell the system to reboot your phone to the bootloader!
Reboot into bootloader with:
adb reboot-bootloader
and check again with:
fastboot devices
7) Next you are going to download TWRP to your phone (not permanently, just for a bit!)
fastboot. flash recovery twrp-3.0.2-0-athene.img
Now you have TWRP (Team Windows RECOVERY PROJECT) loaded.
SO.. THIS is where you create a backup of your current stuff using the backup options.
NEXT:
take the suUser2.78 (stateless rooting), and once your backup is done, install it from TWRP
Then (I was) back to 6.01 rooted.
NEXT: 7.0 and then rooting... (will update tomorrow)
did a successful upgrade to 7.0,
then unsuccessfully tried to sideload supersu2.78, which bricked loader
then downgraded again to 6.01 (and rooted again, ok)
will continue tomorrow.
need working phone for now..
cheers to all, and to all, a happy spelunking!
You can't root factory Nougat as is, it is well encrypted.
You need to replace first the kernel with the ElementalX one, or you will end up with bootloops.
Only after that you can do SuperSU, but only with the latest beta.
A few pointers from your story:
1)As you've found out the hard way, you won't be able to update to Nougat if you have root and/or TWRP, because the update requires a stock system - stock recovery, system and no modifications (bootloader status doesn't matter). In other words, you'll need to unroot and restore your stock recovery - might be easier to reflash the stock system, probably the quickest way to flash a stock ROM (and update to Nougat) is to use the fastboot ROM. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Of course, this will remove root and TWRP, as well as potentially wipe your data, so back up accordingly. This should flash the NPJ25.93-14 build on your device, which appears to be the latest global build.
1a)Also, if you flash Nougat this way, your bootloader and GPT partitions will be updated, so if you wish to downgrade to Marshmallow at any point, when flashing do not flash these partitions from the Marshmallow ROM. Fastboot should stop you, but a brick may occur if these get flashed.
1b) You may find in the Guides section TWRP backups of Nougat builds, I don't recommend using these to update your system with. Granted, they have most of the Nougat system in a TWRP backup, but some crucial firmware (e.g. the baseband) is not included, and may cause you issues if your device is not formally flashed to Nougat.
2) As SoNic67 has already mentioned, the stock kernel security will cause your device to bootloop should you choose to try to root following the Marshmallow method. If you wish to use SuperSU, follow this guide: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 You may wish to use a more up to date TWRP than the official 3.0.2 (I recommend shrep's TWRP 3.0.3 n4 here:https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337) Whatever you do, ensure you flash first the ElementalX kernel before you flash the SuperSU v2.79 SR3 beta (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), or apply the systemless fix with earlier SuperSU versions as directed in the aforementioned rooting with SuperSU guide. Else you'll be having bootloops or your device will not boot whatsoever. Here's my steps in successfully rooting Nougat: https://forum.xda-developers.com/showpost.php?p=71817346&postcount=225. Good luck either way.
echo92 said:
A few pointers from your story:
[...]
1b) You may find in the Guides section TWRP backups of Nougat builds, I don't recommend using these to update your system with. Granted, they have most of the Nougat system in a TWRP backup, but some crucial firmware (e.g. the baseband) is not included, and may cause you issues if your device is not formally flashed to Nougat.
[...]
Click to expand...
Click to collapse
After updating my US retail xt1644 to nougat, by restoring totally-stock marshmallow then taking the OTA, I wiped data and made a *complete* TWRP backup using @Shreps' unofficial 3.1 TWRP build (https://moto.shreps.fr/Moto G4 (athene)/recovery/twrp-3.1.0-athene_shreps.img).
This version of TWRP allows backup/restore of the full set of firmware partitions including baseband, DSP, etc.
In other words, I believe the TWRP backup folder in the following .zip file provides a one-stop path to the latest xt1644 USRET firmware by doing a restore from TWRP 3.1.0.
https://drive.google.com/file/d/0B4XobQzgZVHyRTlmSDMtYkdZeUU/view?usp=drivesdk
My only uncertainly is if the ota process modified the partition table in a way that might make this backup image incompatible with the xt1644 still in the marshmallow state.
I've often wondered if I (or a more skilled enthusiast) couldn't build a TWRP-flashable .zip that would setup the partition table, update the baseband, etc. This is what I've grown used to from devs on other phones I've had, but perhaps there's something about the way moto does things that makes this problematic.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
After updating my US retail xt1644 to nougat, by restoring totally-stock marshmallow then taking the OTA, I wiped data and made a *complete* TWRP backup using @Shrep's unofficial 3.1 TWRP build (https://moto.shreps.fr/Moto G4 (athene)/recovery/twrp-3.1.0-athene_shreps.img).
This version of TWRP allows backup/restore of the full set of firmware partitions including baseband, DSP, etc.
In other words, I believe the TWRP backup folder in the following .zip file provides a one-stop path to the latest xt1644 USRET firmware by doing a restore from TWRP 3.1.0.
https://drive.google.com/file/d/0B4XobQzgZVHyRTlmSDMtYkdZeUU/view?usp=drivesdk
My only uncertainly is if the ota process modified the partition table in a way that might make this backup image incompatible with the xt1644 still in the marshmallow state.
I've often wondered if I (or a more skilled enthusiast) couldn't build a TWRP-flashable .zip that would setup the partition table, update the baseband, etc. This is what I've grown used to from devs on other phones I've had, but perhaps there's something about the way moto does things that makes this problematic.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Nice one, hopefully that'll help more XT 1644 users I'm still not sure if TWRP can backup/flash the baseband by itself, but I don't have a XT 1644 to test. I imagine your backup will need a clean flash (wipe data/cache/Dalvik) to work?
The OTA process does update the partition table, but as far as I know, that should not prevent you from flashing back to Marshmallow/Nougat as you wish, so long as you did not try to downgrade the GPT/bootloader.
There was an effort to create TWRP flashables of the stock ROMs a little while ago (you can see the thread here: https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147) which if I understood it created flashable radios and ROMs from the firmware files we have. We can't touch the GPT/bootloader since, as I recall, you need a signed stock firmware to do so (and besides, downgrading GPT might be asking for a brick). I recall some users mention they were able to run Nougat TWRP flashes on the MM bootloader/GPT without issue.
There were issues with simply flashing the Nougat 93-14 radio baseband files for some US users, losing LTE in the process and appears the only resolution was to flash the stock ROM - I don't know what the cause was (perhaps no/incorrect CDMA support in the radio files?). Your TWRP flash is from a US based phone so may have better luck in that department, and will likely behave on your device since that OTA has updated all the firmware on your device that TWRP isn't able to touch. I still am not sure if we can use this TWRP backup to update on a MM device without issue, but only one way to find out...
I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance
2CanSan said:
I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance
Click to expand...
Click to collapse
It's really simple actually: if you install B15 your data will be wiped, after that just skip everything and update to B29 (is B29 the latest? I have a G, dunno) and then use it. What you describe is not the actual performance that it should have, it's your specific case obviously.
I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery
tabletalker7 said:
I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery
Click to expand...
Click to collapse
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.
2CanSan said:
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.
Click to expand...
Click to collapse
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.
tabletalker7 said:
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.
Click to expand...
Click to collapse
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.
2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Choose an username... said:
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.
Click to expand...
Click to collapse
OK on the A2017U units you need the official marshmallow B29 package to roll back, and that only works with stock recovery on a clean B15 N install. The Rollback package I told you to use earlier will roll you back to B29 marshmallow NO MATTER WHAT YOU ARE USING (I have used this a lot, and OBVIOUSLY there are differences between the the A2017U version in North America and the A2017G version in Europe). If you want stock and rooted, I personally recommend B29 marshmallow over B15 Nougat, but either way go for it (I think the marshmallow had a much better radio than any of the Nougat packages). If you are interested in TWRP and root, I found B29 marshmallow much easier for both, and the marshmallow version of android also gives you Xposed, but back to your first post, you mentioned wanting marshmallow, and this is the best way to get it.
Step by Step method
1. Roll back to B15. Use the update.zip method. It will factory reset your device so backup everything you can't lose
2. Use MiFlash to unlock and install TWRP - check that thread on XDA for instructions.
3. (If desired) In TWRP, install the B29 marshmallow rollback. Do not reboot into system afterwards.
4. (If step 3 is done) In TWRP, flash TWRP. The marshmallow rollback will overwrite recovery with stock recovery
If you do this you will have exactly what you wanted in your original post. I can personally tell you this works, as I have tried every custom rom on here and always wind up back at B29 marshmallow when all is said and done. It has never failed me, and it will never fail you either.
I have found this tutorial in the comments of a tread, and it worked for me, so I decided to bring this tutorial in a new tread so everybody can easily see it:
Thanks hackslash for this tutorial.
To rebrand, you need an unlock bootloader.
1. Download the C10 oeminfo file https://mega.nz/#!aBhnDKAK!qeVVAjcApTl7fqjwHcPMUS6ITUDHL9Rx0u-4k8rx0c4. It is a zip file, extract it to find an img file. Reboot to TWRP and select Install Image and install the file to oeminfo partition.
2. Perform a complete factory reset in TWRP.
3. Download the latest Nougat (3 files package) for FRD-L09C10 through Firmware Finder. Flash it using HuRupdater https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279.
4. After the flash is complete, reboot the device, unlock the bootloader again and flash TWRP.
5. Download the latest Oreo build for FRD-L09C10 through Firmware Finder. Using HuRupdater flash the three Oreo firmware files. Don't perform a factory reset this time.
6. Reboot your device. You're now on Oreo.
(brightness dimming still happening in some apps on oreo)
(I also have tested Pixel experience treble (GSI), and guess what? I got in bootloop, yeah... thanks huawei for the amazing software work ...)
Will I Be Able To Install Unapproved Updates With HurUpdater?
@SuperSwordSmasher Yes you can install every stock firmwares.
@immichao - can you correct the links as they do not work
Deleted
Just updated the links
About GSIs, there are special GSI for Kirin devices. And don't worry they'll be released by the OpenKirin team with support for Honor 8 shortly.
hackslash said:
About GSIs, there are special GSI for Kirin devices. And don't worry they'll be released by the OpenKirin team with support for Honor 8 shortly.
Click to expand...
Click to collapse
I'm glad to hear that, will be the same rom for all the kirins or a special for each one? I wanna know what I have to look for...
immichao said:
I'm glad to hear that, will be the same rom for all the kirins or a special for each one? I wanna know what I have to look for...
Click to expand...
Click to collapse
Thanks to project treble it should be one for all, but we'll have to wait and see
immichao said:
I'm glad to hear that, will be the same rom for all the kirins or a special for each one? I wanna know what I have to look for...
Click to expand...
Click to collapse
Wait On Step 3, Could Of You Just Put TWRP As "recovery.img" And Flash It And Have TWRP Still?
Does The Open Kirin 3.1.1 TWRP Work On Oreo. It Works On Nougat, But Will It Work On Oreo?
Link To The TWRP You Used For Oreo Pls
immichao said:
I have found this tutorial in the comments of a tread, and it worked for me, so I decided to bring this tutorial in a new tread so everybody can easily see it:
Thanks hackslash for this tutorial.
To rebrand, you need an unlock bootloader.
1. Download the C10 oeminfo file https://mega.nz/#!aBhnDKAK!qeVVAjcApTl7fqjwHcPMUS6ITUDHL9Rx0u-4k8rx0c4. It is a zip file, extract it to find an img file. Reboot to TWRP and select Install Image and install the file to oeminfo partition.
2. Perform a complete factory reset in TWRP.
3. Download the latest Nougat (3 files package) for FRD-L09C10 through Firmware Finder. Flash it using HuRupdater https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279.
4. After the flash is complete, reboot the device, unlock the bootloader again and flash TWRP.
5. Download the latest Oreo build for FRD-L09C10 through Firmware Finder. Using HuRupdater flash the three Oreo firmware files. Don't perform a factory reset this time.
6. Reboot your device. You're now on Oreo.
(brightness dimming still happening in some apps on oreo)
(I also have tested Pixel experience treble (GSI), and guess what? I got in bootloop, yeah... thanks huawei for the amazing software work ...)
Click to expand...
Click to collapse
I flashed Oreo onto my FRD-L04C567 using these instructions and now my device will not connect to LTE. It stays on 3g HSPA. Do you know how to reactivate the LTE radios?
jshealton said:
I flashed Oreo onto my FRD-L04C567 using these instructions and now my device will not connect to LTE. It stays on 3g HSPA. Do you know how to reactivate the LTE radios?
Click to expand...
Click to collapse
It's a know issue... I think @hackslash is the only one who can answer you
*** Use this at your very own risk.
***Backup your persist.img. There is a guide to fix it if needed.
*** Backup your working modem. Sometimes it is as simple as restoring it if you lose signal.
*** When flashing, you must understand the difference between fastboot and fastbootd to avoid flashing errors.
*** Backup your files in a safe place.
*** Some users are reporting that the whole thing is not working and going on a blame streak. So if you're not quite ready, please don't attempt this.
Basic Instructions: "I will test again since some users are losing signal after flashing". There is a debate whether msm and update the tmobile firmware, or flash the global. Again this is a WIP.
MSM. Here is the thread.
Unlock bootloader or re-unlock bootloader ... Enable OEM Unlock in developer options. flash token.
Fastboot
Code:
fastboot flash cust-unlock <unlock_token.bin>
Code:
fastboot oem unlock
and now your bootloader is unlocked.
Here is the t-mobile article for the 6t. same instructions for the 8 if you're new to this.
NEXT:
Link to fastboot thread
https://forum.xda-developers.com/oneplus-8/how-to/rom-stock-fastboot-roms-oneplus-8-t4084629
Download the global fastboot rom from here.
Unzip and flash all.
Link to twrp thread:
https://forum.xda-developers.com/oneplus-8/development/recovery-unofficial-twrp-oneplus-8-t4101315
If you want to root.
Boot into twrp or flash the twrp installer. TWRP 3.3.1-10 Test by mauronofrio and or TWRP 3.3.1-10 Test Installer by mauronofrio "newer ones may work"
After booting, you can flash magisk with-in twrp and you're rooted.
I have used oxygen updater to update the firmware while rooted. After the local install, open magisk and flash on the inactive slot.
---------------
If you ever want to revert, use the msm tool. Here is the thread.
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
---------
Old information from the old thread is below, if you want to use it only for reference or for backing up the FP persist
---------------
Old Instructions
Here we go .....
This is fairly new and hasn't been tested so, proceed with caution. There are more knowledgable people here. This was just tested quick and it worked.
Requirements
1-Be on T-mobile firmware and update to the latest version. If you are bootloader unlocked, you mean not be able to take OTA's and you may need to reflash with MSM and update, then unlock the bootloader again. Thread Thanks @Some_Random_Username
2 - Unlock your bootloader.
3- --! IMPORTANT: Make a TWRP backup of your MODEM because we'll restore that later, why? because t-mobile sim doesn't work on the Global Modem. You can also back everything up in TWRP just in case.
If you have OTG, make the backup there so it is safe. You can restore the modem through TWRP with the OTG.
4-Backup your persist. Otherwise you may lose the fingerprint.
You'll need root.
Code:
adb shell
HTML:
su
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Then
Code:
adb pull sdcard/persist.img
Then copy it from from Sdcard to a safe place
*** You may lose signal again if you update the global version. It is a WIP but keep your modem backed up!
With all the above:
It is simple. Download the global firmware and flash it through fastboot. Here is the thread
.. I tested with "10.5.5-GLOBAL-OnePlus8Oxygen_15.O.14" Thanks @mauronofrio
Reboot to fastboot
Unzip and flash-all
It will reboot to the global firmware. "Now you won't get cellphone signal"
Skip the setup and reboot to fastboot.
reboot to twrp, do not flash it.
Code:
fastboot boot twrp.img
link to twrp thread. . I used TWRP 3.3.1-2 Test by @mauronofrio
plug in the OTG or locate the backup and Restore the Modem" to get signal
Reboot and you'll have signal.
To root. you can flash the patched boot located in the sourceforge folder " Patched-Stock-Boot" on this thread
Code:
fastboot flash boot filename.img
You can also flash magisk in twrp. I prefer the patched boot.
Bonus: I am running the Nolimit magisk rom Thanks @xXx
https://forum.xda-developers.com/on...gisk-rom-xxx-nolimits-11-0-speed-ram-t4088609
Thanks @Some_Ghost for testing.
B-E-A-UTIFUL!
I'll wait to see others' results before I brick my phone.
rjp0615 said:
B-E-A-UTIFUL!
I'll wait to see others' results before I brick my phone.
Click to expand...
Click to collapse
It works no bricking. If something happened you can go back with MSM.
matteosaeed said:
Here we go .....
This is fairly new and hasn't been tested so, proceed with caution. There are more knowledgable people here. This was just tested quick and it worked.
Requirements
1-Be on T-mobile firmware and update to the latest version. If you are bootloader unlocked, you mean not be able to take OTA's and you may need to reflash with MSM and update, then unlock the bootloader again. Thread Thanks @Some_Random_Username
2 - Unlock your bootloader.
3- --! IMPORTANT: Make a TWRP backup of your MODEM because we'll restore that later, why? because t-mobile sim doesn't work on the Global Modem. You can also back everything up in TWRP just in case.
If you have OTG, make the backup there so it is safe. You can restore the modem through TWRP with the OTG.
4-Backup your persist. Otherwise you may lose the fingerprint.
*** You may lose signal again if you update the global version. It is a WIP but keep your modem backed up!
With all the above:
It is simple. Download the global firmware and flash it through fastboot. Here is the thread
.. I tested with "10.5.5-GLOBAL-OnePlus8Oxygen_15.O.14" Thanks @mauronofrio
Reboot to fastboot
Unzip and flash-all
It will reboot to the global firmware. "Now you won't get cellphone signal"
Skip the setup and reboot to fastboot.
reboot to twrp, do not flash it.
Code:
fastboot boot twrp.img
link to twrp thread. . I used TWRP 3.3.1-2 Test by @mauronofrio
plug in the OTG or locate the backup and Restore the Modem" to get signal
Reboot and you'll have signal.
To root. you can flash the patched boot located in the sourceforge folder " Patched-Stock-Boot" on this thread
Code:
fastboot flash boot filename.img
You can also flash magisk in twrp. I prefer the patched boot.
Bonus: I am running the Nolimit magisk rom Thanks @xXx
https://forum.xda-developers.com/on...gisk-rom-xxx-nolimits-11-0-speed-ram-t4088609
Thanks @Some_Ghost for testing.
Click to expand...
Click to collapse
Am I understanding correctly, we will have to re-flash the modem after EVERY update?
rjp0615 said:
Am I understanding correctly, we will have to re-flash the modem after EVERY update?
Click to expand...
Click to collapse
For the global, we don't know until we get it, but @Some_Ghost checked with the euro and signal stays, so you can do the euro version instead of the global and still keep the the signal without reflashing your modem.
Does anybody have the modem backup I lost mine and can't find fastboot for tmobile
The EU modem dont fix it I just need tmobile modem if anyone can can someone give be the modem either tarp backup or .img file so I can use data
very easy fix for modem get the ota after you flash global you do ota and modem works fastboot wont flash modem right
delete
---------- Post added at 02:38 AM ---------- Previous post was at 02:32 AM ----------
ecompton59 said:
The EU modem dont fix it I just need tmobile modem if anyone can can someone give be the modem either tarp backup or .img file so I can use data
Click to expand...
Click to collapse
If you flash your modem backup with Euro firm it sticks throughout updates so far... It didn't work for me on global. You still need to restore your modem backup on either firmwares. Global so far modem doesn't stick after updates, euro so far, it stays after updates.
Some_Ghost said:
delete
---------- Post added at 02:38 AM ---------- Previous post was at 02:32 AM ----------
If you flash your modem backup with Euro firm it sticks throughout updates so far... It didn't work for me on global. You still need to restore your modem backup on either firmwares. Global so far modem doesn't stick after updates, euro so far, it stays after updates.
Click to expand...
Click to collapse
I fixed it with ota if you flash global do the enable and and dev settings I waited to install magisk. Ayer first boot put ota for global and it works because ota has modem in it and fastboot can't flash modem yet with bat file but I have no issues I have global modem and global ROM and from here on ota will work no need for modem
not really converting to Global then? this is just so you can use dev ROM, but since DEV rom hasnt come about there really is no reason to do this.
Vio281 said:
not really converting to Global then? this is just so you can use dev ROM, but since DEV rom hasnt come about there really is no reason to do this.
Click to expand...
Click to collapse
What? He used global ROM. Not a DEV ROM.
ecompton59 said:
I fixed it with ota if you flash global do the enable and and dev settings I waited to install magisk. Ayer first boot put ota for global and it works because ota has modem in it and fastboot can't flash modem yet with bat file but I have no issues I have global modem and global ROM and from here on ota will work no need for modem
Click to expand...
Click to collapse
I will try this thanks ??
Does the Global ROM share the same 5G compatibility introduced in the new TMO ROM?
joemossjr said:
What? He used global ROM. Not a DEV ROM.
Click to expand...
Click to collapse
Thats what I'm saying, this is to flash rom, it not necessarily converting the phone to a global phone since it still need Tmobile Modem bin file in order to be function as a phone. If you take the phone outside the U.S it questionable if it works, that is why I say this is only for Dev Rom and in this case stock global rom but it is not a global phone.
@joemossjr
Vio281 said:
Thats what I'm saying, this is to flash rom, it not necessarily converting the phone to a global phone since it still need Tmobile Modem bin file in order to be function as a phone. If you take the phone outside the U.S it questionable if it works, that is why I say this is only for Dev Rom and in this case stock global rom but it is not a global phone.
Click to expand...
Click to collapse
Well check @ecompton59 's response. He was able to get things working.
The modem does work, just there is an issue with the fastboot flashing the modems. The TWRP restore of the modem is to get cell signal right away.
Here is what I did:
After I did what is in the first post in the thread:
I used oxygen updater to download the EU update and flashed it via "Local Upgrade" @Some_Ghost tested that as well.
There is signal. I believe that it may have flashed the modem "maybe", unlike fastboot.
While I was on the EU version, I downloaded the update for the global, and did a "Local Upgrade" again, and got signal.
I did all of this with Magisk being installed and after each "local upgrade, before reboot" I install Magisk on the "inactive slot, ota".
Technically speaking and don't quote me 100%, the first flash to the global is what gives issues with the sim, but that's the way to get the ability to do "local upgrade" because it is disabled on the t-mobile firmware.
Theoretically and I haven't tested.
Unlock bootloader >> Flash global "won't flash everything properly" = no signal
Global to another global or EU update >> will flash the modem >> signal will work "as it will properly flash everything"
matteosaeed said:
@joemossjr
Well check @ecompton59 's response. He was able to get things working.
The modem does work, just there is an issue with the fastboot flashing the modems. The TWRP restore of the modem is to get cell signal right away.
Here is what I did:
After I did what is in the first post in the thread:
I used oxygen updater to download the EU update and flashed it via "Local Upgrade" @Some_Ghost tested that as well.
There is signal. I believe that it may have flashed the modem "maybe", unlike fastboot.
While I was on the EU version, I downloaded the update for the global, and did a "Local Upgrade" again, and got signal.
I did all of this with Magisk being installed and after each "local upgrade, before reboot" I install Magisk on the "inactive slot, ota".
Technically speaking and don't quote me 100%, the first flash to the global is what gives issues with the sim, but that's the way to get the ability to do "local upgrade" because it is disabled on the t-mobile firmware.
Theoretically and I haven't tested.
Unlock bootloader >> Flash global "won't flash everything properly" = no signal
Global to another global or EU update >> will flash the modem >> signal will work "as it will properly flash everything"
Click to expand...
Click to collapse
again, this does not make it a global sim unlock phone, you are flashing a previous Tmobile Modem on top of a Global rom.
Vio281 said:
again, this does not make it a global sim unlock phone, you are flashing a previous Tmobile Modem on top of a Global rom.
Click to expand...
Click to collapse
It at least we can run different firmwares on T-Mobile. You could try the global msm on T-Mobile and report back. As being sim unlocked depends on the bands enabled in other countries but should work with any sim.
matteosaeed said:
It at least we can run different firmwares on T-Mobile. You could try the global msm on T-Mobile and report back. As being sim unlocked depends on the bands enabled in other countries but should work with any sim.
Click to expand...
Click to collapse
is there different functionality between the tmobile modem and global modem firmware? I flashed the global rom and am using that with tmobile modem flashed through twrp. I haven't done a local update yet to get the global modem. if I do, what is the difference running that vs the tmobile modem? im in seattle using tmobile anyway.... would I see a difference in anything? speed? I had updated to the tmobile ota right before I flashed, they supposedly updated something with the modem in that update. im just wondering if there is a benefit to using the global modem or not. I definitely see the benefit in using he global rom though....lol
bluemoel said:
is there different functionality between the tmobile modem and global modem firmware? I flashed the global rom and am using that with tmobile modem flashed through twrp. I haven't done a local update yet to get the global modem. if I do, what is the difference running that vs the tmobile modem? im in seattle using tmobile anyway.... would I see a difference in anything? speed? I had updated to the tmobile ota right before I flashed, they supposedly updated something with the modem in that update. im just wondering if there is a benefit to using the global modem or not. I definitely see the benefit in using he global rom though....lol
Click to expand...
Click to collapse
you'll be fine, my signal hasn't changed since flashing it remained the same as far as I can tell
---------- Post added at 12:34 PM ---------- Previous post was at 12:30 PM ----------
Vio281 said:
again, this does not make it a global sim unlock phone, you are flashing a previous Tmobile Modem on top of a Global rom.
Click to expand...
Click to collapse
Be happy that people actually take the time to experiment and work on things like this for the community so we can root and run different firmwares, kernels, and recoveries etc. At the least we aren't stuck on TMO firmware with lack of updates and missing features and as far as we can tell everything is working and odds are you aren't going to be using a T-Mobile SIM when going out of country anyway. Any issues will be ironed out when we cross that path I am sure ??