*** 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 ??
Related
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Tried flashing it. No success. Also the fiingerprint reader is also missing.
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
GeeteshKhatavkar said:
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
Click to expand...
Click to collapse
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
sabithmk said:
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
Click to expand...
Click to collapse
Which city ?I think you should go for the replacement and then update it via OTA when you get a notification.
Any Solutions Yet ?
Has anyone found any solutions yet !?
It is surely a Software issue
Service Center people are asking Rs.6500/- to replace the motherboard
Can't even relock the bootloader as i flashed the Nougat OTA and thus i can't downgrade the bootloader and lock it either !!
Please Help !
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
You found any solution?? I am facing the same problem...
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
I sent it for service and got a free replacement.
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
Yes I found it..
I created a thread. Check this.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
Check this link friend. I did it. Was having same problem as you.
Check the thread I created.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
echo92 said:
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
Click to expand...
Click to collapse
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
gioyocho said:
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
Click to expand...
Click to collapse
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
Check my link.
You can even OTA update in future if you installed the latest firmware.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
echo92 said:
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
Click to expand...
Click to collapse
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
gioyocho said:
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
Click to expand...
Click to collapse
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
echo92 said:
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
Click to expand...
Click to collapse
well i tried and did not work those run commands
This is for people who have received their phone with a pre-installed Vendor ROM (MIUI Global Stable 8.0.8.0) and wants to switch to the Unofficial EU ROM. In my opinion, the EU ROM is currently the best ROM without any Chinese bloatware or popups until Xiaomi decides to release an actual Global ROM.
For those who are already on a China Stable ROM, there is already an excellent guide to install TWRP, ROOT, compiled by @underlines. This is only intended for switching from a Vendor ROM as I wasn't able to switch from a Vendor ROM to an official build using the previous guide. You need to be on an official build to be able to use TWRP and flash the EU ROM.
EDIT : The reason why I have mentioned to flash an official build at first is because, TWRP can be unresponsive with some Vendor ROMS. You'll be able to boot TWRP but touch would be frozen. I've tried with both versions of TWRP and it wouldn't work with the Vendor ROM installed on my device. TWRP over the Vendor ROM may work for some users.. For some builds like the one which came installed on my phone, it may not work. If TWRP works for you without being on an official build, you can skip the part where you have to flash an official ROM.
1. You need to have an unlocked bootloader. Please follow instructions on the other guide on how to do this.
2. You need the older version of MiFlash found on this link. Thanks to @Thorin78 for this link.
3. Download and extract fastboot Stable or Dev ROM and extract ROM folder to the C:\ Drive. This is because MiFlash may show a "cannot find file" error if you have a lot of subfolders. To avoid this, its best if the folder is C:\ROM Folder.
4.In the older version of MiFlash, click advanced and change the fastboot script location to the flash_all.bat in your unzipped rom folder.
5.Connect your phone in fastboot mode, click "Refresh" in MiFlash. Once your phone is detected, click "Flash" and it should now successfully flash the official ROM of your choice.
If you wish to be on a Xiaomi Official Stable or Dev ROM, Stop here! If you wish to continue installing the EU ROM proceed with the steps below.
6. Now that you have successfully flashed Official Stable or Dev ROM, use Minimal ADB and flash TWRP RC2 using the instructions in the other guide.
7. Once you are in TWRP, Swipe right to allow System Modifications and copy the forced encryption disabler using MTP. Flash this file to ensure that there are no bootloops.
8. After this step, go to WIPE, Format Storage, type "yes" and then Reboot Recovery. Copy SuperSU and EU ROM to storage and flash. Phone may take a few minutes to boot up and you will successfully boot the EU ROM.
For everything else, please follow the guide posted by underlines.
TWRP EU RC2 works with the China Dev ROM as well. Once you Swipe to Right to allow modifications, don't forget to flash the latest dm-verity and forced encryption disabler script from here. This is to prevent the device going into a bootloop.
These are the steps I followed and I am on EU ROM. Hope this helps people who wish to switch to the EU ROM from the Vendor ROM.
The link to miflash takes you DL minimal adb?
jazz452 said:
The link to miflash takes you DL minimal adb?
Click to expand...
Click to collapse
Corrected. Thanks for letting me know! Cheers!
satishp said:
Corrected. Thanks for letting me know! Cheers!
Click to expand...
Click to collapse
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/
jazz452 said:
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/
Click to expand...
Click to collapse
I guess it also depends on the Vendor ROM and customization which comes installed on your device. Not all Vendor ROMs for this device are the same. I tried everything under the sun with the latest miflash. It would detect device and even give a "success" output but the ROM was never actually flashed. The phone would still be on the Vendor ROM. Its as if some Vendor ROMs have some form of write protection baked in.
I could only get it working with the older miflash.
I'm not saying it was easy, the hard thing was making the unpack ING of the file. Sort of did it twice never had that problem before.
Why is it required to flash the official rom before flashing the EU rom?
nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This for people who don't want TWRP, root and dm-verify, just genuine Xiaomi rom with OTA updates and remove vendor rom.
QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?
geubes said:
QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?
Click to expand...
Click to collapse
Wouldn't worry about it the vendor ROMs aren't poison, not sure about dm-verify if you kept read only. I would of swiped then flashed dm-verify but didn't mean I know what I'm doing.
nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This is because some Vendor ROMS have some compatibility issues with TWRP. Touch screen wouldn't work on TWRP. I tried both TWRP versions and couldn't get touch to work.
Finally, I flashed the China Dev ROM and then used TWRP RC2 and touch functionality worked.
As some users below have pointed out that they could get to EU without flashing the one of the official builds, I guess it depends on the amount or type of vendor customizations applied on your device.
Which version do you own? I was wondering if this would work with the 6GB as well.
dbesada said:
Which version do you own? I was wondering if this would work with the 6GB as well.
Click to expand...
Click to collapse
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.
satishp said:
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.
Click to expand...
Click to collapse
Thank you. It worked. I fastboot twrp then factory reset the device and flashed the eu rom. All good. My bootloader was unlocked by the vendor.
Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks
SantinoInc said:
Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks
Click to expand...
Click to collapse
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU
Razorbacktrack5535 said:
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU
Click to expand...
Click to collapse
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?
SantinoInc said:
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?
Click to expand...
Click to collapse
Yes, you have to use Fastboot Mode
Razorbacktrack5535 said:
Yes, you have to use Fastboot Mode
Click to expand...
Click to collapse
I'm not unlocked right? Hope they approve my unlock request soon
SantinoInc said:
I'm not unlocked right? Hope they approve my unlock request soon
Click to expand...
Click to collapse
Yes, you have to wait
Hi,
1. If somebody experience this issue with lack of netwrok after Nougat full Rom update, like:
https://forum.xda-developers.com/showpost.php?p=71063185&postcount=121
than follow this fix from another thread:
https://forum.xda-developers.com/showpost.php?p=71054990&postcount=1456
for me it all seems to work fine now.
2. If somebody has issues with MiFlash, I think it is actually better to do the flash within first 5-10, after that it gives strange errors. If so, restrt EDL and press flash on MiFlash a bit faster .
Regards
I failed to boot nougat using these steps:
Boot to edl.
Flashed using miflash full b15 file and then b15 twrp file.
Flashed in twrp a2017 N modem.
Then it gets stuck at 5 secs screen and phone just reboots back to edl. Am i doing it wrong?
However it boots to nougat if only flashing just the b15 full.
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
RubiCom said:
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
Click to expand...
Click to collapse
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Wuchko said:
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Click to expand...
Click to collapse
Hi,
If you MiFlash B15 Full package it overwrites recovery partition...it is a full package after all. If you want TWRP on your nougat after that you need to Miflsh the B15 TWRP package. However inside the TWRP package, there is also modem driver file which you need to first replace with the new modem file, same as with B15 FULL package.
It is al soooo simple. I had some issues with MiFlash initially, as I read somewhere to "keep the vol up down, power fo 5 sec, release, wait 5seconds and than flash"
However I had near 100% success rate when I did press the flash button around 2-5 seconds after booting into EDL mode. Once you do oem unlock, the process is simple as burning ISO image on a CD
I have it now without that last step. It is unlocked, but without TWRP. I did however MiFlashed TWRP yesterday and it did work fine than as well. I don't however think I need TWRP anymore. I did Dalvik etc. reset during upgrading to Nougat... and that's all I needed it for. Maybe I'm wrong and I will MiFlash it again some day, but honestly, this was first time I flashed any Android phone as I come from Nokia- Windows Phone and all I wanted is working Daydream, Netflix VR for my long business flights. It works now. The rest I might need I will install from play store.
It does have that message about unlocked bootloader when you boot the phone, but it does not bother me and I read somewhere that it is better not to relock he phone.
How do I even know if it's OTA capable? When I checked updates, it says your phone is up to date.
Regards
Ok, now is everything much more clear to me, thank you!
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
otaconremo said:
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
Click to expand...
Click to collapse
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Wuchko said:
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Click to expand...
Click to collapse
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
otaconremo said:
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
Click to expand...
Click to collapse
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Wuchko said:
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Click to expand...
Click to collapse
this is actually wierd. I had this problem my my sims. And I had flashed this many times already trying out different methods including miflash and even stock flashable zips from draken. all yields to the same results.
Do you have any idea where to tweak carrier settings from system files? i tried *#*#4636*#*# but still fails.
Unfortunately I don't know it. I guess I had plenty of luck flashing these ROM's, considering how many people have problems..
Since the 7.1.1 update for chinese a2017 isn't full update file, can we extract the modem from it?
I want to convert my unit to US version using miflash method and I have already done this before but I get problems with signal even after flashing chinese modem from LOS thread by @Unjustified Dev. Although, this signal problem is quite specific with my carrier since I get a stable OS and signal using a different carrier/sim.
I'm thinking about doing it via twrp. Here are the steps I had in mind:
1. From b13, update to 7.1.1 via stock recovery.
2. after finishing setup of 7.1.1, I'll install twrp via fastboot.
3. back up everything in twrp.
4. miflash full b15 US version and twrp.
5. restore modem from twrp from my backup.
Do you think this will work? Or not, since B15 isn't 7.1.1?
Hopefully devs here can also share their thoughts. @ @DrakenFX @Oki @jcadduono
Thanks!
BTW, I attached a pic of what's inside the 7.1.1 update including the contents of patch folder.
otaconremo said:
Since the 7.1.1 update for chinese a2017 isn't full update file, can we extract the modem from it?
I want to convert my unit to US version using miflash method and I have already done this before but I get problems with signal even after flashing chinese modem from LOS thread by @Unjustified Dev. Although, this signal problem is quite specific with my carrier since I get a stable OS and signal using a different carrier/sim.
I'm thinking about doing it via twrp. Here are the steps I had in mind:
1. From b13, update to 7.1.1 via stock recovery.
2. after finishing setup of 7.1.1, I'll install twrp via fastboot.
3. back up everything in twrp.
4. miflash full b15 US version and twrp.
5. restore modem from twrp from my backup.
Do you think this will work? Or not, since B15 isn't 7.1.1?
Hopefully devs here can also share their thoughts. @ @DrakenFX @Oki @jcadduono
Thanks!
BTW, I attached a pic of what's inside the 7.1.1 update including the contents of patch folder.
Click to expand...
Click to collapse
Any idea if this worked?
Also will the Chinese modem from the lineage OS thread work with the latest 7.1.1 update
Is it possible to install european modem on chinese variant? And do I need to unlock bootloader?
Fuilares said:
Is it possible to install european modem on chinese variant? And do I need to unlock bootloader?
Click to expand...
Click to collapse
You could but you probably won't have any signal, might even break wifi.
Modem/bootstack need to match device.
So, as we all know, we have to flash over international rom because of /vendor partition. But, can we flash over a bootloader unlocked T-Mobile ROM? Like, fully updated T-Mobile ROM/radio with twrp and bootloader and sim unlocked and flash havoc?
You can, nothing would stop you. However, you need to make sure that the security patch is the same or close.
Everytime I flash something over my T-MObile stock ROM I end up just flashing the international version recomended in the ROM OP. Then flashing the rom.
I would just take the extra step to flash the stable release then flash custom.
Yep. The bootloader in both International and T-Mobile firmware image are the same, with modem and device configuration partition being the only difference. You can flash whatever you want over any firmware images.
This is kind of why I really like OnePlus phones now, not to mention you pretty much can use a single UEFI payload bootloader contained inside the custom ROM for any model of a certain OnePlus phone (like OnePlus 6T in this case here), making it easier to support as far as development goes. I think I will be a OnePlus customer for life.
Sent from my OnePlus 6T using Tapatalk
So I sort of had the same question. If one slot is unlocked and the other is giving the red corrupt error message, can you switch slots in recovery, use the downloader tool and flash the unlockable image, and then unlock that slot to recover from the device corrupt message?
Scott said:
You can, nothing would stop you. However, you need to make sure that the security patch is the same or close.
Everytime I flash something over my T-MObile stock ROM I end up just flashing the international version recomended in the ROM OP. Then flashing the rom.
I would just take the extra step to flash the stable release then flash custom.
Click to expand...
Click to collapse
My reason is because I want to see if T-Mobile radio/modem is better for T-Mobile users than the international radio/modem
icedventimocha said:
So I sort of had the same question. If one slot is unlocked and the other is giving the red corrupt error message, can you switch slots in recovery, use the downloader tool and flash the unlockable image, and then unlock that slot to recover from the device corrupt message?
Click to expand...
Click to collapse
Yes, when your phone's bootloader is already unlocked, and you run into corrupted system partition, you just simply either switch the slot, or load the bootable TWRP image via USB fastboot, to restore the phone back to working condition.
Also, International version of modem firmware is the same as the T-Mobile version, with modem configuration (ie. SIM slots) being the dominant factor. T-Mobile modem firmware only allow one SIM card to be active (while also locked out of the box), while International version allows two outstanding SIM slots to be active (meaning you can enable or disable any SIM cards at will). Radio bands will be the same for both.
Sent from my OnePlus 6T using Tapatalk
jamescable said:
My reason is because I want to see if T-Mobile radio/modem is better for T-Mobile users than the international radio/modem
Click to expand...
Click to collapse
I would love to see your results.
I just flashed back to the T-Mobile version for now. IM full stock / rooted and want to compare battery life to International.
AFAIK ROMs require the latest Vendor from OxygenOS. While there should be no issues flashing, the TMO ROM is outdated and therefore doesn't have the latest Vendor (9.0.16) which can cause some issues. That's why it's recommended to flash Latest Stock OOS before flashing ROM. However if you don't want to flash Full OOS ZIP and just the Vendor, check in the AOSiP Thread. They have a flash able Vendor ZIP from 9.0.16